Toggle menu
10
18
30
244
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
Niknam3 (talk | contribs)
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)
No edit summary
Line 1: Line 1:
Tactical Communication
__NOTOC__
__NOEDITSECTION__


'''ASACS (Airborne Surveillance and Control System)'''
<!-- PAGE HEADER -->
<div style="font-size:0.58rem; letter-spacing:5px; color:#7a7875; border-bottom:1px solid #c8c5bf; padding-bottom:6px; margin-bottom:6px;">[[Main Page|HOME]] &nbsp;/&nbsp; GENERAL &nbsp;/&nbsp; TACTICAL COMMUNICATION</div>
<div style="font-size:0.6rem; letter-spacing:3px; color:#9a9690; margin-bottom:28px;">SOURCE DCS — COMMUNICATIONS DOCTRINE</div>


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.
<!-- SECTION 01 -->
<div style="font-size:0.58rem; letter-spacing:5px; color:#7a7875; border-bottom:1px solid #c8c5bf; padding-bottom:5px; margin-bottom:14px;">&#9632;&nbsp;&nbsp;01&nbsp;&nbsp;/&nbsp;&nbsp;CONTROL ARCHITECTURE</div>
<div style="padding:4px 0 8px 14px; line-height:1.9; margin-bottom:6px;">
'''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.
</div>
<div style="padding:4px 0 8px 14px; line-height:1.9; margin-bottom:6px;">
'''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.
</div>
<div style="padding:4px 0 8px 14px; line-height:1.9; margin-bottom:6px;">
'''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.
</div>
<div style="padding:4px 0 28px 14px; line-height:1.9;">
'''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.
</div>


'''AWACS (Airborne Warning and Control System)'''
<!-- SECTION 02 -->
<div style="font-size:0.58rem; letter-spacing:5px; color:#7a7875; border-bottom:1px solid #c8c5bf; padding-bottom:5px; margin-bottom:14px;">&#9632;&nbsp;&nbsp;02&nbsp;&nbsp;/&nbsp;&nbsp;INTERCEPT CONTROLLER</div>
<div style="padding:4px 0 14px 14px; line-height:1.9;">
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.


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.
Primary IC responsibilities: target selection and assignment · PICTURE reporting · initial fighter vector (COMMIT)


'''CRC (Control and Reporting Center)'''
Supported operations: '''QRA &nbsp;·&nbsp; AIR TO AIR REFUELLING &nbsp;·&nbsp; COMBAT AIR PATROL'''
</div>


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.
<div style="background:#edecea; border:1px solid #c8c5bf; padding:12px 16px; margin:0 0 28px 14px; font-size:0.75rem;">
 
<div style="font-size:0.58rem; letter-spacing:3px; color:#7a7875; margin-bottom:10px;">CONTROL TYPES</div>
'''GCI (Ground Controlled Intercept)'''
{| style="width:100%; border-collapse:collapse; font-size:0.75rem;"
 
|-
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.
! style="text-align:left; padding:4px 8px; border-bottom:1px solid #c8c5bf; font-weight:600; letter-spacing:1px;" | TYPE
 
! style="text-align:left; padding:4px 8px; border-bottom:1px solid #c8c5bf; font-weight:600; letter-spacing:1px;" | DESCRIPTION
'''Intercept Controller'''
|-
 
| style="padding:5px 8px;" | Close Positive Control
The controller in charge of guiding military assets in a tactical environment.
| style="padding:5px 8px; color:#4a4845;" | IC directs all aspects of the intercept
 
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:
 
* QRA
* AIR TO AIR REFUELLING
* COMBAT AIR PATROL
 
The IC is responsible for:
 
- Selection and assignment of targets
 
- Providing information about the PICTURE
 
- Giving the initial vector to air defense fighters (COMMIT)
 
Control Types
 
[[File:media/image2.png|601x266px]]
 
PIL = Pilots Responsibility
 
IC = Intercept Controllers Responsibility
 
''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''
| style="padding:5px 8px; background:#f4f3f0;" | Broadcast Control
! style="text-align: left;"| ''# FOX-1''
| style="padding:5px 8px; background:#f4f3f0; color:#4a4845;" | IC provides picture; PIL assumes responsibility
! 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
| style="padding:5px 8px;" | Advisory
! style="text-align: left;"| 0
| style="padding:5px 8px; color:#4a4845;" | PIL fully responsible — IC provides information only
! style="text-align: left;"| 2
! style="text-align: left;"| +
! style="text-align: left;"| 10000lbs
! style="text-align: left;"| 90M
|}
|}
<div style="font-size:0.65rem; color:#9a9690; margin-top:8px;">PIL = Pilot's Responsibility &nbsp;·&nbsp; IC = Intercept Controller's Responsibility</div>
</div>


Would mean:
<!-- SECTION 03 -->
<div style="font-size:0.58rem; letter-spacing:5px; color:#7a7875; border-bottom:1px solid #c8c5bf; padding-bottom:5px; margin-bottom:14px;">&#9632;&nbsp;&nbsp;03&nbsp;&nbsp;/&nbsp;&nbsp;STANDARD CALLS</div>


6 x FOX-3, 0 x FOX-1, 2 x FOX-2, Gun Available, 10000lbs of fuel remaining
<div style="padding:4px 0 20px 14px;">
<div style="font-size:0.65rem; letter-spacing:2px; color:#4a4845; text-transform:uppercase; margin-bottom:6px;">State Call</div>
<div style="line-height:1.9; margin-bottom:10px;">A '''State Call''' reports combat status to the IC: '''weapons, fuel, and playtime''' in a fixed order.</div>
<div style="background:#edecea; border:1px solid #c8c5bf; padding:8px 14px; margin-bottom:8px; font-size:0.75rem; font-style:italic; color:#4a4845;">"State is 602+ 10000lbs 90M"</div>
{| class="wikitable" style="font-size:0.75rem; margin-bottom:8px;"
! # FOX-3 !! # FOX-1 !! # FOX-2 !! Gun !! Fuel !! Playtime
|-
| 6 || 0 || 2 || + || 10000 lbs || 90 min
|}
<div style="font-size:0.75rem; color:#4a4845;">6× FOX-3, FOX-1, FOX-2, Gun available, 10,000 lbs fuel, 90 minutes playtime.</div>
</div>


