Attachment 6 - 53 WEGI 11-250.pdf

53 WEG I 11-250 1

BY ORDER OF THE COMMANDER 53 WEG INSTRUCTION 11-250

53D WEAPONS EVALUATION GROUP

(ACC)

1 April 2017

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 at: https://cs1.eis.af.mil/sites/eglin/53weg/STANEVAL/default.aspx .

If you lack access, contact 53 WEG/OGV.

RELEASABILITY: There are no restrictions on releasing this publication.

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

Supersedes: WEGI 11-250 01 May 2014 Pages: 76

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.

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. Live/Inert Ordnance Weapons System Checks

1.12. Hung Ordnance

1.13. Orientation Flights

1.14. WEG Low Altitude Flight Policy

1.15. Off-Station Flying

1.16. Quick Check/Arming/Dearming Procedures

1.17. Tyndall RESCAP Procedures

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

Tyndall Fuel Requirements Table 2.3: AIM 7/9/9X Hang/Misfire Procedures Table 2.4: 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. Aerial Gunnery 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 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. Mission Planning

4.3. Briefing

4.4. Radio Procedures

4.5. Callsigns

Figure 4.1: Combat Hammer Callsigns

4.6. Weapons Delivery Communications

4.7. Holding

4.8. WSEP Chase Procedures

4.9. Range Procedures

4.10. VTR Requirements

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

5.8. Jettison Procedures

lightning procedures. Watercraft crews will take action IAW Florida Offshore procedures. If a SSAT offload is in progress when the lights illuminate, complete the offload as expeditiously as possible, secure the SSAT on shore, and take shelter as rapidly as possible. Lightning protection for watercraft at sea or in port, not actively engaged in SSAT offload procedures, will be IAW Florida Offshore procedures.

3.12.3. The 82 ATRS/CC and Det 1, 82 ATRS/CC; or designated representatives, have the authority to determine and direct cessation of activities at the above-mentioned facilities whenever conditions exist that he/she determines are unsafe for drone operations.

MISSION

CLG/VIS

X-WIND/T-WIND

HEAD WIND

QF-16 NULLO

LAUNCH

2000/3 Note 1,2

15/15 20KTS max (any direction)

20KTS max (any direction)

QF-16 NULLO

LANDING

1500/3 Note 1,3

15/15 5 KTS Max Tail w/ fuel >3000lbs 20KTS max (any direction)

20KTS max (any direction)

QF-16 Captive FCS from Main Base

PWC Dash 1 Dash 1

QF-16 Captive FCS - Droneway Ops

1,500/3 Same as NULLO Same as NULLO

CHASE (QF16 manned) 1,500/3 Dash 1 Dash 1

QF-16 PWC Dash 1 Dash 1

E-9A 200/0.5 or published mins (E-9A may use vis only criteria)

Takeoff/Fullstop:

20/15 dry/wet Touch & Go: 15/10 dry/wet Tailwind: 10

Takeoff/Fullstop:

20/15 dry/wet Touch & Go: 15/10 dry/wet Tailwind: 10

SSAT LAUNCH

WEIGHT

LAUNCH

WINDS

RECOVERY

DRIFT/WIND

Subscale Launch w/CHASE

2,000/5 Dash 1 N/A

BQM-167 N/A – Determined by balloon observation

27 kt tailwind 20 kt x-wind 50 kt headwind

80 sec balloon time 5,150 ft drift 15 kt max- land recovery 20 kt max- water recovery

Table 3.2: Drone Operations Weather Minimums

53 WEG I 11-250 5

NOTES:

1. Real-time assessment of weather suitability for drone launch and recovery will be the joint responsibility of the Tango, DMC, and chase using all available sources.

2. WEG/CC can approve 1500/3 NULLO takeoff minimums with the realization that if a situation requiring an immediate drone recovery occurs, the drone may need to be recovered without a chase.

3. Drone may be recovered without chase. Drones may be recovered with weather less than 1500/3 with 53WEG/CC approval.

3.13. Weather Minimums. Table 3.2 above contains existing/forecast weather minimums for unmanned, manned-remote, and manned missions. Subscale limits may vary with configuration.

Reference T.O. guidance for varying configuration limits. There are no technical order ceiling/visibility restrictions for the launch of the SSAT. However, poor conditions affect the ability to sight the balloon used in recovery wind data calculations and the ability to observe critical actions during launch and climbout. The DMC will use the worst case (including gust factor) from the Tyndall weather shop current observation and the real-time anemometer (within the proceeding five minutes) in GRDCS to ascertain actual wind conditions. The responsibility for a launch decision rests solely with the DMC, in coordination with the operations supervisor.

