Performance Based Navigation PBN Study Group Final Meeting

Performance Based Navigation (PBN) Study Group – Final Meeting PBN Manual Status May 18, 2012 Dave Nakamura Chair, PBNSG

Topics • Background • Volume I and II, Navigation Specifications, Attachments & Appendices •

PBN Study Group Members and Advisors Dave Nakamura Erwin Lassooij Jeff Cochrane Waldemar Krolak Benoit Roturier Antoine Herve Geoff Burtenshaw Mark Steinbicker Barry Miller Nick Tallman Joe Mc. Carthy Franca Pavličević Alex Fisher Christophe Caillaud Michel Calvet Barbara Cassidy [Julio Cesar de Souza Pereira] Carlos Cirillo Didier Delibes Ed Hajek Makoto Eguchi Patrick Harbord Eduardo Juranovic Henrik Nielsen Copyright © 2006 Boeing. All rights reserved. Roland Rawlings Pedro Rivas [Bjarni Stephansson] Theo Van de Ven Dave Van Ness Honghai Yang Rick Leeds Michinobu Utsunomiya, Hirotaka Mori John Kasten Dave Behrens Rob Eagles Ross Dennerstein Ian Mallett Houston Anthony Grady Boyce Veronique Travers Andrew Beadle Ron Tidy Thomas Buchanan Koichiro Kubo Dirk Noordewier Ron Doggett

Background Work Program Copyright © 2006 Boeing. All rights reserved.

Background ICAO Performance Based Navigation Concept Airspace Concept Com Nav Surv ATM Nav Applications Nav Specifications RNAV 10 (RNP 10) RNAV 5 RNAV 2 RNAV 1 Copyright © 2006 Boeing. All rights reserved. Nav Infrastructure RNP Specifications RNP 4 RNP 2 RNP 1 Advanced RNP 0. 3 RNP APCH RNP AR APCH RNP w/ Added Requirements e. g. 3 D, 4 D 5

Background Navigation Specifications Applications reflect performance/functional requirements FLIGHT PHASE APPROACH NAVIGATION SPECIFICATION En Route Oceanic / En Route Remote Continental ARR RNAV 10 (RNP 10) 10 Initial Intermed Final Missed DEP RNAV 5 5 5 RNAV 2 2 2 RNAV 1 1 1 2 or 1 1** 1** 1** 0. 3 1 1 0. 3 1 1 - 0. 1 0. 3 - 0. 1 1 - 0. 1 RNP 4 4 RNP 2 2 2 RNP 1 Advanced RNP 2 RNP 0. 3 RNP APCH RNP AR APCH Copyright © 2006 Boeing. All rights reserved. 2 0. 3 ** includes optional function of RNP scalability

Volume I Vol I, Part B Major update to implementation processes based upon lessons

Volume I Operations Approval Guidance Attachment C to Vol I Objective Provide a high level summary of operational approval processes for general awareness, and complement the new operations approval manual. Rationale Operations approval identified from seminars, Go Team activities and general enquiries as one of the major hurdles for the global implementation of PBN. Copyright © 2006 Boeing. All rights reserved.

Volume II Navigation Specifications Implementing RNP 2 Chapter 2, Vol II, Part C Objective RNP 2 is primarily intended for a diverse set of en route applications; particularly in geographic areas with little or no ground NAVAID infrastructure, limited or no ATS surveillance, and low to medium density traffic , Oceanic/Remote and Continental applications Rationale This provides a solution where RNP routes can be implemented as an element of improved airspace design and traffic flow. Issues • The higher continuity option will need to be addressed through operational approval and flight planning. Copyright © 2006 Boeing. All rights reserved.

Volume II Navigation Specifications Implementing Advanced RNP Chapter 4, Vol II, Part C Objective Provide for RNP operations where the RNP is applicable to all phases of flight, and with RNAV holding, parallel offset, & Radius to Fix as required and Fixed Radius Transition and RNP scalability from 0. 3 to 1. 0 NM, for terminal airspace, as options. Rationale Provides • A means for a single aircraft qualification • Improved airspace capabilities via Advanced RNP functionality • Significantly enhanced approach and departure capabilities Issue • This provides value through it’s operational applications but is sufficiently complex that additional ICAO information and implementation guidance is strongly recommended. Copyright © 2006 Boeing. All rights reserved.

Volume II Navigation Specifications Implementing RNP 0. 3 Chapter 5, Vol II, Part C Objective Provide for RNP operations predicated on rotorcraft RNP systems using TSOC 145()/C 146() functionality Rationale Rotorcraft RNP systems contain the capability for performing RNP operations where improved heliport access and routing through dense airspace is facilitated. Note: This may also be used for qualified fixed wing aircraft. . Copyright © 2006 Boeing. All rights reserved.

Volume II Navigation Specifications Implementing RNP AR APCH Chapter 6, Vol II, Part C Objective Extend RNP AR to address departure. Rationale Initial specification only addresses approach, omitting departure. AR operations are needed for departures from some of the very same runways where AR approach exists. Issues • Not accomplished due to lack of a focal and time. A future action is required due to the demand for departure guidance material. • Outgrowth of discussions identified the need for guidance material concerning use of PBN for one engine inoperative. procedures e. g. , at ICAO Ops Panel. Copyright © 2006 Boeing. All rights reserved.

Volume II Navigation Specifications Radius To Fix (RF) Path Terminator Appendix to Vol II, Part C Objective Provide for fixed radius turns in non-RNP AR APCH applications, where operational improvements can be achieved e. g. environment, access and terrain/obstacles are not a factor. Applicable only on RNP terminal airspace procedures (SID/STAR) and on approach operations outside of the final approach segment. Rationale Provide a predictable and repeatable ground track where fixed ground tracks are required to achieved reduced separation minima, improved traffic flow, or reliable turn performance. Copyright © 2006 Boeing. All rights reserved.

Volume II Navigation Specifications Fixed Radius Transition (FRT) Appendix to Vol II, Part C Objective Provide for fixed radius transitions along RNP ATS routes [for use with Advanced RNP and RNP 2] Rationale Provide a predictable and repeatable ground track where fixed ground tracks are required to achieved reduced separation minima, improved traffic flow, or reliable turn performance. Copyright © 2006 Boeing. All rights reserved.

Volume II Sample Airspace Concept Based On Nav Specs Attachment B to Vol II Objective Provide examples of route spacing achieved per flight phases [with and without radar surveillance] using PBN in specific environments Rationale Following the removal of Attachment B to Annex 11, it was necessary to locate the sample route spacing in another ICAO document. It also is a response to frequent enquiries on the subject. Copyright © 2006 Boeing. All rights reserved.

Conclusions • PBNSG has completed its work on the update to the PBN Manual. • It is recommended that ICAO proceed with publishing the manual. • Shortcomings with filing of PBN in the 2012 ATC FPL identified, which will need to be addressed pre-FF ICE. • Consequential changes [for routes with FRT] are required to ICAO documentation including Annex 11. • It is recommended that ICAO develop supporting guidance/information for the new navigation specifications, especially Advanced RNP. • The timeline for implementation will need to reflect development of supporting guidance material and implementation processes by States. • It is anticipated that future actions will be necessary post-PBNSG to support implementation. • The PBNSG is willing to support ICAO on PBN related papers to ANC/12. Copyright © 2006 Boeing. All rights reserved.