90 Minutes of Playtime
<div style="padding:4px 0 20px 14px;">
<div style="font-size:0.65rem; letter-spacing:2px; color:#4a4845; text-transform:uppercase; margin-bottom:6px;">BRAA Call</div>
<div style="line-height:1.9; margin-bottom:10px;">Tactical control format: '''Bearing, Range, Altitude, Aspect''' relative to the specified friendly aircraft.</div>
{| class="wikitable" style="font-size:0.75rem;"
! Groups !! Format !! Bearing !! Range !! Altitude !! Aspect !! Declaration
|-
| Single Group || BRAA || 320 || 30 || 20000 || Flanking || BOGEY
|}
</div>


''BRAA Call''
<div style="padding:4px 0 20px 14px;">
 
<div style="font-size:0.65rem; letter-spacing:2px; color:#4a4845; text-transform:uppercase; margin-bottom:6px;">Flight Check / Frequency Change</div>
A tactical control format providing target '''bearing, range, altitude, and aspect''' (BRAA) relative to the specified FRIENDLY aircraft.
<div style="line-height:1.9; margin-bottom:10px;">Executed when switching the flight to a new frequency. <span style="color:#7a7875;">Intraflight</span> = flight-internal frequency. <span style="color:#7a7875;">Interflight</span> = control agency frequency.</div>
 
{| class="wikitable" style="font-size:0.75rem;"
{| class="wikitable"
! Station !! Phrase
|-
| ATC || {CS} Push Button _
|-
| Flight Lead (interflight) || {CS} Push Button _
|-
|-
! style="text-align: left;"| ''Groups''
| Flight Lead (intraflight) || Push {UHF/VHF, Radio 1/2} Button _
! 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
| colspan="2" style="text-align:center; color:#7a7875;" | All flight members switch to channel _
! 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''
 
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
 
{| class="wikitable"
|-
|-
! Station
| Flight Lead || {CS} Check
! Phrase
|-
|-
! ATC
| Wingman || 2
! {CS} Push Button _
|-
|-
! Flight Lead (on interflight)
| Element Lead || 3
! {CS} Push Button _
|-
|-
! Flight Lead (on intraflight)
| Element Wingman || 4
! 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; color:#7a7875;" | Flight Lead proceeds with initial call as normal
|}
</div>
 
<div style="padding:4px 0 28px 14px;">
<div style="font-size:0.65rem; letter-spacing:2px; color:#4a4845; text-transform:uppercase; margin-bottom:6px;">Authentication (DRYAD)</div>
<div style="line-height:1.9; margin-bottom:10px;">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. DRYAD table is issued in the pre-mission briefing.</div>
{| class="wikitable" style="font-size:0.75rem;"
! Station !! Phrase
|-
|-
! Flight Lead
| ATC || Authenticate E-A
! {CS} Check
|-
|-
! Wingman of Flight Lead
| Pilot || Come back G
! 2
|-
|-
! Element Lead
| Pilot || Authenticate J-U
! 3
|-
|-
! Wingman of Element Lead
| ATC || Come back R
! 4
|-
|-
! colspan="2" style="text-align: center;"| Flight Lead Proceeds with Initial Call as normal
| Pilot || Good Authentication
|}
|}
</div>


''Authentication''
<!-- SECTION 04 -->
<div style="font-size:0.58rem; letter-spacing:5px; color:#7a7875; border-bottom:1px solid #c8c5bf; padding-bottom:5px; margin-bottom:14px;">&#9632;&nbsp;&nbsp;04&nbsp;&nbsp;/&nbsp;&nbsp;CHECK-IN PROCEDURES</div>
<div style="font-size:0.72rem; color:#7a7875; padding:0 0 10px 14px;">CS = Callsign (e.g. SHADOW1). Not every procedure applies to every mission.</div>


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.
<div style="padding:4px 0 16px 14px;">
<div style="font-size:0.65rem; letter-spacing:2px; color:#4a4845; text-transform:uppercase; margin-bottom:6px;">Check In on Radar — Transit Control</div>
{| class="wikitable" style="font-size:0.75rem; margin-bottom:6px;"
! Station !! Phrase
|-
| colspan="2" style="text-align:center; color:#7a7875;" | Flight Check
|-
| Flight Lead || {CRC-CS} {CS} {FlightLevel}
|-
| colspan="2" style="text-align:center; color:#7a7875;" | Authentication
|-
| CRC || {CS}, Identified, {Instructions}
|}
<div style="font-size:0.72rem; color:#7a7875;">NOTE: Close Positive Control is inferred.</div>
</div>


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>])''
<div style="padding:4px 0 28px 14px;">
 
<div style="font-size:0.65rem; letter-spacing:2px; color:#4a4845; text-transform:uppercase; margin-bottom:6px;">Check In with Weapons Controller</div>
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="font-size:0.75rem; margin-bottom:6px;"
 
! Station !! Phrase
[[File:media/image1.png|581x417px]]
|-
 
| colspan="2" style="text-align:center; color:#7a7875;" | Flight Check
Table Will be provided in the PreMission Briefing
 
{| class="wikitable"
|-
|-
! style="text-align: left;"| ATC
| Flight Lead || {CRC-CS} {CS} Mission Nr {MSN} {Position} {Altitude} {PLAYTIME} {as Fragged / With Exceptions}
! style="text-align: left;"| Authenticate E-A
|-
|-
! style="text-align: left;"| Pilot
| CRC || ''Acknowledges''
! style="text-align: left;"| Come back G
|-
|-
! style="text-align: left;"| Pilot
| colspan="2" style="text-align:center; color:#7a7875;" | Authentication
! style="text-align: left;"| Authenticate J-U
|-
|-
! style="text-align: left;"| ATC
| CRC || {CS}, Identified, {Control Type}, ALPHA CHECK BULLSEYE {position}
! style="text-align: left;"| Come back R
|-
|-
! style="text-align: left;"| Pilot
| Flight Lead || Same {Alpha Check}
! style="text-align: left;"| Good Authentication
|}
|}
<div style="font-size:0.72rem; color:#7a7875;">NOTE: Bullseye cannot be used for initial position calls — only valid after ALPHA CHECK.</div>
</div>


