Performance Based Navigation Erwin Lassooij Technical Officer/ FLS section

Presentation overview PBN – Background PBN – Concept PBN – Status PBN – Implementation

Aviation challenges : Growing demand for RNAV approaches (safety, accessibility) Growing demand for solutions to airspace congestion Growing fuel efficiency requirements Growing Environmental requirements Most can be met with current technology, but standardization and operational requirements have to be put into place

Background ICAO RNP concept FANS identified need for performance based navigation and developed Required Navigation Performance capability concept : To avoid need for ICAO selection between competing systems Manual on Required Navigation Performance (doc 9613) Addressed only the en-route phase of flight (RNP-10 and RNP-4) for oceanic and remote applications No ICAO RNP requirements for continental enroute and terminal applications. This led to: Proliferation of national standards Wide variety of functional requirements Variety of required navigation sensors Differing air crew requirements Lack of global harmonization

Background Industry’ s RNP concept RNP concept has continued to evolve outside ICAO RTCA/EUROCAE defined performance and functional requirements Industry‘s RNP requires performance monitoring and alerting Conflict Current ICAO concept does not require performance monitoring and alerting Now we have two RNP concepts.

Are we now going the right way? P R E S N T Boeing Europe US Australia Canada South America China Japan Airbus F U T R E B-RNAV P-RNAV US-RNAV RNP10 RNP 4 RNP RNP/RNAV Not safe, not efficient, costly, confusing

RNP in relation to area navigation Other RNAV

RNP-where we are today Area Navigation Other RNAV RNAV (GNSS) LAAS Basic-GNSS RNP APV LPV GAGAN GRAS WAAS Other RNAV LAAS LNAV LNAV/VNAV SBAS GBAS Baro-VNAV Galileo BRNAV USRNAV A USRNAV B PRNAV etc etc.

ICAO Recognizes the problems Need for focal point in ICAO to address problems experienced with RNP Concept (GNSSP/4 recommendation 1/1) ANC approves establishment of Required Navigation Performance Special operational requirements Study Group (RNPSORSG) as coordinating group

Adjustment to the RNP concept required Clear distinction between operations that require performance monitoring and alerting and operations that don’t require performance monitoring and alerting Functionality requirements Harmonization of current RNAV and RNP operations Development of new navigation specification to meet operational demand. Need for clear operational approval requirements Need for clear implementation guidance

RNP revised towards PBN PBN is anchored in detailed navigation specifications, which contain performance and functionality requirements. Area Navigation RNP PBN Other RNAV Other RNAV RNAV x RNP x No on-board performance monitoring + alerting on-board performance monitoring + alerting

Harmonization of existing navspecs   Harmonization of existing navspecs Area of Application Nav accuracy Designation of navigation standard: Current situation Designation of navigation specification: PBN concept (new) Simplification results in lower costs for Operators and ANSP Oceanic/ Remote 10 RNP 10 RNAV 10 (RNP 10 label) 4 RNP 4 RNP 4 EnRoute- Continental 5 RNP 5 Basic RNAV RNAV 5 En Route - Continental and Terminal 2 USRNAV type A RNAV 2 . Terminal 1 USRNAV type B and P-RNAV RNAV 1      

Harmonization of RNAV operations not covered by existing nav specs   Harmonization of RNAV operations not covered by existing nav specs Area of Application Nav accuracy (NM) Designation of navigation standard: Current situation Designation of navigation specification: PBN concept (new) Terminal 1 Basic-GNSS SBAS Basic-RNP 1 Approach 1-0.3 Basic-GNSS (Baro-VNAV) SBAS RNP APCH Approach RNP SAAAR (US) RNP AR APCH 1-0.1    

Approach and landing operation Approach procedures vertical guidance required minima type Flight technique NPA RNP APCH no MDA dive and drive CDFA (e.g. using baro-vnav) APV RNP AR APCH barometric DA vertical guidance SBAS APV I/II geometric PA GBAS Cat I

RNP SORSG Performance Based Navigation Concept No perf. monitor and alerting Perf. Monitor and alerting RNAV 10 RNP 4, Basic-RNP 1 RNP APCH, RNP AR APCH Performance based navigation (PBN) Area navigation based on performance requirements for aircraft that are described in navigation specifications

ICAO Provisions Performance Based Navigation Manual PBN Manual to provide a “one-stop shop” for States on how to implement RNAV and RNP in their airspace PBN Manual consists of two volumes: Volume I – Concept and Implementation Guidance Concept of PBN and how it is used Implementation Guidance to States / Regions Volume II – Implementing RNAV and RNP Compendium of Navigation Specifications RNAV 10 RNAV 1 RNP APCH RNAV 5 RNP 4 RNP AR APCH RNAV 2 Basic RNP 1 Advanced RNP 1* RNP 2* * Work in progress

Current status Final draft of PBN manual is finalized and posted on ICAO-NET State Letter with Navigation Specifications is on ICAO-NET AN 11/45-07/22

PBN implementation goals Enroute airspace (where RNAV ops required) Area of operation: Oceanic and remote airspace Applicable navigation specifications: RNAV 10 and RNP 4 Implementation strategy: 100% implementation by 2010 Area of operation: Enroute continental Applicable navigation specifications: RNAV 5, 2, and 1, Implementation strategy: 100% by 2014

PBN implementation goals Terminal airspace (where RNAV ops required) Area of operation: Terminal area Applicable navigation specifications: RNAV 1,2 and Basic-RNP 1 Implementation strategy: 100% by 2016

PBN implementation goals Approach Area of operation: Approach (RNP) Applicable navigation specifications: RNP APCH RNP AR APCH (if normal straight-in approach is operationally not feasible) Implementation strategy: All instrument runways: APV to all runway ends by 2016. NPA where APV is operationally not possible

Implementation Leadership role for ICAO Familiarization Implementation Optimization of ICAO provisions States Develop implementation plan by 31/12/2009 Follow through with plan Stakeholders cooperate with States in their implementation commit the resources necessary to carry out their part of the strategy

Familiarization - Computer Based Training

Familiarization “Introduction to PBN” Seminar Moscow 14-18 April 2008 Montreal 13-15 June 2007 Brussels 21-25 April 2008 Cairo 12-14 November 2007 New Delhi 17-21 September 2007 Mexico City 23-27 June 2008 Dakar 14-18 January 2008 Bangkok 10-14 September 2007 Nairobi 21-25 January 2008 Lima 16-20 June 2008

Summary PBN concept is established Familiarization is imminent ICAO must assume leadership role in implementation: Close coordination between ANB, TCB and regional offices necessary Speak with one voice to States and stakeholders Commitment and active involvement required from States and other stakeholders.