Atch_3_WEGI_11-250_1_Mar_2013.pdf

BY ORDER OF THE COMMANDER 53 WEG INSTRUCTION 11-250

53D WEAPONS EVALUATION GROUP (ACC)

1 March 2013

Operations

53 WEAPONS EVALUATION GROUP

(WEG) AIR OPERATIONS

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

ACCESSIBILITY: This publication is available digitally on the 53d Weapons Evaluation Group (ACC) SharePoint https://eglin.eis.af.mil/53weg/default.aspx. If you lack access, contact the publishing manager.

RELEASABILITY: There are no restrictions on releasing this publication.

OPR: 53 WEG/OGV Certified by: 53 WEG/CC

Supersedes: WEGI 11-250 01 Jul 2008 Pages: 84

This instruction sets forth individual responsibilities and procedures pertaining to the conduct of USAF Weapon System Evaluation Program (WSEP) live-fire missions (COMBAT ARCHER, COMBAT HAMMER), non-WSEP live-fire missions, collateral missions, drone operations, range safety, and other 53 WEG activities in accordance with (IAW) COMACC Plan 85, and COMACC Plan 90. Ensure that all records created as a result of processes prescribed in this publication are maintained in accordance with Air Force Manual (AFMAN) 33-363, Management of Records, and disposed of in accordance with Air Force Records Information Management System (AFRIMS) Records Disposition Schedule (RDS) located at https://www.my.af.mil/gcss-af61a/afrims/afrims/.

SUMMARY OF REVISIONS

This instruction has changed significantly since its last release. All agencies/individuals affected by this instruction should review it in its entirety.

https://eglin.eis.af.mil/53weg/default.aspx https://www.my.af.mil/gcss-af61a/afrims/afrims/

2 53 WEG I 11-250

Chapter 1. GENERAL WEG FLYING OPERATIONS

1.1. Purpose

1.2. Applicability

1.3. Changes

1.4. General

1.5. Safety

1.6. Supervision

1.7. Live-fire Crew Rest and Crew Duty Day Requirements

1.8. Flight Plans and Scheduling

1.9. Flight Operations

1.10. High Winds and Sea State Restrictions

1.11. Chaff And Flare Operations

1.12. Live/Inert Ordnance Weapons System Checks

1.13. Hung Ordnance

1.14. Orientation Flights

1.15. WEG Low Altitude Flight Policy

1.16. Off-Station Flying

1.17. Quick Check/Arming/Dearming Procedures

1.18. Tyndall RESCAP Procedures

1.19. 82 ATRS ACBT Support

Chapter 2. COMBAT ARCHER

2.1. Applicabilty

2.2. Live-Fire Agency Pre-Coordination

2.3. Combat Archer Scheduling

Figure 2.1: WSEP Range Scheduling

2.4. Aces Live Fire Daily Mission Planning

2.5. Live-Fire Brief

2.6. Live-Fire Debrief

2.7. Live-Fire Command and Control

Figure 2.2: Combat Archer Command and Control

2.8. GCI Responsibilities

2.9. Live-Fire Employment Procedures

Table 2.3: Tyndall Fuel Requirements Table 2.4: AIM 7/9 Hang/Misfire Procedures Table 2.5: AIM 120 Hang/Misfire Procedures

2.10. Range Safety Procedures

2.11. Drone Control Procedures

2.12. Range Safety Violations

2.13. Range Safety Violation Responsibilities

2.14. Combat Banner Procedures

Chapter 3. DRONE OPERATIONS

3.1. General

3.2. Scheduling

3.3. Tyndall AFB Scheduling

53 WEG I 11-250 3

3.4. Holloman AFB Scheduling

3.5. Hill AFB Scheduling

3.6. Callsigns

3.7. Qualifications

3.8. 82 ATRS and Det 1 Active Military Responsibilities

3.9. 82 ATRS Contractor Responsibilities

3.10. Exchange of Information

3.11. Drone Mission Fuel Planning:

Table 3.1: Drone Fuel Requirements

3.12. Lightning Procedures

Table 3.2: Drone Operations Weather Minimums

3.13. Weather Minimums

3.14. General Guidance/Mission Conduct:

3.15. Debriefing

3.16. Drone Launch Corridor Clearance Procedures (Tyndall Only)

3.17. 82 ATRS Drone Termination Device

3.18. Drone Emergency Procedures

3.19. Drone Chase Procedures

Figure 3.3: FSAT Pick-Up Pattern

3.20. Subscale Drone Chase

3.21. SSAT/FSAT Low-Altitude Procedures (5,000 FT ASL/AGL and Below)

3.22. Subscale Drone Operations

Chapter 4. COMBAT HAMMER FLYING OPERATIONS

4.1. Tactical Control (TACON)

4.2. Situational Awareness Data Link (SADL)

4.3. Mission Planning

4.4. Briefing

4.5. Radio Procedures

4.6. Callsigns

Figure 4.1: Combat Hammer Callsigns

4.7. Weapons Delivery Communications

4.8. Holding

4.9. WSEP Chase Procedures

4.10. Range Procedures

4.11. VTR Requirements

4.12. Weapons Malfunctions

Chapter 5. COMBAT HAMMER OPERATIONS AT EGLIN AFB

5.1. General

5.2. Supervision

5.3. Flight Plans and Scheduling

5.4. Aircraft Publications

5.5. Ground Operations

5.6. MARSA Operations

5.7. Eglin Range Procedures

4 53 WEG I 11-250

5.8. Jettison Procedures

5.9. IP/FE/Emergency Chase Procedures

Chapter 6. COMBAT HAMMER OPERATIONS AT HILL AFB

6.1. General

6.2. Supervision

6.3. Airspace Scheduling

6.4. Aircraft Publications

6.5. Large Force Exercise Coordination

6.6. Ground Operations

6.7. Local Area Hazards

6.8. Crosswind Limitations

6.9. Exployment Operations--UTTR Procedures……………………………………………..51

6.10. Air-To-Air Training……………………………………………………………………...52

6.11. Air-To-Surface Training…………………………………………………………………52

6.12. Recoveries………………………………………………………………………………..53

6.13. Bailout……………………………………………………………………………………53

ATTACHMENT 1: GLOSSARY

ATTACHMENT 2: COMBAT ARCHER SPINS

ATTACHMENT 3: COMBAT ARCHER COMMUNICATION

ATTACHMENT 4: SSAT MISSION AGENCY RESPONSIBILITIES

