78th VMRS/STANDART CREW CONTRACTS

PREFACE

1. Purpose

This contract establishes the standard crew agreements assumed by every 78th F-16 flight. It governs flight organization, admin parameters, communications, airspace sanitization, task priority, mutual support, and engagement contracts.

2. Scope

a. This contract applies to all 78th F-16 aircrew for every sortie, in training and in combat.

b. This contract governs crew agreements only. It does not restate tactical doctrine. Refer to the BVR pages for beyond visual range (BVR) employment doctrine, to the Formation Flying Contracts (FFC) for all formation matters, and to the 476TTP Threat Guide for threat reactions.

3. Applicability

a. Every item in this contract applies unless a deviation is briefed for that mission.

b. The Flight Lead (FL), the Squadron Lead, or the Wing Lead may propose a deviation. The Combined Air Operations Centre (CAOC) approves the flight briefing, and that approval covers every deviation the briefing contains.

a. No item is exempt. The FL may brief away any standard in this contract, including safety standards.

Note: This authority exists so that no standard can prevent the FL from ensuring safety of flight.

b. The FL will brief each deviation explicitly. Any item not briefed as a deviation applies as written.

c. A deviation applies to one mission only. Changing this contract is an amendment, not a deviation, and follows Section 15.

d. Items marked BRIEFED EVERY MISSION have no standing default and are collected in Section 13. The FL will brief every one of them.

4. Modal Verbs

Table 1 defines the obligation carried by each modal verb used in this contract.

Table 1. Modal Verbs
Verb	Obligation
must	Mandatory. Non-negotiable. Reserved for safety-of-flight, deconfliction, and life-critical items.
will	Standard procedure. The stated action is what the actor does as a matter of course.
should	Recommended practice. The actor retains judgement.
may	Permitted. Not doing it is equally compliant.

5. User Information

Recommended changes should be keyed to the specific section and paragraph, with a rationale, and submitted to the Squadron Lead.

SUMMARY OF CHANGES

This edition hands formation matters to the Formation Flying Contracts (FFC), which is the sole authority on them. The FFC governs wherever the two documents addressed the same subject.

Removed. Established in the FFC:

Taxi (was 2.2) — FFC 2.4.
Departure parameters and the Last Chance Departure Briefing (was 2.3) — FFC Sections 2, 3, and 11.
Formation departure (was 2.4) — FFC Section 3.
Departure and join-up separation (was 2.5, Table 6) — FFC 3.6, 3.7, and 3.8.
Ground calls: taxi, last chance ready, lineup, brakes set, spool-up, takeoff roll (was 2.6) — FFC Sections 2 and 3.
Recovery and the overhead break (was 2.7) — FFC Section 10.
Admin formation and fingertip bank limit (was 3.2) — FFC Section 4.
Rejoin criteria (was 3.3) — FFC Section 7.
Chase procedure (was 3.4) — FFC Section 7.
Ops checks (was 5.2) — FFC 1.7.
Check-in on intraflight (was 6.2) — FFC 2.2.
Frequency changes (was 6.3) — FFC 1.8.

Structural:

Section 2 reduced to ramp system checks (2.1) and runway sides (2.2).
Section 3 reduced to cruise parameters (3.1, 3.2) and the formation ownership statement (3.3).
Section 5 paragraphs renumbered: 5.3 to 5.6 become 5.2 to 5.5.
Section 6 paragraphs renumbered: 6.4 and 6.5 become 6.2 and 6.3.
Tables renumbered 1 to 15 in one sequence. Three duplicate table numbers and identifiers corrected: two Table 6, two Table 7, and two Table 8.
SEAD paragraph anchors corrected. References to a non-existent 11.4 repointed to 11.2.4.
Section 13 relettered after departure parameters and formation selection moved to FFC Section 11.
Every reference to "the FFC document" replaced with a specific FFC paragraph.

Previous edition added:

Modal verb register (Table 1).
Paragraph numbering throughout.
Purpose statement for each section.
UNABLE SHOT contract (10.5).
RESET as a sanitization resume mechanism (7.3).
Required jettison at minimum fuel (12.6).
Ground abort ten-minute decision (12.3).
Safe airspace point as a briefed item (11.3, Section 13).
Airfield Operations section: ramp system checks, taxi, departure parameters, and recovery (Section 2).
ACM entry trigger at 10 NM to the nearest GROUP (10.7).
Air-to-air threat calls separated from ground threat calls (10.15, 11.2.4).
Ground radio failure procedure (12.2).
Airspace Sanitization Radar Setting Specifications
Airfield Operations Calls
WAMOE A2G Pre-employment Checks
Targeting Contracts

Updates:

BINGO redefined with return to base (RTB) or tanker return as valid responses. A single BINGO pilot may be sent to abort.
Default Offensive and Engaged Fighter changed from #1 to #2.
Launch-and-leave is the default at any force ratio; launch-and-decide requires a BANZAI call.
Departure parameters expanded.
Supporting Fighter weapons employment restricted; shot of opportunity removed.
Radio allocation test changed to effect outside the flight.
Congestion call from COMMS IN -> COMMS TACTICAL / COMMS FREE

Removes:

Terrain floors as standing values (now BRIEFED EVERY MISSION).
SEAD standing principle (doctrine, not contract).
OUT from the SEAD post-defensive egress sequence.

SECTION 1 — FLIGHT ORGANIZATION

This section establishes flight composition, crew responsibilities, lookout priorities, split contracts, and succession.

1.1 Positions

Table 2. Flight Positions
Position	Role
#1	Flight Lead (FL)
#2	FL's wingman
#3	Element Lead (EL)
#4	EL's wingman

1.2 Flight Leadership

a. The FL will plan and organize the mission, lead the flight, delegate tasks within it, and know the capabilities and limitations of each flight member.

