Toggle menu
27
118
35
903
SOURCE DCS WIKI
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

MTTP/ACC/A2A/INTERCEPT

From SOURCE DCS WIKI

07 / Quick Reaction Alert (QRA) — Overview

Quick Reaction Alert (QRA), termed "Airspace Control Alert" in US usage, is the standing peacetime posture NATO air forces maintain to protect sovereign and Allied airspace. Armed fighters and crews sit at high readiness so they can launch within minutes to identify, shadow, and if necessary escort or engage an aircraft that has entered, or is approaching, protected airspace without authorisation or without maintaining required communications.

Purpose

QRA(I) — the Interceptor role of QRA — is one of the peacetime activities carried out under NATO Integrated Air and Missile Defence (NIAMD), alongside the Air Surveillance and Control System (ASACS) and the Air Command and Control (Air C2) structure. Typical triggers for a scramble include: an aircraft entering national/Allied airspace without clearance, loss of radio contact with a civil aircraft, an aircraft deviating from its filed flight plan without notification, or an unidentified/unresponsive military contact approaching the border of Allied airspace.

Force Structure

Element Role
ASACS / CRC Ground- and air-based sensors build and maintain the Recognised Air Picture (RAP); a Control and Reporting Centre (CRC) tracks all air traffic within its assigned airspace 24/7/365.
Air C2 (CAOC) A Combined Air Operations Centre (for NATO, Uedem or Torrejón) authorises and directs the scramble, tasks the QRA(I) flight, and applies the current Rules of Engagement (ROE). This is also the agency that takes tactical control of the interceptor once handover occurs — see Step 4, Handover, below.
QRA(I) Flight Armed fighters (2-ship standard) held at cockpit- or runway-alert, ready to launch within a short, nationally-defined reaction time once tasked.

The remainder of this chapter follows a single QRA sortie in order: 1. Alert & Scramble Order → 2. Group-Up & Departure → 3. ATC Guidance (Transit) → 4. Handover → 5. Intercept & Tasking → 6. Recovery.


07.1 / Alert & Scramble Order

Reaction timelines and exact alert postures are nationally classified; publicly reported figures (e.g. UK QRA crews reported at readiness to be airborne within about 15 minutes) can be used as an unclassified planning reference for training purposes.

Scramble Notification

The scramble order is passed via the base's scramble phone (or equivalent dedicated alert line) direct from CAOC/CRC to the alert shed/squadron ops, triggering the launch sequence. Normal base, ground, tower, and departure operations from that point onward are covered in Base / Civil Operations

Scramble Order (filed by CAOC/ADCF)

Sourced from the publicly released FAA Order 7610.4J model — see Sources. Behind the scramble call above, the controlling agency (CAOC in the NATO structure; ADCF in the US/NORAD model this section is based on) identifies the mission to civil ATC as an active air-defence mission and files a short flight plan containing:

  • Call sign and aircraft type/equipment
  • Number of aircraft
  • Departure point
  • Proposed departure time — or simply the word "immediate"
  • Heading, altitude, and duration of flight
  • Remarks: frequency, type of climb, controlling agency, and desired transfer point

07.3 / ATC Guidance (Transit)

The following describes how a scramble is coordinated with civil air traffic control between launch and handover. This section is modelled on the publicly released US FAA/NORAD procedure (FAA Order 7610.4J, "Special Military Operations," 1998) as an unclassified, structurally representative reference — the equivalent German/Luftwaffe–DFS coordination procedure is not publicly published, but the underlying logic is broadly representative of how any NATO nation integrates a QRA launch into controlled civil airspace.

Once airborne, an interceptor does not go straight to a dedicated military-only frequency. It is worked by ordinary civil Air Traffic Control (ATC) like any other IFR flight, with priority/expedited handling, until tactical control is formally handed to the military radar unit directing the intercept — in the US model, the Air Defence Control Facility (ADCF), a military radar unit (Air Defence Sector / AWACS) that is the only type of unit authorised to direct interceptors. The CRC/CAOC in the NATO force structure above fills the equivalent role.

Airborne Orders (filed once the flight is up)

As early as possible after launch, the controlling agency separately files "airborne orders" with the relevant en-route/terminal ATC facilities, containing:

  • Call sign, aircraft type/number
  • Departure point and time
  • Heading and altitude
  • Route of flight, broken into three legs: departure route → route to a fix serving the operating/tasked area → route from that fix to the intercept/destination
  • Frequency, and MARSA (Military Authority Assumes Responsibility for Separation) status if applicable