''AWACS / CRC / … - Communication Procedures''
<!-- SECTION 05 -->
 
<div style="font-size:0.58rem; letter-spacing:5px; color:#7a7875; border-bottom:1px solid #c8c5bf; padding-bottom:5px; margin-bottom:14px;">&#9632;&nbsp;&nbsp;05&nbsp;&nbsp;/&nbsp;&nbsp;TRAINING RANGE &amp; FORMATIONS</div>
CS = Callsign for example SHADOW1
 
'''Check in with a Controlling Center'''
 
Note that this is an example! Depending on the mission, not every procedure may be executed.
 
Check in on Radar (Transit Control)


{| class="wikitable"
<div style="padding:4px 0 16px 14px;">
<div style="font-size:0.65rem; letter-spacing:2px; color:#4a4845; text-transform:uppercase; margin-bottom:6px;">Attack Run</div>
{| class="wikitable" style="font-size:0.75rem; margin-bottom:6px;"
! Station !! Phrase
|-
|-
! Station
| colspan="2" style="text-align:center; color:#7a7875;" | Turning in for attack run
! Phrase
|-
|-
! colspan="2" style="text-align: center;"| Flight Check
| Aircraft || {CS} In Hot, Heading ___
|-
|-
! Flight Lead
| Tactical Controller || Cleared Hot (or Abort, Turn Left/Right HDG)
! {CRC-CS} {CS} {FlightLevel}
|-
|-
! colspan="2" style="text-align: center;"| Authentication
| colspan="2" style="text-align:center; color:#7a7875;" | Upon completion
|-
|-
! CRC
| Aircraft || {CS} Off Target
! {CS}, Identified, {Instructions}
|}
|}
<div style="font-size:0.72rem; color:#7a7875;">Repeated for every attack run. Multiple aircraft on same target: ASACS issues traffic info and may require visual separation.</div>
</div>


NOTE: Close Positive Control is inferred
<div style="padding:4px 0 16px 14px;">
 
<div style="font-size:0.65rem; letter-spacing:2px; color:#4a4845; text-transform:uppercase; margin-bottom:6px;">Formation Splits</div>
Check in with Weapons Controller
{| class="wikitable" style="font-size:0.75rem; margin-bottom:12px;"
 
! Station !! Phrase
{| class="wikitable"
|-
|-
! style="text-align: left;"| Station
| Flight Lead || {CS}, request split into {number} parts of {number} each
! style="text-align: left;"| Phrase
|-
|-
! colspan="2" style="text-align: center;"| Flight Check
| CRC || {CS}, report ready for {Right/Left Hand} {Split Type}
|}
<div style="font-size:0.65rem; letter-spacing:1.5px; color:#4a4845; text-transform:uppercase; margin:0 0 4px;">Vertical (Altitude)</div>
{| class="wikitable" style="font-size:0.75rem; margin-bottom:12px;"
! Station !! Phrase
|-
|-
! style="text-align: left;"| Flight Lead
| Flight Lead || {CS}, ready
! style="text-align: left;"| {CRC-CS} {CS} Mission Nr {MSN} {Position} {Altitude} {PLAYTIME} {as Fragged / With Exceptions }
|-
|-
! style="text-align: left;"| CRC
| CRC || {CS 2}, descend {FL}
! style="text-align: left;"| ''{Acknowledges}''
|-
|-
! colspan="2" style="text-align: center;"| Authentication
| Flight Lead 2 || {CS 2}, descending {FL}
|-
|-
! style="text-align: left;"| CRC
| CRC || {CS 2}, squawk {number} · identified
! style="text-align: left;"| {CS}, Identified, {Control Type}, ALPHA CHECK BULSEYE {position from bullseye}
|-
|-
! style="text-align: left;"| Flight Lead
| colspan="2" style="text-align:center; color:#7a7875;" | Repeat for each new flight
! style="text-align: left;"| Same {Alpha Check}
|}
|}
 
<div style="font-size:0.65rem; letter-spacing:1.5px; color:#4a4845; text-transform:uppercase; margin:0 0 4px;">Lateral (Vector)</div>
NOTE: Bullseye cannot be used for initial position calls.
{| class="wikitable" style="font-size:0.75rem; margin-bottom:6px;"
 
! Station !! Phrase
Bullseye is only valid after ALPHA CHECK
 
'''Training Range Operations'''
 
Ingress
 
{| class="wikitable"
|-
! style="text-align: left;"| Station
! style="text-align: left;"| Phrase
|-
|-
! rowspan="2" colspan="2" style="text-align: center;"| Flight Check
| Flight Lead || {CS}, ready
|-
|-
| CRC || {CS 2} For split turn {side} {degrees}
|-
|-
! Aircraft
| Flight Lead || {CS 2} For split turn {side} {degrees}
! style="text-align: left;"| Tactical, {CS} Leaving IP, Heading ___
|-
|-
! style="text-align: left;"| Tactical Controller
| CRC || {CS 2} squawk {number} · identified
! style="text-align: left;"| Radar Contact, Continue as Fragged, CALL IN
|-
|-
! Aircraft
| colspan="2" style="text-align:center; color:#7a7875;" | Repeat for each new flight
! style="text-align: left;"| Roger, {CS}
|}
|}
</div>


Attack
<div style="padding:4px 0 28px 14px;">
 
<div style="font-size:0.65rem; letter-spacing:2px; color:#4a4845; text-transform:uppercase; margin-bottom:6px;">Join-Up</div>
{| class="wikitable"
{| class="wikitable" style="font-size:0.75rem;"
! 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}
|-
|-
! style="text-align: center;"| Station
| Flight Lead || {CS}, fly {heading} and climb/descend to {angels}
! style="text-align: center;"| Phrase
|-
|-
! colspan="2" style="text-align: center;"| '''Once turning in for an attack run'''
| CRC || {CS}, report {CS 2} in sight
|-
|-
! Aircraft
| Flight Lead || {CS}, {CS 2} in sight, {Position}
! style="text-align: left;"| {CS} In Hot, Heading ___
|-
|-
! style="text-align: left;"| Tactical Controller
| CRC || Visual join-up approved — report formation tight
! style="text-align: left;"| Cleared Hot (or Abort, Turn Left / Right HDG)
|-
|-
! colspan="2" style="text-align: center;"| '''Upon completion of the attack run.'''
| Flight Lead 2 || {CS 2}, formation tight
|-
|-
! Aircraft
| CRC || {CS 2} adopt callsign {new CS}
! style="text-align: left;"| {CS} Off Target
|}
|}
</div>