b. Once airborne, the FL holds final responsibility and controlling authority for establishing formations and leading the flight to and from the target.

c. Wingmen will maintain visual lookout and radar responsibilities and perform back-up navigation. A wingman engages as briefed or when directed, and supports when the lead engages (Section 10).

1.3 Responsibilities

The FL assigns responsibilities so that each pilot carries a manageable number of tasks. Absent a briefed alternative, responsibilities are:

a. #1 (FL). Primary planner and decision maker. Primary navigation. Primary radar lookout. Visual lookout covering #2.

b. #2 (wingman). Maintain formation position. Visual lookout covering #1. Navigation position awareness and radar awareness as other tasks allow.

c. #3 (EL). Secondary planner and alternate decision maker. Maintain the second element's position relative to the lead element. Secondary navigation and radar monitor. Visual lookout covering #4 and the flight as a whole.

d. #4 (wingman). Maintain formation position. Visual lookout for the flight. Navigation position awareness and radar awareness as other tasks allow.

Note: The pairing of an offensive and a supporting fighter, and the calls that transfer those roles, are established in Section 10.

1.4 Lookout Priorities

a. From FENCE IN to FENCE OUT, each pilot will search the sectors in Table 3 in priority order. The sectors are described from the perspective of #2 in a four-ship. The same priority order applies to every position.

Table 3. Lookout Sectors
Priority	Sector	Content
1	NEAR ROCKS	Terrain affecting the flight path within the next 10 to 15 seconds. The hub of the cross-check and the highest priority.
1A	FAR ROCKS	Terrain affecting future manoeuvring.
2	Inside the flight, six o'clock	Own formation position and the lead's six o'clock.
3	Inside the flight, ahead of the 3/9 line	Bandits in a conversion and surface-to-air missiles fired from the front quadrant.
4	Outside the flight, ahead and behind the 3/9 line	Lowest priority. 360-degree coverage.

b. Sectors 1, 1A, and 2 form the basic cross-check: NEAR ROCKS, FAR ROCKS, CHECK SIX.

c. Each pilot must check sectors 1 and 1A on every search cycle.

d. Sectors 2, 3, and 4 are searched as task saturation allows, in that order (Section 8).

1.5 Crew Assignment

a. In mission planning, before the brief, the FL assigns pilots to positions at his discretion. The percentage recorded on the Training Overview page is guidance, not a rule.

b. The guidance order, most experienced first, is #1, #3, #4, #2.

Note: #4 sits ahead of #2 in this order. The FL's own wingman is the least-experienced position.

1.6 Flight Size

a. Four-ship is the standard structure.

b. Three-ship is flown as a four-ship with #4 absent. #3 flies as an element of one. Whether to continue with #3 unsupported is FL discretion.

c. Two-ship is flown as a single element. The same considerations apply as within either element of a four-ship.

d. More than four is split into separate flights: five as a three-ship and a two-ship, six as a four-ship and a two-ship, and so on.

1.7 Splits

a. Split contracts apply to any phase of flight.

b. Individual split. A wingman splitting from his element.

(1) Where the wingman's assigned task cannot be completed while holding formation, the wingman will request a split.

(2) The wingman must not split without clearance.

Individual Split

2:  2, REQUEST SPLIT, <reason>
1:  2, CLEARED SPLIT

or

1:  2, NEGATIVE

(3) On CLEARED SPLIT, the wingman may leave formation to execute the task. On NEGATIVE, the wingman must hold formation.

c. Element split. A four-ship dividing into its two elements.

(1) An element split follows an element-wise task assignment from the FL: element-wise targeting (10.3), the initiation of a GRIND, or an equivalent directive.

(2) An element split is never requested. The assignment itself is the clearance.

Element Split

1:  FIRST ELEMENT, DO X; SECOND ELEMENT, DO Y

(3) Any other element-split condition is BRIEFED EVERY MISSION.

1.8 Succession

a. On loss or abort of the FL, command passes to #3.

b. If both #1 and #3 are lost:

(1) The remaining aircraft must egress and return to base as soon as possible.

(2) #4 assumes navigation lead only and holds no tactical lead responsibility.

(3) #4 must lead the remaining aircraft out of the area of operations and home.

(4) #4 must advise the controlling authority that the flight is an emergency and without a flight lead.

SECTION 2 — AIRFIELD OPERATIONS

This section establishes ramp system checks and runway side discipline. Taxi, departure, ground calls, and recovery are established in the FFC.

2.1 System Checks

a. At the ramp, before taxi, each pilot will complete the checks in Table 4.

Table 4. Ramp System Checks
#	Item	Action
1	FCR	Combined radar mode; move cursor through full travel
2	HTS	Move cursor on all axes
3	TGP	Move on all axes
4	HMD	On; check alignment
5	Datalink	Check flight members displayed as blue dots
6	FLCS	Wipe check, full travel all axes

Legend: FCR — fire control radar; FLCS — flight control system; HMD — helmet-mounted display; HTS — HARM Targeting System; TGP — targeting pod.

b. Each pilot must report a failed check to the lead immediately.

c. System checks forming part of the startup checklist are assumed complete on startup.

2.2 Runway Sides

a. The cold side is the side on which the flight vacates the runway. The hot side is the opposite side.

b. Aircraft on the ground must hold on the cold side.

c. Aircraft must not cross to the cold side without clearance.

Note: Taxi is established in FFC 2.4, ground calls in FFC Sections 2 and 3, departure in FFC Section 3, and recovery in FFC Section 10.

SECTION 3 — ADMIN FLIGHT PARAMETERS

This section establishes cruise parameters for phases outside the vulnerability (VUL) window.

3.1 Application

a. Admin flight parameters apply outside the VUL window (i.e., before FENCE IN and after FENCE OUT).

