Toggle menu
16
49
31
431
SOURCE DCS WIKI
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

General/Tactical Communication Revision 1: Difference between revisions

From SOURCE DCS WIKI
Niknam3 (talk | contribs)
Created page with "<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 i..."
 
Niknam3 (talk | contribs)
 
(17 intermediate revisions by the same user not shown)
Line 31: Line 31:
'''Informative''' — provides information without requiring a response; format is [speaking entity].
'''Informative''' — provides information without requiring a response; format is [speaking entity].
   EAGLE 11, FUEL YELLOW.
   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 or TL (due to missing personal)
----
----


Line 55: Line 67:


=== BRAA and BULLSEYE CallS ===
=== 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, BRAA, SNAPLOCK, and THREAT 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%;"
{| class="wikitable" style="width:100%;"
!Format
!Format
!Bearing
!Bearing
!Range
!Range (nm)
!Altitude
!Altitude (ft)
!Aspect
!Aspect
!Declaration
|-
|-
|BRAA
|BRAA
|320
|3 2 0
|30 nm
|30
|20,000 ft
|20 thousand
|Flanking
|Flanking
|BOGEY
|-
|BULLSEYE
|1 1 0
|30
|25 thousand
|HOT
|}
|}


=== Flight Check / Frequency Change ===
=== 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%;"
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
! style="width:25%;" |Station
Line 78: Line 97:
|-
|-
|Controller
|Controller
|{CS} Push Button _
|{CS} Push Button #
|-
|-
|Flight Lead (interflight)
|FL
|{CS} Push Button _
|{CS} Push Button #
|-
|-
|Flight Lead (intraflight)
|''FL (intraflight)''
|Push {UHF/VHF, Radio 1/2} Button _
|''Flight Push {UHF/VHF, Radio 1/2} Button #''
|-
|-
| colspan="2" style="text-align:center;" |''All flight members switch''
| colspan="2" style="text-align:center;" |''All flight members switch to the new Frequency''
|-
|-
|Flight Lead
|FL
|{CS} Check
|{CS} Check
|-
|-
|Wingman
|WM
|2
|2
|-
|-
|Element Lead
|EL
|3
|3
|-
|-
|Element Wingman
|2nd WM
|4
|4
|}
|}
Line 107: Line 126:
!Phrase
!Phrase
|-
|-
|Pilot
|FL
|{Controller-CS} {CS} Authenticate E-A
|{TACC2-CS} {CS} Authenticate E-A
|-
|-
|Controller
|TACC2
|Come back G
|Come back G
|-
|-
|Controller
|TACC2
|Authenticate J-U
|Authenticate J-U
|-
|-
|Pilot
|FL
|Come back R
|Come back R
|-
|-
|Controller
|TACC2
|Good Authentication
|Authentication Sweet
|}
|}


Line 126: Line 145:
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.
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, WORDS verification, and weather update.
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.
Note: BULLSEYE cannot be used for initial position calls — only valid after ALPHA CHECK.


=== Check In ON TACC2 NET (MNPOPCA Format) ===
=== Check In ON TACC2 NET (MNPOPCA Format) ===
Full check-in includes: Mission number, Number and type of aircraft, Position and altitude, Ordnance, Playtime, Capabilities, Abort code.
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
|}


If a flight is as FRAGGED an abbreviated Check-in should be used
==== Check in AS FRAGGED ====
{| class="wikitable" style="width:100%;"
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
! style="width:25%;" |Station
Line 140: Line 174:
| colspan="2" style="text-align:center;" |''Flight Check, then Authentication''
| colspan="2" style="text-align:center;" |''Flight Check, then Authentication''
|-
|-
|Flight Lead
|FL
|{Controller-CS} {CS} Mission Nr {MSN} {Position} {Altitude} {Playtime} {AS FRAGGED / WITH EXCEPTIONS} Request Alpha Check from Bullseye
|{Controller-CS} {CS} as Fragged, Request Alpha Check from Bullseye
|-
|-
|Controller
|Controller
|{CS}, Identified Alpha Check Bullseye {Position}
|{CS}, Identified, {Control Type}, Alpha Check Bullseye {Position}
|-
|-
|Flight Lead
|FL
|Same {Alpha Check}
|{CS}
|}
|}
If a flight is as FRAGGED an abbreviated Check-in should be used
 
