Appendix_3_AFI_11-502v3.pdf

BY ORDER OF THE

SECRETARY OF THE AIR FORCE

AIR FORCE INSTRUCTION 11-502, Volume 3

26 APRIL 2012

Flying Operations

SMALL UNMANNED AIRCRAFT SYSTEMS

OPERATIONS

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

ACCESSIBILITY: Publications and forms are available on the e-Publishing website at www.e-Publishing.af.mil for downloading or ordering.

RELEASABILITY: There are no releasability restrictions on this publication.

OPR: HQ AFFSA/A3O

Certified by: HAF/A3/5

(Col Gregg D. Vanderley)

Pages: 62

This publication implements AFPD 10-9, Lead Command Designation and Responsibilities for

Weapon Systems and AFPD 11-5, Small Unmanned Aircraft Systems Rules, Procedures, and

Service. It establishes requirements, responsibilities, and guidelines for operation of Air Force

SUAS by Air Force military and civilian personnel, personnel of other services and foreign personnel assigned or attached to USAF units, and contracted Small Unmanned Aircraft System

Operators (SUAS-O) as stipulated in contracts. This publication applies to the Air Force Reserve

Command (AFRC) and the Air National Guard (ANG.) Headquarters, Air Force Flight Standards

Agency (FOA-AFFSA) is the Office of Primary Responsibility (OPR). This AFI may be supplemented at any level, but supplements must be coordinated with the OPR prior to publication. MAJCOMs will forward copies of supplements to HQ AFFSA Workflow

(hqaffsa.cce@tinker.af.mil) for coordination prior to publication. Refer recommended changes, improvements and questions about this publication to the OPR, on AF Form 847, Recommendation for Change of Publication. Route AF Form 847s through MAJCOM channels

IAW AFI 11-215, USAF Flight Manuals Program. Ensure that all records created as a result of processes prescribed in this publication are maintained in accordance with AFMAN 33-363, Management of Records, and disposed of in accordance with the Air Force Records Disposition

Schedule (RDS) located at https://www.my.af.mil/afrims/afrims/afrims/rims.cfm

Chapter 1—POLICY AND RESPONSIBILITIES 6

1.1. General

1.2. Key Definitions:

1.3. SUAS Operator

http://www.e-publishing.af.mil/ mailto:hqaffsa.cce@tinker.af.mil https://www.my.af.mil/afrims/afrims/afrims/rims.cfm

2 AFI11-502V3 26 APRIL 2012

1.4. SUAS Equipment Custodian

1.5. Compliance

1.6. FAA Advisory Circulars (ACs) and Technical Standard Orders (TSOs):

1.7. ―Properly Certified‖ Aircraft

1.8. Waiver Authority

1.9. FAR Exemptions and Authorizations

1.10. Deviations:

1.11. Notification

1.12. Post-Flight Actions

1.13. Violations

1.14. Dimensional Units

1.15. Maintenance and Disposition of Records

Chapter 2—PREFLIGHT REQUIREMENTS 11

2.1. Preflight Planning

2.2. Fuel/Battery Charge Requirements

2.3. Weather

2.4. Briefings

2.5. Prohibitions

2.6. Foreign Object Damage (FOD) Hazards

2.7. Equipment Required for Flight

2.8. Global Positioning System (GPS) Considerations (If Applicable)

2.9. SUAS Hand-off Procedures

Chapter 3—AIRSPACE & FREQUENCY COORDINATION PROCESS: FLIGHT

PLANS AND FAA CERTIFICATES OF AUTHORIZATION (COA) 17

3.1. General

3.2. Flight Plans

3.3. Airspace

3.4. CONUS National Airspace System (NAS) Operations

Figure 3.1. Controlled Airspace

3.5. Coordination Procedures for OCONUS Host Nation Airspace

3.6. Coordination Procedures for Combat Zone and other Contingency Operations. .. 21

Chapter 4—FLIGHT AUTHORIZATION, APPROVAL, AND CLEARANCE

AUTHORITY 22

AFI11-502V3 26 APRIL 2012 3

4.1. Flight Authorization

4.2. Approval Authority

4.3. Additional Approval and Requirements

4.4. ATC Clearances and Instructions

Chapter 5—GENERAL FLIGHT RULES 23

5.1. Operational Standards

5.2. See and Avoid

5.3. Proximity of Aircraft

5.4. Formation Flight/Cooperative Teaming

5.5. Right-of-Way Rules

5.6. Communication in Flight

5.7. Aircraft Speed

5.8. Communications, Navigation and Surveillance/Air Traffic Management

(CNS/ATM) Systems and Procedures

5.9. Airport Operations

5.10. Altitude Requirements

5.11. Disaster Areas

5.12. Altimeter Settings

5.13. Simulated Instrument Flight

5.14. Simulated Emergency Flight Procedures:

5.15. Touch-and-Go Landings

5.16. Dropping Objects

5.17. Aircraft Lighting (if equipped)

5.18. Aerobatics

5.19. Participating in Aerial Events

5.20. Tobacco Use in Air Force GCS

5.21. Landing with Hot Armament

5.22. Pilot Weather Reports (PIREPs)

5.23. Operating in the Vicinity of Thunderstorms

5.24. Wake Turbulence and Wind Shear

5.25. Volcanic Activity

5.26. Night Vision Goggles (NVG) Operations

5.27. Takeoff with Ice or Frost

4 AFI11-502V3 26 APRIL 2012

5.28. SUAS Traffic Alerting and Collision Avoidance System (TCAS) Operations

5.29. Terrain Awareness and Warning Systems (TAWS)

5.30. Imagery and Sensor Operations

5.31. Airborne Operated Air-Launched Off-board SUAS

Chapter 6—LIFE SUPPORT SYSTEMS 34

6.1. General Information

Chapter 7—VISUAL FLIGHT RULES (VFR) 35

7.1. General Information

7.2. Flight Operations under VFR

Table 7.1. USAF VFR Cloud Clearance and Visibility Minimums (FAA Airspace Class). .. 35

Table 7.2. USAF VFR Cloud Clearance and Visibility Minimums (ICAO Airspace Class). 36

Chapter 8—INSTRUMENT FLIGHT RULES (IFR) 38

8.1. General