b. FENCE IN and FENCE OUT timing is established in 4.1.

c. The FL may brief a different switch condition.

3.2 Parameters

a. Cruise speed below FL100 is 300kt CAS.

b. Cruise speed the above FL100 is 350 kt CAS.

c. Cruise speed inside VUL is M0.8

Legend: CAS — calibrated airspeed.

3.3 Formation

All formation contracts (types, parameters, turn execution, bank limits, element split criteria, and rejoin criteria and geometry) are established in the FFC, which is the sole authority on formation matters. Formation selection is BRIEFED EVERY MISSION.

SECTION 4 — FENCE

This section establishes the FENCE IN and FENCE OUT checklists, their timing, and the associated calls.

4.1 Timing

a. The FL calls FENCE IN at or before MARSHAL and shortly before VUL.

b. The FL calls FENCE OUT as soon as practical after leaving the VUL window.

c. On either call, each pilot will complete the checklist for the called direction.

d. The checklist may be executed from memory.

4.2 Calls

a. The FL directs. Each wingman acknowledges in flight order.

FENCE Directive

1:  FLIGHT FENCE IN
2:  2
3:  3
4:  4

b. Each wingman will not report completion.

4.3 FENCE IN Checklist

Table 5. FENCE IN
#	Item	Action
1	Lights	As required (master off or as briefed)
2	AVTR / DVR	As required
3	COMM, MSL, and RWR volume	As desired
4	ECM	As briefed
5	Stores Config switch	CAT I or CAT III as required
6	Master Arm	ARM
7	RWR	On, or as desired
8	Master Mode	As desired
9	Radar	FCR, mode as required
10	CMDS	Program and mode as briefed
11	IFF	Set IAW the mission card
12	Fuel	Check state; announce
13	SMS	Confirm weapon settings
14	TACAN	As required

Legend: AVTR — airborne video tape recorder; CMDS — countermeasures dispenser system; DVR — digital video recorder; ECM — electronic countermeasures; FCR — fire control radar; IAW — in accordance with; IFF — identification friend or foe; MSL — missile; RWR — radar warning receiver; SMS — stores management system.

4.4 FENCE OUT Checklist

Table 6. FENCE OUT
#	Item	Action
1	Master Arm	SAFE
2	ECM	Off, or as required
3	Radar	As required
4	Lights	As required
5	IFF	STBY, or as required
6	CMDS	Safe as required

4.5 Notes

a. Master Arm set to ARM does not authorise weapons release. Rules of engagement and engagement authority still apply.

b. CAT I is air-to-air stores only. CAT III is air-to-ground stores or wing tanks.

SECTION 5 — FUEL AND WEAPON STATES

This section establishes fuel and weapon state definitions, reporting requirements, and the actions triggered by reaching each state.

5.1 Afterburner Floor

Each pilot must not select afterburner below 2,000 lbs total fuel or BINGO, whichever is higher.

5.2 Reporting Fuel State

a. Each pilot will report fuel state on reaching JOKER, on reaching BINGO, on a request from the FL, and at FENCE completion (Section 4).

b. Reporting at JOKER and BINGO is unprompted.

c. Fuel state is passed in thousands of pounds to one decimal place. 10,400 lbs is called "TEN POINT FOUR."

5.3 BINGO

a. On reaching BINGO, the pilot must await the FL's direction. The pilot must not commence RTB or a tanker return unprompted.

b. The FL will declare and instruct either RTB or a return to tankers as soon as practical after a BINGO report.

c. The FL may send a single BINGO pilot to abort while the remainder of the flight continues.

5.4 Reporting Weapon State

a. Each pilot will call every weapon employment with the appropriate brevity.

b. The FL will track the flight's remaining stores.

c. On reaching a briefed threshold, the FL will call WEAPONS YELLOW or WEAPONS RED on TACTICAL.

5.5 Thresholds

a. Default BINGO is 2,000 lbs.

b. The FL computes JOKER and the weapon-state (green, yellow, red) thresholds from that sortie's loadout and fuel plan and briefs them EVERY MISSION, together with any BINGO deviating from the default.

SECTION 6 — COMMUNICATIONS

This section establishes radio allocation, check-in, frequency changes, and comms discipline.

6.1 Radio Allocation

a. Throughout the sortie, each pilot will monitor at least two frequencies.

Table 7. Radio Allocation
Radio	Assignment
Primary	Current controlling authority
Auxiliary	Intraflight

b. A call that has no effect on anyone outside the flight is made on intraflight. Every other call is made on primary.

c. TACTICAL is the frequency of the Airborne Battle Manager (ABM). Before entering VUL, the current authority hands the flight over to Tactical Command and Control (TACC2) acting as ABM. That frequency is TACTICAL.

Note: Calls specified in this contract as "on TACTICAL" are made on primary to the ABM.

6.2 Congested Comms

a. The FL restricts the frequency by calling:

Comms Restriction

1:  COMMS IN
2:  2
3:  3
4:  4

b. While in force, each pilot will restrict transmissions to necessary tactical calls.

c. The restriction ends when the flight leaves the ABM's frequency or when COMMS FREE is called, whichever occurs first.

6.3 Channelisation

Channel assignments are BRIEFED EVERY MISSION and published on the mission data card. No fixed channel-to-agency convention exists.

Note: Never assume a channel from memory.

SECTION 7 — AIRSPACE SANITIZATION AND DATALINK

This section establishes radar and datalink setup for sanitization, the period during which sanitization applies, and the calls that suspend and resume it.

7.1 Application

a. Sanitization begins at FENCE IN and runs until FENCE OUT, except while suspended (7.3).

Note: The offensive and supporting fighter contracts (Section 10) take effect at the same point.

7.2 Setup