This has to be repeated for every attack run.
<!-- SECTION 06 -->
<div style="font-size:0.58rem; letter-spacing:5px; color:#7a7875; border-bottom:1px solid #c8c5bf; padding-bottom:5px; margin-bottom:14px;">&#9632;&nbsp;&nbsp;06&nbsp;&nbsp;/&nbsp;&nbsp;AIR-TO-AIR REFUELLING</div>
<div style="padding:4px 0 14px 14px; line-height:1.9;">
AAR requires close coordination with the tanker around a pre-briefed Rendezvous (RV). SOURCE uses '''RV Alpha (Fixed Anchor)''' for all operations.
</div>


If multiple aircraft are attacking the same target ASACS-Controller will issue traffic information and may request the aircraft to maintain visual separation.
<div style="padding:0 0 16px 14px;">
<div style="font-size:0.65rem; letter-spacing:2px; color:#4a4845; text-transform:uppercase; margin-bottom:8px;">Tanker Orbit Stack</div>
<div style="display:flex; gap:0; border:1px solid #c8c5bf; margin-bottom:16px; font-size:0.72rem; max-width:480px;">
<div style="flex:1; text-align:center; padding:8px 6px; border-right:1px solid #c8c5bf;"><div style="font-weight:600; letter-spacing:1px;">ALPHA</div><div style="color:#7a7875; font-size:0.65rem;">Receivers departing · Emergency</div></div>
<div style="flex:1; text-align:center; padding:8px 6px; border-right:1px solid #c8c5bf;"><div style="font-weight:600; letter-spacing:1px;">BRAVO</div><div style="color:#7a7875; font-size:0.65rem;">Tanker base level</div></div>
<div style="flex:1; text-align:center; padding:8px 6px; border-right:1px solid #c8c5bf;"><div style="font-weight:600; letter-spacing:1px;">CHARLIE</div><div style="color:#7a7875; font-size:0.65rem;">Receiver evasive</div></div>
<div style="flex:1; text-align:center; padding:8px 6px;"><div style="font-weight:600; letter-spacing:1px;">DELTA</div><div style="color:#7a7875; font-size:0.65rem;">Receivers approaching</div></div>
</div>
</div>


'''Formation Splits'''
<div style="padding:4px 0 28px 14px;">
 
<div style="font-size:0.65rem; letter-spacing:2px; color:#4a4845; text-transform:uppercase; margin-bottom:6px;">RV Alpha Procedure</div>
{| class="wikitable"
<div style="font-size:0.75rem; line-height:1.9; margin-bottom:10px;">Receiver: fly 2000 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.</div>
{| class="wikitable" style="font-size:0.75rem; margin-bottom:6px;"
! Station !! Phrase
|-
| CRC || {CS} Proceed Tanker BRAA {BRAA} — RV ALPHA — Tanker Freq {Freq} {Instructions}
|-
| Flight Lead || {CS} Roger, RV A, Tanker Freq {Freq} {Readback}
|-
| colspan="2" style="text-align:center; color:#7a7875;" | Once flight has radar contact with tanker
|-
| Flight Lead || {Flight Name} JUDY 1 Weapons Safe
|-
| All Wingmen (in order) || 2, 3, 4… Weapons Safe
|-
| colspan="2" style="text-align:center; color:#7a7875;" | Once tanker is in sight
|-
| CRC || {CS} Tanker {x} o'clock, Report Visual
|-
|-
! Station
| Flight Lead || {CS} Nose Cold, Visual with Tanker
! Phrase
|-
|-
! Flight Lead
| CRC || {CS} Roger Contact Boom
! {CS}, request split into {number} parts of {number} each
|-
|-
! CRC
| colspan="2" style="text-align:center; color:#7a7875;" | Switch to DCS tanker frequency
! {CS}, report ready for {Right hand / Left Hand \ _} {Split Type}
|}
|}
<div style="font-size:0.72rem; color:#7a7875; margin-top:6px;">NOTE: Flight Lead must confirm Nose Cold with wingmen on intraflight before reporting to ATC.</div>
</div>


Only In case of split by vectors ATC will call the Side (Lefthand / Righthand)
<!-- SECTION 07 -->
<div style="font-size:0.58rem; letter-spacing:5px; color:#7a7875; border-bottom:1px solid #c8c5bf; padding-bottom:5px; margin-bottom:14px;">&#9632;&nbsp;&nbsp;07&nbsp;&nbsp;/&nbsp;&nbsp;POSITIVE IDENTIFICATION (PID)</div>
<div style="padding:4px 0 14px 14px; line-height:1.9;">
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.
</div>


'''Vertical (Split by Altitude Adjustment)''' ''Continued''
<div style="display:flex; gap:16px; padding:0 0 20px 14px;">
<div style="flex:1; background:#edecea; border:1px solid #c8c5bf; padding:12px 14px; font-size:0.75rem;">
<div style="font-size:0.6rem; letter-spacing:2px; color:#7a7875; margin-bottom:6px;">ELECTRONIC PID</div>
IFF interrogation, Link picture, NCTR, controller declaration. Most common form in BVR.
</div>
<div style="flex:1; background:#edecea; border:1px solid #c8c5bf; padding:12px 14px; font-size:0.75rem;">
<div style="font-size:0.6rem; letter-spacing:2px; color:#7a7875; margin-bottom:6px;">VISUAL PID</div>
Confirm number, type, livery, armament, heading, speed. Requires merge or VID pass.
</div>
<div style="flex:1; background:#edecea; border:1px solid #c8c5bf; padding:12px 14px; font-size:0.75rem;">
<div style="font-size:0.6rem; letter-spacing:2px; color:#7a7875; margin-bottom:6px;">GROUND TARGETS</div>
Correlate with prebriefed target. CRC issues Cleared to Engage before weapons release.
</div>
</div>


