Contingency Airspace Management and Select Issue Updates

Size: px

Start display at page:

Download "Contingency Airspace Management and Select Issue Updates"

Helena Dixon
5 years ago
Views:

Meeting by Justin Kinney Significant Incident

1 Contingency Airspace Management and Select Issue Updates presented to State SAR Coordinator's Council Meeting by Justin Kinney Significant Incident Management Operations, System Operations Security, ATO date 28 February 2018

2 Briefing Objectives Provide a quick overview of the FAA Air Traffic Organization s (ATO) response mission relating to air operations in collaboration with state and federal agencies. Update the states on select active issues: Hurricane Harvey ATO Response Overview Temporary Flight Restriction (TFR) Overview Unmanned Aircraft System (UAS) with Special Governmental Interest (SGI) Addendum Process 1

3 Organizational Structure The FAA comprises five Lines-of-Business (LOB) and eight Staff Offices (SO). ATO serves as the operations arm of the FAA. Air Traffic Organization Security & Hazardous Aviation Safety Airports Material Natl Security Programs System Ops Security & Incident Response Commercial Space NextGen Government & Industry Communications Policy, Intl, & Environment Chief Counsel Human Resources Civil Rights Finance 2

4 Mission Mandates Despite the creation of the Transportation Security (TSA) in November 2001 and the Department of Homeland Security (DHS) in November 2002, the FAA has retained statutory security responsibilities and authorities. Under Title 49 United States Code, the agency continues to exercise plenary authority over the country s airspace for the purpose of air commerce and national defense. Protecting the U.S. against Air Domain related threats while ensuring the safety and efficiency of the National Airspace System (NAS) demands the active participation of the nation s Air Navigation Services Provider (ANSP) i.e., the ATO. ATO s security role has been reinforced by foundational Government aviation security plans e.g., the National Strategy for Aviation Security (NSAS) signed by the President in March

5 Core Mission Set System Operation Security leads ATO efforts to fulfill four overarching security and emergency operations missions: Security: 1) To protect the U.S. and its interests from national defense, homeland security, and law enforcement related threats involving the Air Domain in cooperation with the interagency. 2) To mitigate the impact of those threats (and associated responses) on the safety and efficiency of the NAS. Emergency Operations: 1) To sustain the NAS, particularly the agency s ANS that enable operations. 2) To apply ANS capabilities to broader response efforts by interagency partners to save lives, as well as protect infrastructure and property. 4

6 Security Mission Today Protect the nation ATO Security Mission Mitigate impacts on the NAS 5

7 Evolution of Security Mission Since 9/11, the implementation of key Government plans and the interagency response to crucial real-world incidents have driven the expansion of ATO s security mission. Figure 1. Real World Drivers of ATO s Security Missions 09/11/2001 Attacks 11/19/2001 TSA Created 12/22/2001 Shoe Bomber 09/2003 TSOC Established 05/11/2005 GA Capitol Evacuation 08/2006 Transatlantic Liquid Bomb Plot 12/2009 Christmas Day Bomber 01/2010 Haiti Earthquake 09/11/2001 DEN Created 11/25/2002 DHS Created 06/09/2004 KY Governor incident 08/2005 Hurricane Katrina 09/2008 Hurricane Ike 02/2010 Austin Suicide Crash 01/05/2002 Tampa Suicide Crash 10/29/2001 HSPD-1 (creates HSC) 2/28/2003 HSPD-5 (domestic incidents management) 12/17/2003 HSPD-8 (national preparedness) 11/2004 NRP (superseded by NRF) 09/9/2005 NSTS 06/20/2006 NSPD-47/HSPD-16 03/26/2007 NSAS 03/22/2008 NRF 04/23/2009 IMWG MANPADS CONPLAN 04/2010 Deepwater Horizon Oil Spill 08/27/2011 Hurricane Irene 10/29/2012 Hurricane Sandy 6

8 Response Mission Today Support disaster response ATO Emergency Operations Mission Sustain the NAS 7

Evolution of the Response Mission As the government (at the Federal and State levels) has applied lessons learned from Hurricane Katrina and subsequent crises, the need for active participation by

9 Evolution of the Response Mission As the government (at the Federal and State levels) has applied lessons learned from Hurricane Katrina and subsequent crises, the need for active participation by the nation s primary ANSP (i.e., ATO) has become evident. Figure 2. Real World Drivers of ATO s Emergency Operations Missions 09/11/2001 Attacks 11/19/2001 TSA Created 12/22/2001 Shoe Bomber 09/2003 TSOC Established 05/11/2005 GA Capitol Evacuation 08/2006 Transatlantic Liquid Bomb Plot 12/2009 Christmas Day Bomber 01/2010 Haiti Earthquake 09/11/2001 DEN Created 11/25/2002 DHS Created 06/09/2004 KY Governor incident 08/2005 Hurricane Katrina 09/2008 Hurricane Ike 02/2010 Austin Suicide Crash 01/05/2002 Tampa Suicide Crash 10/29/2001 HSPD-1 (creates HSC) 2/28/2003 HSPD-5 (domestic incidents management) 12/17/2003 HSPD-8 (national preparedness) 11/2004 NRP (superseded by NRF) 09/9/2005 NSTS 06/20/2006 NSPD-47/HSPD-16 03/26/2007 NSAS 03/22/2008 NRF 04/23/2009 IMWG MANPADS CONPLAN 04/2010 Deepwater Horizon Oil Spill 08/27/2011 Hurricane Irene 10/29/2012 Hurricane Sandy 8