3.14. General Mission Conduct:

3.14.1. Briefing. The lead X-Ray will brief for the mission IAW AFI 11-2QF16 and 82ATRS Standards. The DMC will brief specific ORM concerns and destruct guidance with the controllers.

3.14.2. The 82 ATRS/CC delegates authority to launch, present, and recover drones to the DMC. The DMC will conduct drone operations IAW 82 ATRS Operational Instructions and approved checklists, as well as applicable portions of this document.

3.14.3. All missions will be conducted in a manner which considers protection of life and property first and operational requirements second. Drones with questionable command/control difficulties or emergencies which involve a progressively deteriorating situation will be returned to or held on range until a stable configuration and command/control can be reestablished. Final decision to recover, destroy, or present the drone rests with the DMC.

3.14.4. At Tyndall, personnel will not move vehicles or aircraft onto the drone runway until they have notified Maintenance Operations in Hangar 9310. Once the runway is available for drone operations, no other vehicle will enter the runway without approval from Maintenance Operations in coordination with Launch Operations Maintenance Operations will notify Tyndall tower of Droneway status. At Holloman AFB, personnel will not move vehicles or aircraft onto the drone runway without approval from the control tower (Command Post if Tower is closed).

Once the runway is available for drone operations, no other vehicles will enter the runway without approval from the tower.

3.14.5. To launch a full-scale drone there must be at least 45 minutes of range time remaining and 60 minutes for a two-ship. Subscale launches require 30 minutes range time remaining. This provides sufficient time to launch and present the drone and 10 minutes for recovery with 915 MHz frequency protection. Full-scale recoveries will be completed no later than 30 minutes prior to sunset.

3.14.6. An 82 ATRS chase is mandatory for all NULLO launches. In addition, special test missions of subscale drones and captive full-scale missions may require a chase. The chase pilot will report battle damage for destruct/recovery decisions, verify critical drone parameters during departure and recovery, and report boat positions. Resources required during full-scale drone operations are outlined in Attachment 8.

3.14.7. NULLOs can squawk Mode 1, 2 and 3. Standard Mode 3 is 6171- 6177 unless customer requirements dictate otherwise. Sub-scale drones squawk 6171 - 6176 depending upon which rail they launch from.

3.14.8. Dedicated UHF primary and backup mission frequencies are required for drone operations. For these missions, the Tango, FCS, chase, and RDO/RSO and Range Control will monitor the mission frequency. During NULLO launch and recovery, tower will monitor 308.9 to provide traffic advisories. During drone emergencies, all agencies will initially maintain radio silence on mission frequency with the exception of the FCS controllers, DMC, and drone chase.

3.14.9. For COMBAT ARCHER FSAT missions, a warhead armed Aces chase is desired, but not required.

3.14.10. (Tyndall Only) All unmanned full-scale and subscale missions require a range patrol. The range patrol may be accomplished by scheduling an E-9 or using a mission aircraft.

53 TSS/OS and the 82 ATRS/ADO will notify external agencies that a range patrol is necessary for all test events that utilize unmanned drones.

3.15. Debriefing. The DMC will verbally debrief with the controller(s) and other control team personnel at the FCS facility following all unmanned missions. When deemed necessary due to mission events, the DMC will conduct a thorough debrief with all players. The DMC will fill out a TAFB Form 19 for each mission.

3.16. Drone Launch Corridor Clearance Procedures (Tyndall Only). The Watercraft Branch will provide primary drone launch corridor clearance and will:

3.16.1. Broadcast the following warning at 90, 60, and 30 minutes prior closing launch corridor on very high frequency (VHF) marine channel 16.

3.16.1.1. For subscale launches, "Attention all vessels in the area of Crooked Island, at

53 WEG I 11-250 7

____enter time____Central Standard Time (CST) or Central Daylight Time (CDT) the launch corridor will be closed for Subscale Drone launch over the Crooked Island and Gulf of Mexico Range. The danger area extends 2 miles East and 1 mile West of the cut in Crooked Island and 4 miles South into the Gulf. All vessels are required to remain clear of this restricted area."

3.16.1.2. For full-scale launches, "Attention all vessels in the area of Crooked Island, at ____enter time____Central Standard Time (CST) or Central Daylight Time (CDT) the launch corridor will be closed for Full-Scale Drone launch over the Crooked Island and Gulf of Mexico Range. The danger area extends 2 miles East and 1 mile West of the cut in Crooked Island and 12 miles South into the Gulf. All vessels are required to remain clear of this restricted area."