ATTACHMENT 5: SEA STATES AND WATERCRAFT RECOVERY

ATTACHMENT 6: SSAT LAUNCH AND RECOVERY TRACKS

ATTACHMENT 7: CRITICAL MATRIX

ATTACHMENT 8: FSAT MISSION AGENCY RESPONSIBILITIES

ATTACHMENT 9: FSAT REQUIRED RESOURCES

ATTACHMENT 10: FSAT DRONE CHASE TRACKS

ATTACHMENT 11: FSAT LAUNCH/RECOVERY ABORT TRACKS

ATTACHMENT 12: PRE-NULLO MISSION CHECKLIST NOTIFICATION

ATTACHMENT 13: CRITICAL PROFILE INFORMATION

ATTACHMENT 14: WEEKLY FLIGHT SCHEDULE DISTRIBUTION

53 WEG I 11-250 5

Chapter 1

GENERAL WEG FLYING OPERATIONS

1.1. Purpose. This instruction ensures USAF Warfare Center (USAFWC) operations are accomplished safely and efficiently. The procedures prescribed in this instruction augment Tyndall AFBI 13-204, HILL AFBI 13-201, Holloman AFBI 11-250, and Eglin AFBI 11-201.

Attachment 1 contains a glossary of terms used throughout this instruction.

1.2. Applicability. All members of assigned and associate units under the operational control of the 53 WEG Commander (CC), and participating units under Tactical Control (TACON) of the 53 WG/CC as executed through the 53 WEG/CC, and those contract agencies tasked by this instruction must comply with all its rules and instructions. This instruction is divided into sections applicable to Air-to-Air Weapon System Evaluation Program (WSEP), Air-to-Ground WSEP, and Drone Operations. Instructions contained herein apply to all 53 WEG operations at any location. Where this document conflicts with local regulations, follow local guidance and provide input to 53 WEG/OGV. Commanders will ensure all personnel comply with the applicable portions of this instruction. For the purpose of this document, the term WSEP refers to all WEG assigned and TDY units flying in both COMBAT ARCHER and COMBAT HAMMER. Where guidance applies to only a portion of WSEP, the terms COMBAT ARCHER or COMBAT HAMMER will be used. 83 FWS and 86 FWS may remove chapters and appendices of this document not applicable to their operations.

1.3. Changes. Submit suggested changes to the Stan/Eval Branch (53WEG/OGV) on an AF Form 847, Recommendation for Change of Publication.

1.4. General. The 53 WEG/CC exercises operational control over COMBAT ARCHER, COMBAT HAMMER, and Drone Operations. The 53 WEG/CC delegates operational control for COMBAT ARCHER to the 83 FWS/CC within the guidelines contained herein. The 53 WEG/CC delegates operational control for GCI support to COMBAT ARCHER to the 81 RCS/CC within the guidelines contained herein. The 53 WEG/CC delegates operational control for COMBAT HAMMER to the 86 FWS/CC within the guidelines contained herein.

The 53 WEG/CC delegates operational control for all Drone Operations to the 82 ATRS/CC within the guidelines contained herein. Each squadron commander has waiver authority for their respective operations except where directed otherwise. Each commander will back brief the 53 WEG/CC on all waivers within 24 hours of occurrence.

1.5. Safety. Any deviation from the range safety rules or criteria set down in this instruction will be reported immediately to the 53 WEG/CC.

1.6. Supervision. Each deployed WSEP unit will provide an Operations Supervisor, referred to as “MDS Expert”, who is a qualified aircrew capable of monitoring the unit’s daily flying and assisting the WSEP Ops Sup. The TDY unit’s MDS Expert will be immediately available in the WSEP operations facility to assist local Supervisor of Flying (SOF) and the WSEP Ops Sup, as required. The deployed squadron SOF can also fulfill the role of MDS Expert (if required) based on manning.

6 53 WEG I 11-250

1.6.1. The 53 WG maintains letters of agreement (LOAs) with host base ACC units to coordinate SOF manning. In general, the host ACC unit will provide a SOF during that wing’s flying window. Outside of that, the deployed WSEP units will provide the SOF.

1.6.2. All SOFs must be home-station qualified and attend the SOF briefing provided by WSEP or the host base prior to performing SOF duties during WSEP.

1.6.3. Additional SOF requirements and information is contained in the base specific chapter of this instruction.

1.6.4. Aircrew will notify Aces/Pit Boss/Drone Ops of any aircraft problems, delays, aborts, or other changes to the assigned mission/lineup. Emergencies will be coordinated through the SOF. If the SOF is not of the same Mission Design Series (MDS), the SOF will primarily handle coordination with local base emergency response units, and the Ops Sup/Bookreader will provide MDS specific guidance to the emergency aircrew on the Ops frequency, SOF frequency, or single frequency approach.

1.7. Live-fire Crew Rest and Crew Duty Day Requirements. Individuals performing Pit Boss, Mike, X-Ray/Yankee, Tango, Wetstone GCI, Range Safety Officer/Specialist (RSO/RSS), and Range Destruct Officer (RDO) duties will observe a minimum 12-hour crew rest and maximum 12-hour duty day requirements. The WEG/CC or designated representative may extend duty day up to 14 hrs upon request.

1.8. Flight Plans and Scheduling.

1.8.1. WSEP units may file using local stereo flight plans or by faxing a DD Form 175, Military Flight Plan to Base Operations, as approved by local base procedures. TDY units will coordinate their flying schedules with the host unit’s DO.

1.8.2. File flight plans IAW locally established procedures, but ensure flight plans are filed prior to step. To file or change a clearance after stepping, contact squadron operations or clearance delivery.

1.8.3. The WSEP flying schedule will be the single source for WSEP missions. Units are discouraged from producing their own schedule as additional schedules may contain inaccurate data and lead to confusion. Units will provide WSEP Flight Management personnel with names of aircrew as requested by WSEP Flight Management.

1.8.4. All coordination for airspace and ranges will be done by the FWS/DO. TDY units will not talk directly with host base units without consent of the FWS/DO or Project Manager

(PM).

1.8.5. For continuation training (CT) sorties, TDY units will provide the FWS PM with airspace/range scheduling requests not later than 30 days prior to deployment. Information should include: Turn plan requested.

1.8.1.1 Type of mission requested.

53 WEG I 11-250 7

1.8.1.2. Local unit support requests and reciprocal offerings.