a. Each pilot must have the settings in Table 8 set at FENCE IN.

Table 8. Sanitization Setup
Item	Setting
FCR	CRM; 80 NM Deep, 60° Wide
HSD	On, centred, 80 NM

Legend: HSD — horizontal situation display. FCR - Fire Control Radar. CRM - Combined Radar Mode

b. Each pilot will set radar antenna elevation so that coverage splits at ANGELS 20 within his element:

(1) Element lead. Place the cursor at 40 NM (centre of screen), then raise elevation until the lower boundary sits at ANGELS 20. The element lead scans above ANGELS 20.

(2) Element wingman. Place the cursor at 40 NM (centre of screen), then lower elevation until the upper boundary reads ANGELS 20. The element wingman scans below ANGELS 20.

c. Both elements set up identically.

7.3 Suspending and Resuming Sanitization

a. Sanitization is suspended by a MELD call from the FL, or by a SNAPLOCK call from any flight member.

b. Sanitization is resumed by a DROPPING call from the fighter concerned, or by a RESET call from the FL.

7.4 Calls

Table 9. Sanitization Calls
Call	Meaning	Who may call
MELD	Shift radar responsibilities from sanitizing to gaining situational awareness on the assigned GROUP.	FL only
SNAPLOCK	The fighter has a radar contact inside briefed threat range at BEAM, FLANK, or HOT aspect and cannot complete sanitization responsibilities. Implies ownership.	Any flight member
DROPPING	Stop monitoring the specified emitter, target, or GROUP and resume search responsibilities.	Any flight member
RESET	Return to the prebriefed position and resume sanitization.	FL only

a. A SNAPLOCK will be answered with BRAA.

b. SNAPLOCK and DROPPING will reference a specific GROUP or contact.

Note: SORT, SORTED, GIMBALS, SPLIT, JUDY, and RESET are established on the BVR pages and apply as written.

7.5 Datalink

a. F-16 datalink is the tactical network datalink (TNDL), configured in the data cartridge before the mission.

b. Datalink function is checked at the ramp (2.1).

c. Each pilot will report datalink information affecting the flight, including loss of datalink and contacts visible only on datalink.

SECTION 8 — CREW RESOURCE MANAGEMENT

This section establishes task priority, the UNABLE call, and the response to it.

8.1 Task Priority

Tasks are prioritised CRITICAL, then FORMATION, then MISSION.

Note: If a flight member and his wingman do not return to the airfield, the mission has failed regardless of objective completion.

8.2 Critical Tasks

In order:

a. Maintain positive control of the aircraft.

b. Terrain avoidance.

c. Mid-air avoidance of other flight members.

d. Mid-air avoidance of other aircraft.

e. Monitor and maintain sufficient fuel.

f. Threat awareness, detection, and defence.

Note: The ground has a probability of kill of almost 100 percent.

8.3 Formation Tasks

In order:

a. Remain IPOC (in position or correcting).

b. Uphold lookout responsibilities.

c. Respond to requests from the lead.

d. Self-reports: fuel and weapon states, DIRT, MUD, SINGER, NAILS, SPIKED, missile launch, datalink information, and pop-up contacts.

Note: Which threat calls are mandatory and which are optional is established in 10.15 (air-to-air) and 11.2.4 (ground).

8.4 Mission Tasks

In order:

a. Targeting.

b. Tactical execution (the BVR timeline and equivalent).

c. System configuration and stores management.

8.5 Continuous Checks

a. Critical and most formation tasks are never complete. Each pilot will check them continuously, not once.

b. Where a task is unsatisfied, each pilot must satisfy every higher-priority task in its category before addressing it.

8.6 UNABLE

a. Where a directive would interfere with a higher-priority task, the flight member must reject it.

b. Where a directive is not executable for any other reason, the flight member will reject it using the same call, stating the reason.

UNABLE

<number> UNABLE

8.7 Response to UNABLE

a. On an UNABLE call, the FL determines which level of task that member can still meet.

b. The FL may apply Table 10.

Table 10. Response to UNABLE
Member cannot meet	FL action
Critical tasks	Take over mutual support and ensure safe egress.
Formation tasks	Take over mutual support, abort the attack or engagement, and regroup.
Mission tasks	Reduce that member's load to preserve mission success: formation changes, reassigning targets, taking over mutual support, minimising requests to that member, or aborting the attack and regrouping.

Critical Task Response

Example, where #2 can no longer meet critical tasks:

1:  2 OFFENSIVE, 1 SUPPORTING, 2 HARD RIGHT, EGRESS EAST

SECTION 9 — MUTUAL SUPPORT

This section establishes the offensive and supporting fighter roles, their triggers by phase, and the calls that assign and transfer them.

9.1 Roles

a. One fighter acts. The other supports.

b. The acting fighter is the Offensive Fighter in general and in air-to-ground (A/G), and the Engaged Fighter in air combat manoeuvring (ACM). The other is the Supporting Fighter.

c. Offensive and Engaged Fighter. The fighter in a vulnerable or low situational awareness position: turning in a within visual range fight, defending a surface-to-air missile threat, or prosecuting a ground target. The primary objective is to survive. Weapons employment is secondary.

d. Supporting Fighter. The fighter that is not vulnerable, or is less so.

9.2 Supporting Fighter Obligations

a. The Supporting Fighter must maintain deconfliction from the Offensive or Engaged Fighter.

b. The Supporting Fighter must communicate threats to him.

c. The Supporting Fighter may maintain situational awareness beyond these two obligations.

d. The Supporting Fighter must not employ weapons except when directed by the FL, or in ACM when the Engaged Fighter's status is NEUTRAL or DEFENSIVE (10.7).

Note: This restriction applies only while mutual support roles are in force (ACM and A/G). It does not apply in BVR, where these roles do not exist.