Chapter 9—REST AND DUTY DAY LIMITATIONS 39

9.1. Background Information

9.2. Waiver Authority

9.3. Air Force Policy

9.4. Duty Day

9.5. Rest Period

9.6. Scheduling Limitations

9.7. Alertness Management Strategies

Chapter 10—NORMAL OPERATING PROCEDURES 41

10.1. Read Files

10.2. Checklists

10.3. Video/Data Capture

10.4. Working Area

10.5. Communication with external agencies

10.6. Observers

10.7. Wake Turbulence Avoidance

10.8. Night Operations

10.9. Post Flight Requirements

Chapter 11—ABNORMAL OPERATING PROCEDURES 44

AFI11-502V3 26 APRIL 2012 5

11.1. General

11.2. Initial Actions

11.3. Emergency Procedures (EP)

11.4. Adverse Weather

11.5. Impound GCS

Chapter 12—SAFETY/OPERATIONAL RISK MANAGEMENT 46

12.1. General

12.2. ORM Principles

12.3. Authorized Uses

12.4. Human Factors

Chapter 13—REPORTING PROCEDURES 48

13.1. General

13.2. System Reporting

13.3. Mishap reporting:

Attachment 1—GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION 50

Attachment 2—SUAS MISHAP WORKSHEET 56

Attachment 3—SAMPLE OPERATORS FLIGHT LOG 58

Attachment 4—SAMPLE SUAS OPERATIONAL RISK ASSESSMENT CHECKLIST 59

Attachment 5—DOD UAS CATEGORIES 61

6 AFI11-502V3 26 APRIL 2012

Chapter 1

POLICY AND RESPONSIBILITIES

1.1. General. This instruction prescribes basic policy and guidance for operating USAF SUAS.

AFI 11-502, Small Unmanned Aircraft Systems Operations, volumes 1, 2, and 3 draw from the respective AFI 11-202, Flying Operations volumes 1, 2, and 3, with modifications tailored to

Small Unmanned Aircraft Systems; knowledge of the AFI 11-202 series is highly encouraged in order to fully understand the parallels and differences between systems and their supporting instructions.

1.1.1. AFSOC is designated Lead Command for Groups 1-3 UAS (generally referred to as

SUAS: see table A5.1). Unmanned Aircraft (UA) of all descriptions fly in the same environment as manned aircraft. UAS operators must follow rules and procedures, as closely aligned as fielded technology permits, to those followed by crews of manned aircraft.

Coordinating SUAS with other manned/unmanned aircraft and surface fire support/maneuver units requires detailed integration and understanding of the tactical environment.

1.1.2. Units do not have the authority to obligate the Government to purchase, lease, procurement, or contract of any new Air Force SUAS to include UA, Ground Control Station

(GCS), Remote Video Terminal (RVT), Electro-Optical/Infrared (EO/IR), or any other payload prior to coordination with SAF/AQIJ. Include AFSOC/A5KJ, AFSOC/A3OU, and

MAJCOM/A3 as information addressees. Exceptions: Air Force Material Command (AFMC) need not coordinate for unfielded test systems and USAFA need not coordinate for unfielded systems for the purpose of conducting research.

1.2. Key Definitions:

1.2.1. ―Will‖ and ―Shall‖ indicate a mandatory requirement.

1.2.2. ―Should‖ indicates a preferred, but not mandatory, method of accomplishment.

1.2.3. ―May‖ indicates an acceptable or suggested means of accomplishment.

1.3. SUAS Operator. An individual, qualified and responsible for the safe ground and flight operation of the unmanned aircraft and onboard systems. A single SUAS-O will be specifically identified by responsible authority as the Lead SUAS-O. The Lead SUAS-O, regardless of rank, is equivalent to the Pilot-in-Command (PIC) of a manned aircraft and is responsible for all aspects of the mission, regardless of crew position. A SUAS mission includes equipment preparation, planning, briefing, ground and air operations, recovery, mission debriefing, and equipment accountability.

1.3.1. Most units operating SUAS are not traditional flying squadrons; for this reason, this volume is intended to be a common source of directives applicable to SUAS operations, to include, but not limited to:

1.3.1.1. Air Force-specific guidance.

1.3.1.2. Federal Aviation Regulations (FARs).

1.3.1.3. International Civil Aviation Organization (ICAO) Standards and Recommended

Practices (SARPs).

AFI11-502V3 26 APRIL 2012 7

1.3.1.4. Commanders’ Guidance.

1.3.1.5. Tactics, Techniques and Procedures (TTP)/Updated TTP.

1.3.1.6. This volume provides broad guidance and cannot address every conceivable circumstance. SUAS-Os are expected to use their best judgment in order to ensure safe conduct of SUAS operations.

1.4. SUAS Equipment Custodian. Equipment custodian will be identified in writing by the

Squadron Commander. The individual will ensure SUAS equipment is secured and accounted for appropriately IAW the equipments’ level of sensitivity. Maintain an account on SUASMAN and keep all equipment status up-to-date. Individuals will be trained prior to conducting field-level repairs on SUAS equipment.

1.5. Compliance.

1.5.1. The SUAS-O will comply, as applicable, with the following:

1.5.1.1. This volume and MAJCOM guidance.

1.5.1.2. UAS Group-Specific instructions and supplements.

1.5.1.3. Federal Aviation Regulations (FARs) applicable to SUAS when operating within the United States to include the airspace overlying the waters out to 12 miles from the US coast, unless the Federal Aviation Administration (FAA) has excluded military operations.

1.5.1.4. International Civil Aviation Organization (ICAO) Standards and Recommended

Practices (SARPs) applicable to SUAS in international airspace over the high seas, military mission permitting.

1.5.1.5. The specific rules of each individual nation as published in Flight Information

Publications (FLIP) Area Planning (AP) and General Planning (GP) documents and the

Foreign Clearance Guide (FCG). Theater commanders must ensure the content of FLIP accurately convey the rules of each nation within their area of responsibility when different from this instruction.

1.5.1.6. ICAO SARPs when operating in a nation whose rules are not published.

1.5.1.7. Procedures and special notices in FLIP, Notice to Airmen (NOTAM), aircraft technical orders, Air Force directives, MAJCOM directives, and Air Traffic Control