1.9. Flight Operations. All assigned and TDY units will conduct operations IAW locally established procedures. Program Managers are responsible for ensuring TDY units are educated on local flight operations procedures. Where appropriate, more restrictive or amplifying information is contained in the following sections.

1.10. High Winds, Sea State Restrictions, Lightning Procedures, and Bird Watch Conditions. IAW TAFBI 13-204 and WEG In-Flight Guide.

1.11. Chaff and Flare Operations. When authorized, flight leads will ensure chaff/flare is not employed in such a manner as to allow it to drift outside assigned airspace into any corridors or to affect ATC operations.

1.12. Live/Inert Ordnance Weapons System Checks.

1.12.1. Air-to-ground weapons system checks will not be performed until established in the working airspace.

1.12.2. Aircrew will not push the pickle button or squeeze the trigger, except as permitted by AFI 11-214 / MDS specific guidance and established in authorized airspace.

1.13. Hung Ordnance. Hung ordnance is any item attached to the aircraft for the purpose of dropping or firing which has malfunctioned and failed to release when commanded (release pulse sent to station). Failed ordnance is ordnance that was commanded to release, but the release sequence was aborted by the weapon or aircraft prior to a release pulse being sent to the weapon station. Hung secure ordnance is ordnance that remains securely attached to the aircraft in the same position as prior to release attempt. Hung unsecured ordnance is ordnance that remains attached to the aircraft but in some position other than the position prior to release attempt (example: a protruding flare). Reference the local area operating regulation and local In- Flight Guide for applicable procedures when landing with hung ordnance.

1.14. Orientation Flights. Pilots will conduct orientation flights IAW AFI 11-401 (with ACC Sup), 53 WGI 11-401 and 53 WEG OI 11-1 guidance. Orientation flights include distinguished visitor, familiarization and incentive flights.

1.15. WEG Low Altitude Flight Policy. To ensure military aircraft minimize the hazards of operating in the local area, 53 WEG/WSEP deployed aircraft are prohibited from flight operations below 1,000’ MSL along the coastline of the Gulf of Mexico.

1.16. Off-Station Flying. All non-test/evaluation support off-station missions (cross countries and static displays) will be requested via a 53 WEG Form 40, Cross Country Request Form.

This process gives WEG scheduling the information to forward to WEG and WG leadership.

The form will be filled out by the mission commander, and routed through the SQ/DO, SQ/CC, and 53 WEG/CC for approval ASAP prior to the planned mission.

8 53 WEG I 11-250

1.16.1. Mission commanders will contact the SQ/DO or his representative (i.e. duty desk) ASAP after each off-station sortie to relay aircraft status, sortie duration, ETD, and contact telephone number.

1.16.2. Changes to the off-station itinerary will be coordinated through the SQ/DO.

1.17. Quick Check/Arming/Dearming Procedures.

1.17.1. Quick checks, Arming, and Dearming will be performed as close to the runway as feasible prior to departure on all flights, including weekend local launches, launches from deployed locations, and cross-country flights

1.17.2 Do not arm or dearm forward firing ordnance in locations other than designated arm/dearm areas without approval from 53 WEG/CC.

1.17.3. Taxi to the arm/dearm area will be via the most direct route. Pilots will use minimal power settings when entering/exiting the EOR area.

1.17.4 Do not taxi or park in front of aircraft being armed/de-armed with forward firing ordnance. Do not taxi aircraft with hot forward firing ordnance behind passenger-type aircraft.

1.17.5. Anytime it is evident that an aircraft or vehicle will move in front of an aircraft being armed/dearmed with forward firing ordnance, the pilot will advise the arm/dearm crew to discontinue operations until the forward area is clear.

1.17.6. The signal for hot-gun operations will be the “cocked pistol” hand signal to confirm hot-gun during arming and cold-gun during dearming.

1.17.7. When pilots experience an incident/malfunction that may require the aircraft to be impounded or placed in limited access, they will notify Squadron Ops. After leaving the aircraft, pilots will remain at maintenance debriefing facility until personnel from Flight Safety and Quality Assurance have been debriefed and the provisions of AFI 21-101, Chapter 9, Impoundment Procedures, have been met.

1.18. Tyndall RESCAP Procedures. Coordinate with the SOF for E-9 and/or tanker support. The on-scene commander should position the E-9, if available, over the crash site and have the E-9 direct WEG drone recovery boats towards survivor(s). On-scene commander duties should be passed to the E-9 crew when the situation dictates.

1.19. 82 ATRS ACBT Support. 82 ATRS ACBT may be schedule in support of COMBAT ARCHER, COMBAT HAMMER, DoD test and evaluation and other CAF requests. 325 FW requests will be supported when the schedule permits. Schedule assets so as not to interfere with the core drone mission. The 83 FWS and 86 FWS are encouraged to make full use of 82 ATRS assets in the execution of COMBAT ARCHER and COMBAT HAMMER. Scheduling priority for 82 ATRS ACBT is DoD evaluation, ARCHER, HAMMER, other CAF requests (including 325th support), in that order.

53 WEG I 11-250 9

1.19.1. 82 ATRS support aircraft will present multiple profiles to include various EA/EP signatures to the maximum extent possible. Flight leads will make every effort to incorporate an EA option in scenarios that present CAF units with the greatest opportunity for learning.

1.19.2. Rules Of Engagement (ROE)/Training Rules (TRs) will be briefed on all ACBT missions. The following additional QF-4 specific ROE apply:

1.19.1.1 82 ATRS aircraft maneuvering category is "Limited" IAW

AFI 11-214.

1.19.1.2. 82 ATRS aircraft bubble for ACBT and red air is 1000 feet (1,500 feet

LOWAT).

10 53 WEG I 11-250

Chapter 2

COMBAT ARCHER

2.1. Applicability. Guidance contained in this chapter pertains to the operation of targets and the employment of live weapons in the Gulf Range Complex. Guidance in this section does not apply to operations on the White Sands Missile Range (WSMR) or Utah Test and Training Range (UTTR). Range control and safety for WSMR and UTTR for all other DoD and FMS missions are handled through local Operating Instructions (OIs).

2.2. Live-Fire Agency Pre-Coordination