9.3 Default

2 is the Offensive or Engaged Fighter by default.

Note: The FL is assumed to hold the better situational awareness and supports the wingman.

9.4 Triggers by Phase

Table 11. Mutual Support Roles by Phase
Phase	Role name	Trigger
ACM	Engaged Fighter	Self-declared: SPIKED (radar in track mode), or an adversary leaning on the fighter, or both.
A/G	Offensive Fighter	Assigned by the FL only, on passing the initial point (IP) for a ground attack. A wingman does not self-declare OFFENSIVE.
BVR	Not applicable	Mutual support roles do not exist in BVR. Mutual support is provided instead by the lookout priorities (1.4) and airspace sanitization (Section 7) contracts. Roles take effect at 10 NM to the nearest GROUP, as ACM (10.7).

9.5 Calls

a. The fighter declaring the role will make the call. The other fighter will respond.

ACM Role Declaration

2:  2 ENGAGED
1:  PRESS

A/G Role Declaration

1:  1 OFFENSIVE
2:  2 SUPPORTING

Where the FL directs the wingman to take the Offensive role:

A/G Directed Role Declaration

1:  2 GO OFFENSIVE
2:  OFFENSIVE
1:  1 SUPPORTING

9.6 Directed Assignment

a. Applies in ACM only.

b. The FL may direct the Engaged role onto his wingman.

Directed Assignment

1:  2 PRESS
2:  2 ENGAGED

c. No fighter other than the FL may push the Engaged role onto another fighter.

Note: The A/G Offensive role is FL-assigned, so no directed-assignment or override mechanism exists in A/G.

9.7 Override

a. Applies in ACM only.

b. A lead may claim the Engaged role from his own wingman.

Override

2:  2 ENGAGED
1:  NEGATIVE, 1 ENGAGED
2:  PRESS

c. #1 may override #2. #3 may override #4. Overrides do not cross elements.

9.8 A/G Sequence

a. The Offensive Fighter becomes offensive on passing the IP.

b. The Supporting Fighter calls supporting, keeps both the target area and the Offensive Fighter in view, and scans ahead and below for threats.

c. The Supporting Fighter is not automatically cleared to leave the formation or reposition.

d. The Offensive Fighter will remain ready to stop all mission tasks and respond immediately to the Supporting Fighter's directive calls.

e. At the end of the engagement (weapons off, out of the vulnerable phase, and visually deconflicted), the Offensive Fighter may hand the role over by calling supporting for a follow-on attack.

SECTION 10 — AIR-TO-AIR

This section establishes the air-to-air engagement contracts: ranges, targeting, sorting, shooting, defensive action, ACM, manoeuvres, cold operations, and tactic selection.

10.1 Ranges

a. TAC RANGE is 60 NM default, measured from the closest fighter to the closest GROUP.

b. Every other air-to-air range is BRIEFED EVERY MISSION.

10.2 COMMIT Call

a. Once COMMIT criteria are met, the FL commits the flight.

COMMIT

1:  SHADOW COMMIT

Note: The COMMIT manoeuvre (power setting and profile) is established in 10.8.

10.3 Targeting

a. HEAVY GROUPs are TARGETED element wise following LEFT LEAD HIGH ordering.

b. REMAINING GROUPs are TARGETED by the remaining flight members following LEFT LEAD HIGH ordering.

c. All flight members should call TARGETING on the assigned GROUPs (see a., b.) unprompted once contact has been established reliably

d. The FL makes every additional targeting assignment on primary (TACTICAL).

e. Each fighter will acknowledge with his number.

f. Individual assignment. The FL assigns a GROUP to each fighter individually. Where a GROUP needs disambiguating, the call includes its composition and altitude.

Individual Targeting Assignment

1:  2, TARGET WEST GROUP, TWO-SHIP, TWENTY THOUSAND
1:  3, TARGET WEST GROUP, TWO-SHIP, FORTY-FIVE THOUSAND
1:  4, TARGET MIDDLE GROUP
2:  2
3:  3
4:  4

e. Every fighter who targets a GROUP will make a TARGETED call. Each fighter reports individually on acquiring his assigned GROUP, including the FL.

Individual TARGETED Reports

1:  1, TARGETED EAST GROUP
2:  2, TARGETED WEST GROUP
3:  3, TARGETED WEST GROUP
4:  4, TARGETED MIDDLE GROUP

f. Element-wise assignment. The FL assigns a GROUP to an entire element. Acknowledgement is the same. Only the EL reports TARGETED, on behalf of the element.

Element-wise Targeting Assignment

1:  1&2, TARGET WEST GROUP; 3&4, TARGET EAST GROUP
2:  2
3:  3
4:  4
3:  3, TARGETED EAST GROUP

Note: An element-wise targeting call is also the clearance for that element to split from the flight. Refer to 1.7 for split contracts.

i. Untargeted GROUPs. Handling a GROUP inside targeting range with no element assigned is at the FL's discretion.

10.4 Sorting

a. On targeting a GROUP, the default sort priority is LEAD LEFT LOW. No sort call is made.

b. A sort other than the default will be prebriefed. The FL will not assign a different sort in flight.

c. A fighter at risk of losing his sorted contact to gimbals will request a split (1.7).

10.5 Shoot

a. The default shoot doctrine is one shot per contact, on targeted contacts only.

b. The shot doctrine in force determines which fighters shoot.

c. A fighter assigned a shot will take it as soon as practical after reaching Transition Range and before Minimum Shot Range.

d. A fighter not assigned a shot must not shoot.

Example: under a SKATE with a one-shot-per-element doctrine and a force ratio of 1, only #1 and #3 shoot.

e. No permission is requested and no announcement is made before firing. The employment itself is called with the appropriate brevity (5.4).