==== Check in WITH EXCEPTIONS ====
{| class="wikitable" style="width:100%;"
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
! style="width:25%;" |Station
Line 156: Line 191:
| colspan="2" style="text-align:center;" |''Flight Check, then Authentication''
| colspan="2" style="text-align:center;" |''Flight Check, then Authentication''
|-
|-
|Flight Lead
|FL
|{Controller-CS} {CS} as Fragged, Request Alpha Check from Bullseye
|{Controller-CS} {CS} Mission Nr #-#-#-# Checking in with Exceptions. Request Alpha Check Bullseye
|-
|-
|Controller
|TACC2
|{CS}, Identified, {Control Type}, Alpha Check Bullseye {Position}
|{CS}, Alpha Check Bullseye {Position} continue with Check In
|-
|-
|Flight Lead
|FL
|Same {Alpha Check}
|{CS} {State Exceptions in plain Language}
|}
|}
If deviations exist from the tasked plan, check in WITH EXCEPTIONS and state the deviation:
  EXXON 1, MISSION NUMBER 6-1-1-1, CHECKING IN WITH EXCEPTIONS. (State Exceptions in plain langue)
----
----


== 04 / Force Packaging ==
== 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 ===
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.
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.
   PACKAGE BRAVO WHISKEY, ROLL CALL.
   MC:      PACKAGE BRAVO WHISKEY, ROLL CALL.
   EAGLE. VIPER WITH EXCEPTIONS. BONES. GROWL. MOJO.
   FLs:      EAGLE. VIPER WITH EXCEPTIONS. BONES. GROWL. MOJO.
   VIPER, GO WITH EXCEPTIONS.
   MC:      VIPER, GO WITH EXCEPTIONS.
   VIPER MINUS 2.
   VIPER FL: VIPER MINUS 2.
 
 
=== Timing Changes ===
=== Timing Changes ===
'''ROLEX''' — timeline adjustment in minutes, always referenced from the original preplanned mission execution time. PLUS is assumed. Not additive.
'''ROLEX''' — timeline adjustment in minutes, always referenced from the original preplanned mission execution time. PLUS is assumed. Not additive.
Line 187: Line 218:
----
----


== 05 / Formations ==
== 06 / Air-to-Air Refueling ==
 
AAR requires close coordination with the tanker around a pre-briefed Rendezvous (RV). SOURCE uses '''RV Alpha (Fixed Anchor)''' for all operations. (due to DCS limitations)
=== Formation Splits ===
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Flight Lead
|{CS}, request split into {number} parts of {number} each
|-
|Controller
|{CS}, report ready for {Right / Left Hand} {Split Type}
|}
 
==== Vertical (Altitude) ====
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Flight Lead
|{CS}, ready
|-
|Controller
|{CS 2}, descend {FL}
|-
|Flight Lead 2
|{CS 2}, descending {FL}
|-
|Controller
|{CS 2}, squawk {number}, identified
|-
| colspan="2" style="text-align:center;" |''Repeat for each new flight''
|}
 
==== Lateral (Vector) ====
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Flight Lead
|{CS}, ready
|-
|Controller
|{CS 2} for split turn {side} {degrees}
|-
|Flight Lead
|{CS 2} for split turn {side} {degrees}
|-
|Controller
|{CS 2} squawk {number}, identified
|-
| colspan="2" style="text-align:center;" |''Repeat for each new flight''
|}
 
=== Join-Up ===
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Flight Lead
|{CS} requesting join-up with {CS 2}
|-
|Controller
|{CS 2}, confirm join-up clearance for {CS}
|-
|Flight Lead 2
|{CS 2}, {CS} is cleared to join up
|-
|Controller
|{CS}, fly {heading} and climb/descend to {angels}
|-
|Controller
|{CS}, report {CS 2} in sight
|-
|Flight Lead
|{CS}, {CS 2} in sight, {position}
|-
|Controller
|Visual join-up approved, report formation tight
|-
|Flight Lead 2
|{CS 2}, formation tight
|-
|Controller
|{CS 2} adopt callsign {new CS}
|}
----
 