2.2.1. Group Weapons and Tactics Talk (GWATT). A 53rd GWATT will be held NLT the last duty day prior to the WSEP period. 83 FWS/DO will set a time for the GWATT NLT the weekly scheduling meeting three weeks prior to the beginning of the WSEP. The GWATT will review all expected profiles for the upcoming COMBAT ARCHER for both profile development and drone control. The 83 FWS Weapons Officer will ensure that all profiles are completely developed prior to the GWATT for adequate review by all mission participants. The following individuals are required at the GWATT: 83 FWS Weapons Officer, 83 FWS chase pilots, applicable 83 FWS missile analyst, range safety officer (RSO), mission director (MD), FSAT controller, SSAT controller, FSAT DMC, SSAT DMC, 325 MXS/MXMWPC (NCOIC, Asst NCOIC and equipment specialist). Additionally:

2.2.1.1. Critical Profile Review. 83 FWS/PMs will identify and coordinate critical profile approvals IAW AFI 91-223 and Attachment 7 of this document.

2.2.1.2. Complex Profile Review. Although not meeting the requirements for a critical profile, some profiles are complex enough to require the X-Rays to simulate and/or conduct manned profile proofing. 83 FWS PMs will attempt to identify/coordinate complex profiles at least a week prior to the GWATT. The following items should be used by COMBAT ARCHER profile planners as a guide when determining if a complex profile review is required:

2.2.1.2.1. Target altitude above 25,000 feet with maneuvers, including drone saving maneuvers.

2.2.1.2.2. Target airspeed above 0.94 Mach.

2.2.1.2.3. Target requiring split throttles/AB use.

2.2.1.2.4. Any profile requiring two maneuvers in addition to a drone saving maneuver.

2.2.1.2.5. Any target formation above 30,000 MSL at any airspeed.

2.2.1.2.6. Any profile requiring drone control through MU-2’s not previously identified as a critical profile.

53 WEG I 11-250 11

2.3. COMBAT ARCHER Scheduling. Use of 53 WEG assets will be finalized no later than the weekly scheduling meeting for the following week. Changes to the schedule, once established during the weekly scheduling meeting will occur via the AF Form 2407 process.

2.3.1. Range associated assets for COMBAT ARCHER are scheduled through the 53 WEG Scheduling Office. To accomplish a normal COMBAT ARCHER, the WEG is allocated a total of 3+15 hours of W-151 range time, up to 5+45 hours of drone control frequency time, 3+15 hours of E-9 telemetry frequency time, and 2+45 hours of missile telemetry frequency time. These assets are managed to support a 2+00 WSEP Period. These assets are fixed, based on the start of the range time, and are firm based on existing agreements between 53 WEG Scheduling and Eglin Range Scheduling. These times are required for COMBAT ARCHER support personnel and assets to accomplish their respective missions.

Figure 2.1 below shows all range asset allocations.

Figure 2.1: WSEP Range Scheduling

2.3.2. Drone Control Frequency Pre-time. The WEG owns protected 915 MHz and 428 MHz time 3+00/1+45 (FSAT/SSAT) before the start of the WSEP Period. This allows countdown of the drones for takeoff in the WSEP Period, IAW with the contract approved timeline.

FSAT Drone Control Frequencies 5+45 hours total (2+00 before to 0+30 past Range Time)

E - 9 Telemetry Frequencies Start of Range Time to end of Range Time

Missile Telemetry Frequencies 0+30 before WSEP Period end of Range Time

END OF

RANGE

Drone

Control Post - Time 0+15 hrs

WSEP PERIOD: SFC to 70K 2+00 hours

Shooters Takeoff 0+00 in WSEP Period *SSAT Takeoff 0+5 in WSEP Period FSAT Takeoff 0+15 in WSEP Period

0+30 hrs SFC - 7k

NON -

WSEP

Range Time 0+30 hours

SSAT Drone Control Frequencies 4+30 hours total (0+45 before to 0+30 past Range Time)

NON - WSEP RANGE TIME

2+00 to Range Time (FSAT) 0+45 to Range Time (SSAT)

START OF RANGE

E - 9 Pre - Time

0+30 hrs SFC - 70k

12 53 WEG I 11-250

2.3.3. E-9 Range Patrol Pre-time. The WEG owns the range starting at the E-9’s scheduled takeoff time for a period of one hour prior to the WSEP period. The first 30 minutes of this period consists of the range from SFC to 7K. The second 30 minutes consists of the range from SFC to 70,000 feet. This allows adequate time for the E-9 to sweep the range and begin to position for telemetry based on the RSO’s shot container. This also allows time for EMC and Wetstone to sanitize the airspace from other users spilling over their allocated range time. This period is reserved solely for the E-9 and will not be used for live-fire planning. Wetstone will return unused portions of this airspace to non-WSEP fighters working in the W-151 complex.

2.3.4. E-9 Telemetry Frequencies. The WEG owns the requested E-9 telemetry frequencies for the duration of the range time, beginning 1+00 prior to the WSEP Period.

2.3.5. Missile Telemetry Frequencies. The WEG owns the requested missile telemetry frequencies starting 0+30 minutes prior to the WSEP Period. This allows for required missile telemetry checks during ground operations prior to launch.

2.3.6. WSEP Period. This portion of the range period is allocated to all COMBAT ARCHER participants for the live-fire mission. All drones will RTB to be off range no later than the end of the WSEP Period. If less than 3+15 hours of range time is granted, the WSEP period will be reduced to accommodate the required pre- and post-times.

2.3.7. Drone Takeoff. FSATs are scheduled to launch 15 minutes after the start of the WSEP period. SSATs are scheduled 5 minutes after the start of the WSEP period. For combined SSAT/FSAT missions, the FSAT will launch first.

2.3.8. Drone Control Post-time. The WEG owns the range 15 minutes after the end of the WSEP period and receives protected 915MHz and 428MHz time 0+30 minutes after the end of the range period. This time exists to ensure the drone is recovered while the drone control frequency is protected. The timing allows for two go-a rounds and destruction on range if required.

2.3.9. Range Extensions. The Pit Boss may request Wetstone to pursue range extensions real-time with Eglin Mission Control and/or Tyndall Scheduling. Eglin Mission automatically extends all assigned frequencies 30 minutes past the requested range extension.

2.3.10. Drone Scheduling and Use.

2.3.10.1. One-for-One. A COMBAT ARCHER mission requires two missiles airborne to request a drone launch. This does not include the Aces chase live warhead, unless specifically planned as a prebriefed investigative profile. Planned deviations will be requested from the 53 WEG/CC.

