Performance Based Navigation Today & Tomorrow An FAA Perspective Presented by: John Barry AIR-131 Aero Engineer/Tech Pilot Aircraft Certification Presented to: OSWG Date: March 2016

PBN Qualification & Ops Approval What’s PBN & RNP? RNP AR(?) Ongoing RNP AR Approvals PBN Guidance Material Future Challenges for PBN

PBN(?) Terminology What’s PBN? What’s RNAV? ─ Area Navigation Performance-Based Navigation → RNAV & RNP What’s RNAV? ─ Area Navigation What’s RNP? ─ Required Navigation Performance Area Navigation (RNAV) + (monitoring & alerting) What about “RNAV (GPS)”? RNAV (GPS) approach is an RNP approach → RNP APCH No change in titling approach procedures No requirement for a new airworthiness approval!

RNP AR Terminology RNP with Authorization Required → PBN! FAA Perspective → Like Cat II & Cat III ILS Aircraft Qual + Flight Crew Qual = Safe Ops Qualification is not for every pilot/operator or OEM Intended to provide specific benefits at specific locations Ops approval requires → Ops Specs, M Specs, LOA AFM should not imply ops qualification Recommend Note → “…ops approval required…” “RNP SAAAR” became “RNP AR” Change in AC 90-101A → harmony w/ICAO PBN Manual March 2011 AIRAC cycle update to all pubs

RNP AR Operational Concept Safety Assurance Philosophy No change in hazard ID & mitigation → TLS 1×10-7 Took advantage of existing airworthiness approvals Applies to new airworthiness projects – contact us! Remain “New” Airworthiness & Ops Concepts No published FAA guidance prior to AC 90-101 (2005) Still evolving → AC 90-101A & AC 20-138D RNP AR Approach Operational Success Requires Close Coordination Across Disciplines Procedure Design Aircraft Performance & Design Operations

Applications of RNP AR Criteria Approach minimums lower than existing minima Increased arrival & departure rates for adjacent airports involved Arrival capacity gains up to 50% over single runway operations Arrival capacity gains up to 60% vs. single runway ops Hundreds of runway ends 10 to 15 Top Airports 15 to 20 Top Airports Single Runway Access Adjacent Airport Operations Converging Operations Parallel 36 16L 16R 9 Airport A Airport B 36L Conventional 36R RNP 750’ - <5000’ Parallel dependent (staggered by ATC radar 1 ½ - 2 miles diagonally on adjacent courses) and simultaneous independent approaches, dual & triple, as currently authorized for ILS/MLS, is one potential RNP application. RNP Parallel Approach Transition (RPAT), where RNP aircraft fly a guided offset path and apply visual separation from ILS traffic with runway centerline spacings as little as 750 feet, is another. Due to inherent capabilities to tailor missed approach paths and to positively restrain protected airspace, RNP promises to lower operational weather minima for Simultaneous Converging Instrument Approach (SCIA) procedures. Rather than reverting to straight-in approaches in less than visual weather conditions that conflict with arrivals/departures at adjacent airports, RNP approaches with curved, guided paths can be designed to de-conflict operations and maintain system capacity. RNP obstacle evaluation areas are typically linear, in contrast to conventional splays, and are scalable by changing RNP values. Combined with the flexibility of curved paths, obstacles can be avoided and approach minima reduced at challenging locations.

RNAV & RNP Guidance Material FAA AC 90-100A → Terminal & En Route RNAV Ops FAA AC 90-105A* → RNP Ops & Baro-VNAV Departure, arrival & approach ops → advanced features FAA AC 90-101A → Ops & Airworthiness Criteria Alternate means of compliance for monitoring GPS “RNP SAAAR” become “RNP AR” → international harmony FAA Order 8260.58 → PBN Procedure Design Updated RNP AR missed approach design criteria Harmonized with ICAO PANS-OPS PBN criteria ICAO Performance-Based Navigation (PBN) Manual Doc 9613 → based on U.S./EASA criteria → expanding