{| class="wikitable"
<div style="padding:4px 0 28px 14px;">
<div style="font-size:0.65rem; letter-spacing:2px; color:#4a4845; text-transform:uppercase; margin-bottom:6px;">Ground Target Engagement</div>
{| class="wikitable" style="font-size:0.75rem;"
! Station !! Phrase
|-
|-
! style="text-align: left;"| Station
| Flight Lead || {CS} Identified {Target Description} {if prebriefed: Matches Target __}
! style="text-align: left;"| Phrase
|-
|-
! style="text-align: left;"| Flight Lead
| CRC || Cleared to Engage
! {CS},ready
|-
|-
! style="text-align: left;"| CRC
| Flight Lead || In Hot {Target Description} {Ingress Heading}
! style="text-align: left;"| {CS 2}, descend {FL number}
|-
|-
! style="text-align: left;"| Flight Lead 2
| CRC || Cleared Hot / Abort
! style="text-align: left;"| {CS 2}, descending {FL number}
|-
|-
! style="text-align: left;"| CRC
| Flight Lead || Completed Engagement
! {CS 2}, squawk {number}
|-
|-
! style="text-align: left;"| Flight Lead 2
| CRC || Continue as Fragged / Additional Instructions
! {CS 2}, squawk {number}
|-
! style="text-align: left;"| CRC
! {CS 2}, identified
|-
! colspan="2" style="text-align: center;"| Repeat for each new flight.
|}
|}
</div>