2.3.10.2. Spare Targets. 83 FWS schedule requests will delineate minimum mission requirements and not consider use of spare targets. 82 ATRS/DO will schedule spare requirements, per contract, to support mission requirements delineated by the 83 FWS/DO.

Spare targets will be used when:

53 WEG I 11-250 13

2.3.10.2.1. The primary target(s) ground abort.

2.3.10.2.2. The primary target(s) air abort prior to the IP.

2.3.10.2.3. The primary target(s) are not able to meet minimum mission requirements (i.e. – plume pod does not light, or chaff/flare will not dispense).

2.3.10.2.4. Pre-planned requests for use of spare targets, after the schedule has gone firm, will be determined by the 82 ATRS/DO. These requests will be made using the AF Form 2407 process.

2.3.10.2.5. Real-time requests (day of the mission) for use of spare targets, not meeting the criteria above, will be determined by the 82 ATRS/DO. Only the 53 WEG/CC may authorize use of spare target(s) to accommodate an impending/existing one-for-one condition.

2.3.11. Scheduling GCI. The 81 RCS (callsign “Wetstone”) provides all GCI support to units deployed to COMBAT ARCHER and their adversaries. This requirement may be waived during competitive events conducted at TAFB by the 53 WEG/CC after participants have received console familiarization and local procedures training. Only Wetstone personnel, WSEP certified or in WSEP upgrade training, will conduct live-fire missions.

2.3.12. Continuation Training Mission Scheduling.

2.3.12.1. Wetstone GCI will control all CT missions that are greater than a 2 v 2 for WSEP TDY units and their adversaries. In the event of WD manning shortages, the duty MD will notify scheduling of missions that will be done with telephone briefings.

2.3.12.2. CT Debrief. ACMI missions may use the ACMI facility.

2.3.12.2.1. ACMI facility debriefs for 4 or less aircraft start 2 hours after the flight’s start of range time. For 5 or more aircraft, the debrief will start 2+45 hours after the start of range time. ACMI facility debriefs last the same duration as the range time (e.g.; A W- 470A/B 1200 – 1300 range time means a 1400-1500 ACMI debrief time). Contact AMCI with changes to the debrief time as soon as possible.

2.4. Aces Live Fire Daily Mission Planning.

2.4.1. The Aces LFMC (typically uses the callsign Aces 01) is the mission commander and is responsible for daily mission planning to execute the profiles briefed at the GWATT.

14 53 WEG I 11-250

2.5. Live-Fire Brief.

2.5.1. Agency Brief. The Aces LFMC conducts this briefing 2+45 hours prior to WSEP period. Additional Aces chases, 83 FWS Top-3, Pit Boss, Wetstone Mission Director (MD), Wetstone Controllers, Target Controller, , Range Safety Officer/Range Safety Specialist (RSO/RSS), Drone Mission Commander (DMC), X-Ray, 83 FWS Missile Analysts, E-9 (Widget) pilot, Telemetry ™ representatives and MU-2 Pilot (if required) attend this briefing.

2.5.2. Live-fire Brief. All aircrew of firing aircraft (shooters) and chase pilots attend this briefing at the published brief time shown on the schedule (normally 2+15 hours prior to WSEP period.).

2.6. Live Fire Debrief. All debriefs will be in the 83 FWS live-fire briefing room. Unless briefed otherwise, the coordination debriefs start 90 minutes after the last "FOX". Chases, Wetstone, DMC, TM, Pit Boss, E-9 and RSO/RSS (as applicable) will attend. The shooter debriefs start 120 minutes after the last “FOX”. Shooters will obtain WSEP shot sheets during their maintenance debrief in order to record pertinent shot information during tape review.

2.7. Live Fire Command and Control. The Combat Archer command and control structure and relationships are found in Figure 2.2 and the following paragraphs.

Figure 2.2: COMBAT ARCHER Command and Control

WETSTONE

53 WEG I 11-250 15

2.7.1. LFMC. Live Fire Mission Commander. The mission commander for all live-fire missions (typically uses the callsign Aces 01). This individual is qualified by the 83 FWS as an Aces LFMC. The Aces LFMC plans, briefs, conducts, and debriefs all elements of the live-fire mission. The Aces LFMC will appoint the deputy mission commander in the event he falls out.

2.7.2. Drone Mission Coordinator (DMC). A designated 82 ATRS member (callsign

“Mike”) responsible for the oversight of the drone control team. This individual is responsible to the 82 ATRS/CC for the safe conduct of drone operations and its integration into the live-fire mission. The DMC coordinates drone control with the Mission Director (MD) through the Target Controller (TC).

2.7.3. Pit Boss. A qualified Aces LFMC located in the RCF that acts as a WSEP safety observer and pilot liaison to the MD. The Pit Boss may assist the MD in coordinating operations with the 83 FWS Operations Supervisor and is the Aces LFMC’s direct link to the 53 WEG/CC.

The Pit Boss will be in place at Wetstone no later than 30 minutes prior to airspace for WSEP live-fire missions. The Pit Boss will assist the MD as required in orchestrating profiles to achieve the end-game objectives required by the Aces LFMC.

2.7.4. Mission Director (MD). The 81 RCS Air Battle Manager responsible for the overall coordination of all Combat Archer participants IAW the Aces LFMC’s plan. The MD coordinates closely with the range safety officer (RSO), Aces LFMC, and the DMC.

2.7.5. Range Destruct Officer (RDO). A highly qualified individual designated by the 53 WEG/CC to ensure public safety is upheld during a Not Under Live Local Operator (NULLO) mission. The RDO performs duty in the GRDCS room during all NULLO missions and coordinates closely with the drone controllers and DMC for range safety and NULLO flight termination.

2.7.6. Range Safety Officer (RSO). A highly qualified individual designated by the

53 WEG/CC to ensure that all of the parameters for operational safety during live-fire missions are met. The RSO performs duty at Wetstone during all missions in which live or inert munitions are being employed with the exception of Combat Banner. The RSO ensures all live-fires are conducted within the confines of the shoot container.

2.7.7. Target Control (TC). TC vectors the drone on the appropriate FSAT/SSAT control frequency. The TC is the direct link between the DMC/X-Ray and MD. The TC provides drone vectors to the X-Ray and coordinates drone assets and profile management on the DMC hotline. Wetstone (Alternate Mission Controller) controls MU-2 support if required for drone control relay. For simultaneous launch and recovery of subscale aerial targets (SSAT), Wetstone (Alternate Mission Controller) will monitor the drone launch/recovery frequency at T-5 and R-5, when R-2905 is hot. The RSO or Wetstone will survey the restricted airspace for conflicting unidentified air traffic. TC will provide the X-Ray with vectors if traffic conflicts arise.

