7/14/2016
RTCA Tactical Operations Committee Fourteenth Meeting June 23, 2016 RTCA Headquarters
Welcome and Introductions
Co-Chairs: Bryan Quigley, United Airlines Dale Wright, NATCA 2
1
7/14/2016
Topical Agenda FAA Report Discuss New Entrants • Commercial Space briefing • Update on the Drone Advisory Committee (DAC)
FAA Response to Numerous Recommendations • Caribbean, Class B, NPA, VOR MON, Airport Construction, NorCal Noise Initiative
Review progress of ongoing tasks • PBN Route Structure • Graphical TFRs 3
PUBLIC MEETING ANNOUNCEMENT Read by: Designated Federal Official Elizabeth Ray Tactical Operations Committee (TOC) June 23, 2016 In accordance with the Federal Advisory Committee Act, this Advisory Committee meeting is OPEN TO THE PUBLIC. Notice of the meeting was published in the Federal Register on: May 24, 2016 Members of the public may address the committee with PRIOR APPROVAL of the chairman. This should be arranged in advance. Only appointed members of the Advisory Committee may vote on any matter brought to a vote by the Chairman. The public may present written material to the Advisory Committee at any time.
4
2
7/14/2016
Review and Approval of: April 4, 2016 Meeting Summary
5
FAA Report Elizabeth “Lynn” Ray Vice President, Mission Support Services Air Traffic Organization 6
3
7/14/2016
Briefing and Discussion on Commercial Space Ron Schneider, FAA
7
ATO Commercial Space Integration
8
4
7/14/2016
ATO Commercial Space Integration
Presented to: By:
Tactical Operations Committee Ron Schneider, Deputy Director, ATO Commercial Space Integration
Date:
June 23, 2016
Agenda • • • •
Background-AST ATO Commercial Space Overview Industry Outreach Next Steps
ATO Commercial Space Integration
10
5
7/14/2016
BACKGROUND
11
ATO Commercial Space Integration
Space Rocket Launch Sites Around the World 9
10 19
11 8 1
2
3 4
7
14
16
12
18
17
20 21
15 13
5 6
22
1. Vandenberg
7. Hammaguir
12. Palmachim
17. Xichang
2. Edwards
8. Torrejon
13. San Marco
18. Taiyuan
3. Wallops Island
9. Andoya
14. Baikonur
19. Svobodny
4. Cape Canaveral
10. Pleasetsk
15. Sriharikota
20. Kagoshima
5. Kourou
11. Kapustin
16. Jiuquan
21. Tanegashima
6. Alcantara
ATO Commercial Space Integration
22. Woomera
12
6
7/14/2016
Worldwide Orbital Launches 120 United States
100 80
19 24
60
17
19
24 13
15
20
26
26
27
Russia
34
30
China
16
19
11 36
40
22
19
29
33
32 33 19
6
10
19
17
11
7
15
20
19
19
16
15
17 26 15
22
20
0
Other India, Japan, Israel, French Guyana, Iran, North Korea, South Korea, Kwajalein RMI, Pacific Ocean
2006 2007 2008 2009 2010 2011 2012 2013 2014 2015
13
ATO Commercial Space Integration
U.S. Orbital / Suborbital Launch Numbers 30 Kodiak, AK
25
1 1 8
20 1
15
2 1
4 1 1
7 4
8 10 10
4
10 17
17
17
14
5
West Texas (Blue Origin) Wallops Flight Facility, VA
10
9
8
3
11
10
10
10
10
7
0
Vandenberg AFB, CA Cape Canaveral, FL
2006 2007 2008 2009 2010 2011 2012 2013 2014 2015
ATO Commercial Space Integration
14
7
7/14/2016
ATO Commercial Space Integration September 2015
15
Air Traffic Depicted with ARTCC’s 5,864 visible flights
ATO Commercial Space Integration
16
8
7/14/2016
Air Traffic Depicted with Routes
17
ATO Commercial Space Integration
Commercial Space Companies Bigelow Aerospace
Space Exploration Technologies (SpaceX)
Company: Bigelow Aerospace Spaceship Name: CST-100 Starliner crew capsule (in collaboration with Boeing Aerospace) Founder(s): Robert Bigelow Backing: $180 million of his personal fortune as owner of the Budget Suites of America hotel chain.
Company: SpaceX Spaceship Name: Dragon spacecraft and Falcon 9R rocket Founder(s): Elon Musk, co-founder of PayPal Backing: $100 million of Musk's personal fortune, $20 million more from outside investors
Blue Origin Company: Blue Origin Spaceship Name: New Shepard Founder(s): Jeff Bezos Backing: His personal fortune as founder of Amazon.com
Orbital -ATK Company: Orbital Sciences Spaceship Name: Minotaur rocket, Pegasus (horizontal launch), Antares rocket Founder(s): David W. Thompson, Bruce W. Ferguson, Scott L. Webster Backing: Publicly traded company, $1.37 billion in revenue (FY 2013)
Virgin Galactic Company: Virgin Galactic Spaceship Name: SpaceShipTwo Founder(s): British Billionaire Sir Richard Branson Backing: His personal fortune as founder of Virgin Group
XCOR Aerospace Company: XCOR Aerospace Spaceship Name: Lynx RocketPlane (sub- orbital spaceflight) Founder(s): CEO- Jeff Greason (1997-2015); John “Jay” Gibson Backing: Company value of $140 million, as of July 2012, presold 175 Lynx flights at $95,000 each
Sierra Nevada Corporation’s (SNC) Space Systems Company: SpaceDev Spaceship Name: Dream Chaser Founder: Jim Benson (deceased), now led by Fatih Ozmen Backing: Sierra Nevada Corp., of Sparks, Nevada
ATO Commercial Space Integration
18
9
7/14/2016
ORGANIZATION STRUCTURE
19
ATO Commercial Space Integration
FAA Organizational Structure Administrator (AOA) ---------------------
Chief of Staff
Audit & Evaluation (AAE)
Deputy Administrator (ADA)
Chief Operating Officer Air Traffic Organization AJO
Associate Administrator for Aviation Safety
Chief Counsel
AGC
ATO Commercial Space Integration
Associate Administrator for Commercial Space Transportation
Assistant Administrator for Human Resource Management AHR
Associate Administrator for Airports
ARP
AST
AVS
ANG
Assistant Administrator for Communications AOC
Assistant Administrator for NextGen
Assistant Administrator for Civil Rights ACR
Assistant Administrator for Government & Industry Affairs
Associate Administrator – Security & Hazardous Materials Safety
AGI
ASH
Assistant Administrator for Policy, International Affairs & Environment APL
Assistant Administrator for Finance & Management AFN
20
10
7/14/2016
AST History and Responsibilities The Office of Commercial Space Transportation (AST) was established in 1984 as part of the Office of the Secretary of Transportation within the Department of Transportation (DOT). In November 1995, AST was transferred to the Federal Aviation Administration (FAA) as the FAA's only space-related line of business. AST was established to:
• Regulate the U.S. commercial space transportation industry, to ensure compliance with international obligations of the United States, and to protect the public health and safety, safety of property, and national security and foreign policy interests of the United States; • Encourage, facilitate, and promote commercial space launches and reentries by the private sector; • Recommend appropriate changes in Federal statutes, treaties, regulations, policies, plans, and procedures; and • Facilitate the strengthening and expansion of the United States space transportation infrastructure
21
ATO Commercial Space Integration
AST Organization Associate Administrator AST-1
Chief of Staff AST-3
Deputy Associate Administrator AST-2
•
Resource Management *
•
Policy & Communications
•
International Outreach *
•
Training
•
Industrial Viability
•
Administrative Support
•
Business Planning
Space Transportation Development Division AST-100
Licensing & Evaluation Division AST-200
Regulations and Analysis Division AST-300
Chief Engineer AST-4 •
Research*
•
Center of Excellence
•
Technical Oversight
•
Trends
•
Safety Management System
Safety Inspection Division AST-400
Operations Integration Division AST-500 -
- Space Traffic Mgmnt * - Environmental Reviews * - Air & Space Integration - Spaceport Grants
* Core
- Licensing * - Experimental Permits* - Safety Approvals * - Waivers
- Rulemaking * - Tools & Analysis * - Advisory Circulars - Guides
- Safety Inspections * - Mishap Response - Enforcement
- Operations Integration * - Federal Ranges - Civil Partnerships - Suborbital Operations
Functions
ATO Commercial Space Integration
22
11
7/14/2016
ATO COMMERCIAL SPACE OVERVIEW
23
ATO Commercial Space Integration
FAA Strategic Initiatives: • FAA Strategic Priorities: Deliver benefits through technology and infrastructure • Administrator Priority Initiatives: National Airspace System (NAS) Initiative: Lay the foundation for the NAS of the future by achieving prioritized NextGen benefits, integrating new user entrants, and delivering more efficient, streamlined services • Related Sub-Initiatives: Integrate new user entrants (unmanned aircraft and commercial space)
ATO Commercial Space Integration Office established April 1, 2015: • Coordinate/align ATO efforts pertaining to commercial space integration. • Ensure effective collaboration with Office of Commercial Space (AST) and other FAA entities to align policy and services with FAA Strategic Initiatives • Provide objective, independent assessments and recommendations. • Ultimately, the successful integration of commercial space operations in the NAS.
Federal Aviation Administration
24
12
7/14/2016
Air Traffic Organization (ATO) Commercial Space Integration Office
•Ron Schneider •Teresa Fuller •Sally Frodge •Fonda Woodard •Tony Ciampa •Randy Nutter •Ernie Snyder
202-267-9504 609-385-5257 202-267-7040 202-267-6501 609-204-5694 202-267-6468 817-948-2759
[email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]
ATO Commercial Space Integration
25
Air Traffic Organization (ATO) Commercial Space Integration Mission Statement: To safely and efficiently integrate commercial space operations into the National Airspace System
ATO Commercial Space Integration
26
13
7/14/2016
Mission: To safely and efficiently integrate commercial space operations into the National Airspace System (NAS)
• Airspace changes to accommodate space operations and minimize NAS impacts • Procedures and Standards for space vehicle operations • ATO Space Vehicle Operations service delivery • ATO Space Vehicle Planning service delivery • ATC Training for space operations • Policy and Regulation for ATO NAS airspace access • Systems and Capabilities including the research and planning needed to accomplish them • Safety assessments for space operations • International Coordination and Space/Airports
Federal Aviation Administration
27
ATO/FAA Road Map
Administrator Priority Initiatives
ATO Commercial Space Integration
National Airspace System (NAS) Initiative: Lay the foundation for the NAS of the future by achieving prioritized NextGen benefits, integrating new user entrants, and delivering more efficient, streamlined services
28
14
7/14/2016
Commercial Space Integration Team Make Up Space X Boeing
Commercial Space Federation RTCA
A4A
Virgin Galactic
IATA
NBAA Blue
ICAO
SpaceDev/ Sierra Nevada Corp
AOPA
Origin
Orbital ATK
Bigelow Aerospace
AJV-1 AJR-1 AJR-2
AJV-5 AJV-7
CSIT
AJW AJI
ANG
XCOR
AJV-8 AJV-E AJV-C
AJT
AJV-W
Labor participation will be in compliance with bargaining unit agreements
29
ATO Commercial Space Integration
Letter of Agreement (LOA)
Launch/Re-entry Sites (Spaceport)
ATO Commercial Space Integration
Launch Operations
Reentry/Recovery Operations
30
15
7/14/2016
OUTREACH
31
ATO Commercial Space Integration
Stakeholders
Air Traffic Organization (ATO)
Next Gen (ANG)
• • • • • • • •
U.S. Federal Launch Sites: • • • • •
Commercial Space Industry:
Vandenberg AFB Cape Canaveral Wallops Flight Facility White Sands Missile Range Edwards AFB
Space-X Orbital-ATK Virgin Galactic Blue Origin Bigelow Aerospace SpaceDev/Sierra Nevada Corp XCOR CSF
DoD NASA Airports/Space Ports Commercial Space Transportation (AST)
ATO Commercial Space Integration
32
16
7/14/2016
Preliminary Findings Strategic Planning Oversight accountability
SIRs Advisories NOTAMS
Clearly defined roles and responsibility
Communication
Standardized repeatable processes
National policy (ATO)
ATO Safety (SMS)
Surveillance capabilities National Special Use Airspace scheduling capabilities
33
ATO Commercial Space Integration
END
ATO Commercial Space Integration
34
17
7/14/2016
35
ATO Commercial Space Integration
Briefing on the Drone Advisory Committee (DAC) Al Secen, RTCA
36
18
7/14/2016
Drone Advisory Committee (DAC) Description •
Drone Advisory Committee (DAC) announced May 4 by the administrator •
Chaired by Brian Krzanich of Intel; DFO will be the FAA Deputy Administrator
•
NAC-like: 30 ± members, C-Suite decision-makers
•
Likely will require a sub-committee of staffers and additional task groups, working groups or other data-gathering groups (not all RTCA administered)
Status •
Application process ran May 4 to May 19 •
Gathered data from interested parties (390+ applied) •
•
•
Initial cut to 200: removed federal employees; foreign owned organizations without US offices; nonexecutive-level candidate
•
Loaded data into the mathematically-based AHP tool for analysis
•
Complete analysis including sort ordered 200; Top 40; Top 10 per domain; and complete set of statistics provided to the FAA on June 8 with final version June 17
Next steps are •
FAA must make final decision on members/Notify the members
•
Training
•
Plan for first meeting
First meeting is tentatively planned for the Washington DC area the 1st week of August •
Notional first topic: help the FAA prioritize the UAS Integration tasks in the FAA reauthorization bill 37
Update on the Graphical TFR Task Group Rune Duke, AOPA Jon Reisinger, Jeppesen
38
19
7/14/2016
Key Elements of Tasking
39
Increasing Number of NOTAMs: 2012 Pilot’s Bill of Rights Increasing number of NOTAMs being issued • Regulatory requirement for pilots to review Established NOTAM Improvement Panel – Recognized pilots were getting NOTAM overload • RTCA TOC tasked to provide recommendations • Work focused on reducing quantity of NOTAMs displayed – Result was NOTAM Search TFRs are viewed by pilots as one of the most significant NOTAM • Serious consequences for not complying • Can result in aircraft being intercepted and/or “deadly force” taken • TFRs can be issued for hazards Number of NOTAMs Issued in 2015 952,422 Domestic 559,896 US created International 130,809 FDC 132,858 Military 1,775,985 Total
Number of TFR NOTAMs Issued in 2015 ≈2,000
20
7/14/2016
System Operations Security (AJR-2) TFRs Issued Since 2013
1800
1663
1600
1439
Year
91.141 VIP
1400
99.7 Special Security
1200 996
1000 800 600
397
400
305 310
200
270 116
99.7 91.141 Special Total VIP Security
CY2013
195
1439
1634
CY2014
305
1663
1968
CY2015
270
996
1266
CY2016*
116
397
513
*Through May 2016
0 CY2013
CY2014
CY2015
CY2016*
Subtracted reissues
Graphics Critical to Awareness Pilots are Embracing Technology – Greater access to graphics •
2016 survey of random sample of AOPA active pilots: – 82% use an EFB frequently/always in the cockpit – How pilots access a preflight briefing: • 60.7% brief use 3rd party vendor (e.g., ForeFlight) • 38.7% call 1‐800‐WX‐BRIEF • 28.6% use DUATS (online web portal – TFRs mentioned by callers as barrier to not solely going online – Many high intenders to call (not go online) highlighted “legality” of FAA/DUATS websites:
“Depicted TFR data may not be a complete listing. Pilots should not use the information on this website for flight planning purposes. For the latest information, call your local Flight Service Station at 1‐800‐WX‐BRIEF.”
21
7/14/2016
Pilots Fly Relying on Graphics
Reality is pilots avoid TFRs laterally by looking at a graphic • “Advisory use” of graphic fails to meet pilots’ need in modern cockpit – Lateral dimensions can be accurately provided to a pilot, just like Class B airspace can be defined and depicted – NOTAM overload – graphic is key mechanism to alert pilot •
Legal/liability considerations: – An FAA generated graphic should be considered different/better than a pilot self‐plotted TFR on a chart (lat/long or FRD) – Continued emphasis on pilot reviewing all available information, including NOTAM text – Inaccurate or incomplete TFR graphics by FAA or DUATS should be viewed by the FAA as mitigating factor for any incursion
Need for Tasking • August 2015 – South Carolina VIP VPOTUS TFR, Lockheed Martin did not show graphic – Pilots notified of violating airspace • Fall 2015 – New York VIP Pope TFR, graphics inverse or incorrect by all vendors • February 2016 – Los Angeles VIP POTUS TFR, Lockheed Martin incorrect graphic • Future Flight Service contract – Data on why pilots call show disclaimers on websites to be a high concern and possible barrier to increased number of online users • FAA TFR shapefile, data, and text all have disclaimer • Vendors – Every vendor AOPA talked with had technical and practical concerns with FAA’s TFR data stream • Authoritative source – Lack of single source creates additional complexity We want to reduce TFR incursions – Graphics are key to pilot situational awareness – Tracking TFR graphics showed variety of discrepancies
22
7/14/2016
FDC 6/1305 – TFR Issued for Controlled Firing Area (CFA)
TFR issued erroneously for CFA AOPA requested originator cancel NOTAM, while still active, which was not possible AJV-11 investigated and determined local facility error New local procedures in place Example of lack of oversight and lack of ability to modify once submitted
FDC 6/1305 ZID IN..AIRSPACE TERRE HAUTE, IN..TEMPORARY FLIGHT RESTRICTIONS CONTROLLED FIRING AREA WI AREA DEFINED AS 1 NM RADIUS OF 385143N864840W (1 NM RADIUS OF OOM 211 DEGREE RADIAL AT 19 NM.) SFC-16500FT. PURSUANT TO 14 CFR SECTION 91.137(A)(1) TEMPORARY FLIGHT RESTRICTIONS ARE IN EFFECT FOR AN AIRBORNE HAZARD AT BLUE SKIES CONTROLLED FIRING AREA(CFA) IN R3404, ELECTROMAGNETIC EMISSIONS REMAIN. AVOIDANCE ADVISED. NAVAL SURFACE WARFARE CENTER IS IN CHARGE OF ON SCENE EMERGENCY RESPONSE ACTIVITY 812-854-5259. INDIANAPOLIS ARTCC /ZID/ TELEPHONE 317-247-2243 IS THE FAA COORDINATION FACILITY. 1601082300-1601090700
FDC 6/5678 & 6/8302 – Kennedy Space Operations
•
•
“If the originator of a TFR does not utilize the TFR Builder application to submit the TFR NOTAM, no graphical depiction will be displayed on the TFR.faa.gov website, unless it's a HAZARD TFR” Many lat/long points – Complexity of plotting TFR manually
23
7/14/2016
FDC 6/6697 – DC Nuclear Summit
• NOTAM text is similar to SFRA/FRZ NOTAM – dimensions and language match • Language is nuanced and no graphic increases chance it is overlooked • Human factors issue: over 1,400 words – 8 parts
FDC 6/6697 ZDC PART 1 OF 8 DC..AIRSPACE WASHINGTON, DC..FLIGHT RESTRICTIONS MARCH 31 - APRIL 1, 2016. PURSUANT TO 49 USC 40103(B), THE FEDERAL AVIATION ADMINISTRATION (FAA) CLASSIFIES THE AIRSPACE DEFINED IN THIS NOTAM AS 'NATIONAL DEFENSE AIRSPACE'. PILOTS WHO DO NOT ADHERE TO THE FOLLOWING PROCEDURES MAY BE INTERCEPTED, DETAINED AND INTERVIEWED BY LAW ENFORCEMENT/ SECURITY PERSONNEL. ANY OF THE FOLLOWING ADDITIONAL ACTIONS MAY ALSO BE TAKEN AGAINST A PILOT WHO DOES NOT COMPLY WITH THE REQUIREMENTS OR ANY SPECIAL INSTRUCTIONS OR PROCEDURES ANNOUNCED IN THIS NOTAM: A) THE FAA MAY TAKE ADMINISTRATIVE ACTION, INCLUDING IMPOSING CIVIL PENALTIES AND THE SUSPENSION OR REVOCATION OF AIRMEN CERTIFICATES; OR B) THE UNITED STATES GOVERNMENT MAY PURSUE CRIMINAL CHARGES, INCLUDING CHARGES UNDER TITLE 49 OF THE UNITED STATES CODE, SECTION 46307; OR C) THE UNITED STATES GOVERNMENT MAY USE DEADLY FORCE AGAINST THE AIRBORNE AIRCRAFT, IF IT IS DETERMINED THAT THE AIRCRAFT POSES AN IMMINENT SECURITY THREAT. PURSUANT TO TITLE 14, CODE OF FEDERAL REGULATIONS, SECTIONS 91.141 1603311100-1604020000 END PART 1 OF 8 FDC 6/6697 ZDC PART 2 OF 8 DC..AIRSPACE WASHINGTON, DC..FLIGHT RESTRICTIONS AND 99.7 SPECIAL SECURITY INSTRUCTIONS, WITHIN THE AREA DESCRIBED AS DC SFRA FROM THE SURFACE, UP TO BUT NOT INCLUDING 18000 FT MSL. EFFECTIVE 1603311100 UTC (0700 LOCAL 03/31/16) UNTIL 1604020000 UTC (2000 LOCAL 04/01/16). WITHIN THE AREA DESCRIBED AS DC FRZ FROM THE SURFACE, UP TO BUT NOT INCLUDING 18000 FT MSL EFFECTIVE 1603311100 UTC (0700 LOCAL 03/31/16) UNTIL 1604020000 UTC (2000 LOCAL 04/01/16). A. THE DC SFRA IS THAT AREA OF AIRSPACE OVER THE SURFACE OF THE EARTH WHERE THE READY IDENTIFICATION, LOCATION, AND CONTROL OF AIRCRAFT IS REQUIRED IN THE INTERESTS OF NATIONAL SECURITY. SPECIFICALLY, THE DC SFRA IS THAT AIRSPACE, FROM THE SURFACE TO BUT NOT INCLUDING FL180, WITHIN A 30-NAUTICAL MILE RADIUS OF 385134N/0770211W OR THE DCA VOR/DME. B. THE WASHINGTON, D.C. METROPOLITAN AREA FLIGHT RESTRICTED ZONE (DC 1603311100-1604020000 END PART 2 OF 8 FDC 6/6697 ZDC PART 3 OF 8 DC..AIRSPACE WASHINGTON, DC..FLIGHT RESTRICTIONS FRZ) IS DEFINED AS AN AREA BOUNDED BY A LINE BEGINNING AT THE WASHINGTON /DCA/ VOR/DME 311 DEGREE RADIAL AT 15NM 385931N/0771830W, THENCE CLOCKWISE ALONG THE DCA 15NM ARC TO THE DCA 002 DEGREE RADIAL AT 15NM 390628N/0770432W, THENCE SOUTHEAST VIA A LINE DRAWN TO THE DCA 049 DEGREE RADIAL AT 14NM 390218N/0765038W, THENCE SOUTH VIA A LINE DRAWN TO THE DCA 064 DEGREE RADIAL AT 13NM 385901N/0764832W, THENCE CLOCKWISE ALONG THE 13NM ARC TO THE DCA 276 DEGREE RADIAL AT 13NM 385053N/0771848W, THENCE NORTH TO THE POINT OF BEGINNING, EXCLUDING THE AIRSPACE WITHIN A 1NM RADIUS OF FREEWAY AIRPORT /W00/ MITCHELLVILLE, MD, FROM THE SURFACE UP TO BUT NOT INCLUDING FL180. THE DC FRZ IS WITHIN AND PART OF THE WASHINGTON DC SFRA. C. THE FOLLOWING FLIGHT RESTRICTIONS/SPECIAL SECURITY INSTRUCTIONS ARE IN EFFECT, ALL FLIGHT OPERATIONS WITHIN THE DC SFRA ARE PROHIBITED EXCEPT AS SPECIFICALLY PROVIDED BELOW: 1.) AUTHORIZED CFR PART 121 AND PART 129 REGULARLY SCHEDULED COMMERCIAL PASSENGER AND PART 135 ALL-CARGO CARRIERS OPERATING UNDER ONE OF THE FOLLOWING TRANSPORTATION SECURITY ADMINISTRATION APPROVED STANDARD SECURITY PROGRAMS/PROCEDURES: AIRCRAFT OPERATOR STANDARD SECURITY PROGRAM (AOSSP), FULL ALL-CARGO AIRCRAFT OPERATOR STANDARD 1603311100-1604020000 END PART 3 OF 8 FDC 6/6697 ZDC PART 4 OF 8 DC..AIRSPACE WASHINGTON, DC..FLIGHT RESTRICTIONS SECURITY PROGRAM (FACAOSSP), TWELVE FIVE STANDARD SECURITY PROGRAM (TFSSP) ALL CARGO, MODEL SECURITY PROGRAM (MSP) OR ALL-CARGO INTERNATIONAL SECURITY PROCEDURES (ACISP). 2.) PART 135 AND PART 91 AIRCRAFT ON AN ACTIVE IFR/VFR FLIGHT PLAN MAY ARRIVE AND/OR DEPART ALL AIRPORTS WITHIN THE SFRA. 3.) FOREIGN AIRCRAFT ISSUED A DOS DIPLOMATIC CLEARANCE ARE AUTHORIZED TO OPERATE IN THE DC SFRA. 4.) VFR OPERATIONS TO, FROM AND BETWEEN AIRPORTS IN THE SFRA WILL BE PERMITTED DURING THE TIME OF THIS NOTAM, SUBJECT TO THE PROVISIONS OF 14 CFR PART 93.337 AND FDC NOTAM 6/2062. 5.) VFR TRANSIT FLIGHTS (NOT LANDING/DEPARTING AN SFRA AIRPORT) OR LOITERING WITHIN THE SFRA ARE NOT PERMITTED DURING THE TIME OF THIS NOTAM. 6.) VFR TRAFFIC PATTERN OPERATIONS AT AIRPORTS WITHIN THE SFRA/FRZ ARE SUSPENDED DURING THE TIME OF THIS NOTAM. 7.) EGRESS PROCEDURES AS DEFINED UNDER 14 CFR 93.345 FOR THE FOLLOWING AIRPORTS: BARNES (MD47), FLYING M FARMS (MD77), MOUNTAIN ROAD (MD43), ROBINSON (MD14), SKYVIEW (51VA), WILL BE IN EFFECT DURING THE TIME OF THIS NOTAM. 1603311100-1604020000 END PART 4 OF 8 FDC 6/6697 ZDC PART 5 OF 8 DC..AIRSPACE WASHINGTON, DC..FLIGHT RESTRICTIONS 8.) THE PROVISIONS OF FDC NOTAM 6/2085, INGRESS/EGRESS PROCEDURES FOR LEESBURG (JYO) WILL BE IN EFFECT DURING THE TIME OF THIS NOTAM. 9.) DOD AND LAW ENFORCEMENT/AIR AMBULANCE OPERATIONS AUTHORIZED BY THE AIR SECURITY OPERATIONS CENTER (ASOC) ARE PERMITTED WITHIN THE DC SFRA, BUT PRIOR COORDINATION AND APPROVAL FOR EACH FLIGHT MUST BE OBTAINED FROM THE ASOC AT 866-598-9524. COORDINATION CALLS WILL NOT BE ACCEPTED MORE THAN 24 HOURS IN ADVANCE OF THE ESTIMATED TIME OF DEPARTURE. 10.) SMALL UAS OPERATIONS WITHIN THE SFRA UNDER NOTAM 6/2069 ARE SUSPENDED DURING THE TIMES OF THIS NOTAM. D. THE FOLLOWING FLIGHT RESTRICTIONS/SPECIAL SECURITY INSTRUCTIONS ARE IN EFFECT, ALL FLIGHT OPERATIONS WITHIN THE DC FRZ ARE PROHIBITED EXCEPT AS SPECIFICALLY PROVIDED BELOW: 1.) DOD AND LAW ENFORCEMENT/AIR AMBULANCE OPERATIONS AUTHORIZED BY THE AIR SECURITY OPERATIONS CENTER (ASOC) ARE PERMITTED WITHIN THE DC FRZ. PRIOR COORDINATION AND APPROVAL MUST BE OBTAINED FROM THE ASOC AT 866-5989524 COORDINATION CALLS WILL NOT BE ACCEPTED MORE THAN 48 HOURS IN ADVANCE OF THE NOTAM EFFECTIVE TIME. OPERATIONS ON 1603311100-1604020000 END PART 5 OF 8 FDC 6/6697 ZDC PART 6 OF 8 DC..AIRSPACE WASHINGTON, DC..FLIGHT RESTRICTIONS OR NEAR HELICOPTER ROUTE 1 FROM THE CABIN JOHN BRIDGE TO THE PRINCE GEORGES CENTER AND WITHIN ZONE 2 SHOULD BE LIFESAVING OR NATIONAL SECURITY MISSIONS ONLY. 2.) ALL AIRCRAFT ARRIVING AND/OR DEPARTING FROM JB ANDREWS (KADW) OR DAVISON ARMY AIRFIELD (KDAA) MUST COORDINATE WITH AND RECEIVE APPROVAL FROM THE AIR SECURITY OPERATIONS CENTER (ASOC), PHONE 866-598-9524, A MINIMUM OF 1 HOUR PRIOR TO DEPARTURE BUT NOT MORE THAN 48 HOURS IN ADVANCE OF THE NOTAM EFFECTIVE TIME. A PPR DOES NOT AUTHORIZE ENTRY INTO THE FRZ. 3.) CFR PART 121 AND PART 129 REGULARLY SCHEDULED COMMERCIAL PASSENGER CARRIERS OPERATING INTO AND OUT OF WASHINGTON REAGAN NATIONAL AIRPORT (KDCA) OPERATING UNDER THE TRANSPORTATION SECURITY ADMINISTRATION AIRCRAFT OPERATOR STANDARD SECURITY PROGRAM (AOSSP) OR MODEL SECURITY PROGRAM (MSP) ARE AUTHORIZED TO OPERATE IN THE DC FRZ. 4.) CFR PART 91 AND PART 135 AIRCRAFT OPERATORS OPERATING INTO AND OUT OF WASHINGTON REAGAN NATIONAL AIRPORT (KDCA) OPERATING UNDER THE TRANSPORTATION SECURITY ADMINISTRATION DCA ACCESS STANDARD SECURITY PROGRAM (DASSP) ARE AUTHORIZED TO OPERATE IN THE DC FRZ. 1603311100-1604020000 END PART 6 OF 8 FDC 6/6697 ZDC PART 7 OF 8 DC..AIRSPACE WASHINGTON, DC..FLIGHT RESTRICTIONS 5.) FOREIGN STATE AIRCRAFT ISSUED A DEPARTMENT OF STATE DIPLOMATIC CLEARANCE ARE AUTHORIZED TO OPERATE INTO AND OUT OF JOINT BASE ANDREWS (KADW) ONLY. 6.) THE PROVISIONS OF FDC NOTAM 6/2060 AND 14 CFR PART 93, PERTAINING TO THE MARYLAND 3 AIRPORTS KNOWN AS WASHINGTON EXECUTIVE AIRPORT/HYDE FIELD (KW32), POTOMAC AIRFIELD (KVKX) AND COLLEGE PARK AIRPORT (KCGS), ARE SUSPENDED DURING THE TIME OF THIS NOTAM. E. ALL AIRCRAFT OPERATING WITHIN THE SFRA/FRZ MUST BE ON AN ACTIVE IFR/VFR FLIGHT PLAN WITH A DISCRETE CODE ASSIGNED BY AN AIR TRAFFIC CONTROL (ATC) FACILITY. AIRCRAFT MUST SQUAWK THE ASSIGNED DISCRETE CODE PRIOR TO DEPARTURE AND AT ALL TIMES WHILE IN THE TFR AND MUST REMAIN IN TWO-WAY RADIO COMMUNICATIONS WITH ATC. LOCALLY BASED LAW ENFORCEMENT, AIR AMBULANCE AND DOD AIRCRAFT WITH A POTOMAC TRACON PRE-ASSIGNED BEACON CODE MAY OPERATE VFR. F. THE FOLLOWING OPERATIONS ARE PROHIBITED IN THE SFRA AND FRZ: UNMANNED AIRCRAFT OPERATIONS (INCLUDING MODEL AIRCRAFT, CIVIL COMMERCIAL AND PUBLIC OPERATIONS), FLIGHT TRAINING, PRACTICE APPROACHES, AEROBATIC MANEUVERS, GLIDER OPERATIONS, PARACHUTE 1603311100-1604020000 END PART 7 OF 8 FDC 6/6697 ZDC PART 8 OF 8 DC..AIRSPACE WASHINGTON, DC..FLIGHT RESTRICTIONS OPERATIONS, ULTRALIGHTS, LIGHTER THAN AIR/BALLOON/MOORED BALLOON, AGRICULTURAL/CROP DUSTING/SPRAYING, ANIMAL POPULATION CONTROL, BANNER TOWING, UTILITY/PIPELINE PATROLS, AIRCRAFT/HELICOPTERS OPERATING FROM A SHIP OR PRIVATE/CORPORATE YACHT, MODEL AIRCRAFT, MODEL ROCKETS, MAINTENANCE FLIGHTS AND LOCAL DOD FLIGHTS. G. ALL WAIVERS TO FDC NOTAM 6/2060 AND 14 CFR PART 93 SFRA/FRZ ARE TEMPORARILY SUSPENDED DURING THE TIME OF THIS NOTAM EXCEPT FOR WAIVERS BEGINNING WITH ELO, GOV, SPO, LEA OR LFG WITH PRIOR COORDINATION WITH THE ASOC. H. THE FEDERAL AVIATION ADMINISTRATION /FAA/ NATIONAL CAPITAL REGION COORDINATION CENTER/NCRCC/ PHONE 866-598-9522, IS THE COORDINATION FACILITY. I. IT IS STRONGLY RECOMMENDED THAT ALL AIRCRAFT OPERATORS CHECK NOTAMS FREQUENTLY FOR POSSIBLE REQUIRED CHANGES TO THIS TFR PRIOR TO OPERATIONS WITHIN THIS REGION. 1603311100-1604020000 END PART 8 OF 8
User-Friendliness
Presentation is Critical for Human Factors • Capital letters • Lacks consistent organization • Main details difficult to find • Lat/long and FRD are all pilots have if no graphic • Block of text The TFR issuer and the user (pilot, FSS, ATC) would benefit from greater standardization and clarity
24
7/14/2016
Current Task Group Membership Rune Duke, Aircraft Owners and Pilots Association (Chair)
John Collins, Foreflight LLC Nick Downing, Foreflight LLC
Dave Bear, Federal Aviation Administration
Tyson Weihs, Foreflight LLC
Trish Gay, Federal Aviation Administration
Jeremy Holman, Garmin Ltd.
Talwyn Haley, Federal Aviation Administration
Jon Reisinger, Jeppesen (Chair)
Michael Helwig, Federal Aviation Administration
Joe Daniele, Lockheed Martin Corporation
Chris Henne, Federal Aviation Administration
Heather Rittiner, Lockheed Martin Corporation
Brian Hint, Federal Aviation Administration
William L Geoghagan, National Air Traffic Controllers Association
Lynette Jamison, Federal Aviation Administration Scott Jerdan, Federal Aviation Administration
Jim McClay, National Business Aviation Association
Scott Leis, Federal Aviation Administration
Trin Mitra, RTCA, Inc.
Bob McMullen, Federal Aviation Administration
Jim Mills, U.S. Air Force
Tiffany Narowski, Federal Aviation Administration
David von Rinteln, U.S. Air Force
Jim Perkins, Federal Aviation Administration
Divya Chandra, Volpe National Transportation Systems Center
Jerry Torres, Federal Aviation Administration
49
Task Group Schedule Thu Jun 16 [Jun 23 TOC] Phone call on Thu Jul 7 Thu Jul 21 Thu Aug 25 Thu Sep 29 Thu Oct 20 [Oct 27 TOC] Thu Dec 8 Deliver final recommendation at Feb 2017 TOC meeting 50
25
7/14/2016
FAA Response to Previous Recommendations National Procedure Assessment VOR MON Airport Construction NorCal Noise Initiative 51
Cancellation of Instrument Flight Procedures Recommendations
Federal Aviation Administration
Presented to: Tactical Operations Committee By:
Elizabeth Ray
Date:
June 23, 2016
Federal Aviation Administration
26
7/14/2016
Fully Accepted Recommendations 1.
Procedures not evaluated for cancellation at this time – Accept recommendations a, b, c, d, e, and f without comment The VOR / DME RNAV Procedures are scheduled for cancellation
4.
Remove Microwave Landing System (MLS) and Transponder Landing System (TLS) Procedure categories – Accept recommendation without comment
5.
Consider remaining Simplified Directional Facility (SDF) procedures for cancellation – Accept recommendation without comment
Federal Aviation Administration
53
Fully Accepted Recommendations (cont.) 6.
PAR and ASR Procedures a) Accept with no comment b) Accept with no comment c) Accept with no comment Facility should be following this process
7.
PBN Instrument Approach Procedures a) Accept with no comment b) Accept with no comment
9. PAR and ASR Procedures a)
Accept with no comment
Federal Aviation Administration
54
27
7/14/2016
Recommendations with Comment 2.
Circling Procedures a) Would require vetting through Federal Register b) Would require a network of training centers and simulator operator points of contact for coordination
3.
Ground-Based Instrument Approach Procedures a) “Extensive” would require further definition to delineate criteria. Accept adding word civil to criteria b) Requires further evaluation due to potential conflict with future cancellation initiatives c) Accept with no comment
8.
Identify candidate SIDs/STARs for cancellation according to the criteria in the figure below Change to “Review candidate SIDs/STARs for cancellation and consider criteria in the figure below during the review process” Federal Aviation Administration
55
Recommendations with Comment (cont.) 10. Recommendation on the Outreach for Procedure Cancellations a) b) c)
Accept with no comment We should accept recommendation but place the guidance in 8260.19 instead of the RAPT Order Accept as best practice resources permitting
11. Additional recommendations a) b)
c) d)
Accept with no comment Current national policy “Performance Based Navigation (PBN) National Airspace System (NAS) Navigation Strategy already exists. Change to develop additional strategies to motivate procedure cancellation FAAs capacity for procedure maintenance and development is being addressed through automation tools and process improvements Accept with no comment Federal Aviation Administration
56
28
7/14/2016
Very High Frequency Omnidirectional Range (VOR) Minimum Operational Network (MON) Implementation Program
Federal Aviation Administration
Program Update
Presented to: RTCA Tactical Operations Committee (TOC) By: Leonixa Salcedo, AJM-324 VOR MON Program Manager Date: June 23, 2016
Agenda • Program Status • VOR MON Program Timeline • RTCA Tactical Operations Committee (TOC) Recommendations • Federal Register Notice (FRN) Background • VOR MON Program Final Policy FRN • Criteria Discussion
VOR MON Implementation Program June 23, 2016
Federal Aviation Administration
58
29
7/14/2016
Program Status •
Achieved Investment Analysis Readiness Decision (IARD) – March 2014
•
DoD/DHS Retention Coordination Received – January 2015
•
RTCA TOC Task Responses Completed – April 2015
•
Program Achieved Final Investment Decision (FID) Phase 1 – September 2015
•
Began VOR MON Program Implementation – October 2015
•
RTCA TOC Briefed – November 2015
•
Program Kick-off Meeting – FAA Internal – December 2015
VOR MON Implementation Program
Federal Aviation Administration
June 23, 2016
59
VOR MON Program Timeline FY14
FY15
FY16
External Drivers
FY17
FY18
FY19
WAAS LPV procedures at qualified runways
VOR MON Program
IARD
Phase 1 FID
FY20
FY21
FY25
ADS-B equipage mandate
Phase 2 FID
Milestones
Current: 957 Program Target: 649
VOR MON Implementation 0 The VOR MON Program will be completed in 2 phases: Phase 1: FY16 – FY20 Phase 2: FY21 – FY25
Phase 1
VOR MON Implementation Program June 23, 2016
Phase 2
• Publish Final Policy FRN: “Provision of Navigation Services for the Next Generation Air Transportation System (NextGen) Transition to Performance Based Navigation (PBN)” • Remove, Replace, Amend affected Instrument Flight Procedures (IFPs) • Discontinue Phase 1 VORs (74) • Plan for Phase 2 Final Investment Decision (FID)
• Continue IFP work • Discontinue Phase 2 VORs (234)
Federal Aviation Administration
60
30
7/14/2016
RTCA TOC Task Recommendations The following were the four (4) task areas in which the VOR MON TG provided recommendations to the FAA: •
Task 1: Review and validate the VOR MON selection criteria and assumptions. –
•
Task 2: Review and validate the draft candidate VOR MON list. –
•
The FAA used the task group’s suggested methodology to develop a final list of VORs to be included as part of the MON. Completed February 2014
Task 3: Review implementation planning to date and make recommendations to the preliminary waterfall schedule developed by the FAA. –
•
In FAA’s response to the task group, all the task group’s recommendations were considered and subsequently incorporated into the VOR MON selection criteria as appropriate. Completed November 2013
The FAA reviewed the recommendations and incorporated the feedback into the VOR MON Program waterfall schedule as appropriate. Completed February 2015
Task 4: Provide recommendations to the FAA on outreach and education that should be accomplished to prepare stakeholders for the VOR MON reduction. –
“The Task Group strongly recommends that the FAA publish a list of all VORs planned for decommissioning at the beginning of the notification process. It is paramount to publish the full list upfront so there are no surprises to the public later in the process about which VORs are being shut down.”
–
The FAA concurred with the recommendation and plans to publish a final policy FRN upon the completion of its Final Investment Decision (FID).
VOR MON Implementation Program June 23, 2016
Federal Aviation Administration
61
Federal Register Notice (FRN) Background • The FAA published an initial proposed policy Federal Register Notice (FRN), “Proposed Provision of Navigation Services for the Next Generation Air Transportation System (NextGen) Transition to Performance-Based Navigation (PBN)”, (76 FR 77939), for comment on December 15, 2011, which discussed retaining an optimized network of VORs as a component of this transition strategy.
• The disposition of all received comments on the notice of proposed policy was published (77 FR 50420) on August 21, 2012.
VOR MON Implementation Program June 23, 2016
Federal Aviation Administration
62
31
7/14/2016
VOR MON Program Final Policy FRN •
The VOR MON Program Final Policy FRN addresses the recommendations outlined by the RTCA TOC in Task 4: – Defines the retention criteria and other supplemental information that was used to assess VORs for discontinuance. – Discusses the working group collaboration process used to solidify the candidate discontinuance list. – Outlines the established policies and processes that the FAA follow when discontinuing VORs. – Provides the full VOR candidate discontinuance list sorted by Phase 1 (FY16-FY20) and Phase 2 (FY21-FY25) of the program.
Target publishing the VOR MON Program Final Policy FRN by July 31, 2016.
•
VOR MON Implementation Program June 23, 2016
Federal Aviation Administration
63
Criteria Discussion •
On June 27, 2014 the FAA published a policy establishing criteria for cancelling certain ground-based Standard Instrument Approach Procedures (SIAPs) (79 FR 36576) as an integral part of right-sizing the quantity and type of procedures in the National Airspace System (NAS).
•
On April 13, 2015 the FAA published (80 FR 19577) a list of 736 SIAPs proposed for cancellation in accordance with that criteria. –
The FAA received public comments for some of those SIAPs, which expressed concern about instrument flight training/proficiency.
–
A metric of “a like-type SIAP at an airport within 20NM of the airport containing the SIAP proposed for cancellation” was established to adjudicate those specific comments. If there is no other airport within 20 NM with a similar type SIAP, the proposed SIAP would be retained.
•
The VOR MON Implementation Program’s criteria states that the MON will support landings by either a VOR, ILS, or LOC approach to an airport no more than 100 nautical miles from any location in the CONUS, where the capability exists today.
•
Although the IFP cancellation criteria used under the NPA Program’s FRN addressed specific comments received, as we transition to PBN the VOR MON Implementation Program criteria will supersede.
VOR MON Implementation Program June 23, 2016
Federal Aviation Administration
64
32
7/14/2016
Questions VOR MON Implementation Program June 23, 2016
Federal Aviation Administration
65
Lunch Until 1pm
66
33
7/14/2016
FAA Response to Caribbean Operations Recommendations Jim Linney, FAA
67
FAA Response to Recommendations on Class B Airspace Gary Norek & Ken Ready, FAA
68
34
7/14/2016
Update from the NextGen Advisory Committee (NAC) Andy Cebula, RTCA
69
NextGen Advisory Committee Meeting June 17thHosted By Boeing – Crystal City
Mike Whitaker’s Final Meeting as DFO Boeing Briefing on Equipage – ADS-B Recommendations Approved: • NextGen Integration Working Group Four Priority Areas • Wake ReCat Analysis • Community Outreach 70
35
7/14/2016
More NAC Highlights
Seattle Greener Skies – Next Steps to Improve Usage
JetBlue Equipage
71
Implementation of PBN Capabilities Established on Required Navigation Performance (EoR) • EoR w/ Radius-to-fix (RF): DEN, PDX, BNA, IAH • EoR w/ Track-to-fix (TF): CLT, PHL, ATL, SDF • Assessment of TF/RF Concurrent Operations
Metroplex • ATL/CLT Mature implementations • Las Vegas Metroplex (LAS) milestones
Established on Departure Operations (EDO) • Assessing information & developing a plan • Possible implementation: ATL, DFW
RF to xLS (RF/TF) • Assessment/identification of pre-implementation milestones • Possible implementation: RNO, SEA 72
36
7/14/2016
Implementation (cont.) Optimized Profile Descents (OPD) - Area Navigation (RNAV) Standard Terminal Arrivals (STARs) • LUCIT1 (GYY), JFUND1 (BOS), PINCH 1 (AUS)
Enhanced Flight Vision Systems (EFVS) • Final rule publication • Possible implementation IND
Advanced RNP (A-RNP) • Demonstration sites: SNA, EGE
New Vertical Guidance • Potential sites: SMO
Departures • RNP – SNA • RNAV - HND
TBD – Actions related to Seattle Greener Skies 73
Decision Support Tools Leveraging opportunities DSTs – identified milestones • Maximize existing tools during transition to additional TBFM capabilities • TBFM Terminal Sequencing and Spacing (TSAS) • TBFM Ground-Based Interval Management-Spacing (GIM-S) • TBFM Integrated Departure Arrival Capability (IDAC)
74
37
7/14/2016
Community Outreach Recommendations: FAA Should Establish Specialized Community Outreach Team(s) Develop a Standard Community Outreach Toolkit Develop specific Local Community Outreach Toolkits Establish Ongoing and scalable Community Outreach Programs in collaboration with local airports
75
Community Outreach (cont.) Disseminate both this document & original Blueprint for Success to Implementing PBN to airport operators, and airlines Incorporate the best practices outlined throughout this document • Preparation • Education • Engagement • Advocacy • Post-implementation steps in PBN-related community engagement
76
38
7/14/2016
Time Speed Spacing Tasking Deliverables Review the plans for time, speed, spacing and related capabilities Develop a 15 year plan for deployment: • 5 - year increments 2016-2020, mid – 2021-2025, far term – 2026-2030 • Identify and prioritize tools and technologies ground vs. aircraft • Appropriate in various operating conditions • Preliminary Report to NAC in June • Final Report in Oct
Capabilities Being Examined Ground-based Interval Management – Spacing (GIM-S) Terminal Sequencing and Spacing (TSAS) Path Stretch (with and without Data Communications) Controlled Time of Arrival (CTA) Via Time of Arrival Control (TOAC) Guidance and Automation TBFM including Integrated Departure and Arrival Capability (IDAC) Flight Deck Interval Management (IM): IM En Route and Terminal Operations
78
39
7/14/2016
Preliminary Findings – Interim Report Cultural challenges part of the solution for transition to PBN NAS Ground based metering is essential to successful implementation of PBN FAA investing heavily in Ground Based systems for first two time frames – industry supports Aircraft based system standards developed, capabilities & use in R&D and trials Longer term horizon area of Task Group analysis 79
DISCUSSION
80
40
7/14/2016
Update from PBN Route Structure Task Group Mark Hopkins, Delta Airlines David Surridge, American Airlines Rune Duke, AOPA 81
Key Guiding Principle
Structure where it is needed and no structure where it is not needed … But the devil is in the details!
82
41
7/14/2016
PBN Route Structure Task Elements Task 1 - Use broader expertise and data to refine or validate CONOPs problem statement. Task 2 - Recommend refinement to the criteria-based methodology for establishing low and high altitude PBN route structure. Task 3 - Recommend a NAS-wide point to point navigation strategy. Task 4 - Recommend alternatives to the proposed approach for design and implementation.
83
Members of Task Group Darrell Pennington, Air Line Pilots Association
Joe Bertapelle, JetBlue Airways
Rune Duke, Aircraft Owners and Pilots Association
Lee Brown, Landrum-Brown
Michael Cirillo, Airlines for America
Bennie Hutto, National Air Traffic Controllers Association
Desmond Keany, American Airlines, Inc.
Jim McAllister, National Air Traffic Controllers Association
Michael O'Brien, American Airlines, Inc.
Eric Owens, National Air Traffic Controllers Association
Dave Surridge, American Airlines, Inc. (Chair)
John Vogelsang, National Air Traffic Controllers Association
Rico Short, Beacon Management Group
Bill Wise, National Air Traffic Controllers Association
Mark Hopkins, Delta Air Lines, Inc. (Chair)
Jeff Woods, National Air Traffic Controllers Association
Ed Olsen, Delta Air Lines, Inc.
Nat Iyengar, National Business Aviation Association
Denise Fountain, DoD Policy Board on Federal Aviation
Bob Lamond Jr, National Business Aviation Association
Steve Anderson, Federal Aviation Administration
Ralph Tamburro, Port Authority of New York & New Jersey
John Dutton, Federal Aviation Administration
Trin Mitra, RTCA, Inc.
Cliff Keirce, Federal Aviation Administration
Perry Clausen, Southwest Airlines
Jeff Kerr, Federal Aviation Administration
Rick Dalton, Southwest Airlines
Robert Novia, Federal Aviation Administration
John Brandt, The MITRE Corporation
Gary Petty, Federal Aviation Administration
Shweta Mulcare, The MITRE Corporation
Jeff Richards, Federal Aviation Administration
Jeff Shepley, The MITRE Corporation
Leonixa Salcedo, Federal Aviation Administration
Bill Cranor, United Airlines, Inc.
Lori Zuest, Federal Aviation Administration
Glenn Morse, United Airlines, Inc.
Phil Santos, FedEx Express
Allan Twigg, United Airlines, Inc.
Bill Murphy, International Air Transport Association
Jonathan Bonds, United Parcel Service
84
42
7/14/2016
Schedule of Meetings Thu May 12 Thu Jun 9 [Jun 23 TOC] Thu Jul 14 Thu Aug 11 Thu Sep 15 Thu Oct 13 [Oct 27 TOC] Thu Nov 10 Thu Dec 15 Recommendation in February 2017 85
Activity to Date FAA review of PBN Route Structure CONOPs and route usage data Industry presentations on challenges in current route structure • Briefings from NBAA, NATCA, AA, UA, WN, DoD, AOPA, IATA
Ongoing documentation of initial findings • Guiding principles, Assumptions, Challenges, Additions to Concept, Criteria for Structure, Implementation Approaches
Determination to spin out CONUS Low Altitude and Alaska Low Altitude Sub Groups 86
43
7/14/2016
Usage of Jet Airways Top 20 Most Used Jet Airways
Utilization of Jet Route means • Flight filing/amended flight plan includes airway • Requested final altitude at or above FL180 • 80% conformance to portion of airway aircraft intended to fly
Average Daily Utilization: 145 Average Daily Filings of Routes: 414
Top 20 Most Used Jet Routes
#21-40 Most Used Jet Routes
#41-60 Most Used Jet Routes
#61-80 Most Used Jet Routes
#81-100 Most Used Jet Routes
The 100th most used Jet Route (out of 300) is used only 24 times a day
Utilization vs Filing of Jet Routes Airway J75 J42 J121 J14 J60 J6 J70 J51 J146 J209 J91 J79 J110 J61 J53 J2 J18 J191 J48 J584
CY 2015 Util. 121,321 90,740 74,258 68,814 66,636 66,294 60,151 59,139 47,557 47,315 42,829 39,860 39,613 35,792 35,085 34,499 34,071 33,650 32,369 30,338
CY 2015 Filings 244,715 192,925 255,281 134,672 210,786 204,962 155,906 225,144 156,399 144,283 92,672 209,853 106,119 51,793 136,859 126,935 93,460 97,852 104,866 74,094
In many cases, utilization of Jet Routes is a fraction of filing of those routes in the flight plan
44
7/14/2016
Segment Level Usage Varies A flight plan may include only a portion of an ATS route, so segment level usage may be useful
Victor Route Usage Average Daily Utilization: 24 Airway V3 V16 V39 V1 V23 V229 V44 V317 V66 V374 V29 V123 V166 V2 V157 V4 V433 V495 V139 V165
CY 2015 Util. 22,316 18,460 15,586 14,245 10,977 9,435 8,183 6,514 6,492 6,489 6,428 6,377 6,032 5,559 5,514 5,444 5,315 5,235 4,781 4,774
CY 2015 Filings 70,171 65,640 52,474 54,506 41,983 34,393 30,346 19,741 16,905 15,916 34,574 9,666 12,446 49,902 24,148 29,509 12,235 13,000 49,326 11,993
Average Daily Filings of Routes: 89
• • • •
Most used Victor route used 61 times a day 20th most used 13 times a day 100th most used 4 times a day There are ~700 Victor routes
45
7/14/2016
Need for PBN Route Structure Task Group validates need for a NAS PBN Route Structure: VORs anchor Jet Routes and VOR MON Program will decommission 30% of VORs by 2025 The current route structure lacks flexibility and many routes have low usage Operators utilizing PBN Emerging PBN route structure being done at local level
However… there are many challenges 91
Some of the Challenges Interdependencies • VOR MON, Data Comm, PBN Sequencing and spacing, NSAAP, LOA/SOP, ERAM functionality
What do we mean by routes? • Full routes or route segments? • Dynamic routes based on Wx/demand?
How do flight planners understand constraints and options for routing each day? Need for facility changes for benefits of route structure Alignment of new technology and capability on flight deck, flight planning systems and ATC FMS database capacity
92
46
7/14/2016
High Altitude Point to Point December 2000 2000 – 2007
RTCA produces High Altitude Concept High Altitude Redesign Program
2008 – 2011
High Altitude Airspace Management Program
September 2009
Task Force 5 recommendations on High Altitude
2012 – present 2014 – 2015
Q-routes under PBN Program Office PBN National Route Structure Con Ops development 93
HAR Vision – November 2002 Source: Brief to ATCSCC on Phase 1 Implementation
94
Source: FAA
47
7/14/2016
Current Example of NRS Usage AAL179: Pref Route: 2354 nm / NRS 2226 nm 550+ flights JFK-SFO per sampled month JFK-SFO PREF ROUTE JFK..GAYEL.J95.BUF.J16.ECK.J38.GRB.J106.GEP.J70.ABR.J32.FMG..ILA..PYE..SFO
AAL179 – Feb 25 JFK..COATE.J36.BAE..KP75E..KD66U..KU51K..RUMPS..OAL.MOD3.SFO
Source: FAA 95
PBN Route Structure Tasking – Low Altitude Sub Groups Rune Duke, AOPA Chair, PBN Route Structure Low Alt Sub Groups 96
48
7/14/2016
Approach for Low Altitude Spun out two Low Altitude sub groups – for CONUS and Alaska • CONUS discussion includes: the MON’s impact, helicopter routes, and need to provide minimum altitude information • Alaska has unique route considerations due to unusual operating conditions
Address compatibility with high altitude group Diverse participation •
Helicopter Association International
•
United Parcel Service
•
Southwest Airlines
•
Alaska Airmen’s Association 97
Schedule for Low Altitude Groups CONUS Low Altitude group • Meetings planned for June 29th and July 13th • Balance of year will conduct Low Alt group meetings on Friday after High Alt group meets
Alaska Low Altitude group • Aligning PBN RS Sub Group activity with Western Service Center Alaska Enroute Navigation Team (AKENT) • Kickoff telecom on July 20th and planning two two-day meetings in SEA during rest of the year
98
49
7/14/2016
Closing Comments Designated Federal Official: Lynn Ray, Federal Aviation Administration Co-Chairs: Bryan Quigley, United Airlines Dale Wright, NATCA
99
Next Meetings: October 27, 2016 February of 2017 Washington, DC 100
50
7/14/2016
Adjournment
101
51