f. A fighter assigned a shot who cannot take it will call UNABLE SHOT.

UNABLE SHOT

<#> UNABLE SHOT, <reason>

or, where the shot is delayed rather than lost:

<#> UNABLE SHOT, STANDBY <time>

Note: This is an UNABLE call against a mission task and is handled under 8.7. Transition Range and Minimum Shot Range are established on the BVR pages.

Note: PACIFIST is not a valid reason.

10.6 Defensive and EXIT

a. On a missile-launch radar warning receiver indication from a fighter threat while inside Minimum Abort Range (MAR), a fighter must call EXIT and execute the defensive manoeuvre. Both conditions must hold.

b. A fighter not meeting both conditions must not call EXIT.

c. The default defensive manoeuvre is a 7G Split-S followed by S-curves, as established on the BVR pages.

EXIT

<#> EXIT <direction>

d. Case A, a wingman goes defensive.

(1) The FL must take over mutual support, calling supporting with his own number.

Mutual Support Handover

1 SUPPORTING

or, for the second element:

3 SUPPORTING

(2) Having taken over mutual support, the supporting fighter may then act to ensure the defensive fighter's survival.

Note: This handoff mechanism is shared with the SEAD defensive contract (Section 11). Only the trigger condition differs.

e. Case B, the FL goes defensive. This is an intercept abort criterion.

(1) The FL will make the call.

Flight Break

1, DEFENSIVE, FLIGHT BREAK <direction>, FLOW <bearing or cardinal direction>

(2) The flight will regroup.

(3) The flight will return to the task only if the timeline, fuel state, and remaining countermeasures all allow. Where all three allow, whether to return is FL discretion.

10.7 ACM

a. ACM roles are the Engaged and Supporting Fighter, established in Section 9. The calls are ENGAGED and PRESS, not OFFENSIVE and SUPPORTING.

b. ACM trigger: 10 NM to the nearest GROUP. At that range the engagement becomes ACM and the mutual support contracts (Section 9) take effect.

c. Bracket trigger: reaching 10 NM while executing BANZAI against the relevant GROUP.

(1) On that trigger the element will bracket.

(2) Outside BANZAI the element will hold as briefed until the FL directs otherwise.

d. STATUS calls.

(1) A STATUS call must include OFFENSIVE, NEUTRAL, or DEFENSIVE, as established in the Communications Doctrine.

(2) The Engaged Fighter will call each change of status unprompted, until the Supporting Fighter calls TALLY.

(3) Once the Supporting Fighter has called TALLY, the Engaged Fighter reports status only on a STATUS request.

Note: OFFENSIVE as a STATUS report means the Engaged Fighter is winning the fight. This is distinct from the Offensive Fighter role used outside ACM (Section 9).

e. The Supporting Fighter must not employ weapons while the Engaged Fighter's status is OFFENSIVE.

f. Once the Engaged Fighter's status is NEUTRAL or DEFENSIVE, the Supporting Fighter should intervene, employing weapons as required to resolve the fight.

10.8 Manoeuvre and Power Settings

a. On the FL's call of a named manoeuvre, each fighter will acknowledge the call and execute the manoeuvre as specified in Table 12.

b. All manoeuvres in 10.8 are executed from LINE ABREAST (LAB).

c. IN, OUT, and CRANK carry a default direction. Appending a direction to the call, relative (OUT LEFT) or compass (OUT WEST), overrides the default for that call.

Table 12. Manoeuvre and Power Settings
Manoeuvre	Contract
COMMIT	Full AB until Mach 1.1 in level flight, then sustained climb until the next manoeuvre is called.
IN (default right)	Full AB, hard turn.
OUT (default right)	Full AB, 5G sliceback.
CRANK (default right)	Turn to the gimbal limit, select military power, descend to 30,000 feet with 30 degrees nose down.

d. NOTCH, two-ship.

(1) Direction is set by position in the LAB. The fighter on the left turns hard left 90 degrees. The fighter on the right turns hard right 90 degrees.

(2) Each fighter will hold the NOTCH for 10 seconds.

(3) Each fighter must call SPIKED or NAKED no later than 7 seconds in.

(4) On SPIKED, execute OUT.

(5) On NAKED, manoeuvre for a missile shot, then execute OUT.

(6) OUT direction is opposite the NOTCH direction. Whoever notched left executes OUT to the right. Whoever notched right executes OUT to the left.

e. NOTCH, four-ship. The same pattern applies by element. The left-hand element notches left. The right-hand element notches right. Every fighter

must call SPIKED or NAKED.

f. After OUT (cold). Military power, sustained climb.

10.9 Cold Operations

a. On a recommit decision after going cold, the FL will follow the decision below.

b. Recommit inside Minimum Recommit Range (MRR):

(1) Is a second element available for targeting? If yes, four-ship DELOUSE.

(2) If no, is a kill necessary for survival? If yes, NOTCHBACK. If no, STAGGERBACK.

c. Recommit outside MRR: execute IN (10.8).

Note: NOTCHBACK, STAGGERBACK, and DELOUSE are established on the BVR pages.

10.10 Manoeuvring GROUPs

a. Where a targeted GROUP changes range or aspect relative to the targeting fighter, each fighter will take the action in Table 13 without waiting for direction.

b. An FL directive overrides Table 13.

Table 13. Manoeuvring GROUPs
Situation	Action
Targeted GROUP inside own WEZ	Shoot and kill, following Transition Range (10.5).
Targeted GROUP inside minimum targeting range	Maintain lock.
Targeted GROUP outside minimum targeting range	Break lock. Search for a closer hot contact. If one is present, call DROPPING on the last GROUP and target the new hot GROUP. Otherwise, relock the last GROUP.
Targeted GROUP outside targeting depth	Break lock, call DROPPING, return to airspace sanitization.
Targeted GROUP manoeuvring out of gimbals	Inform the FL and request a split, citing gimbals as the reason (1.7).