10 Mission Expansion USDOT, FAA, and ATO senior leadership expanded the ATO s emergency operations portfolio in September 2005 after Hurricane Katrina struck New Orleans. The resultant flooding created an urgent demand for response flights (e.g., aerial Search and Rescue) and a corresponding critical need for extraordinary air navigation services (ANS). System Operations Security was tasked by the Chief Operating Officer (COO) and the Deputy Administrator with leading ATO s overall emergency operations efforts, including interagency cooperation. 9

11 Inward and Outward Orientations The ATO s emergency operations efforts focus on two complementary missions: 1) Inwardly focused preparedness and continuity missions to sustain its Air Navigation Services (ANS), which enable NAS operations. Operational continuity activities and plans (OCP) Field Incident Response (FIR) Continuity of Operations (COOP) 2) An outwardly facing mission to apply ANS capabilities to facilitate broader government aviation related efforts to save lives, protect critical infrastructure, preserve private property, etc. Emergency Support Function 1 (ESF-1) activities and other interagency cooperation Contingency air traffic and airspace management 10

12 Issue Updates Hurricane Harvey ATO Response Overview Temporary Flight Restriction (TFR) Overview Unmanned Aircraft System (UAS) with Special Governmental Interest (SGI) Addendum Process 11

Response Overview (ASIRT Perspective) Hurricane Harvey August/September 2017 Nodes/Liaisons: FEMA HQ NRCC (ESF-1 Desk) Texas Air Operations Center (AOC) Louisiana State Emergency Operations

13 Response Overview (ASIRT Perspective) Hurricane Harvey August/September 2017 Nodes/Liaisons: FEMA HQ NRCC (ESF-1 Desk) Texas Air Operations Center (AOC) Louisiana State Emergency Operations (SEOC)/Air Operations Branch (AOB) Actions: Airspace Coordination Areas (ACAs) TFRs (VIP and Disaster) Authorizations in/out of TFRs SGIs (aka ecoas) Coordinating Relief Efforts w/ ATC Assisting with Air Coordination Plan (ACP) Development 12

14 Temporary Flight Restrictions WHAT IS A TFR TFR is a type of Notice to Airmen (NOTAM) that defines an area restricted to air travel due to a hazardous condition, a special event, or a general warning for the entire FAA airspace. The text of the actual TFR contains the fine points of the restriction. DIFFERENT TYPES OF TFRs FAA issues TFRs under the following regulations: (1) Section , Temporary Flight Restrictions in the Vicinity of Disaster/Hazard Areas A1 Protect persons and property on the surface or in the air from a hazard associated with an incident of the surface A2 Provide a safe environment for the operation of disaster relief aircraft A3 Prevent an unsafe congestion of sightseeing and other aircraft above an incident or event which may generate a high degree of public interest (2) Section , Temporary Flight Restrictions in National Disaster Areas in the State of Hawaii (3) Section , Emergency Air Traffic Rules (4) Section , Flight Restrictions in the Proximity of the Presidential and Other Parties (5) Section , Flight Limitation in the Proximity of Space Flight Operations (6) Section , Management of Aircraft Operations in the Vicinity of Aerial Demonstrations and Major Sporting Events (7) Section 99.7, Special Security Instructions 13

15 TFRs and ACAs 14

16 Response Efforts Lateral Deconfliction Key tools outlined in the AMP, include: more advanced disaster TFRs with deconfliction by laterally defined zones. 15

17 Response Efforts Vertical Deconfliction Key tools outlined in the AMP, include: more advanced disaster TFRs with deconfliction by mission-based altitude stratification. 16

18 Temporary Flight Restrictions WHO CAN REQUEST A TFR? TFRs may be requested by various authorities, including: Military commands Federal security/intelligence agencies Regional Directors of the Office of Emergency Planning Civil Defense State Directors Civil authorities directing or coordinating organized relief air operations (e.g., Office of Emergency Planning, law enforcement agencies, U.S. Forest Service, state aeronautical agencies) State Governors FAA Flight Standards District Office (FSDO) Aviation event organizers Sporting event officials 17

