Appendix A — Multiservice Codes Applicable to Flight Test
◬ Codes most often misused are indicated with an warning symbol and include an explanation of how to avoid misuse.
Attention-Getting codes have significant potential for miscommunication. This is often because test aircrew and operators were trained in an operational context, whereas test and range personnel were trained in a test context. Because of the urgent nature of attention-getting codes, they must be carefully defined for each test and briefed carefully.
Attention-Getting Brevity Code |
Definition | Flight Test Context |
---|---|---|
ABORT | Directive call to cease action/attack/event/mission. | Per the comm plan, but typically used when test limits or boundaries have been or will be exceeded. Usually implies a briefed recovery procedure. |
(system) BENT/SICK | System indicated is inoperative/degraded | Describing system difficulties |
BINGO | Fuel state needed for recovery. | Briefed fuel state that triggers an automatic decision to terminate testing and RTB. |
BLIND | No visual contact with friendly aircraft/ground position. Opposite of VISUAL. |
Could be a test or a safety consideration. |
BOGEY | A radar or visual air contact whose identity is unknown. | An indication of “stranger traffic” that could interfere with test execution. |
DIVERT | Proceed to alternate mission/base. | Directing to alternate landing site for WX/MX/other |
JOKER◬ | Fuel state above BINGO at which separation/bugout/event termination should begin. | Briefed fuel state that indicates a decision point in the test flow. ◬Can have multiple jokers for various reasons (tanker, altitude block change, etc.) as determined by test team. |
KNOCK IT OFF | In training, a directive call to cease all air combat maneuvers/attacks/ activities/exercises. | In test, typically used to indicate a safety of flight concern, directing termination of testing and resumption of “normal” flight. Followed by discussion of cause and next action to be taken. |
NO FACTOR | Not a threat. | Declaring that an identified aircraft will not interfere with safety of flight or test. |
NO JOY◬ | Aircrew does not have visual contact with the target/bandit/landmark. Opposite of TALLY. |
◬Similar to BLIND, but BLIND is for friendlies; NO JOY is for everyone else. |
PADLOCKED | Informative call indicating aircrew cannot take eyes off an aircraft, ground target, or surface position without risk of losing TALLY/VISUAL. | Indicates aircrew is task saturated and channelized. |
(system) SOUR (mode) | Invalid/no response to an administrative IFF/SIF check. Opposite of SWEET. |
Systems testing. |
STRANGER | Unidentified traffic that is not a participant with the action in progress. | Traffic that could conflict with test execution or flight safety. |
TALLY | Sighting of a target, non-friendly aircraft, or enemy position. Opposite of NO JOY. |
Should cause a sigh of relief. |
TERMINATE◬ |
|
Often used to cease test point execution. In test, this means whatever the test team briefed it to mean, but the meaning is typically different from standard brevity code. ◬BE CAREFUL TO CLEARLY DEFINE USE WHEN FLIGHT TERMINATION SYSTEMS ARE EMPLOYED!!! |
TUMBLEWEED | Indicates
and is a request for information. |
HELP!! |
VISUAL | Sighting of a friendly aircraft or ground position. Opposite of BLIND. |
Could change required separations per the safety considerations. |
Informative Geometry codes communicate a general condition. They do not often have test-specific meanings, but test teams can make use of the test aircrew and operators prior training to provide clarity and reduce communication bandwidth.
Informative Geometry Brevity Code |
Definition |
---|---|
ANCHOR(ED) (location) |
|
FEET WET/DRY | Flying over water/land. |
IN (direction) |
|
MARSHAL(ING) | Establish(ed) at a specific point. |
OFF (direction) | Informative call indicating attack is terminated and maneuvering to the indicated direction. |
ON STATION | Informative call that unit/aircraft has reached assigned station. |
OUT (direction) | Informative call indicating a turn to a cold aspect relative to a known threat. |
PUSHING | Departing designated point. |
SADDLED | Informative call from wingman or element indicating the return to briefed formation position. |
STRIPPED | Informative call that aircraft is out of prebriefed formation. Opposite of SADDLED. |
WINGS LEVEL | Informative call from aircraft to FAC reporting rolled-out on final attack heading. |
Relative Geometry codes provide relationship between two air vehicles, both location and angles. They do not often have test-specific meanings, but test teams can make use of the test aircrew and operators prior training to provide clarity and reduce communication bandwidth.
Relative Geometry Brevity Code |
Definition |
---|---|
BEAM (cardinal direction) |
Contact stabilized within 70 to 110 degrees of aspect. |
BRAA |
|
BULLSEYE | An established reference point from which the position of an object can be referenced. Extremely important! Ensure that the BULLSEYE is briefed. Typically paired with a bearing and range. “Bullseye 050 at 50 miles.” Think polar coordinates with a briefed origin, instead of the Cartesian lat/long coordinates. |
CLOSING | Decreasing in separation. |
COLD |
|
DRAG (cardinal direction) |
Contact aspect stabilized at 0-60 degrees angle from tail or 120-180 degrees angle from nose. |
FLANK (cardinal direction) |
Contact aspect stabilized at 120 to 150 degrees angle from tail or 30 to 60 degrees angle from nose of aspect. |
HOT |
|
OPENING | Increasing in separation. |
STACK | Two or more contacts or formations with an altitude separation in relation to each other. |
“Picture” Geometry codes provide an overview of the tactical airspace. They do not often have test-specific meanings, but test teams can make use of the test aircrew and operators prior training to provide clarity and reduce communication bandwidth.
“Picture” Geometry Brevity Code |
Definition |
---|---|
PICTURE | A request to provide air information pertinent to the mission in a digital bullseye format. |
NEW PICTURE | Used by controller or aircrew when tactical picture has changed. Supersedes all previous calls and re-establishes picture for all players. |
CONTACT |
|
GROUP | Any number of air contacts within 3 NM in azimuth or range of each other. |
PACKAGE | Geographically isolated collection of GROUPs. |
ARM | Element resulting from target maneuvers exceeding GROUP criteria. |
2 Groups | |
AZIMUTH | A picture label describing two GROUPs separated laterally. |
ECHELON (direction) |
Picture label/fill-in describing two GROUPs with one group displaced behind and to the side of the other group. |
RANGE | A picture label describing two GROUPs separated in distance along the same line of bearing. |
3+ Groups | |
BOX | A picture label describing four distinct GROUPs with two in front and two behind in a square or offset square orientation. |
CHAMPAGNE | A picture label describing three distinct GROUPs with two in front and one behind. |
LADDER | A picture label describing three or more GROUPs separated in range. |
VIC | A picture label describing three GROUPs with a single group closest in range and two trail groups separated in azimuth. |
WALL | A picture label describing three or more GROUPs separated primarily in azimuth. |
Separation | |
DEEP | Descriptive term used to indicate separation between the nearest and farthest GROUPs in range in a relative formation, used to describe a LADDER, VIC, CHAMPAGNE, BOX. |
STACK | Two or more contacts or formations with an altitude separation in relation to each other. |
WEIGHTED (cardinal direction) |
(USN/USMC) Descriptive term used for a multiple GROUP formation (WALL, LADDER, VIC, CHAMPAGNE) that is offset in one direction. |
WIDE | Descriptive term used to indicate the separation between the farthest GROUPs in azimuth in a relative formation, use to describe a WALL, VIC, CHAMPAGNE, or BOX. |
Inner | |
CONTAINER | Inner GROUP formation with four contacts oriented in a square or offset square. |
LEAD-TRAIL | Inner GROUP formation of two contacts separated in range. |
LINE ABREAST | Inner GROUP formation of two or more contacts separated in azimuth. |
NEAR-FAR | (USAF) Fighter term depicting a radar-apparent description of two or more contacts within a GROUP separated in range. |
SIDE-SIDE | (USAF) Fighter term depicting a radar-apparent description of two or more contacts within a group separated in azimuth. |
STINGER | Three-ship inner group formation with two lead contacts line abreast and the single in trail. |
WEDGE | Three-ship inner group formation with a single contact closest in range and two trail contacts line abreast. |
Maneuvers | |
CROSSING | Descriptive term for when two GROUPs initially separated in azimuth decrease azimuth separation to pass each other. |
MANEUVER (AZIMUTH/RANGE/ALTITUDE) | Informative call that specified GROUP is maneuvering in azimuth, range, and/or altitude. |
MARSHAL(ING) | Establish(ed) at a specific point. |
MERGE(D) |
|
PASSING | Descriptive term for when two GROUPs initially separated in range, decrease range separation and pass each other. |
SWITCHED | Indicates an attacker is changing from one aircraft to another. |
TRACK (cardinal direction) | Group/contact’s direction of flight. |
Maneuver codes direct or describe single-ship maneuvers. They do not often have test-specific meanings, but test teams can make use of the test aircrew and operators prior training to provide clarity and reduce communication bandwidth.
Maneuver Brevity Code |
Definition |
---|---|
BANZAI | Informative/directive call to execute launch and decide tactics. Launch your missiles, then continue to the target. May end up as a merge. Not common in DT, but significant for OT tactics. Also, fun to say, with aerial combat overtones. |
BRACKET (direction) |
Directive call to maneuver to a position on opposing sides, either laterally or vertically from the target. |
BUSTER | Directive call to fly at maximum continuous speed (military power). |
CRANK (direction) |
F-Pole maneuver in the direction indicated; implies illuminating target at radar GIMBAL limits. |
EXTEND(ING) (direction) |
Short-term maneuver to gain energy, distance, or separation, normally with the intent of reengaging. |
GATE | Directive/informative call to fly as quickly as possible, using after-burner/max power. |
HOT |
|
JINK | Directive call to perform an unpredictable maneuver to negate a tracking solution. |
LEAN (direction) | Directive/informative call to maneuver in a direction to avoid the threat. |
NOTCH(ING) direction) |
Directive/informative call that an aircraft is in a defensive position and maneuvering with reference to an air-to-air threat. |
OFFSET (direction) | Directive/informative call indicating maneuver in a specified direction with reference to the target. |
PUMP | A briefed maneuver to minimize closure on the threat or geographical boundary with the intent to re-engage. |
SHORT SKATE | (USAF) Informative or directive call to execute launch-and-leave tactics and be out no later than MAR/DR. Launch your missiles, then turn away to fight another day prior to a briefed distance from the target. |
SKATE | Informative or directive call to execute launch-and-leave tactics. Launch your missiles, then turn away to fight another day. Turning at a distance closer than short skate to support your missile for longer. |
STERN | Request for, or directive to, intercept using STERN geometry. |
Turns | |
CHECK (number, LEFT/RIGHT) |
Turn (number) degrees left or right and maintain new heading. |
COMEOFF (direction) |
|
HARD (direction) | High-G, energy sustaining 180 degree turn (or as directed) in the indicated direction. |
HOOK (LEFT/RIGHT) | Directive call to perform an in-place 180 degree turn. |
IN PLACE (direction) | Perform indicated maneuver simultaneously. |
PITCH/PITCHBACK (LEFT/RIGHT) | Directive call for fighter or flight to execute a nose-high heading reversal. |
SLICE/SLICEBACK (LEFT/RIGHT) | Directive call to perform a high-G descending turn in the stated direction, usually 180 degree turn. |
Non-Engagement | |
FLOAT | Directive/informative call to expand the formation laterally within visual limits to maintain radar contact or prepare for a defensive response. |
FLOW (direction) | Directive call to fly stated heading. |
MARSHAL(ING) | Establish(ed) at a specific point. |
POP |
|
POST HOLE | Rapid descending spiral. |
SHACKLE | One weave, a single crossing of flight paths; maneuver to adjust or regain formation parameters. |
SPIN | Directive or informative call to execute a timing/spacing maneuver. |
SPLIT | Informative/directive call that flight member is leaving formation to pursue a separate attack; VISUAL may not be maintained. |
Request codes compress questions into single words. They do not often have test-specific meanings, but test teams can make use of the test aircrew and operators prior training to provide clarity and reduce communication bandwidth.
Request Brevity Code |
Definition |
---|---|
POSIT | Request for friendly position; response in terms of a geographic landmark or off a common reference point. |
STATUS |
|
WHAT LUCK | Request for results of missions or tasks. |
WORDS | Directive or interrogative call regarding further information or directives pertinent to the mission. |
Weapon codes are related to employment of munitions. They do not often have test-specific meanings, but test teams can make use of the test aircrew and operators prior training to provide clarity and reduce communication bandwidth.
Weapon Brevity Code |
Definition |
---|---|
(weapon) AWAY | Release/launch of specified weapon. |
FOX (number) | Simulated/actual launch of air-to-air weapons. ONE - semiactive radar-guided missile. TWO - infrared-guided missile. THREE - active radar-guided missile. |
GUNS | Reference to gun engagement. |
MILLER TIME |
|
PIG(S) | Friendly glide weapon (i.e., JSOW). |
RIFLE | Friendly air-to-surface missile launch. |
RIPPLE | Two or more munitions released or fired in close succession. |
SHOOTER | Aircraft/unit designated to employ ordnance. |
SHOTGUN | Briefed weapons state at which separation/bugout should begin. |
SPLASH(ED) |
|
TARGET |
|
TARGETED | Informative call that GROUP responsibility has been met. |
THUNDER | Informative call one minute prior to A/S weapons impact. |
WHAT STATE (item) | Request for amount of fuel and missiles remaining. Ammunition and oxygen are reported only when specifically requested or critical. (Active) = number of active radar missiles remaining. |
WINCHESTER | No ordnance remaining. |
HARM AGM-88 | |
ARIZONA | No ARM ordnance remaining. |
MAGNUM (system/location) | Launch of friendly antiradiation missile. |
SLAPSHOT (type/bearing) | Directive call for an aircraft to immediately employ a best available HARM against a specified threat at the specified bearing. |
SNIPER (type, location [range, bearing]) | Directive call for an aircraft to employ a range-known HARM against a specified threat at the specified location. |
WORKING |
|
AMRAAM AIM-120 | |
CHEAPSHOT | AIM-120 missile data link terminated between high and medium PRF active. |
FOX 3 (X) SHIP (formative description) | (USAF) Valid missile shot against (x) separate targets (assumes 1 missile per target). |
FOX THREE/ SECOND FOX 3 | (USAF) Simulated or actual launch of multiple active radar-guided missiles on the same target. |
HUSKY | Informative call that the AIM-120 is at HPRF active range. |
MADDOG | Visual AIM-120/AIM-54 launch. |
PITBULL |
|
SKOSH | Aircraft is out of/or unable to employ active radar missiles. |
RADAR/Sensor codes provide information about radio-frequency, optical, and infrared sensors, as well as lasers used for designation and ranging. They do not often have test-specific meanings, but test teams can make use of the test aircrew and operators prior training to provide clarity and reduce communication bandwidth.
RADAR/Sensor Brevity Code | Definition |
---|---|
BROKE LOCK | Advisory call regarding loss of radar/IR lock-on. |
BUDDY LOCK | Locked to a known friendly aircraft. Normally a response to a “SPIKED” or “BUDDY SPIKE” call. Usually for transit to/from range, but could be used during test. |
BUDDY SPIKE (posit/heading/alt) | Friendly aircraft air-to-air indication on radar warning receiver (RWR). Usually for transit to/from range, but could be used during test. |
CAPTURED | Aircrew has acquired and is able to track a specified air-to-ground (A/G) target with an on-board sensor. |
CLEAN |
|
DROP(PING) |
|
EMPTY | No emitters of interest detected. |
FADED | Radar contact is (temporarily) lost on nonfriendly air/surface contact and any positional information given is estimated. |
GADGET | Radar or emitter equipment. |
GIMBAL (direction) | Radar target is approaching azimuth or elevation limits. |
HIT(S) | 1 . Momentary radar return(s). 2. (A/A) Indicates approximate target altitude (e.g., GROUP BULLSEYE 360/10, HITS 15 thousand). 3. (A/G) Weapons impact within lethal distance. |
LASER ON | Directive call to start laser designation. |
LASING | Informative call indicating that the speaker is firing the laser. |
LOCKED |
|
MAPPING | Multifunction radar in an A/G mode. |
MARK |
|
MONITOR | Maintain radar awareness on specified group. |
MUD (type/direction) | Informative call Indicating RWR ground threat displayed. |
MUSIC | Radar electronic deceptive jamming. |
NAILS (direction) | RWR indication of AI radar in search. |
NAKED | No RWR indications. |
NEGATIVE CONTACT | Sensor information on a friendly aircraft is lost. Termination of CONTACT, track plotting is not warranted. |
RAYGUN (position/heading/altitude) | Indicating a radar lock-on to unknown aircraft. A request for a “BUDDY SPIKE” reply from friendly aircraft meeting these parameters. |
SHIFT (direction) | Directive call to shift laser illumination. |
SINGER (type/direction) | Informative call of RWR indication of SAM launch. |
SNAPLOCK (BRAA) | Indicates fighter has obtained a radar contact inside briefed threat range with beam, flank, or hot/head aspect. |
SNIFF (type) | Passive sensor indication of a radar emitter. |
SPARKLE |
|
SPIKE(D) (direction) | RWR indication of an AI threat in track or launch. |
SPOT | Acquisition of laser designation. |
STROBE(S) (bearing) | Radar indication(s) of noise jamming. |
TIED | Positive radar contact with element or aircraft. |
TOY | HTS pods. |
Avionics/Datalink codes describe communications, interrogations, identification, and datalink systems and their states. They do not often have test-specific meanings, but test teams can make use of the test aircrew and operators prior training to provide clarity and reduce communication bandwidth.
Avionics/Datalink Brevity Code |
Definition |
---|---|
(system) BENT | System indicated is inoperative. |
(system) SICK | System indicated is degraded/partially operative. |
(system) SILENT (time) | System will be unavailable for time indicated. |
(system) WELL | System indicated is fully operative. |
(system) SOUR (mode) | Invalid/no response to an administrative IFF/SIF check. Opposite of SWEET. |
(system) SWEET | Valid response to an administrative IFF/SIF check request. Opposite of SOUR. |
Systems | |
GADGET | Radar or emitter equipment. |
PARROT | IFF/SIF transponder. |
TIMBER | Air control NPG of Link 16/TADIL J. Datalink testing, especially “TIMBER SWEET” or “TIMBER SOUR” |
TOY | HTS pods. |
UNIFORM | UHF radio. |
VICTOR | VHF radio. |
PRIME/PRI | Primary radio frequency. UHF if UHF/VHF. UHF1 if UHF1/UHF2. |
AUX | Auxiliary radio frequency. VHF if UHF/VHF. UHF2 if UHF1/UHF2 |
Directives | |
FENCE (IN/OUT) | Set cockpit switches as appropriate before entering/exiting the combat area. |
FLASH (system) | Temporarily activate specified system for identification purposes (IFF/afterburner/flare/chaff/etc.). |
INTERROGATE | Interrogate the designated contact of the IFF mode indicated. |
SQUAWK (mode/code) | Operate IFF/SIF as indicated or IFF/SIF is operating as indicated. |
SQUAWKING (mode #) | An informative/descriptive call denoting a BOGEY is responding with an IFF/SIF mode or code other than that prescribed by the ATO/identification criteria. |
STRANGLE (system) | Turn off equipment indicated. Example: “STRANGLE PARROT” |
TOGGLE | Execute a briefed change of an avionics setting. |
ZAP | Request for data link information. |
Clearance codes have significant potential for miscommunication. This is because there are phases of test execution when a third-party is primarily responsible for clearance (often critical phases such as engine start, taxiing, takeoff, departure, aerial refueling, approach, and landing). There are other phases of test execution where the test team must decide and clarify who is responsible for clearance. The specifics of the test point should be the primary consideration, including how static or dynamic the point is.
Clearance Brevity Code |
Definition | Flight Test Context |
---|---|---|
CLEAR(ED)◬ | Response to requested action is authorized. No engaged/support roles are assumed. | Test point pacing ONLY. DO NOT SAY “CLEARED” WHEN A/C IS ABOUT TO TAXI, TAKE THE RUNWAY, OR LAND. The “cleared” word is reserved in those situations for the controlling agency (ground, tower, etc.). Don’t get your aircrew violated because they acted without clearance from the controlling agency! |
CLEARED HOT◬ | Ordnance release is authorized. | NOT FOR THE TEST CONDUCTOR TO SAY! Range control has the hammer. |
CONTINUE | Continue present maneuver, does not imply a change in clearance to engage or expend ordnance. | VERY USEFUL. By replying to an aircrew query with “CONTINUE”, you are indicating that you are aware of the situation, you’ve taken it into consideration, and they can safely, securely, effectively, and efficiently proceed with the current course of action. |
CONTINUE DRY | Ordnance release not authorized. | NOT FOR YOU TO SAY! |
PRESS◬ | Directive call to continue the attack; mutual support will be maintained. Supportive role will be assumed by the speaker. | Not typically used in flight test conduct, but a very common term in informal settings. |
PUSH (channel) | Go to designated frequency; no acknowledgment required. | Not for you to say, but the flight lead is directing the flight to change frequencies, so follow along. |
RESET | Proceed to a pre-briefed position or AO. | Start over, per the brief. |
RESUME | Resume last formation/route/mission ordered. If test point was paused, resume at last step. | |
ROGER◬ | Indicates the receipt of radio transmission; does not indicate compliance or reaction. | One of the more abused brevity codes. Only indicates that you heard, nothing more. “ROGER, COPY” is redundant, as is “ROGER, WILCO.” |
ROLEX (+/- Time) | Time line adjustment in minutes always referenced from original preplanned mission execution time. Plus means later; minus means earlier. | Often used when delays have offset brief mission times. |
SAUNTER | Fly at best endurance. | Used when test is on hold. |
SKIP IT | Veto of fighter COMMIT, usually followed with further directions. | Used to veto aircrew suggestion or to tell aircrew NOT TO PICKLE. |
UNABLE | Cannot comply as requested or directed. | Used to indicate inability to comply. |
WEAPONS ( )
|
Fire only:
|
Weapons testing. |
Flight Condition codes provide low-fidelity generalizations of altitude and airspeed. They can be very useful when tight tolerances and databands are not required, but a general condition is desired. They do not often have test-specific meanings, but test teams can make use of the test aircrew and operators prior training to provide clarity and reduce communication bandwidth.
Flight Condition Brevity Code |
Definition |
---|---|
VERY FAST | Target speed greater than 900 knots ground speed or Mach 1.5. |
FAST | Target speed is estimated to be 600 – 900 knots ground speed or Mach 1.0 – 1.5 . |
SLOW | Contact with ground speed of less than 300 knots. |
VERY HIGH | Target above 40,000 ft MSL. |
HIGH | Contact is between 25,000 and 40,000 ft MSL. |
MEDIUM | Contact altitude between 10,000 ft MSL and 25,000 ft MSL. |
LOW | Contact altitude below 10,000 ft MSL. |
WEEDS | Indicates that aircraft are operating close to the surface. |
Rules of Engagement (ROE) & Identification (ID) codes provide characterizations of the friend/foe status, as well as free/restrained weapons engagements can be. They do not often have test-specific meanings, but test teams can make use of the test aircrew and operators prior training to provide clarity and reduce communication bandwidth.
ROE & ID Brevity Code |
Definition |
---|---|
Discussion | |
DECLARE | Inquiry as to the identification of a specified track(s), target(s), or correlated GROUP. |
ID |
|
Descriptions | |
BANDIT | An aircraft identified as an enemy in accordance with (IAW) theater ID criteria. The term does not necessarily imply direction or authority to engage. |
BOGEY | A radar or visual air contact whose identity is unknown. |
CHICKS | Friendly aircraft, typically used for aircraft on the tanker. |
FRIENDLY | A positively identified friendly aircraft, ship, or ground position. |
HOSTILE | A contact identified as enemy upon which clearance to fire is authorized in accordance with theater rules of engagement. |
OUTLAW | Informative call that a BOGEY has met point of origin criteria for ROE. Point of Origin means that the contact came from a geographic location identified as hostile. |
PAINT(S) | An interrogated group/radar contact that is responding with any of the specified IFF/SIF modes and correct codes established for the ID criteria. |
PRINT (type) | Active NCTR reply. |
SPADES | An interrogated group/radar contact which lacks all of the ATO (or equivalent) IFF/SIF modes and codes required for the ID criteria. |