Legend: WEZ — weapon engagement zone.

10.11 Threat Reaction

a. On a THREAT call from TACC2, the FL (two-ship) or the first element (four-ship) takes whichever GROUP, the currently targeted GROUP or the new THREAT GROUP, is closer.

b. The wingman (two-ship) or the second element (four-ship) takes the farther GROUP.

c. The FL may reassign against this rule.

10.12 WALL versus GRIND

a. In selecting a tactic against the current picture, the FL should apply the criteria below.

b. WALL if more than two fire control radars are required within Targeting Depth (TD). This is met when either:

(1) Three or more GROUPs within TD with total azimuth greater than 20 NM, or

(2) Two GROUPs within TD where at least one is HEAVY.

c. GRIND otherwise.

10.13 Launch-and-Leave versus Launch-and-Decide

a. Launch-and-leave is the default. It is executed on a SKATE or SHORT SKATE call, and applies whenever nothing is called, at any force ratio.

b. Launch-and-decide is executed only on a BANZAI call.

c. The FL may change the tactic only during cold operations. The FL must not change the tactic inside the current engagement.

Note: The low, medium, and high risk engagement zones are specific to defensive counter-air and do not govern this choice generally.

10.14 GRIND and PUMP

a. Desired Pump Range (PR) is 45 to 55 NM. Desired Out Range (DOR) is the minimum.

b. Element criteria: 20 to 25 NM for a short-burn or active threat. 25 to 30 NM for a long-burn threat.

c. 30 to 45 seconds after OUT.

d. Altitude deconfliction, if required: hot greater than 25,000 feet. Cold less than 24,000 feet.

e. Weather backup: hot is the top 2,000 feet of the block. Cold is the bottom 1,000 feet of the block.

f. On reaching 10 NM down-range on the pump, the second element to pump will call PASSING. The FL will respond with CONTINUE (continue the GRIND) or REFORM (initiate the WALL plan).

10.15 Air-to-Air Threat Calls

a. On observing the indication, each pilot must call SPIKED and missile launch.

b. Each pilot may call NAILS.

c. Calls are made on TACTICAL, using standard brevity.

Note: Ground threat calls (MUD, SINGER, DIRT) are established in 11.2.4.

10.16 Reference

The SKATE family, BANZAI, CRANK, shoot doctrine, WALL and GRIND, and intercept geometry are established on the BVR pages. Key ranges are SHORT SKATE at MAR (19 NM at 30,000 feet), SKATE at Minimum Out Range (27 NM), and LONG SKATE at 35 NM.

SECTION 11 — AIR-TO-SURFACE

This section establishes the suppression of enemy air defences (SEAD) defensive contract, radar warning receiver calls, and threat reaction references.

11.1 Pre-employment Checks (W-A-M-O-E)

a. Before each weapon employment, the Offensive Fighter must complete the W-A-M-O-E check:

Table 14. W-A-M-O-E
Item	Check
W — Weapons	Mode (A, B, C, ...)
A — Arm	Armed
M — Master Mode	A/G or CCIP
O — Ops Check	Complete
E — Error Analysis	Adjustments for the next pass

b. W-A-M-O-E is scoped to A/G.

Note: W-A-M-O-E is unrelated to the general airborne ops-check item list established in FFC 1.7, which applies continuously in flight regardless of role or mission type.

11.2 SEAD

11.2.1 Tasking

Target assignment, shooter allocation, formation, and inventory allocation are all BRIEFED EVERY MISSION.

11.2.2 SEAD Defensive Contract

a. On a surface-to-air missile launch (SINGER indication), the defensive fighter calls:

SEAD Defensive

<#> SINGER 2, <most precise direction known>, DEFENSIVE <direction>

b. Handling follows the same Case A and Case B mutual-support handoff as the general defensive contract (10.6). Only the trigger differs.

(1) A wingman goes defensive. The lead must take over mutual support, calling supporting with his own number (1 SUPPORTING or 3 SUPPORTING), and may then act to ensure the defensive fighter's survival.

(2) The FL goes defensive. This is an attack abort criterion. The FL must call FLIGHT BREAK and FLOW. The flight will then regroup.

11.2.3 Post-Defensive Egress

a. The defensive fighter must egress to the prebriefed safe airspace point, hold there, and await further instructions.

b. The defensive fighter will pass fuel state to the FL.

c. Safe airspace will be a prebriefed point in space (BRIEFED EVERY MISSION, Section 13).

d. The FL may take over mutual support to ensure safe egress.

11.2.4 Ground Threat Calls

a. On observing the indication, each pilot must call MUD and SINGER.

b. Each pilot may call DIRT.

c. Calls are made on TACTICAL.

Ground Threat Call

<flight #> <DIRT | MUD | SINGER> <SAM type> <position>

d. Position may be bullseye, bearing, or clock.

e. The FL alone broadcasts targeting pod and HARM Targeting System emitter information.

Note: Air-to-air threat calls (SPIKED, NAILS, missile launch) are established in 10.15.

11.2.5 Threat Reactions

Refer to the 476TTP Threat Guide until a native 78th threat guide is published.

SECTION 12 — ABNORMALS

This section establishes procedures for lost wingman, radio failure, aborts, renumbering, jettison, and search and rescue.

12.1 Lost Wingman

Established in FFC 9.2. BLIND is established in FFC 9.1 and breakout in FFC 9.3.

Note: BLIND during an intercept is a separate case, handled by GIMBALS and SPLIT (Section 7).

12.2 Radio Failure

a. A wingman's radio fails.

(1) The affected pilot must rock wings and shake head to attract attention.

(2) Any member who observes this must advise #1.

