SOURCE DCS WIKI - User contributions [en]

MTTP/A2A

2026-06-11T15:57:13Z

Niknam3:

== 01 / Overview ==
Air combat is primarily carried out by CAP aircraft. The two main mission types are '''DCA''' (Defensive Counter Air) and '''OCA''' (Offensive Counter Air).

=== Groups and Contacts ===
A '''GROUP''' is any number of air contacts within 3 nm in azimuth and range of each other. A '''CONTACT''' is an individual radar return within a GROUP. Single contact is the assumed strength for all GROUPs unless otherwise specified. A GROUP with three or more contacts is called '''HEAVY'''.

The '''PICTURE''' establishes a common tactical air image and describes the spatial relationship of GROUPs. It is always communicated in BULLSEYE format unless briefed otherwise. Only the Three GROUPs with highest Priority are Conveyed

=== Contact Declaration ===
Before a fighter can engage, a contact must be declared. Declaration is performed by the controller in response to a DECLARE request.

{| class="wikitable" style="width:100%;"
|-
! Declaration !! Meaning !! Engagement Authority
|-
| '''BOGEY''' || Identity unknown || Not cleared to engage
|-
| '''OUTLAW''' || Originates from known or suspected hostile area || Not cleared to engage; escalation criteria apply
|-
| '''SPADES''' || No valid IFF response on interrogation || Not cleared to engage; escalation criteria apply
|-
| '''BANDIT''' || Positively identified as enemy IAW theater ID criteria || Not cleared to engage; does not imply authority to fire
|-
| '''HOSTILE''' || Confirmed enemy; clearance to fire authorized IAW ROE || Cleared to engage
|-
| '''NEUTRAL''' || Positively identified as neutral || Not cleared to engage
|-
| '''FRIENDLY''' || Positively identified as friendly || Not cleared to engage
|-
| '''FURBALL''' || Friendly and non-friendly aircraft within 5 nm || Employment not authorized until resolved
|}

A BOGEY, BANDIT, OUTLAW, or SPADES classification does not authorize engagement. HOSTILE is the only declaration that authorizes weapons employment IAW ROE.

== 02 / Important Concepts ==

=== Communication Cadence by Phase ===
Communication priority shifts between the controller and fighters depending on the phase of the intercept.

{| class="wikitable" style="width:100%;"
|-
! Phase !! Priority Communicators
|-
| Pre-COMMIT / Marshal || 1. Controller · 2. Fighters
|-
| Post-COMMIT / Push || 1. Controller · 2. Fighter
|-
| Targeting / Weapons Employment || 1. Fighters · 2. Controller
|-
| Merge || 1. Engaged Fighter · 2. Supporting Fighters · 3. Controller
|-
| Post-Merge || 1. Fighter Clearing Merge · 2. Supporting Fighters · 3. Controller
|}

=== TAC Range ===
Called at 60 nm (default) by the first asset to recognize the separation. Signals all players to prepare for targeting. Pre-commit SA building continues until this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Fighter || {CS} {Group Label} TAC RANGE
|}

=== Airspace Sanitization ===
A Section consists of two aircraft, each equipped with its own radar. Regardless of the number of bars or maximum azimuth a single radar supports, no single system can cover the entire sky. To compensate, both radars are stacked and assigned to different portions of the airspace — each portion is called an '''Area of Responsibility (AOR)'''. This technique, known as '''Radar Mating''', vastly increases the total volume scanned and ensures that no unknown contacts are operating in the area beyond already-tracked groups. The exact parameters depend on the aircraft type: the US Navy recommends RWS, 140°, 6 bars, end scale 80 nm, with radars mated at 25 nm: placing the flight lead between 40,000 and 15,000 ft, and the wingman from ground level to 25,000 ft.

The process of actively scanning assigned AORs to confirm no unknown contacts are present is called '''Sanitisation'''.

Because both Radar Mating parameters and Sanitisation responsibilities directly affect how an engagement develops, all of this must be '''pre-briefed''' and set as a '''contract''' before the mission. Time pressure may not always permit a thorough sanitisation pass, and how to handle that contingency should likewise be agreed upon in the brief.

=== Targeting ===
The flight assigns GROUP responsibility and confirms classification.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} DECLARE {Group Label or Bullseye Position}
|-
| Controller || {Group Label} DECLARED {HOSTILE / BOGEY / FRIENDLY / UNABLE / FURBALL}
|-
| FL || {CS} TARGET {Group Label} {Tactic}
|-
| colspan="2" style="text-align:center;" | ''Once group appears on radar''
|-
| FL || {CS} TARGETED {Group Label} BULLSEYE {Bearing/Range}
|-
| Controller || ''No response if information correlates. Comparative response if correction is required.''
|}

== 03 / Common Calls ==

=== DECLARE ===
Inquiry as to the identity of a specified GROUP. Full positional data in BULLSEYE format must accompany all responses.
MIKE, EAGLE 11, DECLARE NORTH GROUP.
EAGLE 11, NORTH GROUP BULLSEYE 2-7-3/27, TWENTY-TWO THOUSAND, TRACK EAST, BOGEY SPADES.

=== BOGEY DOPE ===
Request for BRAA information on the indicated GROUP or the closest GROUP if not specified. Does not imply fighter targeting.
MIKE, EAGLE 11, BOGEY DOPE NORTH GROUP.
EAGLE 11, NORTH GROUP BRAA 2-1-0/28, THIRTY-EIGHT THOUSAND, HOT, HOSTILE.

=== NAILS ===
Fighter's radar warning receiver is detecting an airborne interceptor radar in search mode. Called with bearing or cardinal direction.
EAGLE 1, NAILS 2-7-0.

=== SPIKED ===
Fighter is being actively tracked by an airborne radar. Called with bearing or cardinal direction. Controller correlates to a GROUP within ±30 degrees and responds with range, altitude, aspect, declaration, and GROUP name.
EAGLE 1, SPIKED 2-7-0.
EAGLE 1, SPIKE RANGE 17, THIRTY THOUSAND, HOSTILE EAST GROUP, TWO CONTACTS.

=== THREAT Call ===
If a fighter will pierce THREAT range to an untargeted GROUP, the controller makes a THREAT call in BRAA format no later than THREAT range.
HEAT 31, ADDITIONAL GROUP THREAT, BRAA 1-2-5/35, THIRTY-FIVE THOUSAND, HOT, HOSTILE.

If the THREAT is within 5 nm of friendly fighters:
BOLT 1, THREAT NORTH THREE, TEN THOUSAND, TRACK SOUTH, HOSTILE.

=== FADED and VANISHED ===
'''FADED''' — a previously tracked GROUP not updated by sensors for 30 seconds. The controller reports the GROUP as FADED with last known BULLSEYE position. Fighters maintain MONITOR responsibility if they can maintain correlation. FADED is not used for friendly aircraft — controllers use NEGATIVE CONTACT for friendlies not held on sensors.

'''VANISHED''' — a special case of FADED used when the GROUP is not in a known blind zone and is correlated to a friendly shot that meets parameters for successful termination.

=== Unexpected Contacts ===
Three distinct call types exist for contacts not part of the established picture:

{| class="wikitable" style="width:100%;"
|-
! Call !! Criteria !! Format
|-
| '''ADDITIONAL GROUP''' || Newly detected outside targeting range, or does not fit traditional label || BULLSEYE
|-
| '''POP-UP GROUP''' || Previously undetected; appears inside targeting range but outside THREAT range || BULLSEYE
|-
| '''THREAT GROUP''' || Undetected or unreported GROUP meeting briefed THREAT criteria || BRAA to the closest aircraft
|}

DARKSTAR, POP-UP GROUP BULLSEYE 2-7-0/15, FIVE THOUSAND, TRACK WEST, BOGEY SPADES.
RAMBO 2, THREAT GROUP BRAA 2-7-0/13, ONE THOUSAND, HOT, HOSTILE.

== 04 / Engagement ==
The engagement loop is the core sequence executed by all fighter flights once committed and targeting is established. It repeats until the GROUP is splashed, leaves the area, or the flight resets.

=== MELD ===
The flight lead directs all flight members to shift their radars from wide sanitization to focused SA on the assigned GROUP. This transition narrows the radar from maximum azimuth and altitude coverage to a tighter volume centered on the target. Sanitization of the surrounding airspace ceases until DROPPING is called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''All flight members shift radar from sanitization to the assigned GROUP''
|}

=== SORT ===
The flight lead assigns individual contacts within the GROUP to specific flight members. Each member acknowledges with SORTED when they have confirmed their assigned contact on radar and are prepared to engage it. If a member cannot confirm their assigned contact, SORTED is withheld until resolution.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || ''(intraflight) FLIGHT SORT {Criteria}''
|-
| #2 || ''(intraflight) #2 SORTED''
|-
| #3 || ''(intraflight) #3 SORTED''
|-
| #4 || ''(intraflight) #4 SORTED''
|}

=== JUDY ===
Called by the flight lead when the flight no longer requires controller guidance to prosecute the intercept. From this point, the controller minimizes transmissions and provides situational awareness information only. JUDY is not always called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Provides SA and THREAT calls only.''
|}

=== ENGAGE ===
Directive call from the flight lead to a specific wingman to employ weapons. The flight lead may also direct simultaneous employment by multiple members.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} ENGAGE
|-
| Wingman || {CS}
|}

=== Weapon Employment ===
The firing aircraft calls the shot on TACC2 NET immediately after employment. The call includes shot type, GROUP label, contact description, BULLSEYE position, and altitude. The controller acknowledges with COPY SHOT.

If a fighter determines a GROUP HOSTILE and ROE has been met, the fighter may employ autonomously and include HOSTILE in the shot transmission.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft || {TACC2-CS} {CS} FOX THREE {Group Label} {Contact Description} BULLSEYE {Bearing/Range} {Altitude}
|-
| TACC2 || {TACC2-CS} COPY SHOT
|-
| colspan="2" style="text-align:center;" | ''Autonomous HOSTILE employment''
|-
| Firing Aircraft || {Controller-CS} {CS} FOX THREE {Group Label} BULLSEYE {Bearing/Range} {Altitude} HOSTILE
|-
| TACC2 || {TACC2-CS} COPY SHOT
|}

Multiple shots in one transmission are acceptable:
SHADOW12 FOX THREE NORTH GROUP LEAD CONTACT BULLSEYE 2-7-0/20 TWENTY THOUSAND; SHADOW11 FOX THREE NORTH GROUP TRAIL CONTACT.

=== OUT / DEFENDING ===
Following weapon employment the flight turns away from the threat. OUT is a planned maneuver executed at a prebriefed range. DEFENDING indicates a reactive maneuver against an incoming weapon and is called with the cardinal direction of the defensive turn.

OUT cancels targeting responsibility

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction}
|-
| colspan="2" style="text-align:center;" | ''or, if reacting to an incoming weapon''
|-
| Aircraft || {CS} DEFENDING {Direction}
|}

=== DROPPING ===
May be called in conjunction with OUT. Signals the controller that the flight has ceased monitoring the GROUP and is returning to sanitization radar settings. Monitoring responsibility transfers back to the controller. Targeting responsibility is cancelled

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction} DROPPING {Group Label}
|-
| colspan="2" style="text-align:center;" | ''Controller resumes monitoring of the dropped GROUP''
|-
| Controller || ''Resumes monitoring.''
|}

=== Assessment ===
The flight assesses weapon effects from sensor data or controller reports. Three outcomes are possible:

{| class="wikitable" style="width:100%;"
|-
! Outcome !! Action
|-
| GROUP splashed || Call SPLASH
|-
| GROUP remains a factor, follow-up shot required || Turn IN, return to MELD
|-
| GROUP has left the area or is no longer a factor || Proceed with Tasking
|}

=== IN (Follow-up Engagement) ===
If the GROUP remains a factor and the tactic permits a follow-up shot, the flight turns back toward the GROUP. The IN call triggers a new cycle beginning at MELD.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IN {Direction}
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''Re-sort as required, then return to ENGAGE''
|}

=== SPLASH ===
Called when weapon effects confirm the GROUP or contact is destroyed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft or Controller || {CS} SPLASH {Group Label or Contact Description}
|}

----

== 05 / Defensive Counter Air (DCA) ==
DCA is the use of fighter aircraft to defend a ground asset or airspace against hostile air threats. It uses prebriefed lanes and defined ranges.

=== DCA Range Structure ===
All ranges are prebriefed per sortie. The following are the standard range lines used in DCA:

{| class="wikitable" style="width:100%;"
|-
! Range Line !! Definition
|-
| '''Mission Fail Line''' || The line the enemy must not cross for the mission to succeed. Defines the maximum depth of the defensive problem.
|-
| '''Commit Line (CL)''' || The line at which a bogey is declared HOSTILE IAW theater ROE and the flight is authorized to commit. Prebriefed for all DCA sorties.
|-
| '''Targeting Range''' || The prebriefed distance at which all contacts must be intercepted. A GROUP inside this range with no assigned fighter is UNTARGETED. Prebriefed per sortie.
|-
| '''TAC Range''' || Default 60 nm from the closest fighter to the closest GROUP. Signals all players to prepare for targeting.
|-
| '''Threat Range''' || The prebriefed range at which an untargeted GROUP meeting THREAT criteria triggers a THREAT call. Prebriefed per sortie.
|}

=== COMMIT Authority ===
COMMIT authority is derived from the combatant commander and delegated through the chain of command. Any of the following may hold or recommend COMMIT authority depending on what is delegated:

{| class="wikitable" style="width:100%;"
|-
! Role !! Abbreviation !! Authority
|-
| Flight Lead || FL || Usually holds COMMIT authority unless delegated
|-
| Team Lead || TL || May hold COMMIT authority if delegated
|-
| Mission Commander || MC || May hold COMMIT authority if delegated
|-
| TACC2 || — || May hold COMMIT authority if delegated
|}

If only the MC, TL, or FL holds COMMIT authority, the controller may only recommend COMMIT. If the controller holds COMMIT authority, the MC and TL may only recommend.

=== DCA Flow ===

==== Lane Handover ====
When an outgoing flight is relieved on station by an incoming flight, a positive lane handover is required before the outgoing flight departs.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Off-going Lane Commander || {CS} MOVE FORWARD
|-
| On-coming Lane Commander || {CS}
|-
| colspan="2" style="text-align:center;" | ''On-coming aircraft may enter the lane. Lane commander authority has not yet transferred.''
|-
| Off-going Lane Commander || {CS} YOU HAVE THE LANE
|-
| On-coming Lane Commander || {CS} HAS THE LANE
|}

The off-going flight passes critical mission information to the controller before departing. The controller passes big-picture information to the on-coming flight before pushing them to the tactical frequency.

==== Pre-Commit ====
The flight arrives at its prebriefed CAP position with FENCE IN complete and radars in sanitization configuration. The controller holds picture responsibility.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} PICTURE
|-
| Controller || {CS} {Nr of Groups} {Group Label} BULLSEYE {Bearing/Range} {Altitude} TRACK {Direction} {Declaration} {Nr of Contacts}
|}

The flight evaluates commit criteria continuously. Pictures are requested as needed to maintain SA.

==== Commit ====

===== FIGHTER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} Recommend {CS} COMMIT
|-
| FL || {CS} COMMIT
|}

===== CONTROLLER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} Recommend Commit
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} {CS} COMMIT
|-
|FL
|{CS}
|}

After COMMIT, fighters hold radio priority.

=== Engagement Loop ===
The flight executes the standard engagement loop as defined above The loop repeats until the GROUP is splashed, leaves the lane, or:

Once the Engagement is Complete the flight '''RESETS''' back to the briefed Position

==== RESET ====
Directs the flight to return to its prebriefed position or area of operations. RESET implies DROPPING and returns all targeting responsibility to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} RESET
|-
| colspan="2" style="text-align:center;" | ''Flight returns to prebriefed CAP position. Controller resumes full picture responsibility''
|}

----

== 06 / Offensive Counter Air (OCA) ==
OCA is the use of fighter aircraft to suppress, destroy, or neutralize enemy air assets before they can threaten friendly forces. Unlike DCA, OCA is not lane-based and does not require a commit line. The flight pushes into the threat environment rather than waiting for the threat to approach.

=== OCA Range Structure ===
The same range lines apply as in DCA — Threat Range, Targeting Range, and TAC Range — but all are prebriefed based on the specific mission geometry and threat environment. There is no commit line or mission fail line in OCA.

=== OCA Flow ===
OCA does not have a lane handover or a commit phase. The flight checks in, receives the picture, establishes targeting, and executes the engagement loop.

==== FULL COMMUNICATIONS EXAMPLE ====
In this Scenario, SHADOW11 four-ship F16C on OCA. TACC2 Agency CS THUMPER executing Positive Control. The Example begins after the Handover. Check In was done on the previous Frequency. TAC RANGE 60, THREAT RANGE 30
THUMPER SHADOW11 PICTURE

THUMPER PICTURE TEN GROUPS GROUP BULLSEYE 0-2-0/25, TWENTY-SEVEN THOUSAND, THOUSAND, TRACK EAST, HOSTILE, HEAVY, THREE CONTACTS. GROUP BULLSEYE 2-7-0/25, FIFTEEN THOUSAND, TRACK WEST, HOSTILE. GROUP BULLSEYE 2-9-0/35, TEN THOUSAND, TRACK WEST, HOSTILE.

SHADOW11 TARGETED GROUP BULLSEYE 0-2-0/25

SHADOW11 GROUP BULLSEYE 0-2-0/25 TAC RANGE

SHADOW11 SKATE, MELD

SHADOW11 SORTED

SHADOW11 FOX3 BULLSEYE 0-2-0/25

THUMPER COPY SHOT

SHADOW11 OUT SOUTH DROPPING

THUMPER

THUMPER SHADOW11 BOGEYDOPE

SHADOW11 EAST GROUP BRAA 2-1-0/28, FIFTEEN-THOUSAND, COLD, HOSTILE

SHADOW11 IN, MELD

SHADOW11 SORTED

THUMPER SHADOW11 SPLASH EAST GROUP

THUMPER
In the Following Example additional Adversarys Pop Up within Threat Range of SHADOW11
SHADOW11 THUMPER THREAT GROUP, BRAA 1-2-5/28, FIVE-THOUSAND, HOT, HOSTILE, 2 CONTACTS

SHADOW11 TARGETED SORTED LEAD, FOX 3 LEADER, FOX3 TRAILER, BULLSEYE 0-5-0/45, FIVE-THOUSAND

THUMPER COPY SHOTS

SHADOW11 DEFENDING SOUTH, DROPPING

THUMPER

SHADOW11 THUMPER THREAT GROUP, BRAA 0-6-0/15, TWO-THOUSAND, COLD, HOSTILE

SHADOW11

SHADOW11 IN

SHADOW11 FOX3 BULLSEYE 0-6-0/15, TWO-THOUSAND

THUMPER COPY SHOT

SHADOW11 THUMPER THREAT GROUP VANISHED
----

== 07 / QRA ==

== 08 / Intercept (VID) ==
A Visual Identification (VID) intercept is conducted when a contact cannot be declared HOSTILE or FRIENDLY by electronic means alone, and visual confirmation of aircraft type, markings, or behavior is required before engagement authority can be granted or withheld.

VID intercepts follow a structured sequence: the controller guides the fighter to a position from which a visual identification pass can be made, then the fighter reports the result and awaits further direction.

=== Intercept Flow ===

==== Commit ====
The controller or flight lead initiates the intercept against the unidentified contact.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} COMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration} {Nr of Contacts}
|-
| FL || {CS} COMMIT
|}

==== Guidance ====
The controller provides vectors to position the fighter for a VID pass. This is the only phase where the controller takes positive close control of the intercept geometry. BRAA format is used throughout.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} BRAA {Bearing/Range} {Altitude} {Aspect} {Declaration}
|-
| FL || {CS}
|-
| colspan="2" style="text-align:center;" | ''Controller continues to provide updated vectors until fighter calls JUDY''
|}

==== JUDY ====
The fighter calls JUDY when radar contact is established and no further controller guidance is required. The controller minimizes transmissions from this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Continues to provide SA information only.''
|}

==== Tally ====
The fighter calls TALLY when visual contact is established with the target.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} TALLY {Position}
|}

==== Identification ====
The fighter conducts the VID pass and reports the result to the controller. The report includes aircraft type, markings, and behavior observed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IDENTIFIED {Aircraft Type} {Markings / Behavior}
|-
| Controller || {CS} {Further Instructions / Declaration Update}
|}

If the contact is identified as HOSTILE following the VID pass, the controller issues the updated declaration and the flight may proceed to engagement IAW ROE. If the contact is FRIENDLY or NEUTRAL, the flight disengages and returns to its prebriefed position.

----

== 09 / Merge ==
A merge occurs when friendly and target aircraft arrive in the visual arena, within 3–5 nm of each other. At the merge, radar resolution becomes limiting and the engagement transitions from BVR to Within Visual Range (WVR). The engagement is now managed through ACM contracts and direct communication between flight members.

=== Authority and Radio Priority ===
Two distinct concepts govern merge communications: '''authority''' and '''radio priority'''.

'''Authority''' remains with the Flight Lead throughout the engagement. The FL can override, redirect, or terminate the engagement at any time regardless of who is engaged.

'''Radio priority''' belongs to the engaged fighter. Other flight members subordinate their transmissions to avoid stepping on critical engaged fighter calls. The controller minimizes transmissions entirely and provides only THREAT calls, SA updates, and responses to direct requests.

{| class="wikitable" style="width:100%;"
|-
! Role !! Authority !! Radio Priority
|-
| '''Flight Lead''' || Full authority over the engagement at all times || Secondary — subordinates to engaged fighter
|-
| '''Engaged Fighter''' || Manages own engagement IAW FL direction || Primary — holds radio priority
|-
| '''Supporting Fighter''' || Executes IAW engaged fighter and FL direction || Tertiary — transmits only when necessary
|-
| '''Controller''' || Provides SA only || Minimal — THREAT calls and direct requests only
|}

=== MERGED ===
The controller calls MERGED when radar tracks come together within 3–5 nm, or the engaged fighter calls it when visual contact is made at the merge.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Engaged Fighter || {CS} MERGED {Group Label}
|}

=== Role Assignment ===
At or before the merge, engaged and supporting roles must be clearly established. By default the flight lead is engaged. Roles can be assigned or transferred in two ways:

==== Wingman-Initiated Transfer ====
The wingman identifies he is the engaged fighter based on the bandit's plane of motion and lift vector orientation, and calls it.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Wingman || #2 ENGAGED
|-
| Flight Lead || PRESS
|}

==== Flight Lead-Initiated Transfer ====
The flight lead recognizes the wingman is the engaged fighter and assigns the role.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || #2 PRESS
|-
| Wingman || #2 ENGAGED
|}

==== Bandit Switches ====
If the bandit maneuvers to engage the other fighter, the currently engaged fighter communicates the change.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || BANDIT SWITCHED
|-
| colspan="2" style="text-align:center;" | ''Roles are reassessed and reassigned as required''
|}

=== Engaged Fighter SA Calls ===
The engaged fighter is responsible for narrating the fight to maintain the supporting fighter's situational awareness. This enables the supporting fighter to position correctly and employ at the right moment. SA calls include the fight geometry, altitude, and direction.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || {CS} ENGAGED {ONE / TWO CIRCLE} {Direction} {Altitude}
|}

VIPER 1, ENGAGED ONE CIRCLE CLIMBING THROUGH FIFTEEN THOUSAND.
VIPER 1, ENGAGED TWO CIRCLE NORTHBOUND BANDITS LOW TWO'S HIGH.

These calls are made continuously as the fight develops, not just once at the merge. The supporting fighter cannot position or employ safely without them.

=== STATUS Calls ===
STATUS is a request from the supporting fighter for a specific situational update from the engaged fighter. It is the primary tool for IFF at the merge. A generic STATUS call returns a general update. A specific STATUS call asks a targeted question and returns a more useful answer.

The supporting fighter should tailor the STATUS call to the specific information needed to resolve the IFF situation. Generic STATUS calls are acceptable but specific calls are faster and more effective.

{| class="wikitable" style="width:100%;"
|-
! Call !! Question Being Asked !! Example Response
|-
| '''STATUS''' || General situation update || ENGAGED ONE CIRCLE NORTHBOUND BANDITS LOW TWO'S HIGH
|-
| '''STATUS HIGH/LOW''' || Which aircraft is higher || BANDITS LOW TWO'S HIGH
|-
| '''STATUS NOSE HIGH/NOSE LOW''' || Which aircraft has nose above or below horizon || TWO'S NOSE HIGH BANDIT NOSE LOW
|-
| '''STATUS LEFT/RIGHT''' || Which aircraft is left or right || TWO'S LEFT BANDIT RIGHT
|-
| '''STATUS NORTH/SOUTH/EAST/WEST''' || Cardinal orientation of aircraft in the fight || TWO'S NORTH BANDIT SOUTH
|}

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || {CS} STATUS {Qualifier if applicable}
|-
| Engaged Fighter || {Specific SA answer to the STATUS question}
|}

Supporting Fighter: TWO STATUS HIGH LOW.
Engaged Fighter: BANDITS LOW TWO'S HIGH.

If a STATUS call returns an ambiguous response, rephrase with a more specific qualifier before resorting to a FLASH call.

As a last resort, a FLASH call can be used to add physical confirmation to IFF — for example FLASH FLARES or FLASH BURNER. This directs the wingman to briefly activate the specified system so the supporting fighter can visually confirm identity. Exercise extreme caution — the bandit may also be employing flares, and a mistaken identification cannot be undone.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || FLASH {FLARES / BURNER}
|-
| Wingman || ''(executes flash of specified system briefly)''
|}

=== IFF Brevity ===
Standard brevity calls for visual identification status:

{| class="wikitable" style="width:100%;"
|-
! Term !! Meaning
|-
| '''TALLY''' || Visual contact established on the target or bandit
|-
| '''NO JOY''' || No visual contact with the target or bandit
|-
| '''VISUAL''' || Visual contact established on a friendly aircraft
|-
| '''BLIND''' || No visual contact with a friendly aircraft
|}

IFF must be confirmed before employment. Do not rely on aircraft visuals alone — use STATUS calls to confirm orientation before taking a shot.

=== Talk-On ===
If the supporting fighter loses visual on the engaged fighter (BLIND) after the merge, the engaged fighter or flight lead can provide a talk-on to re-establish visual.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter or FL || {CS} {Clock Position} {Range} {Altitude Qualifier}
|}

VIPER 1, THREE O'CLOCK ONE AND A HALF MILES LOW.

Once visual is re-established:

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || {CS} VISUAL
|}

=== Employment ===
Once IFF is confirmed and a valid shot opportunity exists, the supporting fighter employs. The call includes weapon type and target description.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting or Engaged Fighter || {Controller-CS} {CS} FOX TWO {Target Description}
|-
| Controller || COPY SHOT
|}

Gun employment:

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting or Engaged Fighter || {Controller-CS} {CS} GUNS {Target Description}
|}

The flight lead retains authority to call NEGATIVE if employment is unsafe or premature, regardless of who holds radio priority.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || NEGATIVE {CS} {Reason if required}
|}

=== SPLASH ===
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged or Supporting Fighter || {Controller-CS} {CS} SPLASH {Target Description}
|-
| Controller || {CS} COPY SPLASH
|}

=== Bug Out ===
Following SPLASH, or when the flight lead determines the engagement should end, the supporting fighter directs the egress. The supporting fighter holds the best big-picture SA at this point and is best placed to select a safe egress direction.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || {CS} BUG OUT {Direction}
|-
| colspan="2" style="text-align:center;" | ''All flight members flow in the stated direction''
|}

VIPER'S BUG OUT 0-9-0.

If the flight lead was the supporting fighter and the wingman is now visual after the bug out, conventional flight roles are re-established:

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Wingman || {CS} VISUAL PRESS
|-
| Flight Lead || ENGAGED
|}

Following the bug out the flight calls RESET on the TAC C2 NET and returns to the prebriefed position unless directed otherwise.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || {Controller-CS} {CS} RESET
|}

General/Tactical Communication Revision 1

2026-06-11T15:35:43Z

Niknam3: /* RV Alpha Procedure */

General/Tactical Communication Revision 1

2026-06-11T15:35:16Z

Niknam3: /* RV Alpha Procedure */

General/Tactical Communication Revision 1

2026-06-11T15:17:48Z

Niknam3: /* Check in WITH EXCEPTIONS */

General/Tactical Communication Revision 1

2026-06-11T15:17:00Z

Niknam3: /* Check in AS FRAGGED */

General/Tactical Communication Revision 1

2026-06-11T15:16:13Z

Niknam3: /* ALPHA CHECK */

General/Tactical Communication Revision 1

2026-06-11T15:13:44Z

Niknam3: /* Check in AS FRAGGED */

General/Tactical Communication Revision 1

2026-06-11T15:11:06Z

Niknam3: /* Check in AS FRAGGED */

General/Tactical Communication Revision 1

2026-06-11T15:10:11Z

Niknam3: /* Check in AS FRAGGED */

General/Tactical Communication Revision 1

2026-06-11T15:08:30Z

Niknam3: /* Check In ON TACC2 NET (MNPOPCA Format) */

General/Tactical Communication Revision 1

2026-06-11T15:07:52Z

Niknam3: /* Check In ON TACC2 NET (MNPOPCA Format) */

Airspace Classifications

2026-06-03T15:26:57Z

Niknam3: /* Class D */

__NOTOC__

<div style="font-size:1.1em; color:#660000; font-weight:bold;">SOURCE — Airspace Classifications</div>

<div style="font-size:0.85em; font-weight:bold;">Covers: Airspace Types · Restricted Areas · Brevity & Terminology</div>

<div style="font-size:0.8em; color:#555;">''Information is based on real-world procedures but modified to cater to DCS limitations''</div>

----

__TOC__

----

= Airspace Classifications =

Airspace is divided into defined categories and classes, each with its own rules governing who may fly within it, what equipment is required, what level of ATC interaction is expected, and under what conditions — VFR or IFR — flight is permitted. Understanding these classifications is fundamental to flight planning, whether in the real world or in DCS. This page covers the standard ICAO-based airspace classes used in most of the world, as well as the special use and restricted airspace designations that pilots are likely to encounter.
== Controlled vs Uncontrolled Airspace ==

At the broadest level, airspace is divided into two categories: '''controlled''' and '''uncontrolled'''. Controlled airspace is airspace within which ATC service is provided to IFR flights and, depending on the class, to VFR flights as well. Uncontrolled airspace is airspace where no ATC separation service is provided — pilots are responsible for their own separation from terrain and other traffic. This does not mean uncontrolled airspace is ungoverned; VFR weather minimums and other rules still apply. The key distinction is simply whether ATC is actively involved in managing traffic within that volume of airspace.

Beyond controlled and uncontrolled, there is a third broad category: '''special use airspace (SUA)''', which encompasses areas where normal flight operations are limited, restricted, or prohibited for reasons of military activity, security, or hazard. SUA is covered in detail in the second half of this page.

== ICAO Airspace Classes ==
[[File:Airspace-Classification-by-FAA-3752383478.png|left|thumb|800x800px|Airspace Classes]]
The International Civil Aviation Organisation (ICAO) defines seven classes of airspace, designated A through G. Classes A through E are controlled; classes F and G are uncontrolled (with F rarely used in practice). Each class specifies different requirements for pilot certification, equipment, communications, and the services provided by ATC.

=== Class A ===

Class A is the most restrictive class of controlled airspace. In the United States, it begins at 18,000 feet MSL and extends to FL600. '''All flights in Class A must be conducted under IFR''' — VFR flight is not permitted. An IFR flight plan must be filed and an ATC clearance received before entering. ATC provides separation to all aircraft.

=== Class B ===

Class B airspace surrounds the busiest airports — those with the highest volume of IFR operations and passenger traffic. It typically extends from the surface up to 10,000 feet MSL and has a layered, tiered structure, sometimes described as an upside-down wedding cake. '''An ATC clearance is required for all aircraft, both IFR and VFR, to enter Class B airspace''', and ATC provides separation to all traffic within it. Required equipment includes a two-way radio and a transponder with Mode C altitude reporting.

=== Class C ===

Class C airspace surrounds airports that have a control tower and radar approach control, with a significant but lower level of traffic than Class B airports. Pilots must establish '''radio contact with ATC prior to entering''' Class C airspace. IFR and VFR aircraft are sequenced and separated from each other within the Class C area by ATC. A transponder with Mode C is required.

=== Class D ===

Class D airspace surrounds airports with an operational control tower but no radar approach control. Pilots must establish '''radio communications with the control tower''' and acquire an '''clearance''' before entering Class D airspace. No separation services are provided to VFR aircraft, though controllers will issue traffic advisories. Class D becomes Class E or Class G when the tower is not in operation.

=== Class E ===

Class E does not require communication with ATC for VFR flight. IFR flights in Class E receive full ATC separation services; VFR flights receive no separation but still must maintain VFR weather minimums. A transponder with Mode C is required above 10,000 feet MSL.

=== Class F ===

Class F is an ICAO designation for airspace where advisory services are available but ATC separation is not guaranteed. It is rarely used in practice and is not employed in the United States. Some other ICAO member states use it in limited circumstances.

=== Class G ===

Class G is uncontrolled airspace — airspace not designated as any other class. It typically exists from the surface up to the base of overlying Class E airspace. No ATC services are provided to any aircraft in Class G. Pilots are responsible for maintaining their own separation and must comply with VFR weather minimums, which are less stringent in Class G than in controlled airspace — particularly for low-altitude daytime flight.

== VFR Weather Minimums by Class (SUBJ TO CHANGE) ==

The table below summarises the basic VFR weather minimums applicable in each airspace class:

{| class="wikitable"
|-
! Airspace Class !! Visibility !! Cloud Clearance
|-
| A || Not applicable (IFR only) || Not applicable
|-
| B || 3 SM || Clear of clouds
|-
| C || 3 SM || 500 ft below / 1,000 ft above / 2,000 ft horizontal
|-
| D || 3 SM || 500 ft below / 1,000 ft above / 2,000 ft horizontal
|-
| E (below 10,000 ft MSL) || 3 SM || 500 ft below / 1,000 ft above / 2,000 ft horizontal
|-
| E (at or above 10,000 ft MSL) || 5 SM || 1,000 ft below / 1,000 ft above / 1 SM horizontal
|-
| G (≤1,200 ft AGL, day) || 1 SM || Clear of clouds
|-
| G (≤1,200 ft AGL, night) || 3 SM || 500 ft below / 1,000 ft above / 2,000 ft horizontal
|-
| G (>1,200 ft AGL, below 10,000 ft, day) || 1 SM || 500 ft below / 1,000 ft above / 2,000 ft horizontal
|-
| G (>1,200 ft AGL, at or above 10,000 ft) || 5 SM || 1,000 ft below / 1,000 ft above / 1 SM horizontal
|}

== Special Use Airspace (SUA) ==

Beyond the standard airspace classes, certain volumes of airspace are designated for specific or restricted purposes. These fall into two broad groups: '''regulatory''' SUA (prohibited and restricted areas, established through the formal rulemaking process and codified in law) and '''nonregulatory''' SUA (such as MOAs, warning areas, and alert areas, which impose operational guidance without a full legal prohibition). Where overlapping airspace designations apply, the more restrictive designation governs.

In DCS, special use airspace is especially relevant in mission planning — flying into an active restricted or prohibited area without awareness can have serious tactical and narrative consequences.

=== Prohibited Areas ===

Prohibited areas are volumes of airspace within which '''flight is entirely forbidden''', established for reasons of national security or public welfare. No clearance can be obtained to enter a prohibited area — it is a hard exclusion. In the United States, prohibited areas are designated with the prefix "P" (e.g., P-56, which protects airspace over Washington D.C.). In combat environments and in DCS mission scenarios, prohibited areas may correspond to politically sensitive zones, nuclear installations, or high-value ground targets where even overflying is off-limits.

=== Restricted Areas ===

Restricted areas are volumes of airspace where flight is '''permitted only under specific conditions or with prior authorisation''' from the controlling agency. They are typically established over areas where hazardous activities occur — artillery firing ranges, missile launch corridors, or live ordnance training. Unlike prohibited areas, entry into a restricted area may be allowed when the area is inactive (i.e., the hazardous activity is not taking place) or when a specific clearance has been obtained. In the US, restricted areas carry the prefix "R". Pilots approaching a restricted area should contact the controlling authority or ATC to confirm current activity status.

=== Military Operations Areas (MOA) ===

A Military Operations Area is a block of airspace established to '''separate certain military training activities from IFR traffic''' and to identify for VFR traffic where those activities take place. MOAs are nonregulatory — they do not legally prohibit civilian entry — but they are a significant hazard indicator. Activities conducted within active MOAs include air combat manoeuvres, intercepts, aerobatics, formation training, and low-altitude tactics. Military aircraft in an active MOA may operate at high speeds and in ways that are unpredictable to civilian traffic.

When a MOA is active, IFR traffic will be rerouted or held clear by ATC unless separation can be positively assured. VFR pilots may legally enter an active MOA without a clearance, but this is strongly inadvisable without first confirming activity status with ATC or Flight Service. On sectional charts, MOAs are shown with magenta hashed boundaries and are labelled with their name, vertical limits, and controlling agency frequency.

=== Warning Areas ===

Warning areas are similar in character to MOAs but are located in '''international airspace''' (beyond 12 NM from the US coastline), where the FAA does not have the same authority to issue binding restrictions. A warning area notifies pilots of potentially hazardous activity in that airspace — including military exercises and weapons testing — but cannot legally prohibit civilian entry. Pilots should treat active warning areas with the same caution as MOAs and contact ATC for current activity information before entering.

=== Temporary Reserved Area (TRA) ===

A Temporary Reserved Area is a defined volume of airspace that is '''temporarily reserved for the exclusive or priority use of a specific aviation authority or user''', normally for a limited and published period of time. Unlike a permanently restricted area, a TRA is a flexible structure activated through pre-tactical coordination — typically the day before operations — and published in NOTAMs. It is primarily a European/ICAO concept used under the Flexible Use of Airspace (FUA) framework.

Crucially, a TRA is not necessarily impenetrable: depending on the specific designation, other traffic may be permitted to transit the area if coordinated with the airspace user or the relevant ATC authority. This distinguishes it from a Temporary Segregated Area (TSA), in which transit by non-participating aircraft is not permitted at all. In practice, TRAs are most commonly associated with military training exercises that occur on a recurring but non-permanent basis.

=== Temporary Segregated Area (TSA) ===

A Temporary Segregated Area is the more restrictive counterpart to the TRA. When a TSA is active, '''no non-participating aircraft may transit the area under any circumstances''' — it is wholly allocated to the designated user for the duration of activation. TSAs are considered the flexible equivalent of permanent Danger Areas and are activated through the same pre-tactical Airspace Management Cell (AMC) process as TRAs. Once a TSA is activated and published, the only aircraft authorised to operate within it are those of the user who requested the allocation.

=== Danger Areas ===

A Danger Area is a volume of airspace where activities '''hazardous to the flight of aircraft may occur''' at specified times. Unlike prohibited or restricted areas, danger areas do not legally prohibit entry — they exist to warn pilots that operations such as artillery firing, rocket launches, anti-hail operations, or other hazardous activities may be taking place. Some danger areas require notification or a permit before entry; others simply require the pilot to be aware of the nature and timing of the hazard. Danger Areas are published in the AIP and charted on aeronautical maps.

=== No-Fly Zone (NFZ) ===

A No-Fly Zone is a broad, sometimes informal term for any area in which flight is prohibited or heavily restricted, often by direct order of a military or governmental authority rather than through standard civil aviation regulatory channels. NFZs are most commonly associated with '''conflict zones and geopolitical situations''' — for example, NFZs were established over Bosnia in the 1990s and Libya in 2011 under UN Security Council resolutions. In a military aviation context, an NFZ is typically enforced kinetically: aircraft violating the zone may be intercepted and, depending on the terms of the NFZ, engaged.

In the context of civil aviation and DCS, the term NFZ is also used more loosely to refer to any airspace where flight is entirely prohibited — overlapping with what formal regulations would call a prohibited area. Players and mission designers should treat any designated NFZ as a hard exclusion zone from which violations will draw a response.

=== Temporary Flight Restriction (TFR) ===

A Temporary Flight Restriction is a short-duration restriction on flight within a specified volume of airspace, issued by NOTAM. TFRs can be established for a wide range of reasons: natural disasters, emergency response operations, hazardous material incidents, large-scale public events, presidential movements, or active firefighting operations. Unlike the other SUA types described above, TFRs are not charted in advance — they appear in the NOTAM system and must be checked before each flight. In DCS, TFRs are less commonly modelled explicitly but mission briefings may reference equivalent real-world concepts.

=== Alert Areas ===

Alert areas are charted on aeronautical maps to '''notify pilots of a high volume of unusual or intensive aerial activity''' that may present a collision risk, even though that activity is conducted entirely in accordance with regulations. Common examples include areas with heavy flight training, aerobatic activity, or large numbers of student pilots. Alert areas impose no entry restriction — pilots of both participating and non-participating aircraft are equally responsible for collision avoidance within them.

== See Also ==

* [[General/Air Traffic Communication|Air Traffic Communication]]
* [[Navigation Fundamentals]]

==Notes==
<references />

MTTP/A2A

2026-05-31T17:18:39Z

Niknam3: /* FULL COMMUNICATIONS EXAMPLE */

== 01 / Overview ==
Air combat is primarily carried out by CAP aircraft. The two main mission types are '''DCA''' (Defensive Counter Air) and '''OCA''' (Offensive Counter Air).

=== Groups and Contacts ===
A '''GROUP''' is any number of air contacts within 3 nm in azimuth and range of each other. A '''CONTACT''' is an individual radar return within a GROUP. Single contact is the assumed strength for all GROUPs unless otherwise specified. A GROUP with three or more contacts is called '''HEAVY'''.

The '''PICTURE''' establishes a common tactical air image and describes the spatial relationship of GROUPs. It is always communicated in BULLSEYE format unless briefed otherwise. Only the Three GROUPs with highest Priority are Conveyed

=== Contact Declaration ===
Before a fighter can engage, a contact must be declared. Declaration is performed by the controller in response to a DECLARE request.

{| class="wikitable" style="width:100%;"
|-
! Declaration !! Meaning !! Engagement Authority
|-
| '''BOGEY''' || Identity unknown || Not cleared to engage
|-
| '''OUTLAW''' || Originates from known or suspected hostile area || Not cleared to engage; escalation criteria apply
|-
| '''SPADES''' || No valid IFF response on interrogation || Not cleared to engage; escalation criteria apply
|-
| '''BANDIT''' || Positively identified as enemy IAW theater ID criteria || Not cleared to engage; does not imply authority to fire
|-
| '''HOSTILE''' || Confirmed enemy; clearance to fire authorized IAW ROE || Cleared to engage
|-
| '''NEUTRAL''' || Positively identified as neutral || Not cleared to engage
|-
| '''FRIENDLY''' || Positively identified as friendly || Not cleared to engage
|-
| '''FURBALL''' || Friendly and non-friendly aircraft within 5 nm || Employment not authorized until resolved
|}

A BOGEY, BANDIT, OUTLAW, or SPADES classification does not authorize engagement. HOSTILE is the only declaration that authorizes weapons employment IAW ROE.

== 02 / Important Concepts ==

=== Communication Cadence by Phase ===
Communication priority shifts between the controller and fighters depending on the phase of the intercept.

{| class="wikitable" style="width:100%;"
|-
! Phase !! Priority Communicators
|-
| Pre-COMMIT / Marshal || 1. Controller · 2. Fighters
|-
| Post-COMMIT / Push || 1. Controller · 2. Fighter
|-
| Targeting / Weapons Employment || 1. Fighters · 2. Controller
|-
| Merge || 1. Engaged Fighter · 2. Supporting Fighters · 3. Controller
|-
| Post-Merge || 1. Fighter Clearing Merge · 2. Supporting Fighters · 3. Controller
|}

=== TAC Range ===
Called at 60 nm (default) by the first asset to recognize the separation. Signals all players to prepare for targeting. Pre-commit SA building continues until this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Fighter || {CS} {Group Label} TAC RANGE
|}

=== Airspace Sanitization ===
A Section consists of two aircraft, each equipped with its own radar. Regardless of the number of bars or maximum azimuth a single radar supports, no single system can cover the entire sky. To compensate, both radars are stacked and assigned to different portions of the airspace — each portion is called an '''Area of Responsibility (AOR)'''. This technique, known as '''Radar Mating''', vastly increases the total volume scanned and ensures that no unknown contacts are operating in the area beyond already-tracked groups. The exact parameters depend on the aircraft type: the US Navy recommends RWS, 140°, 6 bars, end scale 80 nm, with radars mated at 25 nm: placing the flight lead between 40,000 and 15,000 ft, and the wingman from ground level to 25,000 ft.

The process of actively scanning assigned AORs to confirm no unknown contacts are present is called '''Sanitisation'''.

Because both Radar Mating parameters and Sanitisation responsibilities directly affect how an engagement develops, all of this must be '''pre-briefed''' and set as a '''contract''' before the mission. Time pressure may not always permit a thorough sanitisation pass, and how to handle that contingency should likewise be agreed upon in the brief.

=== Targeting ===
The flight assigns GROUP responsibility and confirms classification.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} DECLARE {Group Label or Bullseye Position}
|-
| Controller || {Group Label} DECLARED {HOSTILE / BOGEY / FRIENDLY / UNABLE / FURBALL}
|-
| FL || {CS} TARGET {Group Label} {Tactic}
|-
| colspan="2" style="text-align:center;" | ''Once group appears on radar''
|-
| FL || {CS} TARGETED {Group Label} BULLSEYE {Bearing/Range}
|-
| Controller || ''No response if information correlates. Comparative response if correction is required.''
|}

== 03 / Common Calls ==

=== DECLARE ===
Inquiry as to the identity of a specified GROUP. Full positional data in BULLSEYE format must accompany all responses.
MIKE, EAGLE 11, DECLARE NORTH GROUP.
EAGLE 11, NORTH GROUP BULLSEYE 2-7-3/27, TWENTY-TWO THOUSAND, TRACK EAST, BOGEY SPADES.

=== BOGEY DOPE ===
Request for BRAA information on the indicated GROUP or the closest GROUP if not specified. Does not imply fighter targeting.
MIKE, EAGLE 11, BOGEY DOPE NORTH GROUP.
EAGLE 11, NORTH GROUP BRAA 2-1-0/28, THIRTY-EIGHT THOUSAND, HOT, HOSTILE.

=== NAILS ===
Fighter's radar warning receiver is detecting an airborne interceptor radar in search mode. Called with bearing or cardinal direction.
EAGLE 1, NAILS 2-7-0.

=== SPIKED ===
Fighter is being actively tracked by an airborne radar. Called with bearing or cardinal direction. Controller correlates to a GROUP within ±30 degrees and responds with range, altitude, aspect, declaration, and GROUP name.
EAGLE 1, SPIKED 2-7-0.
EAGLE 1, SPIKE RANGE 17, THIRTY THOUSAND, HOSTILE EAST GROUP, TWO CONTACTS.

=== THREAT Call ===
If a fighter will pierce THREAT range to an untargeted GROUP, the controller makes a THREAT call in BRAA format no later than THREAT range.
HEAT 31, ADDITIONAL GROUP THREAT, BRAA 1-2-5/35, THIRTY-FIVE THOUSAND, HOT, HOSTILE.

If the THREAT is within 5 nm of friendly fighters:
BOLT 1, THREAT NORTH THREE, TEN THOUSAND, TRACK SOUTH, HOSTILE.

=== FADED and VANISHED ===
'''FADED''' — a previously tracked GROUP not updated by sensors for 30 seconds. The controller reports the GROUP as FADED with last known BULLSEYE position. Fighters maintain MONITOR responsibility if they can maintain correlation. FADED is not used for friendly aircraft — controllers use NEGATIVE CONTACT for friendlies not held on sensors.

'''VANISHED''' — a special case of FADED used when the GROUP is not in a known blind zone and is correlated to a friendly shot that meets parameters for successful termination.

=== Unexpected Contacts ===
Three distinct call types exist for contacts not part of the established picture:

{| class="wikitable" style="width:100%;"
|-
! Call !! Criteria !! Format
|-
| '''ADDITIONAL GROUP''' || Newly detected outside targeting range, or does not fit traditional label || BULLSEYE
|-
| '''POP-UP GROUP''' || Previously undetected; appears inside targeting range but outside THREAT range || BULLSEYE
|-
| '''THREAT GROUP''' || Undetected or unreported GROUP meeting briefed THREAT criteria || BRAA to the closest aircraft
|}

DARKSTAR, POP-UP GROUP BULLSEYE 2-7-0/15, FIVE THOUSAND, TRACK WEST, BOGEY SPADES.
RAMBO 2, THREAT GROUP BRAA 2-7-0/13, ONE THOUSAND, HOT, HOSTILE.

== 04 / Engagement ==
The engagement loop is the core sequence executed by all fighter flights once committed and targeting is established. It repeats until the GROUP is splashed, leaves the area, or the flight resets.

=== MELD ===
The flight lead directs all flight members to shift their radars from wide sanitization to focused SA on the assigned GROUP. This transition narrows the radar from maximum azimuth and altitude coverage to a tighter volume centered on the target. Sanitization of the surrounding airspace ceases until DROPPING is called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''All flight members shift radar from sanitization to the assigned GROUP''
|}

=== SORT ===
The flight lead assigns individual contacts within the GROUP to specific flight members. Each member acknowledges with SORTED when they have confirmed their assigned contact on radar and are prepared to engage it. If a member cannot confirm their assigned contact, SORTED is withheld until resolution.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || ''(intraflight) FLIGHT SORT {Criteria}''
|-
| #2 || ''(intraflight) #2 SORTED''
|-
| #3 || ''(intraflight) #3 SORTED''
|-
| #4 || ''(intraflight) #4 SORTED''
|}

=== JUDY ===
Called by the flight lead when the flight no longer requires controller guidance to prosecute the intercept. From this point, the controller minimizes transmissions and provides situational awareness information only. JUDY is not always called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Provides SA and THREAT calls only.''
|}

=== ENGAGE ===
Directive call from the flight lead to a specific wingman to employ weapons. The flight lead may also direct simultaneous employment by multiple members.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} ENGAGE
|-
| Wingman || {CS}
|}

=== Weapon Employment ===
The firing aircraft calls the shot on TACC2 NET immediately after employment. The call includes shot type, GROUP label, contact description, BULLSEYE position, and altitude. The controller acknowledges with COPY SHOT.

If a fighter determines a GROUP HOSTILE and ROE has been met, the fighter may employ autonomously and include HOSTILE in the shot transmission.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft || {TACC2-CS} {CS} FOX THREE {Group Label} {Contact Description} BULLSEYE {Bearing/Range} {Altitude}
|-
| TACC2 || {TACC2-CS} COPY SHOT
|-
| colspan="2" style="text-align:center;" | ''Autonomous HOSTILE employment''
|-
| Firing Aircraft || {Controller-CS} {CS} FOX THREE {Group Label} BULLSEYE {Bearing/Range} {Altitude} HOSTILE
|-
| TACC2 || {TACC2-CS} COPY SHOT
|}

Multiple shots in one transmission are acceptable:
SHADOW12 FOX THREE NORTH GROUP LEAD CONTACT BULLSEYE 2-7-0/20 TWENTY THOUSAND; SHADOW11 FOX THREE NORTH GROUP TRAIL CONTACT.

=== OUT / DEFENDING ===
Following weapon employment the flight turns away from the threat. OUT is a planned maneuver executed at a prebriefed range. DEFENDING indicates a reactive maneuver against an incoming weapon and is called with the cardinal direction of the defensive turn.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction}
|-
| colspan="2" style="text-align:center;" | ''or, if reacting to an incoming weapon''
|-
| Aircraft || {CS} DEFENDING {Direction}
|}

=== DROPPING ===
May be called in conjunction with OUT. Signals the controller that the flight has ceased monitoring the GROUP and is returning to sanitization radar settings. Monitoring responsibility transfers back to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction} DROPPING {Group Label}
|-
| colspan="2" style="text-align:center;" | ''Controller resumes monitoring of the dropped GROUP''
|-
| Controller || ''Resumes monitoring.''
|}

=== Assessment ===
The flight assesses weapon effects from sensor data or controller reports. Three outcomes are possible:

{| class="wikitable" style="width:100%;"
|-
! Outcome !! Action
|-
| GROUP splashed || Call SPLASH
|-
| GROUP remains a factor, follow-up shot required || Turn IN, return to MELD
|-
| GROUP has left the area or is no longer a factor || Proceed with Tasking
|}

=== IN (Follow-up Engagement) ===
If the GROUP remains a factor and the tactic permits a follow-up shot, the flight turns back toward the GROUP. The IN call triggers a new cycle beginning at MELD.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IN {Direction}
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''Re-sort as required, then return to ENGAGE''
|}

=== SPLASH ===
Called when weapon effects confirm the GROUP or contact is destroyed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft or Controller || {CS} SPLASH {Group Label or Contact Description}
|}

----

== 05 / Defensive Counter Air (DCA) ==
DCA is the use of fighter aircraft to defend a ground asset or airspace against hostile air threats. It uses prebriefed lanes and defined ranges.

=== DCA Range Structure ===
All ranges are prebriefed per sortie. The following are the standard range lines used in DCA:

{| class="wikitable" style="width:100%;"
|-
! Range Line !! Definition
|-
| '''Mission Fail Line''' || The line the enemy must not cross for the mission to succeed. Defines the maximum depth of the defensive problem.
|-
| '''Commit Line (CL)''' || The line at which a bogey is declared HOSTILE IAW theater ROE and the flight is authorized to commit. Prebriefed for all DCA sorties.
|-
| '''Targeting Range''' || The prebriefed distance at which all contacts must be intercepted. A GROUP inside this range with no assigned fighter is UNTARGETED. Prebriefed per sortie.
|-
| '''TAC Range''' || Default 60 nm from the closest fighter to the closest GROUP. Signals all players to prepare for targeting.
|-
| '''Threat Range''' || The prebriefed range at which an untargeted GROUP meeting THREAT criteria triggers a THREAT call. Prebriefed per sortie.
|}

=== COMMIT Authority ===
COMMIT authority is derived from the combatant commander and delegated through the chain of command. Any of the following may hold or recommend COMMIT authority depending on what is delegated:

{| class="wikitable" style="width:100%;"
|-
! Role !! Abbreviation !! Authority
|-
| Flight Lead || FL || Usually holds COMMIT authority unless delegated
|-
| Team Lead || TL || May hold COMMIT authority if delegated
|-
| Mission Commander || MC || May hold COMMIT authority if delegated
|-
| TACC2 || — || May hold COMMIT authority if delegated
|}

If only the MC, TL, or FL holds COMMIT authority, the controller may only recommend COMMIT. If the controller holds COMMIT authority, the MC and TL may only recommend.

=== DCA Flow ===

==== Lane Handover ====
When an outgoing flight is relieved on station by an incoming flight, a positive lane handover is required before the outgoing flight departs.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Off-going Lane Commander || {CS} MOVE FORWARD
|-
| On-coming Lane Commander || {CS}
|-
| colspan="2" style="text-align:center;" | ''On-coming aircraft may enter the lane. Lane commander authority has not yet transferred.''
|-
| Off-going Lane Commander || {CS} YOU HAVE THE LANE
|-
| On-coming Lane Commander || {CS} HAS THE LANE
|}

The off-going flight passes critical mission information to the controller before departing. The controller passes big-picture information to the on-coming flight before pushing them to the tactical frequency.

==== Pre-Commit ====
The flight arrives at its prebriefed CAP position with FENCE IN complete and radars in sanitization configuration. The controller holds picture responsibility.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} PICTURE
|-
| Controller || {CS} {Nr of Groups} {Group Label} BULLSEYE {Bearing/Range} {Altitude} TRACK {Direction} {Declaration} {Nr of Contacts}
|}

The flight evaluates commit criteria continuously. Pictures are requested as needed to maintain SA.

==== Commit ====

===== FIGHTER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} Recommend {CS} COMMIT
|-
| FL || {CS} COMMIT
|}

===== CONTROLLER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} Recommend Commit
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} {CS} COMMIT
|-
|FL
|{CS}
|}

After COMMIT, fighters hold radio priority.

=== Engagement Loop ===
The flight executes the standard engagement loop as defined above The loop repeats until the GROUP is splashed, leaves the lane, or:

Once the Engagement is Complete the flight '''RESETS''' back to the briefed Position

==== RESET ====
Directs the flight to return to its prebriefed position or area of operations. RESET implies DROPPING and returns all targeting responsibility to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} RESET
|-
| colspan="2" style="text-align:center;" | ''Flight returns to prebriefed CAP position. Controller resumes full picture responsibility''
|}

----

== 06 / Offensive Counter Air (OCA) ==
OCA is the use of fighter aircraft to suppress, destroy, or neutralize enemy air assets before they can threaten friendly forces. Unlike DCA, OCA is not lane-based and does not require a commit line. The flight pushes into the threat environment rather than waiting for the threat to approach.

=== OCA Range Structure ===
The same range lines apply as in DCA — Threat Range, Targeting Range, and TAC Range — but all are prebriefed based on the specific mission geometry and threat environment. There is no commit line or mission fail line in OCA.

=== OCA Flow ===
OCA does not have a lane handover or a commit phase. The flight checks in, receives the picture, establishes targeting, and executes the engagement loop.

==== FULL COMMUNICATIONS EXAMPLE ====
In this Scenario, SHADOW11 four-ship F16C on OCA. TACC2 Agency CS THUMPER executing Positive Control. The Example begins after the Handover. Check In was done on the previous Frequency. TAC RANGE 60, THREAT RANGE 30
THUMPER SHADOW11 PICTURE

THUMPER PICTURE TEN GROUPS GROUP BULLSEYE 0-2-0/25, TWENTY-SEVEN THOUSAND, THOUSAND, TRACK EAST, HOSTILE, HEAVY, THREE CONTACTS. GROUP BULLSEYE 2-7-0/25, FIFTEEN THOUSAND, TRACK WEST, HOSTILE. GROUP BULLSEYE 2-9-0/35, TEN THOUSAND, TRACK WEST, HOSTILE.

SHADOW11 TARGETED GROUP BULLSEYE 0-2-0/25

SHADOW11 GROUP BULLSEYE 0-2-0/25 TAC RANGE

SHADOW11 SKATE, MELD

SHADOW11 SORTED

SHADOW11 FOX3 BULLSEYE 0-2-0/25

THUMPER COPY SHOT

SHADOW11 OUT SOUTH DROPPING

THUMPER

THUMPER SHADOW11 BOGEYDOPE

SHADOW11 EAST GROUP BRAA 2-1-0/28, FIFTEEN-THOUSAND, COLD, HOSTILE

SHADOW11 IN, MELD

SHADOW11 SORTED

THUMPER SHADOW11 SPLASH EAST GROUP

THUMPER
In the Following Example additional Adversarys Pop Up within Threat Range of SHADOW11
SHADOW11 THUMPER THREAT GROUP, BRAA 1-2-5/28, FIVE-THOUSAND, HOT, HOSTILE, 2 CONTACTS

SHADOW11 TARGETED SORTED LEAD, FOX 3 LEADER, FOX3 TRAILER, BULLSEYE 0-5-0/45, FIVE-THOUSAND

THUMPER COPY SHOTS

SHADOW11 DEFENDING SOUTH, DROPPING

THUMPER

SHADOW11 THUMPER THREAT GROUP, BRAA 0-6-0/15, TWO-THOUSAND, COLD, HOSTILE

SHADOW11

SHADOW11 IN

SHADOW11 FOX3 BULLSEYE 0-6-0/15, TWO-THOUSAND

THUMPER COPY SHOT

SHADOW11 THUMPER THREAT GROUP VANISHED
----

== 07 / QRA ==

== 08 / Intercept (VID) ==
A Visual Identification (VID) intercept is conducted when a contact cannot be declared HOSTILE or FRIENDLY by electronic means alone, and visual confirmation of aircraft type, markings, or behavior is required before engagement authority can be granted or withheld.

VID intercepts follow a structured sequence: the controller guides the fighter to a position from which a visual identification pass can be made, then the fighter reports the result and awaits further direction.

=== Intercept Flow ===

==== Commit ====
The controller or flight lead initiates the intercept against the unidentified contact.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} COMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration} {Nr of Contacts}
|-
| FL || {CS} COMMIT
|}

==== Guidance ====
The controller provides vectors to position the fighter for a VID pass. This is the only phase where the controller takes positive close control of the intercept geometry. BRAA format is used throughout.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} BRAA {Bearing/Range} {Altitude} {Aspect} {Declaration}
|-
| FL || {CS}
|-
| colspan="2" style="text-align:center;" | ''Controller continues to provide updated vectors until fighter calls JUDY''
|}

==== JUDY ====
The fighter calls JUDY when radar contact is established and no further controller guidance is required. The controller minimizes transmissions from this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Continues to provide SA information only.''
|}

==== Tally ====
The fighter calls TALLY when visual contact is established with the target.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} TALLY {Position}
|}

==== Identification ====
The fighter conducts the VID pass and reports the result to the controller. The report includes aircraft type, markings, and behavior observed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IDENTIFIED {Aircraft Type} {Markings / Behavior}
|-
| Controller || {CS} {Further Instructions / Declaration Update}
|}

If the contact is identified as HOSTILE following the VID pass, the controller issues the updated declaration and the flight may proceed to engagement IAW ROE. If the contact is FRIENDLY or NEUTRAL, the flight disengages and returns to its prebriefed position.

----

== 09 / Merge ==
A merge occurs when friendly and target aircraft arrive in the visual arena, within 3–5 nm of each other. At the merge, radar resolution becomes limiting and the engagement transitions from BVR to Within Visual Range (WVR). The engagement is now managed through ACM contracts and direct communication between flight members.

=== Authority and Radio Priority ===
Two distinct concepts govern merge communications: '''authority''' and '''radio priority'''.

'''Authority''' remains with the Flight Lead throughout the engagement. The FL can override, redirect, or terminate the engagement at any time regardless of who is engaged.

'''Radio priority''' belongs to the engaged fighter. Other flight members subordinate their transmissions to avoid stepping on critical engaged fighter calls. The controller minimizes transmissions entirely and provides only THREAT calls, SA updates, and responses to direct requests.

{| class="wikitable" style="width:100%;"
|-
! Role !! Authority !! Radio Priority
|-
| '''Flight Lead''' || Full authority over the engagement at all times || Secondary — subordinates to engaged fighter
|-
| '''Engaged Fighter''' || Manages own engagement IAW FL direction || Primary — holds radio priority
|-
| '''Supporting Fighter''' || Executes IAW engaged fighter and FL direction || Tertiary — transmits only when necessary
|-
| '''Controller''' || Provides SA only || Minimal — THREAT calls and direct requests only
|}

=== MERGED ===
The controller calls MERGED when radar tracks come together within 3–5 nm, or the engaged fighter calls it when visual contact is made at the merge.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Engaged Fighter || {CS} MERGED {Group Label}
|}

=== Role Assignment ===
At or before the merge, engaged and supporting roles must be clearly established. By default the flight lead is engaged. Roles can be assigned or transferred in two ways:

==== Wingman-Initiated Transfer ====
The wingman identifies he is the engaged fighter based on the bandit's plane of motion and lift vector orientation, and calls it.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Wingman || #2 ENGAGED
|-
| Flight Lead || PRESS
|}

==== Flight Lead-Initiated Transfer ====
The flight lead recognizes the wingman is the engaged fighter and assigns the role.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || #2 PRESS
|-
| Wingman || #2 ENGAGED
|}

==== Bandit Switches ====
If the bandit maneuvers to engage the other fighter, the currently engaged fighter communicates the change.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || BANDIT SWITCHED
|-
| colspan="2" style="text-align:center;" | ''Roles are reassessed and reassigned as required''
|}

=== Engaged Fighter SA Calls ===
The engaged fighter is responsible for narrating the fight to maintain the supporting fighter's situational awareness. This enables the supporting fighter to position correctly and employ at the right moment. SA calls include the fight geometry, altitude, and direction.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || {CS} ENGAGED {ONE / TWO CIRCLE} {Direction} {Altitude}
|}

VIPER 1, ENGAGED ONE CIRCLE CLIMBING THROUGH FIFTEEN THOUSAND.
VIPER 1, ENGAGED TWO CIRCLE NORTHBOUND BANDITS LOW TWO'S HIGH.

These calls are made continuously as the fight develops, not just once at the merge. The supporting fighter cannot position or employ safely without them.

=== STATUS Calls ===
STATUS is a request from the supporting fighter for a specific situational update from the engaged fighter. It is the primary tool for IFF at the merge. A generic STATUS call returns a general update. A specific STATUS call asks a targeted question and returns a more useful answer.

The supporting fighter should tailor the STATUS call to the specific information needed to resolve the IFF situation. Generic STATUS calls are acceptable but specific calls are faster and more effective.

{| class="wikitable" style="width:100%;"
|-
! Call !! Question Being Asked !! Example Response
|-
| '''STATUS''' || General situation update || ENGAGED ONE CIRCLE NORTHBOUND BANDITS LOW TWO'S HIGH
|-
| '''STATUS HIGH/LOW''' || Which aircraft is higher || BANDITS LOW TWO'S HIGH
|-
| '''STATUS NOSE HIGH/NOSE LOW''' || Which aircraft has nose above or below horizon || TWO'S NOSE HIGH BANDIT NOSE LOW
|-
| '''STATUS LEFT/RIGHT''' || Which aircraft is left or right || TWO'S LEFT BANDIT RIGHT
|-
| '''STATUS NORTH/SOUTH/EAST/WEST''' || Cardinal orientation of aircraft in the fight || TWO'S NORTH BANDIT SOUTH
|}

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || {CS} STATUS {Qualifier if applicable}
|-
| Engaged Fighter || {Specific SA answer to the STATUS question}
|}

Supporting Fighter: TWO STATUS HIGH LOW.
Engaged Fighter: BANDITS LOW TWO'S HIGH.

If a STATUS call returns an ambiguous response, rephrase with a more specific qualifier before resorting to a FLASH call.

As a last resort, a FLASH call can be used to add physical confirmation to IFF — for example FLASH FLARES or FLASH BURNER. This directs the wingman to briefly activate the specified system so the supporting fighter can visually confirm identity. Exercise extreme caution — the bandit may also be employing flares, and a mistaken identification cannot be undone.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || FLASH {FLARES / BURNER}
|-
| Wingman || ''(executes flash of specified system briefly)''
|}

=== IFF Brevity ===
Standard brevity calls for visual identification status:

{| class="wikitable" style="width:100%;"
|-
! Term !! Meaning
|-
| '''TALLY''' || Visual contact established on the target or bandit
|-
| '''NO JOY''' || No visual contact with the target or bandit
|-
| '''VISUAL''' || Visual contact established on a friendly aircraft
|-
| '''BLIND''' || No visual contact with a friendly aircraft
|}

IFF must be confirmed before employment. Do not rely on aircraft visuals alone — use STATUS calls to confirm orientation before taking a shot.

=== Talk-On ===
If the supporting fighter loses visual on the engaged fighter (BLIND) after the merge, the engaged fighter or flight lead can provide a talk-on to re-establish visual.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter or FL || {CS} {Clock Position} {Range} {Altitude Qualifier}
|}

VIPER 1, THREE O'CLOCK ONE AND A HALF MILES LOW.

Once visual is re-established:

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || {CS} VISUAL
|}

=== Employment ===
Once IFF is confirmed and a valid shot opportunity exists, the supporting fighter employs. The call includes weapon type and target description.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting or Engaged Fighter || {Controller-CS} {CS} FOX TWO {Target Description}
|-
| Controller || COPY SHOT
|}

Gun employment:

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting or Engaged Fighter || {Controller-CS} {CS} GUNS {Target Description}
|}

The flight lead retains authority to call NEGATIVE if employment is unsafe or premature, regardless of who holds radio priority.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || NEGATIVE {CS} {Reason if required}
|}

=== SPLASH ===
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged or Supporting Fighter || {Controller-CS} {CS} SPLASH {Target Description}
|-
| Controller || {CS} COPY SPLASH
|}

=== Bug Out ===
Following SPLASH, or when the flight lead determines the engagement should end, the supporting fighter directs the egress. The supporting fighter holds the best big-picture SA at this point and is best placed to select a safe egress direction.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || {CS} BUG OUT {Direction}
|-
| colspan="2" style="text-align:center;" | ''All flight members flow in the stated direction''
|}

VIPER'S BUG OUT 0-9-0.

If the flight lead was the supporting fighter and the wingman is now visual after the bug out, conventional flight roles are re-established:

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Wingman || {CS} VISUAL PRESS
|-
| Flight Lead || ENGAGED
|}

Following the bug out the flight calls RESET on the TAC C2 NET and returns to the prebriefed position unless directed otherwise.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || {Controller-CS} {CS} RESET
|}

General/Tactical Communication Revision 1

2026-05-31T17:13:52Z

Niknam3: /* AUTHORITY */

Main Page

2026-05-29T11:53:35Z

Niknam3:

__NOTOC__
__NOEDITSECTION__


<div style="border:1px solid #c8c5bf; padding:48px 32px 36px 32px; margin-bottom:32px; text-align:center;">
<div style="font-size:0.6rem; letter-spacing:5px; color:#9a9690; margin-bottom:20px;">■■■ UNCLASSIFIED — FOR SOURCE MEMBERS ONLY ■■■</div>
<div style="border-top:1px solid #c8c5bf; max-width:200px; margin:0 auto 24px auto;"></div>
[[File:Sourcelogosmall.png|100px|center|link=]]
<div style="font-size:1.6rem; font-weight:600; letter-spacing:8px; margin:20px 0 8px 0;">SOURCE DCS</div>
<div style="font-size:0.72rem; letter-spacing:4px; color:#4a4845; margin-bottom:20px;">SHADOW OPERATIONS - UNDERSTANDING REAL COMBAT ENVIRONMENTS</div>
<div style="border-top:1px solid #c8c5bf; max-width:200px; margin:0 auto 16px auto;"></div>
<div style="font-size:0.62rem; letter-spacing:2px; color:#9a9690;">
CURRENT THEATER: SYRIA -
[[Server Info/Airfields|AIRFIELDS]]
</div>
</div>

----

== 01 / Personnel Onboarding ==

New to SOURCE? Complete all onboarding steps before your first operation. Install required software, read the rules of engagement, and familiarise yourself with communications procedures.

[[Guides/New Member Guide|New Member Guide]] · [[Guides/SRS Setup|SRS Setup]] · [[Guides/Mod Installation|Mod Installation]]

== 02 / General Knowledge ==
Contains all the Knowledge about the threats we could Face along with tactics to evade an neutralize.

[[SAM Surface to Air Missile]]

----

== 03 / multi-Service tactics, techniques, and procedures (MTTP) ==

All personnel are expected to operate within SOURCE standard communications procedures. This includes tactical brevity, ATC phraseology, and carrier comms.

'''IN CASE OF DOUBT USE PLAIN LANGUAGE'''

=== Communication ===
[[General/Tactical Communication Revision 1|Tactical Communication]] · [[General/CATC Communications Guide|CATC Communications Guide]] · [[General/Air Traffic Communication|Operating within Civil Airspace]] · [[DDFORM1801|Filing Flight Plans]] · [[How To Read Charts]]

For Unit-Specific Procedures reference ASSIGNED UNITS below

----

== 04 / Assigned Units ==

{| class="wikitable" style="width:100%;"
|-
! Squadron !! Aircraft
|-
| [[Squadrons/78th VMRS Shadow Knights|78th VMRS Shadow Knights]] || F-16C Viper
|-
| [[Squadrons/14th VSFS Top Hatters|14th VSFS Top Hatters]] || F/A-18C Hornet
|-
| [[Squadrons/509th VSFS Black Anvils|509th VSFS Black Anvils]] || F-15E Strike Eagle
|}

----

== 05 / Active Operations ==

Current campaign briefings, mission assignments, and sortie records are maintained in the operations section. All flight leads are responsible for keeping mission pages up to date following each operation.

[[Campaigns|View All Campaigns]]

File:BanditReversal.png

2026-05-23T17:58:51Z

Niknam3:

File:LeadTurnToEarly.png

2026-05-23T17:56:01Z

Niknam3:

File:TwoCircleEntry.png

2026-05-23T17:55:24Z

Niknam3:

File:LeadTurnWithoutTurningRoom.png

2026-05-23T17:54:31Z

Niknam3:

File:LeadTurn.png

2026-05-23T17:53:44Z

Niknam3:

File:TurnCircleEntryWindow.png

2026-05-23T17:52:54Z

Niknam3:

File:DifferentRateTurns.png

2026-05-23T17:52:23Z

Niknam3:

File:OffsetTurnCircles.png

2026-05-23T17:51:34Z

Niknam3:

File:OutOfPlaneManeuvre.png

2026-05-23T17:50:45Z

Niknam3:

Procedures/78th/A2A/BFM

2026-05-23T17:50:20Z

Niknam3: /* The Turn Circle */

== BFM I — Energy and the EM Diagram ==
This part is based on [https://youtube.com/playlist?list=PLd5Qdmhmp3Y5-SDJjOzuUqV3m3mmuieTQ&si=FNdYqWagls5zNQjG this] video series by [https://www.youtube.com/@TheOpsCenterByMikeSolyom The Ops Center by Mike Solyom].

=== Energy ===
Every decision in a dogfight is an energy decision. An aircraft's energy state is expressed primarily as airspeed and altitude. The faster and higher you are, the more potential energy you have to maneuver. Energy buys turn rate, separation, and shot opportunities. Waste Energy and you will loose.

The First principle of BFM is simple: '''build energy and save it until you have a reason to spend it.''' That reason is either a shot on the bandit or denying a shot on yourself. If neither opportunity exists, maintain or build energy. Do not waste.

=== The Energy Maneuverability (EM) Diagram ===
The EM diagram is the definitive tool for understanding how an aircraft performs in a turning fight. It maps turn rate against airspeed for a specific set of parameters: aircraft weight, altitude, throttle setting, and configuration. Every number on the chart is only valid for those exact conditions.

For the F-16C in DCS the reference diagram is: '''Full AB · Clean · Sea Level · 12300 kg'''
[[File:F16 EM Diagram.png|center|frameless|945x945px]]

Key performance figures from this diagram:
{| class="wikitable" style="width:100%;"
!Parameter
!Value
!Condition
|-
|Max instantaneous turn rate
|24°/s
|393 KCAS
|-
|Max sustained turn rate
|18°/s
|523 KCAS
|-
|Min sustained turn radius
|1,462 ft
|246 KCAS
|-
|Min turn radius
|1,399 ft
|169 KCAS
|}
'''Note:''' The F-16's G-limiter schedule is not fully reflected in the upper portion of this diagram. Maximum instantaneous performance may be lower than indicated in practice. The DCS implementation of the F-16 Flight Model also severely limits the F16's Sustained turn rate.

=== Reading the Diagram ===

==== The Axes ====

* '''Horizontal axis''': airspeed in Mach (lower) and KCAS (higher)
* '''Vertical axis''': turn rate in degrees per second (°/s)

Moving up on the chart means higher turn rate.

==== The Lines ====
'''The Envelope (red)'''

The outer boundary of what the aircraft can physically do. It is shaped by three limits:

* '''Structural G limit''' is the maximum G the airframe can sustain; forms the upper-right boundary
* '''Angle of attack limit''' — the stall boundary; forms the left boundary
* '''Speed limit (Vmax)''' — the right-side boundary (going supersonic will nearly always kill both your turn rate and radius and is not desirable)

No matter what the pilot does, the aircraft cannot operate outside the red envelope.

'''Turn Radius Lines (brown)'''

These straight lines show turn radius in feet at any given point on the chart. Moving up and left gives a smaller radius.

'''G-Load Lines (gray)'''

Indicate how many G must be pulled to reach that point on the chart. To achieve a Instantaneous Turn rate of 20° at 400CAS the aircraft needs to pull about 7.5G

'''Ps Lines (solid black)'''

Specific excess power lines are the most important lines on the chart. They show whether the aircraft is gaining or losing energy at any given combination of speed and G.

* '''Ps = 0''' — the aircraft is exactly maintaining its energy state. This is the sustained turn line. The maximum turn rate achievable while sustaining speed and altitude sits on this line.
* '''Ps > 0 (positive numbers)''' — the aircraft is gaining energy. It can accelerate or climb while maintaining the current turn.
* '''Ps < 0 (negative numbers)''' — the aircraft is losing energy. It is spending saved energy for extra turn performance. This is temporary and cannot be maintained indefinitely.

Anything above the Ps = 0 line is an energy expenditure. The higher above it you go, the faster you bleed speed.

=== Corner Velocity ===
Corner velocity is the airspeed at which the aircraft achieves its maximum instantaneous turn rate — the peak of the envelope. For the F-16C at sea level this occurs at '''401CAS''', producing '''24°/s'''.

For the maximum Instantaneous turn the DCS Flight model requires the pilot to pull 9G and decent with over 1200ft/s which is in any way not sustainable unless the a significant amount of Altitude has been built up. DO NOT use this unless you need to safe your life.

=== Sustained Turn Rate ===
The sustained turn rate is the maximum turn rate the aircraft can maintain indefinitely without losing speed or altitude. For the F-16C at sea level this is '''18°/s @ 523 KCAS'''.

In practice, sustained operations happen on or near the Ps = 0 line. The pilot's job is to find and hold that point. Sadly in DCS to hold and maintain that line is impossible. To Fly Perfect Sustained Turn Rate you need to pull 9G in full afterburner. You will know that you hit the perfect speed if, at max pull, in a level turn, the Jet neither gains nor looses Max energy.

A sustained 9G turn will black out any pilot. To Compensate the Pilot should fly slighly below the Optimal Speed allowing for higher turn rate while loosing a small amount of energy. Once the Jet reaches around 70-80 KTS below optimal speed the pilot should reduce the pull to about 6G for maximum recovery speed. While only pulling 6G the jet will gain energy fast. Once back at optimal speed continue to pull 9G.

If you overshoot the Optimal Speed you will notice that even at max pull the aircraft is still gaining airspeed. In this case execute a spiral climb to return back to Optimal Speed while utilizing the excess Energy.

If you undershoot the Optimal Speed you will notice that at max pull the aircraft is loosing airspeed fast. Either Reduce pull back to 6G until at better speed or trade altitude for extra Energy.

=== Instantaneous vs Sustained ===
{| class="wikitable" style="width:100%;"
!
!Instantaneous
!Sustained
|-
|'''Definition'''
|Maximum turn rate achievable at any moment
|Maximum turn rate maintainable indefinitely
|-
|'''F-16C value (sea level)'''
|24°/s @ 393 KCAS
|18°/s @ 523 KCAS
|-
|'''Energy cost'''
|High: Far above Ps = 0, bleeding speed fast (expect around 50kts/s)
|None if optimally flown on Ps = 0 line
|-
|'''When to use'''
|Short bursts for a shot opportunity or to deny a shot
|Default gameplan in any sustained turning fight
|}
Instantaneous turn rate is spending saved energy. It is a powerful tool but a temporary one. A pilot who pulls to instantaneous continuously will bleed to low speed, and lose the fight on energy.

=== How Altitude and Stores Affect the Diagram ===
The reference diagram is for sea level, clean, full AB. Both altitude and external stores degrade performance:

* '''Altitude''': thinner air reduces lift and engine thrust. Turn rate and sustained performance both decrease. The same airspeed produces a larger turn radius at altitude.
* '''Weight:''' Fuel or Stores will both make you heavy. The heavier you are the worse the performance. As you burn fuel the optimum Sustained turn rate Speed will decrease into manageable Levels.

=== Practical Application ===
In the fight itself: '''treat energy like money.''' Build it, save it, and spend it only when the return is worth it. A valid shot, or surviving by denying the adversary a shot oportunity. Spending energy for no tactical gain is a losing strategy.

== BFM II — Angles and Geometry ==

=== Angles and Definitions ===

[[File:Angles.webp|frameless|715x715px]]

==== Antenna Train Angle (ATA) ====
The ATA is the position of the bandit left or right of the fighter's nose on the radar display. ATA 0 means the target is dead ahead. ATA 30R means the target is 30° to the right of your nose.

The ATA is a property of your own aircraft's orientation. It changes when '''you''' maneuver. It does not change instantaneously when the bandit maneuvers.

On the F-16 FCR, ATA is read on the horizontal axis.

==== Target Aspect (TA) ====
Target Aspect, not to confuse with Aspect Angle is how the bandit appears from your perspective. Specifically, the angle from the bearing line of the fighter to the '''nose''' of the target. It describes which part of the bandit you are looking at.

* TA 0 —you are looking at the bandit's nose (head-on)
* TA 90 — you are looking at the bandit's side
* TA 180 — you are looking at the bandit's tail (pure stern)

TA is signed left or right depending on which side of the bandit you are observing.

Unlike ATA, Target Aspect is '''entirely determined by the bandit's heading''' relative to the bearing line between you. You cannot change it instantaneously. You can only influence it over time by maneuvering to change the geometry.

The F-16 does not display TA directly. It displays the '''Aspect Angle (AA)''', which is the supplementary angle of TA (AA = 180° − TA). A tail-aspect shot has AA 0; a head-on shot has AA 180.
[[File:AAvsTA.webp|thumb|600x600px]]
Common TA labels used in brevity:
{| class="wikitable"
!TA
!AA
!Label
|-
|0°–30°
|150°–180°
|Hot
|-
|31°–75°
|105°–149°
|Flank
|-
|76°–110°
|70°–104°
|Beam
|-
|111°–150°
|30°–69°
|Drag
|-
|151°–180°
|0°–29°
|Cold
|}

==== Cut ====
Cut is the angle from the '''Fighter Heading (FH)''' to the '''Bandit Reciprocal (BR)'''. It describes where your nose is pointing relative to the bandit's course.

Cut is an older concept but remains one of the most useful tools for predicting how the geometry will evolve. Three reference cases:

* '''Cut greater than Collision Course''' — your nose is in front of the bandit. Over time, TA decreases and Lateral Separation decreases. You are closing the geometry aggressively.
* '''Cut equal to Collision Course''' — the magic case. TA is captured: it does not change. Lateral Separation decreases. If co-altitude, you will eventually collide.
* '''Cut less than Collision Course (Zero-Cut / Parallel)''' — your nose points at the bandit's reciprocal. TA increases over time. Lateral Separation is captured: it does not change.
* '''Cut-Away''' — your nose points away from the bandit entirely. Both TA and Lateral Separation increase. Used to build angles or lateral room.

==== Degrees to Go (DTG) / Heading Crossing Angle (HCA) ====
DTG is the number of degrees the fighter needs to turn to be '''parallel''' to the bandit's flight path. It is the supplementary angle of Cut. A useful memory aid: ''Degrees to Go — where? Parallel.''

==== Lateral Separation (LS) ====
Lateral Separation is the perpendicular distance between the two flight paths. It determines how much maneuvering room exists for a conversion. It is approximated as:
LS (ft) = TA × SR × 100
Where SR is slant range in nautical miles. Lateral Separation matters most when planning a stern conversion or assessing whether a shot is geometrically viable.

==== Direction of Passage (DOP) ====
DOP describes the direction the bandit would cross your flight path if neither aircraft maneuvered. Called as left-to-right or right-to-left. Useful shorthand for building SA quickly.

==== Slant Range (SR) ====
[[File:SlantRange.webp|thumb|500x500px|center]]
The straight line-of-sight distance between the two aircraft in three-dimensional space. On the F-16 FCR this is the range displayed on the scope.

=== Pursuit Types ===
[[File:Pursuit.webp|thumb|700x700px|center]]
The type of pursuit describes where your nose is pointing relative to the target.
{| class="wikitable" style="width:100%;"
!Pursuit Type
!Nose Position
!Common Use
|-
|'''Lead Pursuit'''
|In front of the target
|Collision Course, gun employment from RQ
|-
|'''Pure Pursuit'''
|Directly at the target
|Simple conversions; commonly overused by new pilots
|-
|'''Lag Pursuit'''
|Behind the target
|Geometry management, WVR maneuvering
|}

== BFM III — Offensive BFM ==
Offensive BFM begins with you in a position of advantage. The bandit is somewhere in your forward hemisphere and your job is to convert that advantage into a weapons solution before he can deny it.

=== The Turn Circle ===
[[File:TurnCircleEntry.png|frameless|900x900px]]

Every maneuvering aircraft has a turn circle, the circular path it is flying at any given moment. To employ weapons on the bandit you must get inside his turn circle, or at minimum align with it. Getting outside means you are turning wider than he is and falling behind.

The cue for turn circle entry is a high LOS rate (see below). As you approach the edge of the bandit's circle the bandit will begin moving rapidly across your field of view. Turn at that moment. Turn too early and you cross inside his radius, giving him a reversal opportunity. Turn too late and you end up outside his circle with AA too high to employ.

=== Line of Sight Rate ===
Line of Sight (LOS) rate is the speed at which the bandit moves across your field of view. It is one of the most important diagnostic tools in BFM and appears throughout offensive, defensive, and high aspect engagements.

A high LOS rate means the bandit is moving quickly across your canopy. A low or zero LOS rate means the bandit is stable relative to your nose. LOS rate tells you two things:

* '''Where are you relative to the bandit's turn circle'''? A sudden spike in LOS rate signals that you have reached the edge of his turn circle. Inside his circle, LOS rate is high. Outside it, LOS rate is low.
* '''What is the Geometry doing?''' Aft LOS movement means the bandit is drifting toward your 6; forward LOS movement means he is drifting toward your 12. The direction and speed of that drift tells you whether the geometry is improving or deteriorating.

Learning to read LOS rate is not an instrument skill. It is a visual habit and requires practice.

=== The Control Zone ===
The control zone is the offensive firing position, located in the bandit's rear quarter. From the control zone you have sufficient range for weapon employment, a manageable aspect angle, and controlled closure.

Getting into the control zone is not enough. You must '''assess''' before employing. The assessment uses the '''Rule of Threes''':
{| class="wikitable" style="width:100%;"
!Parameter
!Value
!Notes
|-
|Range
|~3,000 ft
|Read from HUD or FCR
|-
|Aspect Angle
|≤30°
|Draw an imaginary box around the bandit — square silhouette means ~30° AA
|-
|Closure
|Steady and controlled
|Not increasing, not zero
|}
All three must be satisfied before moving in for a gun solution. If any are not met, reposition first.

=== Repositions ===
Repositions are controlled adjustments to fix range, closure, or aspect problems from the control zone.

==== Lead Reposition ====
Used when the bandit is pulling away and range is increasing. Pull lead pursuit to close the gap. Do not overshoot.

==== Lag Reposition ====
Used when closure is too high. Pull lag pursuit to slow closure and improve aspect. The bandit will drift aft in your field of view. Reassess once closure is controlled.

==== Ease Reposition ====
Used when range and closure are acceptable but aspect is slightly high. Ease back on the stick to widen your turn circle slightly. AA will decrease as the geometry opens. Once AA is acceptable, resume the original pull and reassess. This is a small correction — if aspect is significantly high, use a lag reposition instead.

=== Visual Aspect Estimation ===
Without looking at instruments, AA can be estimated by the shape of the bandit's silhouette:

* '''Rectangle''' (fuselage longer than wingspan) means AA is above 30°, too high for a clean gun solution
* '''Square''' (fuselage approximately equal to wingspan) means AA is approximately 30°, Rule of Threes satisfied
* '''Narrowing toward a point''' means AA is near 0°, pure tail-aspect

This visual check is faster than any instrument cross-check in a close turning fight.

=== Weapon Employment ===

==== Heat Seeker (FOX-2) ====
A valid FOX-2 shot requires a confirmed seeker tone and AA within the missile's acquisition envelope, typically ≤60° for rear-quarter shots. Do not fire without tone. At significant AA the seeker may struggle to acquire, so use a lag or ease reposition to reduce AA before attempting the shot.

==== Guns ====
A valid gun solution requires the Rule of Threes to be fully satisfied with the pipper placed on the bandit. In a turning fight this requires lead pursuit. Your nose must be ahead of the bandit's projected path, not pointed at him. The amount of lead required varies with range and closure rate.

A tracking shot requires the pipper to remain on the bandit for a sustained period. A snapshot is a momentary pipper-on opportunity taken when it presents itself, lower probability but sometimes the only option available.

=== The Quarter Plane ===
The quarter plane is a last-resort maneuver used when closure rate has become dangerously high and an overshoot is imminent. It is not a reposition.

The cue to act is approximately 1,000 ft of range, at which point the bandit's wingspan will fill roughly half the EEGS funnel on the HUD.

Execution:

# Roll wings level with the horizon
# Set idle power
# Pull maximum performance up and out of the bandit's plane of motion

This arrests closure and separates you vertically from the bandit's plane. Once clear, roll back into a turn toward the bandit and reassess. The quarter plane costs significant energy and altitude. Use it only when nothing else will prevent the overshoot.

=== Common Errors ===
{| class="wikitable" style="width:100%;"
!Error
!Consequence
!Correction
|-
|Late turn circle entry
|End up outside the bandit's circle with AA too high
|Watch for the LOS rate spike and turn at that moment
|-
|Early turn circle entry
|Cross inside bandit's radius, give him a reversal picture
|Wait for the LOS rate spike
|-
|Firing without satisfying Rule of Threes
|Low probability shot
|Reposition first, assess before employing
|-
|Pure pursuit at significant AA
|Missile must curve hard, degraded effectiveness
|Use CC or LC geometry for missile employment
|-
|Uncontrolled closure
|Overshoot, offensive position lost
|Use lag reposition early, quarter plane as last resort
|-
|Spending energy without reason
|Slow speed, large radius, advantage lost
|Maintain AB, only pull above sustained rate for a specific reason
|}

== BFM IV — Defensive BFM ==
This part is based on [https://www.youtube.com/playlist?list=PLd5Qdmhmp3Y5-SDJjOzuUqV3m3mmuieTQ this] video series by [https://www.youtube.com/@TheOpsCenterByMikeSolyom The Ops Center by Mike Solyom].

The objectives of defensive BFM are, in order of priority: survive, deny the bandit a weapons solution, and create the conditions for a role reversal. Survival is the primary objective. A fighter that remains in the fight presents a continuous problem to the attacker — he must maintain focus on the defender, consuming energy and attention that could otherwise be used offensively. Every second the defender survives is a second for supporting elements to close.

=== The Defensive Gameplan ===
The foundation of defensive BFM is the sustained rate turn. The defender should establish and maintain best sustained turn rate as the default gameplan. This accomplishes two things simultaneously: it maximizes the defender's turn performance for the duration of the engagement, and it preserves energy for subsequent maneuvering.

Deviation from the sustained rate gameplan should only occur when a specific threat — an imminent gun or missile shot — requires a more aggressive response. Expending energy prematurely leaves the defender slow, with a large turn radius and reduced options.

=== Cross-Check Discipline ===
In defensive BFM the pilot's attention is predominantly outside the cockpit on the bandit. However, three parameters must be periodically cross-checked throughout the engagement:
{| class="wikitable" style="width:100%;"
!Parameter
!Significance
|-
|'''Lift Vector'''
|Determines plane of motion and available turn rate
|-
|'''G'''
|Confirms correct turn performance is being applied
|-
|'''Airspeed'''
|Identifies energy state; confirms sustained rate speed is maintained
|}
The cross-check must not interrupt tally on the bandit for extended periods. Brief instrument scans returning immediately to visual are the correct technique. Loss of tally in a defensive engagement is a significant threat to survival.

=== Altitude Management ===
Altitude is a reserve of potential energy. Trading altitude for airspeed in a defensive turn temporarily increases available turn rate above the Ps = 0 line by lowering the lift vector below the horizon. This option is only available until the floor is reached. At that point the defender is constrained to a level sustained rate turn and loses the altitude trading option entirely.

=== Reading the Bandit's Intentions ===
The defender must continuously assess the bandit's pursuit course to anticipate his next action. The pursuit course is read visually:
{| class="wikitable" style="width:100%;"
!Pursuit Course
!Visual Cue
!Likely Intent
|-
|'''Pure pursuit'''
|Narrow nose-on profile
|Missile shot setup; seeker acquisition in progress
|-
|'''Lead pursuit'''
|Bandit's belly visible; nose pulled ahead of defender
|Gun shot imminent
|-
|'''Lag pursuit'''
|Top of bandit's aircraft visible; aft LOS movement
|Controlling closure; repositioning for follow-on attack
|}
Transition from lag to pure to lead is the signature sequence of an impending gun attack. Recognition of this sequence is the primary defensive cross-check task outside the cockpit.

Range assessment is equally important. The bandit's size relative to your field of view gives a continuous indication of closure. A bandit that fills a significant portion of your view is inside 2,500 ft and approaching gun parameters.

=== Maneuvers ===

==== Tighten Down ====
The tighten down is the first and most conservative response to a bandit closing into gun parameters. It is executed by increasing back pressure on the stick while already in a sustained rate turn, transitioning from sustained rate to a higher instantaneous turn rate.

The tighten down achieves two simultaneous effects. First, it rotates the defender's vulnerable rear quarter away from the attacker, driving the bandit outside the weapon employment zone. Second, the sudden airspeed reduction caused by the increased G creates a high closure rate problem for the attacker, forcing him to reposition to satisfy the Rule of Threes. This repositioning produces aft LOS movement and potentially a reversal picture.

The tighten down is an energy expenditure. It should be released once the immediate threat is defeated, returning to slightly below sustained rate and allowing AB to restore the energy state.

==== Out-of-Plane Maneuver (OOP) ====
The out-of-plane maneuver removes the defender from the attacker's plane of motion, forcing the attacker to reset his geometry. In a sustained rate turn both aircraft are operating in approximately the same plane of motion. Moving out of that plane disrupts the attacker's sight picture and solution geometry.

Execution:

# Unload the aircraft — reduce back pressure to below 1G
# Reposition the lift vector off the bandit, above or below his plane of motion
# Apply smooth back pressure to establish a turn in the new plane of motion
# Allow sufficient time for the aircraft to develop movement in the new plane before any follow-on maneuver
# Assess LOS rate and bandit pursuit course in the new plane

The unloaded roll is critical. Rolling while pulling G consumes energy without producing useful turning room. The unload must precede the roll.

Upon establishing the new plane of motion, assess for a reversal opportunity. If high aft LOS rate combined with high HCA and close range is observed, a reversal may be executed. Otherwise, continue maneuvering in the new plane.

==== Jink ====
The jink is a last-resort maneuver executed when a gun shot is assessed as imminent and neither the tighten down nor the OOP has defeated the attacker's solution. It combines elements of both into a single aggressive sequence designed to spoil the attacker's plane of motion and create a closure problem simultaneously.

Execution:

# Set throttle to idle
# Unload the aircraft
# Position the lift vector below the bandit
# Apply maximum onset rate back pressure and hold until aerodynamic buffet onset

The resulting airspeed reduction is severe and deliberate. The attacker is presented with a sudden, unforecast closure rate and a simultaneous change in plane of motion. If the attacker does not immediately reposition he will overshoot. If he does reposition, aft LOS movement will develop and a reversal picture may emerge.

If a reversal picture does not present after the first jink, execute a second jink to the opposite side:

# Idle power maintained
# Unload
# Reposition lift vector to the opposite side of the bandit
# Maximum onset back pressure

Continue until the attacker is forced into lag or a reversal picture develops. The jink sequence trades altitude at a high rate. Do not initiate within 1,500 to 2,000 ft of the floor. The jink is the highest energy expenditure maneuver in defensive BFM and is reserved strictly for imminent gun shot situations.

=== The Reversal ===
A reversal is a turn at an opportune moment in the opposite direction, executed to transition from a defensive position to a neutral or offensive one. Correctly timed, a reversal exploits the attacker's angles and closure to reposition the defender onto an advantageous bearing. Incorrectly timed, it degrades the defender's position further.

The opportunity for a correct reversal is rare and may only be available for a few seconds. More often than not a reversal will degrade the situation rather than improve it. Patience and recognition of the correct picture are essential.

==== The Reversal Picture ====
The reversal picture is the combination of visual conditions that indicate a reversal opportunity exists:

* High heading crossing angle (HCA), combined with
* Close range, and or high aft LOS rate

A practical assessment question: ''does it appear that the bandit will cross behind my tail with minimal assistance from me?'' If the answer is yes, execute. If there is any doubt, do not reverse. A premature reversal presents the attacker with a stable, predictable target and makes his job easier.

==== Execution ====
The reversal is executed using an unloaded roll:

# Reduce back pressure to unload the aircraft
# Roll to the opposite direction
# Resume back pressure once established in the new turn
# Shift visual focus to the opposite side to regain tally on the bandit

Lift vector placement after the reversal depends on range. At close range, position the lift vector above or below the bandit to build turning room before pulling into his plane of motion. At greater range, place the lift vector directly on the bandit.

A successful reversal will typically result in a scissors — a neutral position from which either pilot may gain an advantage. This is a significant improvement over the defensive.

=== Maneuver Selection Summary ===
{| class="wikitable" style="width:100%;"
!Situation
!Maneuver
!Notes
|-
|Bandit in lag or pure pursuit, not yet in gun parameters
|Sustained rate turn
|Conserve energy; maintain cross-check
|-
|Bandit transitioning to lead pursuit, gun shot developing
|Tighten down
|First response; moderate energy cost
|-
|Tighten down insufficient; bandit maintaining solution
|Out-of-plane maneuver
|Disrupts attacker geometry; assess for reversal
|-
|Gun shot imminent; no other option
|Jink
|Last resort; high energy cost; do not use prematurely
|-
|Reversal picture present
|Reversal
|Execute with unloaded roll; if in doubt, do not reverse
|}

== BFM V — High Aspect BFM ==
This part is based on [https://www.youtube.com/playlist?list=PLd5Qdmhmp3Y5-SDJjOzuUqV3m3mmuieTQ this] video series by [https://www.youtube.com/@TheOpsCenterByMikeSolyom The Ops Center by Mike Solyom].

High aspect BFM occurs when neither aircraft has a positional advantage at the merge. Both aircraft are nose-to-nose and the engagement begins from a neutral position. The name comes from the fact that at the merge, both aircraft are presenting high aspect to each other.

There are two reasons a pilot ends up in a high aspect fight. Either the bandit turns his nose toward you at the conclusion of a BVR intercept, or a BFM error led to the loss of an offensive position. The response is the same in either case.

=== The Lead Turn ===
The lead turn is the single most important concept in high aspect BFM. It is executed before the merge and determines the starting position of the fight.

Rather than waiting until the bandit's 3-9 line to begin turning — which produces a neutral merge — the pilot initiates the turn early. This builds an angular advantage before the first pass. At the sustained turn rate of the F-16, every additional second of turn produces more than 10° of angular advantage that the bandit must make up. Even two seconds of early turning can produce an advantage that a bandit in the same aircraft cannot recover from.

The lead turn cue is a rapidly increasing LOS rate from 11 to 10 o'clock for a left-side pass, or 1 to 2 o'clock for a right-side pass. This is the correct moment to turn. Turning too late leaves you behind the bandit with an energy problem. Turning too early gives the bandit a reversal picture.

If the lead turn is started too late there is little that can be done — accept the problem and manage it. If the lead turn is started too early, ease off the G momentarily until the bandit's LOS rate resumes, then resume the pull.

When executed correctly, the lead turn produces a '''stern conversion''' — the pilot arrives at the bandit's six o'clock within gun range without requiring further maneuvering.

=== Turning Room ===
Turning room is the separation between the two aircraft that is available to turn into. It can be built vertically or laterally, but never to the outside of the bandit's turn circle — floating outside gives the bandit more time and reduces the angular advantage gained in the lead turn.

The overriding factor when deciding whether to climb or descend is ease of tally on the bandit, and denying the bandit tally on you. Use the environment — put the bandit against a cloud, get between the bandit and the sun, avoid staying at the same altitude as the bandit. Tally is survival.

Vertical turning room comes with an energy cost that must be accounted for. A descent toward the bandit will add approximately 100 KCAS at the merge. A climb will cost approximately 100 KCAS. If this is not managed, the pilot will either overshoot the bandit or arrive too slow to sustain a competitive turn rate. Adjust entry speed before the turn-in accordingly. The fastest way to build speed without turning is to unload the aircraft — do this in the seconds between the turn-in and the merge.

Lateral turning room is always built to the inside of the bandit's turn circle. There is no useful lateral room to the outside.

=== Determining Fight Geometry ===
At the merge, the direction the bandit turns determines the geometry of the fight. '''The last aircraft to turn decides whether the engagement becomes a one-circle or two-circle fight.''' This is a deliberate choice — a pilot who executes a lead turn gives up the ability to choose the fight geometry, because the bandit turns last. The lead turn advantage is generally worth this tradeoff.

* '''Bandit turns toward you''' → two-circle fight. Both aircraft chase each other's tails. Ground track resembles two separate circles.
* '''Bandit turns away from you''' → one-circle fight. Both aircraft circle back toward each other for a second nose-to-nose pass. Ground track resembles a single circle.

Identifying which geometry has been established requires only one visual check: if the bandit is nose-to-tail relative to you, it is a two-circle fight. If it is nose-to-nose, it is a one-circle fight.

=== Losing Tally ===
Losing visual on the bandit in a turning fight is dangerous. Two rules apply immediately:

'''Do not fly straight and level while searching.''' Straight flight makes the defender's job trivial. Maintain the turn at all times.

'''Search along the turn circle.''' The bandit's most likely position is in the high-probability kill zone behind and above — the high-Pk WEZ. When the area behind you is clear, scan upward along the turn circle. The bandit will be somewhere along that arc if still engaged.

== BFM V-A — Two-Circle Fight ==
A two-circle fight begins when the bandit turns away from you at the merge. Both aircraft are now chasing each other's tail, producing a ground track that resembles two separate circles. The fight is a turn rate contest — the aircraft that can sustain a higher turn rate will eventually work its nose onto the the tail of the other.

=== The Default Gameplan ===
In a two-circle fight, maintain best sustained turn rate. Do not deviate from this. The temptation to pull into lead or pure pursuit to force a quick shot will produce a predictable result: range closes rapidly, aspect increases to beam or beyond, and the bandit drifts aft on the canopy. The fight resets to where it started. This yo-yoing effect will repeat indefinitely if the pilot keeps chasing the shot prematurely. Stay on the sustained rate turn and let the geometry develop.

=== Reading the Fight ===
As both aircraft complete the first circle, the bandit's position on the canopy provides continuous information about how the fight is developing. Three conditions are possible:
{| class="wikitable" style="width:100%;"
!Visual Cue
!Assessment
!Action
|-
|Bandit moving forward on the canopy, aspect stagnant or decreasing
|Winning — angular advantage is building
|Continue sustained rate turn; prepare for lead turn at next merge
|-
|Bandit moving forward on the canopy, aspect increasing toward nose-to-nose
|Neutral — neither pilot has an advantage
|Assess energy state; choose one-circle or two-circle at the next merge
|-
|Bandit's motion stagnant or drifting aft, bandit showing narrow nose-on profile
|Losing — bandit is gaining angular advantage
|Check G — increase to moderate buffet; if insufficient, transition to defensive BFM
|}
When neutral cues are present, the decision between one-circle and two-circle at the next merge is based on energy state. Above approximately 350 KCAS the aircraft has sufficient energy for a sustained rate two-circle game plan. Below that, the turn radius is already small enough that a one-circle minimum radius game plan is more effective.

=== Turn Circle Extension (TCX) ===
Even with a turn rate advantage, the two turn circles will not be perfectly aligned after the first pass. The bandit will yo-yo up and down the canopy as the circles overlap and separate. Forcing a shot during this phase produces the same premature high-aspect result described above. The solution is the turn circle extension.

A TCX is two to three seconds of easing off the G — not a full unload, just a reduction in back pressure that allows the center of the turn circle to shift. This repositions the turn circle to better align with the bandit's. It is not a straight line, though it can be. It is simply a brief relaxation of the sustained rate pull followed by resumption.

The cue to extend is the bandit sliding into the assessment window — approximately 45 to 60 degrees AA — combined with aft LOS movement. This is the same assessment window used in offensive BFM. If the bandit's aspect is above 30 degrees, ease back on the G. That easing is the TCX.

Timing matters. A TCX initiated too early shifts the turn circle sideways without closing the gap. A TCX initiated too late pushes both circles further apart. The correct moment is when the bandit is in the assessment window with aft LOS developing.

Multiple TCX corrections should be expected before the turn circles align. The manual notes that this process can require between 500 and 1,000 degrees of turning — approximately three times around the circle. Do not force it. Once the circles align, the fight transitions naturally into offensive BFM.

=== Regaining Tally ===
If tally is lost during a two-circle fight, apply the rules from the fundamentals section: maintain the turn and scan along the turn circle upward through the high-Pk zone. In a nose-to-tail fight the bandit will be somewhere along that arc. Do not level the wings.

== BFM V-B — One-Circle Fight ==
A one-circle fight begins when the bandit turns toward you at the merge. Both aircraft are now circling back to meet each other in a second nose-to-nose pass. The ground track resembles a single circle. Unlike the two-circle fight where turn rate is the deciding factor, the one-circle fight is a '''turn radius contest'''.

=== Why Radius and Not Rate ===
In a two-circle fight, a smaller radius produces no advantage because both aircraft are always on opposite sides of their respective circles and never converge to a point where the nose can be brought to bear. Turn rate determines who gets there first.

In a one-circle fight the geometry is different. Both aircraft are converging on the same point — the next merge. The aircraft with the smaller radius gets its nose pointed at the bandit sooner, creating an opportunity for a lead turn or even a shot before the second pass. The aircraft with the larger radius arrives late and with less angular advantage.

=== The Minimum Radius Gameplan ===
To minimize turn radius in the F-16, pull enough G to reach a moderate aerodynamic buffet. The buffet indicates the aircraft is operating above the sustained turn rate and approaching the maximum lift line on the EM diagram — the region of minimum radius. Do not stall. A moderate buffet is the target.

The F-16 does not have an audio cue for this in DCS. Use the physical buffet as the indicator. If nothing is shaking, more G is needed.

=== Reading the Fight ===
As both aircraft come around the circle toward the second merge, the bandit's position on the canopy indicates whether the radius fight is being won or lost:
{| class="wikitable" style="width:100%;"
!Visual Cue
!Assessment
!Action
|-
|Bandit moving forward on the canopy, aspect stagnant or decreasing, top of bandit's aircraft visible
|Winning — angular advantage is building
|Execute lead turn at next merge to convert to offensive BFM
|-
|Bandit near or inside the canopy, nose pointed at you, bandit showing narrow nose-on profile
|Neutral — neither pilot has significant advantage
|Assess energy state; choose fight geometry at next merge
|-
|Bandit's motion stagnant or drifting aft, bandit showing narrow nose-on profile
|Losing — bandit is gaining the angular advantage
|Increase G to moderate buffet; if insufficient, transition to defensive BFM
|}

=== At the Next Merge ===
A one-circle fight always leads to a second merge. Three outcomes are possible at that merge:

* '''Another one-circle''' — bandit turns away again. Continue minimum radius game plan.
* '''Two-circle''' — bandit turns toward you. Transition to sustained rate game plan.
* '''Scissors''' — both aircraft begin reversing rapidly on each other. See below.

The decision between one-circle and two-circle at the second merge is based on energy state. Above approximately 350 KCAS the aircraft has enough energy for a sustained rate two-circle game plan. Below that, the turn radius is already small and one-circle minimum radius is more effective. Do not be indecisive — the last fighter to turn determines the fight geometry. Commit to a direction.

=== The Scissors ===
The scissors develops when both aircraft are reversing rapidly on each other and neither can establish a clean angular advantage. Both aircraft are within the other's turn circle. The ground track resembles scissor blades opening and closing.

The gameplan in a scissors is identical to the one-circle minimum radius game plan: minimize forward ground track by minimizing turn radius. Pull to moderate buffet, place the lift vector on the bandit, and select max afterburner. The aircraft with the smaller forward ground track will eventually fall behind the other and transition to an offensive position.

One-circle fights and scissors consume energy at a high rate due to the sustained high-G maneuvering required. Be aware of airspeed throughout — winning the radius fight but arriving slow leaves the bandit with an energy advantage that may be unrecoverable.

=== Losing the One-Circle ===
If the bandit is gaining the angular advantage, the symptoms are: the bandit's motion on the canopy goes stagnant or drifts aft, and the bandit's profile narrows to a pure pursuit nose-on silhouette. This is the bandit executing the same minimum radius game plan successfully.

When losing cues are present, first confirm G is sufficient — pull to moderate buffet if not already there. If the situation continues to deteriorate, transition to defensive BFM immediately. The one-circle fight has become a defensive situation and should be treated as one.

Never stop maneuvering. A neutral position is always recoverable.

Procedures/78th/A2A/BFM

2026-05-23T17:46:46Z

Niknam3: /* BFM V-B — One-Circle Fight */

== BFM I — Energy and the EM Diagram ==
This part is based on [https://youtube.com/playlist?list=PLd5Qdmhmp3Y5-SDJjOzuUqV3m3mmuieTQ&si=FNdYqWagls5zNQjG this] video series by [https://www.youtube.com/@TheOpsCenterByMikeSolyom The Ops Center by Mike Solyom].

=== Energy ===
Every decision in a dogfight is an energy decision. An aircraft's energy state is expressed primarily as airspeed and altitude. The faster and higher you are, the more potential energy you have to maneuver. Energy buys turn rate, separation, and shot opportunities. Waste Energy and you will loose.

The First principle of BFM is simple: '''build energy and save it until you have a reason to spend it.''' That reason is either a shot on the bandit or denying a shot on yourself. If neither opportunity exists, maintain or build energy. Do not waste.

=== The Energy Maneuverability (EM) Diagram ===
The EM diagram is the definitive tool for understanding how an aircraft performs in a turning fight. It maps turn rate against airspeed for a specific set of parameters: aircraft weight, altitude, throttle setting, and configuration. Every number on the chart is only valid for those exact conditions.

For the F-16C in DCS the reference diagram is: '''Full AB · Clean · Sea Level · 12300 kg'''
[[File:F16 EM Diagram.png|center|frameless|945x945px]]

Key performance figures from this diagram:
{| class="wikitable" style="width:100%;"
!Parameter
!Value
!Condition
|-
|Max instantaneous turn rate
|24°/s
|393 KCAS
|-
|Max sustained turn rate
|18°/s
|523 KCAS
|-
|Min sustained turn radius
|1,462 ft
|246 KCAS
|-
|Min turn radius
|1,399 ft
|169 KCAS
|}
'''Note:''' The F-16's G-limiter schedule is not fully reflected in the upper portion of this diagram. Maximum instantaneous performance may be lower than indicated in practice. The DCS implementation of the F-16 Flight Model also severely limits the F16's Sustained turn rate.

=== Reading the Diagram ===

==== The Axes ====

* '''Horizontal axis''': airspeed in Mach (lower) and KCAS (higher)
* '''Vertical axis''': turn rate in degrees per second (°/s)

Moving up on the chart means higher turn rate.

==== The Lines ====
'''The Envelope (red)'''

The outer boundary of what the aircraft can physically do. It is shaped by three limits:

* '''Structural G limit''' is the maximum G the airframe can sustain; forms the upper-right boundary
* '''Angle of attack limit''' — the stall boundary; forms the left boundary
* '''Speed limit (Vmax)''' — the right-side boundary (going supersonic will nearly always kill both your turn rate and radius and is not desirable)

No matter what the pilot does, the aircraft cannot operate outside the red envelope.

'''Turn Radius Lines (brown)'''

These straight lines show turn radius in feet at any given point on the chart. Moving up and left gives a smaller radius.

'''G-Load Lines (gray)'''

Indicate how many G must be pulled to reach that point on the chart. To achieve a Instantaneous Turn rate of 20° at 400CAS the aircraft needs to pull about 7.5G

'''Ps Lines (solid black)'''

Specific excess power lines are the most important lines on the chart. They show whether the aircraft is gaining or losing energy at any given combination of speed and G.

* '''Ps = 0''' — the aircraft is exactly maintaining its energy state. This is the sustained turn line. The maximum turn rate achievable while sustaining speed and altitude sits on this line.
* '''Ps > 0 (positive numbers)''' — the aircraft is gaining energy. It can accelerate or climb while maintaining the current turn.
* '''Ps < 0 (negative numbers)''' — the aircraft is losing energy. It is spending saved energy for extra turn performance. This is temporary and cannot be maintained indefinitely.

Anything above the Ps = 0 line is an energy expenditure. The higher above it you go, the faster you bleed speed.

=== Corner Velocity ===
Corner velocity is the airspeed at which the aircraft achieves its maximum instantaneous turn rate — the peak of the envelope. For the F-16C at sea level this occurs at '''401CAS''', producing '''24°/s'''.

For the maximum Instantaneous turn the DCS Flight model requires the pilot to pull 9G and decent with over 1200ft/s which is in any way not sustainable unless the a significant amount of Altitude has been built up. DO NOT use this unless you need to safe your life.

=== Sustained Turn Rate ===
The sustained turn rate is the maximum turn rate the aircraft can maintain indefinitely without losing speed or altitude. For the F-16C at sea level this is '''18°/s @ 523 KCAS'''.

In practice, sustained operations happen on or near the Ps = 0 line. The pilot's job is to find and hold that point. Sadly in DCS to hold and maintain that line is impossible. To Fly Perfect Sustained Turn Rate you need to pull 9G in full afterburner. You will know that you hit the perfect speed if, at max pull, in a level turn, the Jet neither gains nor looses Max energy.

A sustained 9G turn will black out any pilot. To Compensate the Pilot should fly slighly below the Optimal Speed allowing for higher turn rate while loosing a small amount of energy. Once the Jet reaches around 70-80 KTS below optimal speed the pilot should reduce the pull to about 6G for maximum recovery speed. While only pulling 6G the jet will gain energy fast. Once back at optimal speed continue to pull 9G.

If you overshoot the Optimal Speed you will notice that even at max pull the aircraft is still gaining airspeed. In this case execute a spiral climb to return back to Optimal Speed while utilizing the excess Energy.

If you undershoot the Optimal Speed you will notice that at max pull the aircraft is loosing airspeed fast. Either Reduce pull back to 6G until at better speed or trade altitude for extra Energy.

=== Instantaneous vs Sustained ===
{| class="wikitable" style="width:100%;"
!
!Instantaneous
!Sustained
|-
|'''Definition'''
|Maximum turn rate achievable at any moment
|Maximum turn rate maintainable indefinitely
|-
|'''F-16C value (sea level)'''
|24°/s @ 393 KCAS
|18°/s @ 523 KCAS
|-
|'''Energy cost'''
|High: Far above Ps = 0, bleeding speed fast (expect around 50kts/s)
|None if optimally flown on Ps = 0 line
|-
|'''When to use'''
|Short bursts for a shot opportunity or to deny a shot
|Default gameplan in any sustained turning fight
|}
Instantaneous turn rate is spending saved energy. It is a powerful tool but a temporary one. A pilot who pulls to instantaneous continuously will bleed to low speed, and lose the fight on energy.

=== How Altitude and Stores Affect the Diagram ===
The reference diagram is for sea level, clean, full AB. Both altitude and external stores degrade performance:

* '''Altitude''': thinner air reduces lift and engine thrust. Turn rate and sustained performance both decrease. The same airspeed produces a larger turn radius at altitude.
* '''Weight:''' Fuel or Stores will both make you heavy. The heavier you are the worse the performance. As you burn fuel the optimum Sustained turn rate Speed will decrease into manageable Levels.

=== Practical Application ===
In the fight itself: '''treat energy like money.''' Build it, save it, and spend it only when the return is worth it. A valid shot, or surviving by denying the adversary a shot oportunity. Spending energy for no tactical gain is a losing strategy.

== BFM II — Angles and Geometry ==

=== Angles and Definitions ===

[[File:Angles.webp|frameless|715x715px]]

==== Antenna Train Angle (ATA) ====
The ATA is the position of the bandit left or right of the fighter's nose on the radar display. ATA 0 means the target is dead ahead. ATA 30R means the target is 30° to the right of your nose.

The ATA is a property of your own aircraft's orientation. It changes when '''you''' maneuver. It does not change instantaneously when the bandit maneuvers.

On the F-16 FCR, ATA is read on the horizontal axis.

==== Target Aspect (TA) ====
Target Aspect, not to confuse with Aspect Angle is how the bandit appears from your perspective. Specifically, the angle from the bearing line of the fighter to the '''nose''' of the target. It describes which part of the bandit you are looking at.

* TA 0 —you are looking at the bandit's nose (head-on)
* TA 90 — you are looking at the bandit's side
* TA 180 — you are looking at the bandit's tail (pure stern)

TA is signed left or right depending on which side of the bandit you are observing.

Unlike ATA, Target Aspect is '''entirely determined by the bandit's heading''' relative to the bearing line between you. You cannot change it instantaneously. You can only influence it over time by maneuvering to change the geometry.

The F-16 does not display TA directly. It displays the '''Aspect Angle (AA)''', which is the supplementary angle of TA (AA = 180° − TA). A tail-aspect shot has AA 0; a head-on shot has AA 180.
[[File:AAvsTA.webp|thumb|600x600px]]
Common TA labels used in brevity:
{| class="wikitable"
!TA
!AA
!Label
|-
|0°–30°
|150°–180°
|Hot
|-
|31°–75°
|105°–149°
|Flank
|-
|76°–110°
|70°–104°
|Beam
|-
|111°–150°
|30°–69°
|Drag
|-
|151°–180°
|0°–29°
|Cold
|}

==== Cut ====
Cut is the angle from the '''Fighter Heading (FH)''' to the '''Bandit Reciprocal (BR)'''. It describes where your nose is pointing relative to the bandit's course.

Cut is an older concept but remains one of the most useful tools for predicting how the geometry will evolve. Three reference cases:

* '''Cut greater than Collision Course''' — your nose is in front of the bandit. Over time, TA decreases and Lateral Separation decreases. You are closing the geometry aggressively.
* '''Cut equal to Collision Course''' — the magic case. TA is captured: it does not change. Lateral Separation decreases. If co-altitude, you will eventually collide.
* '''Cut less than Collision Course (Zero-Cut / Parallel)''' — your nose points at the bandit's reciprocal. TA increases over time. Lateral Separation is captured: it does not change.
* '''Cut-Away''' — your nose points away from the bandit entirely. Both TA and Lateral Separation increase. Used to build angles or lateral room.

==== Degrees to Go (DTG) / Heading Crossing Angle (HCA) ====
DTG is the number of degrees the fighter needs to turn to be '''parallel''' to the bandit's flight path. It is the supplementary angle of Cut. A useful memory aid: ''Degrees to Go — where? Parallel.''

==== Lateral Separation (LS) ====
Lateral Separation is the perpendicular distance between the two flight paths. It determines how much maneuvering room exists for a conversion. It is approximated as:
LS (ft) = TA × SR × 100
Where SR is slant range in nautical miles. Lateral Separation matters most when planning a stern conversion or assessing whether a shot is geometrically viable.

==== Direction of Passage (DOP) ====
DOP describes the direction the bandit would cross your flight path if neither aircraft maneuvered. Called as left-to-right or right-to-left. Useful shorthand for building SA quickly.

==== Slant Range (SR) ====
[[File:SlantRange.webp|thumb|500x500px|center]]
The straight line-of-sight distance between the two aircraft in three-dimensional space. On the F-16 FCR this is the range displayed on the scope.

=== Pursuit Types ===
[[File:Pursuit.webp|thumb|700x700px|center]]
The type of pursuit describes where your nose is pointing relative to the target.
{| class="wikitable" style="width:100%;"
!Pursuit Type
!Nose Position
!Common Use
|-
|'''Lead Pursuit'''
|In front of the target
|Collision Course, gun employment from RQ
|-
|'''Pure Pursuit'''
|Directly at the target
|Simple conversions; commonly overused by new pilots
|-
|'''Lag Pursuit'''
|Behind the target
|Geometry management, WVR maneuvering
|}

== BFM III — Offensive BFM ==
Offensive BFM begins with you in a position of advantage. The bandit is somewhere in your forward hemisphere and your job is to convert that advantage into a weapons solution before he can deny it.

=== The Turn Circle ===
Every maneuvering aircraft has a turn circle, the circular path it is flying at any given moment. To employ weapons on the bandit you must get inside his turn circle, or at minimum align with it. Getting outside means you are turning wider than he is and falling behind.

The cue for turn circle entry is a high LOS rate (see below). As you approach the edge of the bandit's circle the bandit will begin moving rapidly across your field of view. Turn at that moment. Turn too early and you cross inside his radius, giving him a reversal opportunity. Turn too late and you end up outside his circle with AA too high to employ.

=== Line of Sight Rate ===
Line of Sight (LOS) rate is the speed at which the bandit moves across your field of view. It is one of the most important diagnostic tools in BFM and appears throughout offensive, defensive, and high aspect engagements.

A high LOS rate means the bandit is moving quickly across your canopy. A low or zero LOS rate means the bandit is stable relative to your nose. LOS rate tells you two things:

* '''Where are you relative to the bandit's turn circle'''? A sudden spike in LOS rate signals that you have reached the edge of his turn circle. Inside his circle, LOS rate is high. Outside it, LOS rate is low.
* '''What is the Geometry doing?''' Aft LOS movement means the bandit is drifting toward your 6; forward LOS movement means he is drifting toward your 12. The direction and speed of that drift tells you whether the geometry is improving or deteriorating.

Learning to read LOS rate is not an instrument skill. It is a visual habit and requires practice.

=== The Control Zone ===
The control zone is the offensive firing position, located in the bandit's rear quarter. From the control zone you have sufficient range for weapon employment, a manageable aspect angle, and controlled closure.

Getting into the control zone is not enough. You must '''assess''' before employing. The assessment uses the '''Rule of Threes''':
{| class="wikitable" style="width:100%;"
!Parameter
!Value
!Notes
|-
|Range
|~3,000 ft
|Read from HUD or FCR
|-
|Aspect Angle
|≤30°
|Draw an imaginary box around the bandit — square silhouette means ~30° AA
|-
|Closure
|Steady and controlled
|Not increasing, not zero
|}
All three must be satisfied before moving in for a gun solution. If any are not met, reposition first.

=== Repositions ===
Repositions are controlled adjustments to fix range, closure, or aspect problems from the control zone.

==== Lead Reposition ====
Used when the bandit is pulling away and range is increasing. Pull lead pursuit to close the gap. Do not overshoot.

==== Lag Reposition ====
Used when closure is too high. Pull lag pursuit to slow closure and improve aspect. The bandit will drift aft in your field of view. Reassess once closure is controlled.

==== Ease Reposition ====
Used when range and closure are acceptable but aspect is slightly high. Ease back on the stick to widen your turn circle slightly. AA will decrease as the geometry opens. Once AA is acceptable, resume the original pull and reassess. This is a small correction — if aspect is significantly high, use a lag reposition instead.

=== Visual Aspect Estimation ===
Without looking at instruments, AA can be estimated by the shape of the bandit's silhouette:

* '''Rectangle''' (fuselage longer than wingspan) means AA is above 30°, too high for a clean gun solution
* '''Square''' (fuselage approximately equal to wingspan) means AA is approximately 30°, Rule of Threes satisfied
* '''Narrowing toward a point''' means AA is near 0°, pure tail-aspect

This visual check is faster than any instrument cross-check in a close turning fight.

=== Weapon Employment ===

==== Heat Seeker (FOX-2) ====
A valid FOX-2 shot requires a confirmed seeker tone and AA within the missile's acquisition envelope, typically ≤60° for rear-quarter shots. Do not fire without tone. At significant AA the seeker may struggle to acquire, so use a lag or ease reposition to reduce AA before attempting the shot.

==== Guns ====
A valid gun solution requires the Rule of Threes to be fully satisfied with the pipper placed on the bandit. In a turning fight this requires lead pursuit. Your nose must be ahead of the bandit's projected path, not pointed at him. The amount of lead required varies with range and closure rate.

A tracking shot requires the pipper to remain on the bandit for a sustained period. A snapshot is a momentary pipper-on opportunity taken when it presents itself, lower probability but sometimes the only option available.

=== The Quarter Plane ===
The quarter plane is a last-resort maneuver used when closure rate has become dangerously high and an overshoot is imminent. It is not a reposition.

The cue to act is approximately 1,000 ft of range, at which point the bandit's wingspan will fill roughly half the EEGS funnel on the HUD.

Execution:

# Roll wings level with the horizon
# Set idle power
# Pull maximum performance up and out of the bandit's plane of motion

This arrests closure and separates you vertically from the bandit's plane. Once clear, roll back into a turn toward the bandit and reassess. The quarter plane costs significant energy and altitude. Use it only when nothing else will prevent the overshoot.

=== Common Errors ===
{| class="wikitable" style="width:100%;"
!Error
!Consequence
!Correction
|-
|Late turn circle entry
|End up outside the bandit's circle with AA too high
|Watch for the LOS rate spike and turn at that moment
|-
|Early turn circle entry
|Cross inside bandit's radius, give him a reversal picture
|Wait for the LOS rate spike
|-
|Firing without satisfying Rule of Threes
|Low probability shot
|Reposition first, assess before employing
|-
|Pure pursuit at significant AA
|Missile must curve hard, degraded effectiveness
|Use CC or LC geometry for missile employment
|-
|Uncontrolled closure
|Overshoot, offensive position lost
|Use lag reposition early, quarter plane as last resort
|-
|Spending energy without reason
|Slow speed, large radius, advantage lost
|Maintain AB, only pull above sustained rate for a specific reason
|}

== BFM IV — Defensive BFM ==
This part is based on [https://www.youtube.com/playlist?list=PLd5Qdmhmp3Y5-SDJjOzuUqV3m3mmuieTQ this] video series by [https://www.youtube.com/@TheOpsCenterByMikeSolyom The Ops Center by Mike Solyom].

The objectives of defensive BFM are, in order of priority: survive, deny the bandit a weapons solution, and create the conditions for a role reversal. Survival is the primary objective. A fighter that remains in the fight presents a continuous problem to the attacker — he must maintain focus on the defender, consuming energy and attention that could otherwise be used offensively. Every second the defender survives is a second for supporting elements to close.

=== The Defensive Gameplan ===
The foundation of defensive BFM is the sustained rate turn. The defender should establish and maintain best sustained turn rate as the default gameplan. This accomplishes two things simultaneously: it maximizes the defender's turn performance for the duration of the engagement, and it preserves energy for subsequent maneuvering.

Deviation from the sustained rate gameplan should only occur when a specific threat — an imminent gun or missile shot — requires a more aggressive response. Expending energy prematurely leaves the defender slow, with a large turn radius and reduced options.

=== Cross-Check Discipline ===
In defensive BFM the pilot's attention is predominantly outside the cockpit on the bandit. However, three parameters must be periodically cross-checked throughout the engagement:
{| class="wikitable" style="width:100%;"
!Parameter
!Significance
|-
|'''Lift Vector'''
|Determines plane of motion and available turn rate
|-
|'''G'''
|Confirms correct turn performance is being applied
|-
|'''Airspeed'''
|Identifies energy state; confirms sustained rate speed is maintained
|}
The cross-check must not interrupt tally on the bandit for extended periods. Brief instrument scans returning immediately to visual are the correct technique. Loss of tally in a defensive engagement is a significant threat to survival.

=== Altitude Management ===
Altitude is a reserve of potential energy. Trading altitude for airspeed in a defensive turn temporarily increases available turn rate above the Ps = 0 line by lowering the lift vector below the horizon. This option is only available until the floor is reached. At that point the defender is constrained to a level sustained rate turn and loses the altitude trading option entirely.

=== Reading the Bandit's Intentions ===
The defender must continuously assess the bandit's pursuit course to anticipate his next action. The pursuit course is read visually:
{| class="wikitable" style="width:100%;"
!Pursuit Course
!Visual Cue
!Likely Intent
|-
|'''Pure pursuit'''
|Narrow nose-on profile
|Missile shot setup; seeker acquisition in progress
|-
|'''Lead pursuit'''
|Bandit's belly visible; nose pulled ahead of defender
|Gun shot imminent
|-
|'''Lag pursuit'''
|Top of bandit's aircraft visible; aft LOS movement
|Controlling closure; repositioning for follow-on attack
|}
Transition from lag to pure to lead is the signature sequence of an impending gun attack. Recognition of this sequence is the primary defensive cross-check task outside the cockpit.

Range assessment is equally important. The bandit's size relative to your field of view gives a continuous indication of closure. A bandit that fills a significant portion of your view is inside 2,500 ft and approaching gun parameters.

=== Maneuvers ===

==== Tighten Down ====
The tighten down is the first and most conservative response to a bandit closing into gun parameters. It is executed by increasing back pressure on the stick while already in a sustained rate turn, transitioning from sustained rate to a higher instantaneous turn rate.

The tighten down achieves two simultaneous effects. First, it rotates the defender's vulnerable rear quarter away from the attacker, driving the bandit outside the weapon employment zone. Second, the sudden airspeed reduction caused by the increased G creates a high closure rate problem for the attacker, forcing him to reposition to satisfy the Rule of Threes. This repositioning produces aft LOS movement and potentially a reversal picture.

The tighten down is an energy expenditure. It should be released once the immediate threat is defeated, returning to slightly below sustained rate and allowing AB to restore the energy state.

==== Out-of-Plane Maneuver (OOP) ====
The out-of-plane maneuver removes the defender from the attacker's plane of motion, forcing the attacker to reset his geometry. In a sustained rate turn both aircraft are operating in approximately the same plane of motion. Moving out of that plane disrupts the attacker's sight picture and solution geometry.

Execution:

# Unload the aircraft — reduce back pressure to below 1G
# Reposition the lift vector off the bandit, above or below his plane of motion
# Apply smooth back pressure to establish a turn in the new plane of motion
# Allow sufficient time for the aircraft to develop movement in the new plane before any follow-on maneuver
# Assess LOS rate and bandit pursuit course in the new plane

The unloaded roll is critical. Rolling while pulling G consumes energy without producing useful turning room. The unload must precede the roll.

Upon establishing the new plane of motion, assess for a reversal opportunity. If high aft LOS rate combined with high HCA and close range is observed, a reversal may be executed. Otherwise, continue maneuvering in the new plane.

==== Jink ====
The jink is a last-resort maneuver executed when a gun shot is assessed as imminent and neither the tighten down nor the OOP has defeated the attacker's solution. It combines elements of both into a single aggressive sequence designed to spoil the attacker's plane of motion and create a closure problem simultaneously.

Execution:

# Set throttle to idle
# Unload the aircraft
# Position the lift vector below the bandit
# Apply maximum onset rate back pressure and hold until aerodynamic buffet onset

The resulting airspeed reduction is severe and deliberate. The attacker is presented with a sudden, unforecast closure rate and a simultaneous change in plane of motion. If the attacker does not immediately reposition he will overshoot. If he does reposition, aft LOS movement will develop and a reversal picture may emerge.

If a reversal picture does not present after the first jink, execute a second jink to the opposite side:

# Idle power maintained
# Unload
# Reposition lift vector to the opposite side of the bandit
# Maximum onset back pressure

Continue until the attacker is forced into lag or a reversal picture develops. The jink sequence trades altitude at a high rate. Do not initiate within 1,500 to 2,000 ft of the floor. The jink is the highest energy expenditure maneuver in defensive BFM and is reserved strictly for imminent gun shot situations.

=== The Reversal ===
A reversal is a turn at an opportune moment in the opposite direction, executed to transition from a defensive position to a neutral or offensive one. Correctly timed, a reversal exploits the attacker's angles and closure to reposition the defender onto an advantageous bearing. Incorrectly timed, it degrades the defender's position further.

The opportunity for a correct reversal is rare and may only be available for a few seconds. More often than not a reversal will degrade the situation rather than improve it. Patience and recognition of the correct picture are essential.

==== The Reversal Picture ====
The reversal picture is the combination of visual conditions that indicate a reversal opportunity exists:

* High heading crossing angle (HCA), combined with
* Close range, and or high aft LOS rate

A practical assessment question: ''does it appear that the bandit will cross behind my tail with minimal assistance from me?'' If the answer is yes, execute. If there is any doubt, do not reverse. A premature reversal presents the attacker with a stable, predictable target and makes his job easier.

==== Execution ====
The reversal is executed using an unloaded roll:

# Reduce back pressure to unload the aircraft
# Roll to the opposite direction
# Resume back pressure once established in the new turn
# Shift visual focus to the opposite side to regain tally on the bandit

Lift vector placement after the reversal depends on range. At close range, position the lift vector above or below the bandit to build turning room before pulling into his plane of motion. At greater range, place the lift vector directly on the bandit.

A successful reversal will typically result in a scissors — a neutral position from which either pilot may gain an advantage. This is a significant improvement over the defensive.

=== Maneuver Selection Summary ===
{| class="wikitable" style="width:100%;"
!Situation
!Maneuver
!Notes
|-
|Bandit in lag or pure pursuit, not yet in gun parameters
|Sustained rate turn
|Conserve energy; maintain cross-check
|-
|Bandit transitioning to lead pursuit, gun shot developing
|Tighten down
|First response; moderate energy cost
|-
|Tighten down insufficient; bandit maintaining solution
|Out-of-plane maneuver
|Disrupts attacker geometry; assess for reversal
|-
|Gun shot imminent; no other option
|Jink
|Last resort; high energy cost; do not use prematurely
|-
|Reversal picture present
|Reversal
|Execute with unloaded roll; if in doubt, do not reverse
|}

== BFM V — High Aspect BFM ==
This part is based on [https://www.youtube.com/playlist?list=PLd5Qdmhmp3Y5-SDJjOzuUqV3m3mmuieTQ this] video series by [https://www.youtube.com/@TheOpsCenterByMikeSolyom The Ops Center by Mike Solyom].

High aspect BFM occurs when neither aircraft has a positional advantage at the merge. Both aircraft are nose-to-nose and the engagement begins from a neutral position. The name comes from the fact that at the merge, both aircraft are presenting high aspect to each other.

There are two reasons a pilot ends up in a high aspect fight. Either the bandit turns his nose toward you at the conclusion of a BVR intercept, or a BFM error led to the loss of an offensive position. The response is the same in either case.

=== The Lead Turn ===
The lead turn is the single most important concept in high aspect BFM. It is executed before the merge and determines the starting position of the fight.

Rather than waiting until the bandit's 3-9 line to begin turning — which produces a neutral merge — the pilot initiates the turn early. This builds an angular advantage before the first pass. At the sustained turn rate of the F-16, every additional second of turn produces more than 10° of angular advantage that the bandit must make up. Even two seconds of early turning can produce an advantage that a bandit in the same aircraft cannot recover from.

The lead turn cue is a rapidly increasing LOS rate from 11 to 10 o'clock for a left-side pass, or 1 to 2 o'clock for a right-side pass. This is the correct moment to turn. Turning too late leaves you behind the bandit with an energy problem. Turning too early gives the bandit a reversal picture.

If the lead turn is started too late there is little that can be done — accept the problem and manage it. If the lead turn is started too early, ease off the G momentarily until the bandit's LOS rate resumes, then resume the pull.

When executed correctly, the lead turn produces a '''stern conversion''' — the pilot arrives at the bandit's six o'clock within gun range without requiring further maneuvering.

=== Turning Room ===
Turning room is the separation between the two aircraft that is available to turn into. It can be built vertically or laterally, but never to the outside of the bandit's turn circle — floating outside gives the bandit more time and reduces the angular advantage gained in the lead turn.

The overriding factor when deciding whether to climb or descend is ease of tally on the bandit, and denying the bandit tally on you. Use the environment — put the bandit against a cloud, get between the bandit and the sun, avoid staying at the same altitude as the bandit. Tally is survival.

Vertical turning room comes with an energy cost that must be accounted for. A descent toward the bandit will add approximately 100 KCAS at the merge. A climb will cost approximately 100 KCAS. If this is not managed, the pilot will either overshoot the bandit or arrive too slow to sustain a competitive turn rate. Adjust entry speed before the turn-in accordingly. The fastest way to build speed without turning is to unload the aircraft — do this in the seconds between the turn-in and the merge.

Lateral turning room is always built to the inside of the bandit's turn circle. There is no useful lateral room to the outside.

=== Determining Fight Geometry ===
At the merge, the direction the bandit turns determines the geometry of the fight. '''The last aircraft to turn decides whether the engagement becomes a one-circle or two-circle fight.''' This is a deliberate choice — a pilot who executes a lead turn gives up the ability to choose the fight geometry, because the bandit turns last. The lead turn advantage is generally worth this tradeoff.

* '''Bandit turns toward you''' → two-circle fight. Both aircraft chase each other's tails. Ground track resembles two separate circles.
* '''Bandit turns away from you''' → one-circle fight. Both aircraft circle back toward each other for a second nose-to-nose pass. Ground track resembles a single circle.

Identifying which geometry has been established requires only one visual check: if the bandit is nose-to-tail relative to you, it is a two-circle fight. If it is nose-to-nose, it is a one-circle fight.

=== Losing Tally ===
Losing visual on the bandit in a turning fight is dangerous. Two rules apply immediately:

'''Do not fly straight and level while searching.''' Straight flight makes the defender's job trivial. Maintain the turn at all times.

'''Search along the turn circle.''' The bandit's most likely position is in the high-probability kill zone behind and above — the high-Pk WEZ. When the area behind you is clear, scan upward along the turn circle. The bandit will be somewhere along that arc if still engaged.

== BFM V-A — Two-Circle Fight ==
A two-circle fight begins when the bandit turns away from you at the merge. Both aircraft are now chasing each other's tail, producing a ground track that resembles two separate circles. The fight is a turn rate contest — the aircraft that can sustain a higher turn rate will eventually work its nose onto the the tail of the other.

=== The Default Gameplan ===
In a two-circle fight, maintain best sustained turn rate. Do not deviate from this. The temptation to pull into lead or pure pursuit to force a quick shot will produce a predictable result: range closes rapidly, aspect increases to beam or beyond, and the bandit drifts aft on the canopy. The fight resets to where it started. This yo-yoing effect will repeat indefinitely if the pilot keeps chasing the shot prematurely. Stay on the sustained rate turn and let the geometry develop.

=== Reading the Fight ===
As both aircraft complete the first circle, the bandit's position on the canopy provides continuous information about how the fight is developing. Three conditions are possible:
{| class="wikitable" style="width:100%;"
!Visual Cue
!Assessment
!Action
|-
|Bandit moving forward on the canopy, aspect stagnant or decreasing
|Winning — angular advantage is building
|Continue sustained rate turn; prepare for lead turn at next merge
|-
|Bandit moving forward on the canopy, aspect increasing toward nose-to-nose
|Neutral — neither pilot has an advantage
|Assess energy state; choose one-circle or two-circle at the next merge
|-
|Bandit's motion stagnant or drifting aft, bandit showing narrow nose-on profile
|Losing — bandit is gaining angular advantage
|Check G — increase to moderate buffet; if insufficient, transition to defensive BFM
|}
When neutral cues are present, the decision between one-circle and two-circle at the next merge is based on energy state. Above approximately 350 KCAS the aircraft has sufficient energy for a sustained rate two-circle game plan. Below that, the turn radius is already small enough that a one-circle minimum radius game plan is more effective.

=== Turn Circle Extension (TCX) ===
Even with a turn rate advantage, the two turn circles will not be perfectly aligned after the first pass. The bandit will yo-yo up and down the canopy as the circles overlap and separate. Forcing a shot during this phase produces the same premature high-aspect result described above. The solution is the turn circle extension.

A TCX is two to three seconds of easing off the G — not a full unload, just a reduction in back pressure that allows the center of the turn circle to shift. This repositions the turn circle to better align with the bandit's. It is not a straight line, though it can be. It is simply a brief relaxation of the sustained rate pull followed by resumption.

The cue to extend is the bandit sliding into the assessment window — approximately 45 to 60 degrees AA — combined with aft LOS movement. This is the same assessment window used in offensive BFM. If the bandit's aspect is above 30 degrees, ease back on the G. That easing is the TCX.

Timing matters. A TCX initiated too early shifts the turn circle sideways without closing the gap. A TCX initiated too late pushes both circles further apart. The correct moment is when the bandit is in the assessment window with aft LOS developing.

Multiple TCX corrections should be expected before the turn circles align. The manual notes that this process can require between 500 and 1,000 degrees of turning — approximately three times around the circle. Do not force it. Once the circles align, the fight transitions naturally into offensive BFM.

=== Regaining Tally ===
If tally is lost during a two-circle fight, apply the rules from the fundamentals section: maintain the turn and scan along the turn circle upward through the high-Pk zone. In a nose-to-tail fight the bandit will be somewhere along that arc. Do not level the wings.

== BFM V-B — One-Circle Fight ==
A one-circle fight begins when the bandit turns toward you at the merge. Both aircraft are now circling back to meet each other in a second nose-to-nose pass. The ground track resembles a single circle. Unlike the two-circle fight where turn rate is the deciding factor, the one-circle fight is a '''turn radius contest'''.

=== Why Radius and Not Rate ===
In a two-circle fight, a smaller radius produces no advantage because both aircraft are always on opposite sides of their respective circles and never converge to a point where the nose can be brought to bear. Turn rate determines who gets there first.

In a one-circle fight the geometry is different. Both aircraft are converging on the same point — the next merge. The aircraft with the smaller radius gets its nose pointed at the bandit sooner, creating an opportunity for a lead turn or even a shot before the second pass. The aircraft with the larger radius arrives late and with less angular advantage.

=== The Minimum Radius Gameplan ===
To minimize turn radius in the F-16, pull enough G to reach a moderate aerodynamic buffet. The buffet indicates the aircraft is operating above the sustained turn rate and approaching the maximum lift line on the EM diagram — the region of minimum radius. Do not stall. A moderate buffet is the target.

The F-16 does not have an audio cue for this in DCS. Use the physical buffet as the indicator. If nothing is shaking, more G is needed.

=== Reading the Fight ===
As both aircraft come around the circle toward the second merge, the bandit's position on the canopy indicates whether the radius fight is being won or lost:
{| class="wikitable" style="width:100%;"
!Visual Cue
!Assessment
!Action
|-
|Bandit moving forward on the canopy, aspect stagnant or decreasing, top of bandit's aircraft visible
|Winning — angular advantage is building
|Execute lead turn at next merge to convert to offensive BFM
|-
|Bandit near or inside the canopy, nose pointed at you, bandit showing narrow nose-on profile
|Neutral — neither pilot has significant advantage
|Assess energy state; choose fight geometry at next merge
|-
|Bandit's motion stagnant or drifting aft, bandit showing narrow nose-on profile
|Losing — bandit is gaining the angular advantage
|Increase G to moderate buffet; if insufficient, transition to defensive BFM
|}

=== At the Next Merge ===
A one-circle fight always leads to a second merge. Three outcomes are possible at that merge:

* '''Another one-circle''' — bandit turns away again. Continue minimum radius game plan.
* '''Two-circle''' — bandit turns toward you. Transition to sustained rate game plan.
* '''Scissors''' — both aircraft begin reversing rapidly on each other. See below.

The decision between one-circle and two-circle at the second merge is based on energy state. Above approximately 350 KCAS the aircraft has enough energy for a sustained rate two-circle game plan. Below that, the turn radius is already small and one-circle minimum radius is more effective. Do not be indecisive — the last fighter to turn determines the fight geometry. Commit to a direction.

=== The Scissors ===
The scissors develops when both aircraft are reversing rapidly on each other and neither can establish a clean angular advantage. Both aircraft are within the other's turn circle. The ground track resembles scissor blades opening and closing.

The gameplan in a scissors is identical to the one-circle minimum radius game plan: minimize forward ground track by minimizing turn radius. Pull to moderate buffet, place the lift vector on the bandit, and select max afterburner. The aircraft with the smaller forward ground track will eventually fall behind the other and transition to an offensive position.

One-circle fights and scissors consume energy at a high rate due to the sustained high-G maneuvering required. Be aware of airspeed throughout — winning the radius fight but arriving slow leaves the bandit with an energy advantage that may be unrecoverable.

=== Losing the One-Circle ===
If the bandit is gaining the angular advantage, the symptoms are: the bandit's motion on the canopy goes stagnant or drifts aft, and the bandit's profile narrows to a pure pursuit nose-on silhouette. This is the bandit executing the same minimum radius game plan successfully.

When losing cues are present, first confirm G is sufficient — pull to moderate buffet if not already there. If the situation continues to deteriorate, transition to defensive BFM immediately. The one-circle fight has become a defensive situation and should be treated as one.

Never stop maneuvering. A neutral position is always recoverable.

Procedures/78th/A2A/BFM

2026-05-23T17:40:13Z

Niknam3: /* Losing Tally */

== BFM I — Energy and the EM Diagram ==
This part is based on [https://youtube.com/playlist?list=PLd5Qdmhmp3Y5-SDJjOzuUqV3m3mmuieTQ&si=FNdYqWagls5zNQjG this] video series by [https://www.youtube.com/@TheOpsCenterByMikeSolyom The Ops Center by Mike Solyom].

=== Energy ===
Every decision in a dogfight is an energy decision. An aircraft's energy state is expressed primarily as airspeed and altitude. The faster and higher you are, the more potential energy you have to maneuver. Energy buys turn rate, separation, and shot opportunities. Waste Energy and you will loose.

The First principle of BFM is simple: '''build energy and save it until you have a reason to spend it.''' That reason is either a shot on the bandit or denying a shot on yourself. If neither opportunity exists, maintain or build energy. Do not waste.

=== The Energy Maneuverability (EM) Diagram ===
The EM diagram is the definitive tool for understanding how an aircraft performs in a turning fight. It maps turn rate against airspeed for a specific set of parameters: aircraft weight, altitude, throttle setting, and configuration. Every number on the chart is only valid for those exact conditions.

For the F-16C in DCS the reference diagram is: '''Full AB · Clean · Sea Level · 12300 kg'''
[[File:F16 EM Diagram.png|center|frameless|945x945px]]

Key performance figures from this diagram:
{| class="wikitable" style="width:100%;"
!Parameter
!Value
!Condition
|-
|Max instantaneous turn rate
|24°/s
|393 KCAS
|-
|Max sustained turn rate
|18°/s
|523 KCAS
|-
|Min sustained turn radius
|1,462 ft
|246 KCAS
|-
|Min turn radius
|1,399 ft
|169 KCAS
|}
'''Note:''' The F-16's G-limiter schedule is not fully reflected in the upper portion of this diagram. Maximum instantaneous performance may be lower than indicated in practice. The DCS implementation of the F-16 Flight Model also severely limits the F16's Sustained turn rate.

=== Reading the Diagram ===

==== The Axes ====

* '''Horizontal axis''': airspeed in Mach (lower) and KCAS (higher)
* '''Vertical axis''': turn rate in degrees per second (°/s)

Moving up on the chart means higher turn rate.

==== The Lines ====
'''The Envelope (red)'''

The outer boundary of what the aircraft can physically do. It is shaped by three limits:

* '''Structural G limit''' is the maximum G the airframe can sustain; forms the upper-right boundary
* '''Angle of attack limit''' — the stall boundary; forms the left boundary
* '''Speed limit (Vmax)''' — the right-side boundary (going supersonic will nearly always kill both your turn rate and radius and is not desirable)

No matter what the pilot does, the aircraft cannot operate outside the red envelope.

'''Turn Radius Lines (brown)'''

These straight lines show turn radius in feet at any given point on the chart. Moving up and left gives a smaller radius.

'''G-Load Lines (gray)'''

Indicate how many G must be pulled to reach that point on the chart. To achieve a Instantaneous Turn rate of 20° at 400CAS the aircraft needs to pull about 7.5G

'''Ps Lines (solid black)'''

Specific excess power lines are the most important lines on the chart. They show whether the aircraft is gaining or losing energy at any given combination of speed and G.

* '''Ps = 0''' — the aircraft is exactly maintaining its energy state. This is the sustained turn line. The maximum turn rate achievable while sustaining speed and altitude sits on this line.
* '''Ps > 0 (positive numbers)''' — the aircraft is gaining energy. It can accelerate or climb while maintaining the current turn.
* '''Ps < 0 (negative numbers)''' — the aircraft is losing energy. It is spending saved energy for extra turn performance. This is temporary and cannot be maintained indefinitely.

Anything above the Ps = 0 line is an energy expenditure. The higher above it you go, the faster you bleed speed.

=== Corner Velocity ===
Corner velocity is the airspeed at which the aircraft achieves its maximum instantaneous turn rate — the peak of the envelope. For the F-16C at sea level this occurs at '''401CAS''', producing '''24°/s'''.

For the maximum Instantaneous turn the DCS Flight model requires the pilot to pull 9G and decent with over 1200ft/s which is in any way not sustainable unless the a significant amount of Altitude has been built up. DO NOT use this unless you need to safe your life.

=== Sustained Turn Rate ===
The sustained turn rate is the maximum turn rate the aircraft can maintain indefinitely without losing speed or altitude. For the F-16C at sea level this is '''18°/s @ 523 KCAS'''.

In practice, sustained operations happen on or near the Ps = 0 line. The pilot's job is to find and hold that point. Sadly in DCS to hold and maintain that line is impossible. To Fly Perfect Sustained Turn Rate you need to pull 9G in full afterburner. You will know that you hit the perfect speed if, at max pull, in a level turn, the Jet neither gains nor looses Max energy.

A sustained 9G turn will black out any pilot. To Compensate the Pilot should fly slighly below the Optimal Speed allowing for higher turn rate while loosing a small amount of energy. Once the Jet reaches around 70-80 KTS below optimal speed the pilot should reduce the pull to about 6G for maximum recovery speed. While only pulling 6G the jet will gain energy fast. Once back at optimal speed continue to pull 9G.

If you overshoot the Optimal Speed you will notice that even at max pull the aircraft is still gaining airspeed. In this case execute a spiral climb to return back to Optimal Speed while utilizing the excess Energy.

If you undershoot the Optimal Speed you will notice that at max pull the aircraft is loosing airspeed fast. Either Reduce pull back to 6G until at better speed or trade altitude for extra Energy.

=== Instantaneous vs Sustained ===
{| class="wikitable" style="width:100%;"
!
!Instantaneous
!Sustained
|-
|'''Definition'''
|Maximum turn rate achievable at any moment
|Maximum turn rate maintainable indefinitely
|-
|'''F-16C value (sea level)'''
|24°/s @ 393 KCAS
|18°/s @ 523 KCAS
|-
|'''Energy cost'''
|High: Far above Ps = 0, bleeding speed fast (expect around 50kts/s)
|None if optimally flown on Ps = 0 line
|-
|'''When to use'''
|Short bursts for a shot opportunity or to deny a shot
|Default gameplan in any sustained turning fight
|}
Instantaneous turn rate is spending saved energy. It is a powerful tool but a temporary one. A pilot who pulls to instantaneous continuously will bleed to low speed, and lose the fight on energy.

=== How Altitude and Stores Affect the Diagram ===
The reference diagram is for sea level, clean, full AB. Both altitude and external stores degrade performance:

* '''Altitude''': thinner air reduces lift and engine thrust. Turn rate and sustained performance both decrease. The same airspeed produces a larger turn radius at altitude.
* '''Weight:''' Fuel or Stores will both make you heavy. The heavier you are the worse the performance. As you burn fuel the optimum Sustained turn rate Speed will decrease into manageable Levels.

=== Practical Application ===
In the fight itself: '''treat energy like money.''' Build it, save it, and spend it only when the return is worth it. A valid shot, or surviving by denying the adversary a shot oportunity. Spending energy for no tactical gain is a losing strategy.

== BFM II — Angles and Geometry ==

=== Angles and Definitions ===

[[File:Angles.webp|frameless|715x715px]]

==== Antenna Train Angle (ATA) ====
The ATA is the position of the bandit left or right of the fighter's nose on the radar display. ATA 0 means the target is dead ahead. ATA 30R means the target is 30° to the right of your nose.

The ATA is a property of your own aircraft's orientation. It changes when '''you''' maneuver. It does not change instantaneously when the bandit maneuvers.

On the F-16 FCR, ATA is read on the horizontal axis.

==== Target Aspect (TA) ====
Target Aspect, not to confuse with Aspect Angle is how the bandit appears from your perspective. Specifically, the angle from the bearing line of the fighter to the '''nose''' of the target. It describes which part of the bandit you are looking at.

* TA 0 —you are looking at the bandit's nose (head-on)
* TA 90 — you are looking at the bandit's side
* TA 180 — you are looking at the bandit's tail (pure stern)

TA is signed left or right depending on which side of the bandit you are observing.

Unlike ATA, Target Aspect is '''entirely determined by the bandit's heading''' relative to the bearing line between you. You cannot change it instantaneously. You can only influence it over time by maneuvering to change the geometry.

The F-16 does not display TA directly. It displays the '''Aspect Angle (AA)''', which is the supplementary angle of TA (AA = 180° − TA). A tail-aspect shot has AA 0; a head-on shot has AA 180.
[[File:AAvsTA.webp|thumb|600x600px]]
Common TA labels used in brevity:
{| class="wikitable"
!TA
!AA
!Label
|-
|0°–30°
|150°–180°
|Hot
|-
|31°–75°
|105°–149°
|Flank
|-
|76°–110°
|70°–104°
|Beam
|-
|111°–150°
|30°–69°
|Drag
|-
|151°–180°
|0°–29°
|Cold
|}

==== Cut ====
Cut is the angle from the '''Fighter Heading (FH)''' to the '''Bandit Reciprocal (BR)'''. It describes where your nose is pointing relative to the bandit's course.

Cut is an older concept but remains one of the most useful tools for predicting how the geometry will evolve. Three reference cases:

* '''Cut greater than Collision Course''' — your nose is in front of the bandit. Over time, TA decreases and Lateral Separation decreases. You are closing the geometry aggressively.
* '''Cut equal to Collision Course''' — the magic case. TA is captured: it does not change. Lateral Separation decreases. If co-altitude, you will eventually collide.
* '''Cut less than Collision Course (Zero-Cut / Parallel)''' — your nose points at the bandit's reciprocal. TA increases over time. Lateral Separation is captured: it does not change.
* '''Cut-Away''' — your nose points away from the bandit entirely. Both TA and Lateral Separation increase. Used to build angles or lateral room.

==== Degrees to Go (DTG) / Heading Crossing Angle (HCA) ====
DTG is the number of degrees the fighter needs to turn to be '''parallel''' to the bandit's flight path. It is the supplementary angle of Cut. A useful memory aid: ''Degrees to Go — where? Parallel.''

==== Lateral Separation (LS) ====
Lateral Separation is the perpendicular distance between the two flight paths. It determines how much maneuvering room exists for a conversion. It is approximated as:
LS (ft) = TA × SR × 100
Where SR is slant range in nautical miles. Lateral Separation matters most when planning a stern conversion or assessing whether a shot is geometrically viable.

==== Direction of Passage (DOP) ====
DOP describes the direction the bandit would cross your flight path if neither aircraft maneuvered. Called as left-to-right or right-to-left. Useful shorthand for building SA quickly.

==== Slant Range (SR) ====
[[File:SlantRange.webp|thumb|500x500px|center]]
The straight line-of-sight distance between the two aircraft in three-dimensional space. On the F-16 FCR this is the range displayed on the scope.

=== Pursuit Types ===
[[File:Pursuit.webp|thumb|700x700px|center]]
The type of pursuit describes where your nose is pointing relative to the target.
{| class="wikitable" style="width:100%;"
!Pursuit Type
!Nose Position
!Common Use
|-
|'''Lead Pursuit'''
|In front of the target
|Collision Course, gun employment from RQ
|-
|'''Pure Pursuit'''
|Directly at the target
|Simple conversions; commonly overused by new pilots
|-
|'''Lag Pursuit'''
|Behind the target
|Geometry management, WVR maneuvering
|}

== BFM III — Offensive BFM ==
Offensive BFM begins with you in a position of advantage. The bandit is somewhere in your forward hemisphere and your job is to convert that advantage into a weapons solution before he can deny it.

=== The Turn Circle ===
Every maneuvering aircraft has a turn circle, the circular path it is flying at any given moment. To employ weapons on the bandit you must get inside his turn circle, or at minimum align with it. Getting outside means you are turning wider than he is and falling behind.

The cue for turn circle entry is a high LOS rate (see below). As you approach the edge of the bandit's circle the bandit will begin moving rapidly across your field of view. Turn at that moment. Turn too early and you cross inside his radius, giving him a reversal opportunity. Turn too late and you end up outside his circle with AA too high to employ.

=== Line of Sight Rate ===
Line of Sight (LOS) rate is the speed at which the bandit moves across your field of view. It is one of the most important diagnostic tools in BFM and appears throughout offensive, defensive, and high aspect engagements.

A high LOS rate means the bandit is moving quickly across your canopy. A low or zero LOS rate means the bandit is stable relative to your nose. LOS rate tells you two things:

* '''Where are you relative to the bandit's turn circle'''? A sudden spike in LOS rate signals that you have reached the edge of his turn circle. Inside his circle, LOS rate is high. Outside it, LOS rate is low.
* '''What is the Geometry doing?''' Aft LOS movement means the bandit is drifting toward your 6; forward LOS movement means he is drifting toward your 12. The direction and speed of that drift tells you whether the geometry is improving or deteriorating.

Learning to read LOS rate is not an instrument skill. It is a visual habit and requires practice.

=== The Control Zone ===
The control zone is the offensive firing position, located in the bandit's rear quarter. From the control zone you have sufficient range for weapon employment, a manageable aspect angle, and controlled closure.

Getting into the control zone is not enough. You must '''assess''' before employing. The assessment uses the '''Rule of Threes''':
{| class="wikitable" style="width:100%;"
!Parameter
!Value
!Notes
|-
|Range
|~3,000 ft
|Read from HUD or FCR
|-
|Aspect Angle
|≤30°
|Draw an imaginary box around the bandit — square silhouette means ~30° AA
|-
|Closure
|Steady and controlled
|Not increasing, not zero
|}
All three must be satisfied before moving in for a gun solution. If any are not met, reposition first.

=== Repositions ===
Repositions are controlled adjustments to fix range, closure, or aspect problems from the control zone.

==== Lead Reposition ====
Used when the bandit is pulling away and range is increasing. Pull lead pursuit to close the gap. Do not overshoot.

==== Lag Reposition ====
Used when closure is too high. Pull lag pursuit to slow closure and improve aspect. The bandit will drift aft in your field of view. Reassess once closure is controlled.

==== Ease Reposition ====
Used when range and closure are acceptable but aspect is slightly high. Ease back on the stick to widen your turn circle slightly. AA will decrease as the geometry opens. Once AA is acceptable, resume the original pull and reassess. This is a small correction — if aspect is significantly high, use a lag reposition instead.

=== Visual Aspect Estimation ===
Without looking at instruments, AA can be estimated by the shape of the bandit's silhouette:

* '''Rectangle''' (fuselage longer than wingspan) means AA is above 30°, too high for a clean gun solution
* '''Square''' (fuselage approximately equal to wingspan) means AA is approximately 30°, Rule of Threes satisfied
* '''Narrowing toward a point''' means AA is near 0°, pure tail-aspect

This visual check is faster than any instrument cross-check in a close turning fight.

=== Weapon Employment ===

==== Heat Seeker (FOX-2) ====
A valid FOX-2 shot requires a confirmed seeker tone and AA within the missile's acquisition envelope, typically ≤60° for rear-quarter shots. Do not fire without tone. At significant AA the seeker may struggle to acquire, so use a lag or ease reposition to reduce AA before attempting the shot.

==== Guns ====
A valid gun solution requires the Rule of Threes to be fully satisfied with the pipper placed on the bandit. In a turning fight this requires lead pursuit. Your nose must be ahead of the bandit's projected path, not pointed at him. The amount of lead required varies with range and closure rate.

A tracking shot requires the pipper to remain on the bandit for a sustained period. A snapshot is a momentary pipper-on opportunity taken when it presents itself, lower probability but sometimes the only option available.

=== The Quarter Plane ===
The quarter plane is a last-resort maneuver used when closure rate has become dangerously high and an overshoot is imminent. It is not a reposition.

The cue to act is approximately 1,000 ft of range, at which point the bandit's wingspan will fill roughly half the EEGS funnel on the HUD.

Execution:

# Roll wings level with the horizon
# Set idle power
# Pull maximum performance up and out of the bandit's plane of motion

This arrests closure and separates you vertically from the bandit's plane. Once clear, roll back into a turn toward the bandit and reassess. The quarter plane costs significant energy and altitude. Use it only when nothing else will prevent the overshoot.

=== Common Errors ===
{| class="wikitable" style="width:100%;"
!Error
!Consequence
!Correction
|-
|Late turn circle entry
|End up outside the bandit's circle with AA too high
|Watch for the LOS rate spike and turn at that moment
|-
|Early turn circle entry
|Cross inside bandit's radius, give him a reversal picture
|Wait for the LOS rate spike
|-
|Firing without satisfying Rule of Threes
|Low probability shot
|Reposition first, assess before employing
|-
|Pure pursuit at significant AA
|Missile must curve hard, degraded effectiveness
|Use CC or LC geometry for missile employment
|-
|Uncontrolled closure
|Overshoot, offensive position lost
|Use lag reposition early, quarter plane as last resort
|-
|Spending energy without reason
|Slow speed, large radius, advantage lost
|Maintain AB, only pull above sustained rate for a specific reason
|}

== BFM IV — Defensive BFM ==
This part is based on [https://www.youtube.com/playlist?list=PLd5Qdmhmp3Y5-SDJjOzuUqV3m3mmuieTQ this] video series by [https://www.youtube.com/@TheOpsCenterByMikeSolyom The Ops Center by Mike Solyom].

The objectives of defensive BFM are, in order of priority: survive, deny the bandit a weapons solution, and create the conditions for a role reversal. Survival is the primary objective. A fighter that remains in the fight presents a continuous problem to the attacker — he must maintain focus on the defender, consuming energy and attention that could otherwise be used offensively. Every second the defender survives is a second for supporting elements to close.

=== The Defensive Gameplan ===
The foundation of defensive BFM is the sustained rate turn. The defender should establish and maintain best sustained turn rate as the default gameplan. This accomplishes two things simultaneously: it maximizes the defender's turn performance for the duration of the engagement, and it preserves energy for subsequent maneuvering.

Deviation from the sustained rate gameplan should only occur when a specific threat — an imminent gun or missile shot — requires a more aggressive response. Expending energy prematurely leaves the defender slow, with a large turn radius and reduced options.

=== Cross-Check Discipline ===
In defensive BFM the pilot's attention is predominantly outside the cockpit on the bandit. However, three parameters must be periodically cross-checked throughout the engagement:
{| class="wikitable" style="width:100%;"
!Parameter
!Significance
|-
|'''Lift Vector'''
|Determines plane of motion and available turn rate
|-
|'''G'''
|Confirms correct turn performance is being applied
|-
|'''Airspeed'''
|Identifies energy state; confirms sustained rate speed is maintained
|}
The cross-check must not interrupt tally on the bandit for extended periods. Brief instrument scans returning immediately to visual are the correct technique. Loss of tally in a defensive engagement is a significant threat to survival.

=== Altitude Management ===
Altitude is a reserve of potential energy. Trading altitude for airspeed in a defensive turn temporarily increases available turn rate above the Ps = 0 line by lowering the lift vector below the horizon. This option is only available until the floor is reached. At that point the defender is constrained to a level sustained rate turn and loses the altitude trading option entirely.

=== Reading the Bandit's Intentions ===
The defender must continuously assess the bandit's pursuit course to anticipate his next action. The pursuit course is read visually:
{| class="wikitable" style="width:100%;"
!Pursuit Course
!Visual Cue
!Likely Intent
|-
|'''Pure pursuit'''
|Narrow nose-on profile
|Missile shot setup; seeker acquisition in progress
|-
|'''Lead pursuit'''
|Bandit's belly visible; nose pulled ahead of defender
|Gun shot imminent
|-
|'''Lag pursuit'''
|Top of bandit's aircraft visible; aft LOS movement
|Controlling closure; repositioning for follow-on attack
|}
Transition from lag to pure to lead is the signature sequence of an impending gun attack. Recognition of this sequence is the primary defensive cross-check task outside the cockpit.

Range assessment is equally important. The bandit's size relative to your field of view gives a continuous indication of closure. A bandit that fills a significant portion of your view is inside 2,500 ft and approaching gun parameters.

=== Maneuvers ===

==== Tighten Down ====
The tighten down is the first and most conservative response to a bandit closing into gun parameters. It is executed by increasing back pressure on the stick while already in a sustained rate turn, transitioning from sustained rate to a higher instantaneous turn rate.

The tighten down achieves two simultaneous effects. First, it rotates the defender's vulnerable rear quarter away from the attacker, driving the bandit outside the weapon employment zone. Second, the sudden airspeed reduction caused by the increased G creates a high closure rate problem for the attacker, forcing him to reposition to satisfy the Rule of Threes. This repositioning produces aft LOS movement and potentially a reversal picture.

The tighten down is an energy expenditure. It should be released once the immediate threat is defeated, returning to slightly below sustained rate and allowing AB to restore the energy state.

==== Out-of-Plane Maneuver (OOP) ====
The out-of-plane maneuver removes the defender from the attacker's plane of motion, forcing the attacker to reset his geometry. In a sustained rate turn both aircraft are operating in approximately the same plane of motion. Moving out of that plane disrupts the attacker's sight picture and solution geometry.

Execution:

# Unload the aircraft — reduce back pressure to below 1G
# Reposition the lift vector off the bandit, above or below his plane of motion
# Apply smooth back pressure to establish a turn in the new plane of motion
# Allow sufficient time for the aircraft to develop movement in the new plane before any follow-on maneuver
# Assess LOS rate and bandit pursuit course in the new plane

The unloaded roll is critical. Rolling while pulling G consumes energy without producing useful turning room. The unload must precede the roll.

Upon establishing the new plane of motion, assess for a reversal opportunity. If high aft LOS rate combined with high HCA and close range is observed, a reversal may be executed. Otherwise, continue maneuvering in the new plane.

==== Jink ====
The jink is a last-resort maneuver executed when a gun shot is assessed as imminent and neither the tighten down nor the OOP has defeated the attacker's solution. It combines elements of both into a single aggressive sequence designed to spoil the attacker's plane of motion and create a closure problem simultaneously.

Execution:

# Set throttle to idle
# Unload the aircraft
# Position the lift vector below the bandit
# Apply maximum onset rate back pressure and hold until aerodynamic buffet onset

The resulting airspeed reduction is severe and deliberate. The attacker is presented with a sudden, unforecast closure rate and a simultaneous change in plane of motion. If the attacker does not immediately reposition he will overshoot. If he does reposition, aft LOS movement will develop and a reversal picture may emerge.

If a reversal picture does not present after the first jink, execute a second jink to the opposite side:

# Idle power maintained
# Unload
# Reposition lift vector to the opposite side of the bandit
# Maximum onset back pressure

Continue until the attacker is forced into lag or a reversal picture develops. The jink sequence trades altitude at a high rate. Do not initiate within 1,500 to 2,000 ft of the floor. The jink is the highest energy expenditure maneuver in defensive BFM and is reserved strictly for imminent gun shot situations.

=== The Reversal ===
A reversal is a turn at an opportune moment in the opposite direction, executed to transition from a defensive position to a neutral or offensive one. Correctly timed, a reversal exploits the attacker's angles and closure to reposition the defender onto an advantageous bearing. Incorrectly timed, it degrades the defender's position further.

The opportunity for a correct reversal is rare and may only be available for a few seconds. More often than not a reversal will degrade the situation rather than improve it. Patience and recognition of the correct picture are essential.

==== The Reversal Picture ====
The reversal picture is the combination of visual conditions that indicate a reversal opportunity exists:

* High heading crossing angle (HCA), combined with
* Close range, and or high aft LOS rate

A practical assessment question: ''does it appear that the bandit will cross behind my tail with minimal assistance from me?'' If the answer is yes, execute. If there is any doubt, do not reverse. A premature reversal presents the attacker with a stable, predictable target and makes his job easier.

==== Execution ====
The reversal is executed using an unloaded roll:

# Reduce back pressure to unload the aircraft
# Roll to the opposite direction
# Resume back pressure once established in the new turn
# Shift visual focus to the opposite side to regain tally on the bandit

Lift vector placement after the reversal depends on range. At close range, position the lift vector above or below the bandit to build turning room before pulling into his plane of motion. At greater range, place the lift vector directly on the bandit.

A successful reversal will typically result in a scissors — a neutral position from which either pilot may gain an advantage. This is a significant improvement over the defensive.

=== Maneuver Selection Summary ===
{| class="wikitable" style="width:100%;"
!Situation
!Maneuver
!Notes
|-
|Bandit in lag or pure pursuit, not yet in gun parameters
|Sustained rate turn
|Conserve energy; maintain cross-check
|-
|Bandit transitioning to lead pursuit, gun shot developing
|Tighten down
|First response; moderate energy cost
|-
|Tighten down insufficient; bandit maintaining solution
|Out-of-plane maneuver
|Disrupts attacker geometry; assess for reversal
|-
|Gun shot imminent; no other option
|Jink
|Last resort; high energy cost; do not use prematurely
|-
|Reversal picture present
|Reversal
|Execute with unloaded roll; if in doubt, do not reverse
|}

== BFM V — High Aspect BFM ==
This part is based on [https://www.youtube.com/playlist?list=PLd5Qdmhmp3Y5-SDJjOzuUqV3m3mmuieTQ this] video series by [https://www.youtube.com/@TheOpsCenterByMikeSolyom The Ops Center by Mike Solyom].

High aspect BFM occurs when neither aircraft has a positional advantage at the merge. Both aircraft are nose-to-nose and the engagement begins from a neutral position. The name comes from the fact that at the merge, both aircraft are presenting high aspect to each other.

There are two reasons a pilot ends up in a high aspect fight. Either the bandit turns his nose toward you at the conclusion of a BVR intercept, or a BFM error led to the loss of an offensive position. The response is the same in either case.

=== The Lead Turn ===
The lead turn is the single most important concept in high aspect BFM. It is executed before the merge and determines the starting position of the fight.

Rather than waiting until the bandit's 3-9 line to begin turning — which produces a neutral merge — the pilot initiates the turn early. This builds an angular advantage before the first pass. At the sustained turn rate of the F-16, every additional second of turn produces more than 10° of angular advantage that the bandit must make up. Even two seconds of early turning can produce an advantage that a bandit in the same aircraft cannot recover from.

The lead turn cue is a rapidly increasing LOS rate from 11 to 10 o'clock for a left-side pass, or 1 to 2 o'clock for a right-side pass. This is the correct moment to turn. Turning too late leaves you behind the bandit with an energy problem. Turning too early gives the bandit a reversal picture.

If the lead turn is started too late there is little that can be done — accept the problem and manage it. If the lead turn is started too early, ease off the G momentarily until the bandit's LOS rate resumes, then resume the pull.

When executed correctly, the lead turn produces a '''stern conversion''' — the pilot arrives at the bandit's six o'clock within gun range without requiring further maneuvering.

=== Turning Room ===
Turning room is the separation between the two aircraft that is available to turn into. It can be built vertically or laterally, but never to the outside of the bandit's turn circle — floating outside gives the bandit more time and reduces the angular advantage gained in the lead turn.

The overriding factor when deciding whether to climb or descend is ease of tally on the bandit, and denying the bandit tally on you. Use the environment — put the bandit against a cloud, get between the bandit and the sun, avoid staying at the same altitude as the bandit. Tally is survival.

Vertical turning room comes with an energy cost that must be accounted for. A descent toward the bandit will add approximately 100 KCAS at the merge. A climb will cost approximately 100 KCAS. If this is not managed, the pilot will either overshoot the bandit or arrive too slow to sustain a competitive turn rate. Adjust entry speed before the turn-in accordingly. The fastest way to build speed without turning is to unload the aircraft — do this in the seconds between the turn-in and the merge.

Lateral turning room is always built to the inside of the bandit's turn circle. There is no useful lateral room to the outside.

=== Determining Fight Geometry ===
At the merge, the direction the bandit turns determines the geometry of the fight. '''The last aircraft to turn decides whether the engagement becomes a one-circle or two-circle fight.''' This is a deliberate choice — a pilot who executes a lead turn gives up the ability to choose the fight geometry, because the bandit turns last. The lead turn advantage is generally worth this tradeoff.

* '''Bandit turns toward you''' → two-circle fight. Both aircraft chase each other's tails. Ground track resembles two separate circles.
* '''Bandit turns away from you''' → one-circle fight. Both aircraft circle back toward each other for a second nose-to-nose pass. Ground track resembles a single circle.

Identifying which geometry has been established requires only one visual check: if the bandit is nose-to-tail relative to you, it is a two-circle fight. If it is nose-to-nose, it is a one-circle fight.

=== Losing Tally ===
Losing visual on the bandit in a turning fight is dangerous. Two rules apply immediately:

'''Do not fly straight and level while searching.''' Straight flight makes the defender's job trivial. Maintain the turn at all times.

'''Search along the turn circle.''' The bandit's most likely position is in the high-probability kill zone behind and above — the high-Pk WEZ. When the area behind you is clear, scan upward along the turn circle. The bandit will be somewhere along that arc if still engaged.

== BFM V-A — Two-Circle Fight ==
A two-circle fight begins when the bandit turns away from you at the merge. Both aircraft are now chasing each other's tail, producing a ground track that resembles two separate circles. The fight is a turn rate contest — the aircraft that can sustain a higher turn rate will eventually work its nose onto the the tail of the other.

=== The Default Gameplan ===
In a two-circle fight, maintain best sustained turn rate. Do not deviate from this. The temptation to pull into lead or pure pursuit to force a quick shot will produce a predictable result: range closes rapidly, aspect increases to beam or beyond, and the bandit drifts aft on the canopy. The fight resets to where it started. This yo-yoing effect will repeat indefinitely if the pilot keeps chasing the shot prematurely. Stay on the sustained rate turn and let the geometry develop.

=== Reading the Fight ===
As both aircraft complete the first circle, the bandit's position on the canopy provides continuous information about how the fight is developing. Three conditions are possible:
{| class="wikitable" style="width:100%;"
!Visual Cue
!Assessment
!Action
|-
|Bandit moving forward on the canopy, aspect stagnant or decreasing
|Winning — angular advantage is building
|Continue sustained rate turn; prepare for lead turn at next merge
|-
|Bandit moving forward on the canopy, aspect increasing toward nose-to-nose
|Neutral — neither pilot has an advantage
|Assess energy state; choose one-circle or two-circle at the next merge
|-
|Bandit's motion stagnant or drifting aft, bandit showing narrow nose-on profile
|Losing — bandit is gaining angular advantage
|Check G — increase to moderate buffet; if insufficient, transition to defensive BFM
|}
When neutral cues are present, the decision between one-circle and two-circle at the next merge is based on energy state. Above approximately 350 KCAS the aircraft has sufficient energy for a sustained rate two-circle game plan. Below that, the turn radius is already small enough that a one-circle minimum radius game plan is more effective.

=== Turn Circle Extension (TCX) ===
Even with a turn rate advantage, the two turn circles will not be perfectly aligned after the first pass. The bandit will yo-yo up and down the canopy as the circles overlap and separate. Forcing a shot during this phase produces the same premature high-aspect result described above. The solution is the turn circle extension.

A TCX is two to three seconds of easing off the G — not a full unload, just a reduction in back pressure that allows the center of the turn circle to shift. This repositions the turn circle to better align with the bandit's. It is not a straight line, though it can be. It is simply a brief relaxation of the sustained rate pull followed by resumption.

The cue to extend is the bandit sliding into the assessment window — approximately 45 to 60 degrees AA — combined with aft LOS movement. This is the same assessment window used in offensive BFM. If the bandit's aspect is above 30 degrees, ease back on the G. That easing is the TCX.

Timing matters. A TCX initiated too early shifts the turn circle sideways without closing the gap. A TCX initiated too late pushes both circles further apart. The correct moment is when the bandit is in the assessment window with aft LOS developing.

Multiple TCX corrections should be expected before the turn circles align. The manual notes that this process can require between 500 and 1,000 degrees of turning — approximately three times around the circle. Do not force it. Once the circles align, the fight transitions naturally into offensive BFM.

=== Regaining Tally ===
If tally is lost during a two-circle fight, apply the rules from the fundamentals section: maintain the turn and scan along the turn circle upward through the high-Pk zone. In a nose-to-tail fight the bandit will be somewhere along that arc. Do not level the wings.

== BFM V-B — One-Circle Fight ==
A one-circle fight begins when the bandit turns toward you at the merge. Both aircraft are now circling back to meet each other in a second nose-to-nose pass. The ground track resembles a single circle. Unlike the two-circle fight where turn rate is the deciding factor, the one-circle fight is a '''turn radius contest'''. The aircraft that can get its nose around the circle faster — by minimizing turn radius — will arrive at the next merge with an angular advantage.

=== Why Radius and Not Rate ===
In a two-circle fight, a smaller radius produces no advantage because both aircraft are always on opposite sides of their respective circles and never converge to a point where the nose can be brought to bear. Turn rate determines who gets there first.

In a one-circle fight the geometry is different. Both aircraft are converging on the same point — the next merge. The aircraft with the smaller radius gets its nose pointed at the bandit sooner, creating an opportunity for a lead turn or even a shot before the second pass. The aircraft with the larger radius arrives late and with less angular advantage.

=== The Minimum Radius Gameplan ===
To minimize turn radius in the F-16, pull enough G to reach a moderate aerodynamic buffet. The buffet indicates the aircraft is operating above the sustained turn rate and approaching the maximum lift line on the EM diagram — the region of minimum radius. Do not stall. A moderate buffet is the target, not maximum back pressure.

The F-16 does not have an audio cue for this in DCS. Use the physical buffet as the indicator. If nothing is shaking, more G is needed.

Select maximum afterburner throughout. The minimum radius game plan costs energy — AB partially offsets this bleed and maintains options for subsequent maneuvering.

=== Reading the Fight ===
As both aircraft come around the circle toward the second merge, the bandit's position on the canopy indicates whether the radius fight is being won or lost:
{| class="wikitable" style="width:100%;"
!Visual Cue
!Assessment
!Action
|-
|Bandit moving forward on the canopy, aspect stagnant or decreasing, top of bandit's aircraft visible
|Winning — angular advantage is building
|Execute lead turn at next merge to convert to offensive BFM
|-
|Bandit near or inside the canopy, nose pointed at you, bandit showing narrow nose-on profile
|Neutral — neither pilot has significant advantage
|Assess energy state; choose fight geometry at next merge
|-
|Bandit's motion stagnant or drifting aft, bandit showing narrow nose-on profile
|Losing — bandit is gaining the angular advantage
|Increase G to moderate buffet; if insufficient, transition to defensive BFM
|}

=== At the Next Merge ===
A one-circle fight always leads to a second merge. Three outcomes are possible at that merge:

* '''Another one-circle''' — bandit turns away again. Continue minimum radius game plan.
* '''Two-circle''' — bandit turns toward you. Transition to sustained rate game plan.
* '''Scissors''' — both aircraft begin reversing rapidly on each other. See below.

The decision between one-circle and two-circle at the second merge is based on energy state. Above approximately 350 KCAS the aircraft has enough energy for a sustained rate two-circle game plan. Below that, the turn radius is already small and one-circle minimum radius is more effective. Do not be indecisive — the last fighter to turn determines the fight geometry. Commit to a direction.

=== The Scissors ===
The scissors develops when both aircraft are reversing rapidly on each other and neither can establish a clean angular advantage. Both aircraft are within the other's turn circle. The ground track resembles scissor blades opening and closing.

The gameplan in a scissors is identical to the one-circle minimum radius game plan: minimize forward ground track by minimizing turn radius. Pull to moderate buffet, place the lift vector on the bandit, and select max afterburner. The aircraft with the smaller forward ground track will eventually fall behind the other and transition to an offensive position.

One-circle fights and scissors consume energy at a high rate due to the sustained high-G maneuvering required. Be aware of airspeed throughout — winning the radius fight but arriving slow leaves the bandit with an energy advantage that may be unrecoverable.

=== Losing the One-Circle ===
If the bandit is gaining the angular advantage, the symptoms are: the bandit's motion on the canopy goes stagnant or drifts aft, and the bandit's profile narrows to a pure pursuit nose-on silhouette. This is the bandit executing the same minimum radius game plan successfully.

When losing cues are present, first confirm G is sufficient — pull to moderate buffet if not already there. If the situation continues to deteriorate, transition to defensive BFM immediately. The one-circle fight has become a defensive situation and should be treated as one.

Never stop maneuvering. A neutral position is always recoverable. A position lost by giving up is not.

Procedures/78th/A2A/BFM

2026-05-23T17:10:46Z

Niknam3: /* Turning Room */

== BFM I — Energy and the EM Diagram ==
This part is based on [https://youtube.com/playlist?list=PLd5Qdmhmp3Y5-SDJjOzuUqV3m3mmuieTQ&si=FNdYqWagls5zNQjG this] video series by [https://www.youtube.com/@TheOpsCenterByMikeSolyom The Ops Center by Mike Solyom].

=== Energy ===
Every decision in a dogfight is an energy decision. An aircraft's energy state is expressed primarily as airspeed and altitude. The faster and higher you are, the more potential energy you have to maneuver. Energy buys turn rate, separation, and shot opportunities. Waste Energy and you will loose.

The First principle of BFM is simple: '''build energy and save it until you have a reason to spend it.''' That reason is either a shot on the bandit or denying a shot on yourself. If neither opportunity exists, maintain or build energy. Do not waste.

=== The Energy Maneuverability (EM) Diagram ===
The EM diagram is the definitive tool for understanding how an aircraft performs in a turning fight. It maps turn rate against airspeed for a specific set of parameters: aircraft weight, altitude, throttle setting, and configuration. Every number on the chart is only valid for those exact conditions.

For the F-16C in DCS the reference diagram is: '''Full AB · Clean · Sea Level · 12300 kg'''
[[File:F16 EM Diagram.png|center|frameless|945x945px]]

Key performance figures from this diagram:
{| class="wikitable" style="width:100%;"
!Parameter
!Value
!Condition
|-
|Max instantaneous turn rate
|24°/s
|393 KCAS
|-
|Max sustained turn rate
|18°/s
|523 KCAS
|-
|Min sustained turn radius
|1,462 ft
|246 KCAS
|-
|Min turn radius
|1,399 ft
|169 KCAS
|}
'''Note:''' The F-16's G-limiter schedule is not fully reflected in the upper portion of this diagram. Maximum instantaneous performance may be lower than indicated in practice. The DCS implementation of the F-16 Flight Model also severely limits the F16's Sustained turn rate.

=== Reading the Diagram ===

==== The Axes ====

* '''Horizontal axis''': airspeed in Mach (lower) and KCAS (higher)
* '''Vertical axis''': turn rate in degrees per second (°/s)

Moving up on the chart means higher turn rate.

==== The Lines ====
'''The Envelope (red)'''

The outer boundary of what the aircraft can physically do. It is shaped by three limits:

* '''Structural G limit''' is the maximum G the airframe can sustain; forms the upper-right boundary
* '''Angle of attack limit''' — the stall boundary; forms the left boundary
* '''Speed limit (Vmax)''' — the right-side boundary (going supersonic will nearly always kill both your turn rate and radius and is not desirable)

No matter what the pilot does, the aircraft cannot operate outside the red envelope.

'''Turn Radius Lines (brown)'''

These straight lines show turn radius in feet at any given point on the chart. Moving up and left gives a smaller radius.

'''G-Load Lines (gray)'''

Indicate how many G must be pulled to reach that point on the chart. To achieve a Instantaneous Turn rate of 20° at 400CAS the aircraft needs to pull about 7.5G

'''Ps Lines (solid black)'''

Specific excess power lines are the most important lines on the chart. They show whether the aircraft is gaining or losing energy at any given combination of speed and G.

* '''Ps = 0''' — the aircraft is exactly maintaining its energy state. This is the sustained turn line. The maximum turn rate achievable while sustaining speed and altitude sits on this line.
* '''Ps > 0 (positive numbers)''' — the aircraft is gaining energy. It can accelerate or climb while maintaining the current turn.
* '''Ps < 0 (negative numbers)''' — the aircraft is losing energy. It is spending saved energy for extra turn performance. This is temporary and cannot be maintained indefinitely.

Anything above the Ps = 0 line is an energy expenditure. The higher above it you go, the faster you bleed speed.

=== Corner Velocity ===
Corner velocity is the airspeed at which the aircraft achieves its maximum instantaneous turn rate — the peak of the envelope. For the F-16C at sea level this occurs at '''401CAS''', producing '''24°/s'''.

For the maximum Instantaneous turn the DCS Flight model requires the pilot to pull 9G and decent with over 1200ft/s which is in any way not sustainable unless the a significant amount of Altitude has been built up. DO NOT use this unless you need to safe your life.

=== Sustained Turn Rate ===
The sustained turn rate is the maximum turn rate the aircraft can maintain indefinitely without losing speed or altitude. For the F-16C at sea level this is '''18°/s @ 523 KCAS'''.

In practice, sustained operations happen on or near the Ps = 0 line. The pilot's job is to find and hold that point. Sadly in DCS to hold and maintain that line is impossible. To Fly Perfect Sustained Turn Rate you need to pull 9G in full afterburner. You will know that you hit the perfect speed if, at max pull, in a level turn, the Jet neither gains nor looses Max energy.

A sustained 9G turn will black out any pilot. To Compensate the Pilot should fly slighly below the Optimal Speed allowing for higher turn rate while loosing a small amount of energy. Once the Jet reaches around 70-80 KTS below optimal speed the pilot should reduce the pull to about 6G for maximum recovery speed. While only pulling 6G the jet will gain energy fast. Once back at optimal speed continue to pull 9G.

If you overshoot the Optimal Speed you will notice that even at max pull the aircraft is still gaining airspeed. In this case execute a spiral climb to return back to Optimal Speed while utilizing the excess Energy.

If you undershoot the Optimal Speed you will notice that at max pull the aircraft is loosing airspeed fast. Either Reduce pull back to 6G until at better speed or trade altitude for extra Energy.

=== Instantaneous vs Sustained ===
{| class="wikitable" style="width:100%;"
!
!Instantaneous
!Sustained
|-
|'''Definition'''
|Maximum turn rate achievable at any moment
|Maximum turn rate maintainable indefinitely
|-
|'''F-16C value (sea level)'''
|24°/s @ 393 KCAS
|18°/s @ 523 KCAS
|-
|'''Energy cost'''
|High: Far above Ps = 0, bleeding speed fast (expect around 50kts/s)
|None if optimally flown on Ps = 0 line
|-
|'''When to use'''
|Short bursts for a shot opportunity or to deny a shot
|Default gameplan in any sustained turning fight
|}
Instantaneous turn rate is spending saved energy. It is a powerful tool but a temporary one. A pilot who pulls to instantaneous continuously will bleed to low speed, and lose the fight on energy.

=== How Altitude and Stores Affect the Diagram ===
The reference diagram is for sea level, clean, full AB. Both altitude and external stores degrade performance:

* '''Altitude''': thinner air reduces lift and engine thrust. Turn rate and sustained performance both decrease. The same airspeed produces a larger turn radius at altitude.
* '''Weight:''' Fuel or Stores will both make you heavy. The heavier you are the worse the performance. As you burn fuel the optimum Sustained turn rate Speed will decrease into manageable Levels.

=== Practical Application ===
In the fight itself: '''treat energy like money.''' Build it, save it, and spend it only when the return is worth it. A valid shot, or surviving by denying the adversary a shot oportunity. Spending energy for no tactical gain is a losing strategy.

== BFM II — Angles and Geometry ==

=== Angles and Definitions ===

[[File:Angles.webp|frameless|715x715px]]

==== Antenna Train Angle (ATA) ====
The ATA is the position of the bandit left or right of the fighter's nose on the radar display. ATA 0 means the target is dead ahead. ATA 30R means the target is 30° to the right of your nose.

The ATA is a property of your own aircraft's orientation. It changes when '''you''' maneuver. It does not change instantaneously when the bandit maneuvers.

On the F-16 FCR, ATA is read on the horizontal axis.

==== Target Aspect (TA) ====
Target Aspect, not to confuse with Aspect Angle is how the bandit appears from your perspective. Specifically, the angle from the bearing line of the fighter to the '''nose''' of the target. It describes which part of the bandit you are looking at.

* TA 0 —you are looking at the bandit's nose (head-on)
* TA 90 — you are looking at the bandit's side
* TA 180 — you are looking at the bandit's tail (pure stern)

TA is signed left or right depending on which side of the bandit you are observing.

Unlike ATA, Target Aspect is '''entirely determined by the bandit's heading''' relative to the bearing line between you. You cannot change it instantaneously. You can only influence it over time by maneuvering to change the geometry.

The F-16 does not display TA directly. It displays the '''Aspect Angle (AA)''', which is the supplementary angle of TA (AA = 180° − TA). A tail-aspect shot has AA 0; a head-on shot has AA 180.
[[File:AAvsTA.webp|thumb|600x600px]]
Common TA labels used in brevity:
{| class="wikitable"
!TA
!AA
!Label
|-
|0°–30°
|150°–180°
|Hot
|-
|31°–75°
|105°–149°
|Flank
|-
|76°–110°
|70°–104°
|Beam
|-
|111°–150°
|30°–69°
|Drag
|-
|151°–180°
|0°–29°
|Cold
|}

==== Cut ====
Cut is the angle from the '''Fighter Heading (FH)''' to the '''Bandit Reciprocal (BR)'''. It describes where your nose is pointing relative to the bandit's course.

Cut is an older concept but remains one of the most useful tools for predicting how the geometry will evolve. Three reference cases:

* '''Cut greater than Collision Course''' — your nose is in front of the bandit. Over time, TA decreases and Lateral Separation decreases. You are closing the geometry aggressively.
* '''Cut equal to Collision Course''' — the magic case. TA is captured: it does not change. Lateral Separation decreases. If co-altitude, you will eventually collide.
* '''Cut less than Collision Course (Zero-Cut / Parallel)''' — your nose points at the bandit's reciprocal. TA increases over time. Lateral Separation is captured: it does not change.
* '''Cut-Away''' — your nose points away from the bandit entirely. Both TA and Lateral Separation increase. Used to build angles or lateral room.

==== Degrees to Go (DTG) / Heading Crossing Angle (HCA) ====
DTG is the number of degrees the fighter needs to turn to be '''parallel''' to the bandit's flight path. It is the supplementary angle of Cut. A useful memory aid: ''Degrees to Go — where? Parallel.''

==== Lateral Separation (LS) ====
Lateral Separation is the perpendicular distance between the two flight paths. It determines how much maneuvering room exists for a conversion. It is approximated as:
LS (ft) = TA × SR × 100
Where SR is slant range in nautical miles. Lateral Separation matters most when planning a stern conversion or assessing whether a shot is geometrically viable.

==== Direction of Passage (DOP) ====
DOP describes the direction the bandit would cross your flight path if neither aircraft maneuvered. Called as left-to-right or right-to-left. Useful shorthand for building SA quickly.

==== Slant Range (SR) ====
[[File:SlantRange.webp|thumb|500x500px|center]]
The straight line-of-sight distance between the two aircraft in three-dimensional space. On the F-16 FCR this is the range displayed on the scope.

=== Pursuit Types ===
[[File:Pursuit.webp|thumb|700x700px|center]]
The type of pursuit describes where your nose is pointing relative to the target.
{| class="wikitable" style="width:100%;"
!Pursuit Type
!Nose Position
!Common Use
|-
|'''Lead Pursuit'''
|In front of the target
|Collision Course, gun employment from RQ
|-
|'''Pure Pursuit'''
|Directly at the target
|Simple conversions; commonly overused by new pilots
|-
|'''Lag Pursuit'''
|Behind the target
|Geometry management, WVR maneuvering
|}

== BFM III — Offensive BFM ==
Offensive BFM begins with you in a position of advantage. The bandit is somewhere in your forward hemisphere and your job is to convert that advantage into a weapons solution before he can deny it.

=== The Turn Circle ===
Every maneuvering aircraft has a turn circle, the circular path it is flying at any given moment. To employ weapons on the bandit you must get inside his turn circle, or at minimum align with it. Getting outside means you are turning wider than he is and falling behind.

The cue for turn circle entry is a high LOS rate (see below). As you approach the edge of the bandit's circle the bandit will begin moving rapidly across your field of view. Turn at that moment. Turn too early and you cross inside his radius, giving him a reversal opportunity. Turn too late and you end up outside his circle with AA too high to employ.

=== Line of Sight Rate ===
Line of Sight (LOS) rate is the speed at which the bandit moves across your field of view. It is one of the most important diagnostic tools in BFM and appears throughout offensive, defensive, and high aspect engagements.

A high LOS rate means the bandit is moving quickly across your canopy. A low or zero LOS rate means the bandit is stable relative to your nose. LOS rate tells you two things:

* '''Where are you relative to the bandit's turn circle'''? A sudden spike in LOS rate signals that you have reached the edge of his turn circle. Inside his circle, LOS rate is high. Outside it, LOS rate is low.
* '''What is the Geometry doing?''' Aft LOS movement means the bandit is drifting toward your 6; forward LOS movement means he is drifting toward your 12. The direction and speed of that drift tells you whether the geometry is improving or deteriorating.

Learning to read LOS rate is not an instrument skill. It is a visual habit and requires practice.

=== The Control Zone ===
The control zone is the offensive firing position, located in the bandit's rear quarter. From the control zone you have sufficient range for weapon employment, a manageable aspect angle, and controlled closure.

Getting into the control zone is not enough. You must '''assess''' before employing. The assessment uses the '''Rule of Threes''':
{| class="wikitable" style="width:100%;"
!Parameter
!Value
!Notes
|-
|Range
|~3,000 ft
|Read from HUD or FCR
|-
|Aspect Angle
|≤30°
|Draw an imaginary box around the bandit — square silhouette means ~30° AA
|-
|Closure
|Steady and controlled
|Not increasing, not zero
|}
All three must be satisfied before moving in for a gun solution. If any are not met, reposition first.

=== Repositions ===
Repositions are controlled adjustments to fix range, closure, or aspect problems from the control zone.

==== Lead Reposition ====
Used when the bandit is pulling away and range is increasing. Pull lead pursuit to close the gap. Do not overshoot.

==== Lag Reposition ====
Used when closure is too high. Pull lag pursuit to slow closure and improve aspect. The bandit will drift aft in your field of view. Reassess once closure is controlled.

==== Ease Reposition ====
Used when range and closure are acceptable but aspect is slightly high. Ease back on the stick to widen your turn circle slightly. AA will decrease as the geometry opens. Once AA is acceptable, resume the original pull and reassess. This is a small correction — if aspect is significantly high, use a lag reposition instead.

=== Visual Aspect Estimation ===
Without looking at instruments, AA can be estimated by the shape of the bandit's silhouette:

* '''Rectangle''' (fuselage longer than wingspan) means AA is above 30°, too high for a clean gun solution
* '''Square''' (fuselage approximately equal to wingspan) means AA is approximately 30°, Rule of Threes satisfied
* '''Narrowing toward a point''' means AA is near 0°, pure tail-aspect

This visual check is faster than any instrument cross-check in a close turning fight.

=== Weapon Employment ===

==== Heat Seeker (FOX-2) ====
A valid FOX-2 shot requires a confirmed seeker tone and AA within the missile's acquisition envelope, typically ≤60° for rear-quarter shots. Do not fire without tone. At significant AA the seeker may struggle to acquire, so use a lag or ease reposition to reduce AA before attempting the shot.

==== Guns ====
A valid gun solution requires the Rule of Threes to be fully satisfied with the pipper placed on the bandit. In a turning fight this requires lead pursuit. Your nose must be ahead of the bandit's projected path, not pointed at him. The amount of lead required varies with range and closure rate.

A tracking shot requires the pipper to remain on the bandit for a sustained period. A snapshot is a momentary pipper-on opportunity taken when it presents itself, lower probability but sometimes the only option available.

=== The Quarter Plane ===
The quarter plane is a last-resort maneuver used when closure rate has become dangerously high and an overshoot is imminent. It is not a reposition.

The cue to act is approximately 1,000 ft of range, at which point the bandit's wingspan will fill roughly half the EEGS funnel on the HUD.

Execution:

# Roll wings level with the horizon
# Set idle power
# Pull maximum performance up and out of the bandit's plane of motion

This arrests closure and separates you vertically from the bandit's plane. Once clear, roll back into a turn toward the bandit and reassess. The quarter plane costs significant energy and altitude. Use it only when nothing else will prevent the overshoot.

=== Common Errors ===
{| class="wikitable" style="width:100%;"
!Error
!Consequence
!Correction
|-
|Late turn circle entry
|End up outside the bandit's circle with AA too high
|Watch for the LOS rate spike and turn at that moment
|-
|Early turn circle entry
|Cross inside bandit's radius, give him a reversal picture
|Wait for the LOS rate spike
|-
|Firing without satisfying Rule of Threes
|Low probability shot
|Reposition first, assess before employing
|-
|Pure pursuit at significant AA
|Missile must curve hard, degraded effectiveness
|Use CC or LC geometry for missile employment
|-
|Uncontrolled closure
|Overshoot, offensive position lost
|Use lag reposition early, quarter plane as last resort
|-
|Spending energy without reason
|Slow speed, large radius, advantage lost
|Maintain AB, only pull above sustained rate for a specific reason
|}

== BFM IV — Defensive BFM ==
This part is based on [https://www.youtube.com/playlist?list=PLd5Qdmhmp3Y5-SDJjOzuUqV3m3mmuieTQ this] video series by [https://www.youtube.com/@TheOpsCenterByMikeSolyom The Ops Center by Mike Solyom].

The objectives of defensive BFM are, in order of priority: survive, deny the bandit a weapons solution, and create the conditions for a role reversal. Survival is the primary objective. A fighter that remains in the fight presents a continuous problem to the attacker — he must maintain focus on the defender, consuming energy and attention that could otherwise be used offensively. Every second the defender survives is a second for supporting elements to close.

=== The Defensive Gameplan ===
The foundation of defensive BFM is the sustained rate turn. The defender should establish and maintain best sustained turn rate as the default gameplan. This accomplishes two things simultaneously: it maximizes the defender's turn performance for the duration of the engagement, and it preserves energy for subsequent maneuvering.

Deviation from the sustained rate gameplan should only occur when a specific threat — an imminent gun or missile shot — requires a more aggressive response. Expending energy prematurely leaves the defender slow, with a large turn radius and reduced options.

=== Cross-Check Discipline ===
In defensive BFM the pilot's attention is predominantly outside the cockpit on the bandit. However, three parameters must be periodically cross-checked throughout the engagement:
{| class="wikitable" style="width:100%;"
!Parameter
!Significance
|-
|'''Lift Vector'''
|Determines plane of motion and available turn rate
|-
|'''G'''
|Confirms correct turn performance is being applied
|-
|'''Airspeed'''
|Identifies energy state; confirms sustained rate speed is maintained
|}
The cross-check must not interrupt tally on the bandit for extended periods. Brief instrument scans returning immediately to visual are the correct technique. Loss of tally in a defensive engagement is a significant threat to survival.

=== Altitude Management ===
Altitude is a reserve of potential energy. Trading altitude for airspeed in a defensive turn temporarily increases available turn rate above the Ps = 0 line by lowering the lift vector below the horizon. This option is only available until the floor is reached. At that point the defender is constrained to a level sustained rate turn and loses the altitude trading option entirely.

=== Reading the Bandit's Intentions ===
The defender must continuously assess the bandit's pursuit course to anticipate his next action. The pursuit course is read visually:
{| class="wikitable" style="width:100%;"
!Pursuit Course
!Visual Cue
!Likely Intent
|-
|'''Pure pursuit'''
|Narrow nose-on profile
|Missile shot setup; seeker acquisition in progress
|-
|'''Lead pursuit'''
|Bandit's belly visible; nose pulled ahead of defender
|Gun shot imminent
|-
|'''Lag pursuit'''
|Top of bandit's aircraft visible; aft LOS movement
|Controlling closure; repositioning for follow-on attack
|}
Transition from lag to pure to lead is the signature sequence of an impending gun attack. Recognition of this sequence is the primary defensive cross-check task outside the cockpit.

Range assessment is equally important. The bandit's size relative to your field of view gives a continuous indication of closure. A bandit that fills a significant portion of your view is inside 2,500 ft and approaching gun parameters.

=== Maneuvers ===

==== Tighten Down ====
The tighten down is the first and most conservative response to a bandit closing into gun parameters. It is executed by increasing back pressure on the stick while already in a sustained rate turn, transitioning from sustained rate to a higher instantaneous turn rate.

The tighten down achieves two simultaneous effects. First, it rotates the defender's vulnerable rear quarter away from the attacker, driving the bandit outside the weapon employment zone. Second, the sudden airspeed reduction caused by the increased G creates a high closure rate problem for the attacker, forcing him to reposition to satisfy the Rule of Threes. This repositioning produces aft LOS movement and potentially a reversal picture.

The tighten down is an energy expenditure. It should be released once the immediate threat is defeated, returning to slightly below sustained rate and allowing AB to restore the energy state.

==== Out-of-Plane Maneuver (OOP) ====
The out-of-plane maneuver removes the defender from the attacker's plane of motion, forcing the attacker to reset his geometry. In a sustained rate turn both aircraft are operating in approximately the same plane of motion. Moving out of that plane disrupts the attacker's sight picture and solution geometry.

Execution:

# Unload the aircraft — reduce back pressure to below 1G
# Reposition the lift vector off the bandit, above or below his plane of motion
# Apply smooth back pressure to establish a turn in the new plane of motion
# Allow sufficient time for the aircraft to develop movement in the new plane before any follow-on maneuver
# Assess LOS rate and bandit pursuit course in the new plane

The unloaded roll is critical. Rolling while pulling G consumes energy without producing useful turning room. The unload must precede the roll.

Upon establishing the new plane of motion, assess for a reversal opportunity. If high aft LOS rate combined with high HCA and close range is observed, a reversal may be executed. Otherwise, continue maneuvering in the new plane.

==== Jink ====
The jink is a last-resort maneuver executed when a gun shot is assessed as imminent and neither the tighten down nor the OOP has defeated the attacker's solution. It combines elements of both into a single aggressive sequence designed to spoil the attacker's plane of motion and create a closure problem simultaneously.

Execution:

# Set throttle to idle
# Unload the aircraft
# Position the lift vector below the bandit
# Apply maximum onset rate back pressure and hold until aerodynamic buffet onset

The resulting airspeed reduction is severe and deliberate. The attacker is presented with a sudden, unforecast closure rate and a simultaneous change in plane of motion. If the attacker does not immediately reposition he will overshoot. If he does reposition, aft LOS movement will develop and a reversal picture may emerge.

If a reversal picture does not present after the first jink, execute a second jink to the opposite side:

# Idle power maintained
# Unload
# Reposition lift vector to the opposite side of the bandit
# Maximum onset back pressure

Continue until the attacker is forced into lag or a reversal picture develops. The jink sequence trades altitude at a high rate. Do not initiate within 1,500 to 2,000 ft of the floor. The jink is the highest energy expenditure maneuver in defensive BFM and is reserved strictly for imminent gun shot situations.

=== The Reversal ===
A reversal is a turn at an opportune moment in the opposite direction, executed to transition from a defensive position to a neutral or offensive one. Correctly timed, a reversal exploits the attacker's angles and closure to reposition the defender onto an advantageous bearing. Incorrectly timed, it degrades the defender's position further.

The opportunity for a correct reversal is rare and may only be available for a few seconds. More often than not a reversal will degrade the situation rather than improve it. Patience and recognition of the correct picture are essential.

==== The Reversal Picture ====
The reversal picture is the combination of visual conditions that indicate a reversal opportunity exists:

* High heading crossing angle (HCA), combined with
* Close range, and or high aft LOS rate

A practical assessment question: ''does it appear that the bandit will cross behind my tail with minimal assistance from me?'' If the answer is yes, execute. If there is any doubt, do not reverse. A premature reversal presents the attacker with a stable, predictable target and makes his job easier.

==== Execution ====
The reversal is executed using an unloaded roll:

# Reduce back pressure to unload the aircraft
# Roll to the opposite direction
# Resume back pressure once established in the new turn
# Shift visual focus to the opposite side to regain tally on the bandit

Lift vector placement after the reversal depends on range. At close range, position the lift vector above or below the bandit to build turning room before pulling into his plane of motion. At greater range, place the lift vector directly on the bandit.

A successful reversal will typically result in a scissors — a neutral position from which either pilot may gain an advantage. This is a significant improvement over the defensive.

=== Maneuver Selection Summary ===
{| class="wikitable" style="width:100%;"
!Situation
!Maneuver
!Notes
|-
|Bandit in lag or pure pursuit, not yet in gun parameters
|Sustained rate turn
|Conserve energy; maintain cross-check
|-
|Bandit transitioning to lead pursuit, gun shot developing
|Tighten down
|First response; moderate energy cost
|-
|Tighten down insufficient; bandit maintaining solution
|Out-of-plane maneuver
|Disrupts attacker geometry; assess for reversal
|-
|Gun shot imminent; no other option
|Jink
|Last resort; high energy cost; do not use prematurely
|-
|Reversal picture present
|Reversal
|Execute with unloaded roll; if in doubt, do not reverse
|}

== BFM V — High Aspect BFM ==
This part is based on [https://www.youtube.com/playlist?list=PLd5Qdmhmp3Y5-SDJjOzuUqV3m3mmuieTQ this] video series by [https://www.youtube.com/@TheOpsCenterByMikeSolyom The Ops Center by Mike Solyom].

High aspect BFM occurs when neither aircraft has a positional advantage at the merge. Both aircraft are nose-to-nose and the engagement begins from a neutral position. The name comes from the fact that at the merge, both aircraft are presenting high aspect to each other.

There are two reasons a pilot ends up in a high aspect fight. Either the bandit turns his nose toward you at the conclusion of a BVR intercept, or a BFM error led to the loss of an offensive position. The response is the same in either case.

=== The Lead Turn ===
The lead turn is the single most important concept in high aspect BFM. It is executed before the merge and determines the starting position of the fight.

Rather than waiting until the bandit's 3-9 line to begin turning — which produces a neutral merge — the pilot initiates the turn early. This builds an angular advantage before the first pass. At the sustained turn rate of the F-16, every additional second of turn produces more than 10° of angular advantage that the bandit must make up. Even two seconds of early turning can produce an advantage that a bandit in the same aircraft cannot recover from.

The lead turn cue is a rapidly increasing LOS rate from 11 to 10 o'clock for a left-side pass, or 1 to 2 o'clock for a right-side pass. This is the correct moment to turn. Turning too late leaves you behind the bandit with an energy problem. Turning too early gives the bandit a reversal picture.

If the lead turn is started too late there is little that can be done — accept the problem and manage it. If the lead turn is started too early, ease off the G momentarily until the bandit's LOS rate resumes, then resume the pull.

When executed correctly, the lead turn produces a '''stern conversion''' — the pilot arrives at the bandit's six o'clock within gun range without requiring further maneuvering.

=== Turning Room ===
Turning room is the separation between the two aircraft that is available to turn into. It can be built vertically or laterally, but never to the outside of the bandit's turn circle — floating outside gives the bandit more time and reduces the angular advantage gained in the lead turn.

The overriding factor when deciding whether to climb or descend is ease of tally on the bandit, and denying the bandit tally on you. Use the environment — put the bandit against a cloud, get between the bandit and the sun, avoid staying at the same altitude as the bandit. Tally is survival.

Vertical turning room comes with an energy cost that must be accounted for. A descent toward the bandit will add approximately 100 KCAS at the merge. A climb will cost approximately 100 KCAS. If this is not managed, the pilot will either overshoot the bandit or arrive too slow to sustain a competitive turn rate. Adjust entry speed before the turn-in accordingly. The fastest way to build speed without turning is to unload the aircraft — do this in the seconds between the turn-in and the merge.

Lateral turning room is always built to the inside of the bandit's turn circle. There is no useful lateral room to the outside.

=== Determining Fight Geometry ===
At the merge, the direction the bandit turns determines the geometry of the fight. '''The last aircraft to turn decides whether the engagement becomes a one-circle or two-circle fight.''' This is a deliberate choice — a pilot who executes a lead turn gives up the ability to choose the fight geometry, because the bandit turns last. The lead turn advantage is generally worth this tradeoff.

* '''Bandit turns toward you''' → two-circle fight. Both aircraft chase each other's tails. Ground track resembles two separate circles.
* '''Bandit turns away from you''' → one-circle fight. Both aircraft circle back toward each other for a second nose-to-nose pass. Ground track resembles a single circle.

Identifying which geometry has been established requires only one visual check: if the bandit is nose-to-tail relative to you, it is a two-circle fight. If it is nose-to-nose, it is a one-circle fight.

=== Losing Tally ===
Losing visual on the bandit in a turning fight is dangerous. Two rules apply immediately:

'''Do not fly straight and level while searching.''' Straight flight makes the defender's job trivial. Maintain the turn at all times.

'''Search along the turn circle.''' The bandit's most likely position is in the high-probability kill zone behind and above — the high-Pk WEZ. When the area behind you is clear, scan upward along the turn circle. The bandit will be somewhere along that arc if still engaged.

Procedures/78th/A2A/BFM

2026-05-23T17:10:40Z

Niknam3: /* Maneuver Selection Summary */

== BFM I — Energy and the EM Diagram ==
This part is based on [https://youtube.com/playlist?list=PLd5Qdmhmp3Y5-SDJjOzuUqV3m3mmuieTQ&si=FNdYqWagls5zNQjG this] video series by [https://www.youtube.com/@TheOpsCenterByMikeSolyom The Ops Center by Mike Solyom].

=== Energy ===
Every decision in a dogfight is an energy decision. An aircraft's energy state is expressed primarily as airspeed and altitude. The faster and higher you are, the more potential energy you have to maneuver. Energy buys turn rate, separation, and shot opportunities. Waste Energy and you will loose.

The First principle of BFM is simple: '''build energy and save it until you have a reason to spend it.''' That reason is either a shot on the bandit or denying a shot on yourself. If neither opportunity exists, maintain or build energy. Do not waste.

=== The Energy Maneuverability (EM) Diagram ===
The EM diagram is the definitive tool for understanding how an aircraft performs in a turning fight. It maps turn rate against airspeed for a specific set of parameters: aircraft weight, altitude, throttle setting, and configuration. Every number on the chart is only valid for those exact conditions.

For the F-16C in DCS the reference diagram is: '''Full AB · Clean · Sea Level · 12300 kg'''
[[File:F16 EM Diagram.png|center|frameless|945x945px]]

Key performance figures from this diagram:
{| class="wikitable" style="width:100%;"
!Parameter
!Value
!Condition
|-
|Max instantaneous turn rate
|24°/s
|393 KCAS
|-
|Max sustained turn rate
|18°/s
|523 KCAS
|-
|Min sustained turn radius
|1,462 ft
|246 KCAS
|-
|Min turn radius
|1,399 ft
|169 KCAS
|}
'''Note:''' The F-16's G-limiter schedule is not fully reflected in the upper portion of this diagram. Maximum instantaneous performance may be lower than indicated in practice. The DCS implementation of the F-16 Flight Model also severely limits the F16's Sustained turn rate.

=== Reading the Diagram ===

==== The Axes ====

* '''Horizontal axis''': airspeed in Mach (lower) and KCAS (higher)
* '''Vertical axis''': turn rate in degrees per second (°/s)

Moving up on the chart means higher turn rate.

==== The Lines ====
'''The Envelope (red)'''

The outer boundary of what the aircraft can physically do. It is shaped by three limits:

* '''Structural G limit''' is the maximum G the airframe can sustain; forms the upper-right boundary
* '''Angle of attack limit''' — the stall boundary; forms the left boundary
* '''Speed limit (Vmax)''' — the right-side boundary (going supersonic will nearly always kill both your turn rate and radius and is not desirable)

No matter what the pilot does, the aircraft cannot operate outside the red envelope.

'''Turn Radius Lines (brown)'''

These straight lines show turn radius in feet at any given point on the chart. Moving up and left gives a smaller radius.

'''G-Load Lines (gray)'''

Indicate how many G must be pulled to reach that point on the chart. To achieve a Instantaneous Turn rate of 20° at 400CAS the aircraft needs to pull about 7.5G

'''Ps Lines (solid black)'''

Specific excess power lines are the most important lines on the chart. They show whether the aircraft is gaining or losing energy at any given combination of speed and G.

* '''Ps = 0''' — the aircraft is exactly maintaining its energy state. This is the sustained turn line. The maximum turn rate achievable while sustaining speed and altitude sits on this line.
* '''Ps > 0 (positive numbers)''' — the aircraft is gaining energy. It can accelerate or climb while maintaining the current turn.
* '''Ps < 0 (negative numbers)''' — the aircraft is losing energy. It is spending saved energy for extra turn performance. This is temporary and cannot be maintained indefinitely.

Anything above the Ps = 0 line is an energy expenditure. The higher above it you go, the faster you bleed speed.

=== Corner Velocity ===
Corner velocity is the airspeed at which the aircraft achieves its maximum instantaneous turn rate — the peak of the envelope. For the F-16C at sea level this occurs at '''401CAS''', producing '''24°/s'''.

For the maximum Instantaneous turn the DCS Flight model requires the pilot to pull 9G and decent with over 1200ft/s which is in any way not sustainable unless the a significant amount of Altitude has been built up. DO NOT use this unless you need to safe your life.

=== Sustained Turn Rate ===
The sustained turn rate is the maximum turn rate the aircraft can maintain indefinitely without losing speed or altitude. For the F-16C at sea level this is '''18°/s @ 523 KCAS'''.

In practice, sustained operations happen on or near the Ps = 0 line. The pilot's job is to find and hold that point. Sadly in DCS to hold and maintain that line is impossible. To Fly Perfect Sustained Turn Rate you need to pull 9G in full afterburner. You will know that you hit the perfect speed if, at max pull, in a level turn, the Jet neither gains nor looses Max energy.

A sustained 9G turn will black out any pilot. To Compensate the Pilot should fly slighly below the Optimal Speed allowing for higher turn rate while loosing a small amount of energy. Once the Jet reaches around 70-80 KTS below optimal speed the pilot should reduce the pull to about 6G for maximum recovery speed. While only pulling 6G the jet will gain energy fast. Once back at optimal speed continue to pull 9G.

If you overshoot the Optimal Speed you will notice that even at max pull the aircraft is still gaining airspeed. In this case execute a spiral climb to return back to Optimal Speed while utilizing the excess Energy.

If you undershoot the Optimal Speed you will notice that at max pull the aircraft is loosing airspeed fast. Either Reduce pull back to 6G until at better speed or trade altitude for extra Energy.

=== Instantaneous vs Sustained ===
{| class="wikitable" style="width:100%;"
!
!Instantaneous
!Sustained
|-
|'''Definition'''
|Maximum turn rate achievable at any moment
|Maximum turn rate maintainable indefinitely
|-
|'''F-16C value (sea level)'''
|24°/s @ 393 KCAS
|18°/s @ 523 KCAS
|-
|'''Energy cost'''
|High: Far above Ps = 0, bleeding speed fast (expect around 50kts/s)
|None if optimally flown on Ps = 0 line
|-
|'''When to use'''
|Short bursts for a shot opportunity or to deny a shot
|Default gameplan in any sustained turning fight
|}
Instantaneous turn rate is spending saved energy. It is a powerful tool but a temporary one. A pilot who pulls to instantaneous continuously will bleed to low speed, and lose the fight on energy.

=== How Altitude and Stores Affect the Diagram ===
The reference diagram is for sea level, clean, full AB. Both altitude and external stores degrade performance:

* '''Altitude''': thinner air reduces lift and engine thrust. Turn rate and sustained performance both decrease. The same airspeed produces a larger turn radius at altitude.
* '''Weight:''' Fuel or Stores will both make you heavy. The heavier you are the worse the performance. As you burn fuel the optimum Sustained turn rate Speed will decrease into manageable Levels.

=== Practical Application ===
In the fight itself: '''treat energy like money.''' Build it, save it, and spend it only when the return is worth it. A valid shot, or surviving by denying the adversary a shot oportunity. Spending energy for no tactical gain is a losing strategy.

== BFM II — Angles and Geometry ==

=== Angles and Definitions ===

[[File:Angles.webp|frameless|715x715px]]

==== Antenna Train Angle (ATA) ====
The ATA is the position of the bandit left or right of the fighter's nose on the radar display. ATA 0 means the target is dead ahead. ATA 30R means the target is 30° to the right of your nose.

The ATA is a property of your own aircraft's orientation. It changes when '''you''' maneuver. It does not change instantaneously when the bandit maneuvers.

On the F-16 FCR, ATA is read on the horizontal axis.

==== Target Aspect (TA) ====
Target Aspect, not to confuse with Aspect Angle is how the bandit appears from your perspective. Specifically, the angle from the bearing line of the fighter to the '''nose''' of the target. It describes which part of the bandit you are looking at.

* TA 0 —you are looking at the bandit's nose (head-on)
* TA 90 — you are looking at the bandit's side
* TA 180 — you are looking at the bandit's tail (pure stern)

TA is signed left or right depending on which side of the bandit you are observing.

Unlike ATA, Target Aspect is '''entirely determined by the bandit's heading''' relative to the bearing line between you. You cannot change it instantaneously. You can only influence it over time by maneuvering to change the geometry.

The F-16 does not display TA directly. It displays the '''Aspect Angle (AA)''', which is the supplementary angle of TA (AA = 180° − TA). A tail-aspect shot has AA 0; a head-on shot has AA 180.
[[File:AAvsTA.webp|thumb|600x600px]]
Common TA labels used in brevity:
{| class="wikitable"
!TA
!AA
!Label
|-
|0°–30°
|150°–180°
|Hot
|-
|31°–75°
|105°–149°
|Flank
|-
|76°–110°
|70°–104°
|Beam
|-
|111°–150°
|30°–69°
|Drag
|-
|151°–180°
|0°–29°
|Cold
|}

==== Cut ====
Cut is the angle from the '''Fighter Heading (FH)''' to the '''Bandit Reciprocal (BR)'''. It describes where your nose is pointing relative to the bandit's course.

Cut is an older concept but remains one of the most useful tools for predicting how the geometry will evolve. Three reference cases:

* '''Cut greater than Collision Course''' — your nose is in front of the bandit. Over time, TA decreases and Lateral Separation decreases. You are closing the geometry aggressively.
* '''Cut equal to Collision Course''' — the magic case. TA is captured: it does not change. Lateral Separation decreases. If co-altitude, you will eventually collide.
* '''Cut less than Collision Course (Zero-Cut / Parallel)''' — your nose points at the bandit's reciprocal. TA increases over time. Lateral Separation is captured: it does not change.
* '''Cut-Away''' — your nose points away from the bandit entirely. Both TA and Lateral Separation increase. Used to build angles or lateral room.

==== Degrees to Go (DTG) / Heading Crossing Angle (HCA) ====
DTG is the number of degrees the fighter needs to turn to be '''parallel''' to the bandit's flight path. It is the supplementary angle of Cut. A useful memory aid: ''Degrees to Go — where? Parallel.''

==== Lateral Separation (LS) ====
Lateral Separation is the perpendicular distance between the two flight paths. It determines how much maneuvering room exists for a conversion. It is approximated as:
LS (ft) = TA × SR × 100
Where SR is slant range in nautical miles. Lateral Separation matters most when planning a stern conversion or assessing whether a shot is geometrically viable.

==== Direction of Passage (DOP) ====
DOP describes the direction the bandit would cross your flight path if neither aircraft maneuvered. Called as left-to-right or right-to-left. Useful shorthand for building SA quickly.

==== Slant Range (SR) ====
[[File:SlantRange.webp|thumb|500x500px|center]]
The straight line-of-sight distance between the two aircraft in three-dimensional space. On the F-16 FCR this is the range displayed on the scope.

=== Pursuit Types ===
[[File:Pursuit.webp|thumb|700x700px|center]]
The type of pursuit describes where your nose is pointing relative to the target.
{| class="wikitable" style="width:100%;"
!Pursuit Type
!Nose Position
!Common Use
|-
|'''Lead Pursuit'''
|In front of the target
|Collision Course, gun employment from RQ
|-
|'''Pure Pursuit'''
|Directly at the target
|Simple conversions; commonly overused by new pilots
|-
|'''Lag Pursuit'''
|Behind the target
|Geometry management, WVR maneuvering
|}

== BFM III — Offensive BFM ==
Offensive BFM begins with you in a position of advantage. The bandit is somewhere in your forward hemisphere and your job is to convert that advantage into a weapons solution before he can deny it.

=== The Turn Circle ===
Every maneuvering aircraft has a turn circle, the circular path it is flying at any given moment. To employ weapons on the bandit you must get inside his turn circle, or at minimum align with it. Getting outside means you are turning wider than he is and falling behind.

The cue for turn circle entry is a high LOS rate (see below). As you approach the edge of the bandit's circle the bandit will begin moving rapidly across your field of view. Turn at that moment. Turn too early and you cross inside his radius, giving him a reversal opportunity. Turn too late and you end up outside his circle with AA too high to employ.

=== Line of Sight Rate ===
Line of Sight (LOS) rate is the speed at which the bandit moves across your field of view. It is one of the most important diagnostic tools in BFM and appears throughout offensive, defensive, and high aspect engagements.

A high LOS rate means the bandit is moving quickly across your canopy. A low or zero LOS rate means the bandit is stable relative to your nose. LOS rate tells you two things:

* '''Where are you relative to the bandit's turn circle'''? A sudden spike in LOS rate signals that you have reached the edge of his turn circle. Inside his circle, LOS rate is high. Outside it, LOS rate is low.
* '''What is the Geometry doing?''' Aft LOS movement means the bandit is drifting toward your 6; forward LOS movement means he is drifting toward your 12. The direction and speed of that drift tells you whether the geometry is improving or deteriorating.

Learning to read LOS rate is not an instrument skill. It is a visual habit and requires practice.

=== The Control Zone ===
The control zone is the offensive firing position, located in the bandit's rear quarter. From the control zone you have sufficient range for weapon employment, a manageable aspect angle, and controlled closure.

Getting into the control zone is not enough. You must '''assess''' before employing. The assessment uses the '''Rule of Threes''':
{| class="wikitable" style="width:100%;"
!Parameter
!Value
!Notes
|-
|Range
|~3,000 ft
|Read from HUD or FCR
|-
|Aspect Angle
|≤30°
|Draw an imaginary box around the bandit — square silhouette means ~30° AA
|-
|Closure
|Steady and controlled
|Not increasing, not zero
|}
All three must be satisfied before moving in for a gun solution. If any are not met, reposition first.

=== Repositions ===
Repositions are controlled adjustments to fix range, closure, or aspect problems from the control zone.

==== Lead Reposition ====
Used when the bandit is pulling away and range is increasing. Pull lead pursuit to close the gap. Do not overshoot.

==== Lag Reposition ====
Used when closure is too high. Pull lag pursuit to slow closure and improve aspect. The bandit will drift aft in your field of view. Reassess once closure is controlled.

==== Ease Reposition ====
Used when range and closure are acceptable but aspect is slightly high. Ease back on the stick to widen your turn circle slightly. AA will decrease as the geometry opens. Once AA is acceptable, resume the original pull and reassess. This is a small correction — if aspect is significantly high, use a lag reposition instead.

=== Visual Aspect Estimation ===
Without looking at instruments, AA can be estimated by the shape of the bandit's silhouette:

* '''Rectangle''' (fuselage longer than wingspan) means AA is above 30°, too high for a clean gun solution
* '''Square''' (fuselage approximately equal to wingspan) means AA is approximately 30°, Rule of Threes satisfied
* '''Narrowing toward a point''' means AA is near 0°, pure tail-aspect

This visual check is faster than any instrument cross-check in a close turning fight.

=== Weapon Employment ===

==== Heat Seeker (FOX-2) ====
A valid FOX-2 shot requires a confirmed seeker tone and AA within the missile's acquisition envelope, typically ≤60° for rear-quarter shots. Do not fire without tone. At significant AA the seeker may struggle to acquire, so use a lag or ease reposition to reduce AA before attempting the shot.

==== Guns ====
A valid gun solution requires the Rule of Threes to be fully satisfied with the pipper placed on the bandit. In a turning fight this requires lead pursuit. Your nose must be ahead of the bandit's projected path, not pointed at him. The amount of lead required varies with range and closure rate.

A tracking shot requires the pipper to remain on the bandit for a sustained period. A snapshot is a momentary pipper-on opportunity taken when it presents itself, lower probability but sometimes the only option available.

=== The Quarter Plane ===
The quarter plane is a last-resort maneuver used when closure rate has become dangerously high and an overshoot is imminent. It is not a reposition.

The cue to act is approximately 1,000 ft of range, at which point the bandit's wingspan will fill roughly half the EEGS funnel on the HUD.

Execution:

# Roll wings level with the horizon
# Set idle power
# Pull maximum performance up and out of the bandit's plane of motion

This arrests closure and separates you vertically from the bandit's plane. Once clear, roll back into a turn toward the bandit and reassess. The quarter plane costs significant energy and altitude. Use it only when nothing else will prevent the overshoot.

=== Common Errors ===
{| class="wikitable" style="width:100%;"
!Error
!Consequence
!Correction
|-
|Late turn circle entry
|End up outside the bandit's circle with AA too high
|Watch for the LOS rate spike and turn at that moment
|-
|Early turn circle entry
|Cross inside bandit's radius, give him a reversal picture
|Wait for the LOS rate spike
|-
|Firing without satisfying Rule of Threes
|Low probability shot
|Reposition first, assess before employing
|-
|Pure pursuit at significant AA
|Missile must curve hard, degraded effectiveness
|Use CC or LC geometry for missile employment
|-
|Uncontrolled closure
|Overshoot, offensive position lost
|Use lag reposition early, quarter plane as last resort
|-
|Spending energy without reason
|Slow speed, large radius, advantage lost
|Maintain AB, only pull above sustained rate for a specific reason
|}

== BFM IV — Defensive BFM ==
This part is based on [https://www.youtube.com/playlist?list=PLd5Qdmhmp3Y5-SDJjOzuUqV3m3mmuieTQ this] video series by [https://www.youtube.com/@TheOpsCenterByMikeSolyom The Ops Center by Mike Solyom].

The objectives of defensive BFM are, in order of priority: survive, deny the bandit a weapons solution, and create the conditions for a role reversal. Survival is the primary objective. A fighter that remains in the fight presents a continuous problem to the attacker — he must maintain focus on the defender, consuming energy and attention that could otherwise be used offensively. Every second the defender survives is a second for supporting elements to close.

=== The Defensive Gameplan ===
The foundation of defensive BFM is the sustained rate turn. The defender should establish and maintain best sustained turn rate as the default gameplan. This accomplishes two things simultaneously: it maximizes the defender's turn performance for the duration of the engagement, and it preserves energy for subsequent maneuvering.

Deviation from the sustained rate gameplan should only occur when a specific threat — an imminent gun or missile shot — requires a more aggressive response. Expending energy prematurely leaves the defender slow, with a large turn radius and reduced options.

=== Cross-Check Discipline ===
In defensive BFM the pilot's attention is predominantly outside the cockpit on the bandit. However, three parameters must be periodically cross-checked throughout the engagement:
{| class="wikitable" style="width:100%;"
!Parameter
!Significance
|-
|'''Lift Vector'''
|Determines plane of motion and available turn rate
|-
|'''G'''
|Confirms correct turn performance is being applied
|-
|'''Airspeed'''
|Identifies energy state; confirms sustained rate speed is maintained
|}
The cross-check must not interrupt tally on the bandit for extended periods. Brief instrument scans returning immediately to visual are the correct technique. Loss of tally in a defensive engagement is a significant threat to survival.

=== Altitude Management ===
Altitude is a reserve of potential energy. Trading altitude for airspeed in a defensive turn temporarily increases available turn rate above the Ps = 0 line by lowering the lift vector below the horizon. This option is only available until the floor is reached. At that point the defender is constrained to a level sustained rate turn and loses the altitude trading option entirely.

=== Reading the Bandit's Intentions ===
The defender must continuously assess the bandit's pursuit course to anticipate his next action. The pursuit course is read visually:
{| class="wikitable" style="width:100%;"
!Pursuit Course
!Visual Cue
!Likely Intent
|-
|'''Pure pursuit'''
|Narrow nose-on profile
|Missile shot setup; seeker acquisition in progress
|-
|'''Lead pursuit'''
|Bandit's belly visible; nose pulled ahead of defender
|Gun shot imminent
|-
|'''Lag pursuit'''
|Top of bandit's aircraft visible; aft LOS movement
|Controlling closure; repositioning for follow-on attack
|}
Transition from lag to pure to lead is the signature sequence of an impending gun attack. Recognition of this sequence is the primary defensive cross-check task outside the cockpit.

Range assessment is equally important. The bandit's size relative to your field of view gives a continuous indication of closure. A bandit that fills a significant portion of your view is inside 2,500 ft and approaching gun parameters.

=== Maneuvers ===

==== Tighten Down ====
The tighten down is the first and most conservative response to a bandit closing into gun parameters. It is executed by increasing back pressure on the stick while already in a sustained rate turn, transitioning from sustained rate to a higher instantaneous turn rate.

The tighten down achieves two simultaneous effects. First, it rotates the defender's vulnerable rear quarter away from the attacker, driving the bandit outside the weapon employment zone. Second, the sudden airspeed reduction caused by the increased G creates a high closure rate problem for the attacker, forcing him to reposition to satisfy the Rule of Threes. This repositioning produces aft LOS movement and potentially a reversal picture.

The tighten down is an energy expenditure. It should be released once the immediate threat is defeated, returning to slightly below sustained rate and allowing AB to restore the energy state.

==== Out-of-Plane Maneuver (OOP) ====
The out-of-plane maneuver removes the defender from the attacker's plane of motion, forcing the attacker to reset his geometry. In a sustained rate turn both aircraft are operating in approximately the same plane of motion. Moving out of that plane disrupts the attacker's sight picture and solution geometry.

Execution:

# Unload the aircraft — reduce back pressure to below 1G
# Reposition the lift vector off the bandit, above or below his plane of motion
# Apply smooth back pressure to establish a turn in the new plane of motion
# Allow sufficient time for the aircraft to develop movement in the new plane before any follow-on maneuver
# Assess LOS rate and bandit pursuit course in the new plane

The unloaded roll is critical. Rolling while pulling G consumes energy without producing useful turning room. The unload must precede the roll.

Upon establishing the new plane of motion, assess for a reversal opportunity. If high aft LOS rate combined with high HCA and close range is observed, a reversal may be executed. Otherwise, continue maneuvering in the new plane.

==== Jink ====
The jink is a last-resort maneuver executed when a gun shot is assessed as imminent and neither the tighten down nor the OOP has defeated the attacker's solution. It combines elements of both into a single aggressive sequence designed to spoil the attacker's plane of motion and create a closure problem simultaneously.

Execution:

# Set throttle to idle
# Unload the aircraft
# Position the lift vector below the bandit
# Apply maximum onset rate back pressure and hold until aerodynamic buffet onset

The resulting airspeed reduction is severe and deliberate. The attacker is presented with a sudden, unforecast closure rate and a simultaneous change in plane of motion. If the attacker does not immediately reposition he will overshoot. If he does reposition, aft LOS movement will develop and a reversal picture may emerge.

If a reversal picture does not present after the first jink, execute a second jink to the opposite side:

# Idle power maintained
# Unload
# Reposition lift vector to the opposite side of the bandit
# Maximum onset back pressure

Continue until the attacker is forced into lag or a reversal picture develops. The jink sequence trades altitude at a high rate. Do not initiate within 1,500 to 2,000 ft of the floor. The jink is the highest energy expenditure maneuver in defensive BFM and is reserved strictly for imminent gun shot situations.

=== The Reversal ===
A reversal is a turn at an opportune moment in the opposite direction, executed to transition from a defensive position to a neutral or offensive one. Correctly timed, a reversal exploits the attacker's angles and closure to reposition the defender onto an advantageous bearing. Incorrectly timed, it degrades the defender's position further.

The opportunity for a correct reversal is rare and may only be available for a few seconds. More often than not a reversal will degrade the situation rather than improve it. Patience and recognition of the correct picture are essential.

==== The Reversal Picture ====
The reversal picture is the combination of visual conditions that indicate a reversal opportunity exists:

* High heading crossing angle (HCA), combined with
* Close range, and or high aft LOS rate

A practical assessment question: ''does it appear that the bandit will cross behind my tail with minimal assistance from me?'' If the answer is yes, execute. If there is any doubt, do not reverse. A premature reversal presents the attacker with a stable, predictable target and makes his job easier.

==== Execution ====
The reversal is executed using an unloaded roll:

# Reduce back pressure to unload the aircraft
# Roll to the opposite direction
# Resume back pressure once established in the new turn
# Shift visual focus to the opposite side to regain tally on the bandit

Lift vector placement after the reversal depends on range. At close range, position the lift vector above or below the bandit to build turning room before pulling into his plane of motion. At greater range, place the lift vector directly on the bandit.

A successful reversal will typically result in a scissors — a neutral position from which either pilot may gain an advantage. This is a significant improvement over the defensive.

=== Maneuver Selection Summary ===
{| class="wikitable" style="width:100%;"
!Situation
!Maneuver
!Notes
|-
|Bandit in lag or pure pursuit, not yet in gun parameters
|Sustained rate turn
|Conserve energy; maintain cross-check
|-
|Bandit transitioning to lead pursuit, gun shot developing
|Tighten down
|First response; moderate energy cost
|-
|Tighten down insufficient; bandit maintaining solution
|Out-of-plane maneuver
|Disrupts attacker geometry; assess for reversal
|-
|Gun shot imminent; no other option
|Jink
|Last resort; high energy cost; do not use prematurely
|-
|Reversal picture present
|Reversal
|Execute with unloaded roll; if in doubt, do not reverse
|}

== BFM V — High Aspect BFM ==
This part is based on [https://www.youtube.com/playlist?list=PLd5Qdmhmp3Y5-SDJjOzuUqV3m3mmuieTQ this] video series by [https://www.youtube.com/@TheOpsCenterByMikeSolyom The Ops Center by Mike Solyom].

High aspect BFM occurs when neither aircraft has a positional advantage at the merge. Both aircraft are nose-to-nose and the engagement begins from a neutral position. The name comes from the fact that at the merge, both aircraft are presenting high aspect to each other.

There are two reasons a pilot ends up in a high aspect fight. Either the bandit turns his nose toward you at the conclusion of a BVR intercept, or a BFM error led to the loss of an offensive position. The response is the same in either case.

=== The Lead Turn ===
The lead turn is the single most important concept in high aspect BFM. It is executed before the merge and determines the starting position of the fight.

Rather than waiting until the bandit's 3-9 line to begin turning — which produces a neutral merge — the pilot initiates the turn early. This builds an angular advantage before the first pass. At the sustained turn rate of the F-16, every additional second of turn produces more than 10° of angular advantage that the bandit must make up. Even two seconds of early turning can produce an advantage that a bandit in the same aircraft cannot recover from.

The lead turn cue is a rapidly increasing LOS rate from 11 to 10 o'clock for a left-side pass, or 1 to 2 o'clock for a right-side pass. This is the correct moment to turn. Turning too late leaves you behind the bandit with an energy problem. Turning too early gives the bandit a reversal picture.

If the lead turn is started too late there is little that can be done — accept the problem and manage it. If the lead turn is started too early, ease off the G momentarily until the bandit's LOS rate resumes, then resume the pull.

When executed correctly, the lead turn produces a '''stern conversion''' — the pilot arrives at the bandit's six o'clock within gun range without requiring further maneuvering.

=== Turning Room ===
Turning room is the separation between the two aircraft that is available to turn into. It can be built vertically or laterally, but not to the outside of the bandit's turn circle — floating to the outside gives the bandit more time and reduces the available turning room before the merge.

Vertical turning room is built during the check-away turn by climbing or descending. The direction of the climb or descent affects energy state at the merge, which must be managed using the '''energy atom''':

* Descending toward the bandit: expect to arrive approximately 100 KCAS faster than the bandit's speed. Start approximately 100 KCAS slow to compensate.
* Climbing toward the bandit: expect to arrive approximately 100 KCAS slower. Start approximately 100 KCAS fast.
* Co-altitude: fly at the bandit's briefed speed.

These figures are approximate and must be adjusted based on the specific altitude differential involved.

=== Determining Fight Geometry ===
At the merge, the direction the bandit turns determines the geometry of the fight. '''The last aircraft to turn decides whether the engagement becomes a one-circle or two-circle fight.''' This is a deliberate choice — a pilot who executes a lead turn gives up the ability to choose the fight geometry, because the bandit turns last. The lead turn advantage is generally worth this tradeoff.

* '''Bandit turns toward you''' → two-circle fight. Both aircraft chase each other's tails. Ground track resembles two separate circles.
* '''Bandit turns away from you''' → one-circle fight. Both aircraft circle back toward each other for a second nose-to-nose pass. Ground track resembles a single circle.

Identifying which geometry has been established requires only one visual check: if the bandit is nose-to-tail relative to you, it is a two-circle fight. If it is nose-to-nose, it is a one-circle fight.

=== Losing Tally ===
Losing visual on the bandit in a turning fight is dangerous. Two rules apply immediately:

'''Do not fly straight and level while searching.''' Straight flight makes the defender's job trivial. Maintain the turn at all times.

'''Search along the turn circle.''' The bandit's most likely position is in the high-probability kill zone behind and above — the high-Pk WEZ. When the area behind you is clear, scan upward along the turn circle. The bandit will be somewhere along that arc if still engaged.

Procedures/78th/A2A/BFM

2026-05-23T16:53:44Z

Niknam3: /* Altitude Management */

MTTP/A2A

2026-05-23T16:35:56Z

Niknam3: /* Talk-On */

== 01 / Overview ==
Air combat is primarily carried out by CAP aircraft. The two main mission types are '''DCA''' (Defensive Counter Air) and '''OCA''' (Offensive Counter Air).

=== Groups and Contacts ===
A '''GROUP''' is any number of air contacts within 3 nm in azimuth and range of each other. A '''CONTACT''' is an individual radar return within a GROUP. Single contact is the assumed strength for all GROUPs unless otherwise specified. A GROUP with three or more contacts is called '''HEAVY'''.

The '''PICTURE''' establishes a common tactical air image and describes the spatial relationship of GROUPs. It is always communicated in BULLSEYE format unless briefed otherwise. Only the Three GROUPs with highest Priority are Conveyed

=== Contact Declaration ===
Before a fighter can engage, a contact must be declared. Declaration is performed by the controller in response to a DECLARE request.

{| class="wikitable" style="width:100%;"
|-
! Declaration !! Meaning !! Engagement Authority
|-
| '''BOGEY''' || Identity unknown || Not cleared to engage
|-
| '''OUTLAW''' || Originates from known or suspected hostile area || Not cleared to engage; escalation criteria apply
|-
| '''SPADES''' || No valid IFF response on interrogation || Not cleared to engage; escalation criteria apply
|-
| '''BANDIT''' || Positively identified as enemy IAW theater ID criteria || Not cleared to engage; does not imply authority to fire
|-
| '''HOSTILE''' || Confirmed enemy; clearance to fire authorized IAW ROE || Cleared to engage
|-
| '''NEUTRAL''' || Positively identified as neutral || Not cleared to engage
|-
| '''FRIENDLY''' || Positively identified as friendly || Not cleared to engage
|-
| '''FURBALL''' || Friendly and non-friendly aircraft within 5 nm || Employment not authorized until resolved
|}

A BOGEY, BANDIT, OUTLAW, or SPADES classification does not authorize engagement. HOSTILE is the only declaration that authorizes weapons employment IAW ROE.

== 02 / Important Concepts ==

=== Communication Cadence by Phase ===
Communication priority shifts between the controller and fighters depending on the phase of the intercept.

{| class="wikitable" style="width:100%;"
|-
! Phase !! Priority Communicators
|-
| Pre-COMMIT / Marshal || 1. Controller · 2. Fighters
|-
| Post-COMMIT / Push || 1. Controller · 2. Fighter
|-
| Targeting / Weapons Employment || 1. Fighters · 2. Controller
|-
| Merge || 1. Engaged Fighter · 2. Supporting Fighters · 3. Controller
|-
| Post-Merge || 1. Fighter Clearing Merge · 2. Supporting Fighters · 3. Controller
|}

=== TAC Range ===
Called at 60 nm (default) by the first asset to recognize the separation. Signals all players to prepare for targeting. Pre-commit SA building continues until this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Fighter || {CS} {Group Label} TAC RANGE
|}

=== Airspace Sanitization ===
A Section consists of two aircraft, each equipped with its own radar. Regardless of the number of bars or maximum azimuth a single radar supports, no single system can cover the entire sky. To compensate, both radars are stacked and assigned to different portions of the airspace — each portion is called an '''Area of Responsibility (AOR)'''. This technique, known as '''Radar Mating''', vastly increases the total volume scanned and ensures that no unknown contacts are operating in the area beyond already-tracked groups. The exact parameters depend on the aircraft type: the US Navy recommends RWS, 140°, 6 bars, end scale 80 nm, with radars mated at 25 nm: placing the flight lead between 40,000 and 15,000 ft, and the wingman from ground level to 25,000 ft.

The process of actively scanning assigned AORs to confirm no unknown contacts are present is called '''Sanitisation'''.

Because both Radar Mating parameters and Sanitisation responsibilities directly affect how an engagement develops, all of this must be '''pre-briefed''' and set as a '''contract''' before the mission. Time pressure may not always permit a thorough sanitisation pass, and how to handle that contingency should likewise be agreed upon in the brief.

=== Targeting ===
The flight assigns GROUP responsibility and confirms classification.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} DECLARE {Group Label or Bullseye Position}
|-
| Controller || {Group Label} DECLARED {HOSTILE / BOGEY / FRIENDLY / UNABLE / FURBALL}
|-
| FL || {CS} TARGET {Group Label} {Tactic}
|-
| colspan="2" style="text-align:center;" | ''Once group appears on radar''
|-
| FL || {CS} TARGETED {Group Label} BULLSEYE {Bearing/Range}
|-
| Controller || ''No response if information correlates. Comparative response if correction is required.''
|}

== 03 / Common Calls ==

=== DECLARE ===
Inquiry as to the identity of a specified GROUP. Full positional data in BULLSEYE format must accompany all responses.
MIKE, EAGLE 11, DECLARE NORTH GROUP.
EAGLE 11, NORTH GROUP BULLSEYE 2-7-3/27, TWENTY-TWO THOUSAND, TRACK EAST, BOGEY SPADES.

=== BOGEY DOPE ===
Request for BRAA information on the indicated GROUP or the closest GROUP if not specified. Does not imply fighter targeting.
MIKE, EAGLE 11, BOGEY DOPE NORTH GROUP.
EAGLE 11, NORTH GROUP BRAA 2-1-0/28, THIRTY-EIGHT THOUSAND, HOT, HOSTILE.

=== NAILS ===
Fighter's radar warning receiver is detecting an airborne interceptor radar in search mode. Called with bearing or cardinal direction.
EAGLE 1, NAILS 2-7-0.

=== SPIKED ===
Fighter is being actively tracked by an airborne radar. Called with bearing or cardinal direction. Controller correlates to a GROUP within ±30 degrees and responds with range, altitude, aspect, declaration, and GROUP name.
EAGLE 1, SPIKED 2-7-0.
EAGLE 1, SPIKE RANGE 17, THIRTY THOUSAND, HOSTILE EAST GROUP, TWO CONTACTS.

=== THREAT Call ===
If a fighter will pierce THREAT range to an untargeted GROUP, the controller makes a THREAT call in BRAA format no later than THREAT range.
HEAT 31, ADDITIONAL GROUP THREAT, BRAA 1-2-5/35, THIRTY-FIVE THOUSAND, HOT, HOSTILE.

If the THREAT is within 5 nm of friendly fighters:
BOLT 1, THREAT NORTH THREE, TEN THOUSAND, TRACK SOUTH, HOSTILE.

=== FADED and VANISHED ===
'''FADED''' — a previously tracked GROUP not updated by sensors for 30 seconds. The controller reports the GROUP as FADED with last known BULLSEYE position. Fighters maintain MONITOR responsibility if they can maintain correlation. FADED is not used for friendly aircraft — controllers use NEGATIVE CONTACT for friendlies not held on sensors.

'''VANISHED''' — a special case of FADED used when the GROUP is not in a known blind zone and is correlated to a friendly shot that meets parameters for successful termination.

=== Unexpected Contacts ===
Three distinct call types exist for contacts not part of the established picture:

{| class="wikitable" style="width:100%;"
|-
! Call !! Criteria !! Format
|-
| '''ADDITIONAL GROUP''' || Newly detected outside targeting range, or does not fit traditional label || BULLSEYE
|-
| '''POP-UP GROUP''' || Previously undetected; appears inside targeting range but outside THREAT range || BULLSEYE
|-
| '''THREAT GROUP''' || Undetected or unreported GROUP meeting briefed THREAT criteria || BRAA to the closest aircraft
|}

DARKSTAR, POP-UP GROUP BULLSEYE 2-7-0/15, FIVE THOUSAND, TRACK WEST, BOGEY SPADES.
RAMBO 2, THREAT GROUP BRAA 2-7-0/13, ONE THOUSAND, HOT, HOSTILE.

== 04 / Engagement ==
The engagement loop is the core sequence executed by all fighter flights once committed and targeting is established. It repeats until the GROUP is splashed, leaves the area, or the flight resets.

=== MELD ===
The flight lead directs all flight members to shift their radars from wide sanitization to focused SA on the assigned GROUP. This transition narrows the radar from maximum azimuth and altitude coverage to a tighter volume centered on the target. Sanitization of the surrounding airspace ceases until DROPPING is called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''All flight members shift radar from sanitization to the assigned GROUP''
|}

=== SORT ===
The flight lead assigns individual contacts within the GROUP to specific flight members. Each member acknowledges with SORTED when they have confirmed their assigned contact on radar and are prepared to engage it. If a member cannot confirm their assigned contact, SORTED is withheld until resolution.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || ''(intraflight) FLIGHT SORT {Criteria}''
|-
| #2 || ''(intraflight) #2 SORTED''
|-
| #3 || ''(intraflight) #3 SORTED''
|-
| #4 || ''(intraflight) #4 SORTED''
|}

=== JUDY ===
Called by the flight lead when the flight no longer requires controller guidance to prosecute the intercept. From this point, the controller minimizes transmissions and provides situational awareness information only. JUDY is not always called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Provides SA and THREAT calls only.''
|}

=== ENGAGE ===
Directive call from the flight lead to a specific wingman to employ weapons. The flight lead may also direct simultaneous employment by multiple members.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} ENGAGE
|-
| Wingman || {CS}
|}

=== Weapon Employment ===
The firing aircraft calls the shot on TACC2 NET immediately after employment. The call includes shot type, GROUP label, contact description, BULLSEYE position, and altitude. The controller acknowledges with COPY SHOT.

If a fighter determines a GROUP HOSTILE and ROE has been met, the fighter may employ autonomously and include HOSTILE in the shot transmission.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft || {TACC2-CS} {CS} FOX THREE {Group Label} {Contact Description} BULLSEYE {Bearing/Range} {Altitude}
|-
| TACC2 || {TACC2-CS} COPY SHOT
|-
| colspan="2" style="text-align:center;" | ''Autonomous HOSTILE employment''
|-
| Firing Aircraft || {Controller-CS} {CS} FOX THREE {Group Label} BULLSEYE {Bearing/Range} {Altitude} HOSTILE
|-
| TACC2 || {TACC2-CS} COPY SHOT
|}

Multiple shots in one transmission are acceptable:
SHADOW12 FOX THREE NORTH GROUP LEAD CONTACT BULLSEYE 2-7-0/20 TWENTY THOUSAND; SHADOW11 FOX THREE NORTH GROUP TRAIL CONTACT.

=== OUT / DEFENDING ===
Following weapon employment the flight turns away from the threat. OUT is a planned maneuver executed at a prebriefed range. DEFENDING indicates a reactive maneuver against an incoming weapon and is called with the cardinal direction of the defensive turn.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction}
|-
| colspan="2" style="text-align:center;" | ''or, if reacting to an incoming weapon''
|-
| Aircraft || {CS} DEFENDING {Direction}
|}

=== DROPPING ===
May be called in conjunction with OUT. Signals the controller that the flight has ceased monitoring the GROUP and is returning to sanitization radar settings. Monitoring responsibility transfers back to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction} DROPPING {Group Label}
|-
| colspan="2" style="text-align:center;" | ''Controller resumes monitoring of the dropped GROUP''
|-
| Controller || ''Resumes monitoring.''
|}

=== Assessment ===
The flight assesses weapon effects from sensor data or controller reports. Three outcomes are possible:

{| class="wikitable" style="width:100%;"
|-
! Outcome !! Action
|-
| GROUP splashed || Call SPLASH
|-
| GROUP remains a factor, follow-up shot required || Turn IN, return to MELD
|-
| GROUP has left the area or is no longer a factor || Proceed with Tasking
|}

=== IN (Follow-up Engagement) ===
If the GROUP remains a factor and the tactic permits a follow-up shot, the flight turns back toward the GROUP. The IN call triggers a new cycle beginning at MELD.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IN {Direction}
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''Re-sort as required, then return to ENGAGE''
|}

=== SPLASH ===
Called when weapon effects confirm the GROUP or contact is destroyed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft or Controller || {CS} SPLASH {Group Label or Contact Description}
|}

----

== 05 / Defensive Counter Air (DCA) ==
DCA is the use of fighter aircraft to defend a ground asset or airspace against hostile air threats. It uses prebriefed lanes and defined ranges.

=== DCA Range Structure ===
All ranges are prebriefed per sortie. The following are the standard range lines used in DCA:

{| class="wikitable" style="width:100%;"
|-
! Range Line !! Definition
|-
| '''Mission Fail Line''' || The line the enemy must not cross for the mission to succeed. Defines the maximum depth of the defensive problem.
|-
| '''Commit Line (CL)''' || The line at which a bogey is declared HOSTILE IAW theater ROE and the flight is authorized to commit. Prebriefed for all DCA sorties.
|-
| '''Targeting Range''' || The prebriefed distance at which all contacts must be intercepted. A GROUP inside this range with no assigned fighter is UNTARGETED. Prebriefed per sortie.
|-
| '''TAC Range''' || Default 60 nm from the closest fighter to the closest GROUP. Signals all players to prepare for targeting.
|-
| '''Threat Range''' || The prebriefed range at which an untargeted GROUP meeting THREAT criteria triggers a THREAT call. Prebriefed per sortie.
|}

=== COMMIT Authority ===
COMMIT authority is derived from the combatant commander and delegated through the chain of command. Any of the following may hold or recommend COMMIT authority depending on what is delegated:

{| class="wikitable" style="width:100%;"
|-
! Role !! Abbreviation !! Authority
|-
| Flight Lead || FL || Usually holds COMMIT authority unless delegated
|-
| Team Lead || TL || May hold COMMIT authority if delegated
|-
| Mission Commander || MC || May hold COMMIT authority if delegated
|-
| TACC2 || — || May hold COMMIT authority if delegated
|}

If only the MC, TL, or FL holds COMMIT authority, the controller may only recommend COMMIT. If the controller holds COMMIT authority, the MC and TL may only recommend.

=== DCA Flow ===

==== Lane Handover ====
When an outgoing flight is relieved on station by an incoming flight, a positive lane handover is required before the outgoing flight departs.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Off-going Lane Commander || {CS} MOVE FORWARD
|-
| On-coming Lane Commander || {CS}
|-
| colspan="2" style="text-align:center;" | ''On-coming aircraft may enter the lane. Lane commander authority has not yet transferred.''
|-
| Off-going Lane Commander || {CS} YOU HAVE THE LANE
|-
| On-coming Lane Commander || {CS} HAS THE LANE
|}

The off-going flight passes critical mission information to the controller before departing. The controller passes big-picture information to the on-coming flight before pushing them to the tactical frequency.

==== Pre-Commit ====
The flight arrives at its prebriefed CAP position with FENCE IN complete and radars in sanitization configuration. The controller holds picture responsibility.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} PICTURE
|-
| Controller || {CS} {Nr of Groups} {Group Label} BULLSEYE {Bearing/Range} {Altitude} TRACK {Direction} {Declaration} {Nr of Contacts}
|}

The flight evaluates commit criteria continuously. Pictures are requested as needed to maintain SA.

==== Commit ====

===== FIGHTER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} Recommend {CS} COMMIT
|-
| FL || {CS} COMMIT
|}

===== CONTROLLER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} Recommend Commit
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} {CS} COMMIT
|-
|FL
|{CS}
|}

After COMMIT, fighters hold radio priority.

=== Engagement Loop ===
The flight executes the standard engagement loop as defined above The loop repeats until the GROUP is splashed, leaves the lane, or:

Once the Engagement is Complete the flight '''RESETS''' back to the briefed Position

==== RESET ====
Directs the flight to return to its prebriefed position or area of operations. RESET implies DROPPING and returns all targeting responsibility to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} RESET
|-
| colspan="2" style="text-align:center;" | ''Flight returns to prebriefed CAP position. Controller resumes full picture responsibility''
|}

----

== 06 / Offensive Counter Air (OCA) ==
OCA is the use of fighter aircraft to suppress, destroy, or neutralize enemy air assets before they can threaten friendly forces. Unlike DCA, OCA is not lane-based and does not require a commit line. The flight pushes into the threat environment rather than waiting for the threat to approach.

=== OCA Range Structure ===
The same range lines apply as in DCA — Threat Range, Targeting Range, and TAC Range — but all are prebriefed based on the specific mission geometry and threat environment. There is no commit line or mission fail line in OCA.

=== OCA Flow ===
OCA does not have a lane handover or a commit phase. The flight checks in, receives the picture, establishes targeting, and executes the engagement loop.

==== FULL COMMUNICATIONS EXAMPLE ====
In this Scenario, SHADOW11 four-ship F16C on OCA. TACC2 Agency CS THUMPER executing Positive Control. The Example begins after the Handover. Check In was done on the previous Frequency. TAC RANGE 60, THREAT RANGE 30
THUMPER SHADOW11 PICTURE

THUMPER PICTURE TEN GROUPS GROUP BULLSEYE 0-2-0/25, TWENTY-SEVEN THOUSAND, THOUSAND, TRACK EAST, HOSTILE, HEAVY, THREE CONTACTS. GROUP BULLSEYE 2-7-0/25, FIFTEEN THOUSAND, TRACK WEST, HOSTILE. GROUP BULLSEYE 2-9-0/35, TEN THOUSAND, TRACK WEST, HOSTILE.

SHADOW11 TARGETED GROUP BULLSEYE 0-2-0/25

SHADOW11 GROUP BULLSEYE 0-2-0/25 TAC RANGE

SHADOW11 SKATE, MELD

SHADOW11 SORTED

SHADOW11 FOX3 BULLSEYE 0-2-0/25

THUMPER COPY SHOT

SHADOW11 OUT SOUTH DROPPING

THUMPER

THUMPER SHADOW11 BOGEYDOPE

SHADOW11 EAST GROUP BRAA 2-1-0/28, FIFTEEN-THOUSAND, COLD, HOSTILE

SHADOW11 IN, MELD, SORTED

THUMPER SHADOW11 SPLASH EAST GROUP

THUMPER
In the Following Example additional Adversarys Pop Up within Threat Range of SHADOW11
SHADOW11 THREAT GROUP, BRAA 1-2-5/28, FIVE-THOUSAND, HOT, HOSTILE, 2 CONTACTS

SHADOW11 TARGETED, SORTED LEAD, FOX 3 LEADER, FOX3 TRAILER, BULLSEYE 0-5-0/45, FIVE-THOUSAND

THUMPER COPY SHOT

SHADOW11 DEFENDING SOUTH, DROPPING

THUMPER

SHADOW11 THUMPER THREAT GROUP, BRAA 0-6-0/15, TWO-THOUSAND, COLD, HOSTILE

SHADOW11

SHADOW11 IN

SHADOW11 FOX3 BULLSEYE 0-6-0/15, TWO-THOUSAND

THUMPER COPY SHOT

SHADOW11 THUMPER THREAT GROUP VANISHED
----

== 07 / QRA ==

== 08 / Intercept (VID) ==
A Visual Identification (VID) intercept is conducted when a contact cannot be declared HOSTILE or FRIENDLY by electronic means alone, and visual confirmation of aircraft type, markings, or behavior is required before engagement authority can be granted or withheld.

VID intercepts follow a structured sequence: the controller guides the fighter to a position from which a visual identification pass can be made, then the fighter reports the result and awaits further direction.

=== Intercept Flow ===

==== Commit ====
The controller or flight lead initiates the intercept against the unidentified contact.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} COMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration} {Nr of Contacts}
|-
| FL || {CS} COMMIT
|}

==== Guidance ====
The controller provides vectors to position the fighter for a VID pass. This is the only phase where the controller takes positive close control of the intercept geometry. BRAA format is used throughout.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} BRAA {Bearing/Range} {Altitude} {Aspect} {Declaration}
|-
| FL || {CS}
|-
| colspan="2" style="text-align:center;" | ''Controller continues to provide updated vectors until fighter calls JUDY''
|}

==== JUDY ====
The fighter calls JUDY when radar contact is established and no further controller guidance is required. The controller minimizes transmissions from this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Continues to provide SA information only.''
|}

==== Tally ====
The fighter calls TALLY when visual contact is established with the target.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} TALLY {Position}
|}

==== Identification ====
The fighter conducts the VID pass and reports the result to the controller. The report includes aircraft type, markings, and behavior observed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IDENTIFIED {Aircraft Type} {Markings / Behavior}
|-
| Controller || {CS} {Further Instructions / Declaration Update}
|}

If the contact is identified as HOSTILE following the VID pass, the controller issues the updated declaration and the flight may proceed to engagement IAW ROE. If the contact is FRIENDLY or NEUTRAL, the flight disengages and returns to its prebriefed position.

----

== 09 / Merge ==
A merge occurs when friendly and target aircraft arrive in the visual arena, within 3–5 nm of each other. At the merge, radar resolution becomes limiting and the engagement transitions from BVR to Within Visual Range (WVR). The engagement is now managed through ACM contracts and direct communication between flight members.

=== Authority and Radio Priority ===
Two distinct concepts govern merge communications: '''authority''' and '''radio priority'''.

'''Authority''' remains with the Flight Lead throughout the engagement. The FL can override, redirect, or terminate the engagement at any time regardless of who is engaged.

'''Radio priority''' belongs to the engaged fighter. Other flight members subordinate their transmissions to avoid stepping on critical engaged fighter calls. The controller minimizes transmissions entirely and provides only THREAT calls, SA updates, and responses to direct requests.

{| class="wikitable" style="width:100%;"
|-
! Role !! Authority !! Radio Priority
|-
| '''Flight Lead''' || Full authority over the engagement at all times || Secondary — subordinates to engaged fighter
|-
| '''Engaged Fighter''' || Manages own engagement IAW FL direction || Primary — holds radio priority
|-
| '''Supporting Fighter''' || Executes IAW engaged fighter and FL direction || Tertiary — transmits only when necessary
|-
| '''Controller''' || Provides SA only || Minimal — THREAT calls and direct requests only
|}

=== MERGED ===
The controller calls MERGED when radar tracks come together within 3–5 nm, or the engaged fighter calls it when visual contact is made at the merge.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Engaged Fighter || {CS} MERGED {Group Label}
|}

=== Role Assignment ===
At or before the merge, engaged and supporting roles must be clearly established. By default the flight lead is engaged. Roles can be assigned or transferred in two ways:

==== Wingman-Initiated Transfer ====
The wingman identifies he is the engaged fighter based on the bandit's plane of motion and lift vector orientation, and calls it.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Wingman || #2 ENGAGED
|-
| Flight Lead || PRESS
|}

==== Flight Lead-Initiated Transfer ====
The flight lead recognizes the wingman is the engaged fighter and assigns the role.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || #2 PRESS
|-
| Wingman || #2 ENGAGED
|}

==== Bandit Switches ====
If the bandit maneuvers to engage the other fighter, the currently engaged fighter communicates the change.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || BANDIT SWITCHED
|-
| colspan="2" style="text-align:center;" | ''Roles are reassessed and reassigned as required''
|}

=== Engaged Fighter SA Calls ===
The engaged fighter is responsible for narrating the fight to maintain the supporting fighter's situational awareness. This enables the supporting fighter to position correctly and employ at the right moment. SA calls include the fight geometry, altitude, and direction.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || {CS} ENGAGED {ONE / TWO CIRCLE} {Direction} {Altitude}
|}

VIPER 1, ENGAGED ONE CIRCLE CLIMBING THROUGH FIFTEEN THOUSAND.
VIPER 1, ENGAGED TWO CIRCLE NORTHBOUND BANDITS LOW TWO'S HIGH.

These calls are made continuously as the fight develops, not just once at the merge. The supporting fighter cannot position or employ safely without them.

=== STATUS Calls ===
STATUS is a request from the supporting fighter for a specific situational update from the engaged fighter. It is the primary tool for IFF at the merge. A generic STATUS call returns a general update. A specific STATUS call asks a targeted question and returns a more useful answer.

The supporting fighter should tailor the STATUS call to the specific information needed to resolve the IFF situation. Generic STATUS calls are acceptable but specific calls are faster and more effective.

{| class="wikitable" style="width:100%;"
|-
! Call !! Question Being Asked !! Example Response
|-
| '''STATUS''' || General situation update || ENGAGED ONE CIRCLE NORTHBOUND BANDITS LOW TWO'S HIGH
|-
| '''STATUS HIGH/LOW''' || Which aircraft is higher || BANDITS LOW TWO'S HIGH
|-
| '''STATUS NOSE HIGH/NOSE LOW''' || Which aircraft has nose above or below horizon || TWO'S NOSE HIGH BANDIT NOSE LOW
|-
| '''STATUS LEFT/RIGHT''' || Which aircraft is left or right || TWO'S LEFT BANDIT RIGHT
|-
| '''STATUS NORTH/SOUTH/EAST/WEST''' || Cardinal orientation of aircraft in the fight || TWO'S NORTH BANDIT SOUTH
|}

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || {CS} STATUS {Qualifier if applicable}
|-
| Engaged Fighter || {Specific SA answer to the STATUS question}
|}

Supporting Fighter: TWO STATUS HIGH LOW.
Engaged Fighter: BANDITS LOW TWO'S HIGH.

If a STATUS call returns an ambiguous response, rephrase with a more specific qualifier before resorting to a FLASH call.

As a last resort, a FLASH call can be used to add physical confirmation to IFF — for example FLASH FLARES or FLASH BURNER. This directs the wingman to briefly activate the specified system so the supporting fighter can visually confirm identity. Exercise extreme caution — the bandit may also be employing flares, and a mistaken identification cannot be undone.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || FLASH {FLARES / BURNER}
|-
| Wingman || ''(executes flash of specified system briefly)''
|}

=== IFF Brevity ===
Standard brevity calls for visual identification status:

{| class="wikitable" style="width:100%;"
|-
! Term !! Meaning
|-
| '''TALLY''' || Visual contact established on the target or bandit
|-
| '''NO JOY''' || No visual contact with the target or bandit
|-
| '''VISUAL''' || Visual contact established on a friendly aircraft
|-
| '''BLIND''' || No visual contact with a friendly aircraft
|}

IFF must be confirmed before employment. Do not rely on aircraft visuals alone — use STATUS calls to confirm orientation before taking a shot.

=== Talk-On ===
If the supporting fighter loses visual on the engaged fighter (BLIND) after the merge, the engaged fighter or flight lead can provide a talk-on to re-establish visual.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter or FL || {CS} {Clock Position} {Range} {Altitude Qualifier}
|}

VIPER 1, THREE O'CLOCK ONE AND A HALF MILES LOW.

Once visual is re-established:

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || {CS} VISUAL
|}

=== Employment ===
Once IFF is confirmed and a valid shot opportunity exists, the supporting fighter employs. The call includes weapon type and target description.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting or Engaged Fighter || {Controller-CS} {CS} FOX TWO {Target Description}
|-
| Controller || COPY SHOT
|}

Gun employment:

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting or Engaged Fighter || {Controller-CS} {CS} GUNS {Target Description}
|}

The flight lead retains authority to call NEGATIVE if employment is unsafe or premature, regardless of who holds radio priority.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || NEGATIVE {CS} {Reason if required}
|}

=== SPLASH ===
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged or Supporting Fighter || {Controller-CS} {CS} SPLASH {Target Description}
|-
| Controller || {CS} COPY SPLASH
|}

=== Bug Out ===
Following SPLASH, or when the flight lead determines the engagement should end, the supporting fighter directs the egress. The supporting fighter holds the best big-picture SA at this point and is best placed to select a safe egress direction.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || {CS} BUG OUT {Direction}
|-
| colspan="2" style="text-align:center;" | ''All flight members flow in the stated direction''
|}

VIPER'S BUG OUT 0-9-0.

If the flight lead was the supporting fighter and the wingman is now visual after the bug out, conventional flight roles are re-established:

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Wingman || {CS} VISUAL PRESS
|-
| Flight Lead || ENGAGED
|}

Following the bug out the flight calls RESET on the TAC C2 NET and returns to the prebriefed position unless directed otherwise.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || {Controller-CS} {CS} RESET
|}

MTTP/A2A

2026-05-23T15:52:14Z

Niknam3: /* 12 / Merge */

== 01 / Overview ==
Air combat is primarily carried out by CAP aircraft. The two main mission types are '''DCA''' (Defensive Counter Air) and '''OCA''' (Offensive Counter Air).

=== Groups and Contacts ===
A '''GROUP''' is any number of air contacts within 3 nm in azimuth and range of each other. A '''CONTACT''' is an individual radar return within a GROUP. Single contact is the assumed strength for all GROUPs unless otherwise specified. A GROUP with three or more contacts is called '''HEAVY'''.

The '''PICTURE''' establishes a common tactical air image and describes the spatial relationship of GROUPs. It is always communicated in BULLSEYE format unless briefed otherwise. Only the Three GROUPs with highest Priority are Conveyed

=== Contact Declaration ===
Before a fighter can engage, a contact must be declared. Declaration is performed by the controller in response to a DECLARE request.

{| class="wikitable" style="width:100%;"
|-
! Declaration !! Meaning !! Engagement Authority
|-
| '''BOGEY''' || Identity unknown || Not cleared to engage
|-
| '''OUTLAW''' || Originates from known or suspected hostile area || Not cleared to engage; escalation criteria apply
|-
| '''SPADES''' || No valid IFF response on interrogation || Not cleared to engage; escalation criteria apply
|-
| '''BANDIT''' || Positively identified as enemy IAW theater ID criteria || Not cleared to engage; does not imply authority to fire
|-
| '''HOSTILE''' || Confirmed enemy; clearance to fire authorized IAW ROE || Cleared to engage
|-
| '''NEUTRAL''' || Positively identified as neutral || Not cleared to engage
|-
| '''FRIENDLY''' || Positively identified as friendly || Not cleared to engage
|-
| '''FURBALL''' || Friendly and non-friendly aircraft within 5 nm || Employment not authorized until resolved
|}

A BOGEY, BANDIT, OUTLAW, or SPADES classification does not authorize engagement. HOSTILE is the only declaration that authorizes weapons employment IAW ROE.

== 02 / Important Concepts ==

=== Communication Cadence by Phase ===
Communication priority shifts between the controller and fighters depending on the phase of the intercept.

{| class="wikitable" style="width:100%;"
|-
! Phase !! Priority Communicators
|-
| Pre-COMMIT / Marshal || 1. Controller · 2. Fighters
|-
| Post-COMMIT / Push || 1. Controller · 2. Fighter
|-
| Targeting / Weapons Employment || 1. Fighters · 2. Controller
|-
| Merge || 1. Engaged Fighter · 2. Supporting Fighters · 3. Controller
|-
| Post-Merge || 1. Fighter Clearing Merge · 2. Supporting Fighters · 3. Controller
|}

=== TAC Range ===
Called at 60 nm (default) by the first asset to recognize the separation. Signals all players to prepare for targeting. Pre-commit SA building continues until this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Fighter || {CS} {Group Label} TAC RANGE
|}

=== Airspace Sanitization ===
A Section consists of two aircraft, each equipped with its own radar. Regardless of the number of bars or maximum azimuth a single radar supports, no single system can cover the entire sky. To compensate, both radars are stacked and assigned to different portions of the airspace — each portion is called an '''Area of Responsibility (AOR)'''. This technique, known as '''Radar Mating''', vastly increases the total volume scanned and ensures that no unknown contacts are operating in the area beyond already-tracked groups. The exact parameters depend on the aircraft type: the US Navy recommends RWS, 140°, 6 bars, end scale 80 nm, with radars mated at 25 nm: placing the flight lead between 40,000 and 15,000 ft, and the wingman from ground level to 25,000 ft.

The process of actively scanning assigned AORs to confirm no unknown contacts are present is called '''Sanitisation'''.

Because both Radar Mating parameters and Sanitisation responsibilities directly affect how an engagement develops, all of this must be '''pre-briefed''' and set as a '''contract''' before the mission. Time pressure may not always permit a thorough sanitisation pass, and how to handle that contingency should likewise be agreed upon in the brief.

=== Targeting ===
The flight assigns GROUP responsibility and confirms classification.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} DECLARE {Group Label or Bullseye Position}
|-
| Controller || {Group Label} DECLARED {HOSTILE / BOGEY / FRIENDLY / UNABLE / FURBALL}
|-
| FL || {CS} TARGET {Group Label} {Tactic}
|-
| colspan="2" style="text-align:center;" | ''Once group appears on radar''
|-
| FL || {CS} TARGETED {Group Label} BULLSEYE {Bearing/Range}
|-
| Controller || ''No response if information correlates. Comparative response if correction is required.''
|}

== 03 / Common Calls ==

=== DECLARE ===
Inquiry as to the identity of a specified GROUP. Full positional data in BULLSEYE format must accompany all responses.
MIKE, EAGLE 11, DECLARE NORTH GROUP.
EAGLE 11, NORTH GROUP BULLSEYE 2-7-3/27, TWENTY-TWO THOUSAND, TRACK EAST, BOGEY SPADES.

=== BOGEY DOPE ===
Request for BRAA information on the indicated GROUP or the closest GROUP if not specified. Does not imply fighter targeting.
MIKE, EAGLE 11, BOGEY DOPE NORTH GROUP.
EAGLE 11, NORTH GROUP BRAA 2-1-0/28, THIRTY-EIGHT THOUSAND, HOT, HOSTILE.

=== NAILS ===
Fighter's radar warning receiver is detecting an airborne interceptor radar in search mode. Called with bearing or cardinal direction.
EAGLE 1, NAILS 2-7-0.

=== SPIKED ===
Fighter is being actively tracked by an airborne radar. Called with bearing or cardinal direction. Controller correlates to a GROUP within ±30 degrees and responds with range, altitude, aspect, declaration, and GROUP name.
EAGLE 1, SPIKED 2-7-0.
EAGLE 1, SPIKE RANGE 17, THIRTY THOUSAND, HOSTILE EAST GROUP, TWO CONTACTS.

=== THREAT Call ===
If a fighter will pierce THREAT range to an untargeted GROUP, the controller makes a THREAT call in BRAA format no later than THREAT range.
HEAT 31, ADDITIONAL GROUP THREAT, BRAA 1-2-5/35, THIRTY-FIVE THOUSAND, HOT, HOSTILE.

If the THREAT is within 5 nm of friendly fighters:
BOLT 1, THREAT NORTH THREE, TEN THOUSAND, TRACK SOUTH, HOSTILE.

=== FADED and VANISHED ===
'''FADED''' — a previously tracked GROUP not updated by sensors for 30 seconds. The controller reports the GROUP as FADED with last known BULLSEYE position. Fighters maintain MONITOR responsibility if they can maintain correlation. FADED is not used for friendly aircraft — controllers use NEGATIVE CONTACT for friendlies not held on sensors.

'''VANISHED''' — a special case of FADED used when the GROUP is not in a known blind zone and is correlated to a friendly shot that meets parameters for successful termination.

=== Unexpected Contacts ===
Three distinct call types exist for contacts not part of the established picture:

{| class="wikitable" style="width:100%;"
|-
! Call !! Criteria !! Format
|-
| '''ADDITIONAL GROUP''' || Newly detected outside targeting range, or does not fit traditional label || BULLSEYE
|-
| '''POP-UP GROUP''' || Previously undetected; appears inside targeting range but outside THREAT range || BULLSEYE
|-
| '''THREAT GROUP''' || Undetected or unreported GROUP meeting briefed THREAT criteria || BRAA to the closest aircraft
|}

DARKSTAR, POP-UP GROUP BULLSEYE 2-7-0/15, FIVE THOUSAND, TRACK WEST, BOGEY SPADES.
RAMBO 2, THREAT GROUP BRAA 2-7-0/13, ONE THOUSAND, HOT, HOSTILE.

== 04 / Engagement ==
The engagement loop is the core sequence executed by all fighter flights once committed and targeting is established. It repeats until the GROUP is splashed, leaves the area, or the flight resets.

=== MELD ===
The flight lead directs all flight members to shift their radars from wide sanitization to focused SA on the assigned GROUP. This transition narrows the radar from maximum azimuth and altitude coverage to a tighter volume centered on the target. Sanitization of the surrounding airspace ceases until DROPPING is called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''All flight members shift radar from sanitization to the assigned GROUP''
|}

=== SORT ===
The flight lead assigns individual contacts within the GROUP to specific flight members. Each member acknowledges with SORTED when they have confirmed their assigned contact on radar and are prepared to engage it. If a member cannot confirm their assigned contact, SORTED is withheld until resolution.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || ''(intraflight) FLIGHT SORT {Criteria}''
|-
| #2 || ''(intraflight) #2 SORTED''
|-
| #3 || ''(intraflight) #3 SORTED''
|-
| #4 || ''(intraflight) #4 SORTED''
|}

=== JUDY ===
Called by the flight lead when the flight no longer requires controller guidance to prosecute the intercept. From this point, the controller minimizes transmissions and provides situational awareness information only. JUDY is not always called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Provides SA and THREAT calls only.''
|}

=== ENGAGE ===
Directive call from the flight lead to a specific wingman to employ weapons. The flight lead may also direct simultaneous employment by multiple members.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} ENGAGE
|-
| Wingman || {CS}
|}

=== Weapon Employment ===
The firing aircraft calls the shot on TACC2 NET immediately after employment. The call includes shot type, GROUP label, contact description, BULLSEYE position, and altitude. The controller acknowledges with COPY SHOT.

If a fighter determines a GROUP HOSTILE and ROE has been met, the fighter may employ autonomously and include HOSTILE in the shot transmission.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft || {TACC2-CS} {CS} FOX THREE {Group Label} {Contact Description} BULLSEYE {Bearing/Range} {Altitude}
|-
| TACC2 || {TACC2-CS} COPY SHOT
|-
| colspan="2" style="text-align:center;" | ''Autonomous HOSTILE employment''
|-
| Firing Aircraft || {Controller-CS} {CS} FOX THREE {Group Label} BULLSEYE {Bearing/Range} {Altitude} HOSTILE
|-
| TACC2 || {TACC2-CS} COPY SHOT
|}

Multiple shots in one transmission are acceptable:
SHADOW12 FOX THREE NORTH GROUP LEAD CONTACT BULLSEYE 2-7-0/20 TWENTY THOUSAND; SHADOW11 FOX THREE NORTH GROUP TRAIL CONTACT.

=== OUT / DEFENDING ===
Following weapon employment the flight turns away from the threat. OUT is a planned maneuver executed at a prebriefed range. DEFENDING indicates a reactive maneuver against an incoming weapon and is called with the cardinal direction of the defensive turn.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction}
|-
| colspan="2" style="text-align:center;" | ''or, if reacting to an incoming weapon''
|-
| Aircraft || {CS} DEFENDING {Direction}
|}

=== DROPPING ===
May be called in conjunction with OUT. Signals the controller that the flight has ceased monitoring the GROUP and is returning to sanitization radar settings. Monitoring responsibility transfers back to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction} DROPPING {Group Label}
|-
| colspan="2" style="text-align:center;" | ''Controller resumes monitoring of the dropped GROUP''
|-
| Controller || ''Resumes monitoring.''
|}

=== Assessment ===
The flight assesses weapon effects from sensor data or controller reports. Three outcomes are possible:

{| class="wikitable" style="width:100%;"
|-
! Outcome !! Action
|-
| GROUP splashed || Call SPLASH
|-
| GROUP remains a factor, follow-up shot required || Turn IN, return to MELD
|-
| GROUP has left the area or is no longer a factor || Proceed with Tasking
|}

=== IN (Follow-up Engagement) ===
If the GROUP remains a factor and the tactic permits a follow-up shot, the flight turns back toward the GROUP. The IN call triggers a new cycle beginning at MELD.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IN {Direction}
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''Re-sort as required, then return to ENGAGE''
|}

=== SPLASH ===
Called when weapon effects confirm the GROUP or contact is destroyed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft or Controller || {CS} SPLASH {Group Label or Contact Description}
|}

----

== 05 / Defensive Counter Air (DCA) ==
DCA is the use of fighter aircraft to defend a ground asset or airspace against hostile air threats. It uses prebriefed lanes and defined ranges.

=== DCA Range Structure ===
All ranges are prebriefed per sortie. The following are the standard range lines used in DCA:

{| class="wikitable" style="width:100%;"
|-
! Range Line !! Definition
|-
| '''Mission Fail Line''' || The line the enemy must not cross for the mission to succeed. Defines the maximum depth of the defensive problem.
|-
| '''Commit Line (CL)''' || The line at which a bogey is declared HOSTILE IAW theater ROE and the flight is authorized to commit. Prebriefed for all DCA sorties.
|-
| '''Targeting Range''' || The prebriefed distance at which all contacts must be intercepted. A GROUP inside this range with no assigned fighter is UNTARGETED. Prebriefed per sortie.
|-
| '''TAC Range''' || Default 60 nm from the closest fighter to the closest GROUP. Signals all players to prepare for targeting.
|-
| '''Threat Range''' || The prebriefed range at which an untargeted GROUP meeting THREAT criteria triggers a THREAT call. Prebriefed per sortie.
|}

=== COMMIT Authority ===
COMMIT authority is derived from the combatant commander and delegated through the chain of command. Any of the following may hold or recommend COMMIT authority depending on what is delegated:

{| class="wikitable" style="width:100%;"
|-
! Role !! Abbreviation !! Authority
|-
| Flight Lead || FL || Usually holds COMMIT authority unless delegated
|-
| Team Lead || TL || May hold COMMIT authority if delegated
|-
| Mission Commander || MC || May hold COMMIT authority if delegated
|-
| TACC2 || — || May hold COMMIT authority if delegated
|}

If only the MC, TL, or FL holds COMMIT authority, the controller may only recommend COMMIT. If the controller holds COMMIT authority, the MC and TL may only recommend.

=== DCA Flow ===

==== Lane Handover ====
When an outgoing flight is relieved on station by an incoming flight, a positive lane handover is required before the outgoing flight departs.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Off-going Lane Commander || {CS} MOVE FORWARD
|-
| On-coming Lane Commander || {CS}
|-
| colspan="2" style="text-align:center;" | ''On-coming aircraft may enter the lane. Lane commander authority has not yet transferred.''
|-
| Off-going Lane Commander || {CS} YOU HAVE THE LANE
|-
| On-coming Lane Commander || {CS} HAS THE LANE
|}

The off-going flight passes critical mission information to the controller before departing. The controller passes big-picture information to the on-coming flight before pushing them to the tactical frequency.

==== Pre-Commit ====
The flight arrives at its prebriefed CAP position with FENCE IN complete and radars in sanitization configuration. The controller holds picture responsibility.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} PICTURE
|-
| Controller || {CS} {Nr of Groups} {Group Label} BULLSEYE {Bearing/Range} {Altitude} TRACK {Direction} {Declaration} {Nr of Contacts}
|}

The flight evaluates commit criteria continuously. Pictures are requested as needed to maintain SA.

==== Commit ====

===== FIGHTER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} Recommend {CS} COMMIT
|-
| FL || {CS} COMMIT
|}

===== CONTROLLER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} Recommend Commit
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} {CS} COMMIT
|-
|FL
|{CS}
|}

After COMMIT, fighters hold radio priority.

=== Engagement Loop ===
The flight executes the standard engagement loop as defined above The loop repeats until the GROUP is splashed, leaves the lane, or:

Once the Engagement is Complete the flight '''RESETS''' back to the briefed Position

==== RESET ====
Directs the flight to return to its prebriefed position or area of operations. RESET implies DROPPING and returns all targeting responsibility to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} RESET
|-
| colspan="2" style="text-align:center;" | ''Flight returns to prebriefed CAP position. Controller resumes full picture responsibility''
|}

----

== 06 / Offensive Counter Air (OCA) ==
OCA is the use of fighter aircraft to suppress, destroy, or neutralize enemy air assets before they can threaten friendly forces. Unlike DCA, OCA is not lane-based and does not require a commit line. The flight pushes into the threat environment rather than waiting for the threat to approach.

=== OCA Range Structure ===
The same range lines apply as in DCA — Threat Range, Targeting Range, and TAC Range — but all are prebriefed based on the specific mission geometry and threat environment. There is no commit line or mission fail line in OCA.

=== OCA Flow ===
OCA does not have a lane handover or a commit phase. The flight checks in, receives the picture, establishes targeting, and executes the engagement loop.

==== FULL COMMUNICATIONS EXAMPLE ====
In this Scenario, SHADOW11 four-ship F16C on OCA. TACC2 Agency CS THUMPER executing Positive Control. The Example begins after the Handover. Check In was done on the previous Frequency. TAC RANGE 60, THREAT RANGE 30
THUMPER SHADOW11 PICTURE

THUMPER PICTURE TEN GROUPS GROUP BULLSEYE 0-2-0/25, TWENTY-SEVEN THOUSAND, THOUSAND, TRACK EAST, HOSTILE, HEAVY, THREE CONTACTS. GROUP BULLSEYE 2-7-0/25, FIFTEEN THOUSAND, TRACK WEST, HOSTILE. GROUP BULLSEYE 2-9-0/35, TEN THOUSAND, TRACK WEST, HOSTILE.

SHADOW11 TARGETED GROUP BULLSEYE 0-2-0/25

SHADOW11 GROUP BULLSEYE 0-2-0/25 TAC RANGE

SHADOW11 SKATE, MELD

SHADOW11 SORTED

SHADOW11 FOX3 BULLSEYE 0-2-0/25

THUMPER COPY SHOT

SHADOW11 OUT SOUTH DROPPING

THUMPER

THUMPER SHADOW11 BOGEYDOPE

SHADOW11 EAST GROUP BRAA 2-1-0/28, FIFTEEN-THOUSAND, COLD, HOSTILE

SHADOW11 IN, MELD, SORTED

THUMPER SHADOW11 SPLASH EAST GROUP

THUMPER
In the Following Example additional Adversarys Pop Up within Threat Range of SHADOW11
SHADOW11 THREAT GROUP, BRAA 1-2-5/28, FIVE-THOUSAND, HOT, HOSTILE, 2 CONTACTS

SHADOW11 TARGETED, SORTED LEAD, FOX 3 LEADER, FOX3 TRAILER, BULLSEYE 0-5-0/45, FIVE-THOUSAND

THUMPER COPY SHOT

SHADOW11 DEFENDING SOUTH, DROPPING

THUMPER

SHADOW11 THUMPER THREAT GROUP, BRAA 0-6-0/15, TWO-THOUSAND, COLD, HOSTILE

SHADOW11

SHADOW11 IN

SHADOW11 FOX3 BULLSEYE 0-6-0/15, TWO-THOUSAND

THUMPER COPY SHOT

SHADOW11 THUMPER THREAT GROUP VANISHED
----

== 07 / QRA ==

== 08 / Intercept (VID) ==
A Visual Identification (VID) intercept is conducted when a contact cannot be declared HOSTILE or FRIENDLY by electronic means alone, and visual confirmation of aircraft type, markings, or behavior is required before engagement authority can be granted or withheld.

VID intercepts follow a structured sequence: the controller guides the fighter to a position from which a visual identification pass can be made, then the fighter reports the result and awaits further direction.

=== Intercept Flow ===

==== Commit ====
The controller or flight lead initiates the intercept against the unidentified contact.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} COMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration} {Nr of Contacts}
|-
| FL || {CS} COMMIT
|}

==== Guidance ====
The controller provides vectors to position the fighter for a VID pass. This is the only phase where the controller takes positive close control of the intercept geometry. BRAA format is used throughout.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} BRAA {Bearing/Range} {Altitude} {Aspect} {Declaration}
|-
| FL || {CS}
|-
| colspan="2" style="text-align:center;" | ''Controller continues to provide updated vectors until fighter calls JUDY''
|}

==== JUDY ====
The fighter calls JUDY when radar contact is established and no further controller guidance is required. The controller minimizes transmissions from this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Continues to provide SA information only.''
|}

==== Tally ====
The fighter calls TALLY when visual contact is established with the target.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} TALLY {Position}
|}

==== Identification ====
The fighter conducts the VID pass and reports the result to the controller. The report includes aircraft type, markings, and behavior observed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IDENTIFIED {Aircraft Type} {Markings / Behavior}
|-
| Controller || {CS} {Further Instructions / Declaration Update}
|}

If the contact is identified as HOSTILE following the VID pass, the controller issues the updated declaration and the flight may proceed to engagement IAW ROE. If the contact is FRIENDLY or NEUTRAL, the flight disengages and returns to its prebriefed position.

----

== 09 / Merge ==
A merge occurs when friendly and target aircraft arrive in the visual arena, within 3–5 nm of each other. At the merge, radar resolution becomes limiting and the engagement transitions from BVR to Within Visual Range (WVR). The engagement is now managed through ACM contracts and direct communication between flight members.

=== Authority and Radio Priority ===
Two distinct concepts govern merge communications: '''authority''' and '''radio priority'''.

'''Authority''' remains with the Flight Lead throughout the engagement. The FL can override, redirect, or terminate the engagement at any time regardless of who is engaged.

'''Radio priority''' belongs to the engaged fighter. Other flight members subordinate their transmissions to avoid stepping on critical engaged fighter calls. The controller minimizes transmissions entirely and provides only THREAT calls, SA updates, and responses to direct requests.

{| class="wikitable" style="width:100%;"
|-
! Role !! Authority !! Radio Priority
|-
| '''Flight Lead''' || Full authority over the engagement at all times || Secondary — subordinates to engaged fighter
|-
| '''Engaged Fighter''' || Manages own engagement IAW FL direction || Primary — holds radio priority
|-
| '''Supporting Fighter''' || Executes IAW engaged fighter and FL direction || Tertiary — transmits only when necessary
|-
| '''Controller''' || Provides SA only || Minimal — THREAT calls and direct requests only
|}

=== MERGED ===
The controller calls MERGED when radar tracks come together within 3–5 nm, or the engaged fighter calls it when visual contact is made at the merge.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Engaged Fighter || {CS} MERGED {Group Label}
|}

=== Role Assignment ===
At or before the merge, engaged and supporting roles must be clearly established. By default the flight lead is engaged. Roles can be assigned or transferred in two ways:

==== Wingman-Initiated Transfer ====
The wingman identifies he is the engaged fighter based on the bandit's plane of motion and lift vector orientation, and calls it.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Wingman || #2 ENGAGED
|-
| Flight Lead || PRESS
|}

==== Flight Lead-Initiated Transfer ====
The flight lead recognizes the wingman is the engaged fighter and assigns the role.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || #2 PRESS
|-
| Wingman || #2 ENGAGED
|}

==== Bandit Switches ====
If the bandit maneuvers to engage the other fighter, the currently engaged fighter communicates the change.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || BANDIT SWITCHED
|-
| colspan="2" style="text-align:center;" | ''Roles are reassessed and reassigned as required''
|}

=== Engaged Fighter SA Calls ===
The engaged fighter is responsible for narrating the fight to maintain the supporting fighter's situational awareness. This enables the supporting fighter to position correctly and employ at the right moment. SA calls include the fight geometry, altitude, and direction.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || {CS} ENGAGED {ONE / TWO CIRCLE} {Direction} {Altitude}
|}

VIPER 1, ENGAGED ONE CIRCLE CLIMBING THROUGH FIFTEEN THOUSAND.
VIPER 1, ENGAGED TWO CIRCLE NORTHBOUND BANDITS LOW TWO'S HIGH.

These calls are made continuously as the fight develops, not just once at the merge. The supporting fighter cannot position or employ safely without them.

=== STATUS Calls ===
STATUS is a request from the supporting fighter for a specific situational update from the engaged fighter. It is the primary tool for IFF at the merge. A generic STATUS call returns a general update. A specific STATUS call asks a targeted question and returns a more useful answer.

The supporting fighter should tailor the STATUS call to the specific information needed to resolve the IFF situation. Generic STATUS calls are acceptable but specific calls are faster and more effective.

{| class="wikitable" style="width:100%;"
|-
! Call !! Question Being Asked !! Example Response
|-
| '''STATUS''' || General situation update || ENGAGED ONE CIRCLE NORTHBOUND BANDITS LOW TWO'S HIGH
|-
| '''STATUS HIGH/LOW''' || Which aircraft is higher || BANDITS LOW TWO'S HIGH
|-
| '''STATUS NOSE HIGH/NOSE LOW''' || Which aircraft has nose above or below horizon || TWO'S NOSE HIGH BANDIT NOSE LOW
|-
| '''STATUS LEFT/RIGHT''' || Which aircraft is left or right || TWO'S LEFT BANDIT RIGHT
|-
| '''STATUS NORTH/SOUTH/EAST/WEST''' || Cardinal orientation of aircraft in the fight || TWO'S NORTH BANDIT SOUTH
|}

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || {CS} STATUS {Qualifier if applicable}
|-
| Engaged Fighter || {Specific SA answer to the STATUS question}
|}

Supporting Fighter: TWO STATUS HIGH LOW.
Engaged Fighter: BANDITS LOW TWO'S HIGH.

If a STATUS call returns an ambiguous response, rephrase with a more specific qualifier before resorting to a FLASH call.

As a last resort, a FLASH call can be used to add physical confirmation to IFF — for example FLASH FLARES or FLASH BURNER. This directs the wingman to briefly activate the specified system so the supporting fighter can visually confirm identity. Exercise extreme caution — the bandit may also be employing flares, and a mistaken identification cannot be undone.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || FLASH {FLARES / BURNER}
|-
| Wingman || ''(executes flash of specified system briefly)''
|}

=== IFF Brevity ===
Standard brevity calls for visual identification status:

{| class="wikitable" style="width:100%;"
|-
! Term !! Meaning
|-
| '''TALLY''' || Visual contact established on the target or bandit
|-
| '''NO JOY''' || No visual contact with the target or bandit
|-
| '''VISUAL''' || Visual contact established on a friendly aircraft
|-
| '''BLIND''' || No visual contact with a friendly aircraft
|}

IFF must be confirmed before employment. Do not rely on aircraft visuals alone — use STATUS calls to confirm orientation before taking a shot.

=== Talk-On ===
If the supporting fighter loses visual on the engaged fighter after the merge, the engaged fighter or flight lead can provide a talk-on to re-establish visual.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter or FL || {CS} {Clock Position} {Range} {Altitude Qualifier}
|}

VIPER 1, THREE O'CLOCK ONE AND A HALF MILES LOW.

Once visual is re-established:

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || {CS} VISUAL
|}

=== Employment ===
Once IFF is confirmed and a valid shot opportunity exists, the supporting fighter employs. The call includes weapon type and target description.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting or Engaged Fighter || {Controller-CS} {CS} FOX TWO {Target Description}
|-
| Controller || COPY SHOT
|}

Gun employment:

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting or Engaged Fighter || {Controller-CS} {CS} GUNS {Target Description}
|}

The flight lead retains authority to call NEGATIVE if employment is unsafe or premature, regardless of who holds radio priority.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || NEGATIVE {CS} {Reason if required}
|}

=== SPLASH ===
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged or Supporting Fighter || {Controller-CS} {CS} SPLASH {Target Description}
|-
| Controller || {CS} COPY SPLASH
|}

=== Bug Out ===
Following SPLASH, or when the flight lead determines the engagement should end, the supporting fighter directs the egress. The supporting fighter holds the best big-picture SA at this point and is best placed to select a safe egress direction.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || {CS} BUG OUT {Direction}
|-
| colspan="2" style="text-align:center;" | ''All flight members flow in the stated direction''
|}

VIPER'S BUG OUT 0-9-0.

If the flight lead was the supporting fighter and the wingman is now visual after the bug out, conventional flight roles are re-established:

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Wingman || {CS} VISUAL PRESS
|-
| Flight Lead || ENGAGED
|}

Following the bug out the flight calls RESET on the TAC C2 NET and returns to the prebriefed position unless directed otherwise.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || {Controller-CS} {CS} RESET
|}

MTTP/A2A

2026-05-23T15:51:50Z

Niknam3: /* 09 / Merge */

== 01 / Overview ==
Air combat is primarily carried out by CAP aircraft. The two main mission types are '''DCA''' (Defensive Counter Air) and '''OCA''' (Offensive Counter Air).

=== Groups and Contacts ===
A '''GROUP''' is any number of air contacts within 3 nm in azimuth and range of each other. A '''CONTACT''' is an individual radar return within a GROUP. Single contact is the assumed strength for all GROUPs unless otherwise specified. A GROUP with three or more contacts is called '''HEAVY'''.

The '''PICTURE''' establishes a common tactical air image and describes the spatial relationship of GROUPs. It is always communicated in BULLSEYE format unless briefed otherwise. Only the Three GROUPs with highest Priority are Conveyed

=== Contact Declaration ===
Before a fighter can engage, a contact must be declared. Declaration is performed by the controller in response to a DECLARE request.

{| class="wikitable" style="width:100%;"
|-
! Declaration !! Meaning !! Engagement Authority
|-
| '''BOGEY''' || Identity unknown || Not cleared to engage
|-
| '''OUTLAW''' || Originates from known or suspected hostile area || Not cleared to engage; escalation criteria apply
|-
| '''SPADES''' || No valid IFF response on interrogation || Not cleared to engage; escalation criteria apply
|-
| '''BANDIT''' || Positively identified as enemy IAW theater ID criteria || Not cleared to engage; does not imply authority to fire
|-
| '''HOSTILE''' || Confirmed enemy; clearance to fire authorized IAW ROE || Cleared to engage
|-
| '''NEUTRAL''' || Positively identified as neutral || Not cleared to engage
|-
| '''FRIENDLY''' || Positively identified as friendly || Not cleared to engage
|-
| '''FURBALL''' || Friendly and non-friendly aircraft within 5 nm || Employment not authorized until resolved
|}

A BOGEY, BANDIT, OUTLAW, or SPADES classification does not authorize engagement. HOSTILE is the only declaration that authorizes weapons employment IAW ROE.

== 02 / Important Concepts ==

=== Communication Cadence by Phase ===
Communication priority shifts between the controller and fighters depending on the phase of the intercept.

{| class="wikitable" style="width:100%;"
|-
! Phase !! Priority Communicators
|-
| Pre-COMMIT / Marshal || 1. Controller · 2. Fighters
|-
| Post-COMMIT / Push || 1. Controller · 2. Fighter
|-
| Targeting / Weapons Employment || 1. Fighters · 2. Controller
|-
| Merge || 1. Engaged Fighter · 2. Supporting Fighters · 3. Controller
|-
| Post-Merge || 1. Fighter Clearing Merge · 2. Supporting Fighters · 3. Controller
|}

=== TAC Range ===
Called at 60 nm (default) by the first asset to recognize the separation. Signals all players to prepare for targeting. Pre-commit SA building continues until this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Fighter || {CS} {Group Label} TAC RANGE
|}

=== Airspace Sanitization ===
A Section consists of two aircraft, each equipped with its own radar. Regardless of the number of bars or maximum azimuth a single radar supports, no single system can cover the entire sky. To compensate, both radars are stacked and assigned to different portions of the airspace — each portion is called an '''Area of Responsibility (AOR)'''. This technique, known as '''Radar Mating''', vastly increases the total volume scanned and ensures that no unknown contacts are operating in the area beyond already-tracked groups. The exact parameters depend on the aircraft type: the US Navy recommends RWS, 140°, 6 bars, end scale 80 nm, with radars mated at 25 nm: placing the flight lead between 40,000 and 15,000 ft, and the wingman from ground level to 25,000 ft.

The process of actively scanning assigned AORs to confirm no unknown contacts are present is called '''Sanitisation'''.

Because both Radar Mating parameters and Sanitisation responsibilities directly affect how an engagement develops, all of this must be '''pre-briefed''' and set as a '''contract''' before the mission. Time pressure may not always permit a thorough sanitisation pass, and how to handle that contingency should likewise be agreed upon in the brief.

=== Targeting ===
The flight assigns GROUP responsibility and confirms classification.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} DECLARE {Group Label or Bullseye Position}
|-
| Controller || {Group Label} DECLARED {HOSTILE / BOGEY / FRIENDLY / UNABLE / FURBALL}
|-
| FL || {CS} TARGET {Group Label} {Tactic}
|-
| colspan="2" style="text-align:center;" | ''Once group appears on radar''
|-
| FL || {CS} TARGETED {Group Label} BULLSEYE {Bearing/Range}
|-
| Controller || ''No response if information correlates. Comparative response if correction is required.''
|}

== 03 / Common Calls ==

=== DECLARE ===
Inquiry as to the identity of a specified GROUP. Full positional data in BULLSEYE format must accompany all responses.
MIKE, EAGLE 11, DECLARE NORTH GROUP.
EAGLE 11, NORTH GROUP BULLSEYE 2-7-3/27, TWENTY-TWO THOUSAND, TRACK EAST, BOGEY SPADES.

=== BOGEY DOPE ===
Request for BRAA information on the indicated GROUP or the closest GROUP if not specified. Does not imply fighter targeting.
MIKE, EAGLE 11, BOGEY DOPE NORTH GROUP.
EAGLE 11, NORTH GROUP BRAA 2-1-0/28, THIRTY-EIGHT THOUSAND, HOT, HOSTILE.

=== NAILS ===
Fighter's radar warning receiver is detecting an airborne interceptor radar in search mode. Called with bearing or cardinal direction.
EAGLE 1, NAILS 2-7-0.

=== SPIKED ===
Fighter is being actively tracked by an airborne radar. Called with bearing or cardinal direction. Controller correlates to a GROUP within ±30 degrees and responds with range, altitude, aspect, declaration, and GROUP name.
EAGLE 1, SPIKED 2-7-0.
EAGLE 1, SPIKE RANGE 17, THIRTY THOUSAND, HOSTILE EAST GROUP, TWO CONTACTS.

=== THREAT Call ===
If a fighter will pierce THREAT range to an untargeted GROUP, the controller makes a THREAT call in BRAA format no later than THREAT range.
HEAT 31, ADDITIONAL GROUP THREAT, BRAA 1-2-5/35, THIRTY-FIVE THOUSAND, HOT, HOSTILE.

If the THREAT is within 5 nm of friendly fighters:
BOLT 1, THREAT NORTH THREE, TEN THOUSAND, TRACK SOUTH, HOSTILE.

=== FADED and VANISHED ===
'''FADED''' — a previously tracked GROUP not updated by sensors for 30 seconds. The controller reports the GROUP as FADED with last known BULLSEYE position. Fighters maintain MONITOR responsibility if they can maintain correlation. FADED is not used for friendly aircraft — controllers use NEGATIVE CONTACT for friendlies not held on sensors.

'''VANISHED''' — a special case of FADED used when the GROUP is not in a known blind zone and is correlated to a friendly shot that meets parameters for successful termination.

=== Unexpected Contacts ===
Three distinct call types exist for contacts not part of the established picture:

{| class="wikitable" style="width:100%;"
|-
! Call !! Criteria !! Format
|-
| '''ADDITIONAL GROUP''' || Newly detected outside targeting range, or does not fit traditional label || BULLSEYE
|-
| '''POP-UP GROUP''' || Previously undetected; appears inside targeting range but outside THREAT range || BULLSEYE
|-
| '''THREAT GROUP''' || Undetected or unreported GROUP meeting briefed THREAT criteria || BRAA to the closest aircraft
|}

DARKSTAR, POP-UP GROUP BULLSEYE 2-7-0/15, FIVE THOUSAND, TRACK WEST, BOGEY SPADES.
RAMBO 2, THREAT GROUP BRAA 2-7-0/13, ONE THOUSAND, HOT, HOSTILE.

== 04 / Engagement ==
The engagement loop is the core sequence executed by all fighter flights once committed and targeting is established. It repeats until the GROUP is splashed, leaves the area, or the flight resets.

=== MELD ===
The flight lead directs all flight members to shift their radars from wide sanitization to focused SA on the assigned GROUP. This transition narrows the radar from maximum azimuth and altitude coverage to a tighter volume centered on the target. Sanitization of the surrounding airspace ceases until DROPPING is called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''All flight members shift radar from sanitization to the assigned GROUP''
|}

=== SORT ===
The flight lead assigns individual contacts within the GROUP to specific flight members. Each member acknowledges with SORTED when they have confirmed their assigned contact on radar and are prepared to engage it. If a member cannot confirm their assigned contact, SORTED is withheld until resolution.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || ''(intraflight) FLIGHT SORT {Criteria}''
|-
| #2 || ''(intraflight) #2 SORTED''
|-
| #3 || ''(intraflight) #3 SORTED''
|-
| #4 || ''(intraflight) #4 SORTED''
|}

=== JUDY ===
Called by the flight lead when the flight no longer requires controller guidance to prosecute the intercept. From this point, the controller minimizes transmissions and provides situational awareness information only. JUDY is not always called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Provides SA and THREAT calls only.''
|}

=== ENGAGE ===
Directive call from the flight lead to a specific wingman to employ weapons. The flight lead may also direct simultaneous employment by multiple members.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} ENGAGE
|-
| Wingman || {CS}
|}

=== Weapon Employment ===
The firing aircraft calls the shot on TACC2 NET immediately after employment. The call includes shot type, GROUP label, contact description, BULLSEYE position, and altitude. The controller acknowledges with COPY SHOT.

If a fighter determines a GROUP HOSTILE and ROE has been met, the fighter may employ autonomously and include HOSTILE in the shot transmission.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft || {TACC2-CS} {CS} FOX THREE {Group Label} {Contact Description} BULLSEYE {Bearing/Range} {Altitude}
|-
| TACC2 || {TACC2-CS} COPY SHOT
|-
| colspan="2" style="text-align:center;" | ''Autonomous HOSTILE employment''
|-
| Firing Aircraft || {Controller-CS} {CS} FOX THREE {Group Label} BULLSEYE {Bearing/Range} {Altitude} HOSTILE
|-
| TACC2 || {TACC2-CS} COPY SHOT
|}

Multiple shots in one transmission are acceptable:
SHADOW12 FOX THREE NORTH GROUP LEAD CONTACT BULLSEYE 2-7-0/20 TWENTY THOUSAND; SHADOW11 FOX THREE NORTH GROUP TRAIL CONTACT.

=== OUT / DEFENDING ===
Following weapon employment the flight turns away from the threat. OUT is a planned maneuver executed at a prebriefed range. DEFENDING indicates a reactive maneuver against an incoming weapon and is called with the cardinal direction of the defensive turn.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction}
|-
| colspan="2" style="text-align:center;" | ''or, if reacting to an incoming weapon''
|-
| Aircraft || {CS} DEFENDING {Direction}
|}

=== DROPPING ===
May be called in conjunction with OUT. Signals the controller that the flight has ceased monitoring the GROUP and is returning to sanitization radar settings. Monitoring responsibility transfers back to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction} DROPPING {Group Label}
|-
| colspan="2" style="text-align:center;" | ''Controller resumes monitoring of the dropped GROUP''
|-
| Controller || ''Resumes monitoring.''
|}

=== Assessment ===
The flight assesses weapon effects from sensor data or controller reports. Three outcomes are possible:

{| class="wikitable" style="width:100%;"
|-
! Outcome !! Action
|-
| GROUP splashed || Call SPLASH
|-
| GROUP remains a factor, follow-up shot required || Turn IN, return to MELD
|-
| GROUP has left the area or is no longer a factor || Proceed with Tasking
|}

=== IN (Follow-up Engagement) ===
If the GROUP remains a factor and the tactic permits a follow-up shot, the flight turns back toward the GROUP. The IN call triggers a new cycle beginning at MELD.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IN {Direction}
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''Re-sort as required, then return to ENGAGE''
|}

=== SPLASH ===
Called when weapon effects confirm the GROUP or contact is destroyed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft or Controller || {CS} SPLASH {Group Label or Contact Description}
|}

----

== 05 / Defensive Counter Air (DCA) ==
DCA is the use of fighter aircraft to defend a ground asset or airspace against hostile air threats. It uses prebriefed lanes and defined ranges.

=== DCA Range Structure ===
All ranges are prebriefed per sortie. The following are the standard range lines used in DCA:

{| class="wikitable" style="width:100%;"
|-
! Range Line !! Definition
|-
| '''Mission Fail Line''' || The line the enemy must not cross for the mission to succeed. Defines the maximum depth of the defensive problem.
|-
| '''Commit Line (CL)''' || The line at which a bogey is declared HOSTILE IAW theater ROE and the flight is authorized to commit. Prebriefed for all DCA sorties.
|-
| '''Targeting Range''' || The prebriefed distance at which all contacts must be intercepted. A GROUP inside this range with no assigned fighter is UNTARGETED. Prebriefed per sortie.
|-
| '''TAC Range''' || Default 60 nm from the closest fighter to the closest GROUP. Signals all players to prepare for targeting.
|-
| '''Threat Range''' || The prebriefed range at which an untargeted GROUP meeting THREAT criteria triggers a THREAT call. Prebriefed per sortie.
|}

=== COMMIT Authority ===
COMMIT authority is derived from the combatant commander and delegated through the chain of command. Any of the following may hold or recommend COMMIT authority depending on what is delegated:

{| class="wikitable" style="width:100%;"
|-
! Role !! Abbreviation !! Authority
|-
| Flight Lead || FL || Usually holds COMMIT authority unless delegated
|-
| Team Lead || TL || May hold COMMIT authority if delegated
|-
| Mission Commander || MC || May hold COMMIT authority if delegated
|-
| TACC2 || — || May hold COMMIT authority if delegated
|}

If only the MC, TL, or FL holds COMMIT authority, the controller may only recommend COMMIT. If the controller holds COMMIT authority, the MC and TL may only recommend.

=== DCA Flow ===

==== Lane Handover ====
When an outgoing flight is relieved on station by an incoming flight, a positive lane handover is required before the outgoing flight departs.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Off-going Lane Commander || {CS} MOVE FORWARD
|-
| On-coming Lane Commander || {CS}
|-
| colspan="2" style="text-align:center;" | ''On-coming aircraft may enter the lane. Lane commander authority has not yet transferred.''
|-
| Off-going Lane Commander || {CS} YOU HAVE THE LANE
|-
| On-coming Lane Commander || {CS} HAS THE LANE
|}

The off-going flight passes critical mission information to the controller before departing. The controller passes big-picture information to the on-coming flight before pushing them to the tactical frequency.

==== Pre-Commit ====
The flight arrives at its prebriefed CAP position with FENCE IN complete and radars in sanitization configuration. The controller holds picture responsibility.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} PICTURE
|-
| Controller || {CS} {Nr of Groups} {Group Label} BULLSEYE {Bearing/Range} {Altitude} TRACK {Direction} {Declaration} {Nr of Contacts}
|}

The flight evaluates commit criteria continuously. Pictures are requested as needed to maintain SA.

==== Commit ====

===== FIGHTER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} Recommend {CS} COMMIT
|-
| FL || {CS} COMMIT
|}

===== CONTROLLER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} Recommend Commit
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} {CS} COMMIT
|-
|FL
|{CS}
|}

After COMMIT, fighters hold radio priority.

=== Engagement Loop ===
The flight executes the standard engagement loop as defined above The loop repeats until the GROUP is splashed, leaves the lane, or:

Once the Engagement is Complete the flight '''RESETS''' back to the briefed Position

==== RESET ====
Directs the flight to return to its prebriefed position or area of operations. RESET implies DROPPING and returns all targeting responsibility to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} RESET
|-
| colspan="2" style="text-align:center;" | ''Flight returns to prebriefed CAP position. Controller resumes full picture responsibility''
|}

----

== 06 / Offensive Counter Air (OCA) ==
OCA is the use of fighter aircraft to suppress, destroy, or neutralize enemy air assets before they can threaten friendly forces. Unlike DCA, OCA is not lane-based and does not require a commit line. The flight pushes into the threat environment rather than waiting for the threat to approach.

=== OCA Range Structure ===
The same range lines apply as in DCA — Threat Range, Targeting Range, and TAC Range — but all are prebriefed based on the specific mission geometry and threat environment. There is no commit line or mission fail line in OCA.

=== OCA Flow ===
OCA does not have a lane handover or a commit phase. The flight checks in, receives the picture, establishes targeting, and executes the engagement loop.

==== FULL COMMUNICATIONS EXAMPLE ====
In this Scenario, SHADOW11 four-ship F16C on OCA. TACC2 Agency CS THUMPER executing Positive Control. The Example begins after the Handover. Check In was done on the previous Frequency. TAC RANGE 60, THREAT RANGE 30
THUMPER SHADOW11 PICTURE

THUMPER PICTURE TEN GROUPS GROUP BULLSEYE 0-2-0/25, TWENTY-SEVEN THOUSAND, THOUSAND, TRACK EAST, HOSTILE, HEAVY, THREE CONTACTS. GROUP BULLSEYE 2-7-0/25, FIFTEEN THOUSAND, TRACK WEST, HOSTILE. GROUP BULLSEYE 2-9-0/35, TEN THOUSAND, TRACK WEST, HOSTILE.

SHADOW11 TARGETED GROUP BULLSEYE 0-2-0/25

SHADOW11 GROUP BULLSEYE 0-2-0/25 TAC RANGE

SHADOW11 SKATE, MELD

SHADOW11 SORTED

SHADOW11 FOX3 BULLSEYE 0-2-0/25

THUMPER COPY SHOT

SHADOW11 OUT SOUTH DROPPING

THUMPER

THUMPER SHADOW11 BOGEYDOPE

SHADOW11 EAST GROUP BRAA 2-1-0/28, FIFTEEN-THOUSAND, COLD, HOSTILE

SHADOW11 IN, MELD, SORTED

THUMPER SHADOW11 SPLASH EAST GROUP

THUMPER
In the Following Example additional Adversarys Pop Up within Threat Range of SHADOW11
SHADOW11 THREAT GROUP, BRAA 1-2-5/28, FIVE-THOUSAND, HOT, HOSTILE, 2 CONTACTS

SHADOW11 TARGETED, SORTED LEAD, FOX 3 LEADER, FOX3 TRAILER, BULLSEYE 0-5-0/45, FIVE-THOUSAND

THUMPER COPY SHOT

SHADOW11 DEFENDING SOUTH, DROPPING

THUMPER

SHADOW11 THUMPER THREAT GROUP, BRAA 0-6-0/15, TWO-THOUSAND, COLD, HOSTILE

SHADOW11

SHADOW11 IN

SHADOW11 FOX3 BULLSEYE 0-6-0/15, TWO-THOUSAND

THUMPER COPY SHOT

SHADOW11 THUMPER THREAT GROUP VANISHED
----

== 07 / QRA ==

== 08 / Intercept (VID) ==
A Visual Identification (VID) intercept is conducted when a contact cannot be declared HOSTILE or FRIENDLY by electronic means alone, and visual confirmation of aircraft type, markings, or behavior is required before engagement authority can be granted or withheld.

VID intercepts follow a structured sequence: the controller guides the fighter to a position from which a visual identification pass can be made, then the fighter reports the result and awaits further direction.

=== Intercept Flow ===

==== Commit ====
The controller or flight lead initiates the intercept against the unidentified contact.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} COMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration} {Nr of Contacts}
|-
| FL || {CS} COMMIT
|}

==== Guidance ====
The controller provides vectors to position the fighter for a VID pass. This is the only phase where the controller takes positive close control of the intercept geometry. BRAA format is used throughout.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} BRAA {Bearing/Range} {Altitude} {Aspect} {Declaration}
|-
| FL || {CS}
|-
| colspan="2" style="text-align:center;" | ''Controller continues to provide updated vectors until fighter calls JUDY''
|}

==== JUDY ====
The fighter calls JUDY when radar contact is established and no further controller guidance is required. The controller minimizes transmissions from this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Continues to provide SA information only.''
|}

==== Tally ====
The fighter calls TALLY when visual contact is established with the target.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} TALLY {Position}
|}

==== Identification ====
The fighter conducts the VID pass and reports the result to the controller. The report includes aircraft type, markings, and behavior observed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IDENTIFIED {Aircraft Type} {Markings / Behavior}
|-
| Controller || {CS} {Further Instructions / Declaration Update}
|}

If the contact is identified as HOSTILE following the VID pass, the controller issues the updated declaration and the flight may proceed to engagement IAW ROE. If the contact is FRIENDLY or NEUTRAL, the flight disengages and returns to its prebriefed position.

----

== 12 / Merge ==
A merge occurs when friendly and target aircraft arrive in the visual arena, within 3–5 nm of each other. At the merge, radar resolution becomes limiting and the engagement transitions from BVR to Within Visual Range (WVR). The engagement is now managed through ACM contracts and direct communication between flight members.

=== Authority and Radio Priority ===
Two distinct concepts govern merge communications: '''authority''' and '''radio priority'''.

'''Authority''' remains with the Flight Lead throughout the engagement. The FL can override, redirect, or terminate the engagement at any time regardless of who is engaged.

'''Radio priority''' belongs to the engaged fighter. Other flight members subordinate their transmissions to avoid stepping on critical engaged fighter calls. The controller minimizes transmissions entirely and provides only THREAT calls, SA updates, and responses to direct requests.

{| class="wikitable" style="width:100%;"
|-
! Role !! Authority !! Radio Priority
|-
| '''Flight Lead''' || Full authority over the engagement at all times || Secondary — subordinates to engaged fighter
|-
| '''Engaged Fighter''' || Manages own engagement IAW FL direction || Primary — holds radio priority
|-
| '''Supporting Fighter''' || Executes IAW engaged fighter and FL direction || Tertiary — transmits only when necessary
|-
| '''Controller''' || Provides SA only || Minimal — THREAT calls and direct requests only
|}

=== MERGED ===
The controller calls MERGED when radar tracks come together within 3–5 nm, or the engaged fighter calls it when visual contact is made at the merge.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Engaged Fighter || {CS} MERGED {Group Label}
|}

=== Role Assignment ===
At or before the merge, engaged and supporting roles must be clearly established. By default the flight lead is engaged. Roles can be assigned or transferred in two ways:

==== Wingman-Initiated Transfer ====
The wingman identifies he is the engaged fighter based on the bandit's plane of motion and lift vector orientation, and calls it.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Wingman || #2 ENGAGED
|-
| Flight Lead || PRESS
|}

==== Flight Lead-Initiated Transfer ====
The flight lead recognizes the wingman is the engaged fighter and assigns the role.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || #2 PRESS
|-
| Wingman || #2 ENGAGED
|}

==== Bandit Switches ====
If the bandit maneuvers to engage the other fighter, the currently engaged fighter communicates the change.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || BANDIT SWITCHED
|-
| colspan="2" style="text-align:center;" | ''Roles are reassessed and reassigned as required''
|}

=== Engaged Fighter SA Calls ===
The engaged fighter is responsible for narrating the fight to maintain the supporting fighter's situational awareness. This enables the supporting fighter to position correctly and employ at the right moment. SA calls include the fight geometry, altitude, and direction.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || {CS} ENGAGED {ONE / TWO CIRCLE} {Direction} {Altitude}
|}

VIPER 1, ENGAGED ONE CIRCLE CLIMBING THROUGH FIFTEEN THOUSAND.
VIPER 1, ENGAGED TWO CIRCLE NORTHBOUND BANDITS LOW TWO'S HIGH.

These calls are made continuously as the fight develops, not just once at the merge. The supporting fighter cannot position or employ safely without them.

=== STATUS Calls ===
STATUS is a request from the supporting fighter for a specific situational update from the engaged fighter. It is the primary tool for IFF at the merge. A generic STATUS call returns a general update. A specific STATUS call asks a targeted question and returns a more useful answer.

The supporting fighter should tailor the STATUS call to the specific information needed to resolve the IFF situation. Generic STATUS calls are acceptable but specific calls are faster and more effective.

{| class="wikitable" style="width:100%;"
|-
! Call !! Question Being Asked !! Example Response
|-
| '''STATUS''' || General situation update || ENGAGED ONE CIRCLE NORTHBOUND BANDITS LOW TWO'S HIGH
|-
| '''STATUS HIGH/LOW''' || Which aircraft is higher || BANDITS LOW TWO'S HIGH
|-
| '''STATUS NOSE HIGH/NOSE LOW''' || Which aircraft has nose above or below horizon || TWO'S NOSE HIGH BANDIT NOSE LOW
|-
| '''STATUS LEFT/RIGHT''' || Which aircraft is left or right || TWO'S LEFT BANDIT RIGHT
|-
| '''STATUS NORTH/SOUTH/EAST/WEST''' || Cardinal orientation of aircraft in the fight || TWO'S NORTH BANDIT SOUTH
|}

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || {CS} STATUS {Qualifier if applicable}
|-
| Engaged Fighter || {Specific SA answer to the STATUS question}
|}

Supporting Fighter: TWO STATUS HIGH LOW.
Engaged Fighter: BANDITS LOW TWO'S HIGH.

If a STATUS call returns an ambiguous response, rephrase with a more specific qualifier before resorting to a FLASH call.

As a last resort, a FLASH call can be used to add physical confirmation to IFF — for example FLASH FLARES or FLASH BURNER. This directs the wingman to briefly activate the specified system so the supporting fighter can visually confirm identity. Exercise extreme caution — the bandit may also be employing flares, and a mistaken identification cannot be undone.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || FLASH {FLARES / BURNER}
|-
| Wingman || ''(executes flash of specified system briefly)''
|}

=== IFF Brevity ===
Standard brevity calls for visual identification status:

{| class="wikitable" style="width:100%;"
|-
! Term !! Meaning
|-
| '''TALLY''' || Visual contact established on the target or bandit
|-
| '''NO JOY''' || No visual contact with the target or bandit
|-
| '''VISUAL''' || Visual contact established on a friendly aircraft
|-
| '''BLIND''' || No visual contact with a friendly aircraft
|}

IFF must be confirmed before employment. Do not rely on aircraft visuals alone — use STATUS calls to confirm orientation before taking a shot.

=== Talk-On ===
If the supporting fighter loses visual on the engaged fighter after the merge, the engaged fighter or flight lead can provide a talk-on to re-establish visual.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter or FL || {CS} {Clock Position} {Range} {Altitude Qualifier}
|}

VIPER 1, THREE O'CLOCK ONE AND A HALF MILES LOW.

Once visual is re-established:

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || {CS} VISUAL
|}

=== Employment ===
Once IFF is confirmed and a valid shot opportunity exists, the supporting fighter employs. The call includes weapon type and target description.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting or Engaged Fighter || {Controller-CS} {CS} FOX TWO {Target Description}
|-
| Controller || COPY SHOT
|}

Gun employment:

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting or Engaged Fighter || {Controller-CS} {CS} GUNS {Target Description}
|}

The flight lead retains authority to call NEGATIVE if employment is unsafe or premature, regardless of who holds radio priority.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || NEGATIVE {CS} {Reason if required}
|}

=== SPLASH ===
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged or Supporting Fighter || {Controller-CS} {CS} SPLASH {Target Description}
|-
| Controller || {CS} COPY SPLASH
|}

=== Bug Out ===
Following SPLASH, or when the flight lead determines the engagement should end, the supporting fighter directs the egress. The supporting fighter holds the best big-picture SA at this point and is best placed to select a safe egress direction.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Supporting Fighter || {CS} BUG OUT {Direction}
|-
| colspan="2" style="text-align:center;" | ''All flight members flow in the stated direction''
|}

VIPER'S BUG OUT 0-9-0.

If the flight lead was the supporting fighter and the wingman is now visual after the bug out, conventional flight roles are re-established:

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Wingman || {CS} VISUAL PRESS
|-
| Flight Lead || ENGAGED
|}

Following the bug out the flight calls RESET on the TAC C2 NET and returns to the prebriefed position unless directed otherwise.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || {Controller-CS} {CS} RESET
|}

Procedures/78th/A2A/BFM

2026-05-23T15:47:42Z

Niknam3: /* Common Errors */

MTTP/A2A

2026-05-23T15:44:57Z

Niknam3: /* PRESS */

== 01 / Overview ==
Air combat is primarily carried out by CAP aircraft. The two main mission types are '''DCA''' (Defensive Counter Air) and '''OCA''' (Offensive Counter Air).

=== Groups and Contacts ===
A '''GROUP''' is any number of air contacts within 3 nm in azimuth and range of each other. A '''CONTACT''' is an individual radar return within a GROUP. Single contact is the assumed strength for all GROUPs unless otherwise specified. A GROUP with three or more contacts is called '''HEAVY'''.

The '''PICTURE''' establishes a common tactical air image and describes the spatial relationship of GROUPs. It is always communicated in BULLSEYE format unless briefed otherwise. Only the Three GROUPs with highest Priority are Conveyed

=== Contact Declaration ===
Before a fighter can engage, a contact must be declared. Declaration is performed by the controller in response to a DECLARE request.

{| class="wikitable" style="width:100%;"
|-
! Declaration !! Meaning !! Engagement Authority
|-
| '''BOGEY''' || Identity unknown || Not cleared to engage
|-
| '''OUTLAW''' || Originates from known or suspected hostile area || Not cleared to engage; escalation criteria apply
|-
| '''SPADES''' || No valid IFF response on interrogation || Not cleared to engage; escalation criteria apply
|-
| '''BANDIT''' || Positively identified as enemy IAW theater ID criteria || Not cleared to engage; does not imply authority to fire
|-
| '''HOSTILE''' || Confirmed enemy; clearance to fire authorized IAW ROE || Cleared to engage
|-
| '''NEUTRAL''' || Positively identified as neutral || Not cleared to engage
|-
| '''FRIENDLY''' || Positively identified as friendly || Not cleared to engage
|-
| '''FURBALL''' || Friendly and non-friendly aircraft within 5 nm || Employment not authorized until resolved
|}

A BOGEY, BANDIT, OUTLAW, or SPADES classification does not authorize engagement. HOSTILE is the only declaration that authorizes weapons employment IAW ROE.

== 02 / Important Concepts ==

=== Communication Cadence by Phase ===
Communication priority shifts between the controller and fighters depending on the phase of the intercept.

{| class="wikitable" style="width:100%;"
|-
! Phase !! Priority Communicators
|-
| Pre-COMMIT / Marshal || 1. Controller · 2. Fighters
|-
| Post-COMMIT / Push || 1. Controller · 2. Fighter
|-
| Targeting / Weapons Employment || 1. Fighters · 2. Controller
|-
| Merge || 1. Engaged Fighter · 2. Supporting Fighters · 3. Controller
|-
| Post-Merge || 1. Fighter Clearing Merge · 2. Supporting Fighters · 3. Controller
|}

=== TAC Range ===
Called at 60 nm (default) by the first asset to recognize the separation. Signals all players to prepare for targeting. Pre-commit SA building continues until this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Fighter || {CS} {Group Label} TAC RANGE
|}

=== Airspace Sanitization ===
A Section consists of two aircraft, each equipped with its own radar. Regardless of the number of bars or maximum azimuth a single radar supports, no single system can cover the entire sky. To compensate, both radars are stacked and assigned to different portions of the airspace — each portion is called an '''Area of Responsibility (AOR)'''. This technique, known as '''Radar Mating''', vastly increases the total volume scanned and ensures that no unknown contacts are operating in the area beyond already-tracked groups. The exact parameters depend on the aircraft type: the US Navy recommends RWS, 140°, 6 bars, end scale 80 nm, with radars mated at 25 nm: placing the flight lead between 40,000 and 15,000 ft, and the wingman from ground level to 25,000 ft.

The process of actively scanning assigned AORs to confirm no unknown contacts are present is called '''Sanitisation'''.

Because both Radar Mating parameters and Sanitisation responsibilities directly affect how an engagement develops, all of this must be '''pre-briefed''' and set as a '''contract''' before the mission. Time pressure may not always permit a thorough sanitisation pass, and how to handle that contingency should likewise be agreed upon in the brief.

=== Targeting ===
The flight assigns GROUP responsibility and confirms classification.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} DECLARE {Group Label or Bullseye Position}
|-
| Controller || {Group Label} DECLARED {HOSTILE / BOGEY / FRIENDLY / UNABLE / FURBALL}
|-
| FL || {CS} TARGET {Group Label} {Tactic}
|-
| colspan="2" style="text-align:center;" | ''Once group appears on radar''
|-
| FL || {CS} TARGETED {Group Label} BULLSEYE {Bearing/Range}
|-
| Controller || ''No response if information correlates. Comparative response if correction is required.''
|}

== 03 / Common Calls ==

=== DECLARE ===
Inquiry as to the identity of a specified GROUP. Full positional data in BULLSEYE format must accompany all responses.
MIKE, EAGLE 11, DECLARE NORTH GROUP.
EAGLE 11, NORTH GROUP BULLSEYE 2-7-3/27, TWENTY-TWO THOUSAND, TRACK EAST, BOGEY SPADES.

=== BOGEY DOPE ===
Request for BRAA information on the indicated GROUP or the closest GROUP if not specified. Does not imply fighter targeting.
MIKE, EAGLE 11, BOGEY DOPE NORTH GROUP.
EAGLE 11, NORTH GROUP BRAA 2-1-0/28, THIRTY-EIGHT THOUSAND, HOT, HOSTILE.

=== NAILS ===
Fighter's radar warning receiver is detecting an airborne interceptor radar in search mode. Called with bearing or cardinal direction.
EAGLE 1, NAILS 2-7-0.

=== SPIKED ===
Fighter is being actively tracked by an airborne radar. Called with bearing or cardinal direction. Controller correlates to a GROUP within ±30 degrees and responds with range, altitude, aspect, declaration, and GROUP name.
EAGLE 1, SPIKED 2-7-0.
EAGLE 1, SPIKE RANGE 17, THIRTY THOUSAND, HOSTILE EAST GROUP, TWO CONTACTS.

=== THREAT Call ===
If a fighter will pierce THREAT range to an untargeted GROUP, the controller makes a THREAT call in BRAA format no later than THREAT range.
HEAT 31, ADDITIONAL GROUP THREAT, BRAA 1-2-5/35, THIRTY-FIVE THOUSAND, HOT, HOSTILE.

If the THREAT is within 5 nm of friendly fighters:
BOLT 1, THREAT NORTH THREE, TEN THOUSAND, TRACK SOUTH, HOSTILE.

=== FADED and VANISHED ===
'''FADED''' — a previously tracked GROUP not updated by sensors for 30 seconds. The controller reports the GROUP as FADED with last known BULLSEYE position. Fighters maintain MONITOR responsibility if they can maintain correlation. FADED is not used for friendly aircraft — controllers use NEGATIVE CONTACT for friendlies not held on sensors.

'''VANISHED''' — a special case of FADED used when the GROUP is not in a known blind zone and is correlated to a friendly shot that meets parameters for successful termination.

=== Unexpected Contacts ===
Three distinct call types exist for contacts not part of the established picture:

{| class="wikitable" style="width:100%;"
|-
! Call !! Criteria !! Format
|-
| '''ADDITIONAL GROUP''' || Newly detected outside targeting range, or does not fit traditional label || BULLSEYE
|-
| '''POP-UP GROUP''' || Previously undetected; appears inside targeting range but outside THREAT range || BULLSEYE
|-
| '''THREAT GROUP''' || Undetected or unreported GROUP meeting briefed THREAT criteria || BRAA to the closest aircraft
|}

DARKSTAR, POP-UP GROUP BULLSEYE 2-7-0/15, FIVE THOUSAND, TRACK WEST, BOGEY SPADES.
RAMBO 2, THREAT GROUP BRAA 2-7-0/13, ONE THOUSAND, HOT, HOSTILE.

== 04 / Engagement ==
The engagement loop is the core sequence executed by all fighter flights once committed and targeting is established. It repeats until the GROUP is splashed, leaves the area, or the flight resets.

=== MELD ===
The flight lead directs all flight members to shift their radars from wide sanitization to focused SA on the assigned GROUP. This transition narrows the radar from maximum azimuth and altitude coverage to a tighter volume centered on the target. Sanitization of the surrounding airspace ceases until DROPPING is called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''All flight members shift radar from sanitization to the assigned GROUP''
|}

=== SORT ===
The flight lead assigns individual contacts within the GROUP to specific flight members. Each member acknowledges with SORTED when they have confirmed their assigned contact on radar and are prepared to engage it. If a member cannot confirm their assigned contact, SORTED is withheld until resolution.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || ''(intraflight) FLIGHT SORT {Criteria}''
|-
| #2 || ''(intraflight) #2 SORTED''
|-
| #3 || ''(intraflight) #3 SORTED''
|-
| #4 || ''(intraflight) #4 SORTED''
|}

=== JUDY ===
Called by the flight lead when the flight no longer requires controller guidance to prosecute the intercept. From this point, the controller minimizes transmissions and provides situational awareness information only. JUDY is not always called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Provides SA and THREAT calls only.''
|}

=== ENGAGE ===
Directive call from the flight lead to a specific wingman to employ weapons. The flight lead may also direct simultaneous employment by multiple members.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} ENGAGE
|-
| Wingman || {CS}
|}

=== Weapon Employment ===
The firing aircraft calls the shot on TACC2 NET immediately after employment. The call includes shot type, GROUP label, contact description, BULLSEYE position, and altitude. The controller acknowledges with COPY SHOT.

If a fighter determines a GROUP HOSTILE and ROE has been met, the fighter may employ autonomously and include HOSTILE in the shot transmission.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft || {TACC2-CS} {CS} FOX THREE {Group Label} {Contact Description} BULLSEYE {Bearing/Range} {Altitude}
|-
| TACC2 || {TACC2-CS} COPY SHOT
|-
| colspan="2" style="text-align:center;" | ''Autonomous HOSTILE employment''
|-
| Firing Aircraft || {Controller-CS} {CS} FOX THREE {Group Label} BULLSEYE {Bearing/Range} {Altitude} HOSTILE
|-
| TACC2 || {TACC2-CS} COPY SHOT
|}

Multiple shots in one transmission are acceptable:
SHADOW12 FOX THREE NORTH GROUP LEAD CONTACT BULLSEYE 2-7-0/20 TWENTY THOUSAND; SHADOW11 FOX THREE NORTH GROUP TRAIL CONTACT.

=== OUT / DEFENDING ===
Following weapon employment the flight turns away from the threat. OUT is a planned maneuver executed at a prebriefed range. DEFENDING indicates a reactive maneuver against an incoming weapon and is called with the cardinal direction of the defensive turn.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction}
|-
| colspan="2" style="text-align:center;" | ''or, if reacting to an incoming weapon''
|-
| Aircraft || {CS} DEFENDING {Direction}
|}

=== DROPPING ===
May be called in conjunction with OUT. Signals the controller that the flight has ceased monitoring the GROUP and is returning to sanitization radar settings. Monitoring responsibility transfers back to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction} DROPPING {Group Label}
|-
| colspan="2" style="text-align:center;" | ''Controller resumes monitoring of the dropped GROUP''
|-
| Controller || ''Resumes monitoring.''
|}

=== Assessment ===
The flight assesses weapon effects from sensor data or controller reports. Three outcomes are possible:

{| class="wikitable" style="width:100%;"
|-
! Outcome !! Action
|-
| GROUP splashed || Call SPLASH
|-
| GROUP remains a factor, follow-up shot required || Turn IN, return to MELD
|-
| GROUP has left the area or is no longer a factor || Proceed with Tasking
|}

=== IN (Follow-up Engagement) ===
If the GROUP remains a factor and the tactic permits a follow-up shot, the flight turns back toward the GROUP. The IN call triggers a new cycle beginning at MELD.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IN {Direction}
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''Re-sort as required, then return to ENGAGE''
|}

=== SPLASH ===
Called when weapon effects confirm the GROUP or contact is destroyed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft or Controller || {CS} SPLASH {Group Label or Contact Description}
|}

----

== 05 / Defensive Counter Air (DCA) ==
DCA is the use of fighter aircraft to defend a ground asset or airspace against hostile air threats. It uses prebriefed lanes and defined ranges.

=== DCA Range Structure ===
All ranges are prebriefed per sortie. The following are the standard range lines used in DCA:

{| class="wikitable" style="width:100%;"
|-
! Range Line !! Definition
|-
| '''Mission Fail Line''' || The line the enemy must not cross for the mission to succeed. Defines the maximum depth of the defensive problem.
|-
| '''Commit Line (CL)''' || The line at which a bogey is declared HOSTILE IAW theater ROE and the flight is authorized to commit. Prebriefed for all DCA sorties.
|-
| '''Targeting Range''' || The prebriefed distance at which all contacts must be intercepted. A GROUP inside this range with no assigned fighter is UNTARGETED. Prebriefed per sortie.
|-
| '''TAC Range''' || Default 60 nm from the closest fighter to the closest GROUP. Signals all players to prepare for targeting.
|-
| '''Threat Range''' || The prebriefed range at which an untargeted GROUP meeting THREAT criteria triggers a THREAT call. Prebriefed per sortie.
|}

=== COMMIT Authority ===
COMMIT authority is derived from the combatant commander and delegated through the chain of command. Any of the following may hold or recommend COMMIT authority depending on what is delegated:

{| class="wikitable" style="width:100%;"
|-
! Role !! Abbreviation !! Authority
|-
| Flight Lead || FL || Usually holds COMMIT authority unless delegated
|-
| Team Lead || TL || May hold COMMIT authority if delegated
|-
| Mission Commander || MC || May hold COMMIT authority if delegated
|-
| TACC2 || — || May hold COMMIT authority if delegated
|}

If only the MC, TL, or FL holds COMMIT authority, the controller may only recommend COMMIT. If the controller holds COMMIT authority, the MC and TL may only recommend.

=== DCA Flow ===

==== Lane Handover ====
When an outgoing flight is relieved on station by an incoming flight, a positive lane handover is required before the outgoing flight departs.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Off-going Lane Commander || {CS} MOVE FORWARD
|-
| On-coming Lane Commander || {CS}
|-
| colspan="2" style="text-align:center;" | ''On-coming aircraft may enter the lane. Lane commander authority has not yet transferred.''
|-
| Off-going Lane Commander || {CS} YOU HAVE THE LANE
|-
| On-coming Lane Commander || {CS} HAS THE LANE
|}

The off-going flight passes critical mission information to the controller before departing. The controller passes big-picture information to the on-coming flight before pushing them to the tactical frequency.

==== Pre-Commit ====
The flight arrives at its prebriefed CAP position with FENCE IN complete and radars in sanitization configuration. The controller holds picture responsibility.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} PICTURE
|-
| Controller || {CS} {Nr of Groups} {Group Label} BULLSEYE {Bearing/Range} {Altitude} TRACK {Direction} {Declaration} {Nr of Contacts}
|}

The flight evaluates commit criteria continuously. Pictures are requested as needed to maintain SA.

==== Commit ====

===== FIGHTER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} Recommend {CS} COMMIT
|-
| FL || {CS} COMMIT
|}

===== CONTROLLER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} Recommend Commit
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} {CS} COMMIT
|-
|FL
|{CS}
|}

After COMMIT, fighters hold radio priority.

=== Engagement Loop ===
The flight executes the standard engagement loop as defined above The loop repeats until the GROUP is splashed, leaves the lane, or:

Once the Engagement is Complete the flight '''RESETS''' back to the briefed Position

==== RESET ====
Directs the flight to return to its prebriefed position or area of operations. RESET implies DROPPING and returns all targeting responsibility to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} RESET
|-
| colspan="2" style="text-align:center;" | ''Flight returns to prebriefed CAP position. Controller resumes full picture responsibility''
|}

----

== 06 / Offensive Counter Air (OCA) ==
OCA is the use of fighter aircraft to suppress, destroy, or neutralize enemy air assets before they can threaten friendly forces. Unlike DCA, OCA is not lane-based and does not require a commit line. The flight pushes into the threat environment rather than waiting for the threat to approach.

=== OCA Range Structure ===
The same range lines apply as in DCA — Threat Range, Targeting Range, and TAC Range — but all are prebriefed based on the specific mission geometry and threat environment. There is no commit line or mission fail line in OCA.

=== OCA Flow ===
OCA does not have a lane handover or a commit phase. The flight checks in, receives the picture, establishes targeting, and executes the engagement loop.

==== FULL COMMUNICATIONS EXAMPLE ====
In this Scenario, SHADOW11 four-ship F16C on OCA. TACC2 Agency CS THUMPER executing Positive Control. The Example begins after the Handover. Check In was done on the previous Frequency. TAC RANGE 60, THREAT RANGE 30
THUMPER SHADOW11 PICTURE

THUMPER PICTURE TEN GROUPS GROUP BULLSEYE 0-2-0/25, TWENTY-SEVEN THOUSAND, THOUSAND, TRACK EAST, HOSTILE, HEAVY, THREE CONTACTS. GROUP BULLSEYE 2-7-0/25, FIFTEEN THOUSAND, TRACK WEST, HOSTILE. GROUP BULLSEYE 2-9-0/35, TEN THOUSAND, TRACK WEST, HOSTILE.

SHADOW11 TARGETED GROUP BULLSEYE 0-2-0/25

SHADOW11 GROUP BULLSEYE 0-2-0/25 TAC RANGE

SHADOW11 SKATE, MELD

SHADOW11 SORTED

SHADOW11 FOX3 BULLSEYE 0-2-0/25

THUMPER COPY SHOT

SHADOW11 OUT SOUTH DROPPING

THUMPER

THUMPER SHADOW11 BOGEYDOPE

SHADOW11 EAST GROUP BRAA 2-1-0/28, FIFTEEN-THOUSAND, COLD, HOSTILE

SHADOW11 IN, MELD, SORTED

THUMPER SHADOW11 SPLASH EAST GROUP

THUMPER
In the Following Example additional Adversarys Pop Up within Threat Range of SHADOW11
SHADOW11 THREAT GROUP, BRAA 1-2-5/28, FIVE-THOUSAND, HOT, HOSTILE, 2 CONTACTS

SHADOW11 TARGETED, SORTED LEAD, FOX 3 LEADER, FOX3 TRAILER, BULLSEYE 0-5-0/45, FIVE-THOUSAND

THUMPER COPY SHOT

SHADOW11 DEFENDING SOUTH, DROPPING

THUMPER

SHADOW11 THUMPER THREAT GROUP, BRAA 0-6-0/15, TWO-THOUSAND, COLD, HOSTILE

SHADOW11

SHADOW11 IN

SHADOW11 FOX3 BULLSEYE 0-6-0/15, TWO-THOUSAND

THUMPER COPY SHOT

SHADOW11 THUMPER THREAT GROUP VANISHED
----

== 07 / QRA ==

== 08 / Intercept (VID) ==
A Visual Identification (VID) intercept is conducted when a contact cannot be declared HOSTILE or FRIENDLY by electronic means alone, and visual confirmation of aircraft type, markings, or behavior is required before engagement authority can be granted or withheld.

VID intercepts follow a structured sequence: the controller guides the fighter to a position from which a visual identification pass can be made, then the fighter reports the result and awaits further direction.

=== Intercept Flow ===

==== Commit ====
The controller or flight lead initiates the intercept against the unidentified contact.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} COMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration} {Nr of Contacts}
|-
| FL || {CS} COMMIT
|}

==== Guidance ====
The controller provides vectors to position the fighter for a VID pass. This is the only phase where the controller takes positive close control of the intercept geometry. BRAA format is used throughout.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} BRAA {Bearing/Range} {Altitude} {Aspect} {Declaration}
|-
| FL || {CS}
|-
| colspan="2" style="text-align:center;" | ''Controller continues to provide updated vectors until fighter calls JUDY''
|}

==== JUDY ====
The fighter calls JUDY when radar contact is established and no further controller guidance is required. The controller minimizes transmissions from this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Continues to provide SA information only.''
|}

==== Tally ====
The fighter calls TALLY when visual contact is established with the target.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} TALLY {Position}
|}

==== Identification ====
The fighter conducts the VID pass and reports the result to the controller. The report includes aircraft type, markings, and behavior observed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IDENTIFIED {Aircraft Type} {Markings / Behavior}
|-
| Controller || {CS} {Further Instructions / Declaration Update}
|}

If the contact is identified as HOSTILE following the VID pass, the controller issues the updated declaration and the flight may proceed to engagement IAW ROE. If the contact is FRIENDLY or NEUTRAL, the flight disengages and returns to its prebriefed position.

----

== 09 / Merge ==
A merge occurs when friendly and target aircraft arrive in the visual arena, within 3–5 nm of each other. At the merge, radar resolution becomes limiting and the engagement transitions from BVR to Within Visual Range (WVR).

=== Communication Priority at the Merge ===
The engaged fighter holds radio priority. The supporting fighter and controller subordinate their transmissions accordingly.

{| class="wikitable" style="width:100%;"
|-
! Role !! Responsibility
|-
| '''Engaged Fighter''' || Calls the merge, manages the engagement, and calls employment and results. Holds radio priority.
|-
| '''Supporting Fighter''' || Provides SA to the engaged fighter. Calls PRESS when directed and mutual support is maintained. Subordinates transmissions to the engaged fighter.
|-
| '''Controller''' || Minimizes transmissions. Provides THREAT calls, SA updates, and responds to fighter requests only.
|}

=== Merge Flow ===

==== MERGED ====
The controller calls MERGED when radar tracks come together within 3–5 nm, or the engaged fighter calls it when visual contact is made.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Engaged Fighter || {CS} MERGED {Group Label}
|}

==== IFF Calls ====
At the merge, positive visual identification of friend or foe is critical before employment. Standard IFF calls apply:

Squadrons should define their own IFF procedures to ensure fast execution

{| class="wikitable" style="width:100%;"
|-
! Term !! Meaning
|-
| '''TALLY''' || Visual contact established on the target or bandit
|-
| '''NO JOY''' || No visual contact with the target or bandit
|-
| '''VISUAL''' || Visual contact established on a friendly aircraft
|-
| '''BLIND''' || No visual contact with a friendly aircraft
|}

==== PRESS ====

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} PRESS
|-
| Supporting Fighter || PRESS
|}

==== Employment ====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || {Controller-CS} {CS} FOX TWO {Target Description}
|-
| Controller || COPY SHOT
|}

Gun employment is called as GUNS with target description.

==== SPLASH ====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || {Controller-CS} {CS} SPLASH {Group Label or Contact Description}
|-
| Controller || {CS} COPY SPLASH
|}

Following SPLASH the flight disengages, calls RESET, and returns to its prebriefed position unless directed otherwise.

MTTP/A2S

2026-05-23T15:05:21Z

Niknam3: /* Strike */

== Fundamentals ==
Air-to-surface operations require a shared vocabulary for describing the progression from finding a target to destroying it. The Find, Fix, Track, Target, Engage, and Assess (F2T2EA) sequence governs the flow of a surface attack and the brevity that supports it.

=== Target Acquisition Brevity ===
The following brevity codes describe the state of sensor awareness on a surface target. They are used throughout the F2T2EA (Find, Fix, Track, Target, Engage and Assess) chain by both fighters and controllers.
{| class="wikitable" style="width:100%;"
!Brevity
!Definition
|-
|'''DIRT'''
|Radar warning receiver indication of a surface threat in search mode. The threat is radiating but has not yet established a track.
|-
|'''MUD'''
|Radar warning receiver indication of a surface threat in track mode. The threat has established a track on the aircraft.
|-
|'''SINGER'''
|Radar warning receiver indication of a SAM launch. The threat has fired.
|-
|'''SCAN'''
|Search the indicated sector and report any contacts.
|-
|'''WORK'''
|Directive call to conduct geolocation on a specific target or area.
|-
|'''INVESTIGATE'''
|Verify specified elements of ROE, positive identification (PID), and coordination of forces on the referenced target or track.
|-
|'''FIXED'''
|Target has been located and its position established. Followed by accuracy qualifier: LOW ACCURACY (inside 1 nm) or HIGH ACCURACY (inside 1,000 ft).
|-
|'''MONITOR'''
|Maintain sensor awareness on a specified GROUP or object. Implies tactically significant changes will be communicated.
|-
|'''TRACK'''
|Directive call assigning responsibility to an asset for maintaining sensor or visual observation of a defined object or area.
|-
|'''CAPTURED'''
|Object has been acquired and is being actively tracked.
|-
|'''COVER'''
|Directive call to be ready for reattack or re-engage if weapon effects are not achieved.
|-
|'''HOUNDDOG'''
|Aircraft is in a position to employ weapons. Used in response to COVER.
|}

=== TRESPASS ===
Called when an aircraft enters a non-previously-known SAM MEZ or when any non-SEAD aircraft crosses inside the maximum recommended intercept range of a known SAM. The calling entity directs an immediate SNAP heading away from the threat.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Controller or Aircraft
|{CS} SNAP {Heading} TRESPASS {Threat Type} BULLSEYE {Bearing/Range}
|}
RAMBO 2, SNAP 1-7-0, TRESPASS FIFTEEN BULLSEYE 3-2-0/32.

=== Game Plan ===
The flight lead issues the game plan before pushing to the target. All flight members acknowledge in sequence. The game plan assigns targeting responsibility, cover responsibility, and establishes the push time and TOT. The Following are two examples for possible Gameplans. Note that this part is highly flxible
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|MC
|HORNET, BOLT, PYTHON, STANDBY GAME PLAN
|-
|FLs
|"HORNET" "BOLT" "PYTHON"
|-
|MC
|“HORNET, TARGET AND SCAN ALPHA ALPHA 0-1, TWO VEHICLE
CONVOY BULLSEYE 2-7-5/69, MOVING SOUTH, BEST. PUSH AT

21:17 FROM RED OSCAR.”

“BOLT, COVER ALPHA ALPHA 0-1.”

“RAMBO ESCORT AND PYTHON SEAD PER BRIEF.”
|-
|FLs
|“HORNET.” “BOLT.” “PYTHON.”
|}
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|FL
|SHADOW11 #1 AND #2 TARGET {Target Description} · #3 AND #4 COVER {Target Description}
|-
|All Members
|#2 · #3 · #4
|}
Target and cover assignments may be communicated digitally via data link. Each player acknowledges GOOD DATA if received digitally.
----

== Strike ==
A strike is a planned attack against a pre-briefed fixed or moving ground target. The progression from initial detection to confirmed destruction follows the '''Find, Fix, Track, Target, Engage, and Assess (F2T2EA)''' sequence. Each step has specific brevity and responsibilities. Not every mission requires the same. A pre-briefed fixed target may enter the chain at Track or Target but every step must be satisfied before weapons can be released.

All communications are on the TAC C2 NET unless stated otherwise.

=== Find ===
FIND is the umbrella term for the search phase. It encompasses two activities: searching an area for a target (WORK) and confirming that a located target meets the requirements for engagement (INVESTIGATE).

'''WORK''' is a directive call to conduct geolocation on a specified target or area.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|MC
|{CS} WORK {Target Description or Area} BULLSEYE {Bearing/Range}
|-
|Aircraft
|{CS} WORKING {Target Description or Area} BULLSEYE {Bearing/Range}
|}
'''INVESTIGATE''' is a directive call to verify specified elements of ROE, PID, and coordination of forces on the referenced target or track before engagement can proceed.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|MC
|{CS} INVESTIGATE {Target Description or Track Number}
|-
|Aircraft
|{CS} INVESTIGATING
|}

=== Fix ===
Once the target has been located, its position is established and communicated with a quality assessment. The fix quality determines whether the target is TARGETABLE — that is, whether the position data is accurate enough to support weapon employment.
{| class="wikitable" style="width:100%;"
!Accuracy
!Standard
!Call
|-
|'''Low Accuracy'''
|Inside 1 nm
|{CS} {Target Description} FIXED BULLSEYE {Bearing/Range} LOW ACCURACY
|-
|'''High Accuracy'''
|Inside 1,000 ft
|{CS} {Target Description} FIXED BULLSEYE {Bearing/Range} HIGH ACCURACY
|-
|'''Targetable'''
|Fix quality sufficient for weapon employment
|{CS} {Target Description} FIXED BULLSEYE {Bearing/Range} TARGETABLE
|}
TARGETABLE is the advisory call that position data meets the standard required to proceed to TARGET and ENGAGE. Only when TARGETABLE has been established may ordnance be employed against the target.
HOSS 3, FIXED CONVOY BULLSEYE 3-1-7/17, TARGETABLE.

=== Track ===
TRACK assigns responsibility for maintaining continuous sensor or visual observation of the target. MONITOR is used when continuous tracking is not required but tactically significant changes must be reported. CAPTURED confirms the aircraft has acquired and is actively tracking the target.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|MC
|{CS} TRACK {Target Description} BULLSEYE {Bearing/Range}
|-
|Aircraft
|{CS} CAPTURED {Target Description}
|-
| colspan="2" style="text-align:center;" |''If unable to acquire''
|-
|Aircraft
|{CS} NO JOY
|}
MC: SABRE, TRACK T-72 COLUMN BULLSEYE 0-5-0/55, MOVING NORTH.
SABRE: SABRE, CAPTURED, TRACK NUMBER 2-2-2-2-2.

=== Target ===
TARGET is the assignment of targeting responsibility for a specific object or track. Before TARGET can be called, the following must be satisfied: ROE, PID, coordination of forces, and commander's guidance requirements on the referenced target. Clear field of fire must also be confirmed prior to employing ordnance.

TARGET is a directive call from the MC or flight lead. It establishes who is responsible for the attack. It does not automatically authorize weapons release — ENGAGE does.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|MC or Flight Lead
|{CS} TARGET {Target Description} BULLSEYE {Bearing/Range}
|-
|Aircraft
|{CS}
|}

==== COVER ====
If the flight lead deems a cover element necessary, COVER is assigned at this stage. COVER is a positioning directive — it instructs an aircraft to maneuver to a position from which the target can be reattacked immediately if required. It does not order an attack. HOUNDDOG is the response confirming the aircraft is in position and ready.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Flight Lead
|{CS} COVER {Target Description or Bullseye}
|-
|Cover Aircraft
|{CS} HOUNDDOG
|}

=== Engage ===
Once the target is CAPTURED and all targeting requirements are met, the attacking element pushes. PUSHING is called with the TOT on the TAC C2 NET.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Attacking Aircraft
|{Controller-CS} {CS} CAPTURED {Target Description or Bullseye} PUSHING TOT {Time}
|-
| colspan="2" style="text-align:center;" |''On weapon release''
|-
|Attacking Aircraft
|{Controller-CS} {CS} ONE WEAPON AWAY {Target Description} {Time of Flight} SECONDS {LASING / SCANNING if applicable}
|}

=== Assess ===
The attacking aircraft calls the result once weapon effects can be observed. Two outcomes are possible:
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
| colspan="2" style="text-align:center;" |''Desired weapon effects generated''
|-
|Attacking Aircraft
|{Controller-CS} {CS} SPLASH {Target Description} SUCCESSFUL
|-
|Attacking Aircraft
|{Controller-CS} {CS} DROPPING {Target Description}
|-
| colspan="2" style="text-align:center;" |''Desired weapon effects not generated''
|-
|Attacking Aircraft
|{Controller-CS} {CS} SPLASH {Target Description} FUMBLE {CLEAN / HIT}
|}
'''FUMBLE CLEAN''' — no visible battle damage and no weapon impact observed. The weapon missed entirely.

'''FUMBLE HIT''' — weapon impact was observed within a lethal distance but desired weapon effects were not generated.

=== Reattack ===
REATTACK is the directive to conduct a follow-up attack on the same target. It can be ordered at any time after a FUMBLE assessment.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|MC or Flight Lead
|{CS} REATTACK {Target Description or Bullseye}
|-
|Reattacking Aircraft
|{Controller-CS} {CS} PUSHING TOT {Time}
|-
|Reattacking Aircraft
|{Controller-CS} {CS} ONE WEAPON AWAY {Time of Flight} SECONDS
|-
|Reattacking Aircraft
|{Controller-CS} {CS} SPLASH {Target Description} {SUCCESSFUL / FUMBLE}
|}

=== Egress ===
Following the attack, the flight egresses using one of three calls depending on the situation:
{| class="wikitable" style="width:100%;"
!Call
!Condition
!Phrase
|-
|'''MILLER TIME'''
|Last striker in the package has completed the attack
|{Controller-CS} {CS} MILLER TIME
|-
|'''BUGOUT'''
|Aircraft has completed its attack and has no intention to return
|{Controller-CS} {CS} BUGOUT {Direction}
|-
|'''OFF'''
|Aircraft has completed its attack and is repositioning or egressing within the area
|{Controller-CS} {CS} OFF {Direction}
|}

== SEAD ==
Suppression of Enemy Air Defenses (SEAD) is the action taken to neutralize, destroy, or temporarily degrade surface-to-air missile systems and associated radar emitters. Its purpose is to allow other aircraft to operate within a threat environment that would otherwise deny or restrict their access.

=== The SEAD Game Plan ===
Before the mission, the SEAD lead establishes contracts with the rest of the package: who responds to which threat, in what priority order, with which weapon, and under what conditions.

The underlying logic of SEAD is straightforward. A SAM battery that is actively radiating is vulnerable to antiradiation missiles. A SAM battery that goes silent to avoid being targeted is temporarily suppressed and cannot engage aircraft. Either outcome — destruction or suppression — achieves the mission objective of protecting the package.

SEAD aircraft therefore have two primary tools:

* '''Hard kill''' — employment of an antiradiation missile (ARM) against a radiating threat. The ARM homes on the radar emission. If the radar goes silent the missile loses guidance, so the threat must be forced to stay radiating or be caught radiating.
* '''Soft kill''' — electromagnetic jamming (CANYON) that degrades the threat radar's ability to track or guide a missile without destroying the system.

The decision between hard and soft kill, and between SNIPER (range-known) and SLAPSHOT (range-unknown, immediate), is made based on the quality of targeting data available and the urgency of the situation.

=== Threat Reaction and SEAD Response Contracts ===
When a SAM threat is detected, the aircraft communicates on the mission tactical NET to enable reactive SEAD and maintain the common tactical picture.
{| class="wikitable" style="width:100%;"
!Fidelity
!Format
!Example
|-
|'''Low'''
|Call sign · RWR indication · bearing · DEFENDING with cardinal direction · ownship BULLSEYE
|HORNET 1, SINGER ELEVEN, BEARING 3-6-0, DEFENDING WEST, BULLSEYE 3-4-5/30
|-
|'''High'''
|Call sign · RWR indication · threat BULLSEYE/location · DEFENDING with cardinal direction
|BOLT 1, SINGER ELEVEN, BULLSEYE 3-6-0/32, DEFENDING WEST
|}
High fidelity is defined as a 5 nm semi-major ellipse accuracy or better. Use high fidelity when available — it enables SEAD aircraft to engage with precision rather than azimuth alone.

When a friendly aircraft calls DEFENDING, SEAD aircraft respond with one of the following:
{| class="wikitable" style="width:100%;"
!Response
!Definition
!Meaning
|-
|'''HARM INBOUND'''
|[A/S] [EW] High-speed antiradiation missile already employed
|ARM is already in the air — the threat is being engaged
|-
|'''MAGNUM'''
|[A/S] [EW] Launch of FRIENDLY antiradiation missile
|ARM is being launched now in response to this call
|-
|'''ARIZONA'''
|[A/S] [EW] No antiradiation missile ordnance remaining
|SEAD aircraft is Winchester on ARMs
|}
These responses must be pre-briefed as contracts. Every aircraft in the package needs to know which SEAD asset covers which threat axis, what the response will be, and what to do if the SEAD asset is ARIZONA or unable to respond.

==== SNIPER and SLAPSHOT ====
Two directive calls are used to order ARM employment:

'''SNIPER''' — directive call to employ an antiradiation missile against a range-known threat. Used when targeting data is of sufficient quality to give a precise location.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|SEAD Lead
|{CS} SNIPER {Threat Type} BULLSEYE {Bearing/Range}
|-
|SEAD Aircraft
|{CS} MAGNUM {Threat Type} BULLSEYE {Bearing/Range}
|}
'''SLAPSHOT''' — directive call to immediately employ the best available antiradiation missile against a specified threat at the specified bearing. Range is unknown. Used when a threat is actively engaging friendly aircraft and there is no time to refine targeting data.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|SEAD Lead
|{CS} SLAPSHOT {Threat Type} BEARING {Bearing}
|-
|SEAD Aircraft
|{CS} HARM INBOUND
|}
The distinction matters: SNIPER is deliberate and precise, SLAPSHOT is immediate and azimuth-only. A SLAPSHOT ARM may not hit the radar if it goes silent, but it forces the threat to shut down or risk destruction — either outcome protects the package.

MTTP/A2S

2026-05-23T14:31:48Z

Niknam3: /* Strike */

== Fundamentals ==
Air-to-surface operations require a shared vocabulary for describing the progression from finding a target to destroying it. The Find, Fix, Track, Target, Engage, and Assess (F2T2EA) sequence governs the flow of a surface attack and the brevity that supports it.

=== Target Acquisition Brevity ===
The following brevity codes describe the state of sensor awareness on a surface target. They are used throughout the F2T2EA (Find, Fix, Track, Target, Engage and Assess) chain by both fighters and controllers.
{| class="wikitable" style="width:100%;"
!Brevity
!Definition
|-
|'''DIRT'''
|Radar warning receiver indication of a surface threat in search mode. The threat is radiating but has not yet established a track.
|-
|'''MUD'''
|Radar warning receiver indication of a surface threat in track mode. The threat has established a track on the aircraft.
|-
|'''SINGER'''
|Radar warning receiver indication of a SAM launch. The threat has fired.
|-
|'''SCAN'''
|Search the indicated sector and report any contacts.
|-
|'''WORK'''
|Directive call to conduct geolocation on a specific target or area.
|-
|'''INVESTIGATE'''
|Verify specified elements of ROE, positive identification (PID), and coordination of forces on the referenced target or track.
|-
|'''FIXED'''
|Target has been located and its position established. Followed by accuracy qualifier: LOW ACCURACY (inside 1 nm) or HIGH ACCURACY (inside 1,000 ft).
|-
|'''MONITOR'''
|Maintain sensor awareness on a specified GROUP or object. Implies tactically significant changes will be communicated.
|-
|'''TRACK'''
|Directive call assigning responsibility to an asset for maintaining sensor or visual observation of a defined object or area.
|-
|'''CAPTURED'''
|Object has been acquired and is being actively tracked.
|-
|'''COVER'''
|Directive call to be ready for reattack or re-engage if weapon effects are not achieved.
|-
|'''HOUNDDOG'''
|Aircraft is in a position to employ weapons. Used in response to COVER.
|}

=== TRESPASS ===
Called when an aircraft enters a non-previously-known SAM MEZ or when any non-SEAD aircraft crosses inside the maximum recommended intercept range of a known SAM. The calling entity directs an immediate SNAP heading away from the threat.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Controller or Aircraft
|{CS} SNAP {Heading} TRESPASS {Threat Type} BULLSEYE {Bearing/Range}
|}
RAMBO 2, SNAP 1-7-0, TRESPASS FIFTEEN BULLSEYE 3-2-0/32.

=== Game Plan ===
The flight lead issues the game plan before pushing to the target. All flight members acknowledge in sequence. The game plan assigns targeting responsibility, cover responsibility, and establishes the push time and TOT. The Following are two examples for possible Gameplans. Note that this part is highly flxible
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|MC
|HORNET, BOLT, PYTHON, STANDBY GAME PLAN
|-
|FLs
|"HORNET" "BOLT" "PYTHON"
|-
|MC
|“HORNET, TARGET AND SCAN ALPHA ALPHA 0-1, TWO VEHICLE
CONVOY BULLSEYE 2-7-5/69, MOVING SOUTH, BEST. PUSH AT

21:17 FROM RED OSCAR.”

“BOLT, COVER ALPHA ALPHA 0-1.”

“RAMBO ESCORT AND PYTHON SEAD PER BRIEF.”
|-
|FLs
|“HORNET.” “BOLT.” “PYTHON.”
|}
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|FL
|SHADOW11 #1 AND #2 TARGET {Target Description} · #3 AND #4 COVER {Target Description}
|-
|All Members
|#2 · #3 · #4
|}
Target and cover assignments may be communicated digitally via data link. Each player acknowledges GOOD DATA if received digitally.
----

=== Strike ===
A strike is a planned attack against a pre-briefed fixed or moving ground target. The progression from initial detection to confirmed destruction follows the '''Find, Fix, Track, Target, Engage, and Assess (F2T2EA)''' sequence. Each step has specific brevity and responsibilities. Not every step requires the same level of effort — a pre-briefed fixed target may enter the chain at Track or Target — but every step must be satisfied before weapons can be released.

==== Find ====
FIND is the umbrella term for the search phase. It encompasses two activities: searching an area for a target (WORK) and confirming that a located target meets the requirements for engagement (INVESTIGATE).

'''WORK''' is a directive call to conduct geolocation on a specified target or area.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| MC || ''(intraflight) {CS} WORK {Target Description or Area} BULLSEYE {Bearing/Range}''
|-
| Aircraft || ''(intraflight) {CS} WORKING {Target Description or Area} BULLSEYE {Bearing/Range}''
|}

'''INVESTIGATE''' is a directive call to verify specified elements of ROE, PID, and coordination of forces on the referenced target or track before engagement can proceed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| MC || ''(intraflight) {CS} INVESTIGATE {Target Description or Track Number}''
|-
| Aircraft || ''(intraflight) {CS} INVESTIGATING''
|}

==== Fix ====
Once the target has been located, its position is established and communicated with a quality assessment. The fix quality determines whether the target is TARGETABLE — that is, whether the position data is accurate enough to support weapon employment.

{| class="wikitable" style="width:100%;"
|-
! Accuracy !! Standard !! Call
|-
| '''Low Accuracy''' || Inside 1 nm || {CS} {Target Description} FIXED BULLSEYE {Bearing/Range} LOW ACCURACY
|-
| '''High Accuracy''' || Inside 1,000 ft || {CS} {Target Description} FIXED BULLSEYE {Bearing/Range} HIGH ACCURACY
|-
| '''Targetable''' || Fix quality sufficient for weapon employment || {CS} {Target Description} FIXED BULLSEYE {Bearing/Range} TARGETABLE
|}

TARGETABLE is the advisory call that the position data meets the standard required to proceed to TARGET and ENGAGE. Only when TARGETABLE has been established may ordnance be employed against the target.

HOSS 3, FIXED CONVOY BULLSEYE 3-1-7/17, TARGETABLE.

==== Track ====
TRACK assigns responsibility for maintaining continuous sensor or visual observation of the target. MONITOR is used when continuous tracking is not required but tactically significant changes must be reported. CAPTURED confirms the aircraft has acquired and is actively tracking the target.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| MC || ''(intraflight) {CS} TRACK {Target Description} BULLSEYE {Bearing/Range}''
|-
| Aircraft || ''(intraflight) {CS} CAPTURED {Target Description}''
|-
| colspan="2" style="text-align:center;" | ''If unable to acquire''
|-
| Aircraft || ''(intraflight) {CS} NO JOY''
|}

MC: SABRE, TRACK T-72 COLUMN BULLSEYE 0-5-0/55, MOVING NORTH.
SABRE: SABRE, CAPTURED, TRACK NUMBER 2-2-2-2-2.

==== Target ====
TARGET is the assignment of targeting responsibility for a specific object or track. Before TARGET can be called, the following must be satisfied: ROE, PID, coordination of forces, and commander's guidance requirements on the referenced target. Clear field of fire must also be confirmed prior to employing ordnance.

TARGET is a directive call from the MC or flight lead. It does not automatically authorize weapons release — ENGAGE does. TARGET establishes who is responsible for the attack.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| MC or Flight Lead || ''(intraflight) {CS} TARGET {Target Description} BULLSEYE {Bearing/Range}''
|-
| Aircraft || ''(intraflight) {CS}''
|}

If a cover element is deemed necessary by the flight lead, it is assigned at this point as part of the game plan. COVER is a positioning directive — it instructs an aircraft to maneuver to a position from which the target can be reattacked immediately if required. It does not order an attack. HOUNDDOG is the response confirming the aircraft is in position and ready.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || ''(intraflight) {CS} COVER {Target Description or Bullseye}''
|-
| Cover Aircraft || ''(intraflight) {CS} HOUNDDOG''
|}

==== Engage ====
Once the target is CAPTURED and all targeting requirements are met, the attacking element pushes. PUSHING is called with the TOT.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Attacking Aircraft || {Controller-CS} {CS} CAPTURED {Target Description or Bullseye} PUSHING TOT {Time}
|-
| colspan="2" style="text-align:center;" | ''On weapon release''
|-
| Attacking Aircraft || {Controller-CS} {CS} ONE WEAPON AWAY {Target Description} {Time of Flight} SECONDS {LASING / SCANNING if applicable}
|}

==== Assess ====
The attacking aircraft calls the result once weapon effects can be observed. Two outcomes:

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| colspan="2" style="text-align:center;" | ''Desired weapon effects generated''
|-
| Attacking Aircraft || {Controller-CS} {CS} SPLASH {Target Description} SUCCESSFUL
|-
| Attacking Aircraft || {Controller-CS} {CS} DROPPING {Target Description}
|-
| colspan="2" style="text-align:center;" | ''Desired weapon effects not generated''
|-
| Attacking Aircraft || {Controller-CS} {CS} SPLASH {Target Description} FUMBLE {CLEAN / HIT}
|}

'''FUMBLE CLEAN''' — no visible battle damage and no weapon impact observed.

'''FUMBLE HIT''' — weapon impact was observed within a lethal distance but desired effects were not generated.

==== Reattack ====
REATTACK is the directive to conduct a follow-up attack on the same target. It can be ordered at any time after a FUMBLE assessment, with or without a pre-positioned cover element. If a cover element was pre-assigned and has called HOUNDDOG, the reattack can be executed immediately.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| MC or Flight Lead || ''(intraflight) {CS} REATTACK {Target Description or Bullseye}''
|-
| Reattacking Aircraft || {Controller-CS} {CS} PUSHING TOT {Time}
|-
| Reattacking Aircraft || {Controller-CS} {CS} ONE WEAPON AWAY {Time of Flight} SECONDS
|-
| Reattacking Aircraft || {Controller-CS} {CS} SPLASH {Target Description} {SUCCESSFUL / FUMBLE}
|}

==== Egress ====
Following the attack, the flight egresses using one of three calls depending on the situation:

{| class="wikitable" style="width:100%;"
|-
! Call !! Condition !! Phrase
|-
| '''MILLER TIME''' || Last striker in the package has completed the attack || {Controller-CS} {CS} MILLER TIME
|-
| '''BUGOUT''' || Aircraft has completed its attack and has no intention to return || {Controller-CS} {CS} BUGOUT {Direction}
|-
| '''OFF''' || Aircraft has completed its attack and is repositioning or egressing within the area || {Controller-CS} {CS} OFF {Direction}
|}

==== Full Strike Example ====
''(intraflight) SHADOW FLIGHT STANDBY GAME PLAN''
''(intraflight) #2 · #3 · #4''
''(intraflight) SHADOW FLIGHT, #1 AND #2 TARGET CONVOY BULLSEYE 0-3-0/15 · #3 AND #4 COVER''
''(intraflight) #2 · #3 · #4''

SHADOW11 CAPTURED BULLSEYE 0-3-0/15 PUSHING TOT 21:21:15
''(intraflight) SHADOW13 HOUNDDOG''

SHADOW12 ONE WEAPON AWAY CONVOY BULLSEYE 0-3-0/15 THIRTY SECONDS LASING

SHADOW11 SPLASH CONVOY BULLSEYE 0-3-0/15 FUMBLE HIT
''(intraflight) SHADOW13 REATTACK CONVOY BULLSEYE 0-3-0/15''

SHADOW13 PUSHING TOT 21:23:50
SHADOW13 ONE WEAPON AWAY FORTY SECONDS

SHADOW13 SPLASH CONVOY BULLSEYE 0-3-0/15 SUCCESSFUL
SHADOW11 MILLER TIME

== CAS ==
''Content to be added.''
----

== SEAD ==
Suppression of Enemy Air Defenses (SEAD) is the action taken to neutralize, destroy, or temporarily degrade surface-to-air missile systems and associated radar emitters. Its purpose is to allow other aircraft to operate within a threat environment that would otherwise deny or restrict their access.

=== Threat Reaction ===
When a SAM threat is detected, the aircraft communicates on the mission tactical NET to enable reactive SEAD and maintain the common tactical picture.
{| class="wikitable" style="width:100%;"
!Fidelity
!Format
!Example
|-
|'''Low'''
|Call sign · RWR indication · bearing · DEFENDING with cardinal direction · ownship BULLSEYE
|HORNET 1, SINGER ELEVEN, BEARING 3-6-0, DEFENDING WEST, BULLSEYE 3-4-5/30
|-
|'''High'''
|Call sign · RWR indication · threat BULLSEYE/location · DEFENDING with cardinal direction
|BOLT 1, SINGER ELEVEN, BULLSEYE 3-6-0/32, DEFENDING WEST
|}
High fidelity is defined as a 5 nm semi-major ellipse accuracy or better. Use high fidelity when available — it enables SEAD aircraft to engage with precision rather than azimuth alone.

==== The SEAD Game Plan ====
SEAD is not a reactive afterthought — it is a pre-planned, coordinated element of every strike package that operates in a contested environment. Before the mission, the SEAD lead establishes contracts with the rest of the package: who responds to which threat, in what priority order, with which weapon, and under what conditions.

The underlying logic of SEAD is straightforward. A SAM battery that is actively radiating is vulnerable to antiradiation missiles. A SAM battery that goes silent to avoid being targeted is temporarily suppressed and cannot engage aircraft. Either outcome — destruction or suppression — achieves the mission objective of protecting the strike package.

SEAD aircraft therefore have two primary tools:

* '''Hard kill''' — employment of an antiradiation missile (ARM) against a radiating threat. The ARM homes on the radar emission. If the radar goes silent the missile loses guidance, so the threat must be forced to stay radiating or be caught radiating.
* '''Soft kill''' — electromagnetic jamming (CANYON) that degrades the threat radar's ability to track or guide a missile without destroying the system.

The decision between hard and soft kill, and between SNIPER (range-known) and SLAPSHOT (range-unknown, immediate), is made based on the quality of targeting data available and the urgency of the situation.

==== Threat Reaction and SEAD Response Contracts ====
When a friendly aircraft calls DEFENDING, SEAD aircraft respond with one of the following:
{| class="wikitable" style="width:100%;"
!Response
!Definition (ATP 1-02.1)
!Meaning
|-
|'''HARM INBOUND'''
|[A/S] [EW] High-speed antiradiation missile already employed
|ARM is already in the air — the threat is being engaged
|-
|'''MAGNUM'''
|[A/S] [EW] Launch of FRIENDLY antiradiation missile
|ARM is being launched now in response to this call
|-
|'''ARIZONA'''
|[A/S] [EW] No antiradiation missile ordnance remaining
|SEAD aircraft is Winchester on ARMs
|}
These responses must be pre-briefed as contracts. Every aircraft in the package needs to know which SEAD asset covers which threat axis, what the response will be, and what to do if the SEAD asset is ARIZONA or unable to respond.

==== SNIPER and SLAPSHOT ====
Two directive calls are used to order ARM employment:

'''SNIPER''' — directive call to employ an antiradiation missile against a range-known threat. Used when targeting data is of sufficient quality to give a precise location.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|SEAD Lead
|{CS} SNIPER {Threat Type} BULLSEYE {Bearing/Range}
|-
|SEAD Aircraft
|{CS} MAGNUM {Threat Type} BULLSEYE {Bearing/Range}
|}
'''SLAPSHOT''' — directive call to immediately employ the best available antiradiation missile against a specified threat at the specified bearing. Range is unknown. Used when a threat is actively engaging friendly aircraft and there is no time to refine targeting data.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|SEAD Lead
|{CS} SLAPSHOT {Threat Type} BEARING {Bearing}
|-
|SEAD Aircraft
|{CS} HARM INBOUND
|}
The distinction matters: SNIPER is deliberate and precise, SLAPSHOT is immediate and azimuth-only. A SLAPSHOT ARM may not hit the radar if it goes silent, but it forces the threat to shut down or risk destruction — either outcome protects the package.

MTTP/A2S

2026-05-23T14:21:16Z

Niknam3: /* Fundamentals */

MTTP/A2A

2026-05-23T12:55:09Z

Niknam3: /* FULL COMMUNICATIONS EXAMPLE */

== 01 / Overview ==
Air combat is primarily carried out by CAP aircraft. The two main mission types are '''DCA''' (Defensive Counter Air) and '''OCA''' (Offensive Counter Air).

=== Groups and Contacts ===
A '''GROUP''' is any number of air contacts within 3 nm in azimuth and range of each other. A '''CONTACT''' is an individual radar return within a GROUP. Single contact is the assumed strength for all GROUPs unless otherwise specified. A GROUP with three or more contacts is called '''HEAVY'''.

The '''PICTURE''' establishes a common tactical air image and describes the spatial relationship of GROUPs. It is always communicated in BULLSEYE format unless briefed otherwise. Only the Three GROUPs with highest Priority are Conveyed

=== Contact Declaration ===
Before a fighter can engage, a contact must be declared. Declaration is performed by the controller in response to a DECLARE request.

{| class="wikitable" style="width:100%;"
|-
! Declaration !! Meaning !! Engagement Authority
|-
| '''BOGEY''' || Identity unknown || Not cleared to engage
|-
| '''OUTLAW''' || Originates from known or suspected hostile area || Not cleared to engage; escalation criteria apply
|-
| '''SPADES''' || No valid IFF response on interrogation || Not cleared to engage; escalation criteria apply
|-
| '''BANDIT''' || Positively identified as enemy IAW theater ID criteria || Not cleared to engage; does not imply authority to fire
|-
| '''HOSTILE''' || Confirmed enemy; clearance to fire authorized IAW ROE || Cleared to engage
|-
| '''NEUTRAL''' || Positively identified as neutral || Not cleared to engage
|-
| '''FRIENDLY''' || Positively identified as friendly || Not cleared to engage
|-
| '''FURBALL''' || Friendly and non-friendly aircraft within 5 nm || Employment not authorized until resolved
|}

A BOGEY, BANDIT, OUTLAW, or SPADES classification does not authorize engagement. HOSTILE is the only declaration that authorizes weapons employment IAW ROE.

== 02 / Important Concepts ==

=== Communication Cadence by Phase ===
Communication priority shifts between the controller and fighters depending on the phase of the intercept.

{| class="wikitable" style="width:100%;"
|-
! Phase !! Priority Communicators
|-
| Pre-COMMIT / Marshal || 1. Controller · 2. Fighters
|-
| Post-COMMIT / Push || 1. Controller · 2. Fighter
|-
| Targeting / Weapons Employment || 1. Fighters · 2. Controller
|-
| Merge || 1. Engaged Fighter · 2. Supporting Fighters · 3. Controller
|-
| Post-Merge || 1. Fighter Clearing Merge · 2. Supporting Fighters · 3. Controller
|}

=== TAC Range ===
Called at 60 nm (default) by the first asset to recognize the separation. Signals all players to prepare for targeting. Pre-commit SA building continues until this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Fighter || {CS} {Group Label} TAC RANGE
|}

=== Airspace Sanitization ===
A Section consists of two aircraft, each equipped with its own radar. Regardless of the number of bars or maximum azimuth a single radar supports, no single system can cover the entire sky. To compensate, both radars are stacked and assigned to different portions of the airspace — each portion is called an '''Area of Responsibility (AOR)'''. This technique, known as '''Radar Mating''', vastly increases the total volume scanned and ensures that no unknown contacts are operating in the area beyond already-tracked groups. The exact parameters depend on the aircraft type: the US Navy recommends RWS, 140°, 6 bars, end scale 80 nm, with radars mated at 25 nm: placing the flight lead between 40,000 and 15,000 ft, and the wingman from ground level to 25,000 ft.

The process of actively scanning assigned AORs to confirm no unknown contacts are present is called '''Sanitisation'''.

Because both Radar Mating parameters and Sanitisation responsibilities directly affect how an engagement develops, all of this must be '''pre-briefed''' and set as a '''contract''' before the mission. Time pressure may not always permit a thorough sanitisation pass, and how to handle that contingency should likewise be agreed upon in the brief.

=== Targeting ===
The flight assigns GROUP responsibility and confirms classification.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} DECLARE {Group Label or Bullseye Position}
|-
| Controller || {Group Label} DECLARED {HOSTILE / BOGEY / FRIENDLY / UNABLE / FURBALL}
|-
| FL || {CS} TARGET {Group Label} {Tactic}
|-
| colspan="2" style="text-align:center;" | ''Once group appears on radar''
|-
| FL || {CS} TARGETED {Group Label} BULLSEYE {Bearing/Range}
|-
| Controller || ''No response if information correlates. Comparative response if correction is required.''
|}

== 03 / Common Calls ==

=== DECLARE ===
Inquiry as to the identity of a specified GROUP. Full positional data in BULLSEYE format must accompany all responses.
MIKE, EAGLE 11, DECLARE NORTH GROUP.
EAGLE 11, NORTH GROUP BULLSEYE 2-7-3/27, TWENTY-TWO THOUSAND, TRACK EAST, BOGEY SPADES.

=== BOGEY DOPE ===
Request for BRAA information on the indicated GROUP or the closest GROUP if not specified. Does not imply fighter targeting.
MIKE, EAGLE 11, BOGEY DOPE NORTH GROUP.
EAGLE 11, NORTH GROUP BRAA 2-1-0/28, THIRTY-EIGHT THOUSAND, HOT, HOSTILE.

=== NAILS ===
Fighter's radar warning receiver is detecting an airborne interceptor radar in search mode. Called with bearing or cardinal direction.
EAGLE 1, NAILS 2-7-0.

=== SPIKED ===
Fighter is being actively tracked by an airborne radar. Called with bearing or cardinal direction. Controller correlates to a GROUP within ±30 degrees and responds with range, altitude, aspect, declaration, and GROUP name.
EAGLE 1, SPIKED 2-7-0.
EAGLE 1, SPIKE RANGE 17, THIRTY THOUSAND, HOSTILE EAST GROUP, TWO CONTACTS.

=== THREAT Call ===
If a fighter will pierce THREAT range to an untargeted GROUP, the controller makes a THREAT call in BRAA format no later than THREAT range.
HEAT 31, ADDITIONAL GROUP THREAT, BRAA 1-2-5/35, THIRTY-FIVE THOUSAND, HOT, HOSTILE.

If the THREAT is within 5 nm of friendly fighters:
BOLT 1, THREAT NORTH THREE, TEN THOUSAND, TRACK SOUTH, HOSTILE.

=== FADED and VANISHED ===
'''FADED''' — a previously tracked GROUP not updated by sensors for 30 seconds. The controller reports the GROUP as FADED with last known BULLSEYE position. Fighters maintain MONITOR responsibility if they can maintain correlation. FADED is not used for friendly aircraft — controllers use NEGATIVE CONTACT for friendlies not held on sensors.

'''VANISHED''' — a special case of FADED used when the GROUP is not in a known blind zone and is correlated to a friendly shot that meets parameters for successful termination.

=== Unexpected Contacts ===
Three distinct call types exist for contacts not part of the established picture:

{| class="wikitable" style="width:100%;"
|-
! Call !! Criteria !! Format
|-
| '''ADDITIONAL GROUP''' || Newly detected outside targeting range, or does not fit traditional label || BULLSEYE
|-
| '''POP-UP GROUP''' || Previously undetected; appears inside targeting range but outside THREAT range || BULLSEYE
|-
| '''THREAT GROUP''' || Undetected or unreported GROUP meeting briefed THREAT criteria || BRAA to the closest aircraft
|}

DARKSTAR, POP-UP GROUP BULLSEYE 2-7-0/15, FIVE THOUSAND, TRACK WEST, BOGEY SPADES.
RAMBO 2, THREAT GROUP BRAA 2-7-0/13, ONE THOUSAND, HOT, HOSTILE.

== 04 / Engagement ==
The engagement loop is the core sequence executed by all fighter flights once committed and targeting is established. It repeats until the GROUP is splashed, leaves the area, or the flight resets.

=== MELD ===
The flight lead directs all flight members to shift their radars from wide sanitization to focused SA on the assigned GROUP. This transition narrows the radar from maximum azimuth and altitude coverage to a tighter volume centered on the target. Sanitization of the surrounding airspace ceases until DROPPING is called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''All flight members shift radar from sanitization to the assigned GROUP''
|}

=== SORT ===
The flight lead assigns individual contacts within the GROUP to specific flight members. Each member acknowledges with SORTED when they have confirmed their assigned contact on radar and are prepared to engage it. If a member cannot confirm their assigned contact, SORTED is withheld until resolution.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || ''(intraflight) FLIGHT SORT {Criteria}''
|-
| #2 || ''(intraflight) #2 SORTED''
|-
| #3 || ''(intraflight) #3 SORTED''
|-
| #4 || ''(intraflight) #4 SORTED''
|}

=== JUDY ===
Called by the flight lead when the flight no longer requires controller guidance to prosecute the intercept. From this point, the controller minimizes transmissions and provides situational awareness information only. JUDY is not always called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Provides SA and THREAT calls only.''
|}

=== ENGAGE ===
Directive call from the flight lead to a specific wingman to employ weapons. The flight lead may also direct simultaneous employment by multiple members.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} ENGAGE
|-
| Wingman || {CS}
|}

=== Weapon Employment ===
The firing aircraft calls the shot on TACC2 NET immediately after employment. The call includes shot type, GROUP label, contact description, BULLSEYE position, and altitude. The controller acknowledges with COPY SHOT.

If a fighter determines a GROUP HOSTILE and ROE has been met, the fighter may employ autonomously and include HOSTILE in the shot transmission.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft || {TACC2-CS} {CS} FOX THREE {Group Label} {Contact Description} BULLSEYE {Bearing/Range} {Altitude}
|-
| TACC2 || {TACC2-CS} COPY SHOT
|-
| colspan="2" style="text-align:center;" | ''Autonomous HOSTILE employment''
|-
| Firing Aircraft || {Controller-CS} {CS} FOX THREE {Group Label} BULLSEYE {Bearing/Range} {Altitude} HOSTILE
|-
| TACC2 || {TACC2-CS} COPY SHOT
|}

Multiple shots in one transmission are acceptable:
SHADOW12 FOX THREE NORTH GROUP LEAD CONTACT BULLSEYE 2-7-0/20 TWENTY THOUSAND; SHADOW11 FOX THREE NORTH GROUP TRAIL CONTACT.

=== OUT / DEFENDING ===
Following weapon employment the flight turns away from the threat. OUT is a planned maneuver executed at a prebriefed range. DEFENDING indicates a reactive maneuver against an incoming weapon and is called with the cardinal direction of the defensive turn.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction}
|-
| colspan="2" style="text-align:center;" | ''or, if reacting to an incoming weapon''
|-
| Aircraft || {CS} DEFENDING {Direction}
|}

=== DROPPING ===
May be called in conjunction with OUT. Signals the controller that the flight has ceased monitoring the GROUP and is returning to sanitization radar settings. Monitoring responsibility transfers back to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction} DROPPING {Group Label}
|-
| colspan="2" style="text-align:center;" | ''Controller resumes monitoring of the dropped GROUP''
|-
| Controller || ''Resumes monitoring.''
|}

=== Assessment ===
The flight assesses weapon effects from sensor data or controller reports. Three outcomes are possible:

{| class="wikitable" style="width:100%;"
|-
! Outcome !! Action
|-
| GROUP splashed || Call SPLASH
|-
| GROUP remains a factor, follow-up shot required || Turn IN, return to MELD
|-
| GROUP has left the area or is no longer a factor || Proceed with Tasking
|}

=== IN (Follow-up Engagement) ===
If the GROUP remains a factor and the tactic permits a follow-up shot, the flight turns back toward the GROUP. The IN call triggers a new cycle beginning at MELD.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IN {Direction}
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''Re-sort as required, then return to ENGAGE''
|}

=== SPLASH ===
Called when weapon effects confirm the GROUP or contact is destroyed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft or Controller || {CS} SPLASH {Group Label or Contact Description}
|}

----

== 05 / Defensive Counter Air (DCA) ==
DCA is the use of fighter aircraft to defend a ground asset or airspace against hostile air threats. It uses prebriefed lanes and defined ranges.

=== DCA Range Structure ===
All ranges are prebriefed per sortie. The following are the standard range lines used in DCA:

{| class="wikitable" style="width:100%;"
|-
! Range Line !! Definition
|-
| '''Mission Fail Line''' || The line the enemy must not cross for the mission to succeed. Defines the maximum depth of the defensive problem.
|-
| '''Commit Line (CL)''' || The line at which a bogey is declared HOSTILE IAW theater ROE and the flight is authorized to commit. Prebriefed for all DCA sorties.
|-
| '''Targeting Range''' || The prebriefed distance at which all contacts must be intercepted. A GROUP inside this range with no assigned fighter is UNTARGETED. Prebriefed per sortie.
|-
| '''TAC Range''' || Default 60 nm from the closest fighter to the closest GROUP. Signals all players to prepare for targeting.
|-
| '''Threat Range''' || The prebriefed range at which an untargeted GROUP meeting THREAT criteria triggers a THREAT call. Prebriefed per sortie.
|}

=== COMMIT Authority ===
COMMIT authority is derived from the combatant commander and delegated through the chain of command. Any of the following may hold or recommend COMMIT authority depending on what is delegated:

{| class="wikitable" style="width:100%;"
|-
! Role !! Abbreviation !! Authority
|-
| Flight Lead || FL || Usually holds COMMIT authority unless delegated
|-
| Team Lead || TL || May hold COMMIT authority if delegated
|-
| Mission Commander || MC || May hold COMMIT authority if delegated
|-
| TACC2 || — || May hold COMMIT authority if delegated
|}

If only the MC, TL, or FL holds COMMIT authority, the controller may only recommend COMMIT. If the controller holds COMMIT authority, the MC and TL may only recommend.

=== DCA Flow ===

==== Lane Handover ====
When an outgoing flight is relieved on station by an incoming flight, a positive lane handover is required before the outgoing flight departs.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Off-going Lane Commander || {CS} MOVE FORWARD
|-
| On-coming Lane Commander || {CS}
|-
| colspan="2" style="text-align:center;" | ''On-coming aircraft may enter the lane. Lane commander authority has not yet transferred.''
|-
| Off-going Lane Commander || {CS} YOU HAVE THE LANE
|-
| On-coming Lane Commander || {CS} HAS THE LANE
|}

The off-going flight passes critical mission information to the controller before departing. The controller passes big-picture information to the on-coming flight before pushing them to the tactical frequency.

==== Pre-Commit ====
The flight arrives at its prebriefed CAP position with FENCE IN complete and radars in sanitization configuration. The controller holds picture responsibility.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} PICTURE
|-
| Controller || {CS} {Nr of Groups} {Group Label} BULLSEYE {Bearing/Range} {Altitude} TRACK {Direction} {Declaration} {Nr of Contacts}
|}

The flight evaluates commit criteria continuously. Pictures are requested as needed to maintain SA.

==== Commit ====

===== FIGHTER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} Recommend {CS} COMMIT
|-
| FL || {CS} COMMIT
|}

===== CONTROLLER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} Recommend Commit
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} {CS} COMMIT
|-
|FL
|{CS}
|}

After COMMIT, fighters hold radio priority.

=== Engagement Loop ===
The flight executes the standard engagement loop as defined above The loop repeats until the GROUP is splashed, leaves the lane, or:

Once the Engagement is Complete the flight '''RESETS''' back to the briefed Position

==== RESET ====
Directs the flight to return to its prebriefed position or area of operations. RESET implies DROPPING and returns all targeting responsibility to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} RESET
|-
| colspan="2" style="text-align:center;" | ''Flight returns to prebriefed CAP position. Controller resumes full picture responsibility''
|}

----

== 06 / Offensive Counter Air (OCA) ==
OCA is the use of fighter aircraft to suppress, destroy, or neutralize enemy air assets before they can threaten friendly forces. Unlike DCA, OCA is not lane-based and does not require a commit line. The flight pushes into the threat environment rather than waiting for the threat to approach.

=== OCA Range Structure ===
The same range lines apply as in DCA — Threat Range, Targeting Range, and TAC Range — but all are prebriefed based on the specific mission geometry and threat environment. There is no commit line or mission fail line in OCA.

=== OCA Flow ===
OCA does not have a lane handover or a commit phase. The flight checks in, receives the picture, establishes targeting, and executes the engagement loop.

==== FULL COMMUNICATIONS EXAMPLE ====
In this Scenario, SHADOW11 four-ship F16C on OCA. TACC2 Agency CS THUMPER executing Positive Control. The Example begins after the Handover. Check In was done on the previous Frequency. TAC RANGE 60, THREAT RANGE 30
THUMPER SHADOW11 PICTURE

THUMPER PICTURE TEN GROUPS GROUP BULLSEYE 0-2-0/25, TWENTY-SEVEN THOUSAND, THOUSAND, TRACK EAST, HOSTILE, HEAVY, THREE CONTACTS. GROUP BULLSEYE 2-7-0/25, FIFTEEN THOUSAND, TRACK WEST, HOSTILE. GROUP BULLSEYE 2-9-0/35, TEN THOUSAND, TRACK WEST, HOSTILE.

SHADOW11 TARGETED GROUP BULLSEYE 0-2-0/25

SHADOW11 GROUP BULLSEYE 0-2-0/25 TAC RANGE

SHADOW11 SKATE, MELD

SHADOW11 SORTED

SHADOW11 FOX3 BULLSEYE 0-2-0/25

THUMPER COPY SHOT

SHADOW11 OUT SOUTH DROPPING

THUMPER

THUMPER SHADOW11 BOGEYDOPE

SHADOW11 EAST GROUP BRAA 2-1-0/28, FIFTEEN-THOUSAND, COLD, HOSTILE

SHADOW11 IN, MELD, SORTED

THUMPER SHADOW11 SPLASH EAST GROUP

THUMPER
In the Following Example additional Adversarys Pop Up within Threat Range of SHADOW11
SHADOW11 THREAT GROUP, BRAA 1-2-5/28, FIVE-THOUSAND, HOT, HOSTILE, 2 CONTACTS

SHADOW11 TARGETED, SORTED LEAD, FOX 3 LEADER, FOX3 TRAILER, BULLSEYE 0-5-0/45, FIVE-THOUSAND

THUMPER COPY SHOT

SHADOW11 DEFENDING SOUTH, DROPPING

THUMPER

SHADOW11 THUMPER THREAT GROUP, BRAA 0-6-0/15, TWO-THOUSAND, COLD, HOSTILE

SHADOW11

SHADOW11 IN

SHADOW11 FOX3 BULLSEYE 0-6-0/15, TWO-THOUSAND

THUMPER COPY SHOT

SHADOW11 THUMPER THREAT GROUP VANISHED
----

== 07 / QRA ==

== 08 / Intercept (VID) ==
A Visual Identification (VID) intercept is conducted when a contact cannot be declared HOSTILE or FRIENDLY by electronic means alone, and visual confirmation of aircraft type, markings, or behavior is required before engagement authority can be granted or withheld.

VID intercepts follow a structured sequence: the controller guides the fighter to a position from which a visual identification pass can be made, then the fighter reports the result and awaits further direction.

=== Intercept Flow ===

==== Commit ====
The controller or flight lead initiates the intercept against the unidentified contact.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} COMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration} {Nr of Contacts}
|-
| FL || {CS} COMMIT
|}

==== Guidance ====
The controller provides vectors to position the fighter for a VID pass. This is the only phase where the controller takes positive close control of the intercept geometry. BRAA format is used throughout.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} BRAA {Bearing/Range} {Altitude} {Aspect} {Declaration}
|-
| FL || {CS}
|-
| colspan="2" style="text-align:center;" | ''Controller continues to provide updated vectors until fighter calls JUDY''
|}

==== JUDY ====
The fighter calls JUDY when radar contact is established and no further controller guidance is required. The controller minimizes transmissions from this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Continues to provide SA information only.''
|}

==== Tally ====
The fighter calls TALLY when visual contact is established with the target.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} TALLY {Position}
|}

==== Identification ====
The fighter conducts the VID pass and reports the result to the controller. The report includes aircraft type, markings, and behavior observed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IDENTIFIED {Aircraft Type} {Markings / Behavior}
|-
| Controller || {CS} {Further Instructions / Declaration Update}
|}

If the contact is identified as HOSTILE following the VID pass, the controller issues the updated declaration and the flight may proceed to engagement IAW ROE. If the contact is FRIENDLY or NEUTRAL, the flight disengages and returns to its prebriefed position.

----

== 09 / Merge ==
A merge occurs when friendly and target aircraft arrive in the visual arena, within 3–5 nm of each other. At the merge, radar resolution becomes limiting and the engagement transitions from BVR to Within Visual Range (WVR).

=== Communication Priority at the Merge ===
The engaged fighter holds radio priority. The supporting fighter and controller subordinate their transmissions accordingly.

{| class="wikitable" style="width:100%;"
|-
! Role !! Responsibility
|-
| '''Engaged Fighter''' || Calls the merge, manages the engagement, and calls employment and results. Holds radio priority.
|-
| '''Supporting Fighter''' || Provides SA to the engaged fighter. Calls PRESS when directed and mutual support is maintained. Subordinates transmissions to the engaged fighter.
|-
| '''Controller''' || Minimizes transmissions. Provides THREAT calls, SA updates, and responds to fighter requests only.
|}

=== Merge Flow ===

==== MERGED ====
The controller calls MERGED when radar tracks come together within 3–5 nm, or the engaged fighter calls it when visual contact is made.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Engaged Fighter || {CS} MERGED {Group Label}
|}

==== IFF Calls ====
At the merge, positive visual identification of friend or foe is critical before employment. Standard IFF calls apply:

{| class="wikitable" style="width:100%;"
|-
! Term !! Meaning
|-
| '''TALLY''' || Visual contact established on the target or bandit
|-
| '''NO JOY''' || No visual contact with the target or bandit
|-
| '''VISUAL''' || Visual contact established on a friendly aircraft
|-
| '''BLIND''' || No visual contact with a friendly aircraft
|}

==== PRESS ====
The supporting fighter calls PRESS to indicate the requested action is approved and mutual support will be maintained. PRESS assumes VISUAL on the engaged fighter.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || ''(intraflight) {CS} PRESS''
|-
| Supporting Fighter || ''(intraflight) PRESS''
|}

==== Employment ====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || {Controller-CS} {CS} FOX TWO {Target Description}
|-
| Controller || COPY SHOT
|}

Gun employment is called as GUNS with target description.

==== SPLASH ====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || {Controller-CS} {CS} SPLASH {Group Label or Contact Description}
|-
| Controller || {CS} COPY SPLASH
|}

Following SPLASH the flight disengages, calls RESET, and returns to its prebriefed position unless directed otherwise.

MTTP/A2A

2026-05-23T12:31:49Z

Niknam3: /* 08 / Air-to-Air Combat */

== 01 / Overview ==
Air combat is primarily carried out by CAP aircraft. The two main mission types are '''DCA''' (Defensive Counter Air) and '''OCA''' (Offensive Counter Air).

=== Groups and Contacts ===
A '''GROUP''' is any number of air contacts within 3 nm in azimuth and range of each other. A '''CONTACT''' is an individual radar return within a GROUP. Single contact is the assumed strength for all GROUPs unless otherwise specified. A GROUP with three or more contacts is called '''HEAVY'''.

The '''PICTURE''' establishes a common tactical air image and describes the spatial relationship of GROUPs. It is always communicated in BULLSEYE format unless briefed otherwise. Only the Three GROUPs with highest Priority are Conveyed

=== Contact Declaration ===
Before a fighter can engage, a contact must be declared. Declaration is performed by the controller in response to a DECLARE request.

{| class="wikitable" style="width:100%;"
|-
! Declaration !! Meaning !! Engagement Authority
|-
| '''BOGEY''' || Identity unknown || Not cleared to engage
|-
| '''OUTLAW''' || Originates from known or suspected hostile area || Not cleared to engage; escalation criteria apply
|-
| '''SPADES''' || No valid IFF response on interrogation || Not cleared to engage; escalation criteria apply
|-
| '''BANDIT''' || Positively identified as enemy IAW theater ID criteria || Not cleared to engage; does not imply authority to fire
|-
| '''HOSTILE''' || Confirmed enemy; clearance to fire authorized IAW ROE || Cleared to engage
|-
| '''NEUTRAL''' || Positively identified as neutral || Not cleared to engage
|-
| '''FRIENDLY''' || Positively identified as friendly || Not cleared to engage
|-
| '''FURBALL''' || Friendly and non-friendly aircraft within 5 nm || Employment not authorized until resolved
|}

A BOGEY, BANDIT, OUTLAW, or SPADES classification does not authorize engagement. HOSTILE is the only declaration that authorizes weapons employment IAW ROE.

== 02 / Important Concepts ==

=== Communication Cadence by Phase ===
Communication priority shifts between the controller and fighters depending on the phase of the intercept.

{| class="wikitable" style="width:100%;"
|-
! Phase !! Priority Communicators
|-
| Pre-COMMIT / Marshal || 1. Controller · 2. Fighters
|-
| Post-COMMIT / Push || 1. Controller · 2. Fighter
|-
| Targeting / Weapons Employment || 1. Fighters · 2. Controller
|-
| Merge || 1. Engaged Fighter · 2. Supporting Fighters · 3. Controller
|-
| Post-Merge || 1. Fighter Clearing Merge · 2. Supporting Fighters · 3. Controller
|}

=== TAC Range ===
Called at 60 nm (default) by the first asset to recognize the separation. Signals all players to prepare for targeting. Pre-commit SA building continues until this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Fighter || {CS} {Group Label} TAC RANGE
|}

=== Airspace Sanitization ===
A Section consists of two aircraft, each equipped with its own radar. Regardless of the number of bars or maximum azimuth a single radar supports, no single system can cover the entire sky. To compensate, both radars are stacked and assigned to different portions of the airspace — each portion is called an '''Area of Responsibility (AOR)'''. This technique, known as '''Radar Mating''', vastly increases the total volume scanned and ensures that no unknown contacts are operating in the area beyond already-tracked groups. The exact parameters depend on the aircraft type: the US Navy recommends RWS, 140°, 6 bars, end scale 80 nm, with radars mated at 25 nm: placing the flight lead between 40,000 and 15,000 ft, and the wingman from ground level to 25,000 ft.

The process of actively scanning assigned AORs to confirm no unknown contacts are present is called '''Sanitisation'''.

Because both Radar Mating parameters and Sanitisation responsibilities directly affect how an engagement develops, all of this must be '''pre-briefed''' and set as a '''contract''' before the mission. Time pressure may not always permit a thorough sanitisation pass, and how to handle that contingency should likewise be agreed upon in the brief.

=== Targeting ===
The flight assigns GROUP responsibility and confirms classification.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} DECLARE {Group Label or Bullseye Position}
|-
| Controller || {Group Label} DECLARED {HOSTILE / BOGEY / FRIENDLY / UNABLE / FURBALL}
|-
| FL || {CS} TARGET {Group Label} {Tactic}
|-
| colspan="2" style="text-align:center;" | ''Once group appears on radar''
|-
| FL || {CS} TARGETED {Group Label} BULLSEYE {Bearing/Range}
|-
| Controller || ''No response if information correlates. Comparative response if correction is required.''
|}

== 03 / Common Calls ==

=== DECLARE ===
Inquiry as to the identity of a specified GROUP. Full positional data in BULLSEYE format must accompany all responses.
MIKE, EAGLE 11, DECLARE NORTH GROUP.
EAGLE 11, NORTH GROUP BULLSEYE 2-7-3/27, TWENTY-TWO THOUSAND, TRACK EAST, BOGEY SPADES.

=== BOGEY DOPE ===
Request for BRAA information on the indicated GROUP or the closest GROUP if not specified. Does not imply fighter targeting.
MIKE, EAGLE 11, BOGEY DOPE NORTH GROUP.
EAGLE 11, NORTH GROUP BRAA 2-1-0/28, THIRTY-EIGHT THOUSAND, HOT, HOSTILE.

=== NAILS ===
Fighter's radar warning receiver is detecting an airborne interceptor radar in search mode. Called with bearing or cardinal direction.
EAGLE 1, NAILS 2-7-0.

=== SPIKED ===
Fighter is being actively tracked by an airborne radar. Called with bearing or cardinal direction. Controller correlates to a GROUP within ±30 degrees and responds with range, altitude, aspect, declaration, and GROUP name.
EAGLE 1, SPIKED 2-7-0.
EAGLE 1, SPIKE RANGE 17, THIRTY THOUSAND, HOSTILE EAST GROUP, TWO CONTACTS.

=== THREAT Call ===
If a fighter will pierce THREAT range to an untargeted GROUP, the controller makes a THREAT call in BRAA format no later than THREAT range.
HEAT 31, ADDITIONAL GROUP THREAT, BRAA 1-2-5/35, THIRTY-FIVE THOUSAND, HOT, HOSTILE.

If the THREAT is within 5 nm of friendly fighters:
BOLT 1, THREAT NORTH THREE, TEN THOUSAND, TRACK SOUTH, HOSTILE.

=== FADED and VANISHED ===
'''FADED''' — a previously tracked GROUP not updated by sensors for 30 seconds. The controller reports the GROUP as FADED with last known BULLSEYE position. Fighters maintain MONITOR responsibility if they can maintain correlation. FADED is not used for friendly aircraft — controllers use NEGATIVE CONTACT for friendlies not held on sensors.

'''VANISHED''' — a special case of FADED used when the GROUP is not in a known blind zone and is correlated to a friendly shot that meets parameters for successful termination.

=== Unexpected Contacts ===
Three distinct call types exist for contacts not part of the established picture:

{| class="wikitable" style="width:100%;"
|-
! Call !! Criteria !! Format
|-
| '''ADDITIONAL GROUP''' || Newly detected outside targeting range, or does not fit traditional label || BULLSEYE
|-
| '''POP-UP GROUP''' || Previously undetected; appears inside targeting range but outside THREAT range || BULLSEYE
|-
| '''THREAT GROUP''' || Undetected or unreported GROUP meeting briefed THREAT criteria || BRAA to the closest aircraft
|}

DARKSTAR, POP-UP GROUP BULLSEYE 2-7-0/15, FIVE THOUSAND, TRACK WEST, BOGEY SPADES.
RAMBO 2, THREAT GROUP BRAA 2-7-0/13, ONE THOUSAND, HOT, HOSTILE.

== 04 / Engagement ==
The engagement loop is the core sequence executed by all fighter flights once committed and targeting is established. It repeats until the GROUP is splashed, leaves the area, or the flight resets.

=== MELD ===
The flight lead directs all flight members to shift their radars from wide sanitization to focused SA on the assigned GROUP. This transition narrows the radar from maximum azimuth and altitude coverage to a tighter volume centered on the target. Sanitization of the surrounding airspace ceases until DROPPING is called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''All flight members shift radar from sanitization to the assigned GROUP''
|}

=== SORT ===
The flight lead assigns individual contacts within the GROUP to specific flight members. Each member acknowledges with SORTED when they have confirmed their assigned contact on radar and are prepared to engage it. If a member cannot confirm their assigned contact, SORTED is withheld until resolution.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || ''(intraflight) FLIGHT SORT {Criteria}''
|-
| #2 || ''(intraflight) #2 SORTED''
|-
| #3 || ''(intraflight) #3 SORTED''
|-
| #4 || ''(intraflight) #4 SORTED''
|}

=== JUDY ===
Called by the flight lead when the flight no longer requires controller guidance to prosecute the intercept. From this point, the controller minimizes transmissions and provides situational awareness information only. JUDY is not always called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Provides SA and THREAT calls only.''
|}

=== ENGAGE ===
Directive call from the flight lead to a specific wingman to employ weapons. The flight lead may also direct simultaneous employment by multiple members.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} ENGAGE
|-
| Wingman || {CS}
|}

=== Weapon Employment ===
The firing aircraft calls the shot on TACC2 NET immediately after employment. The call includes shot type, GROUP label, contact description, BULLSEYE position, and altitude. The controller acknowledges with COPY SHOT.

If a fighter determines a GROUP HOSTILE and ROE has been met, the fighter may employ autonomously and include HOSTILE in the shot transmission.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft || {TACC2-CS} {CS} FOX THREE {Group Label} {Contact Description} BULLSEYE {Bearing/Range} {Altitude}
|-
| TACC2 || {TACC2-CS} COPY SHOT
|-
| colspan="2" style="text-align:center;" | ''Autonomous HOSTILE employment''
|-
| Firing Aircraft || {Controller-CS} {CS} FOX THREE {Group Label} BULLSEYE {Bearing/Range} {Altitude} HOSTILE
|-
| TACC2 || {TACC2-CS} COPY SHOT
|}

Multiple shots in one transmission are acceptable:
SHADOW12 FOX THREE NORTH GROUP LEAD CONTACT BULLSEYE 2-7-0/20 TWENTY THOUSAND; SHADOW11 FOX THREE NORTH GROUP TRAIL CONTACT.

=== OUT / DEFENDING ===
Following weapon employment the flight turns away from the threat. OUT is a planned maneuver executed at a prebriefed range. DEFENDING indicates a reactive maneuver against an incoming weapon and is called with the cardinal direction of the defensive turn.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction}
|-
| colspan="2" style="text-align:center;" | ''or, if reacting to an incoming weapon''
|-
| Aircraft || {CS} DEFENDING {Direction}
|}

=== DROPPING ===
May be called in conjunction with OUT. Signals the controller that the flight has ceased monitoring the GROUP and is returning to sanitization radar settings. Monitoring responsibility transfers back to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction} DROPPING {Group Label}
|-
| colspan="2" style="text-align:center;" | ''Controller resumes monitoring of the dropped GROUP''
|-
| Controller || ''Resumes monitoring.''
|}

=== Assessment ===
The flight assesses weapon effects from sensor data or controller reports. Three outcomes are possible:

{| class="wikitable" style="width:100%;"
|-
! Outcome !! Action
|-
| GROUP splashed || Call SPLASH
|-
| GROUP remains a factor, follow-up shot required || Turn IN, return to MELD
|-
| GROUP has left the area or is no longer a factor || Proceed with Tasking
|}

=== IN (Follow-up Engagement) ===
If the GROUP remains a factor and the tactic permits a follow-up shot, the flight turns back toward the GROUP. The IN call triggers a new cycle beginning at MELD.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IN {Direction}
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''Re-sort as required, then return to ENGAGE''
|}

=== SPLASH ===
Called when weapon effects confirm the GROUP or contact is destroyed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft or Controller || {CS} SPLASH {Group Label or Contact Description}
|}

----

== 05 / Defensive Counter Air (DCA) ==
DCA is the use of fighter aircraft to defend a ground asset or airspace against hostile air threats. It uses prebriefed lanes and defined ranges.

=== DCA Range Structure ===
All ranges are prebriefed per sortie. The following are the standard range lines used in DCA:

{| class="wikitable" style="width:100%;"
|-
! Range Line !! Definition
|-
| '''Mission Fail Line''' || The line the enemy must not cross for the mission to succeed. Defines the maximum depth of the defensive problem.
|-
| '''Commit Line (CL)''' || The line at which a bogey is declared HOSTILE IAW theater ROE and the flight is authorized to commit. Prebriefed for all DCA sorties.
|-
| '''Targeting Range''' || The prebriefed distance at which all contacts must be intercepted. A GROUP inside this range with no assigned fighter is UNTARGETED. Prebriefed per sortie.
|-
| '''TAC Range''' || Default 60 nm from the closest fighter to the closest GROUP. Signals all players to prepare for targeting.
|-
| '''Threat Range''' || The prebriefed range at which an untargeted GROUP meeting THREAT criteria triggers a THREAT call. Prebriefed per sortie.
|}

=== COMMIT Authority ===
COMMIT authority is derived from the combatant commander and delegated through the chain of command. Any of the following may hold or recommend COMMIT authority depending on what is delegated:

{| class="wikitable" style="width:100%;"
|-
! Role !! Abbreviation !! Authority
|-
| Flight Lead || FL || Usually holds COMMIT authority unless delegated
|-
| Team Lead || TL || May hold COMMIT authority if delegated
|-
| Mission Commander || MC || May hold COMMIT authority if delegated
|-
| TACC2 || — || May hold COMMIT authority if delegated
|}

If only the MC, TL, or FL holds COMMIT authority, the controller may only recommend COMMIT. If the controller holds COMMIT authority, the MC and TL may only recommend.

=== DCA Flow ===

==== Lane Handover ====
When an outgoing flight is relieved on station by an incoming flight, a positive lane handover is required before the outgoing flight departs.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Off-going Lane Commander || {CS} MOVE FORWARD
|-
| On-coming Lane Commander || {CS}
|-
| colspan="2" style="text-align:center;" | ''On-coming aircraft may enter the lane. Lane commander authority has not yet transferred.''
|-
| Off-going Lane Commander || {CS} YOU HAVE THE LANE
|-
| On-coming Lane Commander || {CS} HAS THE LANE
|}

The off-going flight passes critical mission information to the controller before departing. The controller passes big-picture information to the on-coming flight before pushing them to the tactical frequency.

==== Pre-Commit ====
The flight arrives at its prebriefed CAP position with FENCE IN complete and radars in sanitization configuration. The controller holds picture responsibility.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} PICTURE
|-
| Controller || {CS} {Nr of Groups} {Group Label} BULLSEYE {Bearing/Range} {Altitude} TRACK {Direction} {Declaration} {Nr of Contacts}
|}

The flight evaluates commit criteria continuously. Pictures are requested as needed to maintain SA.

==== Commit ====

===== FIGHTER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} Recommend {CS} COMMIT
|-
| FL || {CS} COMMIT
|}

===== CONTROLLER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} Recommend Commit
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} {CS} COMMIT
|-
|FL
|{CS}
|}

After COMMIT, fighters hold radio priority.

=== Engagement Loop ===
The flight executes the standard engagement loop as defined above The loop repeats until the GROUP is splashed, leaves the lane, or:

Once the Engagement is Complete the flight '''RESETS''' back to the briefed Position

==== RESET ====
Directs the flight to return to its prebriefed position or area of operations. RESET implies DROPPING and returns all targeting responsibility to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} RESET
|-
| colspan="2" style="text-align:center;" | ''Flight returns to prebriefed CAP position. Controller resumes full picture responsibility''
|}

----

== 06 / Offensive Counter Air (OCA) ==
OCA is the use of fighter aircraft to suppress, destroy, or neutralize enemy air assets before they can threaten friendly forces. Unlike DCA, OCA is not lane-based and does not require a commit line. The flight pushes into the threat environment rather than waiting for the threat to approach.

=== OCA Range Structure ===
The same range lines apply as in DCA — Threat Range, Targeting Range, and TAC Range — but all are prebriefed based on the specific mission geometry and threat environment. There is no commit line or mission fail line in OCA.

=== OCA Flow ===
OCA does not have a lane handover or a commit phase. The flight checks in, receives the picture, establishes targeting, and executes the engagement loop.

==== FULL COMMUNICATIONS EXAMPLE ====
In this Scenario, SHADOW11 four-ship F16C on OCA. TACC2 Agency CS THUMPER executing Positive Control. The Example begins after the Handover. Check In was done on the previous Frequency.

----

== 07 / QRA ==

== 08 / Intercept (VID) ==
A Visual Identification (VID) intercept is conducted when a contact cannot be declared HOSTILE or FRIENDLY by electronic means alone, and visual confirmation of aircraft type, markings, or behavior is required before engagement authority can be granted or withheld.

VID intercepts follow a structured sequence: the controller guides the fighter to a position from which a visual identification pass can be made, then the fighter reports the result and awaits further direction.

=== Intercept Flow ===

==== Commit ====
The controller or flight lead initiates the intercept against the unidentified contact.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} COMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration} {Nr of Contacts}
|-
| FL || {CS} COMMIT
|}

==== Guidance ====
The controller provides vectors to position the fighter for a VID pass. This is the only phase where the controller takes positive close control of the intercept geometry. BRAA format is used throughout.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} BRAA {Bearing/Range} {Altitude} {Aspect} {Declaration}
|-
| FL || {CS}
|-
| colspan="2" style="text-align:center;" | ''Controller continues to provide updated vectors until fighter calls JUDY''
|}

==== JUDY ====
The fighter calls JUDY when radar contact is established and no further controller guidance is required. The controller minimizes transmissions from this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Continues to provide SA information only.''
|}

==== Tally ====
The fighter calls TALLY when visual contact is established with the target.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} TALLY {Position}
|}

==== Identification ====
The fighter conducts the VID pass and reports the result to the controller. The report includes aircraft type, markings, and behavior observed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IDENTIFIED {Aircraft Type} {Markings / Behavior}
|-
| Controller || {CS} {Further Instructions / Declaration Update}
|}

If the contact is identified as HOSTILE following the VID pass, the controller issues the updated declaration and the flight may proceed to engagement IAW ROE. If the contact is FRIENDLY or NEUTRAL, the flight disengages and returns to its prebriefed position.

----

== 09 / Merge ==
A merge occurs when friendly and target aircraft arrive in the visual arena, within 3–5 nm of each other. At the merge, radar resolution becomes limiting and the engagement transitions from BVR to Within Visual Range (WVR).

=== Communication Priority at the Merge ===
The engaged fighter holds radio priority. The supporting fighter and controller subordinate their transmissions accordingly.

{| class="wikitable" style="width:100%;"
|-
! Role !! Responsibility
|-
| '''Engaged Fighter''' || Calls the merge, manages the engagement, and calls employment and results. Holds radio priority.
|-
| '''Supporting Fighter''' || Provides SA to the engaged fighter. Calls PRESS when directed and mutual support is maintained. Subordinates transmissions to the engaged fighter.
|-
| '''Controller''' || Minimizes transmissions. Provides THREAT calls, SA updates, and responds to fighter requests only.
|}

=== Merge Flow ===

==== MERGED ====
The controller calls MERGED when radar tracks come together within 3–5 nm, or the engaged fighter calls it when visual contact is made.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Engaged Fighter || {CS} MERGED {Group Label}
|}

==== IFF Calls ====
At the merge, positive visual identification of friend or foe is critical before employment. Standard IFF calls apply:

{| class="wikitable" style="width:100%;"
|-
! Term !! Meaning
|-
| '''TALLY''' || Visual contact established on the target or bandit
|-
| '''NO JOY''' || No visual contact with the target or bandit
|-
| '''VISUAL''' || Visual contact established on a friendly aircraft
|-
| '''BLIND''' || No visual contact with a friendly aircraft
|}

==== PRESS ====
The supporting fighter calls PRESS to indicate the requested action is approved and mutual support will be maintained. PRESS assumes VISUAL on the engaged fighter.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || ''(intraflight) {CS} PRESS''
|-
| Supporting Fighter || ''(intraflight) PRESS''
|}

==== Employment ====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || {Controller-CS} {CS} FOX TWO {Target Description}
|-
| Controller || COPY SHOT
|}

Gun employment is called as GUNS with target description.

==== SPLASH ====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || {Controller-CS} {CS} SPLASH {Group Label or Contact Description}
|-
| Controller || {CS} COPY SPLASH
|}

Following SPLASH the flight disengages, calls RESET, and returns to its prebriefed position unless directed otherwise.

MTTP/A2S

2026-05-23T12:16:04Z

Niknam3: /* 9 / Air-to-Surface Communication */

== Fundamentals ==
Air-to-surface operations require a shared vocabulary for describing the progression from finding a target to destroying it. The Find, Fix, Track, Target, Engage, and Assess (F2T2EA) sequence governs the flow of a surface attack and the brevity that supports it.

=== Target Acquisition Brevity ===
The following brevity codes describe the state of sensor awareness on a surface target. They are used throughout the F2T2EA chain by both fighters and controllers.
{| class="wikitable" style="width:100%;"
!Brevity
!Definition
|-
|'''DIRT'''
|Radar warning receiver indication of a surface threat in search mode. The threat is radiating but has not yet established a track.
|-
|'''MUD'''
|Radar warning receiver indication of a surface threat in track mode. The threat has established a track on the aircraft.
|-
|'''SINGER'''
|Radar warning receiver indication of a SAM launch. The threat has fired.
|-
|'''SCAN'''
|Search the indicated sector and report any contacts.
|-
|'''WORK'''
|Directive call to conduct geolocation on a specific target or area.
|-
|'''INVESTIGATE'''
|Verify specified elements of ROE, positive identification (PID), and coordination of forces on the referenced target or track.
|-
|'''FIXED'''
|Target has been located and its position established. Followed by accuracy qualifier: LOW ACCURACY (inside 1 nm) or HIGH ACCURACY (inside 1,000 ft).
|-
|'''MONITOR'''
|Maintain sensor awareness on a specified GROUP or object. Implies tactically significant changes will be communicated.
|-
|'''TRACK'''
|Directive call assigning responsibility to an asset for maintaining sensor or visual observation of a defined object or area.
|-
|'''CAPTURED'''
|Object has been acquired and is being actively tracked.
|-
|'''COVER'''
|Directive call to be ready for reattack or re-engage if weapon effects are not achieved.
|-
|'''HOUNDDOG'''
|Aircraft is in a position to employ weapons. Used in response to COVER.
|}

=== Threat Reaction ===
When a SAM threat is detected, the aircraft communicates on the mission tactical NET to enable reactive SEAD and maintain the common tactical picture.
{| class="wikitable" style="width:100%;"
!Fidelity
!Format
!Example
|-
|'''Low'''
|Call sign · RWR indication · bearing · DEFENDING with cardinal direction · ownship BULLSEYE
|HORNET 1, SINGER ELEVEN, BEARING 3-6-0, DEFENDING WEST, BULLSEYE 3-4-5/30
|-
|'''High'''
|Call sign · RWR indication · threat BULLSEYE/location · DEFENDING with cardinal direction
|BOLT 1, SINGER ELEVEN, BULLSEYE 3-6-0/32, DEFENDING WEST
|}
High fidelity is defined as a 5 nm semi-major ellipse accuracy or better. Use high fidelity when available — it enables SEAD aircraft to engage with precision rather than azimuth alone.

=== TRESPASS ===
Called when an aircraft enters a non-previously-known SAM MEZ or when any non-SEAD aircraft crosses inside the maximum recommended intercept range of a known SAM. The calling entity directs an immediate SNAP heading away from the threat.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Controller or Aircraft
|{CS} SNAP {Heading} TRESPASS {Threat Type} BULLSEYE {Bearing/Range}
|}
RAMBO 2, SNAP 1-7-0, TRESPASS FIFTEEN BULLSEYE 3-2-0/32.

=== Game Plan ===
The flight lead issues the game plan before pushing to the target. All flight members acknowledge in sequence. The game plan assigns targeting responsibility, cover responsibility, and establishes the push time and TOT. The Following are two examples for possible Gameplans. Note that this part is highly flxible
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|MC
|HORNET, BOLT, PYTHON, STANDBY GAME PLAN
|-
|FLs
|"HORNET" "BOLT" "PYTHON"
|-
|MC
|“HORNET, TARGET AND SCAN ALPHA ALPHA 0-1, TWO VEHICLE
CONVOY BULLSEYE 2-7-5/69, MOVING SOUTH, BEST. PUSH AT

21:17 FROM RED OSCAR.”

“BOLT, COVER ALPHA ALPHA 0-1.”

“RAMBO ESCORT AND PYTHON SEAD PER BRIEF.”
|-
|FLs
|“HORNET.” “BOLT.” “PYTHON.”
|}
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|FL
|SHADOW11 #1 AND #2 TARGET {Target Description} · #3 AND #4 COVER {Target Description}
|-
|All Members
|#2 · #3 · #4
|}
Target and cover assignments may be communicated digitally via data link. Each player acknowledges GOOD DATA if received digitally.
----

== Strike ==
A strike is a planned attack against a pre-briefed fixed or moving ground target. Strike coordination occurs before and during the attack through a structured game plan, with clear assignment of targeting and cover responsibilities within the package.

=== Push ===
Once the game plan is acknowledged and the push time arrives, the attacking element calls PUSHING with the TOT. The cover element acknowledges readiness with HOUNDDOG, indicating they are in position to employ if the primary attack fails.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Attacking Aircraft
|{Controller-CS} {CS} CAPTURED {Target Description or Bullseye} PUSHING TOT {Time}
|-
|Cover Aircraft
|{CS} HOUNDDOG
|}

=== Weapon Away ===
The attacking aircraft calls weapon employment with time of flight. If the weapon requires continued support such as laser designation or scanning, this is added as a fill-in.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Attacking Aircraft
|{Controller-CS} {CS} ONE WEAPON AWAY {Target Description} {Time of Flight} SECONDS {LASING / SCANNING if applicable}
|}

=== Assessment ===
The attacking aircraft calls the result. Two outcomes are possible:
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
| colspan="2" style="text-align:center;" |''Desired weapon effects generated''
|-
|Attacking Aircraft
|{Controller-CS} {CS} SPLASH {Target Description} SUCCESSFUL
|-
| colspan="2" style="text-align:center;" |''Desired weapon effects not generated''
|-
|Attacking Aircraft
|{Controller-CS} {CS} SPLASH {Target Description} FUMBLE {CLEAN / HIT}
|}
FUMBLE CLEAN indicates no visible battle damage and no weapon impact noted. FUMBLE HIT indicates weapon impact was noted within a lethal distance but desired effects were not generated.

=== Reattack ===
If the primary attack results in FUMBLE, the cover element is directed to reattack.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|FL
|''(intraflight) {CS} COVER {Target Description or Bullseye} · {Cover CS} PUSH''
|-
|Cover Aircraft
|{Controller-CS} {CS} PUSHING TOT {Time}
|-
|Cover Aircraft
|{Controller-CS} {CS} ONE WEAPON AWAY {Time of Flight} SECONDS
|-
|Cover Aircraft
|{Controller-CS} {CS} SPLASH {Target Description} {SUCCESSFUL / FUMBLE}
|}

=== Egress ===
Following the attack, the flight egresses using one of three calls depending on the situation:
{| class="wikitable" style="width:100%;"
!Call
!Condition
!Phrase
|-
|'''MILLER TIME'''
|Last striker in the package has completed the attack
|{Controller-CS} {CS} MILLER TIME
|-
|'''BUGOUT'''
|Aircraft has completed its attack and has no intention to return
|{Controller-CS} {CS} BUGOUT {Direction}
|-
|'''OFF'''
|Aircraft has completed its attack and is repositioning or egressing within the area
|{Controller-CS} {CS} OFF {Direction}
|}

=== Full Strike Example ===
''(intraflight) SHADOW FLIGHT STANDBY GAME PLAN''
''(intraflight) #2 · #3 · #4''
''(intraflight) SHADOW FLIGHT, #1 AND #2 TARGET CONVOY BULLSEYE 0-3-0/15 · #3 AND #4 COVER''
''(intraflight) #2 · #3 · #4''

SHADOW11 CAPTURED BULLSEYE 0-3-0/15 PUSHING TOT 21:21:15
''(intraflight) SHADOW13 HOUNDDOG''

SHADOW12 ONE WEAPON AWAY CONVOY BULLSEYE 0-3-0/15 THIRTY SECONDS LASING

SHADOW11 SPLASH CONVOY BULLSEYE 0-3-0/15 FUMBLE HIT
''(intraflight) SHADOW11 COVER BULLSEYE 0-3-0/15 · SHADOW13 PUSH''

SHADOW13 PUSHING TOT 21:23:50
SHADOW13 ONE WEAPON AWAY FORTY SECONDS

SHADOW13 SPLASH CONVOY BULLSEYE 0-3-0/15 SUCCESSFUL
SHADOW11 MILLER TIME
----

=== CAS ===
''Content to be added.''
----

=== SEAD ===
Suppression of Enemy Air Defenses (SEAD) is the action taken to neutralize, destroy, or temporarily degrade surface-to-air missile systems and associated radar emitters. Its purpose is to allow other aircraft to operate within a threat environment that would otherwise deny or restrict their access.

==== The SEAD Game Plan ====
SEAD is not a reactive afterthought — it is a pre-planned, coordinated element of every strike package that operates in a contested environment. Before the mission, the SEAD lead establishes contracts with the rest of the package: who responds to which threat, in what priority order, with which weapon, and under what conditions.

The underlying logic of SEAD is straightforward. A SAM battery that is actively radiating is vulnerable to antiradiation missiles. A SAM battery that goes silent to avoid being targeted is temporarily suppressed and cannot engage aircraft. Either outcome — destruction or suppression — achieves the mission objective of protecting the strike package.

SEAD aircraft therefore have two primary tools:

* '''Hard kill''' — employment of an antiradiation missile (ARM) against a radiating threat. The ARM homes on the radar emission. If the radar goes silent the missile loses guidance, so the threat must be forced to stay radiating or be caught radiating.
* '''Soft kill''' — electromagnetic jamming (CANYON) that degrades the threat radar's ability to track or guide a missile without destroying the system.

The decision between hard and soft kill, and between SNIPER (range-known) and SLAPSHOT (range-unknown, immediate), is made based on the quality of targeting data available and the urgency of the situation.

==== Threat Reaction and SEAD Response Contracts ====
When a friendly aircraft calls DEFENDING, SEAD aircraft respond with one of the following:
{| class="wikitable" style="width:100%;"
!Response
!Definition (ATP 1-02.1)
!Meaning
|-
|'''HARM INBOUND'''
|[A/S] [EW] High-speed antiradiation missile already employed
|ARM is already in the air — the threat is being engaged
|-
|'''MAGNUM'''
|[A/S] [EW] Launch of FRIENDLY antiradiation missile
|ARM is being launched now in response to this call
|-
|'''ARIZONA'''
|[A/S] [EW] No antiradiation missile ordnance remaining
|SEAD aircraft is Winchester on ARMs
|}
These responses must be pre-briefed as contracts. Every aircraft in the package needs to know which SEAD asset covers which threat axis, what the response will be, and what to do if the SEAD asset is ARIZONA or unable to respond.

==== SNIPER and SLAPSHOT ====
Two directive calls are used to order ARM employment:

'''SNIPER''' — directive call to employ an antiradiation missile against a range-known threat. Used when targeting data is of sufficient quality to give a precise location.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|SEAD Lead
|{CS} SNIPER {Threat Type} BULLSEYE {Bearing/Range}
|-
|SEAD Aircraft
|{CS} MAGNUM {Threat Type} BULLSEYE {Bearing/Range}
|}
'''SLAPSHOT''' — directive call to immediately employ the best available antiradiation missile against a specified threat at the specified bearing. Range is unknown. Used when a threat is actively engaging friendly aircraft and there is no time to refine targeting data.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|SEAD Lead
|{CS} SLAPSHOT {Threat Type} BEARING {Bearing}
|-
|SEAD Aircraft
|{CS} HARM INBOUND
|}
The distinction matters: SNIPER is deliberate and precise, SLAPSHOT is immediate and azimuth-only. A SLAPSHOT ARM may not hit the radar if it goes silent, but it forces the threat to shut down or risk destruction — either outcome protects the package.

General/Tactical Communication Revision 1

2026-05-23T12:15:16Z

Niknam3: /* 08 / Air-to-Air Combat */

General/Tactical Communication Revision 1

2026-05-23T12:14:34Z

Niknam3:

MTTP/A2S

2026-05-23T12:14:25Z

Niknam3: Created page with "== 9 / Air-to-Surface Communication == === Fundamentals === Air-to-surface operations require a shared vocabulary for describing the progression from finding a target to destroying it. The Find, Fix, Track, Target, Engage, and Assess (F2T2EA) sequence governs the flow of a surface attack and the brevity that supports it. ==== Target Acquisition Brevity ==== The following brevity codes describe the state of sensor awareness on a surface target. They are used throughout..."

== 9 / Air-to-Surface Communication ==

=== Fundamentals ===
Air-to-surface operations require a shared vocabulary for describing the progression from finding a target to destroying it. The Find, Fix, Track, Target, Engage, and Assess (F2T2EA) sequence governs the flow of a surface attack and the brevity that supports it.

==== Target Acquisition Brevity ====
The following brevity codes describe the state of sensor awareness on a surface target. They are used throughout the F2T2EA chain by both fighters and controllers.
{| class="wikitable" style="width:100%;"
!Brevity
!Definition
|-
|'''DIRT'''
|Radar warning receiver indication of a surface threat in search mode. The threat is radiating but has not yet established a track.
|-
|'''MUD'''
|Radar warning receiver indication of a surface threat in track mode. The threat has established a track on the aircraft.
|-
|'''SINGER'''
|Radar warning receiver indication of a SAM launch. The threat has fired.
|-
|'''SCAN'''
|Search the indicated sector and report any contacts.
|-
|'''WORK'''
|Directive call to conduct geolocation on a specific target or area.
|-
|'''INVESTIGATE'''
|Verify specified elements of ROE, positive identification (PID), and coordination of forces on the referenced target or track.
|-
|'''FIXED'''
|Target has been located and its position established. Followed by accuracy qualifier: LOW ACCURACY (inside 1 nm) or HIGH ACCURACY (inside 1,000 ft).
|-
|'''MONITOR'''
|Maintain sensor awareness on a specified GROUP or object. Implies tactically significant changes will be communicated.
|-
|'''TRACK'''
|Directive call assigning responsibility to an asset for maintaining sensor or visual observation of a defined object or area.
|-
|'''CAPTURED'''
|Object has been acquired and is being actively tracked.
|-
|'''COVER'''
|Directive call to be ready for reattack or re-engage if weapon effects are not achieved.
|-
|'''HOUNDDOG'''
|Aircraft is in a position to employ weapons. Used in response to COVER.
|}

==== Threat Reaction ====
When a SAM threat is detected, the aircraft communicates on the mission tactical NET to enable reactive SEAD and maintain the common tactical picture.
{| class="wikitable" style="width:100%;"
!Fidelity
!Format
!Example
|-
|'''Low'''
|Call sign · RWR indication · bearing · DEFENDING with cardinal direction · ownship BULLSEYE
|HORNET 1, SINGER ELEVEN, BEARING 3-6-0, DEFENDING WEST, BULLSEYE 3-4-5/30
|-
|'''High'''
|Call sign · RWR indication · threat BULLSEYE/location · DEFENDING with cardinal direction
|BOLT 1, SINGER ELEVEN, BULLSEYE 3-6-0/32, DEFENDING WEST
|}
High fidelity is defined as a 5 nm semi-major ellipse accuracy or better. Use high fidelity when available — it enables SEAD aircraft to engage with precision rather than azimuth alone.

==== TRESPASS ====
Called when an aircraft enters a non-previously-known SAM MEZ or when any non-SEAD aircraft crosses inside the maximum recommended intercept range of a known SAM. The calling entity directs an immediate SNAP heading away from the threat.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Controller or Aircraft
|{CS} SNAP {Heading} TRESPASS {Threat Type} BULLSEYE {Bearing/Range}
|}
RAMBO 2, SNAP 1-7-0, TRESPASS FIFTEEN BULLSEYE 3-2-0/32.

==== Game Plan ====
The flight lead issues the game plan before pushing to the target. All flight members acknowledge in sequence. The game plan assigns targeting responsibility, cover responsibility, and establishes the push time and TOT. The Following are two examples for possible Gameplans. Note that this part is highly flxible
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|MC
|HORNET, BOLT, PYTHON, STANDBY GAME PLAN
|-
|FLs
|"HORNET" "BOLT" "PYTHON"
|-
|MC
|“HORNET, TARGET AND SCAN ALPHA ALPHA 0-1, TWO VEHICLE
CONVOY BULLSEYE 2-7-5/69, MOVING SOUTH, BEST. PUSH AT

21:17 FROM RED OSCAR.”

“BOLT, COVER ALPHA ALPHA 0-1.”

“RAMBO ESCORT AND PYTHON SEAD PER BRIEF.”
|-
|FLs
|“HORNET.” “BOLT.” “PYTHON.”
|}
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|FL
|SHADOW11 #1 AND #2 TARGET {Target Description} · #3 AND #4 COVER {Target Description}
|-
|All Members
|#2 · #3 · #4
|}
Target and cover assignments may be communicated digitally via data link. Each player acknowledges GOOD DATA if received digitally.
----

=== Strike ===
A strike is a planned attack against a pre-briefed fixed or moving ground target. Strike coordination occurs before and during the attack through a structured game plan, with clear assignment of targeting and cover responsibilities within the package.

==== Push ====
Once the game plan is acknowledged and the push time arrives, the attacking element calls PUSHING with the TOT. The cover element acknowledges readiness with HOUNDDOG, indicating they are in position to employ if the primary attack fails.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Attacking Aircraft
|{Controller-CS} {CS} CAPTURED {Target Description or Bullseye} PUSHING TOT {Time}
|-
|Cover Aircraft
|{CS} HOUNDDOG
|}

==== Weapon Away ====
The attacking aircraft calls weapon employment with time of flight. If the weapon requires continued support such as laser designation or scanning, this is added as a fill-in.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Attacking Aircraft
|{Controller-CS} {CS} ONE WEAPON AWAY {Target Description} {Time of Flight} SECONDS {LASING / SCANNING if applicable}
|}

==== Assessment ====
The attacking aircraft calls the result. Two outcomes are possible:
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
| colspan="2" style="text-align:center;" |''Desired weapon effects generated''
|-
|Attacking Aircraft
|{Controller-CS} {CS} SPLASH {Target Description} SUCCESSFUL
|-
| colspan="2" style="text-align:center;" |''Desired weapon effects not generated''
|-
|Attacking Aircraft
|{Controller-CS} {CS} SPLASH {Target Description} FUMBLE {CLEAN / HIT}
|}
FUMBLE CLEAN indicates no visible battle damage and no weapon impact noted. FUMBLE HIT indicates weapon impact was noted within a lethal distance but desired effects were not generated.

==== Reattack ====
If the primary attack results in FUMBLE, the cover element is directed to reattack.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|FL
|''(intraflight) {CS} COVER {Target Description or Bullseye} · {Cover CS} PUSH''
|-
|Cover Aircraft
|{Controller-CS} {CS} PUSHING TOT {Time}
|-
|Cover Aircraft
|{Controller-CS} {CS} ONE WEAPON AWAY {Time of Flight} SECONDS
|-
|Cover Aircraft
|{Controller-CS} {CS} SPLASH {Target Description} {SUCCESSFUL / FUMBLE}
|}

==== Egress ====
Following the attack, the flight egresses using one of three calls depending on the situation:
{| class="wikitable" style="width:100%;"
!Call
!Condition
!Phrase
|-
|'''MILLER TIME'''
|Last striker in the package has completed the attack
|{Controller-CS} {CS} MILLER TIME
|-
|'''BUGOUT'''
|Aircraft has completed its attack and has no intention to return
|{Controller-CS} {CS} BUGOUT {Direction}
|-
|'''OFF'''
|Aircraft has completed its attack and is repositioning or egressing within the area
|{Controller-CS} {CS} OFF {Direction}
|}

==== Full Strike Example ====
''(intraflight) SHADOW FLIGHT STANDBY GAME PLAN''
''(intraflight) #2 · #3 · #4''
''(intraflight) SHADOW FLIGHT, #1 AND #2 TARGET CONVOY BULLSEYE 0-3-0/15 · #3 AND #4 COVER''
''(intraflight) #2 · #3 · #4''

SHADOW11 CAPTURED BULLSEYE 0-3-0/15 PUSHING TOT 21:21:15
''(intraflight) SHADOW13 HOUNDDOG''

SHADOW12 ONE WEAPON AWAY CONVOY BULLSEYE 0-3-0/15 THIRTY SECONDS LASING

SHADOW11 SPLASH CONVOY BULLSEYE 0-3-0/15 FUMBLE HIT
''(intraflight) SHADOW11 COVER BULLSEYE 0-3-0/15 · SHADOW13 PUSH''

SHADOW13 PUSHING TOT 21:23:50
SHADOW13 ONE WEAPON AWAY FORTY SECONDS

SHADOW13 SPLASH CONVOY BULLSEYE 0-3-0/15 SUCCESSFUL
SHADOW11 MILLER TIME
----

=== CAS ===
''Content to be added.''
----

=== SEAD ===
Suppression of Enemy Air Defenses (SEAD) is the action taken to neutralize, destroy, or temporarily degrade surface-to-air missile systems and associated radar emitters. Its purpose is to allow other aircraft to operate within a threat environment that would otherwise deny or restrict their access.

==== The SEAD Game Plan ====
SEAD is not a reactive afterthought — it is a pre-planned, coordinated element of every strike package that operates in a contested environment. Before the mission, the SEAD lead establishes contracts with the rest of the package: who responds to which threat, in what priority order, with which weapon, and under what conditions.

The underlying logic of SEAD is straightforward. A SAM battery that is actively radiating is vulnerable to antiradiation missiles. A SAM battery that goes silent to avoid being targeted is temporarily suppressed and cannot engage aircraft. Either outcome — destruction or suppression — achieves the mission objective of protecting the strike package.

SEAD aircraft therefore have two primary tools:

* '''Hard kill''' — employment of an antiradiation missile (ARM) against a radiating threat. The ARM homes on the radar emission. If the radar goes silent the missile loses guidance, so the threat must be forced to stay radiating or be caught radiating.
* '''Soft kill''' — electromagnetic jamming (CANYON) that degrades the threat radar's ability to track or guide a missile without destroying the system.

The decision between hard and soft kill, and between SNIPER (range-known) and SLAPSHOT (range-unknown, immediate), is made based on the quality of targeting data available and the urgency of the situation.

==== Threat Reaction and SEAD Response Contracts ====
When a friendly aircraft calls DEFENDING, SEAD aircraft respond with one of the following:
{| class="wikitable" style="width:100%;"
!Response
!Definition (ATP 1-02.1)
!Meaning
|-
|'''HARM INBOUND'''
|[A/S] [EW] High-speed antiradiation missile already employed
|ARM is already in the air — the threat is being engaged
|-
|'''MAGNUM'''
|[A/S] [EW] Launch of FRIENDLY antiradiation missile
|ARM is being launched now in response to this call
|-
|'''ARIZONA'''
|[A/S] [EW] No antiradiation missile ordnance remaining
|SEAD aircraft is Winchester on ARMs
|}
These responses must be pre-briefed as contracts. Every aircraft in the package needs to know which SEAD asset covers which threat axis, what the response will be, and what to do if the SEAD asset is ARIZONA or unable to respond.

==== SNIPER and SLAPSHOT ====
Two directive calls are used to order ARM employment:

'''SNIPER''' — directive call to employ an antiradiation missile against a range-known threat. Used when targeting data is of sufficient quality to give a precise location.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|SEAD Lead
|{CS} SNIPER {Threat Type} BULLSEYE {Bearing/Range}
|-
|SEAD Aircraft
|{CS} MAGNUM {Threat Type} BULLSEYE {Bearing/Range}
|}
'''SLAPSHOT''' — directive call to immediately employ the best available antiradiation missile against a specified threat at the specified bearing. Range is unknown. Used when a threat is actively engaging friendly aircraft and there is no time to refine targeting data.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|SEAD Lead
|{CS} SLAPSHOT {Threat Type} BEARING {Bearing}
|-
|SEAD Aircraft
|{CS} HARM INBOUND
|}
The distinction matters: SNIPER is deliberate and precise, SLAPSHOT is immediate and azimuth-only. A SLAPSHOT ARM may not hit the radar if it goes silent, but it forces the threat to shut down or risk destruction — either outcome protects the package.

General/Tactical Communication Revision 1

2026-05-23T12:12:32Z

Niknam3: /* 08 / Air-to-Air Combat — Fundamentals */

MTTP/A2A

2026-05-23T12:12:24Z

Niknam3: Created page with "== 08 / Air-to-Air Combat == Air to Air Communication Procedures Air combat is primarily carried out by CAP aircraft. The two main mission types are '''DCA''' (Defensive Counter Air) and '''OCA''' (Offensive Counter Air). === Groups and Contacts === A '''GROUP''' is any number of air contacts within 3 nm in azimuth and range of each other. A '''CONTACT''' is an individual radar return within a GROUP. Single contact is the assumed strength for all GROUPs un..."

== 08 / Air-to-Air Combat ==
[[MTTP/A2A|Air to Air Communication Procedures]]

Air combat is primarily carried out by CAP aircraft. The two main mission types are '''DCA''' (Defensive Counter Air) and '''OCA''' (Offensive Counter Air).

=== Groups and Contacts ===
A '''GROUP''' is any number of air contacts within 3 nm in azimuth and range of each other. A '''CONTACT''' is an individual radar return within a GROUP. Single contact is the assumed strength for all GROUPs unless otherwise specified. A GROUP with three or more contacts is called '''HEAVY'''.

The '''PICTURE''' establishes a common tactical air image and describes the spatial relationship of GROUPs. It is always communicated in BULLSEYE format unless briefed otherwise. Only the Three GROUPs with highest Priority are Conveyed

=== Contact Declaration ===
Before a fighter can engage, a contact must be declared. Declaration is performed by the controller in response to a DECLARE request.

{| class="wikitable" style="width:100%;"
|-
! Declaration !! Meaning !! Engagement Authority
|-
| '''BOGEY''' || Identity unknown || Not cleared to engage
|-
| '''OUTLAW''' || Originates from known or suspected hostile area || Not cleared to engage; escalation criteria apply
|-
| '''SPADES''' || No valid IFF response on interrogation || Not cleared to engage; escalation criteria apply
|-
| '''BANDIT''' || Positively identified as enemy IAW theater ID criteria || Not cleared to engage; does not imply authority to fire
|-
| '''HOSTILE''' || Confirmed enemy; clearance to fire authorized IAW ROE || Cleared to engage
|-
| '''NEUTRAL''' || Positively identified as neutral || Not cleared to engage
|-
| '''FRIENDLY''' || Positively identified as friendly || Not cleared to engage
|-
| '''FURBALL''' || Friendly and non-friendly aircraft within 5 nm || Employment not authorized until resolved
|}

A BOGEY, BANDIT, OUTLAW, or SPADES classification does not authorize engagement. HOSTILE is the only declaration that authorizes weapons employment IAW ROE.

=== Communication Cadence by Intercept Phase ===
Communication priority shifts between the controller and fighters depending on the phase of the intercept.

{| class="wikitable" style="width:100%;"
|-
! Phase !! Priority Communicators
|-
| Pre-COMMIT / Marshal || 1. Controller · 2. Fighters
|-
| Post-COMMIT / Push || 1. Controller · 2. Fighter
|-
| Targeting / Weapons Employment || 1. Fighters · 2. Controller
|-
| Merge || 1. Engaged Fighter · 2. Supporting Fighters · 3. Controller
|-
| Post-Merge || 1. Fighter Clearing Merge · 2. Supporting Fighters · 3. Controller
|}

=== TAC Range ===
Called at 60 nm (default) by the first asset to recognize the separation. Signals all players to prepare for targeting. Pre-commit SA building continues until this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Fighter || {CS} {Group Label} TAC RANGE
|}

=== Airspace Sanitization ===
A Section consists of two aircraft, each equipped with its own radar. Regardless of the number of bars or maximum azimuth a single radar supports, no single system can cover the entire sky. To compensate, both radars are stacked and assigned to different portions of the airspace — each portion is called an '''Area of Responsibility (AOR)'''. This technique, known as '''Radar Mating''', vastly increases the total volume scanned and ensures that no unknown contacts are operating in the area beyond already-tracked groups. The exact parameters depend on the aircraft type: the US Navy recommends RWS, 140°, 6 bars, end scale 80 nm, with radars mated at 25 nm: placing the flight lead between 40,000 and 15,000 ft, and the wingman from ground level to 25,000 ft.

The process of actively scanning assigned AORs to confirm no unknown contacts are present is called '''Sanitisation'''.

Because both Radar Mating parameters and Sanitisation responsibilities directly affect how an engagement develops, all of this must be '''pre-briefed''' and set as a '''contract''' before the mission. Time pressure may not always permit a thorough sanitisation pass, and how to handle that contingency should likewise be agreed upon in the brief.

=== Targeting ===
The flight assigns GROUP responsibility and confirms classification.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} DECLARE {Group Label or Bullseye Position}
|-
| Controller || {Group Label} DECLARED {HOSTILE / BOGEY / FRIENDLY / UNABLE / FURBALL}
|-
| FL || {CS} TARGET {Group Label} {Tactic}
|-
| colspan="2" style="text-align:center;" | ''Once group appears on radar''
|-
| FL || {CS} TARGETED {Group Label} BULLSEYE {Bearing/Range}
|-
| Controller || ''No response if information correlates. Comparative response if correction is required.''
|}

== The Engagement Loop ==
The engagement loop is the core sequence executed by all fighter flights once committed and targeting is established. It repeats until the GROUP is splashed, leaves the area, or the flight resets.

=== MELD ===
The flight lead directs all flight members to shift their radars from wide sanitization to focused SA on the assigned GROUP. This transition narrows the radar from maximum azimuth and altitude coverage to a tighter volume centered on the target. Sanitization of the surrounding airspace ceases until DROPPING is called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''All flight members shift radar from sanitization to the assigned GROUP''
|}

=== SORT ===
The flight lead assigns individual contacts within the GROUP to specific flight members. Each member acknowledges with SORTED when they have confirmed their assigned contact on radar and are prepared to engage it. If a member cannot confirm their assigned contact, SORTED is withheld until resolution.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || ''(intraflight) FLIGHT SORT {Criteria}''
|-
| #2 || ''(intraflight) #2 SORTED''
|-
| #3 || ''(intraflight) #3 SORTED''
|-
| #4 || ''(intraflight) #4 SORTED''
|}

=== JUDY ===
Called by the flight lead when the flight no longer requires controller guidance to prosecute the intercept. From this point, the controller minimizes transmissions and provides situational awareness information only. JUDY is not always called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Provides SA and THREAT calls only.''
|}

=== ENGAGE ===
Directive call from the flight lead to a specific wingman to employ weapons. The flight lead may also direct simultaneous employment by multiple members.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} ENGAGE
|-
| Wingman || {CS}
|}

=== Weapon Employment ===
The firing aircraft calls the shot on TACC2 NET immediately after employment. The call includes shot type, GROUP label, contact description, BULLSEYE position, and altitude. The controller acknowledges with COPY SHOT.

If a fighter determines a GROUP HOSTILE and ROE has been met, the fighter may employ autonomously and include HOSTILE in the shot transmission.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft || {TACC2-CS} {CS} FOX THREE {Group Label} {Contact Description} BULLSEYE {Bearing/Range} {Altitude}
|-
| TACC2 || {TACC2-CS} COPY SHOT
|-
| colspan="2" style="text-align:center;" | ''Autonomous HOSTILE employment''
|-
| Firing Aircraft || {Controller-CS} {CS} FOX THREE {Group Label} BULLSEYE {Bearing/Range} {Altitude} HOSTILE
|-
| TACC2 || {TACC2-CS} COPY SHOT
|}

Multiple shots in one transmission are acceptable:
SHADOW12 FOX THREE NORTH GROUP LEAD CONTACT BULLSEYE 2-7-0/20 TWENTY THOUSAND; SHADOW11 FOX THREE NORTH GROUP TRAIL CONTACT.

=== OUT / DEFENDING ===
Following weapon employment the flight turns away from the threat. OUT is a planned maneuver executed at a prebriefed range. DEFENDING indicates a reactive maneuver against an incoming weapon and is called with the cardinal direction of the defensive turn.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction}
|-
| colspan="2" style="text-align:center;" | ''or, if reacting to an incoming weapon''
|-
| Aircraft || {CS} DEFENDING {Direction}
|}

=== DROPPING ===
May be called in conjunction with OUT. Signals the controller that the flight has ceased monitoring the GROUP and is returning to sanitization radar settings. Monitoring responsibility transfers back to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction} DROPPING {Group Label}
|-
| colspan="2" style="text-align:center;" | ''Controller resumes monitoring of the dropped GROUP''
|-
| Controller || ''Resumes monitoring.''
|}

=== Assessment ===
The flight assesses weapon effects from sensor data or controller reports. Three outcomes are possible:

{| class="wikitable" style="width:100%;"
|-
! Outcome !! Action
|-
| GROUP splashed || Call SPLASH
|-
| GROUP remains a factor, follow-up shot required || Turn IN, return to MELD
|-
| GROUP has left the area or is no longer a factor || Proceed with Tasking
|}

=== IN (Follow-up Engagement) ===
If the GROUP remains a factor and the tactic permits a follow-up shot, the flight turns back toward the GROUP. The IN call triggers a new cycle beginning at MELD.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IN {Direction}
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''Re-sort as required, then return to ENGAGE''
|}

=== SPLASH ===
Called when weapon effects confirm the GROUP or contact is destroyed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft or Controller || {CS} SPLASH {Group Label or Contact Description}
|}

=== Common Calls ===

==== DECLARE ====
Inquiry as to the identity of a specified GROUP. Full positional data in BULLSEYE format must accompany all responses.
MIKE, EAGLE 11, DECLARE NORTH GROUP.
EAGLE 11, NORTH GROUP BULLSEYE 2-7-3/27, TWENTY-TWO THOUSAND, TRACK EAST, BOGEY SPADES.

==== BOGEY DOPE ====
Request for BRAA information on the indicated GROUP or the closest GROUP if not specified. Does not imply fighter targeting.
MIKE, EAGLE 11, BOGEY DOPE NORTH GROUP.
EAGLE 11, NORTH GROUP BRAA 2-1-0/28, THIRTY-EIGHT THOUSAND, HOT, HOSTILE.

==== NAILS ====
Fighter's radar warning receiver is detecting an airborne interceptor radar in search mode. Called with bearing or cardinal direction.
EAGLE 1, NAILS 2-7-0.

==== SPIKED ====
Fighter is being actively tracked by an airborne radar. Called with bearing or cardinal direction. Controller correlates to a GROUP within ±30 degrees and responds with range, altitude, aspect, declaration, and GROUP name.
EAGLE 1, SPIKED 2-7-0.
EAGLE 1, SPIKE RANGE 17, THIRTY THOUSAND, HOSTILE EAST GROUP, TWO CONTACTS.

==== FADED and VANISHED ====
'''FADED''' — a previously tracked GROUP not updated by sensors for 30 seconds. The controller reports the GROUP as FADED with last known BULLSEYE position. Fighters maintain MONITOR responsibility if they can maintain correlation. FADED is not used for friendly aircraft — controllers use NEGATIVE CONTACT for friendlies not held on sensors.

'''VANISHED''' — a special case of FADED used when the GROUP is not in a known blind zone and is correlated to a friendly shot that meets parameters for successful termination.

==== Unexpected Contacts ====
Three distinct call types exist for contacts not part of the established picture:

{| class="wikitable" style="width:100%;"
|-
! Call !! Criteria !! Format
|-
| '''ADDITIONAL GROUP''' || Newly detected outside targeting range, or does not fit traditional label || BULLSEYE
|-
| '''POP-UP GROUP''' || Previously undetected; appears inside targeting range but outside THREAT range || BULLSEYE
|-
| '''THREAT GROUP''' || Undetected or unreported GROUP meeting briefed THREAT criteria || BRAA to the closest aircraft
|}

DARKSTAR, POP-UP GROUP BULLSEYE 2-7-0/15, FIVE THOUSAND, TRACK WEST, BOGEY SPADES.
RAMBO 2, THREAT GROUP BRAA 2-7-0/13, ONE THOUSAND, HOT, HOSTILE.

----

== 09 / Defensive Counter Air (DCA) ==
DCA is the use of fighter aircraft to defend a ground asset or airspace against hostile air threats. It uses prebriefed lanes and defined ranges.

=== DCA Range Structure ===
All ranges are prebriefed per sortie. The following are the standard range lines used in DCA:

{| class="wikitable" style="width:100%;"
|-
! Range Line !! Definition
|-
| '''Mission Fail Line''' || The line the enemy must not cross for the mission to succeed. Defines the maximum depth of the defensive problem.
|-
| '''Commit Line (CL)''' || The line at which a bogey is declared HOSTILE IAW theater ROE and the flight is authorized to commit. Prebriefed for all DCA sorties.
|-
| '''Targeting Range''' || The prebriefed distance at which all contacts must be intercepted. A GROUP inside this range with no assigned fighter is UNTARGETED. Prebriefed per sortie.
|-
| '''TAC Range''' || Default 60 nm from the closest fighter to the closest GROUP. Signals all players to prepare for targeting.
|-
| '''Threat Range''' || The prebriefed range at which an untargeted GROUP meeting THREAT criteria triggers a THREAT call. Prebriefed per sortie.
|}

=== COMMIT Authority ===
COMMIT authority is derived from the combatant commander and delegated through the chain of command. Any of the following may hold or recommend COMMIT authority depending on what is delegated:

{| class="wikitable" style="width:100%;"
|-
! Role !! Abbreviation !! Authority
|-
| Flight Lead || FL || Usually holds COMMIT authority unless delegated
|-
| Team Lead || TL || May hold COMMIT authority if delegated
|-
| Mission Commander || MC || May hold COMMIT authority if delegated
|-
| TACC2 || — || May hold COMMIT authority if delegated
|}

If only the MC, TL, or FL holds COMMIT authority, the controller may only recommend COMMIT. If the controller holds COMMIT authority, the MC and TL may only recommend.

=== DCA Flow ===

==== Lane Handover ====
When an outgoing flight is relieved on station by an incoming flight, a positive lane handover is required before the outgoing flight departs.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Off-going Lane Commander || {CS} MOVE FORWARD
|-
| On-coming Lane Commander || {CS}
|-
| colspan="2" style="text-align:center;" | ''On-coming aircraft may enter the lane. Lane commander authority has not yet transferred.''
|-
| Off-going Lane Commander || {CS} YOU HAVE THE LANE
|-
| On-coming Lane Commander || {CS} HAS THE LANE
|}

The off-going flight passes critical mission information to the controller before departing. The controller passes big-picture information to the on-coming flight before pushing them to the tactical frequency.

==== Pre-Commit ====
The flight arrives at its prebriefed CAP position with FENCE IN complete and radars in sanitization configuration. The controller holds picture responsibility.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} PICTURE
|-
| Controller || {CS} {Nr of Groups} {Group Label} BULLSEYE {Bearing/Range} {Altitude} TRACK {Direction} {Declaration} {Nr of Contacts}
|}

The flight evaluates commit criteria continuously. Pictures are requested as needed to maintain SA.

==== Commit ====

===== FIGHTER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} Recommend {CS} COMMIT
|-
| FL || {CS} COMMIT
|}

==== CONTROLLER AUTHORITY COMMIT ====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} Recommend Commit
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} {CS} COMMIT
|-
|FL
|{CS}
|}

After COMMIT, fighters hold radio priority.

==== Targeting ====
The flight assigns GROUP responsibility and confirms classification.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} DECLARE {Group Label or Bullseye Position}
|-
| Controller || {Group Label} DECLARED {HOSTILE / BOGEY / FRIENDLY / UNABLE / FURBALL}
|-
| FL || {CS} TARGET {Group Label} {Tactic}
|-
| colspan="2" style="text-align:center;" | ''Once group appears on radar''
|-
| FL || {CS} TARGETED {Group Label} BULLSEYE {Bearing/Range}
|-
| Controller || ''No response if information correlates. Comparative response if correction is required.''
|}

If DECLARE returns UNABLE or FURBALL, weapons employment is not authorized until classification is resolved.

==== Engagement Loop ====
The flight executes the standard engagement loop as defined in [[#08 / Air-to-Air Combat — Fundamentals|section 08]]. The loop repeats until the GROUP is splashed, leaves the lane, or the flight resets.

Once the Engagement is Complete the flight resets back to the briefed Position

==== RESET ====
Directs the flight to return to its prebriefed position or area of operations. RESET implies DROPPING and returns all targeting responsibility to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} RESET
|-
| colspan="2" style="text-align:center;" | ''Flight returns to prebriefed CAP position. Controller resumes full picture responsibility''
|}

==== THREAT Call ====
If a fighter will pierce THREAT range to an untargeted GROUP, the controller makes a THREAT call in BRAA format no later than THREAT range.
HEAT 31, ADDITIONAL GROUP THREAT, BRAA 1-2-5/35, THIRTY-FIVE THOUSAND, HOT, HOSTILE.

If the THREAT is within 5 nm of friendly fighters:
BOLT 1, THREAT NORTH THREE, TEN THOUSAND, TRACK SOUTH, HOSTILE.

----

== 10 / Offensive Counter Air (OCA) ==
OCA is the use of fighter aircraft to suppress, destroy, or neutralize enemy air assets before they can threaten friendly forces. Unlike DCA, OCA is not lane-based and does not require a commit line. The flight pushes into the threat environment rather than waiting for the threat to approach.

=== OCA Range Structure ===
The same range lines apply as in DCA — Threat Range, Targeting Range, and TAC Range — but all are prebriefed based on the specific mission geometry and threat environment. There is no commit line or mission fail line in OCA.

=== OCA Flow ===
OCA does not have a lane handover or a commit phase. The flight checks in, receives the picture, establishes targeting, and executes the engagement loop.

==== Pre-Targeting ====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} PICTURE
|-
| Controller || {CS} {Nr of Groups} {Group Label} BULLSEYE {Bearing/Range} {Altitude} TRACK {Direction} {Declaration} {Nr of Contacts}
|}

==== Targeting ====
Identical to DCA targeting. The flight assigns GROUP responsibility, declares, announces the tactical plan on intraflight, and calls TARGETED once the GROUP is on radar.

==== Engagement Loop ====
The flight executes the standard engagement loop as defined in [[#08 / Air-to-Air Combat — Fundamentals|section 08]].

The primary difference from DCA: in OCA there is no prebriefed position to RESET to in the same sense. RESET in OCA returns the flight to the prebriefed holding or egress point as defined in the mission brief.

----

== 11 / Intercept (VID) ==
A Visual Identification (VID) intercept is conducted when a contact cannot be declared HOSTILE or FRIENDLY by electronic means alone, and visual confirmation of aircraft type, markings, or behavior is required before engagement authority can be granted or withheld.

VID intercepts follow a structured sequence: the controller guides the fighter to a position from which a visual identification pass can be made, then the fighter reports the result and awaits further direction.

=== Intercept Flow ===

==== Commit ====
The controller or flight lead initiates the intercept against the unidentified contact.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} COMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration} {Nr of Contacts}
|-
| FL || {CS} COMMIT
|}

==== Guidance ====
The controller provides vectors to position the fighter for a VID pass. This is the only phase where the controller takes positive close control of the intercept geometry. BRAA format is used throughout.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} BRAA {Bearing/Range} {Altitude} {Aspect} {Declaration}
|-
| FL || {CS}
|-
| colspan="2" style="text-align:center;" | ''Controller continues to provide updated vectors until fighter calls JUDY''
|}

==== JUDY ====
The fighter calls JUDY when radar contact is established and no further controller guidance is required. The controller minimizes transmissions from this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Continues to provide SA information only.''
|}

==== Tally ====
The fighter calls TALLY when visual contact is established with the target.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} TALLY {Position}
|}

==== Identification ====
The fighter conducts the VID pass and reports the result to the controller. The report includes aircraft type, markings, and behavior observed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IDENTIFIED {Aircraft Type} {Markings / Behavior}
|-
| Controller || {CS} {Further Instructions / Declaration Update}
|}

If the contact is identified as HOSTILE following the VID pass, the controller issues the updated declaration and the flight may proceed to engagement IAW ROE. If the contact is FRIENDLY or NEUTRAL, the flight disengages and returns to its prebriefed position.

----

== 12 / Merge ==
A merge occurs when friendly and target aircraft arrive in the visual arena, within 3–5 nm of each other. At the merge, radar resolution becomes limiting and the engagement transitions from BVR to Within Visual Range (WVR).

=== Communication Priority at the Merge ===
The engaged fighter holds radio priority. The supporting fighter and controller subordinate their transmissions accordingly.

{| class="wikitable" style="width:100%;"
|-
! Role !! Responsibility
|-
| '''Engaged Fighter''' || Calls the merge, manages the engagement, and calls employment and results. Holds radio priority.
|-
| '''Supporting Fighter''' || Provides SA to the engaged fighter. Calls PRESS when directed and mutual support is maintained. Subordinates transmissions to the engaged fighter.
|-
| '''Controller''' || Minimizes transmissions. Provides THREAT calls, SA updates, and responds to fighter requests only.
|}

=== Merge Flow ===

==== MERGED ====
The controller calls MERGED when radar tracks come together within 3–5 nm, or the engaged fighter calls it when visual contact is made.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Engaged Fighter || {CS} MERGED {Group Label}
|}

==== IFF Calls ====
At the merge, positive visual identification of friend or foe is critical before employment. Standard IFF calls apply:

{| class="wikitable" style="width:100%;"
|-
! Term !! Meaning
|-
| '''TALLY''' || Visual contact established on the target or bandit
|-
| '''NO JOY''' || No visual contact with the target or bandit
|-
| '''VISUAL''' || Visual contact established on a friendly aircraft
|-
| '''BLIND''' || No visual contact with a friendly aircraft
|}

==== PRESS ====
The supporting fighter calls PRESS to indicate the requested action is approved and mutual support will be maintained. PRESS assumes VISUAL on the engaged fighter.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || ''(intraflight) {CS} PRESS''
|-
| Supporting Fighter || ''(intraflight) PRESS''
|}

==== Employment ====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || {Controller-CS} {CS} FOX TWO {Target Description}
|-
| Controller || COPY SHOT
|}

Gun employment is called as GUNS with target description.

==== SPLASH ====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || {Controller-CS} {CS} SPLASH {Group Label or Contact Description}
|-
| Controller || {CS} COPY SPLASH
|}

Following SPLASH the flight disengages, calls RESET, and returns to its prebriefed position unless directed otherwise.

General/Tactical Communication Revision 1

2026-05-23T12:10:54Z

Niknam3: /* 07 / Positive Identification (PID) and CDE */

<div style="font-size:1.1em; color:#660000; font-weight:bold;">SOURCE — Tactical Communications Guide</div><div style="font-size:0.85em; font-weight:bold;">Covers: Airspace Control · TACADMIN · Check-In · Force Packaging · Air-to-Air Communication · Brevity</div><div style="font-size:0.8em; color:#555;">''Based on ATP 3-52.4 / MCRP 3-20F.10 / NTTP 6-02.9 / AFTTP 3-2.8, October 2024. Adapted for DCS.''</div>
----
----

== 01 / Airspace Control ==
Airspace control is the exercise of delegated authority over designated airspace and users through control procedures and coordination measures to maximize operational effectiveness.

There are two methods of airspace control:

'''Positive Control''' relies on positive identification, tracking, and direction of aircraft within an airspace, conducted with electronic means by an agency having the authority and responsibility therein. It requires sensors to locate and identify airspace users in real time and communications to maintain continuous contact.

'''Procedural Control''' relies on a combination of previously agreed upon and promulgated orders and procedures. Examples include air defense identification procedures, voice and digital communications between aircraft and airspace control elements, and airspace control measures such as coordinating altitudes and restricted operating zones.

=== Tactical Command and Control (TAC C2) ===
TAC C2 agencies use positive and/or procedural control methods to control airspace and manage air operations. Throughout this guide, '''Controller''' is used as a generic term for the individual providing tactical control, whether airborne or ground-based.

Primary TAC C2 responsibilities:

* Enable the flow of forces to and from an objective area
* Provide threat warning information and maintain situational awareness
* Maintain SA of supporting asset status, threat information, and target area information
* Maintain air asset deconfliction to and from a working area

=== Transmission Types ===
All radio transmissions are associated with a call sign. There are three transmission types:

'''Directive''' — the call sign of the entity being directed is used.
HORNET 2, TARGET NORTH GROUP.
'''Interrogative''' — requests a response; format is [entity speaking to], [speaking entity].
MIKE, EAGLE 11, DECLARE NORTH GROUP.
'''Informative''' — provides information without requiring a response; format is [speaking entity].
EAGLE 11, FUEL YELLOW.

=== AUTHORITY ===
Their are the following party's that hold decreasing levels of control.

# Tactical Control Center - TACC2
# Mission Commander - MC
# Team Lead (previously called Package Lead) - TL
# Flight Lead - FL
# Element Lead - EL
# Wingman - WM

Within this squadron MC's duties will be taken over by TACC2 (due to missing personal)
----

== 02 / TACADMIN ==
Tactical Administration (TACADMIN) consists of all processes and procedures that occur in the TAC C2 area of operations. It covers interflight and intraflight procedures and airborne mission preparation that directly supports executing the tactical mission objective. Examples include weapon arming, sensor management, and tactical communication checks.

=== Fuel and Weapons Status ===
Aircraft are '''assumed GREEN''' unless otherwise reported.
{| class="wikitable" style="width:100%;"
!Status
!Meaning
|-
|GREEN
|Sufficient for continued mission execution
|-
|YELLOW
|Approaching a level insufficient to continue execution
|-
|RED
|Insufficient to continue execution
|}
Aircraft must relay YELLOW to the controller. The controller is responsible for coordinating on-station relief before an aircraft communicates RED.
RAMBO 01, FUEL RED, WEAPONS GREEN.

=== BRAA and BULLSEYE CallS ===
Tactical control format: '''Bearing, Range, Altitude, Aspect''' relative to the specified friendly aircraft. Used by the controller when information pertains to one specific aircraft, or in response to BOGEY DOPE, SNAPLOCK, and THREAT calls.

Bullseye format: Bearing and Range from BULLSEYE, Altitude, Aspect. Use for description of GROUP and TARGET
{| class="wikitable" style="width:100%;"
!Format
!Bearing
!Range
!Altitude
!Aspect
|-
|BRAA
|3 2 0
|30 nm
|20,000 ft
|Flanking
|-
|BULLSEYE
|1 1 0
|30
|25 Thousand
|HOT
|}

=== Flight Check / Frequency Change ===
When Switching a Frequency it is important to ensure that all Flight Members arrive on that Frequency. To ensure this the FL will execute a '''Flight Check''' a procedure that requires all wingman to respond on that frequency with their inflight Nr.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Controller
|{CS} Push Button #
|-
|''FL (interflight)''
|''{CS} Push Button #''
|-
|''FL (intraflight)''
|''Push {UHF/VHF, Radio 1/2} Button #''
|-
| colspan="2" style="text-align:center;" |''All flight members switch''
|-
|FL
|{CS} Check
|-
|WM
|2
|-
|EL
|3
|-
|2nd WM
|4
|}

=== Authentication (DRYAD) ===
Verifies contact with an allied unit. A challenging station picks a letter from the leftmost column and a second from that row. The responding station replies with the letter directly below the second chosen letter. The DRYAD table is issued in the pre-mission briefing. Pilots are responsible for initiating authentication with the controlling station.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|FL
|{Controller-CS} {CS} Authenticate E-A
|-
|TACC2
|Come back G
|-
|TACC2
|Authenticate J-U
|-
|FL
|Come back R
|-
|TACC2
|Authentication Sweet
|}

== 03 / Check-In Procedures ==
The purpose of check-in is to establish contact between aircrew and TAC C2, allow the controller to establish accountability, and pass critical mission information before handoff to the final controller.

Check-in accomplishes the following before and after mission execution: positive friendly identification via IFF and/or data link, ALPHA CHECK from BULLSEYE, safety-of-flight information, and weather update.

Note: BULLSEYE cannot be used for initial position calls — only valid after ALPHA CHECK.

=== Check In ON TACC2 NET (MNPOPCA Format) ===
The MNPOPCA format outlines the informations a aircrew should prepare before beginning the Check in process:
{| class="wikitable" style="width:100%;"
! style="width:25%;" |MNPOPCA Format
|-
|Number and Type of Aircraft
|-
|Position and Altitude
|-
|Ordnance (if applicable)
|-
|PLAYTIME
|-
|Capabilities (e.g., laser, infrared pod, data link)
|-
|Abort Code
|}

==== Check in AS FRAGGED ====
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
| colspan="2" style="text-align:center;" |''Flight Check, then Authentication''
|-
|FL
|{Controller-CS} {CS} as Fragged, Request Alpha Check from Bullseye
|-
|Controller
|{CS}, Identified, {Control Type}, Alpha Check Bullseye {Position}
|-
|FL
|{CS}
|}

==== Check in WITH EXCEPTIONS ====
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
| colspan="2" style="text-align:center;" |''Flight Check, then Authentication''
|-
|FL
|{Controller-CS} {CS} Mission Nr #-#-#-# Checking in with Exceptions. Request Alpha Check Bullseye
|-
|TACC2
|{CS}, Alpha Check Bullseye {Position} continue with Check In
|-
|FL
|{CS} {State Exceptions in plain Language}
|}
----

== 04 / Force Packaging ==
Before entering a target area or leaving the MARSHAL Hold the MC will ensure that all Flight are able to operate.

=== Roll Call ===
Roll call is initiated by the controller or MC at a predetermined time to confirm force accountability. Each flight lead or team lead responds with call sign in sequence.
MC: PACKAGE BRAVO WHISKEY, ROLL CALL.
FLs: EAGLE. VIPER WITH EXCEPTIONS. BONES. GROWL. MOJO.
MC: VIPER, GO WITH EXCEPTIONS.
VIPER FL: VIPER MINUS 2.
=== Timing Changes ===
'''ROLEX''' — timeline adjustment in minutes, always referenced from the original preplanned mission execution time. PLUS is assumed. Not additive.
PACKAGE WHISKEY ALPHA, ROLEX 10. (Original 1500Z → New 1510Z)
'''SLIP''' — time delay to an individual flight or element event. Not additive.
HOSS 1, SLIP TOT 6 MINUTES. (Original 1500Z → New 1506Z)
----

== 06 / Air-to-Air Refuelling ==
AAR requires close coordination with the tanker around a pre-briefed Rendezvous (RV). SOURCE uses '''RV Alpha (Fixed Anchor)''' for all operations.

=== Tanker Orbit Stack ===
{| class="wikitable" style="width:100%;"
!Level
!Usage
|-
|'''ALPHA'''
|Receivers departing · Emergency
|-
|'''BRAVO'''
|Tanker base level
|-
|'''CHARLIE'''
|Receiver evasive
|-
|'''DELTA'''
|Receivers approaching
|}

=== RV Alpha Procedure ===
Receiver: fly 2,000 ft below AAR altitude · follow controller heading · declare JUDY on radar contact · declare VISUAL when in sight · weapons safe and radar off · take ECHELON LEFT when authorized.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Controller
|{CS} Proceed Tanker BRAA {BRAA}, RV Alpha, Tanker Freq {Freq} {Instructions}
|-
|FL
|{CS} Roger, RV Alpha, Tanker Freq {Freq} {Readback}
|-
| colspan="2" style="text-align:center;" |''Once flight has radar contact with tanker''
|-
|FL
|{Flight Name} Judy 1, Weapons Safe
|-
|All wingmen (in order)
|2, 3, 4… Weapons Safe
|-
| colspan="2" style="text-align:center;" |''Once tanker is in sight''
|-
|Controller
|{CS} Tanker {x} o'clock, report visual
|-
|FL
|{CS} Nose Cold, visual with tanker
|-
|Controller
|{CS} Roger, contact boom
|-
| colspan="2" style="text-align:center;" |''Switch to DCS tanker frequency''
|}
FL must confirm Nose Cold with wingmen on intraflight before reporting to the controller.
----

== 07 / Positive Identification (PID) ==
PID proves, to a defensible standard, that the contact is a legitimate target under the ROE. Proof may come from sensors, behavior, location, declarations, or higher authority.
{| class="wikitable" style="width:100%;"
!Type
!Description
|-
|'''Electronic PID'''
|IFF interrogation, data link picture, NCTR, controller declaration. Most common form in BVR.
|-
|'''Visual PID'''
|Confirm number, type, livery, armament, heading, speed. Requires merge or VID pass.
|-
|'''Ground Targets'''
|Correlate with pre-briefed target.
|}
----

== 08 / Air-to-Air Combat — Fundamentals ==
Air combat is primarily carried out by CAP aircraft. The two main mission types are '''DCA''' (Defensive Counter Air) and '''OCA''' (Offensive Counter Air).

=== Groups and Contacts ===
A '''GROUP''' is any number of air contacts within 3 nm in azimuth and range of each other. A '''CONTACT''' is an individual radar return within a GROUP. Single contact is the assumed strength for all GROUPs unless otherwise specified. A GROUP with three or more contacts is called '''HEAVY'''.

The '''PICTURE''' establishes a common tactical air image and describes the spatial relationship of GROUPs. It is always communicated in BULLSEYE format unless briefed otherwise. Only the Three GROUPs with highest Priority are Conveyed

=== Contact Declaration ===
Before a fighter can engage, a contact must be declared. Declaration is performed by the controller in response to a DECLARE request.

{| class="wikitable" style="width:100%;"
|-
! Declaration !! Meaning !! Engagement Authority
|-
| '''BOGEY''' || Identity unknown || Not cleared to engage
|-
| '''OUTLAW''' || Originates from known or suspected hostile area || Not cleared to engage; escalation criteria apply
|-
| '''SPADES''' || No valid IFF response on interrogation || Not cleared to engage; escalation criteria apply
|-
| '''BANDIT''' || Positively identified as enemy IAW theater ID criteria || Not cleared to engage; does not imply authority to fire
|-
| '''HOSTILE''' || Confirmed enemy; clearance to fire authorized IAW ROE || Cleared to engage
|-
| '''NEUTRAL''' || Positively identified as neutral || Not cleared to engage
|-
| '''FRIENDLY''' || Positively identified as friendly || Not cleared to engage
|-
| '''FURBALL''' || Friendly and non-friendly aircraft within 5 nm || Employment not authorized until resolved
|}

A BOGEY, BANDIT, OUTLAW, or SPADES classification does not authorize engagement. HOSTILE is the only declaration that authorizes weapons employment IAW ROE.

=== Communication Cadence by Intercept Phase ===
Communication priority shifts between the controller and fighters depending on the phase of the intercept.

{| class="wikitable" style="width:100%;"
|-
! Phase !! Priority Communicators
|-
| Pre-COMMIT / Marshal || 1. Controller · 2. Fighters
|-
| Post-COMMIT / Push || 1. Controller · 2. Fighter
|-
| Targeting / Weapons Employment || 1. Fighters · 2. Controller
|-
| Merge || 1. Engaged Fighter · 2. Supporting Fighters · 3. Controller
|-
| Post-Merge || 1. Fighter Clearing Merge · 2. Supporting Fighters · 3. Controller
|}

=== TAC Range ===
Called at 60 nm (default) by the first asset to recognize the separation. Signals all players to prepare for targeting. Pre-commit SA building continues until this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Fighter || {CS} {Group Label} TAC RANGE
|}

=== Airspace Sanitization ===
A Section consists of two aircraft, each equipped with its own radar. Regardless of the number of bars or maximum azimuth a single radar supports, no single system can cover the entire sky. To compensate, both radars are stacked and assigned to different portions of the airspace — each portion is called an '''Area of Responsibility (AOR)'''. This technique, known as '''Radar Mating''', vastly increases the total volume scanned and ensures that no unknown contacts are operating in the area beyond already-tracked groups. The exact parameters depend on the aircraft type: the US Navy recommends RWS, 140°, 6 bars, end scale 80 nm, with radars mated at 25 nm: placing the flight lead between 40,000 and 15,000 ft, and the wingman from ground level to 25,000 ft.

The process of actively scanning assigned AORs to confirm no unknown contacts are present is called '''Sanitisation'''.

Because both Radar Mating parameters and Sanitisation responsibilities directly affect how an engagement develops, all of this must be '''pre-briefed''' and set as a '''contract''' before the mission. Time pressure may not always permit a thorough sanitisation pass, and how to handle that contingency should likewise be agreed upon in the brief.

=== Targeting ===
The flight assigns GROUP responsibility and confirms classification.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} DECLARE {Group Label or Bullseye Position}
|-
| Controller || {Group Label} DECLARED {HOSTILE / BOGEY / FRIENDLY / UNABLE / FURBALL}
|-
| FL || {CS} TARGET {Group Label} {Tactic}
|-
| colspan="2" style="text-align:center;" | ''Once group appears on radar''
|-
| FL || {CS} TARGETED {Group Label} BULLSEYE {Bearing/Range}
|-
| Controller || ''No response if information correlates. Comparative response if correction is required.''
|}

== The Engagement Loop ==
The engagement loop is the core sequence executed by all fighter flights once committed and targeting is established. It repeats until the GROUP is splashed, leaves the area, or the flight resets.

=== MELD ===
The flight lead directs all flight members to shift their radars from wide sanitization to focused SA on the assigned GROUP. This transition narrows the radar from maximum azimuth and altitude coverage to a tighter volume centered on the target. Sanitization of the surrounding airspace ceases until DROPPING is called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''All flight members shift radar from sanitization to the assigned GROUP''
|}

=== SORT ===
The flight lead assigns individual contacts within the GROUP to specific flight members. Each member acknowledges with SORTED when they have confirmed their assigned contact on radar and are prepared to engage it. If a member cannot confirm their assigned contact, SORTED is withheld until resolution.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || ''(intraflight) FLIGHT SORT {Criteria}''
|-
| #2 || ''(intraflight) #2 SORTED''
|-
| #3 || ''(intraflight) #3 SORTED''
|-
| #4 || ''(intraflight) #4 SORTED''
|}

=== JUDY ===
Called by the flight lead when the flight no longer requires controller guidance to prosecute the intercept. From this point, the controller minimizes transmissions and provides situational awareness information only. JUDY is not always called.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Provides SA and THREAT calls only.''
|}

=== ENGAGE ===
Directive call from the flight lead to a specific wingman to employ weapons. The flight lead may also direct simultaneous employment by multiple members.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} ENGAGE
|-
| Wingman || {CS}
|}

=== Weapon Employment ===
The firing aircraft calls the shot on TACC2 NET immediately after employment. The call includes shot type, GROUP label, contact description, BULLSEYE position, and altitude. The controller acknowledges with COPY SHOT.

If a fighter determines a GROUP HOSTILE and ROE has been met, the fighter may employ autonomously and include HOSTILE in the shot transmission.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft || {TACC2-CS} {CS} FOX THREE {Group Label} {Contact Description} BULLSEYE {Bearing/Range} {Altitude}
|-
| TACC2 || {TACC2-CS} COPY SHOT
|-
| colspan="2" style="text-align:center;" | ''Autonomous HOSTILE employment''
|-
| Firing Aircraft || {Controller-CS} {CS} FOX THREE {Group Label} BULLSEYE {Bearing/Range} {Altitude} HOSTILE
|-
| TACC2 || {TACC2-CS} COPY SHOT
|}

Multiple shots in one transmission are acceptable:
SHADOW12 FOX THREE NORTH GROUP LEAD CONTACT BULLSEYE 2-7-0/20 TWENTY THOUSAND; SHADOW11 FOX THREE NORTH GROUP TRAIL CONTACT.

=== OUT / DEFENDING ===
Following weapon employment the flight turns away from the threat. OUT is a planned maneuver executed at a prebriefed range. DEFENDING indicates a reactive maneuver against an incoming weapon and is called with the cardinal direction of the defensive turn.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction}
|-
| colspan="2" style="text-align:center;" | ''or, if reacting to an incoming weapon''
|-
| Aircraft || {CS} DEFENDING {Direction}
|}

=== DROPPING ===
May be called in conjunction with OUT. Signals the controller that the flight has ceased monitoring the GROUP and is returning to sanitization radar settings. Monitoring responsibility transfers back to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} OUT {Direction} DROPPING {Group Label}
|-
| colspan="2" style="text-align:center;" | ''Controller resumes monitoring of the dropped GROUP''
|-
| Controller || ''Resumes monitoring.''
|}

=== Assessment ===
The flight assesses weapon effects from sensor data or controller reports. Three outcomes are possible:

{| class="wikitable" style="width:100%;"
|-
! Outcome !! Action
|-
| GROUP splashed || Call SPLASH
|-
| GROUP remains a factor, follow-up shot required || Turn IN, return to MELD
|-
| GROUP has left the area or is no longer a factor || Proceed with Tasking
|}

=== IN (Follow-up Engagement) ===
If the GROUP remains a factor and the tactic permits a follow-up shot, the flight turns back toward the GROUP. The IN call triggers a new cycle beginning at MELD.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IN {Direction}
|-
| FL || {Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''Re-sort as required, then return to ENGAGE''
|}

=== SPLASH ===
Called when weapon effects confirm the GROUP or contact is destroyed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Firing Aircraft or Controller || {CS} SPLASH {Group Label or Contact Description}
|}

=== Common Calls ===

==== DECLARE ====
Inquiry as to the identity of a specified GROUP. Full positional data in BULLSEYE format must accompany all responses.
MIKE, EAGLE 11, DECLARE NORTH GROUP.
EAGLE 11, NORTH GROUP BULLSEYE 2-7-3/27, TWENTY-TWO THOUSAND, TRACK EAST, BOGEY SPADES.

==== BOGEY DOPE ====
Request for BRAA information on the indicated GROUP or the closest GROUP if not specified. Does not imply fighter targeting.
MIKE, EAGLE 11, BOGEY DOPE NORTH GROUP.
EAGLE 11, NORTH GROUP BRAA 2-1-0/28, THIRTY-EIGHT THOUSAND, HOT, HOSTILE.

==== NAILS ====
Fighter's radar warning receiver is detecting an airborne interceptor radar in search mode. Called with bearing or cardinal direction.
EAGLE 1, NAILS 2-7-0.

==== SPIKED ====
Fighter is being actively tracked by an airborne radar. Called with bearing or cardinal direction. Controller correlates to a GROUP within ±30 degrees and responds with range, altitude, aspect, declaration, and GROUP name.
EAGLE 1, SPIKED 2-7-0.
EAGLE 1, SPIKE RANGE 17, THIRTY THOUSAND, HOSTILE EAST GROUP, TWO CONTACTS.

==== FADED and VANISHED ====
'''FADED''' — a previously tracked GROUP not updated by sensors for 30 seconds. The controller reports the GROUP as FADED with last known BULLSEYE position. Fighters maintain MONITOR responsibility if they can maintain correlation. FADED is not used for friendly aircraft — controllers use NEGATIVE CONTACT for friendlies not held on sensors.

'''VANISHED''' — a special case of FADED used when the GROUP is not in a known blind zone and is correlated to a friendly shot that meets parameters for successful termination.

==== Unexpected Contacts ====
Three distinct call types exist for contacts not part of the established picture:

{| class="wikitable" style="width:100%;"
|-
! Call !! Criteria !! Format
|-
| '''ADDITIONAL GROUP''' || Newly detected outside targeting range, or does not fit traditional label || BULLSEYE
|-
| '''POP-UP GROUP''' || Previously undetected; appears inside targeting range but outside THREAT range || BULLSEYE
|-
| '''THREAT GROUP''' || Undetected or unreported GROUP meeting briefed THREAT criteria || BRAA to the closest aircraft
|}

DARKSTAR, POP-UP GROUP BULLSEYE 2-7-0/15, FIVE THOUSAND, TRACK WEST, BOGEY SPADES.
RAMBO 2, THREAT GROUP BRAA 2-7-0/13, ONE THOUSAND, HOT, HOSTILE.

----

== 09 / Defensive Counter Air (DCA) ==
DCA is the use of fighter aircraft to defend a ground asset or airspace against hostile air threats. It uses prebriefed lanes and defined ranges.

=== DCA Range Structure ===
All ranges are prebriefed per sortie. The following are the standard range lines used in DCA:

{| class="wikitable" style="width:100%;"
|-
! Range Line !! Definition
|-
| '''Mission Fail Line''' || The line the enemy must not cross for the mission to succeed. Defines the maximum depth of the defensive problem.
|-
| '''Commit Line (CL)''' || The line at which a bogey is declared HOSTILE IAW theater ROE and the flight is authorized to commit. Prebriefed for all DCA sorties.
|-
| '''Targeting Range''' || The prebriefed distance at which all contacts must be intercepted. A GROUP inside this range with no assigned fighter is UNTARGETED. Prebriefed per sortie.
|-
| '''TAC Range''' || Default 60 nm from the closest fighter to the closest GROUP. Signals all players to prepare for targeting.
|-
| '''Threat Range''' || The prebriefed range at which an untargeted GROUP meeting THREAT criteria triggers a THREAT call. Prebriefed per sortie.
|}

=== COMMIT Authority ===
COMMIT authority is derived from the combatant commander and delegated through the chain of command. Any of the following may hold or recommend COMMIT authority depending on what is delegated:

{| class="wikitable" style="width:100%;"
|-
! Role !! Abbreviation !! Authority
|-
| Flight Lead || FL || Usually holds COMMIT authority unless delegated
|-
| Team Lead || TL || May hold COMMIT authority if delegated
|-
| Mission Commander || MC || May hold COMMIT authority if delegated
|-
| TACC2 || — || May hold COMMIT authority if delegated
|}

If only the MC, TL, or FL holds COMMIT authority, the controller may only recommend COMMIT. If the controller holds COMMIT authority, the MC and TL may only recommend.

=== DCA Flow ===

==== Lane Handover ====
When an outgoing flight is relieved on station by an incoming flight, a positive lane handover is required before the outgoing flight departs.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Off-going Lane Commander || {CS} MOVE FORWARD
|-
| On-coming Lane Commander || {CS}
|-
| colspan="2" style="text-align:center;" | ''On-coming aircraft may enter the lane. Lane commander authority has not yet transferred.''
|-
| Off-going Lane Commander || {CS} YOU HAVE THE LANE
|-
| On-coming Lane Commander || {CS} HAS THE LANE
|}

The off-going flight passes critical mission information to the controller before departing. The controller passes big-picture information to the on-coming flight before pushing them to the tactical frequency.

==== Pre-Commit ====
The flight arrives at its prebriefed CAP position with FENCE IN complete and radars in sanitization configuration. The controller holds picture responsibility.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} PICTURE
|-
| Controller || {CS} {Nr of Groups} {Group Label} BULLSEYE {Bearing/Range} {Altitude} TRACK {Direction} {Declaration} {Nr of Contacts}
|}

The flight evaluates commit criteria continuously. Pictures are requested as needed to maintain SA.

==== Commit ====

===== FIGHTER AUTHORITY COMMIT =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} Recommend {CS} COMMIT
|-
| FL || {CS} COMMIT
|}

==== CONTROLLER AUTHORITY COMMIT ====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} Recommend Commit
|-
| TACC2 || {TACC2-CS} {BULLSEYE CALL} {CS} COMMIT
|-
|FL
|{CS}
|}

After COMMIT, fighters hold radio priority.

==== Targeting ====
The flight assigns GROUP responsibility and confirms classification.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} DECLARE {Group Label or Bullseye Position}
|-
| Controller || {Group Label} DECLARED {HOSTILE / BOGEY / FRIENDLY / UNABLE / FURBALL}
|-
| FL || {CS} TARGET {Group Label} {Tactic}
|-
| colspan="2" style="text-align:center;" | ''Once group appears on radar''
|-
| FL || {CS} TARGETED {Group Label} BULLSEYE {Bearing/Range}
|-
| Controller || ''No response if information correlates. Comparative response if correction is required.''
|}

If DECLARE returns UNABLE or FURBALL, weapons employment is not authorized until classification is resolved.

==== Engagement Loop ====
The flight executes the standard engagement loop as defined in [[#08 / Air-to-Air Combat — Fundamentals|section 08]]. The loop repeats until the GROUP is splashed, leaves the lane, or the flight resets.

Once the Engagement is Complete the flight resets back to the briefed Position

==== RESET ====
Directs the flight to return to its prebriefed position or area of operations. RESET implies DROPPING and returns all targeting responsibility to the controller.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} RESET
|-
| colspan="2" style="text-align:center;" | ''Flight returns to prebriefed CAP position. Controller resumes full picture responsibility''
|}

==== THREAT Call ====
If a fighter will pierce THREAT range to an untargeted GROUP, the controller makes a THREAT call in BRAA format no later than THREAT range.
HEAT 31, ADDITIONAL GROUP THREAT, BRAA 1-2-5/35, THIRTY-FIVE THOUSAND, HOT, HOSTILE.

If the THREAT is within 5 nm of friendly fighters:
BOLT 1, THREAT NORTH THREE, TEN THOUSAND, TRACK SOUTH, HOSTILE.

----

== 10 / Offensive Counter Air (OCA) ==
OCA is the use of fighter aircraft to suppress, destroy, or neutralize enemy air assets before they can threaten friendly forces. Unlike DCA, OCA is not lane-based and does not require a commit line. The flight pushes into the threat environment rather than waiting for the threat to approach.

=== OCA Range Structure ===
The same range lines apply as in DCA — Threat Range, Targeting Range, and TAC Range — but all are prebriefed based on the specific mission geometry and threat environment. There is no commit line or mission fail line in OCA.

=== OCA Flow ===
OCA does not have a lane handover or a commit phase. The flight checks in, receives the picture, establishes targeting, and executes the engagement loop.

==== Pre-Targeting ====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} PICTURE
|-
| Controller || {CS} {Nr of Groups} {Group Label} BULLSEYE {Bearing/Range} {Altitude} TRACK {Direction} {Declaration} {Nr of Contacts}
|}

==== Targeting ====
Identical to DCA targeting. The flight assigns GROUP responsibility, declares, announces the tactical plan on intraflight, and calls TARGETED once the GROUP is on radar.

==== Engagement Loop ====
The flight executes the standard engagement loop as defined in [[#08 / Air-to-Air Combat — Fundamentals|section 08]].

The primary difference from DCA: in OCA there is no prebriefed position to RESET to in the same sense. RESET in OCA returns the flight to the prebriefed holding or egress point as defined in the mission brief.

----

== 11 / Intercept (VID) ==
A Visual Identification (VID) intercept is conducted when a contact cannot be declared HOSTILE or FRIENDLY by electronic means alone, and visual confirmation of aircraft type, markings, or behavior is required before engagement authority can be granted or withheld.

VID intercepts follow a structured sequence: the controller guides the fighter to a position from which a visual identification pass can be made, then the fighter reports the result and awaits further direction.

=== Intercept Flow ===

==== Commit ====
The controller or flight lead initiates the intercept against the unidentified contact.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} COMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration} {Nr of Contacts}
|-
| FL || {CS} COMMIT
|}

==== Guidance ====
The controller provides vectors to position the fighter for a VID pass. This is the only phase where the controller takes positive close control of the intercept geometry. BRAA format is used throughout.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller || {CS} BRAA {Bearing/Range} {Altitude} {Aspect} {Declaration}
|-
| FL || {CS}
|-
| colspan="2" style="text-align:center;" | ''Controller continues to provide updated vectors until fighter calls JUDY''
|}

==== JUDY ====
The fighter calls JUDY when radar contact is established and no further controller guidance is required. The controller minimizes transmissions from this point.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} JUDY
|-
| Controller || ''Minimizes transmissions. Continues to provide SA information only.''
|}

==== Tally ====
The fighter calls TALLY when visual contact is established with the target.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {CS} TALLY {Position}
|}

==== Identification ====
The fighter conducts the VID pass and reports the result to the controller. The report includes aircraft type, markings, and behavior observed.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| FL || {Controller-CS} {CS} IDENTIFIED {Aircraft Type} {Markings / Behavior}
|-
| Controller || {CS} {Further Instructions / Declaration Update}
|}

If the contact is identified as HOSTILE following the VID pass, the controller issues the updated declaration and the flight may proceed to engagement IAW ROE. If the contact is FRIENDLY or NEUTRAL, the flight disengages and returns to its prebriefed position.

----

== 12 / Merge ==
A merge occurs when friendly and target aircraft arrive in the visual arena, within 3–5 nm of each other. At the merge, radar resolution becomes limiting and the engagement transitions from BVR to Within Visual Range (WVR).

=== Communication Priority at the Merge ===
The engaged fighter holds radio priority. The supporting fighter and controller subordinate their transmissions accordingly.

{| class="wikitable" style="width:100%;"
|-
! Role !! Responsibility
|-
| '''Engaged Fighter''' || Calls the merge, manages the engagement, and calls employment and results. Holds radio priority.
|-
| '''Supporting Fighter''' || Provides SA to the engaged fighter. Calls PRESS when directed and mutual support is maintained. Subordinates transmissions to the engaged fighter.
|-
| '''Controller''' || Minimizes transmissions. Provides THREAT calls, SA updates, and responds to fighter requests only.
|}

=== Merge Flow ===

==== MERGED ====
The controller calls MERGED when radar tracks come together within 3–5 nm, or the engaged fighter calls it when visual contact is made.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Controller or Engaged Fighter || {CS} MERGED {Group Label}
|}

==== IFF Calls ====
At the merge, positive visual identification of friend or foe is critical before employment. Standard IFF calls apply:

{| class="wikitable" style="width:100%;"
|-
! Term !! Meaning
|-
| '''TALLY''' || Visual contact established on the target or bandit
|-
| '''NO JOY''' || No visual contact with the target or bandit
|-
| '''VISUAL''' || Visual contact established on a friendly aircraft
|-
| '''BLIND''' || No visual contact with a friendly aircraft
|}

==== PRESS ====
The supporting fighter calls PRESS to indicate the requested action is approved and mutual support will be maintained. PRESS assumes VISUAL on the engaged fighter.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || ''(intraflight) {CS} PRESS''
|-
| Supporting Fighter || ''(intraflight) PRESS''
|}

==== Employment ====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || {Controller-CS} {CS} FOX TWO {Target Description}
|-
| Controller || COPY SHOT
|}

Gun employment is called as GUNS with target description.

==== SPLASH ====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Engaged Fighter || {Controller-CS} {CS} SPLASH {Group Label or Contact Description}
|-
| Controller || {CS} COPY SPLASH
|}

Following SPLASH the flight disengages, calls RESET, and returns to its prebriefed position unless directed otherwise.

----

== 13 / Air-to-Surface Communication ==

=== Fundamentals ===
Air-to-surface operations require a shared vocabulary for describing the progression from finding a target to destroying it. The Find, Fix, Track, Target, Engage, and Assess (F2T2EA) sequence governs the flow of a surface attack and the brevity that supports it.

==== Target Acquisition Brevity ====
The following brevity codes describe the state of sensor awareness on a surface target. They are used throughout the F2T2EA chain by both fighters and controllers.
{| class="wikitable" style="width:100%;"
!Brevity
!Definition
|-
|'''DIRT'''
|Radar warning receiver indication of a surface threat in search mode. The threat is radiating but has not yet established a track.
|-
|'''MUD'''
|Radar warning receiver indication of a surface threat in track mode. The threat has established a track on the aircraft.
|-
|'''SINGER'''
|Radar warning receiver indication of a SAM launch. The threat has fired.
|-
|'''SCAN'''
|Search the indicated sector and report any contacts.
|-
|'''WORK'''
|Directive call to conduct geolocation on a specific target or area.
|-
|'''INVESTIGATE'''
|Verify specified elements of ROE, positive identification (PID), and coordination of forces on the referenced target or track.
|-
|'''FIXED'''
|Target has been located and its position established. Followed by accuracy qualifier: LOW ACCURACY (inside 1 nm) or HIGH ACCURACY (inside 1,000 ft).
|-
|'''MONITOR'''
|Maintain sensor awareness on a specified GROUP or object. Implies tactically significant changes will be communicated.
|-
|'''TRACK'''
|Directive call assigning responsibility to an asset for maintaining sensor or visual observation of a defined object or area.
|-
|'''CAPTURED'''
|Object has been acquired and is being actively tracked.
|-
|'''COVER'''
|Directive call to be ready for reattack or re-engage if weapon effects are not achieved.
|-
|'''HOUNDDOG'''
|Aircraft is in a position to employ weapons. Used in response to COVER.
|}

==== Threat Reaction ====
When a SAM threat is detected, the aircraft communicates on the mission tactical NET to enable reactive SEAD and maintain the common tactical picture.
{| class="wikitable" style="width:100%;"
!Fidelity
!Format
!Example
|-
|'''Low'''
|Call sign · RWR indication · bearing · DEFENDING with cardinal direction · ownship BULLSEYE
|HORNET 1, SINGER ELEVEN, BEARING 3-6-0, DEFENDING WEST, BULLSEYE 3-4-5/30
|-
|'''High'''
|Call sign · RWR indication · threat BULLSEYE/location · DEFENDING with cardinal direction
|BOLT 1, SINGER ELEVEN, BULLSEYE 3-6-0/32, DEFENDING WEST
|}
High fidelity is defined as a 5 nm semi-major ellipse accuracy or better. Use high fidelity when available — it enables SEAD aircraft to engage with precision rather than azimuth alone.

==== TRESPASS ====
Called when an aircraft enters a non-previously-known SAM MEZ or when any non-SEAD aircraft crosses inside the maximum recommended intercept range of a known SAM. The calling entity directs an immediate SNAP heading away from the threat.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Controller or Aircraft
|{CS} SNAP {Heading} TRESPASS {Threat Type} BULLSEYE {Bearing/Range}
|}
RAMBO 2, SNAP 1-7-0, TRESPASS FIFTEEN BULLSEYE 3-2-0/32.

==== Game Plan ====
The flight lead issues the game plan before pushing to the target. All flight members acknowledge in sequence. The game plan assigns targeting responsibility, cover responsibility, and establishes the push time and TOT. The Following are two examples for possible Gameplans. Note that this part is highly flxible
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|MC
|HORNET, BOLT, PYTHON, STANDBY GAME PLAN
|-
|FLs
|"HORNET" "BOLT" "PYTHON"
|-
|MC
|“HORNET, TARGET AND SCAN ALPHA ALPHA 0-1, TWO VEHICLE
CONVOY BULLSEYE 2-7-5/69, MOVING SOUTH, BEST. PUSH AT

21:17 FROM RED OSCAR.”

“BOLT, COVER ALPHA ALPHA 0-1.”

“RAMBO ESCORT AND PYTHON SEAD PER BRIEF.”
|-
|FLs
|“HORNET.” “BOLT.” “PYTHON.”
|}
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|FL
|SHADOW11 #1 AND #2 TARGET {Target Description} · #3 AND #4 COVER {Target Description}
|-
|All Members
|#2 · #3 · #4
|}
Target and cover assignments may be communicated digitally via data link. Each player acknowledges GOOD DATA if received digitally.
----

=== Strike ===
A strike is a planned attack against a pre-briefed fixed or moving ground target. Strike coordination occurs before and during the attack through a structured game plan, with clear assignment of targeting and cover responsibilities within the package.

==== Push ====
Once the game plan is acknowledged and the push time arrives, the attacking element calls PUSHING with the TOT. The cover element acknowledges readiness with HOUNDDOG, indicating they are in position to employ if the primary attack fails.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Attacking Aircraft
|{Controller-CS} {CS} CAPTURED {Target Description or Bullseye} PUSHING TOT {Time}
|-
|Cover Aircraft
|{CS} HOUNDDOG
|}

==== Weapon Away ====
The attacking aircraft calls weapon employment with time of flight. If the weapon requires continued support such as laser designation or scanning, this is added as a fill-in.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Attacking Aircraft
|{Controller-CS} {CS} ONE WEAPON AWAY {Target Description} {Time of Flight} SECONDS {LASING / SCANNING if applicable}
|}

==== Assessment ====
The attacking aircraft calls the result. Two outcomes are possible:
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
| colspan="2" style="text-align:center;" |''Desired weapon effects generated''
|-
|Attacking Aircraft
|{Controller-CS} {CS} SPLASH {Target Description} SUCCESSFUL
|-
| colspan="2" style="text-align:center;" |''Desired weapon effects not generated''
|-
|Attacking Aircraft
|{Controller-CS} {CS} SPLASH {Target Description} FUMBLE {CLEAN / HIT}
|}
FUMBLE CLEAN indicates no visible battle damage and no weapon impact noted. FUMBLE HIT indicates weapon impact was noted within a lethal distance but desired effects were not generated.

==== Reattack ====
If the primary attack results in FUMBLE, the cover element is directed to reattack.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|FL
|''(intraflight) {CS} COVER {Target Description or Bullseye} · {Cover CS} PUSH''
|-
|Cover Aircraft
|{Controller-CS} {CS} PUSHING TOT {Time}
|-
|Cover Aircraft
|{Controller-CS} {CS} ONE WEAPON AWAY {Time of Flight} SECONDS
|-
|Cover Aircraft
|{Controller-CS} {CS} SPLASH {Target Description} {SUCCESSFUL / FUMBLE}
|}

==== Egress ====
Following the attack, the flight egresses using one of three calls depending on the situation:
{| class="wikitable" style="width:100%;"
!Call
!Condition
!Phrase
|-
|'''MILLER TIME'''
|Last striker in the package has completed the attack
|{Controller-CS} {CS} MILLER TIME
|-
|'''BUGOUT'''
|Aircraft has completed its attack and has no intention to return
|{Controller-CS} {CS} BUGOUT {Direction}
|-
|'''OFF'''
|Aircraft has completed its attack and is repositioning or egressing within the area
|{Controller-CS} {CS} OFF {Direction}
|}

==== Full Strike Example ====
''(intraflight) SHADOW FLIGHT STANDBY GAME PLAN''
''(intraflight) #2 · #3 · #4''
''(intraflight) SHADOW FLIGHT, #1 AND #2 TARGET CONVOY BULLSEYE 0-3-0/15 · #3 AND #4 COVER''
''(intraflight) #2 · #3 · #4''

SHADOW11 CAPTURED BULLSEYE 0-3-0/15 PUSHING TOT 21:21:15
''(intraflight) SHADOW13 HOUNDDOG''

SHADOW12 ONE WEAPON AWAY CONVOY BULLSEYE 0-3-0/15 THIRTY SECONDS LASING

SHADOW11 SPLASH CONVOY BULLSEYE 0-3-0/15 FUMBLE HIT
''(intraflight) SHADOW11 COVER BULLSEYE 0-3-0/15 · SHADOW13 PUSH''

SHADOW13 PUSHING TOT 21:23:50
SHADOW13 ONE WEAPON AWAY FORTY SECONDS

SHADOW13 SPLASH CONVOY BULLSEYE 0-3-0/15 SUCCESSFUL
SHADOW11 MILLER TIME
----

=== CAS ===
''Content to be added.''
----

=== SEAD ===
Suppression of Enemy Air Defenses (SEAD) is the action taken to neutralize, destroy, or temporarily degrade surface-to-air missile systems and associated radar emitters. Its purpose is to allow other aircraft to operate within a threat environment that would otherwise deny or restrict their access.

==== The SEAD Game Plan ====
SEAD is not a reactive afterthought — it is a pre-planned, coordinated element of every strike package that operates in a contested environment. Before the mission, the SEAD lead establishes contracts with the rest of the package: who responds to which threat, in what priority order, with which weapon, and under what conditions.

The underlying logic of SEAD is straightforward. A SAM battery that is actively radiating is vulnerable to antiradiation missiles. A SAM battery that goes silent to avoid being targeted is temporarily suppressed and cannot engage aircraft. Either outcome — destruction or suppression — achieves the mission objective of protecting the strike package.

SEAD aircraft therefore have two primary tools:

* '''Hard kill''' — employment of an antiradiation missile (ARM) against a radiating threat. The ARM homes on the radar emission. If the radar goes silent the missile loses guidance, so the threat must be forced to stay radiating or be caught radiating.
* '''Soft kill''' — electromagnetic jamming (CANYON) that degrades the threat radar's ability to track or guide a missile without destroying the system.

The decision between hard and soft kill, and between SNIPER (range-known) and SLAPSHOT (range-unknown, immediate), is made based on the quality of targeting data available and the urgency of the situation.

==== Threat Reaction and SEAD Response Contracts ====
When a friendly aircraft calls DEFENDING, SEAD aircraft respond with one of the following:
{| class="wikitable" style="width:100%;"
!Response
!Definition (ATP 1-02.1)
!Meaning
|-
|'''HARM INBOUND'''
|[A/S] [EW] High-speed antiradiation missile already employed
|ARM is already in the air — the threat is being engaged
|-
|'''MAGNUM'''
|[A/S] [EW] Launch of FRIENDLY antiradiation missile
|ARM is being launched now in response to this call
|-
|'''ARIZONA'''
|[A/S] [EW] No antiradiation missile ordnance remaining
|SEAD aircraft is Winchester on ARMs
|}
These responses must be pre-briefed as contracts. Every aircraft in the package needs to know which SEAD asset covers which threat axis, what the response will be, and what to do if the SEAD asset is ARIZONA or unable to respond.

==== SNIPER and SLAPSHOT ====
Two directive calls are used to order ARM employment:

'''SNIPER''' — directive call to employ an antiradiation missile against a range-known threat. Used when targeting data is of sufficient quality to give a precise location.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|SEAD Lead
|{CS} SNIPER {Threat Type} BULLSEYE {Bearing/Range}
|-
|SEAD Aircraft
|{CS} MAGNUM {Threat Type} BULLSEYE {Bearing/Range}
|}
'''SLAPSHOT''' — directive call to immediately employ the best available antiradiation missile against a specified threat at the specified bearing. Range is unknown. Used when a threat is actively engaging friendly aircraft and there is no time to refine targeting data.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|SEAD Lead
|{CS} SLAPSHOT {Threat Type} BEARING {Bearing}
|-
|SEAD Aircraft
|{CS} HARM INBOUND
|}
The distinction matters: SNIPER is deliberate and precise, SLAPSHOT is immediate and azimuth-only. A SLAPSHOT ARM may not hit the radar if it goes silent, but it forces the threat to shut down or risk destruction — either outcome protects the package.

== 09 / Brevity Words ==

=== Situational Awareness ===
{| class="wikitable" style="width:100%;"
!Term
!Definition
|-
|'''ALPHA CHECK'''
|Verification of ownship position relative to BULLSEYE. Used at check-in to confirm navigation accuracy. ALPHA CHECK correlation is defined as within 3 nm.
|-
|'''ANGELS'''
|Height of friendly aircraft in thousands of feet MSL (e.g., ANGELS TWENTY = 20,000 ft).
|-
|'''BOGEY DOPE'''
|Request for BRAA information on the indicated or nearest GROUP. Does not imply targeting.
|-
|'''BRAA'''
|Bearing, Range, Altitude, and Aspect relative to the specified friendly aircraft.
|-
|'''BULLSEYE'''
|A pre-briefed reference point from which the position of an object is referred to by magnetic bearing and range in nm. Not to be truncated to "BULL."
|-
|'''CLEAN'''
|1. No sensor information on a GROUP of interest.
2. No visible battle damage.
3. Aircraft not carrying external stores.
|-
|'''CLARA'''
|Radar scope is clear of contacts.
|-
|'''CONTACT'''
|Individual radar return within a GROUP.
|-
|'''FADED'''
|A previously tracked GROUP not updated by sensors for 30 seconds. Last known position implied.
|-
|'''GROUP'''
|Any number of air contacts within 3 nm in azimuth and range of each other.
|-
|'''HEAVY'''
|A GROUP known to contain three or more contacts.
|-
|'''JUDY'''
|Aircrew has taken control of the intercept and requires only situational awareness information. Controller minimizes transmissions.
|-
|'''MERGED'''
|Friendlies and targets have arrived in the visual arena, within 3–5 nm.
|-
|'''MONITOR'''
|Maintain sensor awareness on a specified GROUP or object. Implies tactically significant changes will be communicated.
|-
|'''NEGATIVE CONTACT'''
|Used for friendly aircraft not held on sensors. FADED is not used for friendlies.
|-
|'''NO JOY'''
|No visual contact with the target or bandit.
|-
|'''PICTURE'''
|Request for a description of all GROUPs and their spatial relationships in BULLSEYE format.
|-
|'''PLAYTIME'''
|Time aircraft can remain on station, given in hours plus minutes (e.g., ONE PLUS THIRTY).
|-
|'''TALLY'''
|Visual sighting of a target or enemy aircraft.
|-
|'''VANISHED'''
|A FADED GROUP correlated to a successful friendly shot. Assessed as killed.
|-
|'''VISUAL'''
|Visual sighting of a friendly aircraft, ground unit, or ship.
|}

=== Contact Status and Declaration ===
{| class="wikitable" style="width:100%;"
!Term
!Definition
|-
|'''BANDIT'''
|Positively identified as enemy IAW theater ID criteria. Does not imply authority to engage.
|-
|'''BOGEY'''
|Contact whose identity is unknown.
|-
|'''DECLARE'''
|Inquiry as to the identity of a specified track or GROUP. Responses include: FRIENDLY, BOGEY, BANDIT, HOSTILE, NEUTRAL, UNABLE, CLEAN, or FURBALL. Full positional data (BULLSEYE) must accompany responses.
|-
|'''FRIENDLY'''
|Positively identified friendly aircraft, ship, or ground position.
|-
|'''FURBALL'''
|Non-friendly and friendly aircraft within 5 nm of each other. May be a response to a DECLARE request.
|-
|'''HIGH'''
|Contact is above 40,000 ft MSL.
|-
|'''HOSTILE'''
|Contact identified as enemy upon which clearance to fire is authorized IAW ROE.
|-
|'''NEUTRAL'''
|Positively identified aircraft whose characteristics indicate it is neither supporting nor opposing friendly forces.
|-
|'''OUTLAW'''
|Contact originating from a known or suspected hostile airfield or area.
|-
|'''SPADES'''
|Contact returns no or invalid IFF response on interrogation.
|-
|'''FAST'''
|Target speed 660–900 knots ground speed or Mach 1.1–1.5.
|-
|'''VERY FAST'''
|Target speed above 900 knots or Mach 1.5.
|}

=== Picture Labels ===
{| class="wikitable" style="width:100%;"
!Term
!Definition
|-
|'''AZIMUTH'''
|Two GROUPs separated laterally at approximately the same range from the fighters. Named by cardinal directions (e.g., NORTH GROUP, SOUTH GROUP).
|-
|'''RANGE'''
|Two GROUPs separated in depth along the threat axis. Named LEAD GROUP and TRAIL GROUP.
|-
|'''WALL'''
|Three or more GROUPs separated in azimuth with depth ≤5 nm or closing. Outer GROUPs named by cardinal directions; inner GROUPs named MIDDLE GROUP.
|-
|'''CHAMPAGNE'''
|Three GROUPs with two closest to fighters in azimuth and one in trail. LEAD GROUPs named with cardinal direction; TRAIL GROUP in range.
|-
|'''VIC'''
|Three GROUPs with one closest to fighters and two in trail separated in azimuth. LEAD GROUP closest; TRAIL GROUPs named with cardinal direction.
|-
|'''BOX'''
|Four GROUPs with two in azimuth closest to fighters and two in azimuth farthest. Named LEAD GROUP (cardinal) and TRAIL GROUP (cardinal).
|-
|'''LADDER'''
|Three or more GROUPs separated in range. Named LEAD GROUP, MIDDLE GROUP (or SECOND, THIRD), TRAIL GROUP.
|-
|'''STACK'''
|Two or more contacts in a GROUP with ≥10,000 ft altitude separation. Higher altitude stated first.
|-
|'''LEADING EDGE'''
|The GROUPs the fighters expect to target in the upcoming intercept. Follow-on GROUPs are communicated as WAVES (SECOND WAVE, THIRD WAVE, etc.).
|-
|'''NEW PICTURE'''
|Tactical picture has changed. Supersedes all previous calls and reestablishes the picture for all players.
|-
|'''ADDITIONAL GROUP'''
|Newly detected GROUP outside targeting range that does not fit the current picture label.
|-
|'''POP-UP GROUP'''
|Previously undetected GROUP appearing inside targeting range but outside THREAT range.
|-
|'''THREAT GROUP'''
|Undetected or unreported GROUP meeting briefed THREAT criteria. Communicated in BRAA format to the closest aircraft.
|-
|'''OPENING'''
|Distance between GROUPs is increasing.
|-
|'''CLOSING'''
|Distance between GROUPs is decreasing.
|-
|'''WEIGHTED'''
|Picture with three or more GROUPs where one or more GROUPs are offset from an equidistant arrangement. Accompanied by cardinal direction.
|-
|'''ECHELON'''
|GROUPs in a traditional label that are not directly in azimuth or range with one another. Accompanied by cardinal direction.
|-
|'''PASSING'''
|Two named GROUPs with a RANGE relationship maneuvering to opposite sides in a RANGE relationship.
|-
|'''CROSSING'''
|Two GROUPs with an AZIMUTH relationship maneuvering to opposite sides in an AZIMUTH relationship.
|-
|'''JOINED'''
|Two or more named GROUPs maneuver to meet and maintain GROUP criteria.
|-
|'''UNTARGETED'''
|A GROUP inside targeting range with no assigned fighter. Used by the controller to flag priority GROUPs at risk.
|}

=== Targeting and Responsibility ===
{| class="wikitable" style="width:100%;"
!Term
!Definition
|-
|'''COMMIT'''
|Directive to move to intercept or engage a specified GROUP.
|-
|'''TARGET'''
|Assignment of targeting responsibility for a specific GROUP to a flight or section.
|-
|'''TARGETED'''
|Fighter has acquired the assigned GROUP and assumed responsibility for it.
|-
|'''UNTARGETED'''
|GROUP inside targeting range with no fighter assigned.
|-
|'''DROPPING'''
|Stop monitoring a specified GROUP or emitter and resume search responsibilities.
|-
|'''RESET'''
|Proceed to prebriefed position or area of operations. Implies DROPPING and return of targeting responsibility.
|-
|'''MELD'''
|Shift radar responsibilities from airspace sanitization to gaining situational awareness on the assigned GROUP.
|-
|'''SORTED'''
|Sort responsibility within a GROUP has been met by the calling fighter.
|-
|'''ANCHORED'''
|Turning engagement at the specified location. Fighter is engaged and not flowing.
|-
|'''SEPARATION'''
|Request or information call stating the distance in nm between two GROUPs or WAVES.
|-
|'''LANE CROSSER'''
|A GROUP that maneuvers into a different area of targeting responsibility.
|-
|'''LANE RIDER'''
|A GROUP that maintains a track direction on or near the boundary between targeting areas.
|}

=== Employment ===
{| class="wikitable" style="width:100%;"
!Term
!Definition
|-
|'''ENGAGE'''
|Directive to fire on a designated target.
|-
|'''FOX ONE'''
|Semi-active radar-guided missile fired.
|-
|'''FOX TWO'''
|Infrared-guided missile fired.
|-
|'''FOX THREE'''
|Active radar-guided missile fired.
|-
|'''SPLASH'''
|Missile has impacted. Target is assessed as destroyed.
|-
|'''SNAPLOCK'''
|Fighter has gained sensor contact to a GROUP inside THREAT range with BEAM or hotter aspect. BRAA and aspect implied.
|-
|'''SPIKED'''
|Fighter is being painted by an airborne radar. Called with bearing or cardinal direction.
|-
|'''MUSIC'''
|Fighter is experiencing radar electromagnetic deceptive jamming from a GROUP.
|-
|'''PRESS'''
|Requested action is approved and mutual support will be maintained. Assumes VISUAL.
|-
|'''BANZAI'''
|Execute launch-and-decide tactics with intent to maneuver into the visual arena.
|-
|'''SKATE'''
|Execute launch-and-leave tactics.
|-
|'''DEFEND(ING)'''
|Fighter is maneuvering defensively against a threat. Called with cardinal direction of defensive turn.
|}

=== Maneuver and Flow ===
{| class="wikitable" style="width:100%;"
!Term
!Definition
|-
|'''BREAK'''
|(Direction) Immediate maximum-performance turn. Safety of flight or to defeat a weapons solution.
|-
|'''BUSTER'''
|Fly at maximum continuous speed without afterburner (military power).
|-
|'''GATE'''
|Fly as fast as possible; use afterburner.
|-
|'''FLOW COLD'''
|Initiate a turn away from the anticipated threat; begin COLD operations.
|-
|'''IN'''
|Informative call that the fighter is turning toward the threat or target.
|-
|'''OUT'''
|Informative call that the fighter is turning away from the threat.
|-
|'''CRANK'''
|Maneuver in the indicated direction while maintaining radar contact on the bandit at the radar gimbal limit. Reduces closure rate while sustaining illumination.
|-
|'''NOTCH'''
|Maneuver to place a radar-guided threat on the beam to defeat its Doppler filter.
|-
|'''TRESPASS'''
|Aircraft has entered a known or pop-up SAM MEZ. Directive call to snap 180 degrees away.
|-
|'''HARD'''
|High-G-force, energy sustaining turn in the indicated direction (default is a 180-degree turn).
|}

=== COMPLETION and ABORT ===
{| class="wikitable" style="width:100%;"
|'''MILLER TIME'''
|Last striker in the package has completed the attack
|{Controller-CS} {CS} MILLER TIME
|-
|'''BUGOUT'''
|Aircraft has completed its attack and has no intention to return
|{Controller-CS} {CS} BUGOUT {Direction}
|-
|'''OFF'''
|Aircraft has completed its attack and is repositioning or egressing within the area
|{Controller-CS} {CS} OFF {Direction}
|}
=== AIR TO SURFACE ===
{| class="wikitable" style="width:100%;"
!Term
!Definition
!
|-
|'''DIRT'''
|Radar warning receiver indication of a surface threat in search mode. The threat is radiating but has not yet established a track.
|
|-
|'''MUD'''
|Radar warning receiver indication of a surface threat in track mode. The threat has established a track on the aircraft.
|
|-
|'''SINGER'''
|Radar warning receiver indication of a SAM launch. The threat has fired.
|
|-
|'''SCAN'''
|Search the indicated sector and report any contacts.
|
|-
|'''WORK'''
|Directive call to conduct geolocation on a specific target or area.
|
|-
|'''INVESTIGATE'''
|Verify specified elements of ROE, positive identification (PID), and coordination of forces on the referenced target or track.
|
|-
|'''FIXED'''
|Target has been located and its position established. Followed by accuracy qualifier: LOW ACCURACY (inside 1 nm) or HIGH ACCURACY (inside 1,000 ft).
|
|-
|'''MONITOR'''
|Maintain sensor awareness on a specified GROUP or object. Implies tactically significant changes will be communicated.
|
|-
|'''TRACK'''
|Directive call assigning responsibility to an asset for maintaining sensor or visual observation of a defined object or area.
|
|-
|'''CAPTURED'''
|Object has been acquired and is being actively tracked.
|
|-
|'''COVER'''
|Directive call to be ready for reattack or re-engage if weapon effects are not achieved.
|
|-
|'''HOUNDDOG'''
|Aircraft is in a position to employ weapons. Used in response to COVER.
|
|-
|'''HARM INBOUND'''
|[A/S] [EW] High-speed antiradiation missile already employed
|ARM is already in the air — the threat is being engaged
|-
|'''MAGNUM'''
|[A/S] [EW] Launch of FRIENDLY antiradiation missile
|ARM is being launched now in response to this call
|-
|'''ARIZONA'''
|[A/S] [EW] No antiradiation missile ordnance remaining
|SEAD aircraft is Winchester on ARMs
|}
=== Status and Administrative ===
{| class="wikitable" style="width:100%;"
!Term
!Definition
|-
|'''AS FRAGGED'''
|Unit will perform exactly as briefed or scheduled per the ATO.
|-
|'''WITH EXCEPTIONS'''
|Unit will perform as briefed with stated deviations.
|-
|'''AUTHENTICATE'''
|Request to verify contact with an allied unit using the DRYAD table.
|-
|'''BLIND'''
|No visual contact with a friendly aircraft.
|-
|'''FENCE IN / OUT'''
|Perform the combat configuration checklist entering or exiting the hostile area.
|-
|'''LOWDOWN'''
|Request for the current tactical electromagnetic support or ground/surface picture.
|-
|'''ROLEX'''
|Timeline adjustment in minutes from original planned execution time. PLUS assumed. Not additive.
|-
|'''SLIP'''
|Time delay to an individual flight or element event. Not additive.
|-
|'''UNABLE'''
|Cannot comply as requested or directed.
|}

Guides/New Member Guide

2026-05-23T11:35:03Z

Niknam3: /* The Training Server */

= New Members Guide =

Welcome to the group! This page gives you a quick overview of how things work, where to find information, and what you need to get started. Feel free to jump to whichever section is most relevant to you.

__TOC__

== Getting Set Up ==

Before joining the server or attending any events, make sure you have the required mods and SRS installed and configured.

* '''Required Mods:''' [[Guides/Mod Installation|→ Mod Installation Guide]]
* '''SRS:''' [[Guides/SRS Setup|→ SRS Installation & Setup Guide]]

== The Training Server ==

Our training server is the place to practice, familiarise yourself with procedures, and find official documentation. SOPs — including the LTAG SOPs — are available directly on the server.

=== THEATER ===
The Current Training Theater is Set in Syria. Our homebase is Incirlik AB. Here you can find the Airport SOP's: [[Incirlic Air Base|Incirlic AB]]

=== Flight Plans ===

Whenever the server is controlled, file a flight plan.

* [[DDFORM175|→ How to File a Flight Plan]]

== Missions & Briefings ==

Mission briefings are hosted on the ATO Brief website. Before any event, check there for the current ATO, tasking, and relevant mission information.

* [https://ato.sourcedcs.page → ATO Brief]

Make sure you have read the briefing before joining the server for an event.

== TRAINING ==
You can track your training on our training Page

* [https://sourcedcs.page/skills.html Training Overview]

== Weekly Events ==

We run events on a weekly basis. All events are announced in Discord.

* To sign up, click '''Interested''' on the Discord event post.
* If you can no longer make it, '''text someone''' to let the team know in advance — don't just not show up.

== Where to Find Help ==

If you have questions not covered here, the best place to ask is in the relevant Discord channel. If you're unsure who to contact, reach out to any of the staff members — someone will point you in the right direction.

[[Category:Guides]]
[[Category:Onboarding]]

Main Page

2026-05-23T11:32:37Z

Niknam3:

__NOTOC__
__NOEDITSECTION__


<div style="border:1px solid #c8c5bf; padding:48px 32px 36px 32px; margin-bottom:32px; text-align:center;">
<div style="font-size:0.6rem; letter-spacing:5px; color:#9a9690; margin-bottom:20px;">■■■ UNCLASSIFIED — FOR SOURCE MEMBERS ONLY ■■■</div>
<div style="border-top:1px solid #c8c5bf; max-width:200px; margin:0 auto 24px auto;"></div>
[[File:Sourcelogosmall.png|100px|center|link=]]
<div style="font-size:1.6rem; font-weight:600; letter-spacing:8px; margin:20px 0 8px 0;">SOURCE DCS</div>
<div style="font-size:0.72rem; letter-spacing:4px; color:#4a4845; margin-bottom:20px;">SHADOW OPERATIONS - UNDERSTANDING REAL COMBAT ENVIRONMENTS</div>
<div style="border-top:1px solid #c8c5bf; max-width:200px; margin:0 auto 16px auto;"></div>
<div style="font-size:0.62rem; letter-spacing:2px; color:#9a9690;">
CURRENT THEATER: SYRIA -
[[Server Info/Airfields|AIRFIELDS]]
</div>
</div>

----

== 01 / Personnel Onboarding ==

New to SOURCE? Complete all onboarding steps before your first operation. Install required software, read the rules of engagement, and familiarise yourself with communications procedures.

[[Guides/New Member Guide|New Member Guide]] · [[Guides/SRS Setup|SRS Setup]] · [[Guides/Mod Installation|Mod Installation]]

== 02 / General Knowledge ==
Contains all the Knowledge about the threats we could Face along with tactics to evade an neutralize.

[[SAM Surface to Air Missile]]

----

== 03 / multi-Service tactics, techniques, and procedures (MTTP) ==

All personnel are expected to operate within SOURCE standard communications procedures. This includes tactical brevity, ATC phraseology, and carrier comms.

'''IN CASE OF DOUBT USE PLAIN LANGUAGE'''

=== Communication ===
[[General/Tactical Communication|Tactical Communication]] · [[General/CATC Communications Guide|CATC Communications Guide]] · [[General/Air Traffic Communication|Operating within Civil Airspace]] · [[DDFORM1801|Filing Flight Plans]] · [[How To Read Charts]]

=== TACTICS ===

==== BVR ====

==== A2S ====
For Unit-Specific Procedures reference ASSIGNED UNITS below

----

== 04 / Assigned Units ==

{| class="wikitable" style="width:100%;"
|-
! Squadron !! Aircraft
|-
| [[Squadrons/78th VMRS Shadow Knights|78th VMRS Shadow Knights]] || F-16C Viper
|-
| [[Squadrons/14th VSFS Top Hatters|14th VSFS Top Hatters]] || F/A-18C Hornet
|-
| [[Squadrons/509th VSFS Black Anvils|509th VSFS Black Anvils]] || F-15E Strike Eagle
|}

----

== 05 / Active Operations ==

Current campaign briefings, mission assignments, and sortie records are maintained in the operations section. All flight leads are responsible for keeping mission pages up to date following each operation.

[[Campaigns|View All Campaigns]]

Main Page

2026-05-23T11:32:26Z

Niknam3:

__NOTOC__
__NOEDITSECTION__


<div style="border:1px solid #c8c5bf; padding:48px 32px 36px 32px; margin-bottom:32px; text-align:center;">
<div style="font-size:0.6rem; letter-spacing:5px; color:#9a9690; margin-bottom:20px;">■■■ UNCLASSIFIED — FOR SOURCE MEMBERS ONLY ■■■</div>
<div style="border-top:1px solid #c8c5bf; max-width:200px; margin:0 auto 24px auto;"></div>
[[File:Sourcelogosmall.png|100px|center|link=]]
<div style="font-size:1.6rem; font-weight:600; letter-spacing:8px; margin:20px 0 8px 0;">SOURCE DCS</div>
<div style="font-size:0.72rem; letter-spacing:4px; color:#4a4845; margin-bottom:20px;">SHADOW OPERATIONS - UNDERSTANDING REAL COMBAT ENVIRONMENTS</div>
<div style="border-top:1px solid #c8c5bf; max-width:200px; margin:0 auto 16px auto;"></div>
<div style="font-size:0.62rem; letter-spacing:2px; color:#9a9690;">
CURRENT THEATER: SYRIA -
[[Server Info/Airfields|AIRFIELDS]]
</div>
</div>

----

== 01 / Personnel Onboarding ==

New to SOURCE? Complete all onboarding steps before your first operation. Install required software, read the rules of engagement, and familiarise yourself with communications procedures.

[[Guides/New Member Guide|New Member Guide]] · [[Guides/SRS Setup|SRS Setup]] · [[Guides/Mod Installation|Mod Installation]]

== 02 / General Knowledge ==
Contains all the Knowledge about the threats we could Face along with tactics to evade an neutralize.

[[SAM Surface to Air Missile]]

----

== 03 / multi-Service tactics, techniques, and procedures (MTTP) ==

All personnel are expected to operate within SOURCE standard communications procedures. This includes tactical brevity, ATC phraseology, and carrier comms.

'''IN CASE OF DOUBT USE PLAIN LANGUAGE'''

=== Communication ===
[[General/Tactical Communication|Tactical Communication]] · [[General/CATC Communications Guide|CATC Communications Guide]] · [[General/Air Traffic Communication|Operating within Civil Airspace]] · [[DDFORM1801|Filing Flight Plans]] · [[How To Read Charts]]

=== TACTICS ===

==== BVR ====

==== BSA ====
For Unit-Specific Procedures reference ASSIGNED UNITS below

----

== 04 / Assigned Units ==

{| class="wikitable" style="width:100%;"
|-
! Squadron !! Aircraft
|-
| [[Squadrons/78th VMRS Shadow Knights|78th VMRS Shadow Knights]] || F-16C Viper
|-
| [[Squadrons/14th VSFS Top Hatters|14th VSFS Top Hatters]] || F/A-18C Hornet
|-
| [[Squadrons/509th VSFS Black Anvils|509th VSFS Black Anvils]] || F-15E Strike Eagle
|}

----

== 05 / Active Operations ==

Current campaign briefings, mission assignments, and sortie records are maintained in the operations section. All flight leads are responsible for keeping mission pages up to date following each operation.

[[Campaigns|View All Campaigns]]