'''Lateral (Split by Vector Change)''' ''Continued''
<!-- SECTION 08 -->
<div style="font-size:0.58rem; letter-spacing:5px; color:#7a7875; border-bottom:1px solid #c8c5bf; padding-bottom:5px; margin-bottom:14px;">&#9632;&nbsp;&nbsp;08&nbsp;&nbsp;/&nbsp;&nbsp;AIR-TO-AIR COMBAT</div>
<div style="padding:4px 0 14px 14px; line-height:1.9;">
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 has 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'''.
</div>


{| class="wikitable"
<div style="padding:4px 0 16px 14px;">
<div style="font-size:0.65rem; letter-spacing:2px; color:#4a4845; text-transform:uppercase; margin-bottom:8px;">Contact Declaration</div>
<div style="display:flex; gap:0; flex-wrap:wrap; border:1px solid #c8c5bf; margin-bottom:16px; font-size:0.72rem;">
<div style="flex:1; min-width:90px; padding:8px 10px; border-right:1px solid #c8c5bf;"><div style="font-weight:600;">BOGEY</div><div style="color:#7a7875; font-size:0.65rem;">Unknown — not cleared</div></div>
<div style="flex:1; min-width:90px; padding:8px 10px; border-right:1px solid #c8c5bf;"><div style="font-weight:600;">BANDIT</div><div style="color:#7a7875; font-size:0.65rem;">Enemy — not cleared</div></div>
<div style="flex:1; min-width:90px; padding:8px 10px; border-right:1px solid #c8c5bf;"><div style="font-weight:600; color:#9b1c1c;">HOSTILE</div><div style="color:#7a7875; font-size:0.65rem;">Enemy — cleared to engage</div></div>
<div style="flex:1; min-width:90px; padding:8px 10px; border-right:1px solid #c8c5bf;"><div style="font-weight:600;">NEUTRAL</div><div style="color:#7a7875; font-size:0.65rem;">Neutral — not cleared</div></div>
<div style="flex:1; min-width:90px; padding:8px 10px;"><div style="font-weight:600;">FRIENDLY</div><div style="color:#7a7875; font-size:0.65rem;">Friendly — not cleared</div></div>
</div>
</div>
 
<div style="padding:4px 0 16px 14px;">
<div style="font-size:0.65rem; letter-spacing:2px; color:#4a4845; text-transform:uppercase; margin-bottom:6px;">Commit — Fighter Initiated</div>
{| class="wikitable" style="font-size:0.75rem; margin-bottom:14px;"
! Station !! Phrase
|-
| colspan="2" style="text-align:center; color:#7a7875;" | Once all commit criteria are met
|-
|-
! style="text-align: left;"| Station
| Flight Lead || {CS} Recommend Commit
! style="text-align: left;"| Phrase
|-
|-
! style="text-align: left;"| Flight Lead
| colspan="2" style="text-align:center; color:#7a7875;" | Controller evaluates and initiates
! {CS},ready
|-
|-
! style="text-align: left;"| CRC
| CRC || {GCI-CS} {Nr of groups}, {Group Description} {Fighter-CS} Commit
! style="text-align: left;"| {CS 2} For split turn {side} {degrees}
|-
|-
! style="text-align: left;"| Flight Lead
| Flight Lead || {CS}
! {CS 2} For split turn {side} {degrees}
|}
<div style="font-size:0.65rem; letter-spacing:2px; color:#4a4845; text-transform:uppercase; margin-bottom:6px;">Commit — Controller Initiated</div>
{| class="wikitable" style="font-size:0.75rem; margin-bottom:14px;"
! Station !! Phrase
|-
|-
! style="text-align: left;"| CRC
| CRC || {GCI-CS} {Nr of groups}, {Group Description} {Fighter-CS} Commit {+ VID if required}
! {CS 2} squawk {number}
|-
|-
! style="text-align: left;"| Flight Lead 2
| Flight Lead || {CS} Commit
! {CS 2} squawk {number}
|}
<div style="font-size:0.65rem; letter-spacing:2px; color:#4a4845; text-transform:uppercase; margin-bottom:6px;">Radar / Visual Contact</div>
{| class="wikitable" style="font-size:0.75rem; margin-bottom:14px;"
! Station !! Phrase
|-
|-
! style="text-align: left;"| CRC
| Flight Lead || {CS} Judy — ''radar contact, no further guidance needed''
! {CS 2} identified
|-
|-
! colspan="2" style="text-align: left;"| Repeat for each new flight
| Flight Lead || {CS} Tally — ''visual on target''
|}
|}
 
<div style="font-size:0.65rem; letter-spacing:2px; color:#4a4845; text-transform:uppercase; margin-bottom:6px;">Declare &amp; Weapon Release</div>
'''Join-UP'''
{| class="wikitable" style="font-size:0.75rem; margin-bottom:6px;"
 
! Station !! Phrase
{| class="wikitable"
|-
| Flight Lead || {CRC-CS} Declare {Group Label or Bullseye Position}
|-
| CRC || {Group Label} Declared …
|}
{| class="wikitable" style="font-size:0.75rem; margin-bottom:28px;"
! Station !! Phrase
|-
|-
! style="text-align: left;"| Station
| Aircraft || {CS} Fox-{1,2,3} {Group Label or Bullseye Position} {Target description}
! style="text-align: left;"| Phrase
|-
|-
! style="text-align: left;"| Flight Lead
| CRC || Copy Shot
! {CS} requesting join-up with {CS 2}
|}
</div>
 
<!-- SECTION 09 -->
<div style="font-size:0.58rem; letter-spacing:5px; color:#7a7875; border-bottom:1px solid #c8c5bf; padding-bottom:5px; margin-bottom:14px;">&#9632;&nbsp;&nbsp;09&nbsp;&nbsp;/&nbsp;&nbsp;BREVITY WORDS</div>
<div style="padding:4px 0 28px 0;">
{| class="wikitable" style="font-size:0.75rem; width:100%;"
! style="width:22%;" | Term !! Definition
|-
|-
! style="text-align: left;"| CRC
| '''AS FRAGGED''' || Unit will perform exactly as briefed or scheduled.
! {CS}, roger
|-
|-
! style="text-align: left;"| CRC
| '''WITH EXCEPTIONS''' || Unit will perform as briefed with stated exceptions.
! style="text-align: left;"| {CS 2}, confirm join up clearance for {CS}.
|-
|-
! style="text-align: left;"| Flight Lead 2
| '''ALPHA CHECK''' || Verification of the position of a BULLSEYE or related point.
! style="text-align: left;"| {CS 2}, {CS} is cleared to join up.
|-
|-
! style="text-align: left;"| CRC
| '''ANGELS''' || Height of friendly aircraft in thousands of feet MSL.
! style="text-align: left;"| {CS}, for join-up, fly {heading} and climb / descend to {angels}.
|-
|-
! style="text-align: left;"| Flight Lead
| '''AUTHENTICATE''' || Method to verify communication with allied agencies.
! {CS}, for join-up, fly {heading} and climb / descend to {angels}.
|-
|-
! style="text-align: left;"| CRC
| '''PLAYTIME''' || Time aircraft can remain on station (hours + minutes).
! {CS}, report {CS 2} in sight.
|-
|-
! style="text-align: left;"| Flight Lead
| '''PICTURE''' || Request for mission information in digital bullseye format.
! {CS}, report {CS 2} in sight, {Position}
|-
|-
! style="text-align: left;"| CRC
| '''BRAA''' || Bearing, Range, Altitude, and Aspect relative to a friendly aircraft.
! {CS}, visual join-up approved {CS 2}, report formation tight.
|-
|-
! style="text-align: left;"| Flight Lead 2
| '''BULLSEYE''' || Reference point used to establish positions (bearing + range).
! {CS 2}, formation tight.
|-
|-
! style="text-align: left;"| CRC
| '''GROUP(S)''' || Any number of contacts within 3 NM of each other.
! {CS 2} formation adopt callsign {new CS}
|}
 
'''AAR'''
 
[[File:media/image3.png|601x177px]]
 
Air to Air Refueling is not only mechanically difficult but requires close coordination with the Tanker.
 
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
 
There are multiple Types of RV
 
* RV Alpha - Fixed Anchor
* RV Bravo - Head-on
* RV Charlie - Tail Chase
* RV Delta - Point Parallel
* RV Echo - Timed Arrival
* RV Foxtrot - Sequential Departure
* RV Golf - En Route
 
They get increasingly more complicated and require some calculation to determine the correct speeds and turnradii.
 
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
 
Execution:
 
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
| '''AZIMUTH''' || Two groups separated laterally (by cardinal directions).
! Phrase
|-
|-
! style="text-align: left;"| CRC
| '''RANGE''' || Two groups separated along a line of bearing (LEAD/TRAIL).
! 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
| '''STACK''' || Two or more contacts in a group with ≥10,000 ft altitude separation.
! 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
| '''MONITOR''' || Maintain sensor awareness on a group or object.
|-
|-
! style="text-align: left;"| Flight Lead
| '''CLARA''' || Radarscope clear of enemy contacts.
! style="text-align: left;"| {Flight - Name} JUDY 1 Weapons Safe
|-
|-
! style="text-align: left;"| All Wingmen in order
| '''CLEAN''' || No radar contacts on bandits, bogies, or aircraft of interest.
! style="text-align: left;"| 2,3,4, … Weapons safe
|-
|-
! colspan="2" style="text-align: center;"| Once in view of the Tanker
| '''DRAG / COLD''' || Contact stabilized 000–070°.
|-
|-
! style="text-align: left;"| CRC
| '''BEAM''' || Contact stabilized 070–110°.
! style="text-align: left;"| {CS} Tanker is on your {x} o clock, Report Visual
|-
|-
! style="text-align: left;"| Flight Lead
| '''FLANK''' || Contact stabilized 110–160°.
! style="text-align: left;"| (Once Visual} {CS} Nose Cold, Visual with Tanker
|-
|-
! style="text-align: left;"| CRC
| '''HOT / HEAD ON''' || Contact stabilized 160–180°.
! style="text-align: left;"| {CS} Roger Contact Boom
|-
|-
! colspan="2" style="text-align: center;"| At this point you switch to dcs’s Tanker Frequency
| '''TRACKING''' || Direction of flight/movement (in bullseye format).
|}
 
NOTE: Flight Lead shall ask his wingman on intraflight to confirm Nose Cold before reporting it 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.
 
Just like AAR, this is coordination and discipline under pressure. And unlike refueling, the consequences of getting it wrong don’t end with embarrassment.
 
Execution:
 
The pilot (or flight) must:
 
* Correlate the radar contact with the assigned track from CRC / AWACS
* 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)
* Compare target BRAA with declared hostile tracks from controlling agency
* Assess target behavior (aspect, speed, formation, emissions)
* Ensure ROE criteria are met before weapons release
 
PID is achieved when the flight lead is confident that:
 
* The contact matches the declared hostile track
* 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:
 
'''Electronic PID'''<br />
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
 
{| class="wikitable"
|-
|-
! style="text-align: left;"| Station
| '''MARSHALLING''' || Positioning forces at a point for offensive operations.
! style="text-align: left;"| Phrase
|-
|-
! style="text-align: left;"| Flight Lead
| '''BANDIT''' || Positively identified enemy (not clearance to engage).
! style="text-align: left;"| {CS} Identified {Target Description} {if prebriefed: Matches Target __}
|-
|-
! style="text-align: left;"| CRC
| '''BOGEY''' || Unknown contact.
! style="text-align: left;"| Cleared to Engage
|-
|-
! style="text-align: left;"| Flight Lead
| '''HOSTILE''' || Enemy contact cleared for engagement (IAW ROE).
! style="text-align: left;"| In hot {Target Description / Target ID} {Ingress Heading}
|-
|-
! style="text-align: left;"| CRC
| '''FURBALL''' || Friendly and non-friendly aircraft within 5 NM.
! style="text-align: left;"| Cleared Hot / Abort
|-
|-
! style="text-align: left;"| Flight Lead
| '''FOX ONE''' || Semi-active radar-guided missile.
! style="text-align: left;"| Completed Engagement
|-
|-
! style="text-align: left;"| CRC
| '''FOX TWO''' || IR-guided missile.
! style="text-align: left;"| Continue as Fragged / Additional Instructions
|}
 
Engagement of Air Targets
 
'''PID''' for Aircraft can be achieved through Declaration by a CRC or Visual Identification
 
In some cases a CRC will require an Intercepting Fighter to archive a Visual Identification
 
'''Visual PID'''<br />
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.
 
NOTE: In DCS acquiring the Registration might be considerably difficult because of low resolution monitors and similar. Therefore this is optional
 
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”
 
'''A2A Combat'''
 
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
 
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)
 
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>]
 
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.
 
The most important metric here is Targeting Range, which is an agreed-upon distance at which every contact needs to be intercepted / engaged
 
A group inside the Targeting Range that no fighter has taken responsibility for is labelled as “Untargeted”
 
'''Fighter Initiated'''
 
{| class="wikitable"
|-
|-
! style="text-align: left;"| Station
| '''FOX THREE''' || Active radar-guided missile.
! style="text-align: left;"| Phrase
|-
|-
! colspan="2" style="text-align: center;"| Once all commit criteria are met. The Flight will suggest a Commit
| '''ENGAGE''' || Directive to fire on a target.
|-
|-
! style="text-align: left;"| Flight Lead
| '''GATE''' || Fly as fast as possible — afterburner.
! 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
| '''BUSTER''' || Fly at maximum continuous speed — military power.
|-
|-
! style="text-align: left;"| CRC
| '''BREAK''' || (Direction): Immediate maximum-performance turn.
! style="text-align: left;"| {GCI-CS} {Nr of groups}, {Group Description} {Fighter-CS} Commit
|-
|-
! style="text-align: left;"| Flight Lead
| '''VISUAL''' || Sighting of friendly aircraft, ground unit, or ship.
! style="text-align: left;"| {CS}
|}
 
'''Controller Initiated'''
 
{| class="wikitable"
|-
|-
! Station
| '''BLIND''' || No visual contact with friendly.
! Phrase
|-
|-
! style="text-align: center;"| CRC
| '''TALLY''' || Sighting of a target or enemy aircraft.
! {GCI-CS} {Nr of groups}, {Group Description} {Fighter-CS} Commit {+ VID if required}
|-
|-
! Flight Lead
| '''NO JOY''' || No visual contact with target or enemy.
! {CS} Commit.
|}
 
Once the Formation has the Contact on Radar and no further guidance is required:
 
{| class="wikitable"
|-
|-
! style="text-align: left;"| Station
| '''MERGED''' || Radar tracks have come together (3–5 NM).
! style="text-align: left;"| Phrase
|-
|-
! style="text-align: left;"| Flight Lead
| '''JUDY''' || Aircrew has control of intercept; controller minimizes comms.
! style="text-align: left;"| {CS} Judy
|}
 
Once the Formation has tally on the Target
 
{| class="wikitable"
|-
|-
! Station
| '''DECLARE''' || Inquiry as to track ID. Responses: FRIENDLY, BOGEY, BANDIT, HOSTILE, NEUTRAL, UNABLE, FURBALL.
! Phrase
|-
|-
! Flight Lead
| '''BOGEY DOPE''' || Request info on indicated or nearest group in BRAA format.
! {CS} Tally
|}
 
'''Contact Declaration'''
 
There are 5 possible Declarations.
 
# Bogey - Unknown | Not Cleared to be Engaged
# 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"
|-
|-
! Station
| '''TARGETING''' || Fighter has acquired assigned group and assumes responsibility.
! Phrase
|-
|-
! Flight Lead
| '''CONTACT''' || Individual radar return within a group.
! {CRC-CS} Declare {Group Label or Bullseye Position)
|-
|-
! CRC
| '''HEAVY''' || Group with >3 elements.
! {Group Label} Declared …
|}
 
'''Weapon Release'''
 
{| class="wikitable"
|-
|-
! Station
| '''HIGH''' || Target altitude above 40,000 ft.
! Phrase
|-
|-
! Aircraft employing Weaponary
| '''FAST''' || Target speed 600–900 kts or Mach 1.0–1.5.
! {CS} Fox-{1,2,3} {Group Label or Bullseye Position} {Further Description of Shot upon target within Group}
|-
|-
! CRC
| '''VERY FAST''' || Target speed >900 kts / Mach 1.5+.
! Copy Shot
|}
|}
</div>


'''Brevity Words'''
<!-- FOOTER -->
 
<div style="font-size:0.58rem; letter-spacing:2px; color:#9a9690; border-top:1px solid #c8c5bf; padding-top:10px; margin-top:4px; text-align:center;">
'''AS FRAGGED''': Unit or element will perform exactly as briefed or scheduled.
[[Main Page|HOME]] &nbsp;·&nbsp; [[General/CATC Communications Guide|CATC COMMS]] &nbsp;·&nbsp; [[General/Air Traffic Communication|ATC GUIDE]]
 
</div>
'''WITH EXCEPTIONS:''' Unit or element will perform as briefed with additional given
 
<blockquote>exceptions
</blockquote>
'''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
 