ICAO Performance-Based Navigation (PBN) Manual Doc 9613, Version 4 Volume I – PBN Concept & Implementation Guidance Volume II – Implementing RNAV & RNP Operations

ICAO PBN Manual Volume I – Concept & Implementation Guidance Part A – PBN Concept PBN? Airspace Stakeholders Use of PBN Part B – Implementation Guidance Implementation Processes Identifying an ICAO Navigation Specification “RNAV everywhere…RNP only where you need it” Validation & Implementation Planning

ICAO PBN Manual – Volume II Implementing RNAV & RNP Operations Part A – General Introduction to PBN Operations On-Board Performance Monitoring & Alerting Safety Assessment Considerations Navigation Service Monitoring Part B – Implementing RNAV Operations Implementing RNAV 10 Implementing RNAV 5 Implementing RNAV 1 & RNAV 2

ICAO PBN Manual – Vol II, Part C Implementing RNP Operations Chapter 1: Implementing RNP 4 Supports use of “30-30” separation in oceanic & remote GNSS is the primary navigation sensor Aircraft Eligibility: RNP certification; prior nav system certification; or new technology Does not require new certification Aircraft Requirements: On-board performance monitoring & alerting Functional requirements (i.e. parallel offset, WGS-84 ref) Operating Procedures Navigation Database – DO-200A compliant (exp. LOA)

ICAO PBN Manual – Vol II, Part C Implementing RNP Operations Chapter 2: Implementing RNP 2 Oceanic/remote airspace & remote continental airspace Continuity requirements differ – navaid infrastructure Route separation to be determined Chapter 3: Implementing RNP 1 Supports terminal arrival & departure procedures Based on GNSS – DME/DME navigation “too complex” Can apply RF legs & baro-VNAV performance Both navigation specs rely on: aircraft requirements & functionality; ops procedures & training; & navigation database – no new certification required!

ICAO PBN Manual – Vol II, Part C Implementing RNP Operations Chp 4: Implementing Advanced RNP (A-RNP) Single assessment – applies to multiple navigation accuracy applications – multiple nav specs & multiple phases of flight Applies to: RNAV 5, RNAV 2, RNAV 1, RNP 2, RNP 1 & RNP APCH Intended to support multiple operations approvals in an expeditious manner No need for re-examination of aircraft eligibility per each navigation specification

A-RNP Functions RF Legs Required RNP Scalability Optional Fixed Radius Transitions (FRT) Optional Time of Arrival Control (TOAC) Optional Baro-VNAV Optional Higher Continuity Optional

ICAO PBN Manual – Vol II, Part C Implementing RNP Operations Chapter 5: Implementing RNP APCH Section A: RNP APCH ops to LNAV & LNAV/VNAV mins May use GNSS vertical guidance to LNAV/VNAV mins Section B: RNP APCH ops to LP & LPV mins SBAS is one means of GNSS compliance RNP APCH accuracy values: “1-1-0.3-1” for initial, intermediate, final, & missed approach segments of the procedure States may require operations approval RNP APCH is titled: “RNAV (GPS) RWY XX” “RNAV (GNSS) RWY XX”

ICAO PBN Manual – Vol II, Part C Implementing RNP Operations Chapter 6: Implementing RNP AR APCH Unique due to reduced obstacle clearance & advanced functional requirements Obstacle clearance based on 2×RNP w/no secondary OCS May apply RNP accuracy values between 0.3 & 0.1 Requires compliance with vertical error budget Requires an alert when GNSS updating is lost May use GNSS vertical guidance in lieu of baro-VNAV For RNP AR APCH missed approach ops requiring less than 1.0 to avoid obstacles or terrain, the loss of the display of lateral guidance is a hazardous (severe-major) failure condition.

ICAO PBN Manual – Vol II, Part C Implementing RNP Operations Chapter 7: Implementing RNP 0.3 Supports helicopters eligible for flight under IFR Applies to terminal & en route phases of flight Reduced protected airspace – separation from fixed-wing Low-level, obstacle rich environments The large majority of IFR helicopters are already equipped with TSO C145/146 SBAS systems and moving map displays; and they require autopilot, including stability augmentation, for flight under IFR.