== 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 ===
=== Tanker Orbit Stack ===
Line 282: Line 225:
!Level
!Level
!Usage
!Usage
!ex.
|-
|-
|'''ALPHA'''
|'''ALPHA'''
|Receivers departing · Emergency
|Receivers departing · Emergency
|FL210
|-
|-
|'''BRAVO'''
|'''BRAVO'''
|Tanker base level
|Tanker base level
|FL200
|-
|-
|'''CHARLIE'''
|'''CHARLIE'''
|Receiver evasive
|Receiver evasive
|FL190
|-
|-
|'''DELTA'''
|'''DELTA'''
|Receivers approaching
|Receivers approaching
|FL180
|}
|}


Line 305: Line 253:
|{CS} Proceed Tanker BRAA {BRAA}, RV Alpha, Tanker Freq {Freq} {Instructions}
|{CS} Proceed Tanker BRAA {BRAA}, RV Alpha, Tanker Freq {Freq} {Instructions}
|-
|-
|Flight Lead
|FL
|{CS} Roger, RV Alpha, Tanker Freq {Freq} {Readback}
|{CS} Roger, RV Alpha, Tanker Freq {Freq} {Readback}
|-
|-
| colspan="2" style="text-align:center;" |''Once flight has radar contact with tanker''
| colspan="2" style="text-align:center;" |''Once flight has radar contact with tanker''
|-
|-
|Flight Lead
|FL
|{Flight Name} Judy 1, Weapons Safe
|{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''
| colspan="2" style="text-align:center;" |''Once tanker is in sight''
Line 321: Line 266:
|{CS} Tanker {x} o'clock, report visual
|{CS} Tanker {x} o'clock, report visual
|-
|-
|Flight Lead
|FL
|{CS} Nose Cold, visual with tanker
|{CS} Nose Cold, visual with tanker
|-
|-
Line 327: Line 272:
|{CS} Roger, contact boom
|{CS} Roger, contact boom
|-
|-
| colspan="2" style="text-align:center;" |''Switch to DCS tanker frequency''
| colspan="2" style="text-align:center;" |''Switch to DCS tanker frequency and join up''
|}
|}
Flight Lead must confirm Nose Cold with wingmen on intraflight before reporting to the controller.
FL must confirm Nose Cold / Weapons Safe with wingmen on intraflight before reporting to the controller.
----
----


== 07 / Positive Identification (PID) and CDE ==
== 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.
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%;"
{| class="wikitable" style="width:100%;"
Line 341: Line 286:
|IFF interrogation, data link picture, NCTR, controller declaration. Most common form in BVR.
|IFF interrogation, data link picture, NCTR, controller declaration. Most common form in BVR.
|-
|-
|'''Visual PID'''
|'''Visual PID (VID)'''
|Confirm number, type, livery, armament, heading, speed. Requires merge or VID pass.
|Confirm number, type, livery, armament, heading, speed. Requires merge or VID pass.
|-
|-
|'''Ground Targets'''
|'''Ground Targets'''
|Correlate with pre-briefed target. Controller issues Cleared to Engage before weapons release.
|Correlate with pre-briefed target.
|}
|}
----
----


== 08 / Air-to-Air Combat ==
== 08 / Air-to-Air Combat ==
Air combat is primarily carried out by CAP aircraft. The two main mission types are '''DCA''' (Defensive Counter Air) and '''OCA''' (Offensive Counter Air).
[[MTTP/A2A|Air to Air Communication Procedures]]
 
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.
 
The '''Targeting Range''' is the agreed distance at which all contacts must be intercepted. A GROUP inside targeting range with no assigned fighter is labelled '''UNTARGETED'''. The default TAC Range call is '''60 nm''' from the closest fighter to the closest GROUP.
 