2.8. GCI (callsign “Wetstone”) Responsibilities. Drone missions that require Wetstone/GCI radar-monitoring and flight-following services will use the following procedures:

16 53 WEG I 11-250

2.8.1. Attend drone mission briefings for missions originating at locations other than

TAFB.

2.8.2 Coordinate the range patrol for the RSO.

2.8.3. Ensure that Wetstone UHF radios are tuned to the mission frequencies and checked for suitability no later than T-60.

2.8.4. Provide positive GCI control for all live-fire and holding aircraft.

2.8.5. Provide positive GCI control for E-9 and MU-2’s assets associated with the WSEP live-fire and other DOD test missions when required.

2.8.6. Control drone chase aircraft; provide “picture” updates to drone chase aircraft; and provide drone chase aircraft with vectors to the assigned chase orbit area after chase breaks away from the drone. NOTE: If the drone chase aircraft remains on the mission frequency, radio discipline and brevity are absolutely essential to safely conduct the mission.

2.8.7. If requested, provide BRAA to join the drone chase aircraft with the drone for battle-damage assessment and recovery.

2.8.8. Provide vectors or assistance to mission photo/chase aircraft upon request.

2.8.9. Provide notification calls on guard UHF/VHF announcing the live-fire activity throughout the WSEP time period avoiding interruption of WSEP communications.

2.8.9.1. “Attention on Guard, Attention on Guard, Wetstone is conducting a live-fire mission in (airspace as released to Wetstone) W151_____/W470____ from ____-____ local, Wetstone out.”

2.9. Live Fire Employment Procedures.

2.9.1. IFF Requirements. Set mode 2 to 40+C/S (e.g. Aces 1 uses 4001, Aces 21 uses 4021, etc.). Lead aircraft will squawk the ATC assigned mode 3 squawk (53XX) for the formation. Subsequent aircraft in the formation will squawk sequentially higher (i.e.; ATC assigns Aces 1 a mode 3 of 5310, Aces 2 will squawk 5311, Aces 3: 5312, etc.) when in non-standard formation to/from/and in the area. The last aircraft in a radar trail departure will squawk his discrete mode 3 until joined. DO NOT accept a squawk which does not allow all flight members to squawk sequentially (e.g.; 5315 for a four ship because number 4 cannot set 5318). These discrete squawks also provide built in ATC squawks for elements or singletons recovering from the area.

2.9.2. Aircraft Publications. COMBAT ARCHER units are responsible for ensuring all aircraft have the following U.S. Flight Information Publication (FLIP) products in each aircraft for local operations:

2.9.2.1. HI East Terminal Approach Procedures.

53 WEG I 11-250 17

2.9.2.2. HI-7/8 and 9/10 enroute charts.

2.9.2.3. Instrument Flight Rule (IFR) Enroute Supplement.

2.9.2.4. Low altitude Volume 19 Terminal Approach Procedures and Terminal

Change Notice (TCN) if applicable.

2.9.2.5. Flight Information Handbook.

2.9.3. VFR Fuel Requirements. VFR bingos will be established to provide a minimum of the following listed fuel weights on initial or at the final approach fix (FAF). Tyndall single runway fuels are per Table 2.3 below. Detached/deployed units will set single/dual runway bingos IAW local operating procedures and the notes to the following guidance.

Table 2.3: Tyndall Fuel Requirements

Note: Single runway fuels are based on diverting to the primary VFR divert location (Eglin AFB for Tyndall AFB) in a clean configuration. If the weather allows for VFR Bingos but the overhead pattern is closed, pilots must ensure they have enough fuel to fly the planned instrument approach including possible ATC delays for sequencing in the instrument pattern.

2.9.4. E-9A Separation. Due to the sensitivity of the E-9A telemetry system and the potential for damage to the system, aircraft with Sierra Band (S band) transmitters aboard will maintain a minimum of one mile separation from the E-9A unless the S band transmitter is turned off.

2.9.5. Range Clearing Procedures. A range clearing is required before live fire operations can take place. This will be accomplished primarily by an E-9 aircraft. In the event of E-9 fallout, participating fighters will conduct the range patrol.

2.9.5.1. E-9 Range Patrol. Wetstone will coordinate range clearing and telemetry activities for the E-9. Once complete, the RSO will designate contacts that are a factor to the shoot container as “Boats of Interest (BOI).” The E-9 will provide continual updates on all BOI throughout the range period. In case of an E-9 Radar outage prior to drone takeoff, the E-9 will perform a manual range patrol until the shooters are airborne.

2.9.5.2. Fighter Range Sweep. As a backup to the E-9 range patrol the MD and the RSO will coordinate the manual range patrol plan. Aces LFMC will be passed the manual range patrol plan via Aces Ops. Boats should be called out off Tyndall TACAN and manually

Runway A-10 F-15 F-15E F-16 (thru Blk 30)

F-16 (Blk 40 & 50) QF-4 E-9 F-22

Dual 2,000 2,000 2,500 1,000 1,200 2,500 600 2,500 Single 2,300 2,500 3,000 1,500 1,600 3, 700 800 4,300

18 53 WEG I 11-250

input into the system. Manual range patrols will commence prior to drone take off. Wetstone will follow the briefed game plan at the MD’s direction. Fighter range patrol procedures are as follows:

2.9.5.2.1. Minimum force size is two aircraft as designated by the Aces LFMC;

additional fighters will expedite locating a suitable shoot container.

2.9.5.2.2. Aircraft separation will be such to provide sufficient visual overlap to accomplish a range patrol.

2.9.5.2.3. Headings are airspace dependent and at the discretion of the RSO.

2.9.5.2.4. Fighters will call all contacts out in bearing and range format from

Tyndall TACAN/INS point with approximate headings. Wetstone will input these contacts on the RCS display for the RSO.

2.9.5.2.5. During periods without E-9 sea surveillance, shoot containers are valid for 30 minute periods; the RSO is responsible to terminate active profiles at the expiration of the 30 minute period. If a shoot container's timing expires, only that portion of the airspace must be re-patrolled.

