Toggle search
Toggle menu
16
49
31
443
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: Difference between revisions

From SOURCE DCS WIKI
More actions
VisualWikitext
Niknam3 (talk | contribs)
admin
311 edits
Created page with "Tactical Communication '''ASACS (Airborne Surveillance and Control System)''' is the integrated command-and-control framework that links airborne surveillance platforms, ground-based control centers, and air defense assets into a single coordinated system for managing the air battle. Rather than being a specific unit or aircraft, ASACS defines the doctrine, communications architecture, and authority relationships that govern how assets such as AWACS, CRCs, and radar si..."
 
Niknam3 (talk | contribs)
admin
311 edits
 
(22 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Tactical Communication
__NOTOC__
<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: Control Architecture · Check-In · AAR · PID · Air-to-Air Combat · Brevity</div>
<div style="font-size:0.8em; color:#555;">''Information is based on real-world procedures but modified to cater to DCS limitations''</div>


'''ASACS (Airborne Surveillance and Control System)'''
----


is the integrated command-and-control framework that links airborne surveillance platforms, ground-based control centers, and air defense assets into a single coordinated system for managing the air battle. Rather than being a specific unit or aircraft, ASACS defines the doctrine, communications architecture, and authority relationships that govern how assets such as AWACS, CRCs, and radar sites share data, build a common Recognized Air Picture, and allocate control of aircraft and weapons. Within NATO terminology, ASACS ensures seamless handover, deconfliction, and information flow between airborne and ground controllers so that tactical air operations are directed through one coherent control structure instead of multiple independent agencies.
__TOC__


'''AWACS (Airborne Warning and Control System)'''
----


is an airborne command-and-control platform equipped with long-range radar and battle management consoles. It provides surveillance, identification, and tactical control of aircraft over extended ranges, particularly where ground radar coverage is limited. AWACS builds and maintains an air picture, directs fighter intercepts, coordinates air operations, and relays communications between airborne and ground units.
== 01 / Control Architecture ==


'''CRC (Control and Reporting Center)'''
'''ASACS''' (Airborne Surveillance and Control System) is the integrated command-and-control framework linking airborne surveillance platforms, ground-based control centers, and air defense assets into a single coordinated system. ASACS defines the doctrine, communications architecture, and authority relationships governing how AWACS, CRCs, and radar sites share data, build a Recognized Air Picture, and allocate control of aircraft and weapons.


is a ground-based air command-and-control facility responsible for surveillance, identification, and tactical control within a designated airspace sector. It fuses data from multiple radar and sensor sources to generate a Recognized Air Picture and provides fighter control, airspace coordination, and reporting to higher headquarters. A CRC may control aircraft directly and coordinate with surface-based air defense systems.
'''AWACS''' (Airborne Warning and Control System) is an airborne command-and-control platform with long-range radar and battle management consoles. It provides surveillance, identification, and tactical control of aircraft over extended ranges, particularly where ground radar coverage is limited.


'''GCI (Ground Controlled Intercept)'''
'''CRC''' (Control and Reporting Center) is a ground-based air command-and-control facility responsible for surveillance, identification, and tactical control within a designated airspace sector. It fuses multiple radar sources to generate a Recognized Air Picture and provides fighter control and airspace coordination.


is the tactical function of directing fighter aircraft to intercept airborne targets using ground-based radar and communications. GCI refers to the activity performed by trained controllers rather than a specific facility. It involves providing vectors, target information, and engagement support to aircraft based on radar tracking data.
'''GCI''' (Ground Controlled Intercept) is the tactical function of directing fighter aircraft to intercept airborne targets using ground-based radar. GCI refers to the activity performed by trained controllers, not a specific facility.


'''Intercept Controller'''
=== Control Types ===


The controller in charge of guiding military assets in a tactical environment.
{| class="wikitable" style="text-align:center;"
|-
!
! colspan="2" | CLOSE
! colspan="2" | LOOSE
! BROADCAST
|-
!
! POSITIVE
! ADVISORY
! POSITIVE
! ADVISORY
!
|-
! TARGETS SELECTION
| IC || IC || IC || IC || PIL
|-
! TACTICAL SELECTION
| IC || IC || PIL || PIL || PIL
|-
! GEOMETRY
| IC || IC || PIL || PIL || PIL
|-
! SEPARATION
| IC || PIL || IC || PIL || PIL
|-
! PICTURE FORMAT
| colspan="2" | HDG – SPD – ALT
| colspan="2" | BRAA or BULLSEYE
| BULLSEYE
|}''PIL = Pilot's Responsibility · IC = Intercept Controller's Responsibility''


Even though they have the same job, when located onboard an AEW/AWACS the name changes to '''Weapon Controller (WC)''' but in this manual <u>we always refer to IC for convenience</u>.
----


They have the primary task of assisting and coordinating military aircraft during the operations of:
== 02 / Intercept Controller ==


* QRA
The '''Intercept Controller (IC)''' guides military assets in the tactical environment. When airborne on an AEW/AWACS platform the role is called '''Weapon Controller (WC)''' — this manual uses '''IC''' throughout for convenience.
* AIR TO AIR REFUELLING
* COMBAT AIR PATROL


The IC is responsible for:
Primary IC responsibilities: target selection and assignment · PICTURE reporting · initial fighter vector (COMMIT)


- Selection and assignment of targets
Supported operations: '''QRA · AIR TO AIR REFUELLING · COMBAT AIR PATROL'''


- Providing information about the PICTURE
----


- Giving the initial vector to air defense fighters (COMMIT)
== 03 / Standard Calls ==


Control Types
=== State Call ===


[[File:media/image2.png|601x266px]]
A '''State Call''' reports combat status to the IC: '''weapons, fuel, and playtime''' in a fixed order.


PIL = Pilots Responsibility
Example: ''"State is 602+ 10000lbs 90M"''


IC = Intercept Controllers Responsibility
{| class="wikitable" style="width:100%;"
 
''State Call''
 
A '''State Call''' reports an aircraft’s combat status to the IC.
 
It '''covers weapons, fuel, and playtime''' in a fixed order.
 
Example:
 
Flight Lead: “State is 602+ 10000lbs 90M
 
{| class="wikitable"
|-
|-
! style="text-align: left;"| ''# FOX-3''
! # FOX-3 !! # FOX-1 !! # FOX-2 !! Gun !! Fuel !! Playtime
! style="text-align: left;"| ''# FOX-1''
! style="text-align: left;"| ''# FOX-2''
! style="text-align: left;"| ''Gun''
! style="text-align: left;"| ''Fuel''
! style="text-align: left;"| ''Playtime''
|-
|-
! style="text-align: left;"| 6
| 6 || 0 || 2 || + || 10,000 lbs || 90 min
! style="text-align: left;"| 0
! style="text-align: left;"| 2
! style="text-align: left;"| +
! style="text-align: left;"| 10000lbs
! style="text-align: left;"| 90M
|}
|}


Would mean:
6× FOX-3, 0× FOX-1, 2× FOX-2, gun available, 10,000 lbs fuel, 90 minutes playtime.


6 x FOX-3, 0 x FOX-1, 2 x FOX-2, Gun Available, 10000lbs of fuel remaining
=== BRAA Call ===


90 Minutes of Playtime
Tactical control format: '''Bearing, Range, Altitude, Aspect''' relative to the specified friendly aircraft.


''BRAA Call''
{| class="wikitable" style="width:100%;"
 
A tactical control format providing target '''bearing, range, altitude, and aspect''' (BRAA) relative to the specified FRIENDLY aircraft.
 
{| class="wikitable"
|-
|-
! style="text-align: left;"| ''Groups''
! Groups !! Format !! Bearing !! Range !! Altitude !! Aspect !! Declaration
! style="text-align: left;"| ''Format''
! style="text-align: left;"| ''Bearing''
! style="text-align: left;"| ''Range''
! style="text-align: left;"| ''Altitude''
! style="text-align: left;"| ''Aspect''
! style="text-align: left;"| ''DECLR''
|-
|-
! style="text-align: left;"| Single Group
| Single Group || BRAA || 320 || 30 nm || 20,000 ft || Flanking || BOGEY
! style="text-align: left;"| BRAA
! style="text-align: left;"| 320
! style="text-align: left;"| 30
! style="text-align: left;"| 20000
! style="text-align: left;"| Flanking
! style="text-align: left;"| BOGEY
|}
|}


''Flight Check / Frequency Change''
=== Flight Check / Frequency Change ===
 
When Switching the Flight to a different Frequency a “Flight Check” is executed
 
Intraflight = Frequency only the flight members are on


Interflight = Control Agency’s Frequency
Executed when switching the flight to a new frequency. '''Intraflight''' = flight-internal frequency. '''Interflight''' = control agency frequency.


{| class="wikitable"
{| class="wikitable" style="width:100%;"
|-
|-
! Station
! style="width:25%;" | Station !! Phrase
! Phrase
|-
|-
! ATC
| ATC || {CS} Push Button _
! {CS} Push Button _
|-
|-
! Flight Lead (on interflight)
| Flight Lead (interflight) || {CS} Push Button _
! {CS} Push Button _
|-
|-
! Flight Lead (on intraflight)
| Flight Lead (intraflight) || Push {UHF/VHF, Radio 1/2} Button _
! Push {UHF / VHF, Radio 1 / Radio 2} Button _
|-
|-
! colspan="2" style="text-align: center;"| All Flight Members switch to channel _
| colspan="2" style="text-align:center;" | ''All flight members switch to channel _''
|-
|-
! Flight Lead
| Flight Lead || {CS} Check
! {CS} Check
|-
|-
! Wingman of Flight Lead
| Wingman || 2
! 2
|-
|-
! Element Lead
| Element Lead || 3
! 3
|-
|-
! Wingman of Element Lead
| Element Wingman || 4
! 4
|-
|-
! colspan="2" style="text-align: center;"| Flight Lead Proceeds with Initial Call as normal
| colspan="2" style="text-align:center;" | ''Flight Lead proceeds with initial call as normal''
|}
|}


''Authentication''
=== Authentication (DRYAD) ===


Authentication is a fundamental procedure to make sure you are in contact with an &quot;ally&quot; unit. Normally the check is performed by comparing a table in the possession of both parties who, each other, wonder about the content of the same.
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.


There are several methods available but we are going to focus only on one of them named '''DRYAD''' ''([https://en.wikipedia.org/wiki/DRYAD <u>https://en.wikipedia.org/wiki/DRYAD</u>])''
Pilots are responsible for initiating Authentication with a Controlling Station


For authentication, a challenging station selects a letter at random from the left most column followed by a second (randomly selected) letter in the row of the first chosen letter. The station being challenged would then authenticate by picking the letter directly below the row and position of the second letter selected.
{| class="wikitable" style="width:100%;"
 
|-
[[File:media/image1.png|581x417px]]
! style="width:25%;" | Station !! Phrase
 
Table Will be provided in the PreMission Briefing
 
{| class="wikitable"
|-
|-
! style="text-align: left;"| ATC
| Pilot || {CRC-CS} {CS} Authenticate E-A
! style="text-align: left;"| Authenticate E-A
|-
|-
! style="text-align: left;"| Pilot
| ATC || Come back G
! style="text-align: left;"| Come back G
|-
|-
! style="text-align: left;"| Pilot
| ATC || Authenticate J-U
! style="text-align: left;"| Authenticate J-U
|-
|-
! style="text-align: left;"| ATC
| Pilot || Come back R
! style="text-align: left;"| Come back R
|-
|-
! style="text-align: left;"| Pilot
| ATC || Good Authentication
! style="text-align: left;"| Good Authentication
|}
|}


''AWACS / CRC / … - Communication Procedures''
=== FENCE IN ===
 
----
CS = Callsign for example SHADOW1


'''Check in with a Controlling Center'''
== 04 / Check-In Procedures ==


Note that this is an example! Depending on the mission, not every procedure may be executed.
''CS = Callsign (e.g. SHADOW 1). Not every procedure applies to every mission.''


Check in on Radar (Transit Control)
=== Check In on Radar — Transit Control ===


{| class="wikitable"
{| class="wikitable" style="width:100%;"
|-
|-
! Station
! style="width:25%;" | Station !! Phrase
! Phrase
|-
|-
! colspan="2" style="text-align: center;"| Flight Check
| colspan="2" style="text-align:center;" | ''Flight Check''
|-
|-
! Flight Lead
| Flight Lead || {CRC-CS} {CS} {Flight Level}
! {CRC-CS} {CS} {FlightLevel}
|-
|-
! colspan="2" style="text-align: center;"| Authentication
| colspan="2" style="text-align:center;" | ''Authentication''
|-
|-
! CRC
| CRC || {CS}, Identified, {Instructions}
! {CS}, Identified, {Instructions}
|}
|}


NOTE: Close Positive Control is inferred
''NOTE: Close Positive Control is inferred.''


Check in with Weapons Controller
=== Check In with Weapons Controller ===


{| class="wikitable"
{| class="wikitable" style="width:100%;"
|-
! style="text-align: left;"| Station
! style="text-align: left;"| Phrase
|-
|-
! colspan="2" style="text-align: center;"| Flight Check
! style="width:25%;" | Station !! Phrase
|-
|-
! style="text-align: left;"| Flight Lead
| colspan="2" style="text-align:center;" | ''Flight Check''
! style="text-align: left;"| {CRC-CS} {CS} Mission Nr {MSN} {Position} {Altitude} {PLAYTIME} {as Fragged / With Exceptions }
|-
|-
! style="text-align: left;"| CRC
| colspan="2" style="text-align:center;" | ''Authentication''
! style="text-align: left;"| ''{Acknowledges}''
|-
|-
! colspan="2" style="text-align: center;"| Authentication
| Flight Lead || {CRC-CS} {CS} Mission Nr {MSN} {Position} {Altitude} {Playtime} {As Fragged / With Exceptions}
|-
|-
! style="text-align: left;"| CRC
| CRC || {CS}, Identified, {Control Type}, Alpha Check Bullseye {Position}
! style="text-align: left;"| {CS}, Identified, {Control Type}, ALPHA CHECK BULSEYE {position from bullseye}
|-
|-
! style="text-align: left;"| Flight Lead
| Flight Lead || Same {Alpha Check}
! style="text-align: left;"| Same {Alpha Check}
|}
|}


NOTE: Bullseye cannot be used for initial position calls.
''NOTE: Bullseye cannot be used for initial position calls — only valid after Alpha Check.''
 
Bullseye is only valid after ALPHA CHECK
 
'''Training Range Operations'''


Ingress
----


{| class="wikitable"
== 05 / Training Range & Formations ==
|-
! style="text-align: left;"| Station
! style="text-align: left;"| Phrase
|-
! rowspan="2" colspan="2" style="text-align: center;"| Flight Check
|-
|-
! Aircraft
! style="text-align: left;"| Tactical, {CS} Leaving IP, Heading ___
|-
! style="text-align: left;"| Tactical Controller
! style="text-align: left;"| Radar Contact, Continue as Fragged, CALL IN
|-
! Aircraft
! style="text-align: left;"| Roger, {CS}
|}


Attack
=== Attack Run ===


{| class="wikitable"
{| class="wikitable" style="width:100%;"
|-
|-
! style="text-align: center;"| Station
! style="width:25%;" | Station !! Phrase
! style="text-align: center;"| Phrase
|-
|-
! colspan="2" style="text-align: center;"| '''Once turning in for an attack run'''
| colspan="2" style="text-align:center;" | ''Turning in for attack run''
|-
|-
! Aircraft
| Aircraft || {CS} In Hot, Heading ___
! style="text-align: left;"| {CS} In Hot, Heading ___
|-
|-
! style="text-align: left;"| Tactical Controller
| Tactical Controller || Cleared Hot ''(or: Abort, Turn Left/Right HDG)''
! style="text-align: left;"| Cleared Hot (or Abort, Turn Left / Right HDG)
|-
|-
! colspan="2" style="text-align: center;"| '''Upon completion of the attack run.'''
| colspan="2" style="text-align:center;" | ''Upon completion''
|-
|-
! Aircraft
| Aircraft || {CS} Off Target
! style="text-align: left;"| {CS} Off Target
|}
|}


This has to be repeated for every attack run.
''Repeated for every attack run. Multiple aircraft on the same target: ASACS issues traffic information and may require visual separation.''


If multiple aircraft are attacking the same target ASACS-Controller will issue traffic information and may request the aircraft to maintain visual separation.
=== Formation Splits ===


'''Formation Splits'''
{| class="wikitable" style="width:100%;"
 
{| class="wikitable"
|-
|-
! Station
! style="width:25%;" | Station !! Phrase
! Phrase
|-
|-
! Flight Lead
| Flight Lead || {CS}, request split into {number} parts of {number} each
! {CS}, request split into {number} parts of {number} each
|-
|-
! CRC
| CRC || {CS}, report ready for {Right / Left Hand} {Split Type}
! {CS}, report ready for {Right hand / Left Hand \ _} {Split Type}
|}
|}


Only In case of split by vectors ATC will call the Side (Lefthand / Righthand)
==== Vertical (Altitude) ====


'''Vertical (Split by Altitude Adjustment)''' ''Continued''
{| class="wikitable" style="width:100%;"
 
{| class="wikitable"
|-
! style="text-align: left;"| Station
! style="text-align: left;"| Phrase
|-
! style="text-align: left;"| Flight Lead
! {CS},ready
|-
|-
! style="text-align: left;"| CRC
! style="width:25%;" | Station !! Phrase
! style="text-align: left;"| {CS 2}, descend {FL number}
|-
|-
! style="text-align: left;"| Flight Lead 2
| Flight Lead || {CS}, ready
! style="text-align: left;"| {CS 2}, descending {FL number}
|-
|-
! style="text-align: left;"| CRC
| CRC || {CS 2}, descend {FL}
! {CS 2}, squawk {number}
|-
|-
! style="text-align: left;"| Flight Lead 2
| Flight Lead 2 || {CS 2}, descending {FL}
! {CS 2}, squawk {number}
|-
|-
! style="text-align: left;"| CRC
| CRC || {CS 2}, squawk {number} · identified
! {CS 2}, identified
|-
|-
! colspan="2" style="text-align: center;"| Repeat for each new flight.
| colspan="2" style="text-align:center;" | ''Repeat for each new flight''
|}
|}


'''Lateral (Split by Vector Change)''' ''Continued''
==== Lateral (Vector) ====


{| class="wikitable"
{| class="wikitable" style="width:100%;"
|-
|-
! style="text-align: left;"| Station
! style="width:25%;" | Station !! Phrase
! style="text-align: left;"| Phrase
|-
|-
! style="text-align: left;"| Flight Lead
| Flight Lead || {CS}, ready
! {CS},ready
|-
|-
! style="text-align: left;"| CRC
| CRC || {CS 2} for split turn {side} {degrees}
! style="text-align: left;"| {CS 2} For split turn {side} {degrees}
|-
|-
! style="text-align: left;"| Flight Lead
| Flight Lead || {CS 2} for split turn {side} {degrees}
! {CS 2} For split turn {side} {degrees}
|-
|-
! style="text-align: left;"| CRC
| CRC || {CS 2} squawk {number} · identified
! {CS 2} squawk {number}
|-
|-
! style="text-align: left;"| Flight Lead 2
| colspan="2" style="text-align:center;" | ''Repeat for each new flight''
! {CS 2} squawk {number}
|-
! style="text-align: left;"| CRC
! {CS 2} identified
|-
! colspan="2" style="text-align: left;"| Repeat for each new flight
|}
|}


'''Join-UP'''
=== Join-Up ===


{| class="wikitable"
{| class="wikitable" style="width:100%;"
|-
|-
! style="text-align: left;"| Station
! style="width:25%;" | Station !! Phrase
! style="text-align: left;"| Phrase
|-
|-
! style="text-align: left;"| Flight Lead
| Flight Lead || {CS} requesting join-up with {CS 2}
! {CS} requesting join-up with {CS 2}
|-
|-
! style="text-align: left;"| CRC
| CRC || {CS 2}, confirm join-up clearance for {CS}
! {CS}, roger
|-
|-
! style="text-align: left;"| CRC
| Flight Lead 2 || {CS 2}, {CS} is cleared to join up
! style="text-align: left;"| {CS 2}, confirm join up clearance for {CS}.
|-
|-
! style="text-align: left;"| Flight Lead 2
| CRC || {CS}, fly {heading} and climb/descend to {angels}
! style="text-align: left;"| {CS 2}, {CS} is cleared to join up.
|-
|-
! style="text-align: left;"| CRC
| Flight Lead || {CS}, fly {heading} and climb/descend to {angels}
! style="text-align: left;"| {CS}, for join-up, fly {heading} and climb / descend to {angels}.
|-
|-
! style="text-align: left;"| Flight Lead
| CRC || {CS}, report {CS 2} in sight
! {CS}, for join-up, fly {heading} and climb / descend to {angels}.
|-
|-
! style="text-align: left;"| CRC
| Flight Lead || {CS}, {CS 2} in sight, {position}
! {CS}, report {CS 2} in sight.
|-
|-
! style="text-align: left;"| Flight Lead
| CRC || Visual join-up approved — report formation tight
! {CS}, report {CS 2} in sight, {Position}
|-
|-
! style="text-align: left;"| CRC
| Flight Lead 2 || {CS 2}, formation tight
! {CS}, visual join-up approved {CS 2}, report formation tight.
|-
|-
! style="text-align: left;"| Flight Lead 2
| CRC || {CS 2} adopt callsign {new CS}
! {CS 2}, formation tight.
|-
! style="text-align: left;"| CRC
! {CS 2} formation adopt callsign {new CS}
|}
|}


'''AAR'''
----


[[File:media/image3.png|601x177px]]
== 06 / Air-to-Air Refuelling ==


Air to Air Refueling is not only mechanically difficult but requires close coordination with the Tanker.
AAR requires close coordination with the tanker around a pre-briefed Rendezvous (RV). SOURCE uses '''RV Alpha (Fixed Anchor)''' for all operations.


To ensure that all parties are at the right spot at the same time they agree on a Rendezvous (RV) which will be defined in the Pre-Mission Briefing or directed by the IC
=== Tanker Orbit Stack ===


There are multiple Types of RV
{| class="wikitable" style="width:100%;"
 
|-
* RV Alpha - Fixed Anchor
! Level !! Usage
* RV Bravo - Head-on
|-
* RV Charlie - Tail Chase
| '''ALPHA''' || Receivers departing · Emergency
* RV Delta - Point Parallel
|-
* RV Echo - Timed Arrival
| '''BRAVO''' || Tanker base level
* RV Foxtrot - Sequential Departure
|-
* RV Golf - En Route
| '''CHARLIE''' || Receiver evasive
 
|-
They get increasingly more complicated and require some calculation to determine the correct speeds and turnradii.
| '''DELTA''' || Receivers approaching
 
|}
Since the DCS tanker AI is even with the help of Olympus absolute dogshit we will not be covering the more complex Rendezvous procedures which require the Tanker to manoeuvre out of its Fixed Anchor.


Instead we will focus only on the RV Alpha for simplicity.
=== RV Alpha Procedure ===


RV Alpha
Receiver: fly 2,000 ft below AAR altitude · follow IC heading · declare JUDY on radar contact · declare VISUAL when in sight · weapons safe and radar off · take ECHELON LEFT when authorized.


Execution:
{| class="wikitable" style="width:100%;"
 
The receiver pilot must:
 
* Fly up to an altitude of 2000ft below the AAR Altitude (As instructed by the IC)
* Follow the Heading instructions by the IC
* Declare that they have radar contact with the tanker by the expression JUDY
* When in sight of the tanker declare visual contact by the expression VISUAL
* Secure the armament (Weapons Master OFF) and turn of the radar when in view of the tanker
* Take the position of ENCHELON LEFT when authorized by the IC
 
Tanker Orbit Airspace
 
A tanker orbit is assigned an altitude stack of 4000 feet, from Top to bottom they are Alpha, Bravo, Charlie, Delta
 
Alpha is used for receivers leaving the tanker and the tanker emergency break away level
 
Bravo is the Base level of the Tanker
 
Charlie is used for evasive action on the receiver side
 
Delta is used for receivers approaching the Tanker
 
{| class="wikitable"
|-
|-
! Station
! style="width:25%;" | Station !! Phrase
! Phrase
|-
|-
! style="text-align: left;"| CRC
| CRC || {CS} Proceed Tanker BRAA {BRAA} — RV Alpha — Tanker Freq {Freq} {Instructions}
! style="text-align: left;"| {CS} Proceed Tanker BRAA {BRAA} This will be Rendezvous ALPHA Tanker Frequency {Frequency} {Further Instructions}
|-
|-
! style="text-align: left;"| Flight Lead
| Flight Lead || {CS} Roger, RV Alpha, Tanker Freq {Freq} {Readback}
! style="text-align: left;"| {CS} Roger, RV A, Tanker Frequency {Frequency} {Readback of further instructions}
|-
|-
! colspan="2" style="text-align: center;"| Once the flight has Radar Contact to the Tanker
| colspan="2" style="text-align:center;" | ''Once flight has radar contact with tanker''
|-
|-
! style="text-align: left;"| Flight Lead
| Flight Lead || {Flight Name} Judy 1, Weapons Safe
! style="text-align: left;"| {Flight - Name} JUDY 1 Weapons Safe
|-
|-
! style="text-align: left;"| All Wingmen in order
| All wingmen (in order) || 2, 3, 4… Weapons Safe
! style="text-align: left;"| 2,3,4, … Weapons safe
|-
|-
! colspan="2" style="text-align: center;"| Once in view of the Tanker
| colspan="2" style="text-align:center;" | ''Once tanker is in sight''
|-
|-
! style="text-align: left;"| CRC
| CRC || {CS} Tanker {x} o'clock, report visual
! style="text-align: left;"| {CS} Tanker is on your {x} o clock, Report Visual
|-
|-
! style="text-align: left;"| Flight Lead
| Flight Lead || {CS} Nose Cold, visual with tanker
! style="text-align: left;"| (Once Visual} {CS} Nose Cold, Visual with Tanker
|-
|-
! style="text-align: left;"| CRC
| CRC || {CS} Roger, contact boom
! style="text-align: left;"| {CS} Roger Contact Boom
|-
|-
! colspan="2" style="text-align: center;"| At this point you switch to dcs’s Tanker Frequency
| colspan="2" style="text-align:center;" | ''Switch to DCS tanker frequency''
|}
|}


NOTE: Flight Lead shall ask his wingman on intraflight to confirm Nose Cold before reporting it to ATC
''NOTE: Flight Lead must confirm Nose Cold with wingmen on intraflight before reporting to ATC.''


'''Positive Identification (PID)'''
----


In modern air combat, PID is about proving, to a reasonable and defensible standard, that the contact is a legitimate target under the Rules of Engagement (ROE). That proof can come from sensors, behavior, location, declarations, or higher authority. It is rarely just one thing.
== 07 / Positive Identification (PID) ==


Just like AAR, this is coordination and discipline under pressure. And unlike refueling, the consequences of getting it wrong don’t end with embarrassment.
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.


Execution:
{| class="wikitable" style="width:100%;"
|-
! Type !! Description
|-
| '''Electronic PID''' || IFF interrogation, Link picture, NCTR, controller declaration. Most common form in BVR.
|-
| '''Visual PID''' || Confirm number, type, livery, armament, heading, speed. Requires merge or VID pass.
|-
| '''Ground Targets''' || Correlate with pre-briefed target. CRC issues Cleared to Engage before weapons release.
|}


The pilot (or flight) must:
=== Ground Target Engagement ===


* Correlate the radar contact with the assigned track from CRC / AWACS
{| class="wikitable" style="width:100%;"
* Verify Mode 4 / Mode 5 IFF response (if applicable)
|-
* Confirm that no friendly aircraft are in the engagement basket (deconfliction by altitude, heading, or timing)
! style="width:25%;" | Station !! Phrase
* Compare target BRAA with declared hostile tracks from controlling agency
|-
* Assess target behavior (aspect, speed, formation, emissions)
| Flight Lead || {CS} Identified {Target Description} {if pre-briefed: Matches Target __}
* Ensure ROE criteria are met before weapons release
|-
| CRC || Cleared to Engage
|-
| Flight Lead || In Hot, {Target Description}, {Ingress Heading}
|-
| CRC || Cleared Hot / Abort
|-
| Flight Lead || Completed Engagement
|-
| CRC || Continue as Fragged / {Additional Instructions}
|}


PID is achieved when the flight lead is confident that:
----


* The contact matches the declared hostile track
== 08 / Air-to-Air Combat ==
* The contact does not respond correctly to IFF challenge
* The contact is operating in a hostile declared area or violating airspace
* Higher control (CRC / AWACS) has declared the contact HOSTILE
* Visual confirmation (if required by ROE) has been achieved


There are generally three practical forms of PID:
Air combat is primarily carried out by CAP aircraft — the two main types being '''DCA''' (Defensive Counter Air) and '''OCA''' (Offensive Counter Air). Before a Commit, the controller holds radio priority. After Commit, the fighters hold priority.


'''Electronic PID'''<br />
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'''.
Achieved via IFF interrogation, Link picture, NCTR (Non-Cooperative Target Recognition – radar attempting to classify aircraft type by engine modulation), and controller declaration.<br />
This is the most common in modern BVR.


Engagement of Groundbased Targets
=== Contact Declaration ===


{| class="wikitable"
{| class="wikitable" style="width:100%;"
|-
|-
! style="text-align: left;"| Station
! Declaration !! Meaning !! Engagement Authority
! style="text-align: left;"| Phrase
|-
|-
! style="text-align: left;"| Flight Lead
| '''BOGEY''' || Unknown — identity not confirmed || Not cleared to engage
! style="text-align: left;"| {CS} Identified {Target Description} {if prebriefed: Matches Target __}
|-
|-
! style="text-align: left;"| CRC
| '''OUTLAW''' || Originates from known or suspected hostile area || Not cleared to engage; escalation criteria apply
! style="text-align: left;"| Cleared to Engage
|-
|-
! style="text-align: left;"| Flight Lead
| '''SPADES''' || No valid IFF response on interrogation || Not cleared to engage; escalation criteria apply
! style="text-align: left;"| In hot {Target Description / Target ID} {Ingress Heading}
|-
|-
! style="text-align: left;"| CRC
| '''BANDIT''' || Positively identified as enemy || Not cleared to engage
! style="text-align: left;"| Cleared Hot / Abort
|-
|-
! style="text-align: left;"| Flight Lead
| '''HOSTILE''' || Confirmed enemy IAW ROE || Cleared to engage
! style="text-align: left;"| Completed Engagement
|-
|-
! style="text-align: left;"| CRC
| '''NEUTRAL''' || Neutral aircraft || Not cleared to engage
! style="text-align: left;"| Continue as Fragged / Additional Instructions
|-
| '''FRIENDLY''' || Confirmed friendly || Not cleared to engage
|}
|}


Engagement of Air Targets
A BOGEY, OUTLAW, or SPADES classification does not authorize engagement. Escalation to HOSTILE requires either a controller DECLARE or pre-briefed escalation criteria being met (e.g. radar lock on friendly, threatening posture, point of origin).


'''PID''' for Aircraft can be achieved through Declaration by a CRC or Visual Identification
=== Phase 1 — Pre-Commit ===


In some cases a CRC will require an Intercepting Fighter to archive a Visual Identification
The flight arrives at its prebriefed CAP position with FENCE IN complete and radars in sanitization configuration. The controller holds picture responsibility.


'''Visual PID'''<br />
{| class="wikitable" style="width:100%;"
The pilot must visually confirm number and type of aircraft, (registration), color, armament, heading and rough speed<br />
|-
This often requires merge or VID pass.
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || {CRC-CS} {CS} PICTURE
|-
| CRC || {CS} {Nr of Groups}, {Group Label} BULLSEYE {Bearing/Range} {Altitude} TRACKING {Direction} {Declaration} {Nr of Contacts}
|}


NOTE: In DCS acquiring the Registration might be considerably difficult because of low resolution monitors and similar. Therefore this is optional
The flight processes the picture, builds SA, and evaluates commit criteria. If commit criteria are not yet met, the flight continues sanitizing and requests updated pictures as needed.


NOTE: Color does not necessarily mean the color of the aircraft but if possible the name of the country the aircraft's livery corresponds to. ie: “German / Russian / Syrian Airforce colors”
=== Phase 2 — Commit ===


'''A2A Combat'''
==== Fighter-Initiated ====


For coordination the air combat area is divided into different sectors of control called Lanes. Each lane usually has a CRC or AWACS attached to it. In case of an CRC this is usually referred to as GCI
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| colspan="2" style="text-align:center;" | ''Commit criteria met''
|-
| Flight Lead || {CRC-CS} {CS} RECOMMEND COMMIT {Group Label}
|-
| CRC || {CS} COMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration} {Nr of Contacts}
|-
| Flight Lead || COMMIT {Group Label} {CS}
|}


Air combat is mainly carried out by CAP (Combat Air Patrol) Aircraft there are a great amount of variations of such but the two most important overruling types are DCA (Defensive Counter Air) and OCA (Offensive Counter Air)
==== Controller-Initiated ====


We highly recommend you to watch this video series on BVR combat to get a better understanding on Strategic Air to Air Combat [https://www.youtube.com/playlist?list=PLd5Qdmhmp3Y7wxYI4cVxcDPdswhj_Zgpi <u>https://www.youtube.com/playlist?list=PLd5Qdmhmp3Y7wxYI4cVxcDPdswhj_Zgpi</u>]
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| CRC || {CS} COMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration} {Nr of Contacts}
|-
| Flight Lead || {CS} COMMIT
|}


Each intercept / engagement starts with the controller or the fighter initiating a Commit, before the commit the Controller has Priority, after the commit this changes. As the fighters close in on the group they will have better situational awareness on the Target. Until the intercept concludes the Fighter’s have radio priority.
After Commit, the flight takes radio priority. The controller shifts to tactical or advisory control as briefed.


The most important metric here is Targeting Range, which is an agreed-upon distance at which every contact needs to be intercepted / engaged
=== Phase 3 — Targeting and Declaration ===


A group inside the Targeting Range that no fighter has taken responsibility for is labelled as “Untargeted”
The flight assigns group responsibility and confirms classification before employing weapons.


'''Fighter Initiated'''
{| class="wikitable" style="width:100%;"
 
|-
{| class="wikitable"
! style="width:25%;" | Station !! Phrase
|-
|-
! style="text-align: left;"| Station
| Flight Lead || {CRC-CS} {CS} DECLARE {Group Label or Bullseye Position}
! style="text-align: left;"| Phrase
|-
|-
! colspan="2" style="text-align: center;"| Once all commit criteria are met. The Flight will suggest a Commit
| CRC || {Group Label} DECLARED {HOSTILE / BOGEY / FRIENDLY / UNABLE}
|-
|-
! style="text-align: left;"| Flight Lead
| colspan="2" style="text-align:center;" | ''Flight lead assigns targeting responsibility and announces tactical plan (intraflight)''
! style="text-align: left;"| {CS} Recommend Commit
|-
|-
! colspan="2" style="text-align: center;"| The Controller will evaluate the situation and initiate a Commit based on threat levels
| Flight Lead || ''(intraflight) {CS} TARGET {Group Label} {Tactic}''
|-
|-
! style="text-align: left;"| CRC
| colspan="2" style="text-align:center;" | ''Once group appears on radar''
! style="text-align: left;"| {GCI-CS} {Nr of groups}, {Group Description} {Fighter-CS} Commit
|-
|-
! style="text-align: left;"| Flight Lead
| Flight Lead || {CRC-CS} {CS} TARGETED {Group Label}
! style="text-align: left;"| {CS}
|}
|}


'''Controller Initiated'''
If DECLARE returns UNABLE or FURBALL, weapons employment is not authorized until classification is resolved.
 
=== Phase 4 — MELD, Sort, and JUDY ===


{| class="wikitable"
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || {CRC-CS} {CS} MELD
|-
| colspan="2" style="text-align:center;" | ''All flight members shift radars from sanitization to assigned group''
|-
|-
! Station
| Flight Lead || ''(intraflight) FLIGHT SORT {Criteria}''
! Phrase
|-
|-
! style="text-align: center;"| CRC
| Wingmen || ''(intraflight) #2 SORTED · #3 SORTED · #4 SORTED''
! {GCI-CS} {Nr of groups}, {Group Description} {Fighter-CS} Commit {+ VID if required}
|-
|-
! Flight Lead
| colspan="2" style="text-align:center;" | ''Once sort is complete and no further controller guidance is needed''
! {CS} Commit.
|-
| Flight Lead || {CRC-CS} {CS} JUDY
|}
|}


Once the Formation has the Contact on Radar and no further guidance is required:
After JUDY the controller minimizes transmissions. The flight manages the intercept autonomously.
 
=== Phase 5 — Weapon Employment ===


{| class="wikitable"
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
|-
! style="text-align: left;"| Station
| Flight Lead || ''(intraflight) {Wingman CS} ENGAGE''
! style="text-align: left;"| Phrase
|-
|-
! style="text-align: left;"| Flight Lead
| Firing Aircraft || {CRC-CS} {CS} FOX THREE {Group Label} {Contact Description}
! style="text-align: left;"| {CS} Judy
|-
| CRC || COPY SHOT
|}
|}


Once the Formation has tally on the Target
Multiple shots in one transmission are acceptable.
=== Phase 6 — Out, Dropping, and Reset ===


{| class="wikitable"
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
| Flight Lead || {CRC-CS} {CS} OUT {Direction} DROPPING {Group Label}
|-
|-
! Station
| colspan="2" style="text-align:center;" | ''Flight returns to sanitization radar settings. Controller resumes monitoring of dropped group.''
! Phrase
|-
|-
! Flight Lead
| colspan="2" style="text-align:center;" | ''Once weapon effects are assessed and the flight returns to prebriefed position''
! {CS} Tally
|-
| Flight Lead || {CRC-CS} {CS} RESET
|}
|}


'''Contact Declaration'''
RESET implies DROPPING and returns all targeting responsibility to the controller.
 
There are 5 possible Declarations.


# Bogey - Unknown | Not Cleared to be Engaged
If the dropped group turns hot again before RESET is complete:
# Bandit - Enemy | Not Cleared to be Engaged
# Hostile - Enemy | Cleared to be Engaged
# Neutral - Neutral (Neither a Friendly or Hostile) | Not Cleared to be Engaged
# Friendly - Friendly | Not Cleared to be Engaged


{| class="wikitable"
{| class="wikitable" style="width:100%;"
|-
|-
! Station
! style="width:25%;" | Station !! Phrase
! Phrase
|-
|-
! Flight Lead
| CRC || {CS} RECOMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration}
! {CRC-CS} Declare {Group Label or Bullseye Position)
|-
|-
! CRC
| Flight Lead || {CS} COMMIT
! {Group Label} Declared …
|}
|}


'''Weapon Release'''
=== Phase 7 — In (Follow-up Engagement) ===
 
If the tactic requires a follow-up shot rather than RESET:


{| class="wikitable"
{| class="wikitable" style="width:100%;"
|-
! style="width:25%;" | Station !! Phrase
|-
|-
! Station
| Flight Lead || {CRC-CS} {CS} IN {Direction} TARGETED {Group Label}
! Phrase
|-
|-
! Aircraft employing Weaponary
| Flight Lead || {CRC-CS} {CS} MELD
! {CS} Fox-{1,2,3} {Group Label or Bullseye Position} {Further Description of Shot upon target within Group}
|-
|-
! CRC
| colspan="2" style="text-align:center;" | ''Re-sort as required, then proceed to Phase 5''
! Copy Shot
|}
|}
----


'''Brevity Words'''
== 09 / Brevity Words ==


'''AS FRAGGED''': Unit or element will perform exactly as briefed or scheduled.
{| class="wikitable" style="width:100%;"
 
|-
'''WITH EXCEPTIONS:''' Unit or element will perform as briefed with additional given
! style="width:22%;" | Term !! Definition
 
|-
<blockquote>exceptions
| '''AS FRAGGED''' || Unit will perform exactly as briefed or scheduled.
</blockquote>
|-
'''ALPHA CHECK''': Verification of the position of a BULLSEYE or related point.
| '''WITH EXCEPTIONS''' || Unit will perform as briefed with stated exceptions.
 
|-
'''ANGELS''': Height of FRIENDLY aircraft in thousands of feet MSL.
| '''ALPHA CHECK''' || Verification of the position of a Bullseye or related point.
 
|-
'''AUTHENTICATE''': Method to verify communication with allied agencies.
| '''ANGELS''' || Height of friendly aircraft in thousands of feet MSL.
 
|-
'''PLAYTIME''': Time aircraft can remain on station (hours + minutes).
| '''AUTHENTICATE''' || Method to verify communication with allied agencies.
 
|-
'''PICTURE''': Request for mission information in digital bullseye format.
| '''PLAYTIME''' || Time aircraft can remain on station (hours + minutes).
 
|-
'''BRAA''': Bearing, Range, Altitude, and Aspect relative to a FRIENDLY
| '''PICTURE''' || Request for mission information in digital bullseye format.
 
|-
<blockquote>aircraft.
| '''BRAA''' || Bearing, Range, Altitude, and Aspect relative to a friendly aircraft.
</blockquote>
|-
'''BULLSEYE''': Reference point used to establish positions (bearing + range).
| '''BULLSEYE''' || Reference point used to establish positions (bearing + range).
 
|-
'''GROUP(S)''': Any number of contacts within 3 NM of each other.
| '''GROUP(S)''' || Any number of contacts within 3 nm of each other.
 
|-
'''AZIMUTH''': Two GROUPs separated laterally (referenced by cardinal
| '''AZIMUTH''' || Two groups separated laterally (by cardinal directions).
 
|-
<blockquote>directions).
| '''RANGE''' || Two groups separated along a line of bearing (LEAD/TRAIL).
</blockquote>
|-
'''RANGE''': Two GROUPs separated along a line of bearing (LEAD/TRAIL
| '''STACK''' || Two or more contacts in a group with ≥10,000 ft altitude separation.
 
|-
<blockquote>GROUP).
| '''MONITOR''' || Maintain sensor awareness on a group or object.
</blockquote>
|-
'''STACK''': Two or more contacts within a GROUP with altitude separation
| '''CLARA''' || Radarscope clear of enemy contacts.
 
|-
<blockquote>(≥10,000 ft).
| '''CLEAN''' || No radar contacts on bandits, bogies, or aircraft of interest.
</blockquote>
|-
'''MONITOR''': Maintain sensor awareness on a GROUP or object.
| '''DRAG / COLD''' || Contact aspect stabilized 000–070°.
 
|-
'''CLARA''': Radarscope clear of enemy contacts.
| '''BEAM''' || Contact aspect stabilized 070–110°.
 
|-
'''CLEAN''': No radar contacts on BANDITS, BOGIES, or aircraft of interest.
| '''FLANK''' || Contact aspect stabilized 110–160°.
 
|-
'''DRAG / COLD''': Contact stabilized 000–070°.
| '''HOT / HEAD ON''' || Contact aspect stabilized 160–180°.
 
|-
'''BEAM''': Contact stabilized 070–110°.
| '''TRACKING''' || Direction of flight/movement (in bullseye format).
 
|-
'''FLANK''': Contact stabilized 110–160°.
| '''MARSHALLING''' || Positioning forces at a point for offensive operations.
 
|-
'''HOT / HEAD ON''': Contact stabilized 160–180°.
| '''BANDIT''' || Positively identified enemy (not clearance to engage).
 
|-
'''TRACKING''': Direction of flight/movement (in BULLSEYE format).
| '''BOGEY''' || Unknown contact.
 
|-
'''MARSHALL(ING)''': Positioning forces at a point for offensive operations.
| '''HOSTILE''' || Enemy contact cleared for engagement (IAW ROE).
 
|-
'''BANDIT''': Positively identified enemy (not clearance to engage).
| '''FURBALL''' || Friendly and non-friendly aircraft within 5 nm.
 
|-
'''BOGEY''': Unknown contact.
| '''FOX ONE''' || Semi-active radar-guided missile fired.
 
|-
'''HOSTILE''': Enemy contact cleared for engagement (IAW ROE).
| '''FOX TWO''' || IR-guided missile fired.
 
|-
'''FURBALL''': FRIENDLY and non-FRIENDLY aircraft within 5 NM.
| '''FOX THREE''' || Active radar-guided missile fired.
 
|-
'''FOX (ONE)''': Launch semi-active radar-guided missile.
| '''ENGAGE''' || Directive to fire on a target.
 
|-
'''FOX (TWO)''': Launch IR-guided missile.
| '''GATE''' || Fly as fast as possible — afterburner.
 
|-
'''FOX (THREE)''': Launch active radar-guided missile.
| '''BUSTER''' || Fly at maximum continuous speed — military power.
 
|-
'''ENGAGE''': Directive to fire on a target.
| '''BREAK''' || (Direction) Immediate maximum-performance turn.
 
|-
'''GATE''': Fly as fast as possible (afterburner).
| '''VISUAL''' || Sighting of a friendly aircraft, ground unit, or ship.
 
|-
'''BUSTER''': Fly at maximum continuous speed (military power).
| '''BLIND''' || No visual contact with friendly.
 
|-
'''BREAK''': (Direction): Immediate maximum-performance turn.
| '''TALLY''' || Sighting of a target or enemy aircraft.
 
|-
'''VISUAL''': Sighting of FRIENDLY aircraft/ground/ship.
| '''NO JOY''' || No visual contact with target or enemy.
 
|-
'''BLIND''': No visual contact with FRIENDLY.
| '''MERGED''' || Radar tracks have come together (3–5 nm).
 
|-
'''TALLY''': Sighting of a target/enemy.
| '''JUDY''' || Aircrew has control of intercept; controller minimizes comms.
 
|-
'''NO JOY''': No visual contact with target/enemy.
| '''DECLARE''' || Inquiry as to track ID. Responses: FRIENDLY / BOGEY / BANDIT / HOSTILE / NEUTRAL / UNABLE / FURBALL.
 
|-
'''MERGE(D)''': Radar tracks have come together (3–5 NM).
| '''BOGEY DOPE''' || Request for info on indicated or nearest group in BRAA format.
 
|-
'''JUDY''': Aircrew has control of intercept / Radar Contact; controller
|'''<big>Commit</big>'''
 
|Directive to engage / move to intercept
<blockquote>minimizes comms.
|-
</blockquote>
| '''TARGETING''' || Fighter has acquired assigned group and assumes responsibility.
'''DECLARE''': Inquiry as to ID of track (responses: FRIENDLY, BOGEY,
|-
 
| '''CONTACT''' || Individual radar return within a group.
<blockquote>BANDIT, HOSTILE, NEUTRAL, UNABLE, FURBALL). Positional
|-
 
| '''HEAVY''' || Group with more than 3 elements.
data included.
|-
</blockquote>
| '''HIGH''' || Target altitude above 40,000 ft.
'''BOGEY DOPE''': Request info on indicated or nearest GROUP in BRAA format.
|-
 
| '''FAST''' || Target speed 600–900 kts or Mach 1.0–1.5.
'''TARGETING''': Fighter has acquired assigned GROUP and assumes
|-
 
| '''VERY FAST''' || Target speed above 900 kts / Mach 1.5+.
<blockquote>responsibility.
|}
</blockquote>
'''CONTACT''': Individual radar return within a GROUP.
 
'''HEAVY''': Known GROUP with &gt;3 elements.
 
'''HIGH''': Target altitude above 40,000 ft.
 
'''FAST''': Target speed 600–900 kts GS or Mach 1.0–1.5.
 
'''VERY FAST''': Target speed &gt;900 kts / Mach 1.5+.

Latest revision as of 14:38, 20 May 2026

SOURCE — Tactical Communications Guide
Covers: Control Architecture · Check-In · AAR · PID · Air-to-Air Combat · Brevity
Information is based on real-world procedures but modified to cater to DCS limitations

01 / Control Architecture

ASACS (Airborne Surveillance and Control System) is the integrated command-and-control framework linking airborne surveillance platforms, ground-based control centers, and air defense assets into a single coordinated system. ASACS defines the doctrine, communications architecture, and authority relationships governing how AWACS, CRCs, and radar sites share data, build a Recognized Air Picture, and allocate control of aircraft and weapons.

AWACS (Airborne Warning and Control System) is an airborne command-and-control platform with long-range radar and battle management consoles. It provides surveillance, identification, and tactical control of aircraft over extended ranges, particularly where ground radar coverage is limited.

CRC (Control and Reporting Center) is a ground-based air command-and-control facility responsible for surveillance, identification, and tactical control within a designated airspace sector. It fuses multiple radar sources to generate a Recognized Air Picture and provides fighter control and airspace coordination.

GCI (Ground Controlled Intercept) is the tactical function of directing fighter aircraft to intercept airborne targets using ground-based radar. GCI refers to the activity performed by trained controllers, not a specific facility.

Control Types

CLOSE LOOSE BROADCAST
POSITIVE ADVISORY POSITIVE ADVISORY
TARGETS SELECTION IC IC IC IC PIL
TACTICAL SELECTION IC IC PIL PIL PIL
GEOMETRY IC IC PIL PIL PIL
SEPARATION IC PIL IC PIL PIL
PICTURE FORMAT HDG – SPD – ALT BRAA or BULLSEYE BULLSEYE

PIL = Pilot's Responsibility · IC = Intercept Controller's Responsibility

02 / Intercept Controller

The Intercept Controller (IC) guides military assets in the tactical environment. When airborne on an AEW/AWACS platform the role is called Weapon Controller (WC) — this manual uses IC throughout for convenience.

Primary IC responsibilities: target selection and assignment · PICTURE reporting · initial fighter vector (COMMIT)

Supported operations: QRA · AIR TO AIR REFUELLING · COMBAT AIR PATROL

03 / Standard Calls

State Call

A State Call reports combat status to the IC: weapons, fuel, and playtime in a fixed order.

Example: "State is 602+ 10000lbs 90M"

# FOX-3 # FOX-1 # FOX-2 Gun Fuel Playtime
6 0 2 + 10,000 lbs 90 min

6× FOX-3, 0× FOX-1, 2× FOX-2, gun available, 10,000 lbs fuel, 90 minutes playtime.

BRAA Call

Tactical control format: Bearing, Range, Altitude, Aspect relative to the specified friendly aircraft.

Groups Format Bearing Range Altitude Aspect Declaration
Single Group BRAA 320 30 nm 20,000 ft Flanking BOGEY

Flight Check / Frequency Change

Executed when switching the flight to a new frequency. Intraflight = flight-internal frequency. Interflight = control agency frequency.

Station Phrase
ATC {CS} Push Button _
Flight Lead (interflight) {CS} Push Button _
Flight Lead (intraflight) Push {UHF/VHF, Radio 1/2} Button _
All flight members switch to channel _
Flight Lead {CS} Check
Wingman 2
Element Lead 3
Element Wingman 4
Flight Lead proceeds with initial call as normal

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 a Controlling Station

Station Phrase
Pilot {CRC-CS} {CS} Authenticate E-A
ATC Come back G
ATC Authenticate J-U
Pilot Come back R
ATC Good Authentication

FENCE IN

04 / Check-In Procedures

CS = Callsign (e.g. SHADOW 1). Not every procedure applies to every mission.

Check In on Radar — Transit Control

Station Phrase
Flight Check
Flight Lead {CRC-CS} {CS} {Flight Level}
Authentication
CRC {CS}, Identified, {Instructions}

NOTE: Close Positive Control is inferred.

Check In with Weapons Controller

Station Phrase
Flight Check
Authentication
Flight Lead {CRC-CS} {CS} Mission Nr {MSN} {Position} {Altitude} {Playtime} {As Fragged / With Exceptions}
CRC {CS}, Identified, {Control Type}, Alpha Check Bullseye {Position}
Flight Lead Same {Alpha Check}

NOTE: Bullseye cannot be used for initial position calls — only valid after Alpha Check.

05 / Training Range & Formations

Attack Run

Station Phrase
Turning in for attack run
Aircraft {CS} In Hot, Heading ___
Tactical Controller Cleared Hot (or: Abort, Turn Left/Right HDG)
Upon completion
Aircraft {CS} Off Target

Repeated for every attack run. Multiple aircraft on the same target: ASACS issues traffic information and may require visual separation.

Formation Splits

Station Phrase
Flight Lead {CS}, request split into {number} parts of {number} each
CRC {CS}, report ready for {Right / Left Hand} {Split Type}

Vertical (Altitude)

Station Phrase
Flight Lead {CS}, ready
CRC {CS 2}, descend {FL}
Flight Lead 2 {CS 2}, descending {FL}
CRC {CS 2}, squawk {number} · identified
Repeat for each new flight

Lateral (Vector)

Station Phrase
Flight Lead {CS}, ready
CRC {CS 2} for split turn {side} {degrees}
Flight Lead {CS 2} for split turn {side} {degrees}
CRC {CS 2} squawk {number} · identified
Repeat for each new flight

Join-Up

Station Phrase
Flight Lead {CS} requesting join-up with {CS 2}
CRC {CS 2}, confirm join-up clearance for {CS}
Flight Lead 2 {CS 2}, {CS} is cleared to join up
CRC {CS}, fly {heading} and climb/descend to {angels}
Flight Lead {CS}, fly {heading} and climb/descend to {angels}
CRC {CS}, report {CS 2} in sight
Flight Lead {CS}, {CS 2} in sight, {position}
CRC Visual join-up approved — report formation tight
Flight Lead 2 {CS 2}, formation tight
CRC {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

Level Usage
ALPHA Receivers departing · Emergency
BRAVO Tanker base level
CHARLIE Receiver evasive
DELTA Receivers approaching

RV Alpha Procedure

Receiver: fly 2,000 ft below AAR altitude · follow IC heading · declare JUDY on radar contact · declare VISUAL when in sight · weapons safe and radar off · take ECHELON LEFT when authorized.

Station Phrase
CRC {CS} Proceed Tanker BRAA {BRAA} — RV Alpha — Tanker Freq {Freq} {Instructions}
Flight Lead {CS} Roger, RV Alpha, Tanker Freq {Freq} {Readback}
Once flight has radar contact with tanker
Flight Lead {Flight Name} Judy 1, Weapons Safe
All wingmen (in order) 2, 3, 4… Weapons Safe
Once tanker is in sight
CRC {CS} Tanker {x} o'clock, report visual
Flight Lead {CS} Nose Cold, visual with tanker
CRC {CS} Roger, contact boom
Switch to DCS tanker frequency

NOTE: Flight Lead must confirm Nose Cold with wingmen on intraflight before reporting to ATC.

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, Link picture, NCTR, controller declaration. Most common form in BVR.
Visual PID Confirm number, type, livery, armament, heading, speed. Requires merge or VID pass.
Ground Targets Correlate with pre-briefed target. CRC issues Cleared to Engage before weapons release.

Ground Target Engagement

Station Phrase
Flight Lead {CS} Identified {Target Description} {if pre-briefed: Matches Target __}
CRC Cleared to Engage
Flight Lead In Hot, {Target Description}, {Ingress Heading}
CRC Cleared Hot / Abort
Flight Lead Completed Engagement
CRC Continue as Fragged / {Additional Instructions}

08 / Air-to-Air Combat

Air combat is primarily carried out by CAP aircraft — the two main types being DCA (Defensive Counter Air) and OCA (Offensive Counter Air). Before a Commit, the controller holds radio priority. After Commit, the fighters hold priority.

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.

Contact Declaration

Declaration Meaning Engagement Authority
BOGEY Unknown — identity not confirmed 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 Not cleared to engage
HOSTILE Confirmed enemy IAW ROE Cleared to engage
NEUTRAL Neutral aircraft Not cleared to engage
FRIENDLY Confirmed friendly Not cleared to engage

A BOGEY, OUTLAW, or SPADES classification does not authorize engagement. Escalation to HOSTILE requires either a controller DECLARE or pre-briefed escalation criteria being met (e.g. radar lock on friendly, threatening posture, point of origin).

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.

Station Phrase
Flight Lead {CRC-CS} {CS} PICTURE
CRC {CS} {Nr of Groups}, {Group Label} BULLSEYE {Bearing/Range} {Altitude} TRACKING {Direction} {Declaration} {Nr of Contacts}

The flight processes the picture, builds SA, and evaluates commit criteria. If commit criteria are not yet met, the flight continues sanitizing and requests updated pictures as needed.

Phase 2 — Commit

Fighter-Initiated

Station Phrase
Commit criteria met
Flight Lead {CRC-CS} {CS} RECOMMEND COMMIT {Group Label}
CRC {CS} COMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration} {Nr of Contacts}
Flight Lead COMMIT {Group Label} {CS}

Controller-Initiated

Station Phrase
CRC {CS} COMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration} {Nr of Contacts}
Flight Lead {CS} COMMIT

After Commit, the flight takes radio priority. The controller shifts to tactical or advisory control as briefed.

Phase 3 — Targeting and Declaration

The flight assigns group responsibility and confirms classification before employing weapons.

Station Phrase
Flight Lead {CRC-CS} {CS} DECLARE {Group Label or Bullseye Position}
CRC {Group Label} DECLARED {HOSTILE / BOGEY / FRIENDLY / UNABLE}
Flight lead assigns targeting responsibility and announces tactical plan (intraflight)
Flight Lead (intraflight) {CS} TARGET {Group Label} {Tactic}
Once group appears on radar
Flight Lead {CRC-CS} {CS} TARGETED {Group Label}

If DECLARE returns UNABLE or FURBALL, weapons employment is not authorized until classification is resolved.

Phase 4 — MELD, Sort, and JUDY

Station Phrase
Flight Lead {CRC-CS} {CS} MELD
All flight members shift radars from sanitization to assigned group
Flight Lead (intraflight) FLIGHT SORT {Criteria}
Wingmen (intraflight) #2 SORTED · #3 SORTED · #4 SORTED
Once sort is complete and no further controller guidance is needed
Flight Lead {CRC-CS} {CS} JUDY

After JUDY the controller minimizes transmissions. The flight manages the intercept autonomously.

Phase 5 — Weapon Employment

Station Phrase
Flight Lead (intraflight) {Wingman CS} ENGAGE
Firing Aircraft {CRC-CS} {CS} FOX THREE {Group Label} {Contact Description}
CRC COPY SHOT

Multiple shots in one transmission are acceptable.

Phase 6 — Out, Dropping, and Reset

Station Phrase
Flight Lead {CRC-CS} {CS} OUT {Direction} DROPPING {Group Label}
Flight returns to sanitization radar settings. Controller resumes monitoring of dropped group.
Once weapon effects are assessed and the flight returns to prebriefed position
Flight Lead {CRC-CS} {CS} RESET

RESET implies DROPPING and returns all targeting responsibility to the controller.

If the dropped group turns hot again before RESET is complete:

Station Phrase
CRC {CS} RECOMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration}
Flight Lead {CS} COMMIT

Phase 7 — In (Follow-up Engagement)

If the tactic requires a follow-up shot rather than RESET:

Station Phrase
Flight Lead {CRC-CS} {CS} IN {Direction} TARGETED {Group Label}
Flight Lead {CRC-CS} {CS} MELD
Re-sort as required, then proceed to Phase 5

09 / Brevity Words

Term Definition
AS FRAGGED Unit will perform exactly as briefed or scheduled.
WITH EXCEPTIONS Unit will perform as briefed with stated exceptions.
ALPHA CHECK Verification of the position of a Bullseye or related point.
ANGELS Height of friendly aircraft in thousands of feet MSL.
AUTHENTICATE Method to verify communication with allied agencies.
PLAYTIME Time aircraft can remain on station (hours + minutes).
PICTURE Request for mission information in digital bullseye format.
BRAA Bearing, Range, Altitude, and Aspect relative to a friendly aircraft.
BULLSEYE Reference point used to establish positions (bearing + range).
GROUP(S) Any number of contacts within 3 nm of each other.
AZIMUTH Two groups separated laterally (by cardinal directions).
RANGE Two groups separated along a line of bearing (LEAD/TRAIL).
STACK Two or more contacts in a group with ≥10,000 ft altitude separation.
MONITOR Maintain sensor awareness on a group or object.
CLARA Radarscope clear of enemy contacts.
CLEAN No radar contacts on bandits, bogies, or aircraft of interest.
DRAG / COLD Contact aspect stabilized 000–070°.
BEAM Contact aspect stabilized 070–110°.
FLANK Contact aspect stabilized 110–160°.
HOT / HEAD ON Contact aspect stabilized 160–180°.
TRACKING Direction of flight/movement (in bullseye format).
MARSHALLING Positioning forces at a point for offensive operations.
BANDIT Positively identified enemy (not clearance to engage).
BOGEY Unknown contact.
HOSTILE Enemy contact cleared for engagement (IAW ROE).
FURBALL Friendly and non-friendly aircraft within 5 nm.
FOX ONE Semi-active radar-guided missile fired.
FOX TWO IR-guided missile fired.
FOX THREE Active radar-guided missile fired.
ENGAGE Directive to fire on a target.
GATE Fly as fast as possible — afterburner.
BUSTER Fly at maximum continuous speed — military power.
BREAK (Direction) Immediate maximum-performance turn.
VISUAL Sighting of a friendly aircraft, ground unit, or ship.
BLIND No visual contact with friendly.
TALLY Sighting of a target or enemy aircraft.
NO JOY No visual contact with target or enemy.
MERGED Radar tracks have come together (3–5 nm).
JUDY Aircrew has control of intercept; controller minimizes comms.
DECLARE Inquiry as to track ID. Responses: FRIENDLY / BOGEY / BANDIT / HOSTILE / NEUTRAL / UNABLE / FURBALL.
BOGEY DOPE Request for info on indicated or nearest group in BRAA format.
Commit Directive to engage / move to intercept
TARGETING Fighter has acquired assigned group and assumes responsibility.
CONTACT Individual radar return within a group.
HEAVY Group with more than 3 elements.
HIGH Target altitude above 40,000 ft.
FAST Target speed 600–900 kts or Mach 1.0–1.5.
VERY FAST Target speed above 900 kts / Mach 1.5+.
Retrieved from "https://wiki.sourcedcs.page/index.php?title=General/Tactical_Communication&oldid=307"
Last modified
This page was last edited on 20 May 2026, at 14:38.