Attachment 02- RF-A 2026 SPINS.pdf

UNCLASSIFIED

RED FLAG-ALASKA

SPECIAL INSTRUCTIONS (SPINS)

VERSION 1

UNCLASSIFIED

Table of Contents

1. Exercise Admin

2. Mission Planning

3. Flight Admin

4. Tac Admin

5. Operations

6. Contingencies

7. Post-VUL Training

8. Debrief

9. Standing Rules of Engagement (ROE) APPENDIX 1 - Adaptive Basing ROE APPENDIX 2 - Authentication and SARNEG Procedures APPENDIX 3 – RF-A On-Scene Commander (OSC) Checklist APPENDIX 4 – RF-A PR 15-Line APPENDIX 5 – RF-A DT Coordination Card 10-Line APPENDIX 6 - Link-16 J28.2(0) Free Text Message (“Zap”) Format APPENDIX 7 - ATO Change Request Sheet APPENDIX 8 – Real-Time Effects Coordination Sheet APPENDIX 9 – sIADS/India Target Attack Sheet APPENDIX 10 – Weapons Impact Scoring Set (WISS) Sheet

List of Tables and Figures

Table 4.1. RF-A IFF/SIF Modes and Codes Figure 8.7.2. Unclassified Debrief Flow Figure 8.7.3. Unclassified Debrief RF-A Kill Litany Figure 9.3.3. Air-to-Air ID Matrix (26-1) Figure 9.3.4. Air-to-Air ID Matrix (26-2) Figure 9.3.5. Air-to-Air ID Matrix (26-3) Table 9.4.3. RF-A Collateral Damage Estimate (CDE) Table 9.4.4. RF-A TST and CFACC CCT Decision Matrix Figure E.3. Allen Arrival

SUMMARY OF CHANGES:

REMARKS:

RED FLAG-Alaska (RF-A) participants will comply with the most restrictive of these SPINS, AFMAN11-214 Training Rules, the Joint Pacific Alaska Range Complex (JPARC) Range Handbook, JPARC Weapons Danger Zone (WDZ) Master List, or country/unit-specific guidance. Deviations must be approved by the Airboss.

TIMES/DAYS:

All TOT Times in the daily ATO are ZULU (Z). ZULU = Local + 8 Hours (During Daylight Savings Time) Days are numbered consecutively, but exclude weekends as follows:

FAM (Familiarization) Day = Friday prior to Day 01 (Monday) execution Day 01 = Monday of Week 1 execution Day 06 = Monday of week 2 execution

1. Exercise Admin

1.1. RF-A Planning Products Produced by the JECG (Joint Exercise Control Group)/White Force

1.1.1. RF-A SPINS

1.1.1.1. Contains information planners would find in theater SPINS and Rules of Engagement (ROE).

1.1.1.2. See CLASSIFIED SPINS for additional data as applicable:

https://dod365sec.spo.microsoft.scloud/sites/USAF-PACAF-EIELSON- 354OG/SitePages/353-CTS.aspx

1.1.1.2.1. RF-A CSAR Data is published with VUL mission planning products.

1.1.2. RF-A Air Tasking Order (ATO)

1.1.2.1. The source document outlining VUL-specific information such as Blue assets, callsigns, MSN/CC, Team Leads, weapons allocations, etc.

1.1.2.2. Published for each VUL via email or SIPR Sharepoint and contains information planners would find in a theater Master Air Attack Plan (MAAP) and ATO.

1.1.2.3. To request a change to the ATO, see APPENDIX 7.

1.1.3. RF-A Air Operation Directive (AOD)

1.1.3.1. Published for each VUL and contains information planners would find in a theater AOD and

Area Air Defense Plan (AADP). The RF-A AOD also includes information on VUL specific restricted fire areas, ROZs, Blue marshal limit lines, ROE changes, and Blue ground forces etc.

1.1.4. RF-A Target List

1.1.4.1. Published for each VUL and contains information planners would find in a theater Joint

Integrated Prioritized Target List (JIPTL) and Joint Integrated Prioritized Collection List

(JIPCL).

1.1.5. RF-A simulated Integrated Air Defense System (sIADS) Diagram and Graphical Intelligence Summary (GRINTSUM)

1.1.5.1. Contains information planners would find in a theater Intelligence Preparation of the Battlespace (IPB).

1.2. RF-A Coord Card

1.2.1. The MSN/CC is responsible for producing and distributing an UNCLASS RF-A Coord Card for the

VUL.

1.2.1.1. Coord Cards will be drafted utilizing WIDOW.

1.2.1.2. A first draft of the Coord Card is due to the Airboss by the GPAWM in Mission Planning.

1.2.2. The Coord Card will be finalized and printed no later than 20 minutes prior to the LFE Mass Brief.

1.2.3. The MSN/CC will ensure the finalized Coord Cards are distributed to all participants at the LFE

Mass Brief.

1.3. Pre-Mission Requirements

1.3.1. Any aircraft landing at an off-station/different airfield will verify their own

PPRs/Clearances/Flight Plans/all other support requirements.

1.4. Flight Discipline

https://dod365sec.spo.microsoft.scloud/sites/USAF-PACAF-EIELSON-354OG/SitePages/353-CTS.aspx https://dod365sec.spo.microsoft.scloud/sites/USAF-PACAF-EIELSON-354OG/SitePages/353-CTS.aspx

UNCLASSIFIED

1.4.1. Incidents involving safety, airspace violations, SPINS violations, or flight discipline will be addressed by the 353 CTS/DO or 354 OG Det 1 /DO in coordination with the participant’s leadership on a case-by-case basis.

1.5. WORDS and Situation Update Code (SUC)

1.5.1. Letter designations = WORDS. These are administrative updates affecting RED and BLUE.

1.5.1.1. Examples: Changes to the WARCALL, Tanker plan changes, weather info, VUL slip, recovery changes, ROZ status, contracts that affect Blue and Red etc.

1.5.2. Numeric designations = Situation Update Code (SUC). These are tactically significant updates.

1.5.2.1. Examples: Aircraft fallout, Lowdown, CHATTERMARK, Rolex, contracts etc.

1.5.3. WORDS and SUCs should be given together but may be given separately if required.

1.5.3.1.1. Example: A3 = WORDS ALPHA and SUC 3.

1.5.3.2. Aircrew only need to request “WORDS” to receive both WORDS and SUCs.

1.5.4. The end of the Mass Brief constitutes WORDS ALPHA.

1.5.5. The end of the MSN/CC’s brief constitutes SUC 1.

1.5.5.1. WORDS/SUC Generation and Passage. RF-A Top 3 owns WORDS/SUC generation and passage from the end of the briefs until PANTHER is on station, in coordination with the Airboss.

1.5.5.2. PANTHER will notify the Top 3 when on station.

1.5.5.3. PANTHER owns WORDS/SUC generation and passage until TAC C2 is on station.

1.5.5.4. TAC C2 and PANTHER ensure positive handoff of WORDS generation once established on station.

1.5.6. Red Air will call RF-A Top 3 for WORDS prior to Taxi. If unable to reach RF-A Top 3 then the respective unit Top 3/DDO will call the RF-A Top 3 and relay the WORDS.

2. Mission Planning

2.1. Air-to-Surface (A/S) Munitions Planning

