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)
Niknam3 (talk | contribs)
 
(7 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 61: Line 73:
!Format
!Format
!Bearing
!Bearing
!Range
!Range (nm)
!Altitude
!Altitude (ft)
!Aspect
!Aspect
|-
|-
|BRAA
|BRAA
|3 2 0
|3 2 0
|30 nm
|30
|20,000 ft
|20 thousand
|Flanking
|Flanking
|-
|-
Line 74: Line 86:
|1 1 0
|1 1 0
|30  
|30  
|25 Thousand
|25 thousand
|HOT
|HOT
|}
|}
Line 87: Line 99:
|{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 114: 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 133: 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 147: 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 163: 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 194: 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 289: 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 312: 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 328: 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 334: 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 348: 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 — 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.
 
=== 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, 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
|}
 
=== 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. The tactic determines which steps are executed — the loop defines what is available.
 
==== 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
|}
 
==== 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
|-
| Flight Lead || {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
|-
| Flight Lead || ''(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 — in some tactic profiles the flight may go directly from SORT to ENGAGE without releasing the controller.
 
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || {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. Said on intraflight. The flight lead may also direct simultaneous employment by multiple members.
 
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || ''(intraflight) {Wingman CS} ENGAGE''
|-
| Wingman || ''(intraflight) {CS}''
|}
 
==== Weapon Employment ====
The firing aircraft calls the shot on interflight 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 || {Controller-CS} {CS} FOX THREE {Group Label} {Contact Description} BULLSEYE {Bearing/Range} {Altitude}
|-
| Controller || 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
|-
| Controller || 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
|-
| Flight Lead || {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
|-
| Flight Lead || {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 ====
After OUT, 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 and proceed to RESET
|-
| 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 to RESET
|}
 
==== 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
|-
| Flight Lead || {Controller-CS} {CS} IN {Direction}
|-
| Flight Lead || {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}
|}
 
==== 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
|-
| Flight Lead || {Controller-CS} {CS} RESET
|-
| colspan="2" style="text-align:center;" | ''Flight returns to prebriefed CAP position. Controller resumes full picture responsibility.''
|}
 
=== 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.
 
==== STROBE ====
Fighter is detecting an airborne emitter by direction finding. Response format identical to SPIKED.
 
==== 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. VANISHED implies the contact is assessed as killed.
 
==== 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
|-
| Mission Commander || MC || May hold or delegate COMMIT authority
|-
| Team Lead || TL || May hold COMMIT authority if delegated
|-
| Flight Lead || FL || May hold COMMIT authority if delegated
|-
| Controller || — || May direct COMMIT if delegated; otherwise recommends only
|}
 
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
|-
| 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 continuously. Pictures are requested as needed to maintain SA.
==== Commit ====
===== Fighter, MC, TL, or FL-Initiated =====
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| 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.
==== Targeting ====
The flight assigns GROUP responsibility and confirms classification. The tactical plan is announced on intraflight at the same time.
{| 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}
|-
| 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 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.
Note: Targeting responsibility is cancelled when a fighter communicates BLOWING THROUGH, SPITTER, or executes an OUT. The GROUP becomes UNTARGETED if no fighter subsequently targets it.
==== 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) ==
== 08 / Air-to-Air Combat ==
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.
[[MTTP/A2A|Air to Air Communication Procedures]]


=== OCA Range Structure ===
== 09 / Air-to-Surface Combat ==
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.
[[MTTP/A2S|Air to Surface Communication Procedures]]
 
=== 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
|-
| Flight Lead || {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}
|-
| Flight Lead || {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}
|-
| Flight Lead || {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
|-
| Flight Lead || {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
|-
| Flight Lead || {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
|-
| Flight Lead || {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
|-
|Flight Lead
|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
|-
|Flight Lead
|''(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 ==
== 09 / Brevity Words ==

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.