3.16.2. Broadcast the next workday's scheduled drone launch time at 1600 local on VHF marine channel 16:

3.16.2.1. If there is a drone launch scheduled broadcast: "Attention all vessels in the Panama City area on enter day and date at enter time Central Standard Tim (CST) or Central Daylight Time, the launch corridor will be closed for drone launches over the Crooked Island and Gulf of Mexico Range. All vessels are required to remain clear of this restricted area."

3.16.2.2. If there is not a drone launch scheduled broadcast: "Attention all vessels in the Panama City area there are currently no Drone launches scheduled over the Crooked Island Range for____date. Tyndall Marine Operations Out."

3.16.3. Record the time and content of all broadcasts made in conjunction with drone launch operations on DD Form 1753, Master Station Log.

3.16.4. Provide vessels to perform bay clearance inside St Andrews Sound and conduct corridor clearance south of Crooked Island for all scheduled subscale and full-scale drone launch missions and other missions as required.

3.16.5. Notify the DMC of any vessel(s) whose presence in or near the corridor might cause a delay or cancellation of launch operations. Notification will be on UHF radio (349.7 MHz). If contact cannot be made, marine operations will relay clearance information via telephone.

Attempt to contact the vessel(s) and divert it/them to a safe area.

3.16.6. Record the vessel's name and registration number and any data which will help identify the vessel(s) concerned.

3.16.7. When requested, the boatmaster will submit a written statement detailing the role in attempting to clear the corridor, along with copies of the Marine Masters Operation and Maintenance Log, to the 82 ATRS/CC NLT the first duty day following an incident.

3.16.8. Notify the DMC when unable to perform launch corridor clearance.

3.17. 82 ATRS FSAT Flight Termination Device. The status of the FSAT Safe/Arm Device (SAD) and Flight Termination Device (FTD) depend on their arming status, whether or not the

FSAT / SAD / FTD have been damaged in a mishap/incident, and whether or not fire is involved in the mishap/incident. The status of the FTD and SAD will be determined by the FSAT X-Ray controller in coordination with the Launch leader.

3.17.1. The Arming Status of the FTD / SAD will be in one of three states, IAW definitions below: Fully Safe, Partially Armed, or Fully Armed.

3.17.1.1 Fully SAFE – SAD safety pin IN, FTS Battery Switch OFF, DSP Key Switches SAFE, and SAD ARM Telemetry is SAFE

3.17.1.2 Partially Armed – Any one of these exist:

SAD Safety Pin out - or FTS Battery Switch On - or DSP Key Switches ARM - or SAD ARM Telemetry – ARM

3.17.1.3 Fully Armed – All of these conditions exist:

SAD Safety Pin out - and FTS Battery Switch On - and DSP Key Switches ARM - and SAD ARM Telemetry - ARM

3.17.2 In the event of an emergency, mishap, or unusual incident, the arming status will be passed to Fire Department or EOD on-scene commander before allowing personnel to approach the drone (aborted takeoff, gear collapse on landing, runway departure, etc.). If unable to confirm the FTD / SAD is fully safe, the X-Ray controller must assume the status of the destruct device is either partially or fully armed, and will initially restrict personnel and equipment to stay at least 475 feet away from the drone until the arrival of the Fire Department and EOD.

3.17.3. If the SAD / FTS is ever involved in a fire, immediately evacuate all personnel to a distance of 4000 feet.

3.17.4. If the SAD / FTS is damaged / dropped while partially armed or fully armed, but there is NO fire – initial withdrawal distance is 475 feet.

3.17.5. If the SAD / FTS is damaged / dropped/ while fully safe, but there is NO fire - -initial withdrawal distance is 475 feet.

3.17.6. If the SAD / FTS is partially or fully armed, but there are no malfunctions, damage, or fire: Normal operations and withdrawal distance for essential personnel is zero feet.

3.17.7. If the SAD / FTS is fully safe and there are no malfunctions, damage, or fire:

Normal operations and withdrawal distance is zero feet.

53 WEG I 11-250 9

3.18. Drone Emergency Procedures. Emergency procedures for the drone are outlined in appropriate technical data and are a drone-controller responsibility. Outside agency support will be handled IAW locally established MOA, LOA, or other applicable guidance. Additionally:

3.18.1. Following a mishap/incident the DMC will serve as the on-scene commander with the controllers acting as his liaison until the arrival of the base incident commander. All members of the drone control team will remain at their stations until transfer of on-scene commander duties to the incident commander. The DMC will notify the squadron/Det commander and 53 WEG/SE of any unusual event, emergency incident, mishap potential or actual mishap. The squadron/Det commander will notify the 53 WEG/CC or CV.

3.18.2. For SSAT emergencies that call for deploying recovery chutes, the drone controller may execute the applicable procedures independent of DMC guidance.

3.18.3. For those NULLO emergencies that call for the destruction of the drone, the DMC is the determining authority on NULLO destruction, and method of destruction. The RDO has the authority to destroy the drone, without the DMC’s consent as deemed necessary for public safety.

3.18.4. A NULLO suspected of battle damage will not be permitted off range until a chase has performed a BDA. A non-cooperative SSAT suspected of battle damage will be placed in the chute while on range, as close to the recovery vessel as possible.

3.18.5. The DMC will not declare an emergency for a drone. The DMC will, however, coordinate closely with Tower/RAPCON for the recovery of crippled drones, IAW local guidance. The DMC will declare "Drone Minimum Fuel" and "Drone Emergency Fuel" as defined in 82 ATRS Operating Instructions.

3.18.6. For a controlled, aborted approach at the Droneway, maneuver the drone to the east as to remain in the confines of R-2905B. Specific conditions required for an aborted approach are contained in 82 ATRS OIs. At Holloman, for a controlled, aborted approach to Runway 04, the NULLO will be maneuvered IAW HAFBI 11-250 and 82 ATRS Det 1 OIs/MOA.

3.18.7. Following an emergency situation, similar drones will not be launched without the 53 WEG/CC approval. Dissimilar drones may be launched with 82 ATRS/CC or designated representative approval

3.18.8. Degraded Datalink Communications Procedures. No full-scale or subscale drones will be launched during periods of excessive EMI or with abnormally degraded datalink quality.

3.18.8.1. Whiskey and X-Ray/Yankee experience is the key factor in controlling drones during periods of degraded datalink quality which may be attributed to electromagnetic interference (EMI) or hardware failure. The DMC will consider their experience as the primary reference when determining if excessive EMI or datalink degradation is present. Sound judgment should be applied when determining the ability to present or recover drones during degraded datalink performance. The Air Force, through the DMC, assumes the risk of continuing to operate a drone during periods of suspected EMI. Recognizing the drone’s built in redundancies to perform preplanned escape routines during a loss of carrier; it’s generally preferable to RTB the drone rather than continue to present the drone during periods of sustained EMI. The following steps will be taken upon encountering degraded control datalink performance.

3.18.8.2. When the engineer detects degraded data quality, the drone will enter holding while the degradation is further investigated. If the degradation is severe, the drone will begin an RTB while the Whiskey further investigates.

3.18.8.3. When EMI is suspected, the drone controller, with approval from the DMC, can explore options to climb or descend in holding to determine if an altitude deviation corrects datalink degradation by eliminating the EMI. If an altitude deviation allows drone control, the DMC can explore the option with the Aces LFMC/Project to present the drone at other than a briefed altitude.

3.18.8.4. Time permitting and with 82 ATRS/DO concurrence, the chase aircraft can be launched to help determine the source of the EMI or system malfunction.

3.19. Drone Chase Procedures.

3.19.1. Preflight. Chase aircrews will preflight all chase aircraft (primary and spares) and check in as directed to confirm mission status.

3.19.2. Tyndall drone chase departure. The drone chase aircraft will launch from the main base and fly the boat report and drone chase pickup pattern IAW locally established procedures.

Remain above 1,000 AGL/ASL at all times and 300 KIAS, except where published otherwise.

The drone chase will avoid personnel on the droneway by 500’ and avoid over-flying Bldg 9310.

In the event that holding is required for other than a typical, brief delay, coordinate with RAPCON/Wetstone to hold VFR in W-151.

3.19.3. Holloman drone chase departure. The drone chase aircraft will launch from Runway 25 and proceed directly into the drone pickup pattern. If a lengthy delay is expected, the Drone Chase should hold VFR with Holloman tower, or coordinate with RAPCON to hold on WSMR.

3.19.4. Drone chase pattern. Drone chase pilots will maintain 300 KIAS minimum until aligned with the drone runway. Once aligned with the drone runway, and in a wings level attitude, the drone chase may slow to no slower than 230 KIAS as required to pick up the drone.

Minimum altitude is IAW AFI 11-2QF16 Vol 3. The drone chase pilot will accompany the drone from launch to the range, perform item checks if required, and clear the drone when directed.