2.1.1. Aircraft will NOT carry live or inert munitions unless appropriately coordinated with the JECG, annotated on the ATO (or an approved ATO change request), and fully mission planned.

(Exception: CATM A/A munitions).

2.1.1.1. Once the ATO is published, live/inert munitions must be requested and approved via ATO Change Request (APPENDIX 7).

2.1.2. Aircrew carrying live/inert weapons will:

2.1.2.1. Ensure weapon to target pairings have approved Weapon Danger Zones (WDZs), bombing range and weapons delivery restrictions.

2.1.2.1.1. Information is located at:

https://intelshare.intelink.gov/sites/354RANS/SitePages/Home.aspx

2.1.2.2. Verify weapon/target pairing matches WDZ data found at website listed above and QR code at ops desk.

2.1.2.3. Report any munitions malfunctions IAW the 354 MUNS checklist located in the RF-A Ops

Desk binder and https://usaf.dps.mil/sites/eielson/354OG/353CTS/SitePages/Home.aspx -> RED-FLAG Alaska -> Documents.

2.1.3. All Live/Inert employment in the live target areas will be planned with a safe escape from a 2000 pound class weapon frag due to possible unexploded ordnance on the range.

https://intelshare.intelink.gov/sites/354RANS/SitePages/Home.aspx

UNCLASSIFIED

2.1.4. Weapons Impact Scoring System (WISS)

2.1.4.1. WISS cameras will be used for live/inert A/S munition deliveries if available.

2.1.4.2. Submit the WISS request sheet (APPENDIX 10) to the Airboss during mission planning.

2.2. A/S Time-On-Target (TOT)

2.2.1. An initial TOT will be planned for all live and inert ATO assigned A/S impacts.

2.2.2. Two minutes prior to the TOT, a ROZ will be activated to a baseline SFC-24k’ (IAW ACP) in the respective range to ensure Red Air has time to deconflict.

2.2.2.1. Changes to baseline altitudes and confines will be addressed in the MPC with Airboss approval.

2.2.2.2. ROZ locations, altitudes, and start times will be annotated on the Blue and Red coord cards.

The Blue coord card will be the source of accurate data.

2.2.3. Live/Inert Weapon Releases

2.2.3.1. No RED aircraft may be in the respective Live/Inert Munitions ROZ from 2 minutes prior to the TOT until declared COLD.

2.2.3.2. BLUE aircraft may be in the confines of the ROZ, but will be at a higher altitude than the formation/s dropping bombs.

2.2.3.3. The MSN/CC will ensure a bomb fall deconfliction plan is briefed at the GCAM and Mass Brief.

2.2.3.4. Blue Aircraft under JTAC/FAC control

2.2.3.4.1. Initial TOT’s do not apply when aircraft are under JTAC/FAC control.

2.2.3.4.2. Weapon deconfliction is determined by the JTAC/FAC. The JTAC will pass WDZ restrictions as part of the 9-line.

2.2.3.4.3. Red aircraft may not be in the JTAC/FAC controlled ROZ unless above a mission planned ROZ ceiling.

2.2.4. Simulated Weapon Releases

2.2.4.1. Bomb fall deconfliction will be mission planned for simulated weapons.

2.2.5. Deliveries which require a deviation or transition from the assigned Blue blocks must be approved by Airboss during mission planning.

2.3. Fuel Planning

2.3.1. Blue will plan fuel for a tactical egress to scenario directed recovery line/point, then back to their base of intended landing via the expected recovery.

2.3.2. JBER recovering fighters, will flow cold for 1 minute, then may 90 out to the fight East or West with mission planned assumptions for tactical scenario egress.

2.3.2.1. Exception: Aircraft assigned a “CAS CP” may plan to RTB direct from their CP location.

2.3.3. A “Reliability Tanker” will be designated for each VUL (normally a red tanker). Expect boom only.

If drogue operations are required, it must be specifically coordinated and may not be available.

2.3.3.1. The “Reliability Tanker” will carry 20,000 lbs. of off-loadable fuel (releasable only by the Airboss) and will remain on-station until released by the Airboss. After the “REDFLAG KIO”, expect to relocate to the SMOLT AAR track in Yukon 1 via C2 coordination or Airboss direction. Utilize ASAP if safety of flight dictates at any time. Updates will be briefed by the Tanker Task Force (TTF) in Mass Brief.

2.3.4. See section 6.6 Low Fuel and 6.7.2 Tanker Fallout/Delays for fuel and tanker contingencies.

2.4. Real-Time Effects Planning

UNCLASSIFIED

2.4.1. Attacks/Non-Kinetic Effects (NKE) on the simulated IADS (sIADS) can generate real time effects during the VUL when coordinated prior to execution and communicated IAW section 5.9 Real- Time Effects and Air-to-Surface Attacks.

2.4.1.1. All sIADS DPIs on the ATO Target List will have the letter “India” prefix followed by numbers (i.e. “I02”).

2.4.2. The MSN/CC will ensure the Real Time Effects Coordination Sheet (PET Shots, kinetic attacks, MALD route data, jamming, etc.) is filled out and given to the Airboss NLT the end of the GCAM.

See APPENDIX 8 – Real-Time Effects Coordination Sheet.

2.4.2.1. Real Time Effects Coordination Sheet will be provided to Red 1 NLT Mass Brief.

2.5. Live/Virtual/Constructive (LVC) Planning

2.5.1. All players will treat live and synthetic participants the same. Blue synthetic entities will be accounted for in the deconfliction plan, to include their own block altitudes.

2.5.2. Virtual Stand-off Weapons

2.5.2.1. Blue mission planners will coordinate with the respective LNOs for the stand-off weapons (SOW) planned for employment: MALD, JASSM, LRASM, etc.

2.5.2.2. SOW will count against the ATO loadout.

2.5.2.3. SOW users will coordinate with the Airboss NLT the GCAM and annotate routes and desired effects IAW paragraph 2.4 Real-Time Effects Planning.

2.5.2.4. Airboss will coordinate effects with RED-1 and SAM-1 NLT the Mass Brief.

2.5.3. Constructive SAMs (C-SAMs)

2.5.3.1. C-SAM locations are matched to real-world building sites when possible (simulating C-SAM components).

2.5.3.2. C-SAMs will not be co-located with real emitting sites.

2.5.3.3. Blue weapons effects will be assessed real-time IAW paragraph 5.9 Real-Time Effects and

Air-to-Surface Attacks.

2.5.4. Simulated Combined Air Operations Center (CAOC), Callsign “WARPIG”

2.5.4.1. The JECG will act as the CAOC and transmit/receive on the C2 Coordination frequency, through PANTHER, or Mardem-Bey Internet Relay Chat (mIRC).

3. Flight Admin

3.1. Flight Plans:

3.1.1. RF-A aircraft will file stereo IFR flight plans to the max extent practical.

3.1.2. Exception: Aircraft taking off prior to Airspace activation time may file routing to an entry point and hold outside of airspace prior to airspace clearance for mission requirements. Examples include: Tankers, MARSA tanker drags, airborne C2, etc.

3.1.2.1. Stereos are listed in the RF-A IFG Supplement and 3 WG/354 FW IFG.

3.1.2.2. Coordinate with Joint Exercise Control Group (JECG [Airboss/Ops Sup]) when stereo flight plans are not compatible with scenario planning.

