MTTP/A2A

08 / Air-to-Air Combat

Air combat is primarily carried out by CAP aircraft. The two main mission types are DCA (Defensive Counter Air) and OCA (Offensive Counter Air).

Groups and Contacts

A GROUP is any number of air contacts within 3 nm in azimuth and range of each other. A CONTACT is an individual radar return within a GROUP. Single contact is the assumed strength for all GROUPs unless otherwise specified. A GROUP with three or more contacts is called HEAVY.

The PICTURE establishes a common tactical air image and describes the spatial relationship of GROUPs. It is always communicated in BULLSEYE format unless briefed otherwise. Only the Three GROUPs with highest Priority are Conveyed

Contact Declaration

Before a fighter can engage, a contact must be declared. Declaration is performed by the controller in response to a DECLARE request.

Declaration	Meaning	Engagement Authority
BOGEY	Identity unknown	Not cleared to engage
OUTLAW	Originates from known or suspected hostile area	Not cleared to engage; escalation criteria apply
SPADES	No valid IFF response on interrogation	Not cleared to engage; escalation criteria apply
BANDIT	Positively identified as enemy IAW theater ID criteria	Not cleared to engage; does not imply authority to fire
HOSTILE	Confirmed enemy; clearance to fire authorized IAW ROE	Cleared to engage
NEUTRAL	Positively identified as neutral	Not cleared to engage
FRIENDLY	Positively identified as friendly	Not cleared to engage
FURBALL	Friendly and non-friendly aircraft within 5 nm	Employment not authorized until resolved

A BOGEY, BANDIT, OUTLAW, or SPADES classification does not authorize engagement. HOSTILE is the only declaration that authorizes weapons employment IAW ROE.

Communication Cadence by Intercept Phase

Communication priority shifts between the controller and fighters depending on the phase of the intercept.

Phase	Priority Communicators
Pre-COMMIT / Marshal	1. Controller · 2. Fighters
Post-COMMIT / Push	1. Controller · 2. Fighter
Targeting / Weapons Employment	1. Fighters · 2. Controller
Merge	1. Engaged Fighter · 2. Supporting Fighters · 3. Controller
Post-Merge	1. Fighter Clearing Merge · 2. Supporting Fighters · 3. Controller

TAC Range

Called at 60 nm (default) by the first asset to recognize the separation. Signals all players to prepare for targeting. Pre-commit SA building continues until this point.

Station	Phrase
Controller or Fighter	{CS} {Group Label} TAC RANGE

Airspace Sanitization

A Section consists of two aircraft, each equipped with its own radar. Regardless of the number of bars or maximum azimuth a single radar supports, no single system can cover the entire sky. To compensate, both radars are stacked and assigned to different portions of the airspace — each portion is called an Area of Responsibility (AOR). This technique, known as Radar Mating, vastly increases the total volume scanned and ensures that no unknown contacts are operating in the area beyond already-tracked groups. The exact parameters depend on the aircraft type: the US Navy recommends RWS, 140°, 6 bars, end scale 80 nm, with radars mated at 25 nm: placing the flight lead between 40,000 and 15,000 ft, and the wingman from ground level to 25,000 ft.

The process of actively scanning assigned AORs to confirm no unknown contacts are present is called Sanitisation.

Because both Radar Mating parameters and Sanitisation responsibilities directly affect how an engagement develops, all of this must be pre-briefed and set as a contract before the mission. Time pressure may not always permit a thorough sanitisation pass, and how to handle that contingency should likewise be agreed upon in the brief.

Targeting

The flight assigns GROUP responsibility and confirms classification.

Station	Phrase
FL	{Controller-CS} {CS} DECLARE {Group Label or Bullseye Position}
Controller	{Group Label} DECLARED {HOSTILE / BOGEY / FRIENDLY / UNABLE / FURBALL}
FL	{CS} TARGET {Group Label} {Tactic}
Once group appears on radar
FL	{CS} TARGETED {Group Label} BULLSEYE {Bearing/Range}
Controller	No response if information correlates. Comparative response if correction is required.

The Engagement Loop

The engagement loop is the core sequence executed by all fighter flights once committed and targeting is established. It repeats until the GROUP is splashed, leaves the area, or the flight resets.

