300 likes | 590 Views
The Future on RNAV and RNP. Presented by Erwin Lassooij. NAM/CAR/SAM Regional Seminar on RNAV and RNP Implementation Mexico City, Mexico, 11 to 13 August 2005. The Future on RNAV and RNP Goal of presentation. To update on the current issues
E N D
The Future on RNAV and RNP Presented by Erwin Lassooij NAM/CAR/SAM Regional Seminar on RNAV and RNP Implementation Mexico City, Mexico, 11 to 13 August 2005
The Future on RNAV and RNPGoal of presentation • To update on the current issues • To inform on the status of the concept of RNAV and RNP • To inform about the products to be delivered by ICAO • To inform on the envisaged timeline
History FANS identified need for performance based navigation and developed: Required Navigation Performance capability (RNPC) concept: Parameter describing lateral deviations from assigned or selected track as well as along track position fixing accuracy on the basis of an appropriate containment level
RNP History • 1990: RGCSP noted that capability and performance were distinctively different. • Airspace planning needs measured performance, not designed in capability RNPC
Current ICAO RNP concept • Required Navigation Performance (RNP). A statement of the navigation performance necessary for operation within a defined airspace. • RNP type. A containment value expressed as a distance in nautical miles from the intended position within which flights would be at least 95% of the total flying time E.g. RNP4 represents a navigation accuracy of +/- 4 NM on 95% basis
Current ICAO RNP concept Current applications: • RNP 10 • RNP 4 Both are oceanic applications Containment based on: • Accuracy • Functional integrity • Continuity • Availability
Industry developments • Need for RNP in the terminal airspace • ICAO concept deemed not sufficient to obtain realistic separation standards (99.9% probability required) • RTCA developedRNP RNAVconcept (RTCA DO236)
Industry developments • Main differences between ICAO (RNP) and industry (RNP RNAV) concept: Functional integrity vs Containment integrity and continuity
Industry developments Integrity (ICAO doc 9613): The ability of a system to provide timely warnings to users when the system should not be used for navigation. Containment integrity (RTCA doc 236): A measure of confidence in the estimated position, expressed as the probability that the system will detect and annunciate the condition where the TSE is greater than the cross track containment limit.
Problems arise • Two different standards with similar terminology • RNP manual (Doc 9613) does not provide sufficient guidance for implementation Confusion!
Problems arise • States, in many cases do not have the full picture how to implement, e.g. relation between ops approval and airspace planning
Mismatch of Coordinate Datums In different coordinate systems, approach doesn’t aim at runway threshold. Localizer Runway
Need for focal point in ICAO to lead further development of RNAV and RNP Problems arise • States, in many cases do not have the full picture how to implement, e.g. relation between ops approval and airspace planning • Proliferation in States (PRNAV, USRNAV, RNP1, approach procedure specials etc.)
RNPSORSG ANC approves establishment of Required Navigation Performance Special operations requirements Study Group as coordinating group
RNP SOR SG Concept • Common understanding of the RNP concept and the relationship between RNP and RNAV functionality
RNPSORSGRNP Concept • Main issue to address was the term “containment”: • ICAO does not currently require integrity on the system to detect and annunciate where TSE is greater than cross track containment limit • RTCA does require containment integrity and containment continuity
RNPSORSGConcept RNPSORSG agreed there is a need for Navigation Specifications with and without containment integrity and continuity
RNPSORSGConcept • Operations without containment integrity to be designated as RNAV • Designation should be clear • Operations with containment integrity to be designated as RNP
RNP SOR SGHarmonization • Common understanding of the performance based navigation concept and the relationship between RNP and RNAV functionality • Harmonization between States
Area of Application Nav accuracy Designation of navigation standard: Current situation Designation of navigation standard: new RNP concept Oceanic/ Remote 10 RNP 10 RNP 10 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 P-RNAV RNAV 1 RNP SORSG - Harmonization RNAV 10?
RNP SOR SGApproach • Common understanding of the performance based navigation concept and the relationship between RNP and RNAV functionality • Harmonization between States • Development of concept for approach
RNP SOR SGApproach • Promulgation of operations without containment integrity not envisaged • Default RNP (0.3NM) • Basic GNSS • SBAS • Scaleable RNP (0.3 – 0.1NM)
FixA FAF MAPt Scaleable Default RNP SOR SGApproach Plan view
FAF Scaleable Default-APV Default-NPA MAPt RNP SOR SGApproach Profile view
RNPSOR SGConcept Nav specifications w/o containment to be completed end of 2005 Nav specifications RNP 0.3 – 0.1 completed end of 2006 Other Nav specifications will be developed once there is an operational requirement
RNP SOR SGPerformance based Navigation Manual • Common understanding of the performance based navigation concept and the relationship between RNP and RNAV functionality • Harmonization between States • Development of concept for approach • PBN Manual that provides a “one stop shop” for States how to implement RNAV and RNP in their airspace
Performance based Navigation Manual • Part A: The Performance Based Navigation Concept • Chapter 1 – General (Context of Performance Based Navigation) • Chapter 2 – Description of Performance Based Navigation • Chapter 3 – Concepts of Operation • Chapter 4 – Implications of Performance Based Navigation • Part B: Implementation Guidance • Chapter 1 – Implementation Processes • Chapter 2 – Identifying Navigation Requirements • Chapter 3 – Using an Existing Navigation Spec to Satisfy and Airspace Concept • Chapter 4 – Development of New Nav Spec to Satisfy and Airspace Concept • Chapter 5 – Implementation Preparation • Chapter 6 – Post Implementation • Part C: Compendium of Navigation Specifications • Chapter 1 – Overview of Compendium • Chapter 2 – RNAV Navigation Specifications • Chapter 3 – RNP Navigation Specifications • Chapter 4 - Matrix
RNP SOR SGStandards and procedures • Common understanding of the performance based navigation concept and the relationship between RNP and RNAV functionality • Harmonization between States • Development of concept for approach • RNP Manual that provides a “one stop shop” for States how to implement RNAV and RNP in their airspace • Provision of detailed standards and procedures
RNP SOR SGICAO provisions • High level Standards • State consultation August 2006 • Applicable November 2007 • PBN manual • Available July 2006 • Obstacle Clearance Criteria (PANS-OPS) • State consultation August 2006 • Applicable November 2007 • Separation Criteria (PANS-ATM) • State consultation August 2006 • Applicable November 2007