UNCLASSIFIED

3.1.3. Aircrew will annotate ATO-assigned Mode 3 in the remarks section of stereo flight plans or DD1801. Once cleared and established in airspace, set ATO assigned M3A/C.

3.1.3.1. The ATO-assigned Mission number is the Mode 3.

3.2. Departure

3.2.1. Depart IAW 3 WG/354 FW In-Flight Guide and the RF-A IFG Supplement or filed flight plan.

3.2.2. Lead aircraft will always squawk Mode 3/C. When in standard formation all others will strangle

Mode 3/C. When in non-standard formation the last aircraft will squawk Mode 3/C 4000.

3.2.2.1. Once inside RF-A airspace, all aircraft will squawk ATO assigned Mode 3/C at all times and

P5/ACMI (if able).

3.2.2.1.1. Exception: M3A/C Off Procedures, if in effect. See section 3.5 M3A/C Procedures.

3.3. Airspace Entry/Check-In

3.3.1. Fixed Wing Aircraft

3.3.1.1. Anchorage Center (ZAN) is the clearance authority to enter training airspace. ZAN will pass

“Cleared into RED FLAG airspace as briefed, radar service terminated, frequency change approved” to aircraft on IFR flight plans.

3.3.1.1.1. If departing via THUNDER VFR DEPARTURE, clearance into the airspace will come from Eielson Tower prior to takeoff e.g., “THUNDER VFR DEPARTURE to the north approved, cleared into RED FLAG airspace as briefed, frequency change approved.”

3.3.1.1.2. Maintain last assigned clearance (altitude etc.) until inside RF-A airspace.

3.3.1.2. Contact Check-In C2 with alibis after ZAN release.

3.3.1.2.1. C2 will authenticate flights IAW APPENDIX 2 - Authentication and SARNEG Procedures, check IFF/SIF, pass altimeter setting, relay the Warcall (if already passed), provide administrative updates via WORDS and tactical updates via SUC, pass Electronic Order of Battle (EOB), lowdown, and Roll Call IAW MSN/CC gameplan.

3.3.2. Rotary Wing Aircraft

3.3.2.1. May fly and maintain VFR to/in RF-A airspace.

3.3.2.2. Must receive clearance from TAC C2 (primary), Eielson Range Control (ERC) (secondary), or

Airboss (tertiary) before entering any restricted area.

3.3.2.3. Rotary Wing aircraft must maintain Mode 3 A/C for the entire duration of their assigned airspace timing.

3.4. Altitude Blocks

3.4.1. The blocks listed on the finalized Coord Card issued at the RF-A Mass Brief are the sole reference for airborne execution. RF-A LFE players will not change altitude block assignments after the LFE Mass Brief.

3.4.2. If the Coord Card-assigned altitude block(s) is unusable for execution (icing, turbulence, VMC-only player) and no alternate block(s) is available, affected players will coordinate holding with C2 and/or RTB.

3.4.3. The Airboss is the approval authority for deviations to the ACP block structure. This must occur during the mission planning day.

UNCLASSIFIED

3.5. M3A/C Procedures

3.5.1. IAW 354 OG/OGV FCIF A25-04 for RF-A the Airboss will be the Radar Monitoring Agency (RMA).

3.5.1.1. M3A/C OFF areas are IAW the ACP, >5NM within approved Special Airspace Activity (SAA) border, and 1K feet below ceiling of SAA. Aircraft will turn on M3A/C NLT 5 min prior to contacting ZAN or directed to by Airboss/RMA/C2.

3.5.1.2. The Airboss/RMA is the authority for M3A/C OFF operations. Once the Airboss directs M3A/C off operations in the Warcall, C2 will direct assets to strangle M3A/C once all requisites have been accomplished. Treat directives from C2 as coming from Airboss/RMA.

The requisites for M3A/C off can be found below:

3.5.1.2.1. Reliable two-way communication between C2 and aircraft.

AND

3.5.1.2.2. Positive aircraft control via radar contact and bullseye check.

3.5.1.3. Once the Airboss/RMA has approved M3 A/C OFF operations, the Airboss/RMA will authorize C2 to direct players to turn M3 A/C ON or OFF IAW the criteria above. This will be included in the Warcall.

3.5.1.4. C2 (ground and/or airborne) will ensure a good alpha check and ability to monitor position in known coverage areas before directing players to turn off M3 A/C.

3.5.1.4.1. If tracking is lost in a known coverage area, C2 will inform the Airboss and is authorized to direct M3A/C ON for that player(s).

3.5.1.4.2. Player(s) having received positive authorization and subsequently lose two-way communication may procedurally follow 3.5.1.1 once established unless directed otherwise.

3.5.1.5. If a player(s) recognizes a Special Activity Airspace (SAA) bust, inform Airboss immediately to initiate a Whiskey Alert to ZAN/ATC.

3.5.1.6. At RED FLAG KIO, all players set M3A/C ON.

3.5.2. Large Frame Aircraft (LFA), tankers and C2 platforms will keep M3A/C ON unless authorized otherwise by the scenario.

3.5.2.1. Excluding Rotary Wing aircraft (see section 3.3.2.3. above).

3.6. Air to Air Refueling

3.6.1. See ACP or RF-A IFG Sup for AAR admin specific tracks.

3.6.2. Operations will be IAW ATP-3.3.4.2.

3.6.3. EMCON 3 is the standard option for air refueling operations. EMCON 2 may be utilized if safety dictates. EMCON 4 is not authorized.

3.6.4. Travel to and from AR Tracks under TAC-C2 to max extent practical or mission planned procedures. Use all available sensors to clear flight paths. In the absence of positive C2 control, broadcast position, intentions, and clear aggressively.

3.6.4.1. If holding is required, hold at least 15NM away from MOA gates avoiding standard entry/exit altitudes.

3.6.5. Receivers will fly C2 assigned altitude (or Coord Card alt block if no C2) enroute to AAR. Enter 1,000 ft below AAR base altitude.

3.6.6. After AAR, receivers will climb 1,000 ft above AAR base altitude (unless C2 directs a higher altitude) and contact check-in C2 for further direction.

UNCLASSIFIED

3.6.7. Tanker tracks, sandboxes and altitudes may be altered to match mission requirements, with Airboss approval.

3.6.7.1. TTF will alibi “unable to slide/scram” in the debrief, and record time of attempted slide/scram.

3.6.8. Fighters transiting in the lateral confines of the AAR track will do so with positive C2 control to max extent practical.

3.6.8.1. Note: Given the constraints of ground-based Command and Control (C2), it is imperative that all participants familiarize themselves with the full extent of ground-based radar and communication coverage within the JPARC airspace.

3.6.9. Chinook Track is primarily for Airborne C2.

3.6.10. See paragraph 6.7.2 Tanker Fallout/Delays for contingencies.

3.7. Range Clearing Pass

3.7.1. When live/inert weapons are on the ATO, RED-1 (or as delegated) will execute a Range Clearing Pass IAW AFMAN11-214 and the JPARC Range Handbook. If unsuccessful (weather, fallout) Airboss will transmit “[…] Ranges are RED […]” during the Warcall and Blue will execute dry A/S attacks for the VUL.

3.7.2. A clearing pass for RF-A VULs is valid for 120 min (MFE) with the ability for impacts to be spotted.