MELD

The flight lead directs all flight members to shift their radars from wide sanitization to focused SA on the assigned GROUP. This transition narrows the radar from maximum azimuth and altitude coverage to a tighter volume centered on the target. Sanitization of the surrounding airspace ceases until DROPPING is called.

Station	Phrase
FL	{Controller-CS} {CS} MELD
All flight members shift radar from sanitization to the assigned GROUP

SORT

The flight lead assigns individual contacts within the GROUP to specific flight members. Each member acknowledges with SORTED when they have confirmed their assigned contact on radar and are prepared to engage it. If a member cannot confirm their assigned contact, SORTED is withheld until resolution.

Station	Phrase
FL	(intraflight) FLIGHT SORT {Criteria}
#2	(intraflight) #2 SORTED
#3	(intraflight) #3 SORTED
#4	(intraflight) #4 SORTED

JUDY

Called by the flight lead when the flight no longer requires controller guidance to prosecute the intercept. From this point, the controller minimizes transmissions and provides situational awareness information only. JUDY is not always called.

Station	Phrase
FL	{Controller-CS} {CS} JUDY
Controller	Minimizes transmissions. Provides SA and THREAT calls only.

ENGAGE

Directive call from the flight lead to a specific wingman to employ weapons. The flight lead may also direct simultaneous employment by multiple members.

Station	Phrase
FL	{CS} ENGAGE
Wingman	{CS}

Weapon Employment

The firing aircraft calls the shot on TACC2 NET immediately after employment. The call includes shot type, GROUP label, contact description, BULLSEYE position, and altitude. The controller acknowledges with COPY SHOT.

If a fighter determines a GROUP HOSTILE and ROE has been met, the fighter may employ autonomously and include HOSTILE in the shot transmission.

Station	Phrase
Firing Aircraft	{TACC2-CS} {CS} FOX THREE {Group Label} {Contact Description} BULLSEYE {Bearing/Range} {Altitude}
TACC2	{TACC2-CS} COPY SHOT
Autonomous HOSTILE employment
Firing Aircraft	{Controller-CS} {CS} FOX THREE {Group Label} BULLSEYE {Bearing/Range} {Altitude} HOSTILE
TACC2	{TACC2-CS} COPY SHOT

Multiple shots in one transmission are acceptable:

 SHADOW12 FOX THREE NORTH GROUP LEAD CONTACT BULLSEYE 2-7-0/20 TWENTY THOUSAND; SHADOW11 FOX THREE NORTH GROUP TRAIL CONTACT.

OUT / DEFENDING

Following weapon employment the flight turns away from the threat. OUT is a planned maneuver executed at a prebriefed range. DEFENDING indicates a reactive maneuver against an incoming weapon and is called with the cardinal direction of the defensive turn.

Station	Phrase
FL	{Controller-CS} {CS} OUT {Direction}
or, if reacting to an incoming weapon
Aircraft	{CS} DEFENDING {Direction}

DROPPING

May be called in conjunction with OUT. Signals the controller that the flight has ceased monitoring the GROUP and is returning to sanitization radar settings. Monitoring responsibility transfers back to the controller.

Station	Phrase
FL	{Controller-CS} {CS} OUT {Direction} DROPPING {Group Label}
Controller resumes monitoring of the dropped GROUP
Controller	Resumes monitoring.

Assessment

The flight assesses weapon effects from sensor data or controller reports. Three outcomes are possible:

Outcome	Action
GROUP splashed	Call SPLASH
GROUP remains a factor, follow-up shot required	Turn IN, return to MELD
GROUP has left the area or is no longer a factor	Proceed with Tasking

IN (Follow-up Engagement)

If the GROUP remains a factor and the tactic permits a follow-up shot, the flight turns back toward the GROUP. The IN call triggers a new cycle beginning at MELD.

Station	Phrase
FL	{Controller-CS} {CS} IN {Direction}
FL	{Controller-CS} {CS} MELD
Re-sort as required, then return to ENGAGE

SPLASH

Called when weapon effects confirm the GROUP or contact is destroyed.

Station	Phrase
Firing Aircraft or Controller	{CS} SPLASH {Group Label or Contact Description}

Common Calls

DECLARE

