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.

Communication Fundamentals

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

Group

• A GROUP is any number of air CONTACTs within 3 nautical miles (nm) in azimuth and range of each other.
  • CONTACT is an individual radar return within a GROUP.
  • SINGLE CONTACT is the assumed STRENGTH for all GROUPs. More CONTACTs are specified (e.g., SINGLE GROUP TWO CONTACTs).
• GROUPs are distinguished by either a unique name or unique position. There are four unique naming conventions used:
  • Cardinal Relationship (e.g., NORTH GROUP, SOUTH GROUP).
  • Range Relationship. Relationship relative to a specific aircraft perspective (e.g. LEAD GROUP, TRAIL GROUP).
  • Combined Cardinal and Range Relationship (e.g., NORTH LEAD GROUP).
  • Descriptive Name (e.g., SINGLE GROUP, ADDITIONAL GROUP, POPUP GROUP).
• Unique Position Reference. GROUPs can be distinguished using unique position names such as BULLSEYE, BRAA, or geographic reference (GEOREF).

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.

Core Information Format

• Controllers and air assets will use the core information format to communicate GROUPs:
• Total Number of GROUPs.
• GROUP Location (i.e., BULLSEYE, BRAA, or GEOREF).
• Altitude (rounded to the nearest thousands of feet).
• Track direction or specific aspect (e.g., cardinal/sub-cardinal or HOT/FLANK/BEAM/DRAG).
• Declaration.
• Fill-ins (as appropriate).

GROUP Location

• BULLSEYE (primary method to communicate the GROUP location).
  • BULLSEYE is an established reference point from which the position of an object can be referred to by bearing (magnetic) and range (nm).
  • BULLSEYE information is rounded to the nearest degree and nm.
    • For example, BULLSEYE 225/30 means 30 nm on a magnetic bearing of 225 degrees from the BULLSEYE location.
    • It is communicated “two-two-five thirty”.
    • If an aircraft is within 5 nm of BULLSEYE, controllers may describe the GROUP as AT BULLSEYE unless that GROUP is to be targeted.
  • Use the code name for BULLSEYE when directed by SPINS.
  • BULLSEYE will not be truncated to “bull” to avoid it being misinterpreted as “BRAA”.
• Bearing Range Altitude and Aspect (BRAA).
  • BRAA information for bearing and range are rounded to the nearest degree and nm.
  • 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”.
  • 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.
  • Controllers will also use the BRAA format when providing a THREAT call to an aircraft.
• GEOREF Point.
  • The controller may use a GEOREF to provide the approximate location of a GROUP.
  • Examples of GEOREFs may be a prominent natural feature, such as a mountain peak, or a prominent manmade structure, such as an airfield.

GROUP AT BULLSEYE Example
“SHOWTIME 11, LEAD GROUP, AT BULLSEYE, THIRTY-NINE THOUSAND, TRACK NORTH, HOSTILE.”

BULLSEYE Code Name Example
BULLSEYE Code Name: ROCK.
“MIKE, SOUTH GROUP, ROCK 255/29, THIRTY-NINE THOUSAND, CAP, HOSTILE.”

THREAT Call Example
“SHOWTIME 11, LEAD GROUP, THREAT BRAA 270/55, THIRTY-NINE THOUSAND, FLANK NORTHEAST, HOSTILE.”

Geographic Reference Example
Prominent Enemy Airfield Code Name: DEPOT.
“SHOWTIME 11, LEAD GROUP, AT DEPOT, THIRTY-NINE THOUSAND, CAP, HOSTILE.”

GROUP Altitude

• Fighters and controllers will round altitudes to the nearest thousand feet indicated on their system.
• 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.
• Controllers will omit altitude from the communication format if the controlling platform is not capable of generating an altitude.
• Altitude STACKS.
  • 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.
  • 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.

Altitude Stack Example
“SHOWTIME 11, NORTH GROUP BRAA 300/32, STACK THIRTY-TWO THOUSAND AND EIGHT THOUSAND, HOT, HOSTILE, TWO CONTACTS, FLANKER.”

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.”

Track Direction and Specific Aspect

• 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).
• PICTURE Exception.
  • 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.
  • If amplifying the PICTURE with TRACK direction, controllers should not provide a track direction for every GROUP in the picture.
• 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.
  • Specific aspects (i.e., HOT, FLANK, BEAM, and DRAG) are determined by the GROUP target aspect (TA) or aspect angle (AA) to the fighter.
  • FLANK, BEAM, DRAG are accompanied with a cardinal/sub-cardinal direction (e.g., DRAG WEST).
• MANEUVER Description (TRACK Direction or Specific Aspects).
• Controllers may use “maneuver hot” to communicate groups/contacts that have maneuvered toward the fight axis.
• 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.

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.”

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.”

FIGURE "Aspect Angle"

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

 

Declaration

Fill-in Information

Picture

Anchoring a PICTURE

Core Information Concerning a PICTURE

Traditional Labels for a PICTURE

Amplifying a Traditional Label for a PICTURE