ICAO PBN Manual – Vol II, Part C Implementing RNP Operations Appendix 1: Radius-to-Fix (RF) Path Terminators Appendix 2: Fixed Radius Transitions (FRT) Appendix 3: Time of Arrival Control (TOAC) Attachment A: Barometric VNAV Attachment B: Sample airspace concept based on PBN Manual nav specs applications

Future Challenges for PBN OEM Compliance → aircraft & avionics Make PBN compliance part of airworthiness projects → new TCs, STCs, navigation-related projects Develop clear, concise AFM entries; recommended flight crew operating procedures; avionics operating guides Update & enhance our guidance material → example: refine guidance on demonstrating flight technical error Must ensure PBN aircraft eligibility becomes part of projects’ system safety assessments → any impact? International Harmonization ICAO PBN Manual, Doc 9613 & PANS-OPS → update!! International implementation remains to be seen

Challenges for RNP AR Ops Approval No aircraft type design in full compliance New aircraft type designs → certification plan??? No flight crew procedures from aircraft OEM Customers do not use OEM checklists? → OEM should still define specific RNP AR flight crew procedures by aircraft type & configuration If no OEM procedures, more FAA oversight required Multiple variants of a single aircraft type design Variations in avionics require specific recognition ─ tail # by tail # ─ of aircraft qualification in ops application Application should breakout major systems impacting RNP AR aircraft performance Need RNP capability documentation

What’s the bottom line?

Ongoing RNP AR Approvals Aircraft OEMs → AFM & Flight Crew Ops Manual Boeing, Airbus, Gulfstream, Embraer, Cessna Customers conducting/desiring RNP AR approach ops Defining/defined/redefining aircraft qualification Ops approvals require mitigations/limitations → shortfalls in aircraft qualification → aircraft mod/evaluations underway Other aircraft OEMs being pushed by customers Avionics OEMs Honeywell (Pegasus, Primus Epic, NG), GE (737NG) Rockwell Collins, Universal, CMC, Thales… → defining/redefining compliance Use of SBAS vertical guidance → exceeds requirements

Ongoing RNP AR Approvals 3rd-Party Facilitators can play a key role in approval! Application package preparation → they know the requirements & the “answers to the test” Can facilitate requirements compliance as operator’s rep → example: RNP AR database management Can design RNP AR instrument approach procedures for public use → experts in use Order 8260.52() criteria Overall impact? → Lightens the load on FAA resources Approved 3rd-Party Facilitators: GE (Naverus), Honeywell, Boeing, Jeppesen, Airbus

RNP AR Ops Approvals Recent Operational Approvals: United 787 BP3 Virgin America A320 new deliveries Cathay Pacific 777 Qatar 777 NetJets Int’l – Aspen Special jetBlue – Embraer temp comp Numerous Gulfstream Operators – G450/550 (RNP 0.30) Delta A319/320 American 787 Act Two Falcon 900 EX Miami Air 737 Numerous applications staged &/or pending Needs current list, esp 129 carriers

Aircraft & RNP AR Ops Approval Boeing aircraft performance details found in the RNP Capabilities Documents – by aircraft type Incomplete documentation led to 2008 memo of understanding between Boeing, FAA & operators to specific RNP AR requirements Example: B767 does not meet the RNP AR vertical error budget & requires unique pilot vertical deviations limits Boeing revising all RNP Capabilities Documents Began in Fall 2015 with 777 and 787 747 and 737 in review 757, 767 to complete this year Different capabilities with different customer options Operator must provide listing of Optional Program Code selections for each hardware and software configuration

Aircraft & RNP AR Ops Approval Airbus aircraft performance details found in the Airbus Compliance Documents Airbus aircraft configurations are not common, even within a single type design (i.e. A300 configuration not common) Each operator must provide a copy of the ACD applicable to their particular aircraft

John Barry/ AIR-131 / 202-267-1665 John.C.Barry@faa.gov Questions? John Barry/ AIR-131 / 202-267-1665 John.C.Barry@faa.gov