=== Communication Cadence by Intercept Phase ===
{| 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
|}
 
=== Contact Declaration ===
{| 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, OUTLAW, or SPADES classification does not authorize engagement. Escalation to HOSTILE requires a controller DECLARE response or pre-briefed escalation criteria being met.
 
=== Phase 1 — Pre-Commit ===
The flight arrives at its prebriefed CAP position with FENCE IN complete and radars in sanitization configuration. The controller holds picture responsibility and uses BULLSEYE format.
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Flight Lead
|{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. If not yet met, the flight continues sanitizing and requests updated pictures as needed.
 
==== 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
|Anchored using BULLSEYE
|-
|'''POP-UP GROUP'''
|Previously undetected, appears inside targeting range but outside THREAT range
|Anchored using BULLSEYE
|-
|'''THREAT GROUP'''
|Undetected or unreported GROUP meeting briefed THREAT criteria
|BRAA format to the closest aircraft
|}
  DARKSTAR, FIRST 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.
 
=== Phase 2 — Commit ===
 
==== Fighter or MC/TL-Initiated ====
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
| colspan="2" style="text-align:center;" |''Commit criteria met''
|-
|Flight Lead
|{Controller-CS} {CS} RECOMMEND COMMIT {Group Label}
|-
|Controller
|{CS} COMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration} {Nr of Contacts}
|-
|Flight Lead
|COMMIT {Group Label} {CS}
|}
 
==== Controller-Initiated ====
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Controller
|{CS} COMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration} {Nr of Contacts}
|-
|Flight Lead
|{CS} COMMIT
|}
After COMMIT, fighters hold radio priority. The controller transitions to tactical or advisory control.
 
=== Phase 3 — Targeting and Declaration ===
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Flight Lead
|{Controller-CS} {CS} DECLARE {Group Label or Bullseye Position}
|-
|Controller
|{Group Label} DECLARED {HOSTILE / BOGEY / FRIENDLY / UNABLE / FURBALL}
|-
| colspan="2" style="text-align:center;" |''Flight lead assigns targeting responsibility and announces tactical plan (intraflight)''
|-
|Flight Lead
|''(intraflight) {CS} TARGET {Group Label} {Tactic}''
|-
| colspan="2" style="text-align:center;" |''Once group appears on radar''
|-
|Flight Lead
|{Controller-CS} {CS} TARGETED {Group Label} BULLSEYE {Bearing/Range}
|-
|Controller
|''No response required if information correlates. Controller responds comparatively if information does not correlate or requires correction.''
|}
A fighter that has called TARGETED indicates that fighter is maintaining awareness of and responsibility for the specified group. If DECLARE returns UNABLE or FURBALL, weapons employment is not authorized until classification is resolved.


=== Phase 4 — TAC Range, MELD, Sort, and JUDY ===
== 09 / Air-to-Surface Combat ==
{| class="wikitable" style="width:100%;"
[[MTTP/A2S|Air to Surface Communication Procedures]]
! style="width:25%;" |Station
!Phrase
|-
|Controller or Fighter
|{CS} {Group Label} TAC RANGE ''(called at 60 nm default)''
|-
|Flight Lead
|{Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" |''All flight members shift radars from sanitization to assigned group''
|-
|Flight Lead
|''(intraflight) FLIGHT SORT {Criteria}''
|-
|Wingmen
|''(intraflight) #2 SORTED · #3 SORTED · #4 SORTED''
|-
| colspan="2" style="text-align:center;" |''Once sort is complete and no further controller guidance is needed''
|-
|Flight Lead
|{Controller-CS} {CS} JUDY
|}
After JUDY the controller minimizes transmissions. The flight manages the intercept autonomously and requires only situational awareness information.
 
=== Phase 5 — Weapon Employment ===
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Flight Lead
|''(intraflight) {Wingman CS} ENGAGE''
|-
|Firing Aircraft
|{Controller-CS} {CS} FOX THREE {Group Label} {Contact Description} BULLSEYE {Bearing/Range} {Altitude}
|-
|Controller
|COPY SHOT
|}
Multiple shots in one transmission are acceptable.
 