19 Temporary Flight Restrictions HOW TO REQUEST A TFR? NON-FAA: Contact the nearest Air Traffic Control facility. If possible, have the latitude/longitude of the location in Degrees/Minutes/Seconds format. FAA - Non-Emergency: Contact Service Area Representative for proper handling of the request. FAA - Emergency: The Air Route Traffic Control Centers (ARTCC) that is responsible for the area in question has the authority to issue TFRs during an emergency. Note: The System Operations Support Center (SOSC) can answer questions regarding TFR issuance (202)

20 UAS Operations Overview Aircraft Requirements* Pilot Requirements Airspace Requirements Types of Operation Part 107 UAS < 55 lbs. Part 107 remote pilot certificate with small UAS rating Airspace waiver or authorization for Class B, C, D, E airspace VLOS, daytime, Class G, 400 ft., not over people OR waiver provisions Section 333 As specified in exemption Part 61 airman certificate Blanket COA or Standard COA for specific airspace UAS > 55 lbs. Experimental Aircraft Experimental Special Airworthiness Certificate Part 61 airman certificate Standard COA for specific airspace Research and development, crew training, and market survey Type Certificated Aircraft Restricted type or special class certification Part 61 airman certificate Part 91 airspace requirements Specified in operating authorization Public Aircraft Self-certification by public agency Self-certification by public agency Blanket COA or Standard COA for specific airspace Public Aircraft Operations (AC A); UAS Test Site operations Section 336 Model Aircraft UAS < 55 lbs.* Community-based organization (CBO) standards Notification requirement within 5 miles of an airport Hobby or recreational, VLOS, Section 336 operating rules, CBO standards * Note: All UAS greater than 0.55 pounds that do not meet the definition and operational requirements of a model aircraft must be registered (see part 47 and part 48 requirements) ** The exception to this weight limit is stated in P.L , Section 336 (a)(3) *Some of these requirements are subject to waiver. 19

Part 107 Operating Rules Pilot requires Remote Pilot

Visual line-of-sight, daylight operations At or below 400

authorization required for class B, C, D, and E surface

structure Max groundspeed of 100 mph Not directly over

21 Part 107 Operating Rules Pilot requires Remote Pilot Certificate UAS registered and less than 55 lbs. Visual line-of-sight, daylight operations At or below 400 feet AGL in uncontrolled (Class G) airspace Airspace authorization required for class B, C, D, and E surface areas (via website) Altitude 400 or 400 radius when over structure Max groundspeed of 100 mph Not directly over people Must yield right-of-way to aircraft One UAS per pilot in command No NOTAM 20

Public Aircraft Operations Certificate of Authorization (COA) Part

At or below 400 feet AGL NOTAM Required Typically processed in 10

specific operating area where UAS operations may take place (size

Standards and Air Traffic Processing time 30 business days or more

active COA and/or Part 107 Cert Enables operations outside of

22 Public Aircraft Operations Certificate of Authorization (COA) Part 91 Blanket (CONUS) Area COA Operations in Class G, day and night At or below 400 feet AGL NOTAM Required Typically processed in 10 business days Jurisdictional (Area Boundary) COA Defines a specific operating area where UAS operations may take place (size of city, county, state) needs to be coordinated with Flight Standards and Air Traffic Processing time 30 business days or more Special Government Interest (Emergency COA) Requires approved active COA and/or Part 107 Cert Enables operations outside of approved COA provisions or operations within TFR Processing approval within 60 minutes 21

23 UAS Operation as a Public Entity 22

24 Special Governmental Interest (SGI) Addendum (formerly ecoas) Operating under the authority of an active COA or Part 107 Public and selected civil operations Significant and urgent governmental interests National defense Homeland security Law Enforcement Emergency operations objectives (benefiting critical public good) Restoration of electrical grid Critical infrastructure Normally, requested operations must be flown by a governmental entity or sponsored by a government entity Qualifying proponents of public UAS operations must contact the System Operations Support Center (SOSC), a component of System Operations Security, for assistance (202)

25 UAS Bottom Line ATO focuses on working with federal interagency partners to ensure familiarity with process and rules for use in disaster areas. ATO measures include procedures to expedite the handling of requests for COA addendums. Our office can quickly assist with your incident support requests First call should be to one of our CREO members (AJR-221) Experts knowledgeable of UAS regulatory authorities (AJR-22) Experts knowledgeable of UAS operations with approval authority for expedited SGI (aka ecoas) processing (AJR-24) First stop for UAS operators: Remember: no COA, no ecoa (SGI) 24

26 Questions Justin Kinney Program Manager, SIMO, AJR-221 Geographic AOR: Central Service Area office: Mike Hughes Manager, Significant Incident Management Operations, AJR-221 office: Hank Rigol Program Manager, Unmanned Aircraft System (UAS), AJR-2 office:

Public Aircraft Operations (Governmental Entities)

Public Aircraft Operations (Governmental Entities) Scott Gardner Acting Manager, Emerging Technologies Integration Directorate, Mission Support Services, FAA Air Traffic Organization Workshop 9: Public