(ATC) instructions.

1.5.1.8. Contractor requirement to comply with Air Force UAS guidance must be stipulated in contracts.

1.5.1.9. UAS leased or loaned to Air Force organizations will be operated in compliance with Air Force guidance.

1.5.2. MAJCOM Supplements. MAJCOM supplements shall not be less restrictive than this instruction. MAJCOM supplements to this instruction must be coordinated with HQ AFFSA prior to publication IAW AFPD 11-5. MAJCOMs will forward copies of supplements to

AFFSA, HQ AFFSA/A3O and HQ AFFSA/A3FV for coordination prior to publication at hqaffsa.a3of@tinker.af.mil.

mailto:hqaffsa.a3of@tinker.af.mil.

8 AFI11-502V3 26 APRIL 2012

1.6. FAA Advisory Circulars (ACs) and Technical Standard Orders (TSOs): IAW AFI 63-

1301, Global Air Traffic Management (GATM) and Navigation Safety system performance and software development processes for non-civil type certificated aircraft must either satisfy civil standards or provide an equivalent level of safety and performance. FAA Advisory Circulars

(ACs) and Technical Standard Orders (TSOs) provide civil standards for the Certification and

Operational Approval of GATM and navigation safety systems.

1.7. “Properly Certified” Aircraft. In many cases this AFI uses the term ―properly certified‖ in lieu of listing all applicable civil equipment and integration standards for CNS/ATM and

Navigation Safety systems. The term ―Properly Certified‖ indicates the aircraft systems comply with appropriate FAA ACs and TSOs or provide an equivalent level of safety and performance.

A list of required civil standards may be obtained from the AFFSA web site