<blockquote>aircraft.
</blockquote>
'''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 (referenced by cardinal
 
<blockquote>directions).
</blockquote>
'''RANGE''': Two GROUPs separated along a line of bearing (LEAD/TRAIL
 
<blockquote>GROUP).
</blockquote>
'''STACK''': Two or more contacts within a GROUP with altitude separation
 
<blockquote>(≥10,000 ft).
</blockquote>
'''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 stabilized 000–070°.
 
'''BEAM''': Contact stabilized 070–110°.
 
'''FLANK''': Contact stabilized 110–160°.
 
'''HOT / HEAD ON''': Contact stabilized 160–180°.
 
'''TRACKING''': Direction of flight/movement (in BULLSEYE format).
 
'''MARSHALL(ING)''': 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)''': Launch semi-active radar-guided missile.
 
'''FOX (TWO)''': Launch IR-guided missile.
 
'''FOX (THREE)''': Launch active radar-guided missile.
 
'''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 FRIENDLY aircraft/ground/ship.
 
'''BLIND''': No visual contact with FRIENDLY.
 
'''TALLY''': Sighting of a target/enemy.
 
'''NO JOY''': No visual contact with target/enemy.
 
'''MERGE(D)''': Radar tracks have come together (3–5 NM).
 
'''JUDY''': Aircrew has control of intercept / Radar Contact; controller
 
