1 / 24

Performance Based Navigation leading towards a performance based Airspace concept

Performance Based Navigation leading towards a performance based Airspace concept. Erwin Lassooij Manager Performance Based Navigation Programme ICAO. Presentation overview. PBN – background PBN - Concept RCP and RSP Overview of presentations on Thursday. Aviation challenges. :

miguela
Download Presentation

Performance Based Navigation leading towards a performance based Airspace concept

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 Navigationleading towards a performance based Airspace concept Erwin Lassooij Manager Performance Based Navigation Programme ICAO

  2. Presentation overview • PBN – background • PBN - Concept • RCP and RSP • Overview of presentations on Thursday

  3. Aviation challenges : • Growing demands for RNAV approaches (safety, accessibility) • Growing demands for solution airspace congestion • Growing fuel efficiency requirements • Growing Environmental requirements • Can be met with most of 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) • Emphasize on 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. • Proliferation of national standards • Wide variety of functional requirements • Variety of required navigation sensors • Differing air crew requirements • Lack of global harmonization

  5. NonPrecision Approach Approach with Vertical guidance (APV) Precision Approach RNAV (GNSS) Basic-GNSS RNP APV LPV GAGAN GRAS WAAS LAAS LNAV LNAV/VNAV SBAS GBAS Baro-VNAV Galileo Approachproliferation of types Non-Precision Approach Precision Approach Definition of operations become very blurred Need for performance requirements and possibly need for reclassification Etc. Etc. Etc.

  6. 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 and alerting • Now we have two RNP concepts.

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

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

  9. What needs to be done • Original RNP concept in principle good, however… • Adjustment to the RNP concept required. • Clear distinction between operations that require performance monitoring and alerting and operations that don’t require • Harmonization of current RNAV and RNP operations • Development of new navigation specification to meet operational demand. • Need for clear operational approval requirements • Clear implementation guidance

  10. Require on-board performance monitoring + alerting Do not require on-board performance monitoring + alerting Agreeing PBN • PBN specifies RNAV system performance i.e. accuracy, integrity, continuity, availability + functionality; - written up in navigation specifications This is different than the RNP concept, which stressed navigation accuracy and ‘stopped’ at required performance.However, PBN is anchored in detailed navigation specifications, which contain performanceand functionality requirements. RNAV X specifications RNP X specifications

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

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

  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 existing RNAV operations not covered by nav specs • RNP approach for lowest common denominator • Meets RNP0.3 in final segment • Basic GNSS/SBAS • Functionalities: VNAV optional • No Special authorization required 1-0.1

  14. 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 existing RNAV operations not covered by nav specs • RNP approach for lowest common denominator • Meets RNP0.3 in final segment • Basic GNSS/SBAS • Functionalities: VNAV optional • No Special authorization required • Scaleable RNP (0.3 – 0.1NM) • Functionalities: VNAV, RF legs • Authorization required (small protection area) • Operational approval • Aircraft qualification 1-0.1

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

  16. 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 being developed: Two Volumes: • Volume I – An Application of RNP and RNAV • Concept of PBN and how it is used • Implementation Guidance to States / Regions • Volume II – Compendium of Navigation Specifications * Work in progress

  17. EUROPE B-RNAV US Boeing P-RNAV Australia US-RNAV China Airbus RNP10 Canada Japan RNP 4 South America PBN Convergence…. F U T U R E P R E S E N T PBN PBN RNPSORSG initiatives

  18. PBN RCP RSP Context of PBN Airspace Concept Airspace Concept ATM COM NAV SUR

  19. Required Communication Performance (RCP) Initiation • Response to Recommendation 2/2 of the fourth meeting of the Aeronautical Mobile Communications Panel (AMCP/4, Montreal, April 1996). • Air Navigation Commission tasked the Automatic Dependent Surveillance Panel (renamed as the Operational Data Link Panel (OPLINKP) in 2000) to develop the concept of RCP.

  20. Required Communication Performance (RCP) Achievements • In 2001, the OPLINKP completed its Concept of Required Communication Performance document which became the basis for the Manual on Required Communication Performance (RCP) (Doc 9869) (available on the ICAO NET). • In 2003, a continuation of the work on RCP was endorsed at the Eleventh Air Navigation Conference in the light of the urgent need for global harmonization of communication performance measures and support the efforts of States to transition to performance-based operations, a critical aspect of evolving to a safer and more efficient global ATM environment.

  21. Required Communication Performance (RCP) Critical elements of the concept • Required communication performance (RCP). A statement of the performance requirements for operational communication in support of specific ATM functions. • RCP is performance-based, human-centred, operationally significant, independent of specific technologies and applicable to both voice communications and data link communications. ICAO provisions: • Recent amendments to Annex 6, 11 and the PANS-ATM include the initial high-level provisions necessary to support the introduction of RCP. (Applicable 22 November 2007).

  22. Required Surveillance Performance (RSP) Initiation • Need identified by ICAO to complement PBN and RCP • Work programme currently established by ICAO • RSP can be used for both existing and future surveillance applications, airborne as well as terrestrial. It is envisaged that RSP will interact with other performance parameters (PBN, RCP) in meeting Required Total System Performance levels.

  23. Detailed presentations • Introducing PBN • Mr. Alex Hendriks, EUROCONTROL, • Mr. Jeff Williams, US FAA • Mr. John Mc Graw US FAA • Stake Holders perspective on PBN • Mr. Yoshiki Imawaka, JCAB • Mr. Dave Nakamura, ICCAIA • Mr . Dave Behrens, IATA • PBN – The future • Mr. Erwin Lassooij, ICAO • Progress on RCP • Mr. Tom Kraft, US FAA • Progress on RSP • Mr. Massoud Paydar, ICAO

  24. END Thank you for your attention!

More Related