Appendix A - Post Disaster Airspace

From UAS Operations for Emergency Management
Revision as of 02:00, 30 January 2017 by Dmerrick (talk | contribs) (Created page with "Flight operations, manned and unmanned, in post-disaster airspace are complicated and potentially dangerous. As such, close coordination between FAA ATO, the SERT Air Operati...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Flight operations, manned and unmanned, in post-disaster airspace are complicated and potentially dangerous. As such, close coordination between FAA ATO, the SERT Air Operations Branch and the UAS operator are critical. When operating in these environments, UAS crews should maintain a sterile cockpit at all times.

UAS Coordination

UAS flights supporting disaster response and/or recovery will occur only after coordination with and approval by the responsible Air Operations Branch at the city, county or state level. During all post-disaster UAS operations, CDRP will designate a UAS Coordinator as the direct contact to the Air Operations Branch. The UAS Coordinator will be co-located with the Air Operations Branch whenever practical.

Airspace Deconfliction

UAS operations need to be in compliance with the FAA Airspace Management Plan for Disasters (AMP). This is accomplished within the Air Operations Branch.

The standard FAA AMP calls for rotary wing search and rescue (SAR) and rotary wing sling load operations to occur between the surface and 500' AGL. This is in direct conflict with the typical airspace for small UAS operations. Therefore, it is recommended that UAS operations be segregated from active rotary wing SAR and sling load operations.

Pilots of manned aircraft are not likely to see a UAS at low altitude. Therefore it is the responsibility of the UAS crew to see and avoid manned aircraft at all times. UAS are required to always yield to manned aircraft.

UAS segregation should occur using three factors: geographic, altitude, and date/time. UAS flights should be authorized only in specific airspace, from the surface to a specific altitude (typically 400' AGL or less) and in specific date and time blocks. All altitude coordination with the AOB or ATC must be done in feet (English).

Air Operations Branch Communication

UAS crew must notify the AOB via telephone prior to launch of a UAS and again upon recovery. If the duration of the UAS sortie is to exceed 20 minutes, the UAS crew must notify the AOB every 20 minutes of the aircraft status, location, airspeed and altitude.

Local Traffic Radio Communication

The UAS crew must advise local air traffic via the established CTAF (Common Traffic Advisory Frequency) every 20 minutes of UAS position, airspeed and altitude. In case of operations near towered airports, these CTAF reports will be made to the local ATC controlling the airspace. In operations away from towered airports, CTAF calls will be made "in the blind" in the same manner as manned aircraft notify local traffic of activities in and around the traffic pattern of uncontrolled airports. A.5 - Airspace Exceptions

In a post-disaster environment, particularly when a Temporary Flight Restriction (TFR) has been issued by the FAA, UAS Flights may occur in any type of airspace authorized by the FAA and the Air Operations Branch.