See JPARC Range Handbook 2024 “MFE Clearing Target Area” and “Clearing Target Area”.

3.7.3. If an earlier clearing pass was not completed, the first players will be required to clear prior to employing ordnance. If ranges are clear, inform Airboss and utilize reattack option to expend weapons. Expect admin drops to take place during scenario or post-VUL.

3.7.4. For contingency IMC drops with ground or airborne players spotting beneath, ensure bomb fall deconfliction and frag avoidance are met.

3.8. Warcall

3.8.1. Airboss will transmit the Warcall on Guard (243.0), via mIRC in the C2 Coord chat, and via J28.2 message 15 minutes prior to VUL with maneuvering category/weather restrictions, M3A/C status, Eielson/JBER recovery routings (to include OPFOR recovery as applicable), Eielson/JBER declared alternates (when applicable), range status, and the altimeter setting. Example: “RED FLAG is IMC rules, with control, unlimited clear of clouds, M3 OFF AUTHORIZED. Eielson is BNGAL to instrument approach, Eielson alternate is Fairbanks. JBER is BRODE to VFR. Ranges are RED/GREEN. 2211 recoveries are open/closed. Altimeter 29.92”.

3.8.1.1. RF-A aircraft will use the altimeter setting announced during the Warcall for all RF-A VULs.

3.8.2. If the Warcall is not received:

3.8.2.1. Maintain your block.

3.8.2.2. Do NOT go further than your respective MLL/CLL.

3.8.2.3. Do NOT Push. Maintain M3A/C ON.

3.8.2.4. Attempt contact with C2 and/or the Airboss for the Warcall.

UNCLASSIFIED

3.9. Air Combat Training Airspace (ACBT)/MLL/CLL ROE

3.9.1. All Out-of-Block maneuvering will occur within the ACBT borders (Red may also tactically maneuver in “Blue no-fly” areas). See the ACP for coordinates.

3.9.1.1. BLUE Out-of-Block threat reactions north of the ACBT are acceptable if you have the

“Requisite SA” to leave your block IAW AFMAN11-214.

3.9.1.2. Aircraft established in the AXSEM, TANACROSS, DRAGONFLY, or GRASSHOPPER ALTRVs are still considered part of the fight. They will continue to fight on the local altimeter IAW ACP.

3.9.2. After VUL start time late joiners will enter the ACBT from the North/South, behind their respective CLL/MLL if applicable (no lateral boundary ACBT entries after VUL start time).

3.9.2.1. The MLL/CLL:

3.9.2.1.1. 26-1 & 26-2: is set per the ACP, AOD or ATO.

3.9.2.1.2. 26-3: Blue: scenario defined point. Red: Regen line/point or Baron discretion with

Airboss coordination.

3.9.3. After VUL start time BLUE aircraft may exit/re-enter the northern boundary of the ACBT as required.

3.9.3.1. RED aircraft may exit/re-enter the southern boundary of the ACBT as required.

3.9.3.2. 26-3 ONLY: Both RED and BLUE may cross the Western/Eastern ACBT boundaries but must be established in the respective ALTRV altitude blocks before doing so.

3.9.3.3. JBER aircraft may RTB through the lateral boundary of the ACBT IAW ACP section 2.9.3.3.

3.9.4. Aircraft violating ACBT ROE or crossing the MLL/CLL (if applicable) before VUL start may be colored white in the debrief at the Shot Validation Lead’s discretion.

3.9.4.1. Exception: Rotary wing/slow-mover early ACBT entry options.

3.9.4.1.1. May originate at a specified location inside the ACBT at VUL start per the ATO.

3.9.4.1.2. Red players will react to slow-mover ACBT entry players only after VUL start time.

3.10. VUL Timing

3.10.1. ATO VUL start time = auto “fights on.”

3.10.2. Pre-Vul effects (A/A or A/G) MLL crossing must be previously coordinated with Airboss via

Real-Time Effects Coordination Sheet (APPENDIX 8).

3.10.2.1. A “Slip” or “Rolex” applies to Blue only and does not change VUL start time or planned

TOT windows. Changes to planned TOT windows require Airboss approval.

3.10.3. VUL Start Time Changes

3.10.3.1. The MSN/CC may request Airboss change the VUL start time (Blue and Red). If approved, Airboss will transmit the new VUL start time on Guard (i.e. “New VUL start time 1900z”).

This shifts TOT windows and all planned events relative to the time change.

3.10.3.1.1. Airboss will coordinate the new TOTs and post-LFE VUL training plan with RF-A Top- 3, SOF, C2, and ERC.

3.10.4. VUL End Time

UNCLASSIFIED

3.10.4.1. Airboss will transmit “RED FLAG Knock-It-Off DLO” on Guard (243.0), via mIRC in the C2 Coord chat, and via J28.2 message. This ends all LFE tactical maneuvering and the scenario portion of training.

3.10.4.1.1. MSN/CC or TAC Mentor (in the event of MSN/CC upgrade) will coordinate KIO criteria (DLOs) with Airboss during mission planning.

3.10.4.1.2. Airboss will add “standby new VUL time” to the KIO call if desiring to reset and start a new VUL (typically used if DLOs met and there is time and fuel available).

3.10.4.2. Execute KIO procedures IAW section 6.1 RED FLAG Knock-It-Off (KIO).

3.11. Check-Out

3.11.1. Turn M3A/C ON when approaching known admin corridors, airspace borders, or as directed by

C2.

3.11.2. Contact Check-out C2 IAW the ACP once clear of local engagements.