(https://www.mil.tinker.af.mil/affsa/affsa.html – see CNS System Requirements) or aircraft certification matrices maintained by ESC/GA.

1.8. Waiver Authority. Unless otherwise specified, HQ AFFSA/A3O is the waiver authority for this instruction. Waivers to the basic guidance in this instruction will be requested through applicable operations channels to MAJCOM/A3, or equivalent level. MAJCOM/A3s will forward request in message or memo format to HQ AFFSA/A3O, with a copy to HQ

AFSOC/A3OU. Waivers to supplemental guidance will be handled by the MAJCOM agency that generated the supplement. Unless otherwise specified in AFI 11-5 UAS Group-Specific, Volume

3, MAJCOM/A3s are the waiver authority for specific individual SUAS crewmember operations requirements. When the United States Air Force Academy (USAFA) utilizes resources of the

306th Flying Training Group (FTG) (AETC), AETC is the parent MAJCOM. Waivers to this instruction will not exceed 12 months. Units assigned, attached, or under operational control of a combatant commander will request waivers through the Commander, Air Force Forces

(COMAFFOR) who may approve, disapprove, or forward to HQ AFFSA/A3O for action.

1.8.1. HQ AFFSA will approve waivers to this instruction only when:

1.8.1.1. Compliance with this instruction creates a hazard.

1.8.1.2. An essential MAJCOM requirement makes a waiver necessary.

1.8.2. MAJCOMs. MAJCOMs may authorize a waiver to this instruction without prior approval from HQ AFFSA, if doing so is ―essential to the defense of the United States‖ because of a military emergency or an urgent military necessity. MAJCOM designated representatives will notify HQ AFFSA within 72 hours of authorizing a waiver at hqaffsa.a3of@tinker.af.mil or DSN 339-9783. Unless otherwise specified in appropriate

AFI 11-5GP(1, 2, or 3)-SUAS, Volume 3, MAJCOM/A3 is waiver authority for operational procedures. Delegation of waiver authority is at MAJCOM discretion.

1.8.3. Waiver Process. HQ AFFSA will provide only written waivers. Units requiring a waiver will follow the procedure listed below:

1.8.3.1. Units will forward their request for a waiver to this instruction through their chain of command to their MAJCOM/A3. The unit must include a detailed package supporting the request.

https://www.mil.tinker.af.mil/affsa/affsa.html mailto:hqaffsa.a3of@tinker.af.mil

AFI11-502V3 26 APRIL 2012 9

1.8.3.2. MAJCOM/A3 will review the request. If approved, MAJCOM/A3 will endorse the request and forward it to HQ AFFSA/A3O and info copy AFSOC/A3OU at least 30 days prior to the waiver requirement.

1.8.3.3. MAJCOMs will track the currency of all approved waivers to ensure waiver renewals are requested a minimum of 30 days prior to the expiration date. HQ AFFSA will review and respond in writing to MAJCOM waiver requests.

1.8.3.4. Approved waivers will include an expiration date.

1.9. FAR Exemptions and Authorizations. MAJCOMs will obtain FAA exemptions only through HQ AFFSA.

1.9.1. MAJCOM commanders may unilaterally authorize deviation from air traffic rules if it is considered essential to the defense of the United States and there is insufficient time to follow normal procedures. MAJCOMs will notify HQ AFFSA as soon as practical.

1.9.2. An ATC clearance is not authority to deviate from this instruction.

1.10. Deviations:

1.10.1. SUAS-Os may deviate from any flight rule when:

1.10.1.1. An in-flight emergency requires immediate action.

1.10.1.2. Deviation is required to protect lives.

1.10.1.3. When safety of flight dictates. Note: Consideration of hazards created must be factored into a decision to deviate. Preservation of the UA is not paramount.

1.11. Notification. When deviating from an ATC clearance, the SUAS-O will notify ATC of the action taken as soon as possible.

1.12. Post-Flight Actions. The following post-flight actions shall be taken in the event of a deviation from a flight rule and/or when given traffic priority by ATC in an emergency:

1.12.1. The SUAS-O will notify the immediate supervisor as soon as practical and will make a detailed written record within 24 hours of the incident IAW Attachment 2.

1.12.2. The unit will keep a copy of that record and be prepared to provide that record to the appropriate investigating authority and HQ AFSOC/A3OU IAW the AFIs listed in paragraph

1.12. The record will be kept for one year from the date of the incident.

1.12.3. Minor deviations from assigned airspace or mission profiles that do not qualify for formal reporting and do not result in a Hazardous Air Traffic Report (HATR) are to be reported using the format in Attachment 2. Complete all information except the individual’s name/unit and submit to HQ AFSOC/A3OU for trend analysis purposes. Exception: AFMC is lead command for test operations.

1.13. Violations. A violation may result when an Air Force SUAS deviates from flight rules.

FAA ATC facility deviation reports involving an Air Force SUAS are processed IAW AFI 13-

201, Air Force Airspace Management. Air Force air traffic control facility deviation reports involving Air Force SUAS are processed IAW AFI 91-202, The US Air Force Mishap

Prevention Program. Violations that occur in the airspace of foreign nations are handled IAW the procedures of that nation.

10 AFI11-502V3 26 APRIL 2012

1.13.1. The names of the operators will not be released to non-USAF agencies without the permission of the Air Force Representative to the FAA (AFREP) coordinating the investigation.

1.14. Dimensional Units. Visibility distances are in statute miles (SM). All other distances referred to in this instruction are in nautical miles (NM) unless otherwise identified.

1.15. Maintenance and Disposition of Records. Maintain records IAW Air Force Manual

(AFMAN) 33-363, Management of Records. Dispose of records IAW Air Force Records

Information Management System (AFRIMS) Records Disposition Schedule located at https://www.my.af.mil/gcss-af61a/afrims/afrims/.

https://www.my.af.mil/gcss-af61a/afrims/afrims

AFI11-502V3 26 APRIL 2012 11

Chapter 2

PREFLIGHT REQUIREMENTS

2.1. Preflight Planning.

2.1.1. SUAS-Os will accomplish preflight planning. Operators will acquaint themselves with all information, procedures and rules appropriate to the SUAS and the mission. This should include:

2.1.1.1. Appropriate sections of the aircraft Technical Order (T.O.), Technical Manuals

(TM) or equivalent manufacturers’ publications and MAJCOM mission-specific guidance

(e.g. FCIF and SIIs).

2.1.1.2. All relevant information, to include NOTAM and GPS NOTAMs, found at https://www.notams.jcs.mil. When operating in deployed locations, contact the Space

Duty Officer at the AOC for current GPS and SATCOM performance, interference, and jamming information.

2.1.1.3. Flight Information Publications (FLIP) appropriate to the specific SUAS and mission, including appropriate sectional aeronautical charts or Portable Flight Planning

System (PFPS)/Falcon View with FAA/ICAO airspace and/or display of approved working area boundaries (whichever is more restrictive). Ensure PFPS is updated with current Charts, DAFIF/eCHUM.

2.1.1.4. Airfield Suitability and Restrictions Report (ASRR), Special Departure

Procedure (SDP) information, and Jeppesen Military Chart Service information.

MAJCOMs will provide guidance on the use of additional Airfield Suitability and

Restrictions Report (ASRR), Special Departure Procedure (SDP) information, and

Jeppesen Military Chart Service, as required. MAJCOMs will establish procedures to ensure personnel can access and use the ASRR. SDP and Jeppesen Military Chart Service information are available at commercial websites. The MAJCOM Standardization and

Evaluation office may obtain usernames and passwords from HQ AFFSA/A3OF. The

ASRR is available at https://www.afd.scott.af.mil.

2.1.1.5. Alternatives available if the flight cannot be completed as planned.

2.1.1.6. Departure, en route, destination, and alternate weather observations and forecasts.

2.1.1.7. Fuel/battery charge requirements per appropriate technical manual.

2.1.1.8. Maximum operating altitudes, minimum safe altitudes, visual line-of-sight, and data link line-of-sight considerations for the planned route of flight and area of operations.

2.1.1.9. Loss-of-Link procedures coordinated through ATC and Range Control agencies.

2.1.1.10. Takeoff and landing limitations.

2.1.1.11. AFI 11-5GP(1, 2, or 3)-SUAS, Volume 3, SUAS Operations Procedures.

https://www.notams.jcs.mil/ https://www.afd.scott.af.mil/

12 AFI11-502V3 26 APRIL 2012

2.1.1.12. Applicable airfield advisories, bird advisories and hazard information, available through Automated Terminal Information System (ATIS), Internet sources, or as disseminated locally.

2.1.1.13. Operational Environment Assessment. An assessment as to the operational viability which may or may not be based on one or more factors (e.g., intel, weather, legal, C2, terrain, SA).

2.1.2. Due Regard. In international airspace, when operationally necessary, SUAS-Os are authorized to conduct military flight operations with due regard for the safety of navigation of civil traffic IAW FLIP GP ―Operations and Firings over the High Seas.‖ Due Regard operations may be conducted under the following restrictions:

2.1.2.1. In Visual Meteorological Conditions (VMC); or

2.1.2.2. Within radar surveillance and under positive communication control of a surface or airborne radar; or

2.1.2.3. Outside the limits of controlled airspace.

2.2. Fuel/Battery Charge Requirements.

2.2.1. General Information. The SUAS-O will ensure sufficient fuel/battery charge is available on board the aircraft to comply with the requirements of this instruction and safely conduct the flight. Before takeoff the aircraft must have enough usable fuel/battery charge aboard to complete the flight to a final landing, either at the destination airport or landing zone or the alternate airport (if one is required), plus the fuel reserves. (Exception: Group 1

SUAS have no alternate airport or reserve fuel requirement and are exempt from the requirements of paragraphs 2.2.2 and 2.2.3. Land the UA before reaching minimum useable battery capacity.)

2.2.2. Alternate Airport Required. Reserved for future operations.

2.2.3. Fuel Reserve. The SUAS-O must ensure the aircraft is carrying enough usable fuel on each flight to increase the total planned flight time between refueling points by 10 percent

(up to a maximum of 45 minutes for fixed wing or 30 minutes for helicopters) or 20 minutes, whichever is greater. To compute fuel reserves:

2.2.3.1. For reciprocating engine-driven aircraft and helicopters, use fuel consumption rates for normal cruising altitudes.

2.2.3.2. For turbine-powered aircraft use fuel consumption rates that provide maximum endurance at 10,000 ft. Mean Sea Level (MSL).

2.2.3.3. If the MAJCOM authorizes holding (instead of an alternate airport) for a remote or island destination, do not consider the prescribed holding time as part of the total planned flight time for computing fuel reserve.

2.2.4. Flight Logs. The following are the approved types of flight logs:

2.2.4.1. AF Form 70, Pilot’s Flight Plan and Flight Log.

2.2.4.2. MAJCOM-approved form.

AFI11-502V3 26 APRIL 2012 13

2.2.4.3. Approved computer-generated flight log. The lead command will approve flight-planning software to meet SUAS group-specific training and operational requirements.

2.2.4.4. Flight planning computations annotated on a navigation chart.

2.2.5. Minimum/Emergency Fuel Advisory. When operating in FAA airspace, SUAS operators will declare minimum/emergency fuel to the controlling agency when in their judgment the aircraft may land at the intended destination with less than the required emergency fuel reserve.

2.3. Weather.

2.3.1. The SUAS-O will obtain sufficient weather information to safely conduct the flight and comply with this instruction. Units employing SUAS should refer to the Flight

Information Handbook (FIH) for Operational Weather Squadron (OWS) contact information.

When necessary, record the appropriate weather information on a DD Form 175-1, Flight

Weather Briefing. The following weather sources are authorized:

2.3.1.1. US Military Weather Services.

2.3.1.2. Approved weather sources listed in the MAJCOM supplement to this instruction or UAS Group-Specific, Volume 3.

2.3.2. SUAS-O of Group 1 UAS are exempt from the weather briefing requirements of paragraph 2.3.1. Group 1 SUAS-Os must have reasonable cause to believe that the local weather conditions will permit successful employment and operations will be in compliance with applicable range directives, operations orders, FAA Certificates of Authorization

(COA), or other governing directives.

2.3.3. Weather Considerations. All SUAS mission planning requires careful attention to weather and its effects on the UA during flight operations; particular attention should be paid to temperature, winds, precipitation, and hazardous weather phenomena. These factors include, but are not limited to:

2.3.3.1. Wind effects on launch, navigation legs, loiter, and landing. Operators must keep in mind small unmanned aircraft avionics may be more sensitive to turbulence.

2.3.3.2. Wind effects on acoustic signature of the UA at the target.

2.3.3.3. Effects of thermals on altitude, station-keeping and image stability.

2.3.3.4. Restrictions to visibility (fog, smoke, haze, precipitation, sun angle) and effects on observation of the UA and UA sensor capability.

2.3.3.5. Timing and effects of thermal crossover on sensor ability.

2.3.3.6. Temperature extremes and its effects on aircraft, payloads, and batteries.

2.3.3.7. Effects of high humidity on internal and external payloads (sensors).

2.3.3.8. Effects of precipitation on payloads, batteries, and electronics.

2.3.3.9. Hazardous weather (i.e., thunderstorms, turbulence, icing, clouds, precipitation, and poor visibility during launch and recovery) pose hazards to SUAS operations. Present

SUAS design and payload limitations do not include any sort of weather avoidance system; SUAS-Os rely on forecast weather and personal observations.

14 AFI11-502V3 26 APRIL 2012

2.4. Briefings.

2.4.1. The lead SUAS-O must ensure each crewmember is briefed on items affecting safety or mission completion. These briefings will include, but need not be limited to:

2.4.1.1. Emergency procedures.

2.4.1.2. Airspace/working area and frequencies authorized for operations and method of complying with restrictions.

2.4.1.3. Precautions and restrictions.

2.4.1.4. Special procedures and instructions for use during training, formation, or operational missions.

2.4.1.5. Prohibitions listed in paragraph 2.5.

2.4.2. Briefing Guides. MAJCOMs may develop briefing guides. Use of briefing guides is not mandatory, but all applicable items in the briefing guides must be adequately briefed by the SUAS-O or other members of the crew. Units may augment these guides as required for mission accomplishment.

2.4.3. Briefing Times. Start briefings in sufficient time to complete the briefing prior to flight operations.

2.4.4. Mission Brief. All crewmembers scheduled to fly the mission will receive a mission briefing prior to assuming control of the UAS.

2.4.4.1. Brief an alternate mission for each flight (if applicable).

2.4.4.2. Mission elements and events may be modified and briefed while the UA is airborne as long as changes do not compromise flight safety. Do not fly non-briefed missions and/or events. The SUAS-O will ensure all crewmembers acknowledge all changes.

2.4.5. Mission Debrief. After changeover or landing, debrief all missions.

2.5. Prohibitions. The following prohibitions apply to all individuals in vicinity of the GCS.

Until engineering evaluations are complete, the provisions of paragraph 2.5. will apply to UAS ground segments including the control element and all associated communication facilities.

2.5.1. Electronic Devices. This section provides guidance on the use of electronic devices during flight operations. NOTE: Standard SUAS electronic equipment undergoes extensive design and testing to ensure compatibility. Almost all electronic items produce electromagnetic (EM) energy, thus creating potential interference with sensitive antenna-connected receivers. Transmitting devices produce much higher EM environments; these can potentially interfere with any SUAS electronic equipment (ground or air). For the purposes of this instruction, ―electronic devices‖ are any electronic devices not electrically interfaced with existing SUAS equipment.

2.5.1.1. Authorized Portable Non-transmitting Devices.

2.5.1.1.1. Hearing Aids.

2.5.1.1.2. Heart Pacemakers.

AFI11-502V3 26 APRIL 2012 15

2.5.1.1.3. Electronic watches, hand-held nonprinting calculators, portable tape players that do not have a recording capability (such as Walkmans, etc).

2.5.1.1.4. Electric Shavers.

2.5.1.1.5. Equipment certified by ASC/ENAE, 2530 Loop Road West, Wright

Patterson AFB (WPAFB) OH 45433-7101, dsn 785-8929 or 785-2860.

2.5.1.1.6. Still photography cameras (not including digital cameras).

2.5.1.2. Other Devices. Other devices include land mobile and tactical radios, cellular phones, pagers, wireless internet capable devices and similar devices. From the time the aircraft is readied for launch or leaves its parking spot for departure until recovered or parked after landing, SUAS-Os must mitigate any risks associated with Electromagnetic

Interference (EMI) from other devices by moving required devices a sufficient distance so as to prevent EMI, turning the device off, or moving the Ground Control Station

(GCS). Exception: If an EMI analysis has been completed and approval granted for the specific device to be used in the GCS, the above restrictions need not apply.

2.5.2. SUAS-O Responsibility. The SUAS-O will prohibit the use of any device suspected of creating interference with any component of the UAS or that causes crew distraction.

2.6. Foreign Object Damage (FOD) Hazards. MAJCOMs will provide guidance on the wearing of wigs, hairpieces, ornaments, barrettes, pins, clips, other hair fasteners, or earrings in the SUAS ground segment, and at the launch and recovery area. Procedures must ensure operators wearing these items do not create a FOD hazard.

2.7. Equipment Required for Flight. SUAS, designed for automatic flight, typically incorporate self-stabilizing subsystems. All equipment necessary for automatic flight is required for operations. Note: The minimum required displays for emergency manual recovery are:

airspeed, altitude, heading and last known position.

2.7.1. Flight Instrumentation. Primary flight instrumentation must provide full-time display of attitude, altitude, and airspeed information and the capability to recognize, confirm, and recover from unusual attitudes. Information must be positioned and arranged in a manner enabling an effective crosscheck.

2.7.1.1. The following flight instrumentation must always be displayed and illuminated during night operations:

2.7.1.1.1. Climb/Dive Angle (or pitch and vertical velocity). Exception: Group 1

UAS may use the sensor display for attitude reference.

2.7.1.1.2. Bank Angle. Exception: Group 1 UAS may use the sensor display for attitude reference.

2.7.1.1.3. Barometric Altitude.

2.7.1.1.4. Indicated or Calibrated Airspeed.

2.7.1.1.5. Prominent Horizon Reference. Exception: Group 1 UAS may use the sensor display for attitude reference.

2.7.1.1.6. Heading.

16 AFI11-502V3 26 APRIL 2012

2.7.1.1.7. Fault indications to include lost communication links.

2.7.1.2. Electronic Flight Displays. Many modern instrument displays allow the SUAS-O to optimize GCS instrumentation for a particular mission by de-cluttering, removing or relocating presentations. In some cases, a SUAS-O can omit elements necessary for basic attitude awareness and aircraft control. Regardless of the type aircraft, mission, or mission phase, attitude awareness and paragraph 2.7.1 instrumentation are a full-time Air

Force mission requirement.

2.8. Global Positioning System (GPS) Considerations (If Applicable). A GPS Notice

Advisory to NAVSTAR Users (NANU) is an advisory message to inform users of a change in the GPS constellation. These messages are released 72 hours in advance for planned maintenance. These messages are also used to notify users of unscheduled outages. General

NANUs can be used to disseminate general GPS information. NANUs will be checked if intending to operate a GPS-reliant unmanned system. A source is:

http://celestrak.com/GPS/NANU/

2.8.1. Operators will attempt to verify satellite availability prior to using GPS as the basis of flight operations. Satellites that will become unavailable during the flight should be manually deselected, if possible.

2.8.2. A GPS predictive tool can be found at http://augur.ecacnav.com/. This resource should not be used to replace NANUs, but as a preliminary mission planning tool or in the event Notice Advisory to NAVSTAR Users (NANU) are unavailable in the operational area.

2.8.3. Units will develop procedures to disseminate information about GPS reliability to operators in the field.

2.9. SUAS Hand-off Procedures. Detailed procedures for hand-off of airborne UAs between ground control stations will be included in each SUAS operator’s manual or established in local operating procedures. These are the minimum items that must be accomplished prior to launch of the UA:

2.9.1. Select time and location for hand-off.

2.9.2. Select a safe recovery area for the UA.

2.9.3. Identify a method to confirm positive transfer of control between operators, i.e., voice, UA maneuvering, etc.

2.9.4. Brief all participants on the contingency plan for unsuccessful UA hand-off.

2.9.5. Identify and confirm specific equipment settings, required at each GCS, for hand-off.

http://celestrak.com/GPS/NANU http://augur.ecacnav.com/

AFI11-502V3 26 APRIL 2012 17

Chapter 3

AIRSPACE & FREQUENCY COORDINATION PROCESS: FLIGHT PLANS AND FAA

CERTIFICATES OF AUTHORIZATION (COA)

3.1. General. SUAS operations are conducted only in authorized airspace. SUAS operating characteristics and systems capabilities, mission requirements, and SUAS Crew qualifications drive specific airspace requests. Without a certified ―Sense and Avoid‖ capability, separation from other aircraft is accomplished by mitigating measures such as segregated operating areas, altitude blocks, or external observers. For SUAS operations in the National Airspace System

(NAS) outside of Warning and Restricted areas refer to paragraph 3.4. Operations conducted within Restricted or Warning Areas (or within a theater of operations under combat airspace control measures) require only coordination between responsible organizations. SUAS-Os shall be appropriately qualified (or directly supervised by an instructor) in order to conduct operations within the class of airspace authorized for operations.

3.2. Flight Plans. There is no file and fly provision for SUAS. This paragraph is reserved for future development.

3.3. Airspace. Airspace managers may resolve an airspace conflict by the use of time separation, altitude separation, lateral separation, relocation of one of the airspace users, elimination of one of the users, or by concurrence of the approving authorities (range, airspace, and participating units) to accept the assessed risk of simultaneous operations. SUAS-Os and mission planners will use the procedures in paragraphs 3.4. – 3.6. to facilitate the coordination/deconfliction process. SUAS-Os will comply with the following:

3.3.1. FAA Documents (e.g. FAAN JO 7110.512.). Note: FAA Advisory Circular 91-57, Model Aircraft Operating Standards, does not apply to the operations of SUAS intended for military use.

3.3.2. DOD-FAA MOAs.

3.3.3. ICAO regulations.

3.3.4. Host country rules, regulations, and laws.

3.3.5. Military regulations (e.g. AFI 13-204, Functional Management of Airfield

Operations).

3.3.6. DoD FLIP (e.g. General Planning Guide, Area Planning Guides).

3.3.7. Local flight regulations and procedures (e.g., Base Flying Regulations).

3.3.8. SUAS operations manuals, checklists, and SOP.

3.3.9. Frequency Deconfliction directives (contact MAJCOM/A6 Frequency Manager and

Base/Range Frequency Manager).

3.3.10. Description of operating area or a depiction, showing agreed working area boundaries/limits. Consider identifying a buffer zone to prevent exceeding cleared limits.

3.4. CONUS National Airspace System (NAS) Operations.

18 AFI11-502V3 26 APRIL 2012

3.4.1. Units will coordinate use of airspace within the National Airspace System (NAS)

IAW this chapter and Federal Aviation Administration (FAA) directives. SUAS operations may be conducted outside of restricted airspace and warning areas only with FAA authorization in the form of an FAA Certificate of Waiver or Authorization (COA) or IAW other established FAA agreements. A DOD/FAA Memorandum of Agreement (MOA), dated

24 Sep 07 permits Group 1 UAS operations in Class G airspace without a COA. UAS operations requiring a COA or operated IAW the Class G provisions of the current

DOD/FAA MOA shall contact AFSOC/A3OU through their appropriate MAJCOM to obtain assistance with a COA or the Class G notification. (Exception: AFMC/A3O will process all

COAs for AFMC RDT&E missions and units in lieu of procedures below and will forward info copies of approved COAs to AFSOC/A3OU.) For planning purposes, a unit submitting a COA should anticipate a minimum of 70 business days for processing the COA once the

COA has been submitted to AFSOC. AFSOC requires ten business days for mission plan approval, COA on line account issuance, COA review, etc., and the FAA requires 60 business days for their process. For Class G notifications, AFSOC/A3OU requires a minimum of three business days prior to the mission. AFSOC/A3OU will assist the requesting unit to ensure a NOTAM is issued NLT 24 hours prior to the Class G operation.

Note: FAA authorization/approval of a COA is not guaranteed. Units requesting FAA approval to operate SUAS will follow the guidance below:

3.4.1.1. AF units must request authorization/approval for SUAS operations outside of restricted airspace or warning areas through their appropriate MAJCOM POC.

3.4.1.2. If approved, the MAJCOM will forward the request to AFSOC/A3OU via email to AFSOC.A3OU.WF@Hurlburt.af.mil. If the request is disapproved, the MAJCOM will notify the unit and provide the rationale for disapproval.

3.4.1.3. Upon receipt of MAJCOM approval, AFSOC/A3OU will issue a COA on-line account to the unit (without commit authority). A COA on-line account is required for both COAs and for Class G notifications IAW the current DOD/FAA MOA.

3.4.1.4. Unit requesting the COA or a Class G notification will input the information into the FAA COA on-line system and notify AFSOC/A3OU via email to

AFSOC.A3OU.WF@Hurlburt.af.mil that the COA application or Class G notification information is complete.

3.4.1.5. AFSOC/A3OU will review the COA application and/or Class G notification for accuracy to include, but not limited to:

3.4.1.5.1. Airworthiness statement.

3.4.1.5.2. Medical qualifications (both observers and operators).

3.4.1.5.3. Training qualifications (both observers and operators).

3.4.1.5.4. System and operational information.

3.4.1.6. Once the COA application and/or Class G notification is complete, AFSOC/A3OU will commit the COA/Class G notification to the FAA and will notify the unit and the MAJCOM with the COA case number or Class G notification number.

AFSOC/A3OU will continuously track the COA application status and will update units and MAJCOM as needed.

mailto:AFSOC.A3OU.WF@Hurlburt.af.mil.

mailto:AFSOC.A3OU.WF@Hurlburt.af.mil

AFI11-502V3 26 APRIL 2012 19

3.4.1.7. AFSOC/A3OU will notify AF/A3O-BA of the COA details (who, what, where, when, etc.) and/or Class G notifications via email within 1-day of committing the COA or notification to the FAA.

3.4.1.8. The FAA COA process normally takes 60 business days for new COA applications and 30 business days for renewals. AFSOC/A3OUI, working through

AF/A3O-BA, will coordinate/ recommend solutions to unit based on FAA feedback, questions, or concerns. AF/A3O-BA will engage with the FAA to resolve any COA issues.

3.4.2. Units requesting UAS operations in the NAS will coordinate with the appropriate frequency manager for authorization to use SUAS communication frequencies (e.g., control and data links, WIFI, LMR, etc.).

3.4.3. Units must remain in communication with the specified controlling agency at all times during operations as well as an independent means of backup communications available from the ground control element to the controlling agency.

3.4.4. If operations spill out of the assigned airspace or a Loss-of-Link (LOL) condition occurs and the UA does not return to the designated return home point, contact the controlling agency as soon as possible and provide the following information to the controlling agency:

3.4.4.1. SUAS type/size.

3.4.4.2. Last known location and time of LOL.

3.4.4.3. Heading, altitude, airspeed.

3.4.4.4. Estimated flight time remaining.

3.4.5. Contact controlling agency if mission is cancelled or terminated early.

3.4.6. Airspace restrictions for the National Airspace System (NAS). The FAA defines the

NAS as a common network of United States airspace; air navigation facilities, equipment and services, airports or landing areas; aeronautical charts, information and services; rules, regulations and procedures, technical information, and manpower and material. Included are system components shared jointly with the military. There are two types of airspace within the NAS, controlled and uncontrolled.

3.4.6.1. Uncontrolled Airspace. The portion of airspace that air traffic control has neither the authority nor the responsibility for exercising control over air traffic.

3.4.6.2. Controlled Airspace. Airspace of defined dimensions which air traffic control service is provided to IFR flights and to VFR flights in accordance with airspace classification. Controlled airspace is a generic term that covers Class A, Class B, Class C, Class D, and Class E airspace. Listed below is a brief description and depiction of each class of airspace. For more details refer to the DoD Flight Information Publication, General Planning (GP).

3.4.6.2.1. Class A. Generally, that airspace from 18,000 feet MSL up to and including FL600, including the airspace overlying the waters within 12 nautical miles of the coast of the 48 contiguous States and Alaska. Unless otherwise authorized, all persons must operate their aircraft under IFR.

20 AFI11-502V3 26 APRIL 2012

3.4.6.2.2. Class B. Generally, that airspace from the surface to 10,000 feet MSL surrounding the nation's busiest airports in terms of IFR operations or passenger handling. An ATC clearance is required for all aircraft to operate in the area, and all aircraft that are so cleared receive separation services within the airspace.

3.4.6.2.3. Class C. Generally that airspace from the surface to 4,000 feet above the airport elevation surrounding those airports that have an operational control tower, are serviced by a radar approach control, and have a certain number of IFR operations or passenger handling. The airspace usually consists of a surface area with a 5 NM radius, and an outer circle with a 10 NM radius that extends from 1,200 feet to 4,000 feet above the airport elevation. Each person must establish two-way radio communications with the ATC facility providing air traffic services prior to entering the airspace and thereafter maintain those communications while within the airspace.

VFR aircraft are only separated from IFR aircraft within the airspace.

3.4.6.2.4. Class D. Generally, that airspace from the surface to 2,500 feet above the airport elevation surrounding those airports that have an operational control tower.

Unless otherwise authorized, each person must establish two-way radio communications with the ATC facility providing air traffic services prior to entering the airspace and thereafter maintain those communications while in the airspace. No separation services are provided to VFR aircraft.

3.4.6.2.5. Class E. Generally, if the airspace is not Class A, Class B, Class C, or

Class D, and it is controlled airspace, it is Class E airspace. Class E airspace extends upward from either the surface or a designated altitude to the overlying or adjacent controlled airspace. Also in this class are Federal airways, airspace beginning at either

700 or 1,200 feet AGL used to transition to/from the terminal or enroute environment, enroute domestic, and offshore airspace areas designated below 18,000 feet MSL.

Unless designated at a lower altitude, Class E airspace begins at 14,500 MSL over the

United States, including that airspace overlying the waters within 12 nautical miles of the coast of the 48 contiguous States and Alaska. Class E airspace does not include the airspace 18,000 MSL or above.

3.4.6.2.6. Class G. (uncontrolled airspace). That airspace not designated as Class A, B, C, D, or E.

Figure 3.1. Controlled Airspace.

AFI11-502V3 26 APRIL 2012 21

3.4.6.2.7. Operations in Class D Airspace. SUAS operations in Class D airspace require a Certificate of Authorization (COA) or other FAA approval.

Additional guidance in AFI 13-204, paragraph 5.8. states procedures for local SUAS operations must be published in the Base Airfield Operations Instruction, and any other appropriate Lines of Position (LOP).

3.4.6.2.8. Restricted Area. Restricted areas contain airspace identified by an area on the surface of the earth within which the flight of aircraft, while not wholly prohibited, is subject to restrictions. Activities within these areas must be confined because of their nature or limitations imposed upon aircraft operations that are not a part of those activities or both. Restricted areas denote the existence of unusual, often invisible, hazards to aircraft such as artillery firing, aerial gunnery, or guided missiles.

Penetration of restricted areas without authorization from the using or controlling agency may be extremely hazardous to the aircraft and its occupants.

3.4.6.2.9. Warning Area. A warning area is airspace of defined dimensions, extending from three nautical miles outward from the coast of the U.S. that contains activity that may be hazardous to nonparticipating aircraft. The purpose of such warning areas is to warn nonparticipating pilots of the potential danger. A warning area may be located over domestic or international waters or both.

3.5. Coordination Procedures for OCONUS Host Nation Airspace. Refer to specific host nation agreements and International Civil Aviation Organization (ICAO) Standards and

Recommended Practices (SARPs). MAJCOMs are responsible for specifying airspace and frequency request procedures.

3.6. Coordination Procedures for Combat Zone and other Contingency Operations. Refer to Joint Publication 3-52, Joint Doctrine for Airspace Control in the Combat Zone, and theater air operations directives.

22 AFI11-502V3 26 APRIL 2012

Chapter 4

FLIGHT AUTHORIZATION, APPROVAL, AND CLEARANCE AUTHORITY

4.1. Flight Authorization. USAF SUAS flights must be authorized by the unit commander or the first commander in the operational chain of command. Mission validity, planning, and risk mitigation must be considered before authorization. Approving officer will initial the risk assessment checklist (Attachment 4). Exception: AFMC will develop a tailored Operational Risk

Management (ORM) Checklist and will define the ORM program requirements for test operations. Note: To ensure the noncombatant status of civilians and contractors is not jeopardized, commanders shall consult with their servicing judge advocate office for guidance before using civilian or contractor personnel in combat operations or other missions involving direct participation in hostilities.

4.1.1. SUAS-O. The SUAS-O must be current and qualified in the SUAS to be operated or under the supervision of a SUAS-I.

4.2. Approval Authority.

4.2.1. SUAS-Os authorized by the unit commander are the approval authority for their flights with the following exceptions:

4.2.1.1. Unit commanders will approve flights for students or other non-unit SUAS-Os.

4.2.1.2. Unit commanders will approve flights by Group 2 or higher UAS to or from other than established landing surfaces, such as highways, pastures, etc.

4.3. Additional Approval and Requirements.

4.3.1. (P) Fields. MAJCOMs may prescribe which Air Force aircraft can file to or land at

Continental United States (CONUS) civil (P) airports. MAJCOMs shall approve each airfield from which SUAS may operate.

4.4. ATC Clearances and Instructions.

4.4.1. The SUAS-O will ensure compliance with ATC clearances or instructions unless:

4.4.1.1. An amended clearance is obtained.

4.4.1.2. An emergency exists.

4.4.1.3. Deviation is required in response to a Traffic Alert and Collision Avoidance

System (TCAS) advisory.

4.4.1.4. Deviation is necessary to ensure safety of flight.

4.4.2. If the SUAS-O is unsure of the ATC clearance he or she should immediately clarify it with ATC.

AFI11-502V3 26 APRIL 2012 23

Chapter 5

GENERAL FLIGHT RULES

5.1. Operational Standards.

5.1.1. Reckless Flying. The SUAS-O is responsible for ensuring the aircraft is not operated in a careless or reckless manner that could endanger life or property. SUAS will not be used to conduct flights for personal use.

5.1.2. Off-Station Training. The SUAS-O will ensure the execution of all off-station training activities are unit commander-approved, flown to achieve valid training requirements, present a positive image of the Air Force and does not present an image of waste and/or abuse of government resources.

5.1.3. Unauthorized SUAS Flight Demonstrations. Unauthorized or impromptu SUAS flight demonstrations, maneuvers, or ―fly-bys‖ are prohibited.