2.9.5.3. Check-In/Holding. All shooters will initially check-in with Wetstone (hold frequency during FSAT missions and the shoot frequency during SSAT missions) and advise when ready to climb to the briefed holding altitude. Wetstone will provide holding instructions and any live-fire updates via “words”. Shooters will accept close control vectors from Wetstone.

Wetstone will manage the holding pattern based on upcoming profiles and hand-off the next shooter when directed by the MD.

2.9.5.4. Fighter holding definition. Unless otherwise briefed the standard hold dimensions are 15NM legs, left hand turns, altitude and airspeed in accordance with briefed parameters.

2.9.5.5. FSAT Drone chase holding. Wetstone will direct the holding of the drone chase aircraft after drone launch. The drone chase will return to the drone control frequency for the post mission drone rejoin.

53 WEG I 11-250 19

2.9.5.6. Live Fire Employment Flow. An Aces chase will direct the MD to coordinate the next engagement by pairing a shooter with an employment profile (e.g., “Wetstone, cleared to pair Aces 02 on a profile alpha”). An optional “on deck” radio call may be made by an Aces chase to inform GCI of the next aircraft to shoot (e.g. “Wetstone, cleared to pair Aces 02 on a profile alpha, Aces 03 On deck profile whiskey”). The MD will direct an “ID” tasking to the shooting aircraft that is next to employ (e.g., Aces 02, ID group over Bullseye, 22,000, Bogey).

This “ID” radio call signifies to all agencies that the intercept has started. The shooting aircraft will acknowledge the radio call and Wetstone will provide vectors to engage the drone. All live-fire profiles will be conducted IAW the brief and Attachments 2 and 3.

2.9.6. Live Weapons Release Prerequisites. The following must occur prior to employment of ordnance (excluding banner-tow).

2.9.6.1. A Drone IP/Bullseye and Fighter CAP must exist for each air-to-air profile.

2.9.6.2. Aces chase begins the engagement by issuing a “cleared to pair” radio call to the

MD.

2.9.6.3. The MD orchestrates the profile IAW the briefed parameters and issues an “ID” radio call to begin the intercept.

2.9.6.4. The RSO must verify the engagement will take place inside the shoot container and issue a “Commit” through the MD to the Aces Chase.

2.9.6.5. The DMC must verify the drone is on or able to meet required parameters prior to releasing it to the RSO. For FSATs, the DMC releases the drone to the RDO who in turn releases the drone to the RSO. For SSATs, the DMC releases the drone directly to the RSO.

2.9.6.6. The RSO must verify the drone is released, live-weapons release is safe, and issue a “Bandit, Bandit” to the MD.

2.9.6.7. The MD must verify the presentation is IAW the briefed parameters and issue the “Bandit, Bandit” to the Aces chase.

2.9.6.8. The Aces chase must verify all requirements in Attachment 2 are met, and issue a “Hostile, Clear to Fire” call IAW Attachment 3.

2.9.6.9. Shooters must verify targeting has met the requirements in Attachment 2, received a “Hostile, Clear to Fire” call, and is in the required weapons parameters prior to weapons release.

2.9.6.10. For air-to-ground weapons employment, Aces chase is required during WSEP live-fire missions. When air-to-ground weapons are released during CT mission, Range Safety is required and Aces chase is desired.

2.9.6.10.1. Range Safety will build a target and IP IAW the brief from the chase using range safety guidance and weapons footprint data. The target and IP are not required to be co-located with the A/A shoot container.

20 53 WEG I 11-250

2.9.6.10.2. Target and IP coordinates will be passed to fighters on the ground through Pit Boss or Top-3 via WORDS. Weapons release parameters will be passed only if differing from briefed request. All air-to-ground weapon equipped aircraft will accomplish a read back of coordinates on the ground prior to takeoff with DVRs turned on and in the air to ACES Chase/Flight lead.

2.9.6.10.3. PGM Procedures. When Aces chase or flight lead is ready for a “hot” pass, they will transmit “Wetstone/Safety Aces 01 request direct IP.” When “Cleared direct IP” and inside the weapon footprint, range safety will advise Wetstone/fighters “Aces 01, Smack Target”. At this time Aces 01/Flight lead owns safety responsibility for the formation.

2.9.6.10.4. On profiles where air-to-ground weapons and missiles will be employed on the same pass, Aces chase will brief the profile and desired target position along with a backup profile that does not include air-to-ground employment. All A/A WSEP SPINS from WEGI 11-250 still apply. In addition to all WEGI 11-250 requirements, range safety will not give Wetstone authority to pass a “bandit, bandit” until shooters are inside a safety footprint for both the missile and air to ground weapon.

2.9.7. Post Attack. After the engagement is complete and a “knock it off” radio call has been acknowledged by all participants, the Aces Chase (Wetstone by exception) will voice a post attack heading, and send the shooter back to the hold frequency and alternate mission discrete frequency. Post attack fighters should keep their speed up and check in with heading and angels with Wetstone. It is imperative that fighters move out of the shoot container expeditiously so the next intercept may begin. During the post-attack the drone may maneuver off of assigned altitude or vector. Shooters will maintain situational awareness on the drone and ensure altitude or lateral deconfliction.

2.9.8. Alternate Mission/RTB. Shooters will coordinate alternate mission/post shot activities with Wetstone. Shooters will accomplish a battle damage check prior to executing the alternate mission/RTB. Shooters will coordinate recoveries with Wetstone no later than 5 minutes prior. Shooters will remain on Wetstone frequency until cleared to RTB.

2.9.9. Misfire/Hangfire Procedures.

2.9.9.1. If the shooter calls “Fox” and the missile motor does not fire, Aces chase will call “Check Switches.” If a switch error occurred, then shooters may correct the error and fire within parameters (assuming they still have clearance to fire). If the shooter fixes the switch error but is out of parameters he/she will call “Aces XX, terminate parameters”.

2.9.9.2. If the switches were correct, the shooter will call “Aces XX, terminate misfire” and follow appropriate Aces chase direction and misfire/hangfire procedures for the type of missile which malfunctioned. The Aces chase will direct the appropriate terminate/KIO.

Wetstone will gather necessary information, notify the appropriate recovery agency of the shooter's emergency, and keep the affected aircraft in the shoot container or in a safe area on the range for at least five minutes (fuel permitting), or until telemetry has determined that the missile battery has fully discharged. The aircrew will declare an emergency and the SOF/83d Ops Sup will have an explosive ordnance disposal (EOD) team meet the aircraft upon landing.

