1 / 24

Performance Based Navigation

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)

emily
Download Presentation

Performance Based Navigation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Performance Based Navigation Erwin Lassooij Technical Officer/ FLS section

  2. Presentation overview • PBN – Background • PBN – Concept • PBN – Status • PBN – Implementation

  3. 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

  4. BackgroundICAO 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

  5. BackgroundIndustry’ 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.

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

  7. RNP in relation to area navigation Area Navigation Other RNAV RNP

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

  9. 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

  10. 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

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

  12. Area of Application Nav accuracy Designation of navigation standard: Current situation Designation of navigation specification: PBN concept (new) 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 existing navspecs Simplification results in lower costs for Operators and ANSP

  13. 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 Harmonization of RNAV operations not covered by existing nav specs 1-0.1

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

  15. ICAO ProvisionsPerformance 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 * Work in progress

  16. 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

  17. 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

  18. 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

  19. 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

  20. 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

  21. Familiarization- Computer Based Training

  22. 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 Bangkok 10-14 September 2007 Dakar 14-18 January 2008 Nairobi 21-25 January 2008 Lima 16-20 June 2008

  23. 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.

More Related