If a fighter determines a GROUP HOSTILE and ROE has been met, the fighter may employ and include HOSTILE in the shot transmission:
  RAPTOR 1, FOX 3 LEAD GROUP BULLSEYE 1-2-5/27, TWENTY-NINE THOUSAND, HOSTILE.
 
=== Phase 6 — Out, Dropping, and Reset ===
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Flight Lead
|{Controller-CS} {CS} OUT {Direction} DROPPING {Group Label}
|-
| colspan="2" style="text-align:center;" |''Flight returns to sanitization radar settings. Controller resumes monitoring of dropped group.''
|-
| colspan="2" style="text-align:center;" |''Once weapon effects are assessed and the flight returns to prebriefed position''
|-
|Flight Lead
|{Controller-CS} {CS} RESET
|}
RESET implies DROPPING and returns all targeting responsibility to the controller.
 
Note: Targeting responsibility is also cancelled when a fighter communicates BLOWING THROUGH, SPITTER, or executes an OUT. The group should be treated as UNTARGETED if no fighter subsequently targets it.
 
=== Phase 7 — In (Follow-up Engagement) ===
If the tactic requires a follow-up shot rather than RESET:
{| class="wikitable" style="width:100%;"
! style="width:25%;" |Station
!Phrase
|-
|Flight Lead
|{Controller-CS} {CS} IN {Direction} TARGETED {Group Label}
|-
|Flight Lead
|{Controller-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" |''Re-sort as required, then proceed to Phase 5''
|}
 
=== COLD Operations ===
Fighters communicate COLD operations with FLOW COLD or FLOW with a cold heading:
  EAGLE, FLOW COLD.  or  EAGLE, FLOW 0-9-0.
During COLD operations the controller will voice RANGE BACK — the distance from the closest friendly aircraft to the closest GROUP measured parallel to the fight axis.
  DICE 4, FOCUS, RANGE BACK THIRTY-FIVE ADDITIONAL GROUP.
 
=== THREAT Call ===
If a fighter will pierce THREAT range to an untargeted GROUP, a THREAT call is made using BRAA format. Default THREAT criteria is 35 nm, independent of aspect.
  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 and provides last known BULLSEYE position. Fighters maintain MONITOR responsibility for a FADED group if they can maintain correlation.
 
'''VANISHED''' — a special case of FADED. Used when the GROUP is not in a known blind zone and is correlated to a shot by friendly forces that meets parameters for successful termination. VANISHED implies the contact is assessed as killed.
 
FADED is not used for friendly aircraft. Controllers use NEGATIVE CONTACT for friendly aircraft not held on sensors.
 
=== SNAPLOCK ===
If fighters gain sensor contact to a GROUP inside THREAT range with BEAM or hotter aspect:
  FREEDOM 31, SNAPLOCK 1-2-5/10, EIGHT THOUSAND.
Controller responds with GROUP name, BRAA, declaration, and fill-ins. If previously undetected, the group is named THREAT GROUP.
 
=== 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.
 
=== SPIKE / STROBE ===
'''SPIKED''' — fighter is being painted by an airborne radar. Fighter calls 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.
'''STROBE''' — fighter is detecting an airborne emitter by direction finding. Same response format as SPIKED.
 
=== LEAKER ===
A LEAKER is an airborne threat that has passed through a defensive layer. May be called by fighters or controllers.
  VIPER 1, LEAKER BULLSEYE 3-0-5/65, FIVE THOUSAND, TRACK SOUTH, HOSTILE TWO CONTACTS.
----


== 09 / Brevity Words ==
== 09 / Brevity Words ==
Line 653: Line 323:
|-
|-
|'''CLEAN'''
|'''CLEAN'''
|1. No sensor information on a GROUP of interest. 2. No visible battle damage. 3. Aircraft not carrying external stores.
|1. No sensor information on a GROUP of interest.
2. No visible battle damage.  
3. Aircraft not carrying external stores.  
|-
|-
|'''CLARA'''
|'''CLARA'''
Line 699: Line 371:
|'''VISUAL'''
|'''VISUAL'''
|Visual sighting of a friendly aircraft, ground unit, or ship.
|Visual sighting of a friendly aircraft, ground unit, or ship.
|-
|'''WORDS'''
|Directive or interrogative call regarding further information or directives pertinent to the mission or operating area.
|}
|}


