## Acc

# Multi-Service Tactics, Techniques, And Procedures For Air Control Communication

## Atp 3-52.4 Mcrp 3-20F.10 Nttp 6-02.9 Afttp 3-2.8 September 2021 Foreword

This multi-Service tactics, techniques, and procedures (MTTP) publication is a product of the Air Land Sea Application (ALSA) Center in accordance with the memorandum of agreement between the Headquarters of the United States (US) Army, Marine Corps, Navy, and Air Force doctrine commanders directing ALSA to develop MTTP
publications to meet the immediate needs of the warfighter.

This MTTP publication has been prepared by ALSA under our direction for implementation by our respective commands and for use by other commands as appropriate.

Brigadier General, US Army Colonel, US Marine Corps Director Director, Policy and Standards Division Mission Command Center of Excellence Training and Education Command

## Lisle H. Babcock

Captain, US Navy Colonel, US Air Force Commander Commander
Navy Warfare Development Command Curtis E. Lemay Center for Doctrine
  Development and Education This publication is available through the following websites:
ALSA (https://www.alsa.mil/);
US Army (https://armypubs.army.mil);
US Marine Corps
(https://homeport.usmc.mil/sites/mcdoctrine/SitePages/Home.aspx);
US Navy at Navy Doctrine Library (https://doctrine.navy.mil);
US Air Force at US Air Force Center for Doctrine Development and Education
(http://www.doctrine.af.mil/); and Joint Electronic Library Plus
(https://jdeis.js.mil/jdeis/index.jsp?pindex=0).

## Preface

1. Purpose This multi-Service tactics, techniques, and procedures (MTTP) publication establishes communications tactics, techniques, and procedures (TTP) for tactical command and control (TAC C2) to manage air operations and to control airspace and aircraft. It also establishes TTP for force packaging and direct air support coordination, air-to-air (A/A)
communication, A/A intercept, threat A/A warning, threat surface-to-air warning, and airto-surface communication. 2. Scope This publication provides MTTP for the control and coordination of air operations in TAC C2 managed areas of responsibility (AORs). 3. Applicability This MTTP publication applies to all TAC C2 airspace control elements and warfighters that conduct air operations in AORs managed by the joint force commander (JFC) and overseen by the airspace control authority in accordance with the JFC signed airspace control plan (ACP) and airspace control order (ACO). Operational planners and exercise planners can use this publication to inform the ACP, ACO, the special instructions, the area air defense plan, and rules of engagement.

This publication addresses an avenue for the Services to tap into the intelligence, surveillance, and reconnaissance (ISR) constellation. It provides TTP to leverage current intelligence from platforms like RQ-4H; RC-135; E-8 Joint Surveillance Target Attack Radar System (JSTARS); U-2; unmanned aircraft systems (UASs); space; and cyberspace by contacting the TAC C2. The TAC C2 may be manned by the United States (US) Air Force, Navy, or Marine Corps. TAC C2 would provide the current, consolidated battlespace picture. For example, a ground force commander ordered an Apache to conduct armed reconnaissance in US Army-controlled airspace. The primary targets are enemy air defense and artillery batteries. Unit intelligence briefed the known threat and target locations before departing for a mission, but the Apache has no organic ISR for updates to those locations. During the mission, the Apache would contact TAC C2 for ISR
personnel's updated intelligence on threat and target locations. This information would enhance situational awareness and mission effectiveness.
After attacking multiple targets, the aircrew were out of ordnance but their targets remained. The aircrew would leverage the TAC C2, again, for support. Passing grid locations to TAC C2 enhanced the battlespace picture and enabled re-tasking other assets to strike the targets and support the ground force commander's objective. 4. Implementation Plan Participating Service command offices of primary responsibility will review this publication; validate the information; and, where appropriate, use as a reference and incorporate it in Service manuals, regulations, and curricula as follows:
Army. Upon approval and authentication, this publication incorporates the TTP
contained herein into the US Army Doctrine and Training Literature Program as directed by the Commander, US Army Training and Doctrine Command. Distribution is in accordance with applicable directives listed on the authentication page.

Marine Corps.1 The Marine Corps will incorporate the procedures in this publication in United States Marine Corps (USMC) doctrine publications as directed by the Commanding General, Training and Education Command (TECOM). Distribution is in accordance with the Marine Corps Publication Distribution System.

Navy. The Navy will incorporate these procedures in US Navy training and doctrine publications as directed by the Commander, Navy Warfare Development Command (NWDC) [N5]. Distribution is in accordance with MILSTRIP/MILSTRAP Desk Guide, Naval Supply Systems Command Publication 409.

Air Force. The Air Force will incorporate the procedures in this publication in accordance with applicable governing directives. Distribution is in accordance with Air Force Instruction 33-360, *Publications and Forms Management*.

## 5. User Information

a. US Army Combined Arms Center; USMC, TECOM; NWDC; Curtis E. LeMay Center for Doctrine Development and Education; and Air Land Sea Application
(ALSA) Center developed this publication with the joint participation of the approving Service commands. ALSA will review and update this publication as necessary. b. This publication reflects current joint and Service doctrine, command and control organizations, facilities, personnel, responsibilities, and procedures. Changes in Service protocol, appropriately reflected in joint and Service publications, will be incorporated in revisions to this document. c. We encourage recommended changes for improving this publication. Key your comments to the specific page and paragraph and provide a rationale for each recommendation. Send comments and recommendations directly to:

## Army

Commander, US Army Combined Arms Center ATTN: ATZL-MCD
Fort Leavenworth, KS 66027-6900 DSN 552-4885 COMM (913) 684-4885 E-mail: usarmy.leavenworth.mccoe.mbx.cadd-org-mailbox@mail.mil

## Marine Corps

Commanding General, Training and Education Command Policy and Standards Division, Doctrine Branch ATTN: C466 Quantico, VA 22134 DSN 278-6228 COMM (703) 784-6228 E-mail: doctrine@usmc.mil

## Navy

Commander, Navy Warfare Development Command ATTN: N5 1528 Piersey St, Building O-27 Norfolk, VA 23511-2723 DSN 341-4185 COMM (757) 341-4185 E-mail: nwdc_nrfk_fleetpubs@navy.mil

## Air Force

Commander, Curtis E. LeMay Center for Doctrine Development and Education ATTN: DDJ 401 Chennault Circle Maxwell AFB, AL 36112-6428 DSN 493-7864/1681 COMM (334) 953-7864/1681 E-mail: afddec.ddj@us.af.mil

## Alsa

Director, ALSA Center 114 Andrews Street Joint Base Langley-Eustis, VA 23665-2785 DSN 575-0902 COMM (757) 225-0902 E-mail: alsadirector@us.af.mil

## Summary Of Changes

ATP 3-52.4/MCRP 3-20F.10/NTTP 6-02.9/AFTTP 3-2.8, Multi-Service Tactics, Techniques, and Procedures for Air Control Communication. This revision: Updates:


Additional Air Force TAC C2 players.

WEAPONS and FUEL state communication standardization.

Aspect and Target Angles.

PICTURE communication.
Removes:


UNTARGETED as a fill-in.
Adds:


Picture WEIGHTED component clarification.

TARGETING standardization and associated communication.

Clarifies group JOINED example.

GRIND Operations.

Additional terminology.

| ATP 3-52.4                          | US Army Training and Doctrine Command    |
|-------------------------------------|------------------------------------------|
| Joint Base Langley-Eustis, Virginia |                                          |
| US Army Combined Arms Center        |                                          |
| Fort Leavenworth, Kansas            |                                          |
| MCRP 3-20F.10                       | USMC, Training and Education Command     |
| Quantico, Virginia                  |                                          |
| NTTP 6-02.9                         | Navy Warfare Development Command         |
| Norfolk, Virginia                   |                                          |
| AFTTP 3-2.8                         | Curtis E. LeMay Center for Doctrine      |
| Development and Education           |                                          |
| Maxwell Air Force Base, Alabama     |                                          |
| 2 September 2021                    |                                          |

## Acc Multi-Service Tactics, Techniques, And Procedures For Air Control Communication

EXECUTIVE SUMMARY ........ x CHAPTER I OVERVIEW ........ 1
1. Airspace Control **........ 1** 2. Tactical Command and Control (TAC C2) **........ 2** 3. Assumptions **........ 2**
CHAPTER II TACTICAL ADMINISTRATION (TACADMIN) COMMUNICATION ........ 5
1. TACADMIN **........ 5** 2. Communication Priorities **........ 5** 3. NET Transmissions**........ 6** 4. Check-In Procedure **........ 6** 5. Unable to Make Contact on the Primary Check-in NET **........ 9** 6. Link 16 Fidelity Checks **........ 9** 7. Link 16 ID Procedures **........ 9** 8. NEGATIVE JACKAL **........ 11** 9. WORDS Procedures **........ 11** 10. HAVE QUICK II Procedures **........ 12** 11. In-flight Report **........ 13**

DISTRIBUTION STATEMENT A: Approved for public release, distribution is unlimited.

*Supersedes ATP 3-52.4/MCRP 3-20F.10/NTTP 6-02.9/AFTTP 3-2.8, dated 14 February 2020.

## Executive Summary Acc

Multi-Service Tactics, Techniques, and Procedures (MTTP) for Air Control Communication (ACC) establishes tactics, techniques, and procedures (TTP) to describe the format for direct coordinating communication. Air assets can use these TTP to coordinate force packaging and air-to-air (A/A) and air-to-surface (A/S) missions with tactical command and control (TAC C2) agencies. TAC C2 agencies can use these TTP to control airspace that air assets use to accomplish A/A and A/S missions.

## Chapter I Overview

Chapter I gives an overview of airspace control and describes TAC C2. A list of assumptions are provided for the warfighter to understand appropriate times to apply these TTP.

## Chapter Ii Tactical Administration Communication

Chapter II defines tactical administration. It describes procedures for network transmissions, check in, WORDS, HAVE QUICK, in-flight reports, returning force accountability, and procedural control.

## Chapter Iii Force Packaging And Direct Air Support Coordination

Chapter III describes TTP for roll calls, LOWDOWN, mission timing changes, CHATTERMARK procedures, battlespace handover procedures, and YELLOW/RED communication contracts.

## Chapter Iv Air-To-Air Communication Fundamentals

Chapter IV provides the fundamental ways fighters and TAC C2 agencies communicate about air entities. This lexicon and format for communication are critical for executing A/A intercepts.

## Chapter V Air-To-Air Intercept Communication

Chapter V establishes a communication format for A/A employment and air intercept control. It governs communication fundamentals, format, and integration between fighters and controllers, independent of mission design series (MDS) or type, model, and/or series (T/M/S). This chapter is the baseline for all A/A communication in training and combat. Service-specific differences are annotated.

## Chapter Vi Air-To-Surface Communication

Chapter VI describes aircraft as any air assets executing an A/S mission under TAC C2. This chapter establishes a communication format for A/S employment. It governs communication fundamentals, format, and integration between aircraft and controllers, independent of MDS or T/M/Ss.

## Program Participants

The following commanders and agencies participated in creating this publication:

## Joint

United States (US) Joint Staff, J7, Suffolk, Virginia

## Army

US Army Aviation Center of Excellence, Fort Rucker, Alabama US Army Combined Arms Center, Fort Leavenworth, Kansas US Army Training and Doctrine Command, Joint Base Langley-Eustis, Virginia

## Marine Corps

Marine Aviation Weapons and Tactics Squadron One, Marine Corps Air Station Yuma, Arizona Policy and Standards Division, Doctrine Branch, Quantico, Virginia Training and Education Command, Quantico, Virginia

## Navy

Naval Aviation Warfighting Development Center N7, Topgun, Fallon Naval Air Station, Nevada Navy Warfare Development Command, Norfolk, Virginia

## Air Force

422 Test and Evaluation Squadron, Nellis Air Force Base, Nevada Curtis E. LeMay Center for Doctrine Development and Education, Maxwell Air Force Base, Alabama US Air Force Weapons School, Nellis Air Force Base, Nevada

## Chapter I Overview 1. Airspace Control

a. Airspace control is the capabilities and procedures used to increase operational effectiveness by promoting the safe, efficient, and flexible use of airspace (Joint Publication (JP) 3-52, *Joint Airspace Control*).

b. There are two methods of airspace control: positive and procedural.
(1) Positive Control. A method of airspace control that relies on positive identification (ID), tracking, and direction of aircraft within an airspace, conducted with electronic means by an agency having the authority and responsibility therein (JP 3-52). Positive control requires sensors to locate and identify airspace
users in real time and communications to maintain continuous contact with the
user.
(2) Procedural Control. A method of airspace control which relies on a combination of previously agreed upon and promulgated orders and procedures (JP 3-52). Examples include:

(a) Air defense ID procedures and aircraft ID maneuvers. (b) Voice and digital communications between aircraft and airspace control elements. (c) Airspace control measures, such as low-level transit routes, minimum-risk
routes, coordinating altitude, restricted operations zones, and high-density
airspace control zones. (d) Fire support coordinating measures, such as restrictive fire and no-fire
areas.
c. At the tactical level, airspace control is provided by the interaction between airspace users and airspace control elements (JP 3-52). These may include:

(1) A control and reporting center (CRC).
(2) A tactical air operations center (TAOC).
(3) An E-3 Airborne Warning and Control System (AWACS).
(4) An E-8 Joint Surveillance Target Attack Radar System (JSTARS). (5) A tactical air control center. (6) An E-2 Hawkeye. (7) A direct air support center (DASC). (8) An air support operations center (ASOC).
(9) Air defense airspace management. (10) A brigade aviation element.
(11) Other military and civil air traffic control entities.

## 2. Tactical Command And Control (Tac C2)

a. TAC C2. TAC C2 are airspace control elements under tactical control of the joint force air component commander, joint force maritime component commander, or composite warfare commander (CWC) and use positive and procedural control methods to control airspace and manage air operations. Not all airspace control elements are considered TAC C2.

b. TAC C2 should:
(1) Enable the flow of forces to and from an objective area.
(2) Provide threat warning information and maintain situational awareness (SA)
to the primary objective. (3) Maintain SA of supporting asset status, threat information, and target area information. (4) Maintain air asset deconfliction to and from a working area.
c. The following are TAC C2 capable entities by Service.
(1) Army. None.
(2) Marine Corps. TAOC and early warning and control.
(3) Navy. E-2 Hawkeye, Ticonderoga-class guided missile cruisers (CGs),
Arleigh Burke-class guided missile destroyers (DDGs), Nimitz/Ford-class aircraft
carriers, nuclear (CVNs), amphibious assault ships (general purpose) (LHAs), Wasp-class amphibious assault ships (multi-purpose) (LHDs), and the San
Antonio-class amphibious transport docks (LPDs).
(4) Air Force. AWACS, JSTARS, CRC, Battle Control Center (BCC), and ASOC.

## 3. Assumptions

a. The functional/Service components will adhere to the joint force commander's (JFC's) guidance provided through the rules of engagement (ROE), airspace control plan, airspace control order (ACO), area air defense plan, special instructions (SPINS), and operational tasking (message) (OPTASK). b. The JFC has delegated commit, ID, and engagement authority to the component commanders and authorizes further delegation for mission accomplishment. c. Component commanders have outlined unambiguous commit, ID, and engagement authority to battle managers through ROE.

d. When executing as a standalone entity, the carrier strike group's CWC concept will independently fulfill the roles in paragraphs a.c. The officer in tactical command may delegate authority to the CWC. Guidance outlined by the CWC will be implemented by the following principle warfare commanders:

(1) Air and missile warfare commander.
(2) Sea combat commander. (3) Strike warfare commander.
(4) Information operations warfare commander.
e. The ASOC or DASC is the airspace control element for air action short of the fire support coordination line and below a coordinating altitude. These volumes of airspace are commonly referred to as division assigned airspace or Marine airground task force assigned airspace, respectively.

This page intentionally left blank.

## Chapter Ii Tactical Administration (Tacadmin) Communication

Note: Information transmitted via a network (NET) (e.g., FRIENDLY, GROUP, or THREAT) and examples of NET transmissions are shown in all capital letters.

## 1. Tacadmin

a. TACADMIN consists of all processes and procedures that occur in the TAC C2 area of responsibility (AOR). It relates to:

(1) Interflight and intraflight procedures.
(2) Airborne mission preparation that directly supports executing the tactical mission objective. (3) Examples include: weapon arming, sensor management, personnel recovery package marshalling, and tactical communication checks.
b. TACADMIN does not refer to processes and procedures that coordinate air assets outside the managed AOR. Examples are:

(1) Navigating in civil airspace under civilian air traffic control. (2) Operating aircraft in the terminal area under military tower or local area air traffic control. (3) Controlling air traffic to facilitate arrival to or departure from an operating
base. (4) An example of an exception to 1.b. is an aircraft launched under scramble orders (e.g., an alert status) but operating in civil airspace.

## 2. Communication Priorities

The prioritized and efficient flow of communication is vital to complex, contested air operations. Table 1 specifies the priority for air communication.

## Table 1.  Communication Priorities

1
Flight safety and aircraft emergencies.
2
KILL verification (in a training environment: range training officer (RTO) communications).
3
DEFENDING, SPIKE, and THREAT calls.
4
Requests for controller and fighter targeting situational awareness (i.e., DECLARE or BOGEY DOPE).
5
Response to electromagnetic attack.
6
PICTURE or fill-ins.
7
Tactical administration (e.g., WORDS update).

## 3. Net Transmissions

A call sign is associated with every radio transmission.

a. Directive Transmissions. Aircrew and TAC C2 will use the call sign of the entity being directed.

## Directive Transmission

Directed by HORNET 1: "HORNET 2, TARGET NORTH GROUP." b. Interrogative Transmissions. Calls that are requests for a response will use the "[entity speaking to], [speaking entity]" format.

## Interrogative Transmission

Interrogative from SHOWTIME 11: "MIKE, SHOWTIME 11, DECLARE ADDITIONAL GROUP." c. Descriptive Transmissions. Calls that provide information that does not require a response. Descriptive call will use the same format as interrogative.

## Descriptive Transmission

Descriptive from SHOWTIME 11: "MIKE, SHOWTIME 11, FUEL YELLOW."

d. Relaying a Call.
(1) The communication format is "[entity speaking to], relay, [call sign of entity call *being* relayed]".

(2) Do not include the relaying entity's call sign.

## Relay Transmission

From HOG 1 relayed by SNAKE 11 to MIKE: "MIKE, RELAY HOG 1. STRIKE PACKAGE MILLER TIME." Note: SNAKE 11's call sign is omitted from the transmission.

## 4. Check-In Procedure A. Check In.

(1) The purpose of check in is for aircrew and TAC C2 airspace control elements to establish contact, allow the airspace element to establish accountability of the airborne asset, and to pass critical information to the aircrew before handoff to a final mission controller.

(a) TAC C2 will verify position and identity of the aircraft. (b) TAC C2 will route the aircrew to their mission area. (c) The aircrew will gain updated information for the mission area. (d) The aircrew can check secure communication systems.
(2) The aircrew should establish communication with TAC C2 on a dedicated check-in NET. Dedicated NETs support TACADMIN without interfering with employment.

(3) Once all tactical information has been relayed to the check-in aircraft, TAC
C2 will switch the aircrew to the final controller tactical NET.
Note: When checking in with the final controller, the on-coming aircraft is assumed to be TACADMIN complete.

(4) For continuous operations (e.g., lane handoff), TAC C2 should consider passing big-picture information before pushing air assets to the tactical NET.

(5) Check in should accomplish the items in table 2 before and after mission execution.

## Table 2.  Check-In Procedures

1.
Ensure positive friendly identification. (See note 1.) a.
Correct or valid response to IFF (i.e., modes 1, 2, 3A, 4, 5, and S).
b.
PPLI is present on Link 16 or similar data link systems.
c.
Secure voice with radar correlation.
d.
Authentication procedures (e.g., challenge and reply, time, or ISOPREP).
e.
Adherence to ACO.
f.
Adherence to briefed sanctuaries (e.g., TL, TR, MRR, or LLTR).
2.
Accomplish ALPHA CHECK from BULLSEYE. (See note 2.)
3.
Verify WORDS received via digital means (primary; e.g., J28.2) or voice.
4.
Provide safety-of-flight information (e.g., airspace coordinating measure, airspace changes, or block changes).
5.
Check weather. a.
Combat. Update operating area weather that impacts the briefed plan.
b.
Training. Relay the weather plan or war call.
6.
Accomplish a post-mission in-flight report.
Notes: 1. Specific procedures are outlined in the SPINS. 2. ALPHA CHECK correlation is defined as within 3 nm. Solving for correlation rests with the aircraft checking in. 3. Multiple TAC C2 NETs may be used to accomplish these check-in tasks.

Legend: ACOairspace control order IFFidentification, friend or foe ISOPREPisolated personnel report LLTRlow-level transit route MRRminimum-risk route nmnautical mile

PPLIprecise participant location and identification SPINSspecial instructions TAC C2tactical command and control TLtransit levels TRtransit route

b. Aircrew Check In with TAC C2.
(1) The full aircraft check-in format should include mission number and aircraft number and type, position and altitude, ordnance, PLAYTIME, capabilities, and abort code.

Note: MNPOPCA is a mnemonic useful for remembering the order of check in. (See table 3.)

Mission Number Number and Type of Aircraft Position and Altitude Ordnance (if applicable) PLAYTIME

Capabilities (e.g., laser, infrared pod, data link) Abort Code
(2) AS FRAGGED Check In. AS FRAGGED means the unit or element is performing as briefed, in accordance with the air tasking order (ATO) or air plan.

(a) Use an abbreviated aircraft check when aircraft are on a published ATO or air plan. (b) Check in with the aircrew's mission number, AS FRAGGED, and request an ALPHA CHECK from the assigned BULLSEYE. The ALPHA CHECK provides aircrew a position system check.

## Check In As Fragged

Aircraft: "MISER, HORNET 1, MISSION NUMBER 5-1-1-1, CHECKING IN AS FRAGGED, REQUEST ALPHA CHECK DEPOT." TAC C2: "HORNET 1, MISER, CONTACT, ALPHA CHECK DEPOT 270/30."
(3) Aircrew must check in "with exceptions" if there are deviations.

(a) Communicate pertinent exceptions to the current mission. (b) The following deviations should always be communicated by aircrew and controllers at check in:

- Number of aircraft (e.g., a three-ship flight when four-ships are
anticipated).
- Ordnance. WEAPONS YELLOW or RED or changes to the tasked
loadout.
- PLAYTIME. FUEL YELLOW or RED.
- Capabilities (e.g., TIMBER SOUR, NEGATIVE JACKAL, GADGET
BENT).
- Other pertinent mission-specific exceptions (identify them during
mission planning).
(c) The following is an example of a check in with exceptions.

## Example #1: Check In With Exceptions

Aircraft: "MISER, EXXON 1, MISSION NUMBER 6-1-1-1, CHECKING IN WITH EXCEPTIONS, REQUEST ALPHA CHECK BULLSEYE." TAC C2: "EXXON 1, MISER, ALPHA CHECK BULLSEYE 270/30, CONTINUE WITH CHECK IN." Aircraft: "EXXON 1, OFFLOAD, FRAG MINUS 30 K."
(d) The following is an example of a check in with controller exceptions:

## Example #2: Check-In With Tac C2 Exceptions

Aircraft: "MISER, HORNET 1, MISSION NUMBER 5-1-1-1, CHECKING IN AS FRAGGED, REQUEST ALPHA CHECK BULLSEYE." TAC C2: "HORNET 1, MISER, ALPHA CHECK BULLSEYE 270/30." Aircraft: "HORNET 1." TAC C2: "MISER, TIMBER SOUR." Aircraft: "HORNET 1."
(4) Unmanned aircraft systems (UAS) should check in with TAC C2 via tactical chat using the same format.

## Unmanned Aircraft System (Uas) Check-In Example <#Uas_Ops Chat Room>

MUSTANG 01: KINGPIN, CHECKING IN AS FRAGGED, REQUEST ALPHA CHECK BULLSEYE.

## 5. Unable To Make Contact On The Primary Check-In Net

a. The aircrew and TAC C2 should refer to the CHATTERMARK procedures. b. If still unable to complete the check in, contact the final controller and, at a minimum, receive an ALPHA CHECK and WORDS update.

## 6. Link 16 Fidelity Checks

a. Fidelity checks will begin as soon as aircraft have operational systems and the checks will be completed routinely and prior to entering the AOR.

b. Three attempts will be made to conduct Link 16 fidelity checks. If unsuccessful after the third attempt, the affected asset will report TIMBER SOUR.

## 7. Link 16 Id Procedures

a. All TAC C2 agencies have change ID authority.
b. If an ID difference exists on an air track, coordination will be accomplished on the track supervision net to verify the correct ID as in the following example.

## Air Track Id Coordination Mojo: "Barnyard, Mojo, Track 0-1-2-3-3 Hostile, Tag Flanker" Barnyard: "Barnyard, Track 0-1-2-3-3 Hostile, Flanker."

c. Table 4 outlines the standard J3.5 track ID plan for specific events. Table 5 outlines the J12.0 mission assignments by aircraft.

| Event                                           | Track or Specific Type                            |
|-------------------------------------------------|---------------------------------------------------|
| Convoy                                          | Convoy moving.                                    |
| Theater Ballistic Missile (TBM)                 | Ballistic missile defense site.                   |
| TBM Launch Position                             | Ballistic missile preparing for launch.           |
| TBM Fire                                        | Hostile ballistic missile firing.                 |
| High-Value Individual (HVI)                     | Hostile train.                                    |
| Surface-to-air Missile (SAM)                    | Hostile SAM site.                                 |
| Troops in Contact                               | Hostile troop concentration.                      |
| Command and Control (C2)                        | Hostile C2 site.                                  |
| Air Defense Artillery (ADA)                     | Hostile ADA.                                      |
| Uncorrelated Mover (single)                     | Unknown vehicle.                                  |
| Uncorrelated Rotator                            | Neutral radar site.                               |
| Downed Aircraft                                 | J3.1 downed aircraft (bailout or pilot in water). |
| Friendly troop concentration search and rescue. | Downed Aircraft Refined                           |
| Coordinates                                     |                                                   |

Note: The first platform to correlate a kill holds the responsibility for dropping the track once the striking aircraft calls SPLASH with a BULLSEYE location and type.

Cockpit Displayed Messages
Mission Type
Investigate
Target
Smack
A-10C
INV
Engage
Attack
B-1B
INV
Intervene
Attack
B-52
INV
TARGET
Attack
F-15
Visual ID
Interdict
Attack
F-16
Orbit
Interdict
Attack
FA-18
INVSTGAT
COMMIT
ATTACK
F-22
INV
Engage
Attack
F-35
INV
Armed Reconn
Attack

Note: Investigate can also be "INTERROGATE". Target can also be "PRIORITY KILL".

## 8. Negative Jackal

Fighters should communicate NEGATIVE JACKAL to controllers during check in or during the mission when they are not receiving accurate surveillance information.

a. If fighters are NEGATIVE JACKAL, the controller should ensure correlation is met prior to targeting. b. If correlation is in question, fighters may request the controller DECLARE a group or request bearing, range, altitude, and aspect (BRAA) to a GROUP prior to weapons employment.

## 9. Words Procedures

a. WORDS is a directive or interrogative call for further information or directives pertinent to a mission. WORDS are designated by ATO day, numbered sequentially, and established and deleted individually. For example, WORDS AA01 (pronounced ALPHA ALPHA 0-1) would represent the first WORDS generated on ATO day AA.

(1) WORDS are generated by the TAC C2 agency outlined in the SPINS. (2) The first WORDS for a new ATO day should incorporate pertinent information from the previous day. (3) WORDS are limited in scope to each operating area.
b. Examples of WORDS information are:
(1) Changes to the package. (2) NET changes (e.g., a new tactical mission NET). (3) Timing changes. (4) Threat updates (e.g., a new active threat axis or sector).
(5) Change to threat warning condition or weapons control status. (6) Weather affecting execution.
c. TAC C2 will relay WORDS to all assets in the operating area, the joint air operations center (JAOC), tactical air command center, and appropriate CWC.

(1) New WORDS will be relayed by TAC C2. (2) TAC C2 will use digital means (e.g., J28.2), to the maximum extent possible, when passing WORDS to air assets.
d. Aircraft that check in with TAC C2, should consider adding the current WORDS they have at the check-in call (i.e., "CHECKING IN WITH WORDS BRAVO ALPHA 0-1").

## Words Change

TAC C2: "HORNET 1, GAMBLER, WORDS BRAVO ALPHA 0-2 NOW CURRENT." Aircraft: "GAMBLER, HORNET 1 WITH WORDS BRAVO ALPHA 0-1." TAC C2: "HORNET 1, GAMBLER WORDS BRAVO ALPHA 0-2 TO FOLLOW. NEW THREAT AXIS 3-1-0, THREAT WARNING CONDITION RED, WEAPONS CONTROL STATUS TIGHT." e. In the previous example, HORNET 1 had WORDS BA01.

(1) TAC C2 only had to relay WORDS BA02.
(2) If the aircrew had checked in without WORDS, TAC C2 would have relayed
all information in WORDS BA01 and BA02.
f. When there are multiple command and control agencies in an operating area, WORDS are generated by the assigned TAC C2 agency based on the tactical situation and inputs from other agencies or units.

## 10. Have Quick Ii Procedures

a. Successful HAVE QUICK II requires a synchronized time-of-day (TOD) signal, MICKEY, between all communicators. The following is a prioritized list of TOD sources.

(1) Global Positioning System. (2) Auto-TOD from an operating location.
(3) Aircrew manual MICKEY (e.g., FA-18 section lead pass to DASH 2).
(4) TAC C2 auto TOD. (5) TAC C2 manual MICKEY.

## Manual Mickey

Aircraft: "STRIKE, DOOM 1, REQUEST MICKEY." TAC C2: "DOOM 1, MICKEY IN FIVE." b. Once the aircrew has received a tone, have them attempt a prebriefed HAVE QUICK II NET with instructions on a return frequency, if it fails.

## Have Quick Ii Check

Aircraft: "DOOM 1, GOOD MICKEY." TAC C2: "DOOM 1, STRIKE, PUSH ACTIVE TAD 57 POGO."
Note: AWACS manual MICKEY is single tone only. Expect a multiple tone MICKEY from other TAC C2 agencies.

## 11. In-Flight Report

This report expedites the information flow to the JAOC. It can aid in bomb hit assessments that inform retasking assets (e.g., reattack).

a. Theater SPINS or local guidance will outline in-flight report procedures. b. A dedicated in-flight report frequency may be used to pass this report. c. JP 3-09.3, *Close Air Support,* provides a table for reference. (See table 6.)

| Item                                       | Example Radio Communication              |
|--------------------------------------------|------------------------------------------|
| Request from Aircraft                      | "COWBOY, HOSS 01, IN-FLIGHT REPORT."     |
| "HOSS 01, GO WITH IN-FLIGHT REPORT."       | Acknowledgment from Tactical             |
| Command and Control                        |                                          |
| Line 1Call sign                           | "HOSS 01 FLIGHT."                        |
| Line 2Mission number                      | "0552."                                  |
| Line 3Location                            | "N3645 W11523" (latitude and longitude), |
| "10S 0559 4282" (grid),                    |                                          |
| or "GAMECOCK" (place name/operating area). |                                          |
| Line 4Time on target                      | "1518Z."                                 |
| Line 5Result                              | "5 ENEMY TANKS DESTROYED, 5 LIGHT        |
| TRUCKS DISABLED, 30 TROOPS IN THE          |                                          |
| OPEN."                                     |                                          |
| Remarks                                    | "SIX DIRT NORTH. REMAINING TANKS         |
| DISENGAGING WEST. LIGHT SURFACE-TO-        |                                          |
| AIR FIRE TO 10,000 FEET, 5 MILES SOUTH OF  |                                          |
| TARGET AREA."                              |                                          |

## 12. Return To Forces Phase

TAC C2 check-in controller should attempt to ensure the following for returning forces.

a. Verify aircraft are SQUAWKING appropriate modes and codes prior to friendly missile engagement zone (MEZ) entry. b. Obtain mission results and flight statuses via Link 16 or voice, and pass the inflight report to the JAOC or CWC.
c. Execute Wounded Bird, battle damage, or hung ordnance notification procedures in accordance with theater directives.

(1) FORCE TELL the track until directed by higher headquarters. (2) Obtain call sign, status, and track number of the aircraft. (3) Monitor and track the aircraft until it is out of radar coverage or until it is under recovery base approach control to ensure a safe return. (4) Prepare to coordinate combat search and rescue operations.
d. Pass information on HOME PLATE weather and operational status (e.g., runway closures or recovery procedures).

## 13. Establishing Procedural Control

When TAC C2 moves from positive to procedural control, the aircrew should be advised, to the maximum extent practical:

a. Transmit, "NEGATIVE CONTACT", when an aircraft checks in.
b. TAC C2 may use, "PROCEDURAL CONTROL IN EFFECT", when the current operating area standard is positive control.
c. If the operating area standard is procedural control, then TAC C2 does not need to state, "PROCEDURAL CONTROL IN EFFECT".

## Procedural Control

"GRIM 11, VULTURE, NEGATIVE CONTACT, PROCEDURAL CONTROL IN EFFECT."

## Chapter Iii Force Packaging And Direct Air Support Coordination

Missions that involve a mission commander (MC) require extensive coordination to execute. The MC and TAC C2 should establish a plan to receive the LOWDOWN, obtain force package accountability before and after mission execution, establish backup communication plans, and establish air communication contracts. This section, and the following chapters, establish baseline tactics, techniques, and procedures for these items.

## 1. Force Package Accountability And Roll Call

The MC should ensure the required minimum forces are ready. Two techniques are a TAC C2-provided update or a roll call.

a. TAC C2 Update. TAC C2 should maintain a tally of players that have checked in. At a predetermined time, TAC C2 provides the MC with the current players.

## C2 Update

"DARKSTAR, PACKAGE BRAVO WHISKEY, MINUS LION 01, MINIMUM FORCES MET". b. Roll Call. Roll call is initiated by the TAC C2 or MC, at a predetermined time.

Once initiated, each aircraft, flight lead, or package lead (as determined by the MC) will respond with call sign in a predetermined sequence. As a technique, this sequence can follow the call sign order on a coordination card.

## Flight Lead Roll Call Example

Package BRAVO WHISKEY Flight Leads: EAGLE, VIPER, BONES, GROWL, MOJO. MC: "PACKAGE BRAVO WHISKEY, ROLL CALL." Flight Leads Respond in Sequence: "EAGLE", "VIPER WITH EXCEPTIONS", "BONES", "GROWL", "MOJO".

MC: "VIPER GO WITH EXCEPTIONS."
VIPER: "VIPER MINUS 2." If a flight does not respond to the roll call, the MC can query TAC C2.

## Package Commander (Pc) Roll Call Example

Package BRAVO WHISKEY PCs: Escort, Strike, Airlift, TAC C2. MC: "PACKAGE BRAVO WHISKEY, ROLL CALL." PCs Respond in Sequence: "ESCORT WITH EXCEPTIONS", "STRIKE", "AIRLIFT", "TAC C2". MC: "ESCORT GO WITH EXCEPTIONS." Escort PC: "ESCORT MINUS RAPTOR. MINIMUM FORCES MET."

c. Times to consider initiating a roll call.
(1) Post LOWDOWN. (2) When there are updated WORDS.
(3) When forces completed their mission and are returning. (4) When there is a suspected or known loss of an air asset. (5) When there is a timing change to the mission. (6) When the weather plan changes. (7) When there is key mission enabler fallout. (8) Post CHATTERMARK on a new NET.

## 2. Lowdown

LOWDOWN is a request for the tactical ground picture in an area of interest. TAC C2 should correlate all factor ground systems using the BULLSEYE format.

Note: When communicating with United States (US) Army or US Marine Corps rotarywing and UAS, pass surface threat information in military grid reference system (MGRS), if known. Attempt to provide at least a 6-digit grid.

a. LOWDOWN is passed at a briefed time (e.g., 5 minutes prior to mission execution) and is immediately followed by a roll call. b. An aircrew may request LOWDOWN but should do so in accordance with communication priorities (allow 30 to 60 seconds for TAC C2 to compile LOWDOWN). c. For aircraft not in the tactical NET during the initial LOWDOWN, it is passed upon initial check in as part of the WORDS. d. LOWDOWN may not be required for each mission set, such as when fighters are conducting a defensive counterair mission in a permissive environment. e. LOWDOWN is passed digitally, via Link 16 and tactical chat, or verbally. In order of priority (unless otherwise briefed), the LOWDOWN should include:
(a) Strategic surface-to-air missile (SAM) systems ACTIVE or AWAKE within the last 8 hours that were not a part of the briefed threat defensive missile order of battle. Expect strategic SAMs references using mission planning naming conventions. (b) Tactical SAMs ACTIVE or AWAKE within the last hour (e.g., enemy naval tactical SAM).

(c) MOVERS/ROTATORS meeting briefed reporting criteria. (d) Additional entities, events, or areas of interest applicable to the mission.

## Lowdown Example

"GOLIATH, LOWDOWN. TWO ACTIVE BULLSEYE 090/10, EIGHT ACTIVE BULLSEYE 085/13, SIX AWAKE BULLSEYE 075/14, ROTATOR BULLSEYE 260/15. HOSTILE CONVOY BULLSEYE 270/10 TRACK EAST." f. For tactical SAMs and MOVERS, the order of dissemination is:

(1) Closest MEZ to friendly forces. (2) Closest MEZ to friendly axis of attack or ingress routes. (3) Most lethal.

## 3. Timing Changes

a. ROLEX. Timeline adjustment in minutes; always referenced from original preplanned mission execution time.

(1) ROLEX is used to adjust the mission timing as a whole.
(2) PLUS is assumed. (3) If a time on target (TOT) window extension is required to adhere to the ROLEX, TAC C2 agencies should request approval and pass it to the affected flights. (4) ROLEX is made in 5-minute increments and is not additive.

## Rolex Example

Original package WHISKEY ALPHA mission start time: 1500Z. "COWBOY, PACKAGE WHISKEY ALPHA, ROLEX 10." New mission start time: 1510Z. "COWBOY, PACKAGE WHISKEY ALPHA, ROLEX 15." New mission start time: 1515Z. b. SLIP. SLIP is time delay to individual flight or element event. SLIP is not additive.

## Slip Example

Original TOT: 1500Z. "HARDROCK, HOSS 1, SLIP TOT 6 MINUTES." New TOT: 1506Z. "HARDROCK, HOSS 1, SLIP TOT 9 MINUTES." New TOT: 1509Z. c. For changes to training vulnerability times, MCs and TAC C2 should use plain language to avoid confusion.

## 4. Chattermark Procedures

a. CHATTERMARK procedures are established to transition from primary to alternate tactical NETs. b. The CHATTERMARK plan should:
(1) Provide alternate NETs, which reside in different frequency bands.

(2) Prioritize secure, frequency-hopping forms of radio communication. (Tailor them based on threat communication jamming capabilities.)
(3) Establish a "get well" NET, such as the TAC C2 check-in NET. If the aircrew are unsure of the current tactical NET, they can switch to the "get well" NET to receive direction from TAC C2. (4) Outline the criteria and authority for executing a CHATTERMARK. This resides with MC or a designated PC. Degradation on the primary tactical NET
due to communications jamming or system limitations for the aircrew or controller
(e.g., UNABLE HAVE QUICK) are the most common reasons to CHATTERMARK.

c. Request a CHATTERMARK via a "Request POGO [NET name in color and number]" (e.g., INDIGO 03). d. If a CHATTERMARK is directed, all assets will switch to the planned alternate NET, in accordance with the CHATTERMARK plan, and await a roll call.

(1) TAC C2 or MC will repeat CHATTERMARK three times on the primary tactical NET prior to switching to the alternate tactical NET and publish a digital message. (2) If able, TAC C2 will simulcast on the old, affected NET and the new NET. (3) TAC C2 simulcast will continue until force accountability is confirmed on the new NET.

(4) Force Accountability on New NET.
(a) Per the mission plan, flight leads or PCs should communicate their call sign on the new NET. TAC C2 should only acknowledge if communication time allows in accordance with communication priorities. (b) TAC C2 should note accountability as players check in. TAC C2 will accomplish a ROLL CALL if needed. (c) TAC C2 should communicate "NET SWEET" on the new NET once all players have checked in.

## Chattermark Example

Primary NET degradation is noted by TAC C2. Transmitting on the Old NET: MISER (TAC C2): "CHATTERMARK, CHATTERMARK, CHATTERMARK." Transmitting on New NET: Flight Leads: "EAGLE." "RAPTOR." "HORNET." "GROWLER." MISER: "NET SWEET."

## 5. Battlespace Handover Procedures

a. A positive handoff is required by the off-going and on-coming lane commander.
(1) PUSH. On-coming aircraft may enter the operating area (e.g., defensive
counterair lane). (2) COMMIT. When directed by the off-going aircraft, this call transitions
communication priority to the on-coming aircraft to take over as the lane commander. (3) Lane Commander Transition. The off-going lane commander will get positive communication lane handoff to the on-coming lane commander.

## Lane Handoff

Off-going Lane Commander: "HORNET 1, YOU HAVE THE LANE." On-coming Lane Commander: "HORNET 1, HAS THE LANE." b. The off-going lane commander will pass critical mission information to TAC C2 in accordance with theater in-flight report procedures.

(1) TAC C2 will use this information to update WORDS or LOWDOWN. (2) TAC C2 should pass big-picture information to the oncoming lane
commander before pushing assets to the tactical frequency.

## Example 1

"TEN GROUPS, TWO PACKAGES, NORTH PACKAGE TARGETED BY SWEEP. SOUTH PACKAGE TARGETED BY BIG STICK."

## Example 2

"TWELVE GROUPS, LEADING EDGE FOUR GROUP WALL TARGETED BY RAPTOR." c. TAC C2 will relay critical information affecting off-going aircraft return-to-base procedures. Pass information on weather and airfield issues (e.g., runway closures). d. Refer to other mission-specific publications for positive handoff of mission command roles (e.g., strike coordination and reconnaissance or close air support).

## 6. Yellow And Red Statuses

a. Unless otherwise briefed, YELLOW and RED are defined as:
(1) YELLOW: One engagement option available (per type, model, and/or series
(T/M/S) or mission design series (MDS) specific primary mission set).
(2) RED: No engagement option is available due to either a FUEL, WEAPON, or sensor limitation.
b. Aircraft must relay when they are YELLOW to TAC C2.
TAC C2 is responsible to coordinate on-station relief prior to the aircraft communicating RED on the primary NET.

## Fuel/Weapons State Example

Fighter that is FUEL red and WEAPONS green will report: "RAMBO 01, FUEL RED, WEAPONS GREEN."

## Chapter Iv Air-To-Air Communication Fundamentals

Note: For the purpose of this publication, controller is a general term used to define the individual providing tactical control of an intercept or mission. The term "fighter" is used throughout this chapter. Fighter information applies to any aircraft capable of employing A/A ordnance. Controller and fighter are used independent of platform or Service.

## 1. Communication Fundamentals

a. A GROUP is the way TAC C2 and aircraft describe other air assets, and is used to describe unknown or enemy aircraft. b. The PICTURE establishes a common tactical air image and describes the spatial relationship of GROUPs.

## 2. Group

a. A GROUP is any number of air CONTACTs within 3 nautical miles (nm) in azimuth and range of each other.

(1) CONTACT is an individual radar return within a GROUP. (2) SINGLE CONTACT is the assumed STRENGTH for all GROUPs. More CONTACTs are specified (e.g., SINGLE GROUP TWO CONTACTs).
Note: The controlling platform's capabilities and limitations will determine if controllers will communicate the number of CONTACTs in a GROUP. If unable to determine the number of CONTACTs, but assessed to be three or more, controllers will only use the fill-in, HEAVY.

b. GROUPs are distinguished by either a unique name or unique position.
(1) There are four unique naming conventions used:
(a) Cardinal Relationship (e.g., NORTH GROUP, SOUTH GROUP). (b) Range Relationship. Relationship relative to a specific aircraft perspective (e.g. LEAD GROUP, TRAIL GROUP). (c) Combined Cardinal and Range Relationship (e.g., NORTH LEAD GROUP). (d) Descriptive Name (e.g., SINGLE GROUP, ADDITIONAL GROUP, POP-
UP GROUP).
(2) Unique Position Reference. GROUPs can be distinguished using unique position names such as BULLSEYE, BRAA, or geographic reference (GEOREF).

## 3. Core Information Format

Controllers and air assets will use the core information format to communicate GROUPs:

a. Total Number of GROUPs. b. GROUP Location (i.e., BULLSEYE, BRAA, or GEOREF).
c. Altitude (rounded to the nearest thousands of feet). d. Track direction or specific aspect (e.g., cardinal/sub-cardinal or
HOT/FLANK/BEAM/DRAG). e. Declaration. f. Fill-ins (as appropriate).

## 4. Group Location

a. BULLSEYE (primary method to communicate the GROUP location).
(1) BULLSEYE is an established reference point from which the position of an object can be referred to by bearing (magnetic) and range (nm).

(2) BULLSEYE information is rounded to the nearest degree and nm.
(a) For example, BULLSEYE 225/30 means 30 nm on a magnetic bearing of 225 degrees from the BULLSEYE location. (b) It is communicated "two-two-five thirty". (c) If an aircraft is within 5 nm of BULLSEYE, controllers may describe the GROUP as AT BULLSEYE unless that GROUP is to be targeted.

## Group At Bullseye Example

"SHOWTIME 11, LEAD GROUP, AT BULLSEYE, THIRTY-NINE THOUSAND, TRACK NORTH, HOSTILE."
(3) Use the code name for BULLSEYE when directed by SPINS.

## Bullseye Code Name Example

BULLSEYE Code Name: ROCK. "MIKE, SOUTH GROUP, ROCK 255/29, THIRTY-NINE THOUSAND, CAP, HOSTILE."
(4) BULLSEYE will not be truncated to "bull" to avoid it being misinterpreted as "BRAA".

b. Bearing Range Altitude and Aspect (BRAA).
(1) BRAA information for bearing and range are rounded to the nearest degree and nm. (2) BRAA calls provide target bearing, range, altitude, and aspect relative to the specified FRIENDLY aircraft. For example, BRAA 225/10 means 10 nm on a magnetic bearing of 225 degrees from the FRIENDLY aircraft. It is communicated "two-two-five ten".

(3) Controllers should use the BRAA format if the information being communicated pertains only to one specific aircraft or if responding directly to the following fighter requests: BRAA, BOGEY DOPE, and SNAPLOCK. (4) Controllers will also use the BRAA format when providing a THREAT call to an aircraft.

## Threat Call Example

"SHOWTIME 11, LEAD GROUP, THREAT BRAA 270/55, THIRTY-NINE THOUSAND, FLANK NORTHEAST, HOSTILE."

c. GEOREF Point.
(1) The controller may use a GEOREF to provide the approximate location of a GROUP. (2) Examples of GEOREFs may be a prominent natural feature, such as a mountain peak, or a prominent manmade structure, such as an airfield.

## Geographic Reference Example

Prominent Enemy Airfield Code Name: DEPOT. "SHOWTIME 11, LEAD GROUP, AT DEPOT, THIRTY-NINE THOUSAND, CAP, HOSTILE."

## 5. Group Altitude

a. Fighters and controllers will round altitudes to the nearest thousand feet indicated on their system. b. Controllers will not use LOW or HIGH in place of the altitude and will use "ALTITUDE UNKNOWN" if the controlling platform is capable of determining altitude, but a solution is not available. c. Controllers will omit altitude from the communication format if the controlling platform is not capable of generating an altitude.

d. Altitude STACKS.
(1) Altitude separation in a GROUP greater than or equal to 10,000 feet are voiced as a STACK stating the higher altitude first, then the lower altitude.

## Altitude Stack Example

"SHOWTIME 11, NORTH GROUP BRAA 300/32, STACK THIRTY-TWO THOUSAND AND EIGHT THOUSAND, HOT, HOSTILE, TWO CONTACTS, FLANKER."
(2) If the STACK has two or more altitude separations of 10,000 feet within the group, then controllers may voice the number of CONTACTs HIGH/MEDIUM/LOW or at specific altitudes as fill-in information.

## High/Medium/Low Altitude Stack Example

"HARDROCK, NORTH GROUP UTAH 300/12, STACK THIRTY-FIVE THOUSAND and TWENTY-FOUR THOUSAND, TRACK WEST, HOSTILE, HEAVY, THREE CONTACTS, TWO HIGH, ONE LOW."

## Specific Altitude Example

"BARNYARD, ADDITIONAL GROUP PEAK 200/12, STACK THIRTY-FIVE THOUSAND, TWENTY-FOUR THOUSAND and TEN THOUSAND, TRACK WEST, HOSTILE, HEAVY, THREE CONTACTS."

## 6. Track Direction And Specific Aspect

a. Track direction will always be used to communicate a GROUP via BULLSEYE
and communicated with the cardinal or sub-cardinal direction (e.g., TRACK SOUTH, TRACK NORTHEAST).

b. PICTURE Exception.
(1) If all GROUPs in a traditional PICTURE, LEADING EDGE, or PACKAGE are tracking the same direction other than hot, controllers should use the term TRACK with the cardinal direction following the PICTURE label.

## Groups Track The Same Direction Example

"MIKE, TWO GROUPS RANGE 30, TRACK EAST. LEAD GROUP ROCK 145/60, THIRTY-FIVE THOUSAND, HOSTILE. TRAIL GROUP TWENTY THOUSAND, HOSTILE."
(2) If amplifying the PICTURE with TRACK direction, controllers should not provide a track direction for every GROUP in the picture.

c. Specific aspects, as depicted in figure 1, are used when correlating a group to a specific fighter and will be used when communicating with the BRAA format.

(1) Specific aspects (i.e., HOT, FLANK, BEAM, and DRAG) are determined by the GROUP target aspect (TA) or aspect angle (AA) to the fighter. (2) FLANK, BEAM, DRAG are accompanied with a cardinal/sub-cardinal direction (e.g., DRAG WEST).

Note: If the controller assesses GROUPs in a CAP, "CAP" may be communicated in place of TRACK direction or a specific aspect.

d. MANEUVER Description (TRACK Direction or Specific Aspects). e. Controllers may use "maneuver hot" to communicate groups/contacts that have maneuvered toward the fight axis. f. When controllers assess GROUP maneuvers during the PICTURE call and are unable to determine the TRACK direction or aspect, controllers may use MANEUVER instead of the TRACK direction.

## Group Maneuvers Example

"TANGO, TWO GROUPS RANGE 25 OPENING. LEAD GROUP BULLSEYE 265/18, THIRTY-FIVE THOUSAND, MANEUVER, HOSTILE. TRAIL GROUP, THIRTY-FIVE THOUSAND, TRACK NORTH, HOSTILE."

## 7. Declaration

a. A declaration is required to communicate a GROUP via BULLSEYE or BRAA.
b. Declaration is BOGEY, FRIENDLY, NEUTRAL, BANDIT, or HOSTILE.

## 8. Fill-In Information

a. Fill-ins increase descriptive details about a GROUP.
b. Fill-ins are prioritized as follows:
(1) HEAVY and Number of CONTACTs.
(a) A GROUP is HEAVY if it is known to contain three or more CONTACTs. (b) Provide the number of CONTACTs in a GROUP, if it is determined.
(c) Fighters will use STRENGTH and controllers will use the term
CONTACTs to distinguish who is providing the STRENGTH assessment.

## Contacts Versus Strength Example

Controller: "CLUBHOUSE, WEST GROUP FOUR CONTACTS." Fighter: "SHOWTIME 12, EAST GROUP STRENGTH THREE."
(2) Platform/Type. Controllers will provide an aircraft platform (e.g., fighter or bomber), North Atlantic Treaty Organization (NATO) type designator (e.g., FULCRUM or FLANKER), or as mission planned with PICTURES and requests for SA to that GROUP. (3) HIGH. Contact is greater than 40,000 feet mean sea level. HIGH can be used as a fill-in.

(4) FAST or VERY FAST. These definitions are provided as references.
(a) FAST. Target speed of 600900 knots ground speed or 1.01.5 mach.
(b) VERY FAST. Target speed greater than 900 knots or 1.5 mach.

## Fill-Ins Example

"DRAGNET, NORTH GROUP, BULLSEYE 270/15, FORTY-TWO THOUSAND, TRACK WEST, HOSTILE, HIGH, VERY FAST."

(5) UNTARGETED.
(a) If a GROUP has not been targeted inside the briefed targeting range, then the controller should use the term UNTARGETED. UNTARGETED will follow Group name/label to describe the priority GROUPS that are a risk to the mission or force (e.g., an enemy approaching the mission fail line).

## Untargeted Example

"DRAGNET, NORTH GROUP UNTARGETED, BULLSEYE 270/15, TWENTY THOUSAND, TRACK WEST, HOSTILE."
Note: US Navy assets will issue directive targeting to fighters who are inside the targeting range if the controller assesses targeting has not been issued or is not sound.

(b) Tactics selection per the fighter's targeting plan will determine the applicability of UNTARGETED. (c) If a fighter calls TARGETED or acknowledges directive targeting, contracts for UNTARGETED and THREAT calls are cancelled. (d) Controllers could use UNTARGETED or issue directive targeting to the appropriate GROUP if the inside targeting range and targeting are assessed to be unsound.

(6) TARGETED BY, LEANING ON, THREAT TO.
(a) TARGETED BY provides SA that a GROUP is already TARGETED.

## Targeted By Example

Fighter: "MIKE, EAGLE 11, DECLARE NORTH GROUP." Controller: "EAGLE 11, NORTH GROUP, BULLSEYE 285/35, TWENTY THOUSAND, TRACK EAST, HOSTILE, TARGETED BY HORNET 2."
(b) Targeting responsibility is cancelled when the fighters communicate any of the following: DROP(ING) (GROUP name), BLOW(ING) THROUGH, STIFF ARM, SPITTER, or executes an out. (c) LEANING ON aids in assessing which aircraft a THREAT is possibly targeting.

- Making an accurate LEANING ON assessment is increasingly difficult with improved THREAT capabilities. For example, a FLANK or BEAM THREAT could be employing ordnance while LEANING ON another fighter.

- LEANING ON assessments are reserved for when fighters are in COLD
operations.

## Leaning On Example

"DARKLORD, SINGLE GROUP ROCK 256/49, THIRTY-NINE THOUSAND, TRACK EAST, HOSTILE, FLANKER, LEANING ON EAGLE 1."
(d) THREAT TO is reserved for when fighters are in COLD operations and a fighter does not meet the minimum recommit range.

## Threat To Example

"MIKE, TWO GROUPS AZIMUTH 25. NORTH GROUP, ROCK 285/35, THIRTY- FIVE THOUSAND, TRACK EAST, HOSTILE, THREAT TO HORNET 1. SOUTH GROUP THIRTY THOUSAND, TRACK EAST, HOSTILE."
(7) IMPACT (PLUS Time of Flight).

(a) Controllers will add the IMPACT time to any FRIENDLY surface-to-air (S/A) fires when operating in a joint engagement zone or fighter engagement zone.

## Impact Example 1

"GAMBLER, BIG STICK AWAY TRAIL GROUP, IMPACT 1 PLUS 15."
(b) The IMPACT time is used to aid follow-on fighter targeting, decision making, and ensure fires deconfliction. (c) IMPACT time can be used as a PICTURE fill-in as well.

## Impact Example 2

"GAMBLER, TRAIL GROUP ROCK 180/85, THIRTY THOUSAND, TRACK NORTH, HOSTILE, IMPACT 1 PLUS 15."

c. Inner GROUP Formations.
(1) When describing an inner GROUP formation, controllers and fighters will use the terms described in Figure 2, Inner Group Formations. (2) Controllers and fighters should name the inner GROUP formation when this call will enhance fighter targeting or SA approaching the merge. (3) Inner GROUP formations should be used inside expected radar resolution ranges.

## 9. Picture

a. PICTURE is a request to provide information pertinent to the mission in a BULLSEYE format, unless briefed otherwise.

b. The PICTURE establishes a common tactical air image and describes the spatial relationship of GROUPs.

Note: FRIENDLY, NEUTRAL, STRANGERS, and nonparticipating GROUPs will not be included in the PICTURE or total number of GROUPs identified as part of the tactical picture. If FRIENDLY, NEUTRAL, STRANGERS, or nonparticipating GROUPs are a factor, they are addressed in a separate transmission.

c. Standardized intercept contracts are executed based on the PICTURE.

d. PICTURE Format.
(1) There are four ways to communicate the PICTURE. They are:
(a) Core information. (b) Traditional labels. (c) LEADING EDGE communication. (d) PACKAGES.
(2) Within a PICTURE, each GROUP will have an established name that is retained until:
(a) A NEW PICTURE is called. (b) The GROUP is reduced by attrition. (c) The GROUP is no longer a factor to the operating area.

## 10. Anchoring A Picture

The following are ways anchoring uses the same priorities as PICTURE.

a. Anchoring is prioritized communication of GROUPs.
(1) An anchor is a BULLSEYE used to establish the PICTURE and aid in fighter targeting. (2) GROUPs will be anchored with BULLSEYE if the GROUPs are outside 10 nm in azimuth.

(3) Geographic boundaries and the targeting game plan will dictate the maximum GROUPs that are anchored (e.g., dual-lane defensive counterair with a fighter engagement zone that has a defined azimuth boundary).

b. Force and Mission Anchoring Priority.
(1) Anchoring priorities can shift from the force (e.g., fighters) to the mission. For example, an enemy striker approaches a mission fail line and puts the mission at risk. In this case, the enemy striker may be the anchoring priority. (2) Anchoring priority for risk to mission can take priority over risk to force.

c. When risk to force is a higher priority than risk to the mission, controllers will anchor GROUPs referring to the following priorities:

(1) The threat that is closest to fighters. (2) The most capable threat (based on combat ID, declaration, aircraft type, flight profile). (3) HIGH GROUPs. (4) The largest GROUP STRENGTH.

## 11. Core Information Concerning A Picture

a. Core information concerning a picture is primarily used to:
(1) Pre-COMMIT.
(2) If the PICTURE does not meet a traditional or LEADING EDGE label. (3) If there are three GROUPs or fewer.
b. The PICTURE call will include the total number of GROUPs and is anchored in accordance with anchoring priorities. (See figure 3.)

c. FOUR GROUPs or More.
(1) The call will include the total number of GROUPs. (2) Communicate only the three highest priority GROUPs.

## Four Groups Or More Example

"DARKSTAR, TEN GROUPS. GROUP BULLSEYE 020/25, TWENTY-SEVEN THOUSAND, TRACK EAST, HOSTILE, HEAVY, THREE CONTACTS. GROUP BULLSEYE 270/25, FIFTEEN THOUSAND, TRACK WEST, HOSTILE. GROUP BULLSEYE 290/35, TEN THOUSAND, TRACK WEST, HOSTILE."

## 12. Traditional Labels For A Picture

a. Controllers should use traditional labels and GROUP names with the following criteria:

(1) COMMIT criteria has been met. (2) Threat formation is discernible and labeling a PICTURE will build SA and aid fighter targeting.
(3) If a traditional label does not apply based on the threat presentation,
controllers should use LEADING EDGE communication.
b. The standard labels used are: SINGLE GROUP, RANGE, AZIMUTH, VIC, CHAMPAGNE, WALL, LADDER, and BOX.

Note: FRIENDLY, NEUTRAL, STRANGERS, and nonparticipating GROUPs will not be included in the PICTURE or total number of GROUPs identified as part of the tactical picture. If FRIENDLY, NEUTRAL, STRANGERS, or nonparticipating GROUPs are a factor, they are addressed in a separate transmission.

## 13. Amplifying A Traditional Label For A Picture

a. Amplifying remarks follow the dimensions of the traditional PICTURE. OPENING/CLOSING, TRACK, WEIGHTED, and ECHELON are the most common amplifying remarks.

b. OPENING or CLOSING.
(1) OPENING or CLOSING can be applied when the distance between GROUPs is increasing or decreasing and may impact the fighter intercept. (2) OPENING or CLOSING is placed following the PICTURE label and dimensions but in front of other amplifying remarks, such as ECHELON and TRACK. (See figures 4 and 5.)
c. PICTURE amplification order will be:

(1) Opening/closing. (2) Weighted. (3) Echelon. (4) Track direction.

## Picture Amplification Example

"VENOM, THREE GROUP VIC, 15 DEEP OPENING, 10 WIDE, WEIGHTED NORTH. LEAD GROUP BULLSEYE 270/80, 41K, HOSTILE, HIGH, FAST; NORTH TRAIL GROUP 17K, HOSTILE, TWO CONTACTS, SOUTH TRAIL GROUP 12K, BOGEY SPADES."

d. TRACK.
(1) If all GROUPs in a PICTURE are hot to the fight axis, track direction is assumed, as depicted in figure 6. (2) If all groups share a common track direction other than hot, controller will voice the track direction amplification for the entire picture, as depicted in figure 7. (3) If GROUPS do not share a common track direction, controller will provide track direction fill-ins on each individual group, as depicted in figure 8.

e. WEIGHTED. This is an amplifying remark that describes traditional labels with THREE GROUPs or more.

(1) The PICTURE is WEIGHTED if one or more GROUPs are offset (i.e., the distance between GROUPs are not equidistant).

(a) Divide the azimuth into thirds.
(b) If the out-of-position GROUP is outside the middle third, it is WEIGHTED.
(c) In a WEIGHTED WALL PICTURE, communicate a separation distance
from the highest priority, anchored GROUP to the next closest GROUP.
(d) If the picture is a weighted VIC and the lead group is outside of the trail groups, use weighted if the lead group is 5 nm laterally when measured perpendicular to the threat axis and not opening. Otherwise, consider using a wall label with an echelon component. (e) If the picture is a weighted CHAMPAGNE and the trail group is outside of the lead groups, use weighted if the trail group is 5 nm laterally when measured perpendicular to the threat axis and not opening. Otherwise, consider using a wall label with an echelon component.  (See Figure 9.)
(2) WEIGHTED is accompanied by a cardinal direction relative to the defined threat axis.

## F. Echelon.

(1) ECHELON is used to amplify a traditional label when GROUPs in the traditional label are not directly in AZIMUTH or RANGE with one another. (2) ECHELON should not be used if the depth component between GROUPs is less than or equal to 5 nm. (3) ECHELON is accompanied by a cardinal or sub-cardinal direction and is stated following the PICTURE label and dimensions. The threat axis will determine the direction of the ECHELON.

(a) If the distance between GROUPs is wider than it is deep, the PICTURE is called AZIMUTH. If the separation is deeper than it is wide, the PICTURE is called RANGE. (b) Controllers can create a line 45 degrees from the GROUP closest to the fighters, in the direction of the offset GROUP. (c) If the offset GROUP is forward of the 45-degree line, the PICTURE is an AZIMUTH. If the GROUP is aft of the 45-degree line, the PICTURE is a RANGE. (See figures 10 and 11.)

## 14. Single Group/Two Groups Traditional Label For A Picture

a. The label SINGLE GROUP will only be used when one known BOGEY/BANDIT/HOSTILE group is detected in an operating area. The label is SINGLE GROUP and all information is passed as core information.

## Single Group Example

"CHALICE, SINGLE GROUP BULLSEYE 360/20, TWENTY THOUSAND, TRACK WEST, BOGEY SPADES."

b. TWO GROUPs are labeled AZIMUTH or RANGE.
(1) AZIMUTH. When the distance from the GROUPs relative to the fighters are approximately the same. GROUPs in AZIMUTH are named using cardinal directions. (See figure 12.)
(2) RANGE. If one GROUP is closer to the fighters than the other, RANGE is used as the PICTURE label. GROUPs in RANGE are named LEAD GROUP and TRAIL GROUP. (See figure 13.)

## 15. Three Groups Or More Traditional Picture Labels

a. General. The five traditional PICTURE labels for three or more GROUPs are: WALL, CHAMPAGNE, VIC, BOX, and LADDER. Controllers will use 5 nm of depth to determine the tactical relationship between GROUPs. WALL is the label used if depth is equal to or less than 5 nm or CLOSING inside of 5 nm. CHAMPAGNE or VIC is the label used if the depth is greater than 5 nm or OPENING outside 5 nm.

b. WALL. THREE GROUPs or more separated in AZIMUTH.
(1) WIDE. The term WIDE is used to describe the dimension of a WALL.

(2) THREE GROUPS.
(a) The outer GROUP names are the cardinal direction relative to the defined THREAT axis. For example, EAST GROUP and WEST GROUP.

(b) The inner GROUP is named MIDDLE GROUP. (See figure 14.) (c) In a WEIGHTED WALL PICTURE, a separation distance will be communicated from the priority, anchored GROUP to the next closest GROUP.

(3) FIVE GROUPs or Less.
(a) The outer GROUP names are the cardinal direction relative to the defined THREAT axis. For example, EAST GROUP and WEST GROUP. (b) The inner GROUPs are named MIDDLE GROUPs. (c) A cardinal direction is added to multiple MIDDLE GROUPs so each has a unique GROUP name. For example, NORTH MIDDLE GROUP, MIDDLE GROUP, and SOUTH MIDDLE GROUP. (See figure 15.)

(4) More than FIVE GROUPs.
(a) The fighters and controller should name the outrigger GROUPs based on cardinal relationship (i.e., NORTH, SOUTH, EAST, WEST) and inner GROUPS in numerical sequence (e.g., NORTH GROUP, SECOND GROUP... SEVENTH GROUP, SOUTH GROUP.) (b) The SECOND GROUP will always be closest to the first anchored outrigger GROUP.

c. CHAMPAGNE. This is THREE GROUPs with the two closest GROUPs to the fighters in AZIMUTH and the third GROUP in RANGE.

(1) The term WIDE is used first to describe the AZIMUTH dimension of the CHAMPAGNE. (2) The term DEEP is used second to describe the RANGE dimension of the CHAMPAGNE. (3) The two GROUPs closest to the fighters are named LEAD GROUPs with a cardinal direction descriptor. The GROUP in trail is named the TRAIL GROUP. (See figure 16.)
d. VIC. This is THREE GROUPs with the first GROUP closest in to the fighters and two GROUPs in RANGE of the first GROUP, separated in AZIMUTH.

(1) The term DEEP is used first to describe the RANGE dimension of the VIC. (2) The term WIDE is used, second, to describe the AZIMUTH dimension of the VIC. (3) The GROUP closest to the fighters is named LEAD GROUP. The two GROUPs in RANGE are named the TRAIL GROUPS with a cardinal direction descriptor. (See figure 17.)
e. BOX. A BOX is FOUR GROUPs with two GROUPs closest to fighters separated in AZIMUTH and two GROUPs farthest from fighters also separated in AZIMUTH.

(1) The term WIDE is used first to describe the AZIMUTH dimension of the BOX.

(2) The term DEEP is used second to describe the RANGE dimension of the BOX. (3) The GROUPs closest to the fighters are named LEAD GROUP with a cardinal direction descriptor (i.e., EAST LEAD GROUP and WEST LEAD GROUP).

The GROUPs farthest from the fighters are named TRAIL GROUP with a cardinal direction descriptor. (See figure 18.)
f. LADDER. This is THREE GROUPs or more separated in RANGE from one another.

(1) The term DEEP is used to describe the *total* RANGE dimension of the LADDER. (2) The first GROUP in a LADDER will always be named LEAD GROUP. The last GROUP will always be the TRAIL GROUP. (3) A separation distance will be communicated from the LEAD GROUP to the next GROUP. (4) In a THREE-GROUP LADDER, The GROUP names are LEAD GROUP, MIDDLE GROUP, and TRAIL GROUP. (See figure 19.) (5) When there are more than THREE GROUPs, the GROUP names are LEAD GROUP, SECOND GROUP, THIRD GROUP, TRAIL GROUP.

## 16. A Leading Edge Picture

(1) The leading edge is defined based on which GROUPs the fighters expect to target on an intercept. (2) LEADING-EDGE communication is applied:
(a) When all GROUPs in an operating area do not fit a traditional label.

(b) To minimize the radio transmission when communicating complicated PICTURES. (c) To facilitate rapid targeting of priority GROUPs.

(3) If LEADING EDGE communication is not appropriate, fighters and controllers can relay the PICTURE using core information. (4) The following is the LEADING EDGE communication format.

(a) The controller should communicate the total number of GROUPs prior to communicating LEADING EDGE. (b) A traditional PICTURE label will follow LEADING EDGE. (c) The controller should label the PICTURE based on which GROUPs are expected to be targeted in the upcoming fighter attack (e.g., fighter recommit). For example, avoid a label with a depth component (e.g., VIC or CHAMPAGNE) if the fighters do not intend to target in depth. (d) FOLLOW ON is included at the end of a LEADING EDGE PICTURE call. Controllers should measure the shortest distance, parallel to the threat axis from the LEADING EDGE to the closest FOLLOW ON group. (See figure 20.)

## Figure 20. Leading Edge 17. Package Picture Labeling

a. Define bounding limits in mission planning. Some considerations should include:
(1) If defined by a range, the shortest distance between GROUPs must be greater than the bounding limits to meet PACKAGE criteria.
(2) Bounding limits, which can be determined based on geographic separation. For example, if executing dual-lane, defensive counterair and the controller is
operating in one lane, the controller does not discuss GROUPs in the other lane. (3) Elements operating outside the predetermined bounding range are not considered operating in a common formation.

## Package Example

"GOLIATH, TWO PACKAGES AZIMUTH 60, NORTH PACKAGE BULLSEYE 030/45, SOUTH PACKAGE BULLSEYE 110/55."

b. Within each PACKAGE, there may be a PICTURE that can be labeled.

## Package With A Picture Example

"CHALICE, NORTH PACKAGE, TWO GROUPS RANGE 10, TRACK WEST. LEAD GROUP BULLSEYE 045/35, TWENTY-FIVE THOUSAND, HOSTILE, TWO CONTACTS. TRAIL GROUP FIFTEEN THOUSAND, HOSTILE, TWO CONTACTS." c. The GROUP name and PACKAGE name are used when referring to GROUPs, if multiple PACKAGES are being TARGETED.

## Package Target Example

"VIPER 2, TARGET LEAD GROUP NORTH PACKAGE." d. If bounding limits are defined by a known geographic boundary, controllers may use geographic references to describe the relationship between PACKAGES.

## Lane With Truncated Picture Example

"GOLIATH, NORTH LANE THREE GROUP CHAMPAGNE."

## 18. New Picture

a. Controllers should maintain original labels unless a new label and names will fix or better facilitate targeting. If time compressed when combining a range call and a picture, controllers will truncate fill-ins and respond comparatively after targeting calls. b. Controllers should not make a NEW PICTURE call inside the targeting range. c. If fighters request a PICTURE inside the targeting range (e.g., fighters clear a merge) controllers should use PICTURE labeling criteria unless the nearest GROUP meets THREAT criteria. d. Fighters executing COLD operations will request a PICTURE. e. The term NEW PICTURE will be used when fighters are HOT.

## 19. Additional, Pop-Up, And Threat Groups

a. ADDITIONAL GROUP.
(1) ADDITIONAL GROUP is applied to a GROUP that is newly detected outside the targeting range or does not fit a traditional label. (2) An ADDITIONAL GROUP is anchored using BULLSEYE in accordance with the defined anchoring priorities.

## Additional Group Example

Controller: "MISER, TWO GROUPS AZIMUTH 20. NORTH GROUP BULLSEYE 360/20, THIRTY-TWO THOUSAND, TRACK WEST, HOSTILE. SOUTH GROUP AT BULLSEYE, EIGHT THOUSAND, TRACK EAST, HOSTILE." Fighter: "EAGLE 1, ADDITIONAL GROUP BULLSEYE 090/7, FIVE THOUSAND, TRACK WEST, HOSTILE FLANKER."
(3) If an ADDITIONAL GROUP is part of the LEADING EDGE and the fighters are outside the targeting range, the controller should re-label it as a NEW PICTURE and include the ADDITIONAL GROUP as part of the NEW PICTURE. (4) If there are multiple ADDITIONAL GROUPs, each ADDITIONAL GROUP is prefaced with a cardinal direction and/or number (e.g. NORTH ADDITIONAL GROUP, FIRST ADDITIONAL GROUP).

b. POP-UP GROUP.
(1) If a previously undetected or unreported GROUP appears inside the targeting range and outside the THREAT range, it is named a POP-UP GROUP. (2) A POP-UP GROUP is anchored using BULLSEYE in accordance with the defined anchoring priorities. (3) If there are multiple POP-UP GROUPs, each POP-UP GROUP is prefaced with a cardinal direction and/or number (e.g., WEST POP-UP GROUP, FIRST POP-UP GROUP).

## Pop-Up Group Example

Controller: "DARKSTAR, FIRST POP-UP GROUP BULLSEYE 270/15, FIVE THOUSAND, TRACK WEST, BOGEY SPADES. SECOND POP-UP GROUP BULLSEYE 300/20, TEN THOUSAND, TRACK NORTHWEST, BOGEY SPADES."

c. THREAT GROUP.
(1) If an undetected or unreported GROUP meets briefed THREAT criteria, it is named a THREAT GROUP. Controllers should use the BRAA format when issuing a THREAT call to the closest aircraft.

## Threat Group Example

Controller: "RAMBO 2, THREAT GROUP BRAA 270/13, ONE THOUSAND, HOT, HOSTILE."
(2) If there are multiple THREAT GROUPS, each THREAT GROUP is prefaced with a cardinal direction and/or number (e.g., EAST THREAT GROUP, FIRST
THREAT GROUP).

## Chapter V Air-To-Air Intercept Communication 1. Overview

This chapter establishes a communication format for A/A employment and air intercept control. It governs communication fundamentals, format, and integration between fighters and controllers, independent of MDS or T/M/S. This chapter is the baseline for all A/A communication in training and combat. Service-specific differences are annotated. Refer to the following weapons schools for Service-specific tactics and employment considerations:
a. United States Army Aviation Center of Excellence (USAACE), Fort Rucker, Alabama. b. Marine Aviation Weapons and Tactics Squadron One (MAWTS-1), Marine Corps Air Station, Yuma, Arizona. c. Naval Aviation Warfighting Development Center (NAWDC) N7 (Topgun), Fallon Naval Air Station, Nevada. d. United States Air Force Weapons School (USAFWS), Nellis Air Force Base, Nevada.

Note: For the purpose of this publication, controller is a general term used to define the individual providing tactical control of an intercept or mission. The term fighter is the example used throughout this chapter but this information applies to any aircraft capable of employing A/A ordnance. Controller and fighter are used independent of platform or Service.

## 2. Communication Cadence By Intercept Phase

a. The A/A communication cadence establishes the flow of information during different phases of a mission. It ensures fighters receive priority information transmitted by the controller.

(1) Communication priorities shift between controllers and fighters during different phases of an intercept. (2) Priorities shift based on what asset has the most SA to communicate timesensitive information.
b. Table 7 outlines the A/A intercept phases and the communication priorities.

| Phase                    | Priority Communicators       |
|--------------------------|------------------------------|
| 1. Pre-COMMIT or MARSHAL | 1. Controller.               |
| 2. Fighters.             |                              |
| 2. Post-COMMIT or PUSH   | 1. Fighters.                 |
| 2. Controller.           |                              |
| 3. Merge                 | 1. Engaged Fighter.          |
| 2. Supporting Fighters.  |                              |
| 3. Controller.           |                              |
| 4. Postmerge             | 1. Fighter Clearing a Merge. |
| 2. Supporting Fighters.  |                              |
| 3. Controller.           |                              |

## 3. Commit/Target Beyond Visual Range (Bvr)

a. COMMIT Criteria.
(1) During mission planning, COMMIT criteria is determined based on the overall mission objective. (2) COMMIT criteria considerations are:
(a) Range based (e.g., predetermined range from fighters or a defended asset). (b) Location based (e.g., enemy assets affecting a strike route). (c) Threat based (e.g., only COMMIT against certain aircraft types). (d) Weapon employment based (e.g., allow fighters to employ at their first available employment range).

b. COMMIT Authority.
(1) COMMIT authority is derived from the combatant commander and can be delegated to the MC, PC, or controller based on the theater SPINS/OPTASK messages. (2) If COMMIT authority is granted to the MC, PC, or controller it ensures fighters remain on the timeline against THREATS. (3) If only the MC, PC, or controller (if delegated) retain the COMMIT authority:
(a) The MC or PC and/or controller will COMMIT once COMMIT criteria has been achieved. (b) Controllers can recommend the COMMIT.

## Controller Commit Example

Controller: "TANGO, TEN GROUPS, GROUP ROCK 250/45, THIRTY-FIVE THOUSAND, TRACK EAST, HOSTILE, RECOMMEND RAPTOR COMMIT." Fighter: "RAPTOR COMMIT."
(4) If only the controller retains COMMIT authority:
(a) The controller should direct the COMMIT once COMMIT criteria has been met.

(b) The MC or PC may only recommend COMMIT.

## Recommend Commit Example

Fighter: "RAPTOR 1, RECOMMEND COMMIT." Controller: "TANGO, TEN GROUPS, GROUP ROCK 250/45, THIRTY-FIVE THOUSAND, TRACK EAST, HOSTILE, RAPTOR COMMIT." Fighter: "RAPTOR 1."
(5) Two-way communication between the fighters and controller is required when a COMMIT is recommended or directed. (6) If a COMMIT is directed by the fighter, the controller will transition from pre- COMMIT communication standards to tactical control and traditional label or LEADING EDGE PICTURE communication.

## Fighter Commit Example

Fighter: "RAPTOR COMMIT." Controller: "TANGO, TEN GROUPS, LEADING EDGE TWO GROUPS AZIMUTH 40, TRACK EAST. NORTH GROUP ROCK 300/15, THIRTY-FIVE THOUSAND, HOSTILE. SOUTH GROUP ROCK 230/20, THIRTY-FIVE THOUSAND HOSTILE. FOLLOW-ON GROUP 25."

## 4. Tactical (Tac) Range Call

a. Fighters should prebrief the "TAC range" call with controllers. b. A 45-nm separation from the closest fighter to the closest GROUP is a default.
c. The first to recognize the appropriate separation will make the "TAC range" call using the closest fighter call sign and the closest GROUP name.

## Tac Range Example

"SHOWTIME 11, NORTH GROUP FORTY-FIVE MILES."

## 5. Targeted

a. Fighters will communicate targeting using the minimum words required while enabling C2 to verify targeting. For example, with datalink between fighters and C2, the only communications required may be TARGETED and the group label. Without datalink, the targeted call must include location information, preferably BULLSEYE.

Without C2, fighters should use minimum communications while enabling the flight lead to verify targeting.

## Targeted Communications Examples

Datalink enabled to C2: "RAMBO 2, TARGETED WEST GROUP." Datalink not enabled to C2: "SATAN 2 TARGETED WEST GROUP BULLSEYE 270/15." b. Fighters may include more information if they desire to update or re-emphasize information provided by C2 (e.g., more contacts detected, altitude changes, expected changes to flow or targeting that the flight lead has not yet communicated). If including more information, fighters will use the format described in core information format.

## Core Information Format Example

"RAMBO 2, TARGETED WEST GROUP BULLSEYE 270/15, TWENTY THOUSAND, HOT, HOSTILE, STRENGTH TWO." c. Fighters may combine targeting with shot communication by voicing "FOX" (with a sort, as appropriate) after "TARGETED."

## Targeting Examples

"RAMBO 2, TARGETED, FOX 3 TWO-SHIP WEST GROUP BULLSEYE 270/15, TWENTY THOUSAND." RAMBO 2, TARGETED, FOX 3 SORTED EASTERN, WEST GROUP BULLSEYE 270/15, TWENTY THOUSAND, STRENGTH THREE d. C2 contracts for the UNTARGETED fill-in and THREAT calls are canceled if a fighter calls "TARGETED" on their targeting responsibility with:

(1) A correlated bullseye; or, (2) A GROUP name and a J12.6 with lock/shot-line that is correlated to or
displayed within 3nm of the surveillance track. Shots against GROUPS other than the primary targeting responsibility with no "TARGETED" call do not cancel C2 contracts.

## 6. Declare

a. A DECLARE call is an interrogative call (i.e., request for information) made by either the fighters or controller.

b. Use the following communication format.
(1) Call sign of asset maintaining custody to the GROUP.
(2) The requesting asset's call sign. (3) "DECLARE BULLSEYE." (4) Position of the group in the BULLSEYE format. (5) Altitude. (6) Track direction (only required to discriminate).

## Declare Request Example 1

"DARKSTAR, VIPER 1, DECLARE BULLSEYE 230/12, TWELVE THOUSAND." c. When a declaration request is made after the tactical picture has been labeled, the GROUP name can be used instead of the BULLSEYE location.

## Declare Request Example 2

"CHALICE, HORNET 1, DECLARE EAST GROUP."

d. DECLARE Response.
(1) Controllers will always respond to a DECLARE request with BULLSEYE, altitude, track direction, declaration, and fill-ins.

(2) DECLARE responses may include: BOGEY, FRIENDLY, NEUTRAL, BANDIT, HOSTILE, FURBALL, UNABLE, or CLEAN (VANISHED can be used in training).

## Declare Response Example

"CHALICE, EAST GROUP BULLSEYE 273/27, TWENTY-TWO THOUSAND, TRACK EAST, BOGEY SPADES."

## 7. Hostile Declaration During Shot Communication

a. If a fighter determines a GROUP HOSTILE, and ROE has been met, the fighter may employ weapons against that GROUP. b. Fighters should communicate GROUP BULLSEYE, altitude, and HOSTILE in the shot transmission so other fighters and the controller can correlate to each other.

c. Track direction is included only if it enhances SA.

## Track Direction Example

"RAPTOR 1, FOX 3 LEAD GROUP BULLSEYE 125/27, TWENTY-NINE THOUSAND, TRACK NORTH, HOSTILE." d. Controllers can upgrade GROUPs declared BOGEY or BANDIT to HOSTILE without correlating to BULLSEYE if a correlated J12.6 and shot line are displayed within 3 nm of a surveillance track. A voice correlation with a J12.6 and shot line are not mandatory for a controller declaration upgrade to HOSTILE. e. QC TARGETING. Controllers will respond to targeting calls with comparative communication, updating core information and fill-ins. If all information provided by the fighter correlates to information available to the controller, no response is provided.

Note: Not all controller platforms can correlate a J12.6 and shot line. Query the controlling platform during mission planning to evaluate this contract.

## 8. Clean

a. If a fighter calls CLEAN on their targeting responsibility, controllers will provide a full positional update or respond with CLEAN, FADED, or VANISHED.

## Clean Example

"MIKE, SHOWTIME 11 CLEAN NORTH GROUP." "MIKE, NORTH GROUP BULLSEYE 290/35, THIRTY-EIGHT THOUSAND, TRACK EAST, HOSTILE." b. If fighters are CLEAN to a GROUP and desire a GROUP location relative to ownship, they should request a BRAA/BOGEY DOPE to the GROUP.

## Braa Request Example

"MIKE, SHOWTIME 11 BRAA NORTH GROUP." "SHOWTIME 11, NORTH GROUP BRAA 210/28, THIRTY-EIGHT THOUSAND, HOT, HOSTILE."

## Bogey Dope Request Example

"MIKE, SHOWTIME 11 BOGEY DOPE NORTH GROUP." "SHOWTIME 11, NORTH GROUP BRAA 210/28, THIRTY-EIGHT THOUSAND, HOT, HOSTILE."

## 9. Shoot

This is directive communication by fighters for missile employment against a specific GROUP or CONTACT when fighters are targeting another GROUP. This does not imply BANZAI flow to the GROUP or CONTACT.

## Shoot Example

Fighter: "BOLT 4, SHOOT SOUTHERN SOUTH LEAD GROUP."

## 10. Group Maneuvers

a. Controllers and fighters are responsible to communicate GROUP maneuvers. The three components to each maneuver are:

(1) Recognizing the maneuver. (2) Communicating the relationship of the maneuver. (3) Updating GROUP names to aid in fighter targeting, as well as group altitude to include fighter targeting, stacks, change in +/- 5K feet, or a change in fighter sanitization areas.
b. GROUPs maneuver into ARMs. ARMs maneuver into CONTACTs.
(1) Once a maneuver is recognized, it is communicated using the term MANEUVER. (2) If a maneuver direction can be determined, the controller or fighter will update the maneuver using: own CALL SIGN, GROUP name, and type of maneuver (e.g., BEAM NORTH or DRAG EAST).

## Group Maneuver Example 1

"DARKSTAR, LEAD GROUP BEAM NORTH."
(3) If a specific aspect is not applicable to all fighters, controllers and fighters should use the TRACK DIRECTION to describe the maneuver.

## Group Maneuver Example 2

"DARKSTAR, LEAD GROUP TRACK NORTH."
Note: Maneuvers can drive a NEW PICTURE if it is outside targeting range or during COLD operations.

## C. Azimuth And Range Maneuvers.

(1) The terms MANEUVER AZIMUTH or MANEUVER RANGE are used if a GROUP maneuvers outside GROUP criteria. (See figures 2122.)
(2) Communicate "MANEUVER RANGE AND AZIMUTH" if three or more CONTACTs maneuver in range and azimuth simultaneously while at least one CONTACT(S) remains FLANK/HOT. (See figure 23.) (3) Communicate, "MANEUVER AZIMUTH AND RANGE", if three or more CONTACTs maneuver in azimuth and range, simultaneously, while the CONTACT(S) BEAM/DRAG with no contacts remaining FLANK/HOT. (See figure 24.)
(4) As a technique, if a GROUP with three or more CONTACTs maneuvers to a traditional label (e.g., VIC, WALL, or CHAMPAGNE), controllers may communicate a NEW PICTURE to simplify targeting.

d. The following concerns changing GROUP names relative to targeting range.
(1) Fighter timelines will vary based on MDS and T/M/S and threat capabilities. Prior to any mission, controllers and fighters should ensure they are referring to the same timeline. If controllers and fighters are not able to brief each other, the
following concepts and timeline considerations are used as defaults.
(a) Targeting Range. Targeting range refers to the first time targeting is issued for any fighter in the element or the term TARGETED is communicated on the control NET. (b) Outside Targeting Range. If maneuvers occur outside the targeting range, controllers may issue a NEW PICTURE. (c) Inside Targeting Range. If maneuvers occur inside the targeting range, controllers can choose to:

- Update each CONTACT with a new name. - Use UNTARGETED for the highest factor GROUP, ARM, or CONTACT
not being TARGETED.
- Issue targeting per the fighters' targeting game plan.
(d) If multiple GROUPs maneuver outside GROUP criteria, fighters and controllers should use the new name (e.g., ARM or CONTACT) and the previous GROUP name (e.g., LEAD GROUP or NORTH GROUP).

## Arm Examples

Multiple NORTH ARMS: "DARKSTAR, NORTH ARM LEAD GROUP TRACK NORTH." Single NORTH ARM: "DARKSTAR, NORTH ARM TRACK NORTH." e. When GROUPs maneuver and their positional relationships affect targeting or flow, use PASSING, CROSSING, or JOINED.

(1) PASSING. PASSING is two or more named GROUPs with a RANGE
relationship maneuver to opposite sides in a RANGE relationship. It is an informative call using the GROUP names from the original PICTURE. (See figure
25.)
(2) CROSSING. Crossing is two GROUPs with an AZIMUTH relationship maneuver to opposite sides in an AZIMUTH relationship. CROSSING is an informative call using the GROUP names from the original PICTURE. (See figure 26.) (3) JOINED. JOINED occurs when two or more named GROUPs maneuver to meet and maintain GROUP criteria.  The new GROUP label should make sense based on the tactical situation (e.g., based on the new targeting plan). (See figure
27.)

## 11. Bogey Dope

a. BOGEY DOPE is a request for information on an indicated GROUP or closest GROUP (if not indicated) to build/enhance fighter SA. b. Controllers will respond using the BRAA format and add appropriate fill-ins.

## Bogey Dope Example

"WARRIOR, EAGLE 1 BOGEY DOPE." "EAGLE 1, FIRST ADDITIONAL GROUP BRAA 120/38, THIRTY-FIVE THOUSAND, HOT, HOSTILE." c. BOGEY DOPE does not imply fighter targeting.

## 12. Electromagnetic Attack

a. STROBE. Controllers will respond to STROBE calls with range, altitude, aspect (HOT assumed), declaration, and GROUP name (if applicable) to the closest GROUP along that line of bearing.

## Strobe Example

Fighter: "RAMBO 1, STROBE 3-6-0" or "RAMBO 1, STROBE LEAD GROUP." Controller: "RAMBO 1, STROBE RANGE 37, TWENTY-FIVE THOUSAND, HOT, HOSTILE, LEAD GROUP."

b. MUSIC.
(1) MUSIC is an informative call that fighters are experiencing radar electromagnetic deceptive jamming from a GROUP. (2) Controllers will respond to MUSIC calls by anchoring the GROUP off BULLSEYE and providing the altitude, track direction, declaration, and fill-ins.

## Music Example

Fighter: "HEAT 1, MUSIC EAST GROUP." Controller: "BARNYARD, EAST GROUP, BULLSEYE 210/15, TWENTY-FIVE THOUSAND, TRACK EAST, HOSTILE, 2 CONTACTS LINE ABREAST THREE."
Note: If controllers cannot correlate STROBE +/- 30 degrees to a GROUP, they should respond with CLEAN. This indicates the contact may be below the controller sensor coverage or may be a ground-based jammer.

c. METALLICA.
(1) This is an informative call to communicate electromagnetic attack (EA) is preventing fighter employment on a specific GROUP. (2) Controllers are not required to respond to METALLICA. (3) METALLICA does not alleviate fighter targeting responsibility for a GROUP.

## Metallica Example

Fighter: "PYTHON 2, METALLICA LEAD GROUP."

## 13. Spike

a. Fighters call SPIKED with a bearing or cardinal/sub-cardinal direction.
(1) The controller should correlate the SPIKE 30 degrees of the bearing to a detected GROUP. (2) Respond with the range, altitude, aspect (HOT assumed), declaration, GROUP name (if applicable), and fill-ins.

## Spiked Example 1

Fighter: "EAGLE 1, SPIKED 2-7-0." Controller: "EAGLE 1, SPIKE RANGE 17, THIRTY THOUSAND, HOT, HOSTILE EAST GROUP, TWO CONTACTS." b. If a controller cannot correlate a GROUP along the aircraft's spike bearing or cardinal direction, controllers will respond with CLEAN and the bearing of the SPIKE.

## Spiked Example 2

Fighter: "EAGLE 1, SPIKED 2-7-0." Controller: "EAGLE 1, WARRIOR CLEAN 2-7-0."

## 14. Jackal

a. JACKAL is not a substitute for fighters gaining sensor SA, but it does provide fighters an understanding of where all GROUPs are located. b. JACKAL allows fighters to loosen initial correlation and can alleviate the controller from having to anchor each GROUP on an intercept. c. If directive targeting is not to be issued by the controller, fighters can brief for the controller to only anchor one GROUP (e.g., NORTH GROUP of a THREE GROUP WALL). d. The separation and fill-ins provided by the controller will allow fighters to correlate the exact location of each GROUP even when they do not have sensor SA.

e. During all PICTURE calls, the controller should anchor all GROUPs to be targeted via BULLSEYE, unless otherwise briefed.

## 15. Engage/Merge Phase

a. Controllers should refer to fighters as MERGED when the resolution capabilities of the controller systems become limiting factors or when fighters are within 35 nm of a GROUP.

b. Controllers should talk to a MERGED fighter for:
(1) Fighter requests. (2) THREAT calls. (3) TRESPASS calls. (4) STRENGTH disparity (e.g., comparative communication). (5) Update fighter flow direction to follow on GROUPs (if required).
c. Controllers should refer MERGE phase if a fighter calls ANCHORED (GROUP name) or STANDBY (GROUP name). d. ANCHORED or STANDBY calls should include the BULLSEYE location, if the GROUP does not have a name.

## Anchored Example

Fighter: "RAPTOR 1, STANDBY SOUTH GROUP" or "RAPTOR 1, ANCHORED BULLSEYE 170/50."

## E. Separation.

(1) SEPARATION is a fighter request or C2 enhancing call to provide the distance (nm) between two GROUPs.

(a) It is used when a fighter is ANCHORED.

(b) SEPARATION request implies it is from the current ANCHORED GROUP to the requested GROUP, if not specified.
(2) In the SEPARATION response, controllers should use their call sign followed by the follow-on GROUP's SEPARATION, altitude, and fill-ins.

(3) Controllers may use RANGE SEPARATION or AZIMUTH SEPARATION, if the tactical relationship between GROUPs changed and the controller did not have the ability to make a NEW PICTURE call.

## 16. Cold Operations

a. Fighters should communicate COLD operations with either "FLOW COLD" or FLOW with a COLD heading.

## Flow Example

"SHOWTIME, FLOW COLD." or "SHOWTIME, FLOW 0-9-0." b. Communication priorities are as follows:

(1) SPIKES or THREATS within a stern weapon engagement zone (WEZ).
(2) FADED or POP-UP GROUPs inside of Launch and Decide targeting depth. (3) DELOUSE or directive targeting. (4) PICTURE. (5) Fighter targeting game plan.

## 17. Grind Operations

a. Applies when elements are executing an "OUT" and subsequent "IN"; all communications will comply with the briefed priorities and occur on the primary frequency. b. Continue to update the picture during the GRIND, while meeting the priorities listed below:

(1) Controllers should maintain the original labels unless a new label and names will fix or better facilitate targeting.
(2) If time compressed when combining a range call and a picture, controllers will truncate fill-ins and respond comparatively after targeting calls.

(3) Communication priorities are as follows:

(a) Threats within a stern (WEZ) to the "out" element or any spike responses.
(b) PICTURE or BOGEY DOPE to the "IN" element.
(c) Assist in gaining mutual support (as required).

## 18. Threat Call

a. If a fighter will pierce the THREAT range to an UNTARGETED GROUP, a THREAT call is made using the GROUP name, bearing or cardinal/sub-cardinal direction, range, altitude, and aspect, followed by declaration and fill-ins.

b. The THREAT call is completed no later than threat range.
c. THREAT criteria is defined during mission planning and relayed during the brief or check in with the controller.

(1) Controllers should use 35 nm, independent of aspect, as a default THREAT criteria.

## Threat Example

Controller: "HEAT 31, ADDITIONAL GROUP THREAT BRAA 125/35, THIRTY- FIVE THOUSAND, HOT, HOSTILE."
(2) If the exact fighter location is not known, or the THREAT pertains to multiple fighters, THREAT information may be provided using BULLSEYE.

(a) BULLSEYE will immediately follow the word THREAT. (b) If a fighter receives a THREAT BULLSEYE call, the fighter should respond with own call sign.

Note: When communicating with United States Army or United States Marine Corps rotary-wing aircraft and UASs, pass surface threat information in MGRS. Attempt to provide at least a six-digit grid.

## Threat With Bullseye Example

Controller: "COBRA 1, CHALICE, NORTH GROUP THREAT BULLSEYE 295/26, TWENTY THOUSAND, TRACK WEST, HOSTILE."
(3) When a THREAT is within 5 nm of FRIENDLY fighters, controllers may provide THREAT information using the cardinal direction, range, altitude, track direction, and declaration.

Controller: "BOLT 1, THREAT NORTH THREE, TEN THOUSAND, TRACK SOUTH, HOSTILE."
(4) If a fighter calls TARGETED or acknowledges directive targeting, contracts for UNTARGETED and THREAT calls are cancelled.

d. Cross-court THREAT.
(1) A cross-court THREAT is a GROUP that is TARGETED by one fighter, but meets THREAT criteria to another. (2) For example, when operating outside a visual formation, the controller may give a THREAT call to a GROUP that is TARGETED by another fighter within the element.

(a) Fighters may use the term HEADS UP to other flights or elements when TARGETED GROUPs maneuver and appear to meet THREAT criteria to the other flight or element. (b) Controllers may add TARGETED BY as fill-in information in the THREAT
call, if applicable. (See figure 28.)

e. Stern WEZ threat.
(1) During cold ops, grinder ops, or situations of detached mutual support when a friendly element indicates a COLD flow (via EXIT, OUT, ABORT, COLD, or FLOW) in relation to the adversary, the controller will use the following rule of thumb due to TAC C2 limitations in obtaining radar altitude measurements:

(a) Short radar threat7 nm. (b) Long radar threat13 nm. (c) Active-radar threat14 nm.

## 19. Faded Or Vanished A. Faded.

(1) If a previously tracked GROUP is not updated by on- or off-board sensors for
30 seconds, a controller will report the GROUP as FADED. (See figure 29.)
(2) If a status of the FADED group/contact is requested or if a "PICTURE/NEW PICTURE" call is made within 1 minute of the fade, controllers will reference the last known BULLSEYE position with number of contacts.  If the contact was continuously tracked by a fighter after the controller lost contact on the group, the last fighter location will be used in the "FADED...LAST KNOWN" call. Otherwise, controllers will respond with "CLEAN" and "[number of] contacts FADED."

## Picture Within 1 Minute Of Fade Example

"VENOM, TWO GROUP AZIMUTH 8, NORTH GROUP BULLSEYE 270/30, TWENTY-THREE THOUSAND, HOSTILE, SOUTH GROUP TEN THOUSAND, HOSTILE...SINGLE CONTACT FADED BULLSEYE 280/45, TRACK EAST, BEAR."

## Picture Last Known Location Example

"VENOM, TWO GROUP AZIMUTH 8, NORTH GROUP BULLSEYE 270/30, TWENTY-THREE THOUSAND, HOSTILE, SOUTH GROUP TEN THOUSAND, HOSTILE...SINGLE CONTACT FADED **LAST KNOWN** BULLSEYE 280/45, TRACK EAST, BEAR."

## Picture Single Contact Fade From Multiple Contact Group

"VENOM, NORTH GROUP NOW SINGLE CONTACT ONLY.  ONE CONTACT FADED BULLSEYE 270/30, TRACK EAST."
(3) In response to a picture request, controllers will report "1," "2" or "multiple" contacts FADED, as appropriate.

Fighter: "BARNYARD, PYTHON 1, PICTURE" (requested more than 1 min after fade). Controller: "BARNYARD, SINGLE GROUP AT BULLSEYE, THIRTY THOUSAND, HOSTILE, BARNYARD TWO CONTACTS FADED."
Note: Controllers should not anchor a group previously FADED if the elapsed time from when the group FADED exceeds 1 minute due to system limitations and degradations in sensor SA.

(4) Fighters will maintain MONITOR responsibility for the GROUP that has been voiced "FADED" by controllers, if the fighters can maintain correlation.
Note: FADED will not be used to describe FRIENDLY aircraft. Controllers will use NEGATIVE CONTACT to report a lack of sensor data on FRIENDLY aircraft.

## Negative Contact Example

Controller: "EAGLE 1, DARKSTAR, NEGATIVE CONTACT." b. VANISHED.

(1) VANISHED is a special case of FADED. If a previously tracked GROUP is not updated by on- or off-board sensors, a controller will report the GROUP as VANISHED, if it meets the following criteria.

(a) It is not in a known blind zone (terrain masking or Doppler blind zone). (b) It is correlated to a shot, by FRIENDLY forces, that meet parameters for successful termination. (See figure 30.)
Note: In training, when GROUPs are called DEAD by a range training officer (RTO) or a GROUP acknowledges a KILL call/KILL removes, controllers will use VANISHED in response to DECLARE/STATUS requests and updated PICTURES, to prevent erroneous targeting. The RTO should respond to requests on dead aircraft with DEADMAN. If a GROUP has alive and dead CONTACTs, update the number of CONTACTs in the GROUP counting only those that are alive.

## 20. Snaplock

If fighters gain sensor SA to a group inside the THREAT range with BEAM or hotter aspect, fighters should make a SNAPLOCK call.

a. During the SNAPLOCK call, BRAA and aspect are implied due to the reduced timeline to identify and attrite the threat. b. The controller should respond to a SNAPLOCK call with the GROUP name, BRAA, declaration, and fill-ins.

c. If the GROUP was not previously detected, it is named THREAT GROUP.

## Snaplock Example

"FREEDOM 31, SNAPLOCK 125/10, EIGHT THOUSAND." "FREEDOM 31, THREAT GROUP BRAA 125/10, EIGHT THOUSAND, HOT, HOSTILE, TWO CONTACTS."

## 21. Leaker

a. A LEAKER is an airborne threat that has passed through a defensive layer. b. LEAKER can be communicated by fighters or controllers. c. The entity making the LEAKER call should use own call sign.

## Leaker Example Viper 1: "Viper 1, Leaker Bullseye 305/65, Five Thousand, Track South, Hostile Two Contacts." 22. Lane Crossers And Lane Riders

a. A LANE CROSSER is a GROUP that crosses into different areas of targeting responsibility. b. A LANE RIDER is a GROUP that maintains a track direction on or near the line that divides different areas of targeting responsibility. c. During mission planning, fighters and controllers should identify whether a LANE CROSSER/LANE RIDER is TARGETED via integrated fires or, organically, by the fighters in the lane.

(1) There is increased communication required between the controllers of both targeting lanes to facilitate fighter targeting or integrated fires. (2) The controller should use the fill-ins LANE CROSSER/LANE RIDER and TARGETED BY to describe who is targeting the GROUP.

(3) TARGETED BY fill-ins can be added during the PICTURE call or as a descriptive update.

## Lane Rider Example

Example 1, Controller (as a descriptive update): "BLACKOUT, NORTH GROUP LANE RIDER TARGETED BY HORNET." Example 2, Controller: "BLACKOUT, NORTH GROUP LANE RIDER TARGETED BY NORTH LANE."
(4) Fighters in the lanes can direct targeting a LANE CROSSER/LANE RIDER or the controller or fighters can delegate this targeting authority to the controller. (5) When operating in a dual lane construct, the controller should incorporate LANE CROSSERS and LANE RIDERS in the PICTURE call. (See figure 31.) (6) Controllers in the adjacent lanes may include the same GROUP into their PICTURE call. Controllers are responsible to coordinate targeting to avoid double targeting.

This page intentionally left blank.

## Chapter Vi Air-To-Surface Communication 1. Overview

This chapter establishes a communication format for air-to-surface (A/S) employment. It governs communication fundamentals, format, and integration between aircraft and controllers, independent of MDS or T/M/S. For interflight communication, refer to the appropriate MDS- or T/M/S-specific manual. Refer to the following weapons schools for Service-specific tactics and employment considerations:
a. United States Army Aviation Center of Excellence (USAACE), Fort Rucker, Alabama. b. Marine Aviation Weapons and Tactics Squadron One (MAWTS-1), Marine Corps Air Station, Yuma, Arizona. c. Naval Aviation Warfighting Development Center (NAWDC) N7 (Topgun), Fallon Naval Air Station, Nevada. d. United States Air Force Weapons School (USAFWS), Nellis Air Force Base, Nevada.

Note: For the purpose of this publication, controller is a general term used to define the individual providing tactical control of an intercept or mission. The term aircraft is a general term for air assets executing an A/S mission. Controller and aircraft are used independent of platform or Service.

## 2. Air-To-Surface (A/S) Tasking Serialization

A/S taskings are passed from controllers to aircraft. During a high operation tempo, multiple A/S taskings may be passed. Therefore, it is advantageous to use serialization. Serialization is a system for assigning unique codes to simplify communication. It can use letters, numbers, or symbols to identify a large set of information. Serialization is applied to each task in the order of creation and does not imply priority or confidence.

a. Plan for the mission to include the A/S tasking serialization technique. b. The labeling convention should use the ATO day and two-digit numeric sequencing. For example:
(1) AA01 is the first task of ATO day AA. (2) This designator should precede the tasking message. (3) Digital messages should end with "EOM" meaning "end of message". This indicates receipt of all digital message data (e.g., "[aircraft call sign] AA01 [tasking message text] EOM").

## 3. Air-To-Surface (A/S) Tasking Format

A/S taskings can be passed as full or partial digital or voice.

a. Taskings should pass the minimum information required to safely and efficiently accomplish the mission.

b. Taskings should include the following information, when applicable.
(1) Call sign of the asset being tasked. (2) Task type (e.g., TARGET, INVESTIGATE, or SMACK). (3) Link 16 track number and target description.
(4) Desired point of impact (DPI) in the requested format or formatted in
accordance with the SPINS (e.g., MGRS or latitude (DDMM.MMM), longitude (DDDMM.MMM), elevation (feet)).
(5) Target location error (TLE) or categories (CATs) 16. This segment may be repeated for targets with more than one DPI. (6) Quantity (Q), number (N), and application [per (P) or total (T)] for each DPI. Per (P) is used with multiple DPI target sets and total (T) is used if only one DPI
is shown. (7) Remarks. These can include mission priority, additional target description for INVESTIGATE or TARGET tasks, and coordinating data for other missions assigned to the package.

## 4. Full Digital Taskings (J28.2 And J12.0 Tasking Against J3.X Track)

a. If a response is desired, controllers should start the tasking process by communicating CHECK DATA.

b. J28.2 is the assumed data source unless the controller specifies another.

## Full Digital Tasking Example

Controller: "BONE 1, STRIKESTAR, CHECK DATA, ALPHA ALPHA 0-1." J28.2 message: BE01//AA01//TGT//160/10//JS010//TANKS//CAT4//EOM Aircraft: "STRIKESTAR, BONE 1, GOOD DATA, ALPHA ALPHA 0-1." Controller: "BONE 1, COMEBACK WITH ETA, TOT, AND BDA." c. Controllers should use all available J-series messages, even if the tasked asset is TIMBER SOUR or not Link 16 capable. This serves to increase force package SA on the operating area taskings.

## 5. Full Voice Taskings Full Voice Tasking Example

Controller: "HORNET 1, SABRE, TASK ALPHA ALPHA 0-1. TARGET BULLSEYE 160/10, TRACK NUMBER JS010. CALL READY DETAILS." Aircraft: "HORNET 1, READY DETAILS ALPHA ALPHA 0-1." Controller: "HORNET 1, 548 FEET, THREE VEHICLE CONVOY EASTBOUND, NORTH 3-7-3-4 DECIMAL 1-5, WEST 1-1-6-1-0 DECIMAL 1-2, 548 FEET, CAT IV, CALL READY REMARKS." Aircraft: "HORNET 1, COPIES 548 FEET, THREE VEHICLE CONVOY EASTBOUND, NORTH 3-7-3-4 DECIMAL 1-5, WEST 1-1-6-1-0 DECIMAL 1-2, 548 FEET, CAT IV READY REMARKS." Controller: "HORNET 1, READBACK CORRECT. CONFIRMED ENEMY TANKS IN THE OPEN. COME BACK WITH ETA, TOT, AND BDA."

## 6. Partial Digital Taskings (Voice And J12.0 Tasking Against J3.X Track)

a. For taskings with a J3.3 or J3.5 message only, use a modified voice format.

## Partial Digital Tasking Example

Controller: "HOSS 1, SABRE, TASK ALPHA ALPHA 0-1. TARGET BULLSEYE 160/10, TRACK NUMBER JS010, CAT IV. CALL READY REMARKS." Aircraft: "HOSS 1, CAPTURED JS010. READY REMARKS ALPHA ALPHA 0-1." Controller: "HOSS 1, CONFIRMED ENEMY TANKS IN THE OPEN, COME BACK WITH ETA, TOT, AND BDA." b. If a tasked asset is HOLLOW for the J3.3 or J3.5 message, communicate the track details.

## 7. Read Backs

Theater or exercise guidance should specify the required read back. In the absence of direction, the following read-back formats for full- and partial digital and voice are listed from least restrictive and least radio time to the most restrictive and most radio time.

a. WILCO digital response to J12.0. b. Voice response with task type and location (e.g., BULLSEYE, J3.5 track number, or coordinates). c. Voice response with task type, coordinates, elevation, and remarks.

## 8. Surface Threat Picture Communication

a. Common Tactical Ground Picture. The signals intelligence (SIGINT) ID authority is responsible for maintaining accuracy of the common tactical ground picture based on emitter or ROTATOR information as well as resolving any emitter ID ambiguities.

(1) Refer to SAM systems by their number only (e.g., SIX or ROLAND) to
preserve brevity on the tactical NET. (2) Only voice "S-A-(number)" if required to eliminate ambiguity. (3) SIGINT Terminology.
(a) AWAKE. This describes land or surface activity detected via communications intelligence. (b) ACTIVE. This means the emitter is radiating (derived from electronic intelligence).

Note: Assume all threat emitters only remain ACTIVE/AWAKE for short periods and, therefore, only report DOWN (previously active, but no longer emitting) or ASLEEP in response to a status request or to eliminate ambiguity.

(c)
REPORTED. Used this if a threat emitter is derived from an off-board source.

(4) COLOR and TAG.
(a) COLOR calls will have the requesting agency's call sign, COLOR
system/subsystem type, frequency, and location (if known), and fill-ins. (b) Transmit a J14.0 with every COLOR call. (c) Respond to a COLOR call with TAG. Use comparative communication for TAG responses, providing the mission information or tactical report (TACREP) for the emitter, if appropriate.

## Color And Tag Example

Known Frequency (freq): "CHALICE, COLOR SIX MIPPLE ELEVEN FREQ 10 thousand 300 MEGAHERTZ, BULLSEYE 123/30" (CHALICE FORCE TELL associated J14.0). Unknown Freq: "CHALICE, COLOR BULLSEYE 123/30." Response: "AGENT, TAG ELEVEN BULLSEYE 123/30."

(5) TACREP.
(a) Transmit TACREPs on virtual private networks (VPNs) indicating the collection of tactical intelligence. (b) Assign TACREPs an alphanumeric designator indicating the type of activity and serialization. (c) Use the phrase "UPDATE TACREP" to provide updated or amplifying information on an existing TACREP. (d) Ensure alphanumeric designators are in accordance with table 8.

| Alphanumeric    | Intelligence                    |
|-----------------|---------------------------------|
| A-##            | Communication (air activity)    |
| E-##            | Electronic                      |
| G-##            | Communication (ground activity) |
| F-##            | Fusion (All/Multi-Source)       |
| H-##            | Human                           |
| I-##            | Imagery or nonimaging infrared  |
| J-##            | Radar moving-target indication  |
| N-##            | Communication (naval activity)  |
| O-##            | Overhead persistent infrared    |
| R-##            | Air operations center           |
| S-##            | Survivor/Isolated Personnel     |

## Tacrep Example

"AGENT, TACREP ECHO 0-4, SIX TARGET ACQUISITION ACTIVE, BULLSEYE 235/18, TRACK NUMBER 1-3-2-0-7, FREQ X-X-X-X-X." b. Situation Report (SITREP). Pass SIGINT, imagery intelligence, and moving target indication information on surface emitters on VPN.

(1) The SITREP is passed 5 minutes prior to the package LOWDOWN unless mission planning directs otherwise. (2) Emitters are passed using system type, BULLSEYE location, and operating frequency in the following priority:
(a) Air activity and location, in absence of an air picture (e.g., controller system is degraded). (b) ACTIVE/AWAKE (or within the last 8 hours) strategic SAMs that were not a part of the briefed enemy order of battle. (c) Any ACTIVE/AWAKE (or within the last hour) tactical SAMs. (d) Early warning or ground control intercept radars.

Note: The order of dissemination for ACTIVE/AWAKE strategic and tactical SAMs is: closest MEZ to friendly forces, closest MEZ to friendly axis of attack or ingress routes, and most lethal.

## Sitrep Example

"AGENT, SU-27 AIRBORNE TONOPAH. TWO TRACKER ACTIVE BULLSEYE 121/20, FREQ [X-X-X-X-X], TRACK NUMBER 0-6-0-2-3. SIX AWAKE BULLSEYE 135/40, TRACK NUMBER 0-6-0-0-4. ROLAND AWAKE BULLSEYE 125/35, TRACK NUMBER 0-6-0-3-7. TALL KING ACTIVE BULLSEYE 090/6 FREQ [X-X-X-X-X]." c. Combat Advisory Broadcast (CAB). Active S/A threat emitters are passed on the tactical NET using prebriefed labels or the BULLSEYE format.

(1) CAB is an addition to the threat picture.

(2) C2 agencies will relay CAB information received from VPN to the appropriate NETs.

## Cab Example

CAB from BANDSAW on primary NET: "BANDSAW, TWO ACTIVE BULLSEYE 035/8" or "BANDSAW, NORTH TWO ACTIVE."

d. Imminent Threat Warning (ITW). ITW is a S/A threat warning to a friendly asset.
(1) An ITW is passed when a friendly aircraft is within 5 nm of the maximum recommended intercept range of any ACTIVE, AWAKE, launching, or firing threat.

(2) An ITW is prefaced with the aircraft call sign or the BULLSEYE position of the friendly aircraft and uses prebriefed labels or the BULLSEYE format for the threat
description.
Note: When communicating with United States Army or United States Marine Corps rotary-wing aircraft and UASs, pass surface threat information in MGRS, if known. Attempt to provide at least a six-digit grid.

(3) No ITW is required if an aircraft has reported MUD, DEFENDING, or SINGER to the specified threat. (4) ITW procedures are coordinated for low-observable assets during mission planning.

## Itw Example "Eagle 1, Agent, Eleven Active Bullseye 015/9."

e. TRESPASS. Aircraft, controllers, and agencies will voice TRESPASS when an aircraft is within a not-previously-known SAM MEZ (e.g., a POP-UP SAM). If able, aircraft, controllers, or sensor operators, also, will voice the BULLSEYE location of the SAM.

## Trespass Example "Rambo 1, Trespass Fifteen Bullseye 155/52." 9. Threat Reaction Communication

a. Targeted aircraft should communicate S/A threat reactions on mission tactical NETs:
(1) If it enables, or aircraft requires, reactive suppression of enemy air defenses
(SEAD).

(2) To enhance the common tactical picture for other mission or package assets.
b. These transmissions should be in either a low- or high-fidelity format. Minimum accuracy to consider a threat "high fidelity" is a 5 nm, semi-major ellipse, or as mission-planned.

## Low-Fidelity Format

Call sign, radar warning receiver indication, bearing, DEFENDING with cardinal direction, ownship BULLSEYE.

## Low-Fidelity Example

"HORNET 1, SINGER 11, BEARING 3-6-0, DEFENDING WEST, BULLSEYE 345/30."

## High Fidelity Format

Call sign, radar warning receiver indication, S/A threat BULLSEYE/LOCATION, DEFENDING with cardinal direction.

## High Fidelity Example

"BOLT 1, SINGER 11 BULLSEYE 360/32, DEFENDING WEST."

## 10. Suppression Of Enemy Air Defenses (Sead) Contracts

a. SEAD aircraft should provide one of four responses to a DEFENDING call:
(1) HARM INBOUND. High-speed antiradiation missile (HARM) already employed. (2) MAGNUM. Launch of FRIENDLY antiradiation missile (ARM). (3) EMPTY. No emitters of interest detected.
(4) ARIZONA. No ARM ordnance remaining.
b. SNIPER and SLAPSHOT Communication.
(1) SNIPER.
(a) This is a directive call from the SEAD package/flight lead. (b) It indicates a specific aircraft/element should employ an ARM against a range-known S/A threat.

## Sniper Example

Directive Call: "STORM, SNIPER 11 BULLSEYE 360/32." Response: "STORM 2, MAGNUM 11 BULLSEYE 360/32."
(2) SLAPSHOT.

(a) This is a directive call indicating an aircraft or element should immediately employ the best-available ARM on the specified threat bearing. (b) SLAPSHOT assumes the S/A threat range is unknown.

## Slapshot Example

Directive Call: "STORM, SLAPSHOT 15 BEARING 3-1-7." Response: "STORM 2, HARM INBOUND."
(3) SEAD players respond with HARM INBOUND, MAGNUM, EMPTY, or ARIZONA.

c. Electromagnetic Attack (EA) Communication. Aircraft should direct or communicate EA using the following terminology:

## Ea Examples

Directing EA: "BOLT 1, JAM 11, BULLSEYE 360/32." Informative EA: "BOLT 1, CANYON 11, BULLSEYE 360/32." Ceasing EA: "BOLT 1, CLAM 11, BULLSEYE 360/32".

## 11. Find, Fix, Track, Target, Engage, And Assess (F2T2Ea) Contracts

a. Find. The MC is responsible to hold or delegate authority for aircraft or element search contracts.

## Find Example

MC: "BOLT, WORK 6 BULLSEYE 360/34." Aircraft: "BOLT 1, WORKING 6 BULLSEYE 360/34." MC: "HOSS, MAP 15 BULLSEYE 317/17." Aircraft: "HOSS 3, MAPPING 15 BULLSEYE 317/17." MC: "CONAN, INVESTIGATE TRACK NUMBER 1-2-3-4-5." Aircraft: "CONAN."

b. Fix.
(1) Locate the threat and pass TLE or ellipse (semi-major) quality with the FIXED call. (2) Use the following terms to delineate fix quality:
(a) Low Accuracy. Inside 1 nm.

## Low Accuracy Example

"BOLT 1, 6 FIXED BULLSEYE 360/32, LOW ACCURACY."

(b) High Accuracy. Inside 1,000 feet.

## High Accuracy Example

"AGENT 6, FIXED BULLSEYE 360/32, HIGH ACCURACY, TRACK NUMBER 0- 3-0-0-7."

(c) TARGETABLE. CAT II low is assumed.
- Any other TLE is added as a fill-in. - Controllers should populate a J3.5 over individual J12.6s once they are
called TARGETABLE.

## Targetable Examples

"HOSS 3, FIXED SCRUM HALF BULLSEYE 3-1-7/17, TARGETABLE." "AGENT, SCRUM HALF BULLSEYE 3-1-7/17, TARGETABLE, TRACK NUMBER 1-6-1-7-3."

## C. Track.

(1) TRACKING is necessary for custody of a threat, SAM, high-value target, or other surface entity. (2) The MC or PC can direct an asset to TRACK, SCAN, or MONITOR an area or object.

(a) TRACK. This is a directive call assigning responsibility to maintain sensors or a visual on a defined object or area to an asset.

(b) MONITOR.
- Maintain sensor awareness on a specified GROUP or object. It implies
tactically significant changes are communicated.
- For maritime operations, this means maintain contact or targeting
information on a maritime surface contact.
(c) SCAN. Search the indicated sector and report any CONTACTs.
(3) Assets can respond with OCCUPIED, TALLY, TRACKING, CAPTURED, or MONITORING, if able to TRACK.

## Tally Example

MC: "HOSS, TRACK THREE VEHICLE CONVOY BULLSEYE 300/45, MOVING WEST, TRACK NUMBER 3-4-3-4-5." Aircraft: "HOSS 1, TALLY."

## Captured Example

MC: "SABRE, TRACK T-72 COLUMN BULLSEYE 050/55, MOVING NORTH." Aircraft: "SABRE, CAPTURED, TRACK NUMBER 2-2-2-2-2."

## Monitoring Example

MC: "WEASEL 51, MONITOR 11, TRACK NUMBER 1-1-1-1-1." Aircraft: "WEASEL 51, MONITORING 11, BULLSEYE 316/60."
(4) Assets can respond with NO JOY if they have not found the object.

## D. Target And Attack Plan.

(1) The purpose of the ATTACK plan is to:
(a) Establish a SORT, especially across multiple formations. (b) To establish weapon pairings. (c) Reference locations (e.g., predetermined points, anchor references with distance, or BULLSEYE). (d) Time and deconfliction prior to PUSHING as a force package.
(2) This plan should also delineate responsibilities.
Note: The plan can be communicated via Link 16, and each player needs only to acknowledge GOOD DATA.

## Attack Game Plan Example

In the following example, RAMBO is the MC and escort PC, HORNET is the strike PC, BOLT is a strike flight lead, and PYTHON is the SEAD PC. RAMBO (MC): "HORNET, BOLT, PYTHON, STANDBY GAME PLAN." Flight Leads: "HORNET." "BOLT." "PYTHON." RAMBO: "HORNET, TARGET AND SCAN ALPHA ALPHA 0-1, TWO VEHICLE
CONVOY BULLSEYE 275/69, MOVING SOUTH, BEST. PUSH AT 21:17 FROM RED OSCAR." "BOLT, COVER ALPHA ALPHA 0-1." "RAMBO ESCORT AND PYTHON SEAD PER BRIEF."
Flight Leads: "HORNET." "BOLT." "PYTHON."

e. Engage.
(1) The aircraft executing the attack will call ATTACKING at the push, with a TOT, once all players have acknowledged the plan.

(2) Aircraft should call releases with time of flight and IMPACT, when able. If an aircraft has additional support requirements for the A/S weapon, provide this as a fill-in (e.g., LASING or SCANNING).

## Attacking Example

"HORNET, CAPTURED ALPHA ALPHA 0-1. ATTACKING TOT 21:21:15." "HORNET 1, ONE WEAPON AWAY ALPHA ALPHA 0-1, 45 SECONDS, LASING."
"HORNET 1, SPLASH ALPHA ALPHA 0-1."

f. Assess.
(1) SCAN can be used to direct the weapon effects assessment.
(a) SCAN means to search the indicated sector and report any CONTACTs. (b) Once the target or object has been acquired and is being tracked with an onboard sensor or visually, respond with CAPTURED or TALLY. (c) If unable to find the target or object, relay VACANT, EMPTY, or NO JOY.
(2) To describe the weapon results, use successful or unsuccessful.
(a) SUCCESSFUL. Desired weapon effects were generated.  SUCCESSFUL can be used to complete the F2T2EA chain.
- DROPPING is an informative call from a tasked aircraft that the aircrew is no longer targeting/targeted to a tasking.

## Weapons Effects Generated (Dropping) Example

HORNET: "HORNET SPLASH ALPHA ALPHA 0-1 SUCCESSFUL. DROPPING
ALPHA ALPHA 0-1."
- DROP is a directive call to remove a ground target from the tactical ground picture.

## Weapons Effects Generated (Drop) Example

HORNET: "HORNET SPLASH ALPHA ALPHA 0-1 SUCCESSFUL." HORNET: "DARKSTAR DROP ALPHA ALPHA 0-1, T-N 5-2-3-4-2."
(b) FUMBLE. Desired weapon effects were not generated.

- Informative fill-ins can assist when relaying UNSUCCESSFUL.
- "FUMBLE CLEAN" (i.e., no visible battle damage) indicates the target
sustained no damage or no weapon impact was noted.
- "FUMBLE HIT" indicates weapon impact was noted within a lethal
distance, but the effects were not generated.

## Weapons Effects Not Generated Example

HORNET: "HORNET, SPLASH ALPHA ALPHA 0-1, FUMBLE HIT."
(3) Reattack.

(a) Plan reattack options during mission planning, if an asset is capable of a real-time hit assessment. (b) To facilitate rapid reattack, consider using SCAN with COVER.
- COVER. This is a directive call to be ready for reattack or reengage, if
weapons effects are not generated.
- HOUNDDOG. This call is in response to COVER, indicating the directed
aircraft is in a position to employ weapons.

## Reattack Option Example

MC: "HORNET TARGET AND SCAN ALPHA ALPHA 0-1.

BOLT COVER ALPHA ALPHA 0-1."
HORNET: "HORNET 1, ONE WEAPON AWAY ALPHA ALPHA 0-1,
45 SECONDS, LASING AND SCANNING."
HORNET: "HORNET, SPLASH ALPHA ALPHA 0-1, UNSUCCESSFUL HIT." BOLT: "BOLT, HOUNDDOG ALPHA ALPHA 0-1." MC: "BOLT, REATTACK, ALPHA ALPHA 0-1."
This page intentionally left blank.

## References Joint Publications

DOD *Dictionary of Military and Associated Terms*, as of January 2021
JP 1-0, *Joint Personnel Support*, 01 December 2020
JP 3-0, *Joint Operations*, 17 January 2017 (Incorporating Change 1, 22 October 2018)
JP 3-09.3, *Close Air Support*, 10 June 2019
JP 3-52, *Joint Airspace Control*, 13 November 2014

## Glossary Part IAbbreviations And Acronyms

A
A/A
air-to-air
A/S
air-to-surface
AA
aspect angle
ACO
airspace control order
ACC
air control communication
AFTTP
Air Force tactics, techniques, and procedures
ALSA
Air Land Sea Application (Center)
AOR
area of responsibility
ARM
antiradiation missile
ASOC
air support operations center
ATO
air tasking order
AWACS
Airborne Warning and Control System
B
BDA
battle damage assessment
BRAA
bearing, range, altitude, and aspect
BVR
Beyond visual range
C
C2
command and control
CAB
Combat Advisory Broadcast
CAP
combat air patrol
CAT
category
CG
guided missile cruiser
CRC
control and reporting center
CVN
multi-purpose aircraft carrier (nuclear powered)
CWC
composite warfare commander
D
DASC
direct air support center
DDG
guided missile destroyer
DPI
desired point of impact
E
EA
electromagnetic attack
| EOM     | end of message                                    |
|---------|---------------------------------------------------|
| ETA     | estimated time of arrival                         |
| F       |                                                   |
| F2T2EA  | find, fix, track, target, engage, assess          |
| freq    | frequency                                         |
| G       |                                                   |
| GEOREF  | geographic reference                              |
| H       |                                                   |
| HARM    | high-speed antiradiation missile                  |
| I       |                                                   |
| ID      | identification                                    |
| ISR     | intelligence, surveillance, and reconnaissance    |
| ITW     | imminent threat warning                           |
| J, K    |                                                   |
| JAOC    | joint air operations center                       |
| JFC     | joint force commander                             |
| JP      | joint publication                                 |
| JSTARS  | Joint Surveillance Target Attack Radar System     |
| L       |                                                   |
| LHA     | amphibious assault ship (general purpose)         |
| LHD     | amphibious assault ship (multi-purpose)           |
| LLTR    | low-level transit route                           |
| LPD     | amphibious transport dock                         |
| M       |                                                   |
| MAWTS-1 | Marine Aviation Weapons and Tactics Squadron One  |
| MC      | mission commander                                 |
| MCRP    | Marine Corps reference publication                |
| MDS     | mission design series                             |
| MEZ     | missile engagement zone                           |
| MGRS    | military grid reference system                    |
| MTTP    | multi-service tactics, techniques, and procedures |
| N       |                                                   |
| NAWDC   | Naval Aviation Warfighting Development Center     |
| NET     | Network                                           |
| nm      | nautical mile                                     |
| NTTP     | Navy tactics, techniques, and procedures    |
|----------|---------------------------------------------|
| NWDC     | Naval Warfare Development Command           |
| O        |                                             |
| QC       | quality control                             |
| OPTASK   | operational tasking (message)               |
| P, Q     |                                             |
| PC       | package commander                           |
| R        |                                             |
| ROE      | rules of engagement                         |
| RTO      | range training officer                      |
| S        |                                             |
| S/A      | surface-to-air                              |
| SA       | situational awareness                       |
| SAM      | surface-to-air missile                      |
| SEAD     | suppression of enemy air defenses           |
| SIGINT   | signals intelligence                        |
| SITREP   | situation report                            |
| SPINS    | special instructions                        |
| T        |                                             |
| TA       | target aspect                               |
| TAC      | tactical                                    |
| TACADMIN | tactical administration                     |
| TAC C2   | tactical command and control                |
| TACREP   | tactical report                             |
| TAOC     | tactical air operations center (USMC)       |
| TECOM    | Training and Education Command              |
| TLE      | target location error                       |
| T/M/S    | type, model, and/or series                  |
| TOD      | time-of-day                                 |
| TOT      | time on target                              |
| TTP      | tactics, techniques, and procedures         |
| U        |                                             |
| UAS      | unmanned aircraft system                    |
| US       | United States                               |
| USAACE     | United States Army Aviation Center of Excellence    |
|------------|-----------------------------------------------------|
| USAFWS     | United States Air Force Weapons School              |
| USMC       | United States Marine Corps                          |
| V          |                                                     |
| VPN        | virtual private network                             |
| W, X, Y, Z |                                                     |
| WEZ        | weapons engagement zone                             |

## Part IiTerms And Definitions

airspace controlThe capabilities and procedures used to increase operational effectiveness by promoting the safe, efficient, and flexible use of airspace. (DOD
Dictionary. Source: JP 3-52, Joint Airspace Control) anchored[A/A] Turning engagement at the specified location. (Source: Brevity MTTP) bandit[A/A] [AIR-MAR] Positively identified as an enemy IAW theater ID criteria. The term does not imply direction or authority to engage. * [SO] A SUSPECT whose orbital parameters are such that it may become a collection and/or counterspace concern to a spacecraft in the relative near-term, therefore limiting decision space. (Source: Brevity MTTP) blow(ing) through 1. [A/A] Directive call to continue straight ahead at the MERGE and do not become ANCHORED with target(s). 2. [A/A] Informative call that the intercepting aircraft is dropping targeting responsibility and commencing a BLOW THROUGH. (Source: Brevity MTTP) bogey[A/A] [S/A] [SO] A CONTACT whose identity is unknown. (Source: Brevity MTTP) clean1. [A/A] No sensor information on a GROUP of interest. 2. No visible battle damage. 3. Aircraft not carrying external stores. (Source: Brevity MTTP) cold1. [A/A] Initiate(ing) a turn in the combat air patrol away from the anticipated threats.2. [A/S] Defined area is not expected to receive fire (enemy or FRIENDLY).

3. [A/A] Intercept geometry will result in a pass or roll out behind the target. 4. * [A/A] Contact aspect stabilized 020 degrees from the tail or 160180 degrees from the nose. 5. [A/S] Contact aspect stabilized 0-20 degrees or 160-180 degrees from referenced position (friendly forward operating base, named area of interest (NAI), target area, etc.). 6. [AIR-MAR] Contact aspect stabilized 0-20 degrees from stern or 160-180 degrees from bow. (Source: Brevity). combatant commanderA commander of one of the unified or specified combatant commands established by the President. Also called CCDR. (DOD Dictionary. Source: JP 3-0) contractA preestablished communication plan to delineate roles and responsibilities, outline criteria for execution, and establish the method of communication. (This term and its definition are applicable only in the context of this publication and cannot be referred to this way outside this publication.) crossing[A/A] Two GROUPs initially separated in azimuth decreasing azimuth separation to pass each other. (Source: Brevity MTTP)
declare[A/A] [S/A] [AIR-MAR] Inquiry as to the ID of a specified track(s), target(s), or correlated GROUP. Responses include: FRIENDLY, BOGEY, BANDIT, HOSTILE, NEUTRAL, UNABLE, CLEAN, or FURBALL. Full positional data (BULLSEYE) must accompany responses. (Source: Brevity MTTP)
descriptive callsA transmission providing information but does not require a response. See also interrogative call. (This term and its definition are applicable only in the context of this publication and cannot be referred to this way outside this publication.) drop(ing) 1. [A/A] [A/S] Stop or stopping monitoring of specified emitter or target or GROUP and resume(ing) search responsibilities. 2. (TRACK number) Remove the emitter or target from tactical picture or track stores.

3. [EW] Remove a specific system or EOB category from search responsibilities.

(Source: Brevity MTTP) electronic remote fill (ERF)Method by which an NCS electronically updates FH data of netmembers and transmits sync time for cold start net openings. (Source: TM 11- 5820-890-10-8)
electronic warfare(DOD) Military action involving the use of electromagnetic and directed energy to control the electromagnetic spectrum or to attack the enemy. Also called EW. See also directed energy; electromagnetic spectrum; electronic attack; electronic protection; electronic warfare support. (DOD Dictionary of Military and Associated Terms. Source: JP 3-13.1) friendly A positively identified FRIENDLY aircraft, ship, spacecraft, or ground position. (Source: Brevity MTTP) furball[A/A] Non-FRIENDLY aircraft and FRIENDLY aircraft are inside of 5 nautical miles of each other. Can be response to a DECLARE request.

* [SO] Spacecraft are so close together that off-board sensors cannot distinguish relative positions. (Source: Brevity MTTP) group(s)1. [A/A] Any number of air CONTACT(S) within 3 nautical miles in azimuth and range of each other. 2. [AIR-MAR] Any number of surface CONTACTs within 1 nautical miles of each other. (Source: Brevity MTTP) hostile A contact identified as enemy upon which clearance to fire is authorized IAW theater rules of engagement. (Source: Brevity MTTP) interrogative callsA transmission requiring a response. See also descriptive call. (This term and its definition are applicable only in the context of this publication and cannot be referred to this way outside this publication.) lane crosserA GROUP that maneuvers into different areas of targeting responsibility. See also lane rider. (This term and its definition are applicable only in the context of this publication and cannot be referred to this way outside this publication.) lane riderA GROUP that maintains a track direction on or near the line dividing different areas of targeting responsibility. See also lane crosser. (This term and its definition are applicable only in the context of this publication and cannot be referred to this way outside this publication.) joined[A/A] Two or more radar returns have come together. (Source: Brevity MTTP) merge[A/A] FRIENDLIES and targets have arrived in the visual arena. (Source:
Brevity MTTP)
monitor(ing) 1. [A/A] [A/S] Maintain(ing) sensor awareness on specified GROUP or object. Implies that tactically significant changes will be communicated. (Source: Brevity MTTP) 2. * [AIR-MAR] Maintain contact or targeting information on a maritime surface contact. neutralA positively identified aircraft, ship, or ground position whose characteristics, behavior, origin, or nationality indicate it is neither supporting nor opposing FRIENDLY forces.(Source: Brevity MTTP)
new picture[A/A] [A/S] [AIR-MAR] Used by controller or aircrew when tactical PICTURE has changed. Supersedes all previous calls and reestablishes PICTURE for all players. (Source: Brevity MTTP)
passing[A/A] Two GROUPs initially separated in range, decrease range separation and are passing each other. (Source: Brevity MTTP) tactical administrationThe interflight and intraflight processes and procedures established in a tactical command and control managed area of responsibility. Also called TACADMIN. See also tactical command and control. (This term and its definition are applicable only in the context of this publication and cannot be referred to this way outside this publication.) tactical command and controlThe joint force air or maritime component commander's use of positive and/or procedural control methods to control airspace and manage air operations. Also called TAC C2. (This term and its definition are applicable only in the context of this publication and cannot be referred to this way outside this publication.)
tactical controlThe authority over forces that is limited to the detailed direction and control of movements or maneuvers within the operational area necessary to accomplish missions or tasks assigned. Also called TACON. (DOD Dictionary. Source:
JP 1) targeted[A/A] Fighter has acquired assigned GROUP and has assumed responsibility for it. (Source: Brevity MTTP) track1. [A/A] GROUP or CONTACTS direction of flight or movement.

2. ** [A/S] [S/S] Directive call assigning responsibility toan asset for maintaining sensor or visual observation of a defined object or area.

3. ** [A/S] Rotary wing directive call to establish race track (e.g., "Taz 31, TRACK left). 4. ** [A/S] [AIR-MAR] Information call stating direction of vehicle or CONTACT in motion
(e.g. TALLY TECHNICAL TRACK Northwest). (Source: Brevity MTTP)
unableCannot comply as requested or directed. (Source: Brevity MTTP)
This page intentionally left blank.
By Order of the Secretary of the Army JAMES C. MCCONVILLE
General, United States Army Chief of Staff Official:
MARK F. AVERILL
Acting Administrative Assistant to the Secretary of the Army
2123804
DISTRIBUTION:
Active Army, Army National Guard, and US Army Reserve: Distributed in electronic media only (EMO).

By Order of the Secretary of the Air Force LESLIE H. BABCOCK
Colonel, USAF
Commander Curtis E. LeMay Center for Doctrine Development and Education

ACCESSIBILITY:
Publications and forms are available on the e-Publishing website
at www.e-publishing.af.mil for downloading or ordering.
RELEASABILITY:
Distribution approved for public release; distribution is unlimited.
* Supersedes ATP 3-52.4/MCRP 3-20F.10/NTTP 6-02.9/AFTTP 3-2.8, dated 14 February 2020.

This page intentionally left blank.