Standing Authorisation & Squawk

For missions that cannot be conducted within normal ATC procedures, a standing pre-authorisation (in the US model, the FAA Authorization for Interceptor Operations, AFIO) allows active air-defence missions to proceed outside the normal clearance process. Aircraft operating under this authorisation squawk a dedicated identification code (Mode 3/A 7777 in the US model) so ATC and the controlling agency can positively track them even while outside the standard clearance framework.

Beyond Controlled Airspace: "Due Regard"

When an intercept and its supporting aircraft operate in controlled airspace beyond national territorial limits and a normal ATC clearance is impractical, the operation shifts to the "due regard" concept (from DOD FLIP, used for operations over the high seas): the controlling agency itself assumes responsibility for separating its aircraft from all observed traffic, in place of ATC. This only applies under specific conditions — e.g. the aircraft is in visual meteorological conditions, is within surveillance/radio contact of a radar facility, or carries its own separation-capable radar — and separation becomes the aircraft commander's own responsibility once outside the controlling agency's radar coverage.


07.4 / Handover (Transfer of Control)

The handoff from civil ATC to the controlling agency (CRC/CAOC, ADCF in the US model) is governed by a small set of rules, not a fixed altitude or distance:

  • The interceptor is retained under civil ATC control for as long as possible. ATC does not initiate the handoff on its own.
  • The controlling agency must request the transfer; it is not allowed to request control until the aircraft actually reaches the point where control must be assumed to carry out the intercept — i.e. it cannot take the aircraft "early, just in case."
  • When requested, ATC must expedite the transfer.
  • The transfer point (a time, fix, or altitude) is chosen so that no conflict remains with any other traffic still under the transferring facility's control.

Once handover is complete, the sequence transitions seamlessly into the intercept procedure — see Step 5, below.


07.5 / Intercept & Tasking

Following handover, the intercept controller runs the flight through one of two intercept types depending on the tactical picture: an ID intercept (radar/visual identification with follow-on tasking) also called a VID

ID Intercept

An Identification (ID) intercept establishes the type, registration, colour, and armament of an unknown contact by radar and/or visual means before follow-on tasking (shadow, intervention, radio interrogation, obey-check, or friendly termination) is assigned.

ID Result Format: Number of Acft, Type, Registration, Colour, Armament, SPEED, HEADING, ALTITUDE

Task: ID

Station Phrase
FL {CS} confirm ready to copy ID(-result)
Controller {Controller-CS} ready
FL Bogey is {Number} {Colour} {Acft Type}, registration {REGISTRATION}, {Armament}, at {Altitude}, Heading {HDG}, speed {Speed}
Controller {Controller-CS} copied, ({ID result}) new task {Task}
FL {CS} roger task {Task}

This concludes Task ID; the controller can then assign one of the following follow-on tasks: Shadow, Obey-Check, Radio Interrogation, Intervention, or Friendly/Terminate.

Task: Shadow

Station Phrase
Controller {CS} new task shadow
FL {Controller-CS} roger task shadow

Task Shadow means following the aircraft at a distance of approximately 1–2 NM without further closure.

Task: Obey-Check

Station Phrase
Controller {CS} new task obey-check, fly HDG {HDG}
FL {Controller-CS} task obey-check HDG {HDG}
FL {Controller-CS} bogey is playmate (or: aircraft is not obeying)
Controller {CS} copied

Obey-Check means the fighter rocks its wings and then flies a turn in the specified direction. While doing so, it observes the target and reports whether it also rocks its wings and follows ("playmate") or does not ("aircraft is not obeying").

Task: Radio Interrogation

Station Phrase
Controller {CS} new task radio interrogation (on simulated guard {Frequency})
FL {Controller-CS} roger, task radio interrogation
FL (on guard) {Colour} {Acft Type} {Position}, with registration {REGISTRATION} (squawking {Squawk}) this is the eurofighter on your left wing calling on (simulated) guard ({Frequency}) you have been intercepted by the german air force. For purpose of identification state: Registration, Callsign, aerodrome of departure and aerodrome of destination on (simulated) guard ({Frequency})
Intercepted Acft (German Interceptor) this is {Callsign} registration {REG} on guard, departure is {ICAO}, destination {ICAO}
FL Roger, standby
FL {Controller-CS} did you copy (the answer) on guard?
Controller Affirmative / Negative