Line 729: Line 398:
|'''HOSTILE'''
|'''HOSTILE'''
|Contact identified as enemy upon which clearance to fire is authorized IAW ROE.
|Contact identified as enemy upon which clearance to fire is authorized IAW ROE.
|-
|'''LEAKER'''
|An airborne threat that has passed through a defensive layer.
|-
|-
|'''NEUTRAL'''
|'''NEUTRAL'''
Line 741: Line 407:
|'''SPADES'''
|'''SPADES'''
|Contact returns no or invalid IFF response on interrogation.
|Contact returns no or invalid IFF response on interrogation.
|-
|'''STRANGER'''
|Unidentified traffic not a factor to the mission. Not included in the PICTURE.
|-
|-
|'''FAST'''
|'''FAST'''
Line 834: Line 497:
|'''TARGETED'''
|'''TARGETED'''
|Fighter has acquired the assigned GROUP and assumed responsibility for it.
|Fighter has acquired the assigned GROUP and assumed responsibility for it.
|-
|'''TARGETING'''
|Informative call; fighter is in the process of acquiring the assigned GROUP.
|-
|-
|'''UNTARGETED'''
|'''UNTARGETED'''
|GROUP inside targeting range with no fighter assigned.
|GROUP inside targeting range with no fighter assigned.
|-
|-
|'''DROP / DROPPING'''
|'''DROPPING'''
|Stop monitoring a specified GROUP or emitter and resume search responsibilities. Targeting responsibility returns to the controller.
|Stop monitoring a specified GROUP or emitter and resume search responsibilities.
|-
|-
|'''RESET'''
|'''RESET'''
Line 852: Line 512:
|'''SORTED'''
|'''SORTED'''
|Sort responsibility within a GROUP has been met by the calling fighter.
|Sort responsibility within a GROUP has been met by the calling fighter.
|-
|'''BLOW(ING) THROUGH'''
|Directive or informative call that the fighter is continuing straight ahead at the merge and is dropping targeting responsibility.
|-
|-
|'''ANCHORED'''
|'''ANCHORED'''
Line 861: Line 518:
|'''SEPARATION'''
|'''SEPARATION'''
|Request or information call stating the distance in nm between two GROUPs or WAVES.
|Request or information call stating the distance in nm between two GROUPs or WAVES.
|-
|'''RANGE BACK'''
|Distance from the closest friendly aircraft to the closest GROUP measured parallel to the fight axis. Used during COLD operations.
|-
|-
|'''LANE CROSSER'''
|'''LANE CROSSER'''
Line 897: Line 551:
|'''SPIKED'''
|'''SPIKED'''
|Fighter is being painted by an airborne radar. Called with bearing or cardinal direction.
|Fighter is being painted by an airborne radar. Called with bearing or cardinal direction.
|-
|'''STROBE'''
|Fighter is detecting an airborne emitter on direction finding. Called with bearing.
|-
|-
|'''MUSIC'''
|'''MUSIC'''
|Fighter is experiencing radar electromagnetic deceptive jamming from a GROUP.
|Fighter is experiencing radar electromagnetic deceptive jamming from a GROUP.
|-
|'''METALLICA'''
|EA is preventing fighter employment on a specific GROUP.
|-
|-
|'''PRESS'''
|'''PRESS'''
Line 952: Line 600:
|Aircraft has entered a known or pop-up SAM MEZ. Directive call to snap 180 degrees away.
|Aircraft has entered a known or pop-up SAM MEZ. Directive call to snap 180 degrees away.
|-
|-
|'''SNAP'''
|'''HARD'''
|Immediate turn to the specified heading.
|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 ===
=== Status and Administrative ===
{| class="wikitable" style="width:100%;"
{| class="wikitable" style="width:100%;"
Line 972: Line 700:
|'''BLIND'''
|'''BLIND'''
|No visual contact with a friendly aircraft.
|No visual contact with a friendly aircraft.
|-
|'''CHATTERMARK'''
|Directive to transition from primary to alternate tactical frequency.
|-
|-
|'''FENCE IN / OUT'''
|'''FENCE IN / OUT'''
Line 981: Line 706:
|'''LOWDOWN'''
|'''LOWDOWN'''
|Request for the current tactical electromagnetic support or ground/surface picture.
|Request for the current tactical electromagnetic support or ground/surface picture.
|-
|'''MARSHALL'''
|Holding at a designated point prior to mission execution.
|-
|'''NET SWEET'''
|All players have checked in on the new frequency following a CHATTERMARK.
|-
|-
|'''ROLEX'''
|'''ROLEX'''
Line 993: Line 712:
|'''SLIP'''
|'''SLIP'''
|Time delay to an individual flight or element event. Not additive.
|Time delay to an individual flight or element event. Not additive.
|-
|'''TIMBER SOUR'''
|Data link is not functioning correctly or not providing accurate surveillance information.
|-
|-
|'''UNABLE'''
|'''UNABLE'''
|Cannot comply as requested or directed.
|Cannot comply as requested or directed.
|-
|'''WORDS'''
|Directive or interrogative call regarding further information or directives pertinent to the mission. Generated by TAC C2 and outlined in SPINS.
|}
|}