Inquiry as to the identity of a specified GROUP. Full positional data in BULLSEYE format must accompany all responses.

 MIKE, EAGLE 11, DECLARE NORTH GROUP.
 EAGLE 11, NORTH GROUP BULLSEYE 2-7-3/27, TWENTY-TWO THOUSAND, TRACK EAST, BOGEY SPADES.

BOGEY DOPE

Request for BRAA information on the indicated GROUP or the closest GROUP if not specified. Does not imply fighter targeting.

 MIKE, EAGLE 11, BOGEY DOPE NORTH GROUP.
 EAGLE 11, NORTH GROUP BRAA 2-1-0/28, THIRTY-EIGHT THOUSAND, HOT, HOSTILE.

NAILS

Fighter's radar warning receiver is detecting an airborne interceptor radar in search mode. Called with bearing or cardinal direction.

 EAGLE 1, NAILS 2-7-0.

SPIKED

Fighter is being actively tracked by an airborne radar. Called with bearing or cardinal direction. Controller correlates to a GROUP within ±30 degrees and responds with range, altitude, aspect, declaration, and GROUP name.

 EAGLE 1, SPIKED 2-7-0.
 EAGLE 1, SPIKE RANGE 17, THIRTY THOUSAND, HOSTILE EAST GROUP, TWO CONTACTS.

FADED and VANISHED

FADED — a previously tracked GROUP not updated by sensors for 30 seconds. The controller reports the GROUP as FADED with last known BULLSEYE position. Fighters maintain MONITOR responsibility if they can maintain correlation. FADED is not used for friendly aircraft — controllers use NEGATIVE CONTACT for friendlies not held on sensors.

VANISHED — a special case of FADED used when the GROUP is not in a known blind zone and is correlated to a friendly shot that meets parameters for successful termination.

Unexpected Contacts

Three distinct call types exist for contacts not part of the established picture:

Call	Criteria	Format
ADDITIONAL GROUP	Newly detected outside targeting range, or does not fit traditional label	BULLSEYE
POP-UP GROUP	Previously undetected; appears inside targeting range but outside THREAT range	BULLSEYE
THREAT GROUP	Undetected or unreported GROUP meeting briefed THREAT criteria	BRAA to the closest aircraft

 DARKSTAR, POP-UP GROUP BULLSEYE 2-7-0/15, FIVE THOUSAND, TRACK WEST, BOGEY SPADES.
 RAMBO 2, THREAT GROUP BRAA 2-7-0/13, ONE THOUSAND, HOT, HOSTILE.

09 / Defensive Counter Air (DCA)

DCA is the use of fighter aircraft to defend a ground asset or airspace against hostile air threats. It uses prebriefed lanes and defined ranges.

DCA Range Structure

All ranges are prebriefed per sortie. The following are the standard range lines used in DCA:

Range Line	Definition
Mission Fail Line	The line the enemy must not cross for the mission to succeed. Defines the maximum depth of the defensive problem.
Commit Line (CL)	The line at which a bogey is declared HOSTILE IAW theater ROE and the flight is authorized to commit. Prebriefed for all DCA sorties.
Targeting Range	The prebriefed distance at which all contacts must be intercepted. A GROUP inside this range with no assigned fighter is UNTARGETED. Prebriefed per sortie.
TAC Range	Default 60 nm from the closest fighter to the closest GROUP. Signals all players to prepare for targeting.
Threat Range	The prebriefed range at which an untargeted GROUP meeting THREAT criteria triggers a THREAT call. Prebriefed per sortie.

COMMIT Authority

COMMIT authority is derived from the combatant commander and delegated through the chain of command. Any of the following may hold or recommend COMMIT authority depending on what is delegated:

Role	Abbreviation	Authority
Flight Lead	FL	Usually holds COMMIT authority unless delegated
Team Lead	TL	May hold COMMIT authority if delegated
Mission Commander	MC	May hold COMMIT authority if delegated
TACC2	—	May hold COMMIT authority if delegated

If only the MC, TL, or FL holds COMMIT authority, the controller may only recommend COMMIT. If the controller holds COMMIT authority, the MC and TL may only recommend.

DCA Flow

Lane Handover