If the controller did not copy the response on guard, the fighter relays the answer. After this, termination is possible, or further tasks may follow.

Task: Intervention

Station Phrase
Controller {CS} new task intervention to {ICAO}
FL {Controller-CS} roger, intervention to {ICAO}
Further radio follows the Intercept Call, kneeboard side (see below)

During Interrogation and Intervention, the fighter flies to the left of the target at cockpit height (the pilot in command usually sits on the left).

Intercept Call:

Station Phrase
Interceptor INTERCEPTED AIRCRAFT this is german INTERCEPTOR callsign {Callsign}, you will be intervented to {Airport} FOLLOW, FOLLOW
Intercepted Acft WILCO / CAN NOT
Interceptor What is your callsign?
Intercepted Acft CALL SIGN {Callsign}
Interceptor Descend to altitude {ALT} ft, QNH {HPA}
Intercepted Acft WILCO / CAN NOT
Interceptor What is your preferred approach speed?
Intercepted Acft {Speed}
Interceptor What is your gear down speed?
Intercepted Acft {Speed}
Interceptor This is your airport, after split up join right/left hand pattern of RWY {NR} at {Altitude} feet, QNH {HPA}; YOU LAND, YOU LAND
Intercepted Acft WILCO

Phrases used by the intercepted aircraft (ICAO standard responses):

Phrase Meaning
CALL SIGN (callsign) My callsign is....
WILCO Understood. I will perform
CAN NOT Unable to perform
REPEAT Repeat the instructions
AM LOST Unknown location
MAYDAY They are in danger
HIJACK I was hijacked
LAND (location) I ask to land at...
DESCEND I ask to descend

Post-Intercept Options

Following identification (ID or VID), the QRA(I) flight is normally tasked to shadow or escort the contact out of the airspace, hand it to a follow-on national asset, or — in the case of a genuine emergency (lost comms, distress) — assist it to a safe landing per the Intervention procedure above. Engagement is authorised only as an absolute last resort and strictly IAW the current ROE issued by Air C2.


07.6 / Recovery

Once tasking is complete and the flight is terminated (see Termination, above), control jurisdiction reverts from the intercept controller (CRC/ADCF) back to civil ATC for the return-to-base and recovery phase — this happens once the flight is clear of any other traffic still under the controlling agency's control.

From this handback point onward, the sortie is flown as normal IFR traffic under standard ATC procedures; see [SOURCE ATC/Recovery document — link TBD] for departure/arrival handling, approach, and landing sequencing. Not duplicated here.


Sources / Further Reading

Please review and approve before I link footnotes in the wiki:

Quick Reaction Alert (QRA) — NATO:

Civil ATC Interface — Scramble Order, Transit, Handover (US/NORAD model, used illustratively):

  • FAA Order 7610.4J — "Special Military Operations," 3 November 1998, Distribution Statement A (public release). Chapter 4: "FAA/NORAD/PACAF Procedures for Control of Air Defense Aircraft" — covers ADCF control instructions, transfer-of-control rules, scramble/airborne order format, AFIO, and "due regard" operations. Superseded internally by the current, FOUO-restricted JO 7610.4 (sensitive) / JO 7610.14 (non-sensitive) editions; this 1998 edition remains the last fully public release and is archived via DTIC, accession no. ADA355579. — https://apps.dtic.mil/sti/tr/pdf/ADA355579.pdf
  • FAA Order JO 7110.65 — Air Traffic Control (current edition), §9-2-7 "Interceptor Operations" — baseline ATC separation/priority handling for active air-defence scrambles — https://www.faa.gov/air_traffic/publications/atpubs/atc_html/chap9_section_2.html

Intercept & Tasking (ID / VID):

Note: Exact QRA reaction times and alert levels are nationally classified; the ~15 minutes mentioned in Step 1 is a publicly known, unclassified reference figure (RAF), not an official NATO standard. Likewise, Steps 3–4 (ATC Guidance/Handover) reflect the publicly available US/NORAD procedural model; the exact German/Luftwaffe scramble-to-ATC coordination procedure is not publicly published.