(3) #1 must rock wings in response, which clears the affected aircraft for immediate RTB.

b. The FL's radio fails. Command falls back to #3 for the duration of the outage.

c. Radio failure on the ground. The affected pilot must squawk the briefed emergency code and contact Mission Command via Discord.

Note: This is distinct from the permanent succession rule (1.8). Command reverts to #1 once communication is reestablished.

12.3 Ground Abort

a. On an abort before takeoff, the aborting pilot will advise #1, roll to the EOR pad on the opposite side of the runway from takeoff, and attempt to resolve the problem.

b. The aborting pilot will advise #1 whether he can be airborne again within 10 minutes.

(1) Able within 10 minutes. Obtain separate clearance and attempt rejoin.

(2) Not able within 10 minutes. The FL and the CAOC will coordinate to achieve mission success without that aircraft.

12.4 Air Abort

a. On an abort after takeoff, the aborting pilot will advise #1 and the controlling authority.

12.5 Renumbering

a. If a member aborts or is lost, the remaining flight retains its original numbers.

b. The remaining lead may reassign numbers explicitly.

12.6 Jettison

a. Jettison over urban areas is prohibited at all times.

b. In combat and outside combat are defined by FENCE status. Inside FENCE IN is in combat. Before FENCE IN or after FENCE OUT is not.

c. Permitted.

Table 15. Jettison Authorisation
Situation	Authorised for
In combat (FENCE IN)	Fuel emergency or general flight safety
Outside combat (FENCE OUT)	Fuel emergency only, outside urban areas

d. Required on reaching minimum fuel or lower.

(1) Minimum fuel is a projected arrival at the Initial Approach Fix (IAF) below 1,200 lbs assuming optimal piloting.

(2) On reaching it, the pilot must jettison stores at the next practical moment.

12.7 Search and Rescue

Not modelled.

SECTION 13 — BRIEFED EVERY MISSION

The FL will brief each of the following on every sortie.

a. Departure parameters and formation selection are briefed under FFC Section 11.

b. Terrain avoidance floors: friendly and hostile minimum altitudes.

c. JOKER and weapon-state thresholds, and any BINGO deviating from the 2,000 lbs default.

d. Radio channelisation.

e. All air-to-air ranges other than TAC RANGE.

f. SEAD target assignment, shooter allocation, formation, and inventory plan.

g. Safe airspace point for defensive egress.

SECTION 14 — AMENDMENT

14.1 Authority

Only the Squadron Lead or the Wing Lead may amend this contract.

14.2 Review

a. Flight briefings are archived.

b. The Squadron Lead may review them ad hoc for recurring non-standard items, which are candidates for formalisation into this contract.

c. A non-standard item briefed on three consecutive missions is such a candidate.

SECTION 15 — REFERENCES

a. Formation Flying Contracts (FFC), 78th VMRS, Edition 1. Sole authority on formation matters: formations, turns, rejoins, ground operations, departure, recovery, lost sight procedures, ops checks, and frequency changes.

b. BVR I through VII, 78th VMRS. Beyond visual range employment doctrine.

c. Communications Doctrine, 78th VMRS. STATUS call formats.

d. Training Overview, 78th VMRS. Experience percentages for crew assignment.

e. 476TTP 3-1 Threat Guide, 476th Virtual Fighter Group. Threat reactions, pending a native 78th publication.

SECTION 16 — GLOSSARY

AB — afterburner.

ABM — Airborne Battle Manager. The role TACC2 assumes on taking control of the flight before VUL (6.1).

ANGELS — altitude in thousands of feet. ANGELS 20 is 20,000 feet.

BINGO — the fuel state at which a pilot must return to base or return to tankers, calculated to arrive with normal approach and landing reserve.

CAOC — Combined Air Operations Centre. Approves flight briefings, including any deviations from this contract (Preface, paragraph 3).

CAS — calibrated airspeed.

CRM - Combined Radar Mode.

DOR — Desired Out Range. Established on the BVR pages.

EL — Element Lead. #3 in a four-ship.

EOR — End of Runway.

FCR — fire control radar.

FL — Flight Lead. #1. Commands the flight.

HMD — helmet-mounted display.

HTS — HARM Targeting System.

Lead — the aircraft a given flight member is flying on: #1 for #2 and #3, #3 for #4. Not interchangeable with FL. A #4 rejoining on #3 has #3 as lead and #1 as the FL (FFC 1.1).

HEAVY — a GROUP of more than two contacts.

IAF — Initial Approach Fix.

IAW — in accordance with.

IP — initial point.

IPOC — in position or correcting. The aircraft is either holding its assigned formation position or actively manoeuvring to regain it.

JOKER — a fuel state above BINGO at which separation or bugout begins, giving the flight time to disengage before reaching BINGO.

LAB — LINE ABREAST. A formation established in FFC 5.3.

LCC — Last Chance Check.

MAR — Minimum Abort Range. Established on the BVR pages.

Minimum fuel — a projected arrival at the IAF below 1,200 lbs assuming optimal piloting. Triggers required stores jettison (12.6).

MRR — Minimum Recommit Range. Established on the BVR pages.

PR — Pump Range. The desired GRIND range (10.14).

TACC2 — Tactical Command and Control. Assumes control of the flight before VUL, acting as ABM on the TACTICAL frequency (6.1).

TD — Targeting Depth. Established on the BVR pages.

TGP — targeting pod.

TNDL — tactical network datalink. The F-16 datalink, configured via the data cartridge before the mission (7.5).

VUL — the vulnerability window. FENCE IN is called shortly before it begins and FENCE OUT shortly after it ends (3.1).

WEZ — weapon engagement zone.

Note: Data cartridges, including TNDL configuration, are prepared by ground crew and require no aircrew action.