53 WEG I 11-250 21

2.9.9.3. If a misfire/hangfire occurs with missile(s) in flight, the Aces chase may delay the KIO call until after missile timeout. If this occurs, and barring amplifying dangerous conditions, the Aces chase will issue a “Terminate” to the affected shooter, who will acknowledge the terminate. The shooter will continue to flow with the profile and remain pointed downtrack keeping all other aircraft behind 3/9. Aces chase will issue the KIO after missile to drone passage.

2.9.9.4. AIM-7/9.

2.9.9.4.1. DO NOT POINT AT OTHER AIRCRAFT.

2.9.9.4.2. Master Arm - Off/Safe.

2.9.9.4.3. Evaluate the weapon with TM to determine if the battery was fired.

Battery NOT FIRED Battery FIRED

1. Attempt another shot. 1. Hold 5 minutes (fuel permitting)

2. If second attempt fails, follow Battery FIRED procedures

2. Confirm with TM that the battery is dead

3. Contact SOF & declare IFE

4. RTB via Hung Ordnance recovery

Table 2.4: AIM-7/9 Hang/Misfire Procedures

2.9.9.5. AIM-120.

2.9.9.5.1. “KNOCK-IT-OFF” / MAINTAIN HEADING & FORMATION /

DESCEND TO 10,000 feet MSL or below (i.e.; Stay in the shoot container or a safe area; do not let anyone fly in front of you, and shrink the missile envelope).

2.9.9.5.2. NO SWITCH CHANGES / EVALUATE THE WEAPON.

2.9.9.5.3. PACS / SMS.

2.9.9.5.3.1. Check MSL ARM status (RDY / MAL / REL / “BLANK”).

2.9.9.5.3.2. Check MSL status (AIL / DEGRADED / HUNG / FAILED).

2.9.9.5.3.3. Check quantity remaining.

2.9.9.5.3.4. Battle damage check.

2.9.9.5.3.5. TM will determine if the battery fired/what the missile abort code indicates.

22 53 WEG I 11-250

Battery NOT FIRED Battery FIRED

1. Master Arm – Off/Safe 1. Hold 15 minutes (fuel permitting)

2. Contact SOF & declare IFE 2. Confirm with TM that the battery is dead

3. RTB via Hung Ordnance recovery 3. Master Arm – Off/Safe

4. Contact SOF & declare IFE

5. RTB via Hung Ordnance recovery

Table 2.5: AIM-120 Hang/Misfire Procedures

2.9.9.6. GUN.

2.9.9.6.1. KNOCK-IT-OFF” (Do not point at any other aircraft).

2.9.9.6.2. Master Arm – Off/Safe.

2.9.9.6.3. Battle Damage Check.

2.9.9.6.4. Contact SOF & Declare an IFE.

2.9.9.6.5. RTB via Hung Ordnance Recovery.

2.9.9.7. For all Hung Forward Firing Ordnance recoveries:

2.9.9.7.1. Avoid overflight of populated areas, configure the aircraft over water, and land from a straight-in approach to the outside runway.

2.9.9.7.2. Taxi to the misfire area at the intersection of the Bravo and Golf taxiways (north side of the field). If necessary, pilots will back taxi on the runway and make all turns to swing the nose of the aircraft through North, away from the flightline.

2.9.9.7.3. Taxi back to parking is permitted if weapons personnel can “safe” the missile; otherwise, shutdown in the misfire area.

2.10 Range Safety Procedures.

2.10.1. For full-scale missions, voice communications between the RSO and RDO will be established T-45 minutes on the Safety NET and backup loops. At T-5 minutes in the countdown, the RSO and RDO will remain hot on the Safety NET. If communications between the RSO and RDO fail after launch but prior to initiation of intercept activity, the RSO will call cease fire and try to reestablish communications with the RDO. If communications cannot be quickly reestablished the RSO will call KIO and hold the aircraft clear of the target track. If all communications fail during intercept activity, the RSO will immediately KIO and hold the mission aircraft clear of the target track.

2.10.2. The DMC will immediately notify mission aircraft to “clear the drone” if command guidance or control of the drone is lost. The Aces chase will respond to all “clear the drone”

53 WEG I 11-250 23

calls with a “drone is clear” call. The drone chase will respond to “clear the drone” with a “drone is clear” call, when appropriate.

2.10.3. If GRDCS loses drone tracking information on a full-scale drone, the RDO via the Mike will give drone bearing and range to the X-Ray.

2.10.4. Rapid Release of Damaged FSATs to Aces chase. The following procedures exist for the release of a damaged full-scale drone during COMBAT ARCHER. They are meant to expedite the time between missile impact and Aces chase’s release of live-warhead munitions on the drone. All mission participants will use sound judgment during these times and call KIO if any unsafe situation arises.

2.10.4.1. Upon the “Clear the Drone” call by the DMC, the Aces chase will clear the drone and call “drone is clear.” The Aces chase will gain or retain radar/visual status with the drone. If visual, refrain from transmitting the drone’s status unless queried by the DMC.

2.10.4.2. The Aces chase will transmit “Aces XX Tally the Drone” if visual, or “Aces XX Targeted (BRAA/Bullseye)” if BVR; to indicate to the DMC that he is targeted and awaiting a clearance to fire on the drone. If BVR, the RDO will confirm Aces chase is targeted the drone.

The DMC will confirm the drone status with the X-Ray and determine if the drone can present or must be destroyed.

2.10.4.3. If the drone must be destroyed, but is flyable and time is available to release live-weapons, the RDO will confirm the drone and Aces chase are clear of boat/airborne traffic and issue a “Bandit, Bandit” verbally to the DMC.

2.10.4.3.1. “Flyable” is defined as: not out-of-control and responding to control inputs by the X-ray.2.10.4.4. The DMC will release the drone directly to Aces chase by issuing a “Bandit, Bandit” call on the shoot frequency.

2.10.4.5. Aces chase are to interpret a “Bandit, Bandit” call from the DMC as indicating:

2.10.4.5.1. The drone is hit and not presentable.

2.10.4.5.2. The drone is not able to turn to establish a cine-track or other shot parameters.

2.10.4.5.3. The drone is likely losing altitude/airspeed and conditions are deteriorating.

2.11 Drone Control Procedures: Specific guidance for drone control is contained in technical orders, 82 ATRS OIs, and Chapter 4 of this document. This section applies specifically to those drone control procedures that must be integrated with range control and safety.