<blockquote>minimizes comms.
</blockquote>
'''DECLARE''': Inquiry as to ID of track (responses: FRIENDLY, BOGEY,
 
<blockquote>BANDIT, HOSTILE, NEUTRAL, UNABLE, FURBALL). Positional
 
data included.
</blockquote>
'''BOGEY DOPE''': Request info on indicated or nearest GROUP in BRAA format.
 
'''TARGETING''': Fighter has acquired assigned GROUP and assumes
 
<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+.

Revision as of 15:45, 5 March 2026


HOME  /  GENERAL  /  TACTICAL COMMUNICATION
SOURCE DCS — COMMUNICATIONS DOCTRINE
■  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.

■  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

CONTROL TYPES
TYPE DESCRIPTION
Close Positive Control IC directs all aspects of the intercept
Broadcast Control IC provides picture; PIL assumes responsibility
Advisory PIL fully responsible — IC provides information only
PIL = Pilot's Responsibility  ·  IC = Intercept Controller's Responsibility
■  03  /  STANDARD CALLS
State Call
A State Call reports combat status to the IC: weapons, fuel, and playtime in a fixed order.
"State is 602+ 10000lbs 90M"
# FOX-3 # FOX-1 # FOX-2 Gun Fuel Playtime
6 0 2 + 10000 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 20000 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. DRYAD table is issued in the pre-mission briefing.
Station Phrase
ATC Authenticate E-A
Pilot Come back G
Pilot Authenticate J-U
ATC Come back R
Pilot Good Authentication
■  04  /  CHECK-IN PROCEDURES
CS = Callsign (e.g. SHADOW1). Not every procedure applies to every mission.
Check In on Radar — Transit Control
Station Phrase
Flight Check
Flight Lead {CRC-CS} {CS} {FlightLevel}
Authentication
CRC {CS}, Identified, {Instructions}
NOTE: Close Positive Control is inferred.
Check In with Weapons Controller
Station Phrase
Flight Check
Flight Lead {CRC-CS} {CS} Mission Nr {MSN} {Position} {Altitude} {PLAYTIME} {as Fragged / With Exceptions}
CRC Acknowledges
Authentication
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 same target: ASACS issues traffic info 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
ALPHA
Receivers departing · Emergency
BRAVO
Tanker base level
CHARLIE
Receiver evasive
DELTA
Receivers approaching
RV Alpha Procedure
Receiver: fly 2000 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 A, 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.

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 prebriefed target. CRC issues Cleared to Engage before weapons release.

Ground Target Engagement
Station Phrase
Flight Lead {CS} Identified {Target Description} {if prebriefed: 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 has 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
BOGEY
Unknown — not cleared
BANDIT
Enemy — not cleared
HOSTILE
Enemy — cleared to engage
NEUTRAL
Neutral — not cleared
FRIENDLY
Friendly — not cleared
Commit — Fighter Initiated
Station Phrase
Once all commit criteria are met
Flight Lead {CS} Recommend Commit
Controller evaluates and initiates
CRC {GCI-CS} {Nr of groups}, {Group Description} {Fighter-CS} Commit
Flight Lead {CS}
Commit — Controller Initiated
Station Phrase
CRC {GCI-CS} {Nr of groups}, {Group Description} {Fighter-CS} Commit {+ VID if required}
Flight Lead {CS} Commit
Radar / Visual Contact
Station Phrase
Flight Lead {CS} Judy — radar contact, no further guidance needed
Flight Lead {CS} Tally — visual on target
Declare & Weapon Release
Station Phrase
Flight Lead {CRC-CS} Declare {Group Label or Bullseye Position}
CRC {Group Label} Declared …
Station Phrase
Aircraft {CS} Fox-{1,2,3} {Group Label or Bullseye Position} {Target description}
CRC Copy Shot
■  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 stabilized 000–070°.
BEAM Contact stabilized 070–110°.
FLANK Contact stabilized 110–160°.
HOT / HEAD ON Contact 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.
FOX TWO IR-guided missile.
FOX THREE Active radar-guided missile.
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 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 info on indicated or nearest group in BRAA format.
TARGETING Fighter has acquired assigned group and assumes responsibility.
CONTACT Individual radar return within a group.
HEAVY Group with >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 >900 kts / Mach 1.5+.

HOME  ·  CATC COMMS  ·  ATC GUIDE