Latest revision as of 17:13, 31 May 2026

SOURCE — Tactical Communications Guide
Covers: Airspace Control · TACADMIN · Check-In · Force Packaging · Air-to-Air Communication · Brevity
Based on ATP 3-52.4 / MCRP 3-20F.10 / NTTP 6-02.9 / AFTTP 3-2.8, October 2024. Adapted for DCS.


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.

  1. Tactical Control Center - TACC2
  2. Mission Commander - MC
  3. Team Lead (previously called Package Lead) - TL
  4. Flight Lead - FL
  5. Element Lead - EL
  6. Wingman - WM

Within this squadron MC's duties will be taken over by TACC2 or TL (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.

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

Format Bearing Range (nm) Altitude (ft) Aspect
BRAA 3 2 0 30 20 thousand 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.

Station Phrase
Controller {CS} Push Button #
FL {CS} Push Button #
FL (intraflight) Flight Push {UHF/VHF, Radio 1/2} Button #
All flight members switch to the new Frequency
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.

Station Phrase
FL {TACC2-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:

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

Station Phrase
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

Station Phrase
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 Refueling

AAR requires close coordination with the tanker around a pre-briefed Rendezvous (RV). SOURCE uses RV Alpha (Fixed Anchor) for all operations. (due to DCS limitations)

Tanker Orbit Stack

Level Usage ex.
ALPHA Receivers departing · Emergency FL210
BRAVO Tanker base level FL200
CHARLIE Receiver evasive FL190
DELTA Receivers approaching FL180

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.

Station Phrase
Controller {CS} Proceed Tanker BRAA {BRAA}, RV Alpha, Tanker Freq {Freq} {Instructions}
FL {CS} Roger, RV Alpha, Tanker Freq {Freq} {Readback}
Once flight has radar contact with tanker
FL {Flight Name} Judy 1, Weapons Safe
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
Switch to DCS tanker frequency and join up

FL must confirm Nose Cold / Weapons Safe 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.

Type Description
Electronic PID IFF interrogation, data link picture, NCTR, controller declaration. Most common form in BVR.
Visual PID (VID) Confirm number, type, livery, armament, heading, speed. Requires merge or VID pass.
Ground Targets Correlate with pre-briefed target.

08 / Air-to-Air Combat

Air to Air Communication Procedures

09 / Air-to-Surface Combat

Air to Surface Communication Procedures

09 / Brevity Words

Situational Awareness

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

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

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

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

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

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

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

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

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.