When an outgoing flight is relieved on station by an incoming flight, a positive lane handover is required before the outgoing flight departs.

Station	Phrase
Off-going Lane Commander	{CS} MOVE FORWARD
On-coming Lane Commander	{CS}
On-coming aircraft may enter the lane. Lane commander authority has not yet transferred.
Off-going Lane Commander	{CS} YOU HAVE THE LANE
On-coming Lane Commander	{CS} HAS THE LANE

The off-going flight passes critical mission information to the controller before departing. The controller passes big-picture information to the on-coming flight before pushing them to the tactical frequency.

Pre-Commit

The flight arrives at its prebriefed CAP position with FENCE IN complete and radars in sanitization configuration. The controller holds picture responsibility.

Station	Phrase
FL	{Controller-CS} {CS} PICTURE
Controller	{CS} {Nr of Groups} {Group Label} BULLSEYE {Bearing/Range} {Altitude} TRACK {Direction} {Declaration} {Nr of Contacts}

The flight evaluates commit criteria continuously. Pictures are requested as needed to maintain SA.

Commit

FIGHTER AUTHORITY COMMIT

Station	Phrase
TACC2	{TACC2-CS} {BULLSEYE CALL} Recommend {CS} COMMIT
FL	{CS} COMMIT

CONTROLLER AUTHORITY COMMIT

Station	Phrase
FL	{CS} Recommend Commit
TACC2	{TACC2-CS} {BULLSEYE CALL} {CS} COMMIT
FL	{CS}

After COMMIT, fighters hold radio priority.

Targeting

The flight assigns GROUP responsibility and confirms classification.

Station	Phrase
FL	{Controller-CS} {CS} DECLARE {Group Label or Bullseye Position}
Controller	{Group Label} DECLARED {HOSTILE / BOGEY / FRIENDLY / UNABLE / FURBALL}
FL	{CS} TARGET {Group Label} {Tactic}
Once group appears on radar
FL	{CS} TARGETED {Group Label} BULLSEYE {Bearing/Range}
Controller	No response if information correlates. Comparative response if correction is required.

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

Engagement Loop

The flight executes the standard engagement loop as defined in section 08. The loop repeats until the GROUP is splashed, leaves the lane, or the flight resets.

Once the Engagement is Complete the flight resets back to the briefed Position

RESET

Directs the flight to return to its prebriefed position or area of operations. RESET implies DROPPING and returns all targeting responsibility to the controller.

Station	Phrase
FL	{Controller-CS} {CS} RESET
Flight returns to prebriefed CAP position. Controller resumes full picture responsibility

THREAT Call

If a fighter will pierce THREAT range to an untargeted GROUP, the controller makes a THREAT call in BRAA format no later than THREAT range.

 HEAT 31, ADDITIONAL GROUP THREAT, BRAA 1-2-5/35, THIRTY-FIVE THOUSAND, HOT, HOSTILE.

If the THREAT is within 5 nm of friendly fighters:

 BOLT 1, THREAT NORTH THREE, TEN THOUSAND, TRACK SOUTH, HOSTILE.

10 / Offensive Counter Air (OCA)

OCA is the use of fighter aircraft to suppress, destroy, or neutralize enemy air assets before they can threaten friendly forces. Unlike DCA, OCA is not lane-based and does not require a commit line. The flight pushes into the threat environment rather than waiting for the threat to approach.

OCA Range Structure

The same range lines apply as in DCA — Threat Range, Targeting Range, and TAC Range — but all are prebriefed based on the specific mission geometry and threat environment. There is no commit line or mission fail line in OCA.

OCA Flow

OCA does not have a lane handover or a commit phase. The flight checks in, receives the picture, establishes targeting, and executes the engagement loop.

Pre-Targeting

Station	Phrase
FL	{Controller-CS} {CS} PICTURE
Controller	{CS} {Nr of Groups} {Group Label} BULLSEYE {Bearing/Range} {Altitude} TRACK {Direction} {Declaration} {Nr of Contacts}

Targeting

Identical to DCA targeting. The flight assigns GROUP responsibility, declares, announces the tactical plan on intraflight, and calls TARGETED once the GROUP is on radar.

Engagement Loop

The flight executes the standard engagement loop as defined in section 08.