53 WEG I 11-250 11

Figure 3.3. Full-Scale Aerial Target Pick-Up Pattern

3.19.5. Drone Rejoin. The chase will maintain altitude separation from the drone (IAW AFI 11-214) until visually acquiring the drone. Rejoins on drones will be conducted in VMC, and will not be conducted below 1000' AGL/MSL.

3.19.6. Drone Chase Weather Penetration. For unmanned drone chase through the weather, the in-cloud visibility must be at least 100 feet to allow the chase to fly in a position to observe the drone while maintaining nose-tail separation. If chase loses visual with the drone, standard lost wingman procedures will apply. If in-cloud visibility is not at least 100 feet, the drone chase may execute a trail departure maintaining known heading and power settings with the drone, ensuring at least 500 feet of altitude separation until VMC and tally with the drone.

Drone chase through the weather may only be conducted within the confines of the W-151 or WSMR complexes.

3.20. Subscale Drone Chase. Chase for subscale missions is not a standard procedure and will only be performed to support specific test mission requirements. Subscale chase profiles and ground tracks will vary to meet strict test objectives. Subscale chase pilots will maintain VMC and visual contact with the SSAT at all times. If weather does not permit maintaining visual contact with the drone, perform standard lost wingman procedures, ensure altitude and flight path deconfliction, and maintain at least 500 feet of altitude separation until VMC can be reached and a rejoin executed.

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

3.21.1. The 82 ATRS/ADO, will assist users with determining critical profile requirements and approval. See Attachment 7, for Critical Profile specifics.

3.21.2. Profiles flown between 50-500 ft MSL/AGL require the user to fund/provide aircraft chase for altitude validation.

3.21.3. Drones operating over open water, in restricted areas or non-congested areas adhere to minimum altitudes published in FLIP AP for that particular special use airspace. Comply with altitude separation requirements in AFI 11-202v3. Do not overfly any person, vessel, vehicle, or structure at less than 500 feet.

3.22. Subscale Drone Operations.

3.22.1. For all SSAT launches, a land-recovery and water-recovery capability must exist.

82 ATRS/CC or the Operations Supervisor in his absence is the approval authority for land-recovery only launches. 53 WEG/CC is the waiver authority when water-only or no recovery options exist.

3.22.1.1. Water-recovery capability is defined as having a drone-recovery boat on station and compatible sea conditions (Attachment 5). Planned water recoveries must be at least 5 NM inside range boundaries. The SSAT flight path must be parallel to or away from the coastline.

The recovery area will be clear of surface vessels other than the SSAT recovery vessel.

Clearance of the recovery area may be performed by the recovery vessel or by mission aircraft.

3.22.2. The drone maintenance contractor will raise the 16-foot red range pennant 30 minutes prior to scheduled drone launch. The pennant will be taken down after the release (or launch) of the last mission drone.

3.22.3. The land recovery area is a four-square mile tract with coordinates 85º 27' west and 85º 29' west by 30º 01' north and 29º 59' north. The DMC will commit subscale drones to a normal land recovery when the following criteria are met:

3.22.3.1. All required SSAT-related systems are operational and target responds to commands.

3.22.3.2. Winds are within limits IAW table 3.2.

3.22.3.3. The SSAT has been stabilized in level flight for at least one minute at proper tech order altitude prior to commanding recovery chutes.

53 WEG I 11-250 13

ATTACHMENT 5

SEA STATE CODES AND WATERCRAFT RECOVERY CAPABILITY FOR SUB-

SCALE DRONES

A5.1. These apply only to sub-scale drone recovery operations. See TAFBI 11-250 for manned operations.

Term Height of Waves (In feet) Sea State Code Calm 0 Smooth Less than 1 1 Slight 1 – 3 2 Moderate 3 – 5 3 Rough 5 – 8 4 Very Rough 8 – 12 5 High 12 – 20 6

Very High 20 – 24 7 Mountainous 25 and higher 8 Confused 9

Recovery Capability by 82ATRS Watercraft

Sea State Code:

0 Through 2 – 100 percent recovery capability.

3 – 0 to 50 percent depending upon wind factor. Potential danger for man in the water. Safe water recovery capability of a downed drone in the proposed shoot area will be assessed by the boatmaster. If boatmaster assesses no water recovery capability, water recovery of a downed drone will not be attempted.

4 – Dangerous on deck. Extremely dangerous for a man in the water.

5 – Water recovery of a downed drone will not be attempted.

6 Through 9 - Drone boats confined to harbor for safety.