3.11.3. Pass Bomb Hit Assessment (BHA): “(c/s), [weapon types and number expended], [Target/DPIs

#s hit], [Target/DPI #s assigned not hit or unsuccessful], [amplifying remarks].”

3.11.4. When ready for RTB pass number in flight and “playtime.” (Playtime = flight’s time to hold until bingo). Ex: “(c/s), 4-ship, 10 minutes playtime.”

3.11.5. Pass “dead” flight member data IAW 5.7.2.

3.12. Recovery

3.12.1. Refer to RF-A ACP and RF-A IFG Supplement and comply with the following:

3.12.2.1. After radio contact with ATC, use the same Mode 3A/C squawk ROE as section 3.2 Departure.

3.12.2. Recovery Routing:

3.12.2.1. Execute the recovery IAW the Warcall, IFG and ATC guidance. If a different recovery is required, coordinate with the C2 and Airboss.

3.13. Magnetic Variation

3.13.1. Units participating in RF-A will ensure their aircraft magnetic variation is updated prior to the exercise.

3.13.2. If a unit cannot confirm their magnetic variation or has incorrect tables, they will manually enter the current magnetic variation. Utilize the NOAA magnetic field calculator website https://www.ngdc.noaa.gov/geomag/calculators/magcalc.shtml, input MIZZI (N64 22.1173 W145 30.4693) as the reference point and select World Magnetic Model (WMM).

3.13.2.1. If unable to accomplish, communicate loose pairing criteria requirements.

4. Tac Admin

4.1. IFF/SIF (Identification Friend or Foe/Selective Identification Feature)

4.1.1. Squawk IAW Table 4.1 below.

4.1.2. Neither Blue nor Red will use Mode 3/C interrogation for tactical execution unless executing

MODE 3 off operations. It may be used for admin and safety of flight.

https://www.ngdc.noaa.gov/geomag/calculators/magcalc.shtml

UNCLASSIFIED

4.1.3. Tac admin (G-Exercise if required) will be accomplished within the airspace and prior to entering a hold. Coordinate deviations with C2.

Table 4.1. RF-A IFF/SIF Modes and Codes Blue Red

Mode 1 Off IAW Classified SPINS annex Mode 2 IAW MSN/CC, 2222 = DEAD IAW Classified SPINS annex, 2222 = DEAD

Mode 3/C On*; Code: IAW ATO MSN # (flights in sequence) On*; Code: IAW ATO MSN # (flights in sequence) Mode 4 Off Off Mode 5 IAW Classified SPINS annex

1*Unless briefed to be Mode 3A/C Off by RF-A Staff.

4.2. A/A TACAN

4.2.1. BLUE ≤ 28 and 40-41

4.2.2. RED ≥ 52

4.2.3. Tankers (RED and BLUE) = 29-39

4.3. Radio Frequencies/Communication

4.3.1. All radio frequencies (UHF, VHF, HF etc.) used will be IAW the RF-A Comm Plan.

4.3.1.1. T-NET/FMT-NETs may be used. WODs are IAW the 3 WG/354 FW IFG.

4.3.1.2. T-NET/FMT-NET primary TOD is GPS, secondary is airborne C2, tertiary is fighter.

4.3.2. All CSEL radios will be loaded IAW PACAF SPINS to ensure OTH comms are possible with the Rescue Coordination Center (RCC). See section 6.11.

4.3.3. mIRC Rooms

4.3.3.1. mIRC-capable RF-A players will use the COMPACFLT IRC mIRC server if US only and AFCENT

CAOC server if S\\Rel to USA, FVEY. JECG will provide login information.

4.3.3.2. Use the following chat windows:

4.3.3.2.1. #RED_FLAG_AK_SADO: JECG (CAOC “WARPIG”) battlespace injects and coordination such as intel updates and dynamic target taskings etc.

4.3.3.2.1.1. Players: Airboss, LVC, C2 and all other mIRC capable assets prosecuting dynamic surveillance and targeting.

4.3.3.2.2. #RED_FLAG_AK _C2 _COORD: Coordination between C2 participants.

4.3.3.2.3. #RED_FLAG_AK_LINK_COORD: Coordination between JICO and C2 for link operations.

4.3.3.2.4. #RED_FLAG_AK_JPRC: Simulated PR related operations coordination.

4.3.3.2.4.1. Players: C2, CSAR assets, Airboss, and other rescue response related operations.

4.3.3.2.5. #RED_FLAG_AK_SOTF: SOF communication nodes and C2.

4.3.3.2.6. #RED_FLAG_AK_FIRES: US Army HIMARS coordination (all ROZ and dynamic targeting coordination will be passed in the #RED_FLAG_AK_SADO window).

UNCLASSIFIED

4.4. Datalink

4.4.1. Reference the RF-A OPTASKLINK and COMSEC Callout.

4.5. SIGINT ID Authority

4.5.1. The SIGINT Identity Authority (SIA) will plot and update all air and ground J-Series messages associated with the lowdown and tactical air picture. The SIA may delegate plotting responsibilities to subordinate MDS’ when troubleshooting equipment issues or to meet mission requirements.

4.5.2. TACREP Alphanumeric Designators

4.5.2.1. A: COMINT (Air)

4.5.2.2. E: ELINT

4.5.2.3. F: Fusion (all/multi-source)

4.5.2.4. G: COMINT (Ground)

4.5.2.5. H: HUMINT

4.5.2.6. I: IMINT

4.5.2.7. J: Radar MTI

4.5.2.8. M: MASINT

4.5.2.9. N: COMINT (Naval activity)

4.5.2.10. O: OPIR

4.5.2.11. R: CAOC

4.5.2.12. S: Survivor

4.5.3. TACREP Blocks and SIGINT ID authority priority

4.5.3.1. RC-135V/W: 01-99

4.5.3.2. NAVY (EP-3 / EA-18G): 100-199

4.5.3.3. E-2D/E-7: 201-299

4.5.3.4. E-3B/C/G: 301-499

4.5.3.5. DGS: 501-599

4.5.3.6. NTM/NTI: 601-699

4.5.3.7. CAOC: 701-799

4.5.3.8. Space: 801-899

4.5.3.9. Open: 901-999

4.5.4. TACREP Reporting Method

4.5.5. Positive handover of plotting contracts will be passed as follows:

4.5.5.1. Primary: mIRC and/or Chatsurfer

4.5.5.2. Secondary: VPN and/or J28.2

4.5.5.3. Tertiary: C2 Coord

5. Operations

5.1. Live/Inert Ordnance Operations

5.1.1. All live/inert weapon impacts must be observed by one of the following:

5.1.1.1. Onboard sensors from any aircraft (Targeting Pod, visual, etc.)

5.1.1.2. WISS (remote cameras on the range) – See section 2.1.4 and APPENDIX 10.

5.1.1.3. JTAC or other qualified observer on the ground.

5.1.2. IMC employment

5.1.2.1. Live employment of inertial aided munitions in IMC is authorized if a clearing pass can be completed and either WISS camera, airborne player or ground party support to visually spot.

5.1.2.2. Inert inertial aided munitions and laser guided bombs may be dropped through IMC if all applicable procedures from the JPARC Range Handbook concerning IMC deliveries have been followed. A clearing pass is always required for IMC deliveries IAW the JPARC Range Handbook.

5.1.3. No Spot Reports

UNCLASSIFIED

5.1.3.1. Aircrew will pass each weapon’s release conditions (altitude, airspeed, heading, bomb range, and aircraft displayed TOT) to the 354 RANS Range Duty Officer (RDO) prior to the LFE Mass Debrief to produce the No Spot Report.

5.1.4. All attacks on dynamic targets (any target not published on the ATO) or off range targets will be dry.

5.1.5. Flights dropping live/inert ordnance will report expenditures to ERC on RTB.

5.2. A/A Shot ROE

5.2.1. Alive Red aircraft may be shot any time while in the Airspace during VUL time IAW section 9, Standing Rules of Engagement (ROE) and/or applicable VUL specific updates.

5.2.1.1. Blue/Red RTB or late joiner aircraft will squawk dead until regenerated. Any shots into such aircraft will be disregarded and “missile back” may be granted by RTOs.

5.2.2. There is no “Blue Safe Criteria” unless outlined in VUL specific products.

5.2.2.1. When RTB, fighters will tactically egress to exit the ACBT. When ready to RTB, cease tactical maneuvering, squawk Mode 2 of “2222”, and begin checkout procedures with C2.

5.2.2.2. Shots that timeout against Blue aircraft outside of the ACBT will be called and executed to airborne to the max extent practical.

5.3. Range Training Officer (RTO) Operations (callsign “TWO BEARS”)

5.3.1. All VULs will be planned as RTO assessment, Within Visual Range (WVR) option, realistic employment, with orthogonal roll procedures.

5.3.1.1. Weapons Pk is IAW JECG Adversary Threat Matrix.

5.3.2. Execute RTO procedures IAW 3-1 Shot Kill.

5.3.2.1. Call A/A shots on the primary fight frequency or as briefed using Bullseye format. Use

Bearing, Range, Altitude, and Aspect (BRAA) if unable to use Bullseye.

5.3.2.2. If TWO BEARS does not acknowledge, repeat the call until receiving “copy shot.”

5.3.3. The MSN/CC is responsible for coordinating and briefing a TWO BEARS/SAM-1 comm relay plan for aircraft with expected comm limitations.

5.4. RTO-Aided Visual Identification (VID)

5.4.1. If a Blue player VIDs an aircraft type which is playing on both Blue and Red in the VUL Blue may request a “VID” or “Eyeball” from the RTO:

5.4.1.1. Blue Fighter 1: “TWO BEARS, Dice 11, merged VID F-15 bullseye 353/18”

5.4.1.2. RTO Response 1: “DICE 11, TWO BEARS, VID Hostile”

5.4.1.3. Blue Fighter 2: “TWO BEARS, Dice 11, EYEBALL F-15, bearing 353”

5.4.1.4. RTO Response 2: “DICE 11, TWO BEARS, EYEBALL Flanker”

5.5. Slide/Scram

5.5.1. Slide/scram ranges, terminates and resets will be planned per MDS. Realistic ranges will be used to the max extent possible.

5.5.2. Tanker Slide

5.5.2.1. Continue AAR operations and transit in assigned altitude block IAW mission planned slide contract.

5.5.2.1.1. If no slide contract, maintain AAR track, and any deaths will be debriefed to a logical conclusion.

5.5.3. Tanker Scram

5.5.3.1. Execute normal AAR disconnect.

UNCLASSIFIED

5.5.3.2. Transit at training scram speed and conduct no AAR until scram complete or “Terminate” by tanker or receiver for fuel priority/emergency.

5.5.3.3. Combat descents approved if deconflicted in mission planning and briefed thoroughly.

5.5.3.4. Receivers may AAR during reset transit.

5.5.3.5. If no scram contract, maintain AAR track, and any deaths will be debriefed to a logical conclusion.

5.6. Terminate Procedures

5.6.1. Call terminate with bullseye on TWO BEARS IAW AFMAN11-214 for training rules stops

(LOWAT/TA/IMC).

5.6.1.1. TWO BEARS will relay terminate call, with bullseye, to Red and Blue.

5.6.2. All aircraft within 5NM of a “Terminate” will flow BVR (min 10 NM separation) before re-engaging.

5.6.3. Clearly offensive aircraft may flow as desired.

5.6.4. Neutral/defensive Blue aircraft will flow minimum 5NM IAW section 5.7 Aircraft Kill Removal.

5.6.5. Neutral/defensive Red aircraft will kill remove.

5.6.6. Terminate HVAA defensive tactics a minimum of 10 NM from the RF-A Airspace border.

5.7. Aircraft Kill Removal

5.7.1. When called dead by TWO BEARS or SAM-1, aircraft will:

5.7.1.1. Acknowledge kill call on the frequency received.

5.7.1.2. Cease all weapon employment, tactical sensor/emitter use, tactical maneuvering (threat reactions etc.), and tactical comm.

5.7.1.2.1. Exception: Interdiction/Airlift/Helo may continue planned A/S deliveries IAW

5.7.1.4.1.

5.7.1.2.2. 5th Gen: Cease interflight datalink as soon as deconfliction is assured.

5.7.1.3. Fighters

5.7.1.3.1. Escort/SEAD: Flow 90 out then cold for 5 min.

5.7.1.3.1.1. DCA touch the line coincident with Yukon 5 northern border: N 64 40 line

5.7.1.4. AI/Bomber/Airlift/Helo

5.7.1.4.1. If called dead, “ghost” along ingress routing and execute delivery, then regen with prior loadout (no A/S ordnance).

5.7.1.4.1.1. Deliveries from “ghosting” aircraft will be assessed as unsuccessful in debrief.

MSN/CC and Team Leads re-roll as appropriate to achieve mission objectives.

5.7.1.5. CAS/DT

5.7.1.5.1. “Ghost” for 5 min by continuing ingress route or remain in AO/ROZ as applicable.

5.7.1.6. HVAA

5.7.1.6.1. C2: Provide safety of flight directions only. Orbit in place. Discontinue contributions to link-16 surveillance tracks.

5.7.1.6.2. Tanker: No offload for 10 minutes (unless required for safety of flight) - Aircraft on boom at the time are dead. Aircraft on the wing may be colored white in the debrief at the TAC Mentor’s discretion.

5.7.2. If the tactical situation allows the asset with the most situational awareness (SA) will report the “called dead” aircraft to TAC C2 by passing lines 1, 2, 3 of the PR 15 line (see APPENDIX 4 – RF-A PR 15-Line). Do not say PR, CSAR, SAR, or survivor on the radio. If the tactical situation does not allow, pass data to C2 on checkout.

UNCLASSIFIED

5.7.2.1. The intent of passing “called dead” data is to exercise force accountability, not to exercise additional OSC responsibilities. For OSC exercise details see section 5.13.6 Immediate Shoot-Down.

5.7.2.2. Example: “DARKSTAR, VIPER 2…VIPER 1 called dead, standby data. VIPER 1, 1 IP, bullseye 353/18”.

5.7.2.3. C2 provides the Force Accountability to the MSN/CC NLT than Pre-Mass.

5.7.3. TAC C2 will report all Blue “called dead” to the JPRC via mIRC #RED_FLAG_AK_JPRC (primary) or pass data to Airboss 30 minutes prior to debrief (secondary).

5.7.4. TAC C2 Link-16 procedures for kill-removing OPFOR aircraft:

5.7.4.1. Initiate “Neutral General No Statement (NGNS)” for kill-removing OPFOR

5.7.4.2. Transmit “dead” OPFOR tracks on datalink as “NGNS”; no tactical action will be taken against them.

5.7.4.3. TAC C2 drop track files for kill removing OPFOR exiting the ACBT or within 10 NM of a regen airfield.

5.7.4.4. Initiate a new track once the aircraft has reached Point of Origin (POO) criteria AND is no longer squawking “dead”. Re-identify the track IAW ROE.

5.7.4.4.1. Approved early regens meet POO criteria.

5.8. Regens

5.8.1. Blue Air may regen after their “dead” times expire IAW section 5.7 Aircraft Kill Removal.

5.8.1.1. Blue Air will regen with the same weapon state as when called “dead”, minus any A/G weapons/equipment etc. dropped while “ghosting”.

5.8.2. Red Air will regen at regen airfield(s) or regen line IAW JECG coordination. For airfields, Red will regen when within 3 NM of the airfield coordinates. “Dead” Red air will stay greater than 5 NM away from regen airfields until “alive.”

5.9. Real-Time Effects and Air-to-Surface Attacks

5.9.1. Real-Time Effects

5.9.1.1. Air-to-Surface RTO (callsign “BUSHMAN”)

5.9.1.2. Fidelity checks on departure IAW A-G RTO slide in Mass Brief

5.9.1.2.1. All Air-to-Surface munitions employed should be called to BUSHMAN on UHF 277.2 (or IAW Comm Card, if mission planned on an alternate freq).

5.9.1.2.2. BUSHMAN will assess CE of employed weapons IAW 3-1.SHOT KILL and provide real-time feedback of weapons effectiveness.

5.9.1.3. sIADS impacts will be IAW Real-Time Effects Planning.

5.9.1.4. All attacks must be called and acknowledged by BUSHMAN to receive real-time effects.

5.9.1.4.1. Repeat comm until acknowledged.

5.9.1.4.2. Bushman will provide ARM Acknowledgement & NTRK per 3-1 on sIADS.

5.9.1.5. Brevity Terms:

5.9.1.5.1. Splash = Ability to validate weapons impact and desired weapons effect on intended target (i.e. visually or with targeting pod).

5.9.1.5.2. Magnum = ARM shot.

5.9.1.5.3. Magnum High = AARGM MMW-P or ARM PTP shot.

5.9.1.5.4. Timeout = Shooter assesses valid BVR release parameters have been met. Munition has reached termination and impact is obscured or cannot be confirmed.

5.9.1.5.5. Canyon/Buzzer = Jamming with labels.

UNCLASSIFIED

5.9.1.5.6. Update = Request status of DWE for target visually acquired (to include TGP).

5.9.1.5.7. All other terms are IAW ALSA Brevity and 3-1.Shot Kill.

5.9.1.6. Call “magnum (high)” at ARM shot time (Shot-Kill HARM Option 2) with threat, bearing/bullseye, shot settings (TI/NON COOP/SHUT DOWN, GEO DEFAULT/MP) and relative impact time (MM+SS) if known.

5.9.1.6.1. PET shots called with label

5.9.1.6.2. HARMs are assumed SD/GEO OFF unless voiced or coordinated prior.

5.9.1.6.3. Example: Fighter: “(c/s), magnum SA-6 bullseye 353/18, TI, timeout 1+18” -or-

“(c/s), magnum SA-8, bearing 353, SHUT DOWN, GEO MP” -or- “(c/s), magnum PET A”. BUSHMAN: “copy magnum”.

5.9.1.7. Call “splash/timeout” at weapons impact time with ATO target(s)/DT(s) number (primary), JDPI number (secondary), threat system with bullseye or “India label”.

5.9.1.7.1. Example: Fighter: “(c/s), splash/timeout target 31” -or- “(c/s), splash/timeout JDPI 8069A -8069F”.

BUSHMAN: “copy splash” -or- “Pk miss” -or- “copy timeout”.

5.9.1.7.2. Example: Fighter: “(c/s), splash SA-6 bullseye 353/18” -or- “(c/s), timeout India 3”.

BUSHMAN: “copy splash” -or- “Pk miss” -or- “copy timeout”.

5.9.1.8. Call “canyon/buzzer/clam” on/off with label

5.9.1.8.1. Example: Fighter: “(c/s), music A on”. BUSHMAN: “copy music”.

5.9.1.9. Call “update” with JDPI number, threat or component and bullseye.

5.9.1.9.1. Example: Fighter: “BUSHMAN, (c/s) update Fan Song bullseye 353/18”. BUSHMAN:

“alive” -or- “dead”.

5.9.1.9.2. Example: Fighter: “BUSHMAN, (c/s) update target 31”.

BUSHMAN: “alive” -or- “dead”.

5.9.1.10. Also see section 8.2 Air-to-Ground Attack Data Collection.

5.9.2. Surface Threat Kill Removal and Regen

5.9.2.1. BUSHMAN will assess communicated attacks IAW 3-1.shot-kill, apply Pk, and coordinate real-time effects with SAM-1 and/or kill remove threats when attack is assessed as a hit.

5.9.2.2. Pk Misses

5.9.2.2.1. BUSHMAN will respond to “splash” calls with “Pk miss” when appropriate (BUSHMAN will always respond to “timeout” calls with “copy timeout” regardless of hit or Pk miss).

5.9.2.2.2. ARMs assessed as a hit will be assigned a Pk IAW 3-1.Shot Kill.

5.9.2.2.3. Bombs will be assigned a Pk IAW the scenario threat matrix.

5.9.2.3. Surface threat regen criteria is based on JECG Adversary Threat Matrix coordination (Airboss, Intel-1, RED-1, SAM-1, Tac Mentor).

5.9.3. Dynamic Targets (DT)

5.9.3.1. A DT tasking originates at the CAOC (callsign “WARPIG”) or Tactical Operations Center

(TOC) and will be transmitted to TAC C2 or direct to Blue players via voice, Link-16, or mIRC using APPENDIX 5 – RF-A DT Coordination Card 10-Line format or DLER format per JFIRE.

5.9.3.2. Aircraft supported by JTF-49 (callsign “JEFE”) may hear “JEFE DIRECTS” or “JEFE APPROVES”, or direction from JTF-49 ground forces. Targets originating from JTF-49 carry the weight and authority of WARPIG for air-to-ground engagements only on targets that meet TST-2 and below on Table 9.4.3 RF-A Collateral Damage Estimate (CDE).

UNCLASSIFIED

5.9.3.3. If there are discrepancies in any of the targeting products, then coordination with the CAOC is required. The Ground Forces or Aircrew will contact TAC C2 who in turn will coordinate with the CAOC to clarify.

5.10. Jamming/Electronic Warfare (EW)

5.10.1. All EW will be conducted in accordance with the RF-A Comm Plan, Electronic Attack (EA) Authorization and AFMAN 11-214.

5.10.1.1. Contact RF-A Spectrum Management, DSN 317-552-7184 COMM 907-552-7184, for current EA Authorization.

5.10.2. Only training EW settings will be used.

5.10.3. Comm Jamming/Spoofing:

5.10.3.1. Spoofing will only be executed by JECG.

5.10.3.1.1. Successful spoofing events will be discussed in the debrief.

5.10.3.2. Not permitted to affect aircraft in IMC conditions.

5.10.3.3. Allowed from 20 minutes prior to VUL until VUL end (other jamming may occur at any time.

5.10.3.4. Blue Jamming

5.10.3.4.1. Blue may only jam frequencies authorized per the RF-A Comm Plan and EA Authorization.

5.10.3.4.2. Blue will not jam Red C2 or Red RTO COMM frequencies.

5.10.3.4.2.1. To receive credit for jamming Red C2, coordinate to jam an alternate frequency with Airboss IAW the RF-A Comm Plan and include plan/effects on the Real-Time Effects Coordination Sheet (see APPENDIX 8).

5.10.3.5. Red/JECG Jamming Blue

5.10.3.5.1. May be conducted on Blue fight frequencies or Blue interflight frequencies IAW

Airboss and/or SAM-1 direction (to include Have Quick/SATURN).

5.10.3.5.1.1. TWO BEARS/TAC C2 will make any required safety calls on Guard if a fight frequency is being jammed.

5.10.3.6. TABOO/No-Jam Frequencies

5.10.3.6.1. Only frequencies identified on the PACAF Electronic Attack Authorization memo may be jammed.

5.10.3.6.2. The following frequencies will never be jammed:

5.10.3.6.2.1. Guard

5.10.3.6.2.2. Airboss

5.10.3.6.2.3. Eielson Range Control

5.10.3.6.2.4. Blue Check-In/Check-Out

5.10.3.6.2.5. Red C2

5.10.3.6.2.6. RTO

5.10.3.6.2.7. AAR Rendezvous and AAR “Boom”

5.10.3.6.2.8. Air Drop during live cargo or personnel drops

5.10.3.6.2.9. Any non-RED FLAG-Alaska associated frequency

5.10.3.7. See section 6.2 Cease Buzzer for contingencies.

UNCLASSIFIED

5.11. Tactical Command and Control (TAC C2) Operations

5.11.1. Operational RADAR is a requirement for primary TAC C2.

5.11.2. PANTHER Ground Control Interceptor (GCI) assumes all C2 responsibilities pre-VUL until the

ATO-fragged Airborne TAC C2 is on-station with at least RADAR operational.

5.11.3. Once airborne and/or able, TAC C2 will check-in with PANTHER for WORDS and SUC and give system status (“On-Station as Fragged” = min systems required to execute tasked mission).

5.11.4. TAC C2 will collect/track BHA and force accountability (to include tracking Blue called dead).

5.11.5. ATO-fragged C2 will hand off C2 responsibilities IAW the Post-VUL C2 plan (or to PANTHER GCI) when practical after “RED FLAG Knock-it-Off” to RTB in a timely manner.

5.11.5.1. Ensure positive handoff of roles and responsibilities between C2 entities.

5.12. Wounded Bird

5.12.1. Airboss, TWO BEARS, or TAC C2 will transmit “(callsign), you are a wounded bird.”

5.12.2. “Wounded bird” aircraft are limited to 300 knots/30° bank and may not employ weapons or chaff/flare unless the radio notification includes other instructions or limitations.

5.12.2.1. C2: Provide safety of flight directions only. Orbit in place. Discontinue contributions to link-16 surveillance tracks.

5.12.2.2. Tankers may not offload fuel unless required for safety of flight.

5.12.3. “Wounded bird” aircraft may regen and re-enter the LFE after meeting regen criteria IAW sections 5.7 and 5.8.

5.13. Simulated Personnel Recovery (PR) Operations

5.13.1. See section 6.11 for real-world PR procedures. Contact 353 CTS SERE Specialists for PR questions.

5.13.2. Blue players will be ready to execute simulated PR at any time to include OSC duties.

5.13.3. During simulated PR events, Link-16 J3.1 Emergency Points are authorized.

5.13.4. Do not say SAR, CSAR, PR, rescue vehicle (RV), or survivor on the radio. Use the terms

Immediate Shoot-Down and/or [Callsign] 99.

5.13.5. If the Isolated Personnel’s (IP) coordinates are passed verbally over a non-secure radio, it will be encrypted IAW APPENDIX 2 - Authentication and SARNEG Procedures.

5.14. Immediate Shoot-Down

5.14.1. “Immediate Shootdowns” are training scenario injects by white force to introduce a downed wingman into the scenarios without detracting from the other DLOs of the scenario. This simply introduces an additional training task.

5.14.1.1. Used to exercise immediate On-Scene Commander (OSC) responsibilities and assumes a notional wingman of the aircraft in question was shot down.

5.14.1.2. Airboss will transmit on fight frequency “(callsign), Airboss, immediate shoot-down— bullseye XXX/YY, Altitude.”. C2 will also transmit digitally.

5.14.1.2.1. The aircraft at that bullseye or as delegated is now the OSC for a notional formation member.

5.14.1.3. When “Immediate Shootdown” scenarios are introduced, there is a real person on the ground near the B/R/A called by the Airboss playing the role of a survivor. They will assume “[callsign] 99” and will be awaiting contact from air players.

UNCLASSIFIED

5.14.1.4. The pilot, or as delegated, will assume the OSC role IAW APPENDIX 3 – RF-A On-Scene Commander (OSC) Checklist and coordinate bed-down for the IP unless additional guidance is briefed or passed by the Airboss via TAC C2.

5.14.1.5. No air player will be removed from the VUL for Immediate Shootdowns. The callsign of the formation identified will act as if one of their wingmen was shot down and conduct themselves appropriately.

5.14.1.5.1. C2 will pass “OSC checklist complete” to JPRC in mIRC.

5.14.1.6. If committed keep fighting until no threats to element, once threat is neutralized assume

OSC duties.

5.14.1.7. The OSC (and if available, the IP and SERE) will provide full debrief of the event in the

Mass Debrief.

5.14.1.7.1. Example: “BILL flight- Airboss. BILL 99 is an immediate shootdown (Bullseye)

123/45, (Altitude) 23K” Bill 41-44 will make a mark point of the B/R/A called for BILL 99 as if it was one of their formation. They will report to C2 (or appropriate agency identified during mission planning) the location of the survivor and their intentions.

BILL 41 will report to C2 “BILL 99 immediate shootdown MIZZI XYZ. BILL 41 unable OSC at this time. Will contact on egress.”

Or BILL 41 will report to PANTHER “BILL 99 immediate shootdown MIZZI XYZ. BILL 41 unable OSC at this time. Recommend tasking other asset, or re-task BILL flight on egress”.

Or BILL 41 will report to “XYZ agency” “BILL 99 immediate shootdown MIZZI XYZ. BILL 41 established OSC”.

5.14.2. Pre-Planned Simulated Personnel Recovery (PR)/Combat Search and Rescue (CSAR)

5.14.2.1. An IP will be on the ground and will comply with their Evasion Plan of Action (EPA).

5.14.2.1.1. IPs will use “[callsign] 99” with crew position A, B, C etc… as applicable.

5.14.2.2. The IP’s EPA, ISOPREP, and 15-line information will dictate PR mission planning considerations. Contact 353 CTS SERE specialists for PR operations questions.

5.14.2.3. Reference AFTTP 3-3.IPE Attachment 15 for PR mission planning considerations.

5.14.3. “[callsign] 99” SARDOT

5.14.3.1. Coordinates will be per mission planning products. Each SARDOT will be named. Do not say SARDOT on the radio.

5.14.3.2. References to SARDOT will use magnetic heading (do not use true heading).

5.14.3.3. “[Callsign] 99” will report own position to the SARDOT using range (nautical miles) and bearing (degrees magnetic). Example “Dobby 99 posit is 18 miles at 353 mag to Dallas”.

5.14.4. “[Callsign] 99” SARNEG

5.14.4.1. Do not say SARNEG on the radio. Use the term “NEG”.

5.14.4.2. See APPENDIX 2 - Authentication and SARNEG Procedures.

5.14.5. “[Callsign] 99” Authentication

5.14.5.1. All codes used or burned will be tracked and passed to JPRC (via mIRC).

5.14.5.2. “Third letter of the word of the day” will be the pre-programmed authentication question when using the CSEL databurst.

UNCLASSIFIED

5.14.5.3. Color of the day is used in voice authentication - reserved for OSC/SANDY.

5.14.5.4. Number of the day is used in voice authentication - reserved for PJ/Ground Party.

5.14.5.5. The duress word is used in voice or text message to indicate capture is imminent or transmissions are made under duress. It is changed as required with other authenticators.

5.14.5.6. The letter of the day will be used as the NORDO GTAS signal and authenticator.

5.14.5.7. The IP’s ISOPREP data will be used only during recoveries, or after it is reasonable to believe CSAR SPINS data has been burned/compromised.

5.14.6. “[Callsign] 99” Procedures

5.14.6.1. “[Callsign] 99” trainees will develop an EPA facilitating their recovery which will be briefed by SERE.

5.15. HIMARS/PATRIOT/LRASM/TLAM/CYBER/SPACE Assets: Both Live and Synthetic

5.15.1. If participating in the exercise,…