The primary difference from DCA: in OCA there is no prebriefed position to RESET to in the same sense. RESET in OCA returns the flight to the prebriefed holding or egress point as defined in the mission brief.

11 / Intercept (VID)

A Visual Identification (VID) intercept is conducted when a contact cannot be declared HOSTILE or FRIENDLY by electronic means alone, and visual confirmation of aircraft type, markings, or behavior is required before engagement authority can be granted or withheld.

VID intercepts follow a structured sequence: the controller guides the fighter to a position from which a visual identification pass can be made, then the fighter reports the result and awaits further direction.

Intercept Flow

Commit

The controller or flight lead initiates the intercept against the unidentified contact.

Station	Phrase
Controller	{CS} COMMIT {Group Label} BULLSEYE {Bearing/Range} {Altitude} {Declaration} {Nr of Contacts}
FL	{CS} COMMIT

Guidance

The controller provides vectors to position the fighter for a VID pass. This is the only phase where the controller takes positive close control of the intercept geometry. BRAA format is used throughout.

Station	Phrase
Controller	{CS} BRAA {Bearing/Range} {Altitude} {Aspect} {Declaration}
FL	{CS}
Controller continues to provide updated vectors until fighter calls JUDY

JUDY

The fighter calls JUDY when radar contact is established and no further controller guidance is required. The controller minimizes transmissions from this point.

Station	Phrase
FL	{Controller-CS} {CS} JUDY
Controller	Minimizes transmissions. Continues to provide SA information only.

Tally

The fighter calls TALLY when visual contact is established with the target.

Station	Phrase
FL	{CS} TALLY {Position}

Identification

The fighter conducts the VID pass and reports the result to the controller. The report includes aircraft type, markings, and behavior observed.

Station	Phrase
FL	{Controller-CS} {CS} IDENTIFIED {Aircraft Type} {Markings / Behavior}
Controller	{CS} {Further Instructions / Declaration Update}

If the contact is identified as HOSTILE following the VID pass, the controller issues the updated declaration and the flight may proceed to engagement IAW ROE. If the contact is FRIENDLY or NEUTRAL, the flight disengages and returns to its prebriefed position.

12 / Merge

A merge occurs when friendly and target aircraft arrive in the visual arena, within 3–5 nm of each other. At the merge, radar resolution becomes limiting and the engagement transitions from BVR to Within Visual Range (WVR).

Communication Priority at the Merge

The engaged fighter holds radio priority. The supporting fighter and controller subordinate their transmissions accordingly.

Role	Responsibility
Engaged Fighter	Calls the merge, manages the engagement, and calls employment and results. Holds radio priority.
Supporting Fighter	Provides SA to the engaged fighter. Calls PRESS when directed and mutual support is maintained. Subordinates transmissions to the engaged fighter.
Controller	Minimizes transmissions. Provides THREAT calls, SA updates, and responds to fighter requests only.

Merge Flow

MERGED

The controller calls MERGED when radar tracks come together within 3–5 nm, or the engaged fighter calls it when visual contact is made.

Station	Phrase
Controller or Engaged Fighter	{CS} MERGED {Group Label}

IFF Calls

At the merge, positive visual identification of friend or foe is critical before employment. Standard IFF calls apply:

Term	Meaning
TALLY	Visual contact established on the target or bandit
NO JOY	No visual contact with the target or bandit
VISUAL	Visual contact established on a friendly aircraft
BLIND	No visual contact with a friendly aircraft

PRESS

The supporting fighter calls PRESS to indicate the requested action is approved and mutual support will be maintained. PRESS assumes VISUAL on the engaged fighter.

Station	Phrase
Engaged Fighter	(intraflight) {CS} PRESS
Supporting Fighter	(intraflight) PRESS

Employment

Station	Phrase
Engaged Fighter	{Controller-CS} {CS} FOX TWO {Target Description}
Controller	COPY SHOT

Gun employment is called as GUNS with target description.

SPLASH

Station	Phrase
Engaged Fighter	{Controller-CS} {CS} SPLASH {Group Label or Contact Description}
Controller	{CS} COPY SPLASH

Following SPLASH the flight disengages, calls RESET, and returns to its prebriefed position unless directed otherwise.