UNLIMITED FREE ACCESS TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

- Trained on our vast library of engineering resources.

ICAO - 9613

Performance-based Navigation (PBN) Manual

active, Most Current
Organization: ICAO
Publication Date: 1 January 2023
Status: active
Page Count: 398
scope:

FOREWORD

History of this manual

The Special Committee on Future Air Navigation Systems (FANS) identified that the method most commonly used over the years to indicate required navigation capability was to prescribe mandatory carriage of certain equipment. This constrained the optimum application of modern on-board equipment. To overcome this problem, the committee developed the concept of required navigation performance capability (RNPC). FANS defined RNPC as a 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.

The RNPC concept was approved by the ICAO Council and was assigned to the Review of the General Concept of Separation Panel (RGCSP) for further elaboration. In 1990, the RGCSP, noting that capability and performance were distinctly different, and that airspace planning is dependent on measured performance, rather than designed-in capability, changed RNPC to required navigation performance (RNP).

The RGCSP then developed the concept of RNP further by expanding it to be a statement of the navigation performance necessary for operation within a defined airspace. It was proposed that a specified type of RNP should define the navigation performance of all users within the airspace to be commensurate with the navigation capability available within the airspace. RNP types were to be identified by a single RNP value as envisaged by FANS. While this was found to be appropriate for application in remote and oceanic areas, the associated guidance for route separation was not sufficient for continental RNAV applications; this was due to a number of factors, including the setting of performance and functional standards for aircraft navigation systems, working within the constraints of available airspace, and using a more robust communications, ATS surveillance and ATM environment.

Due to the gradual development of area navigation capability, together with the need to derive early benefits from the installed equipment, different specifications of navigation capability were developed with common navigation accuracy. A divergence of implementation resulted in a lack of harmonization between RNP applications, which needed to be addressed with a globally harmonized concept.

On 3 June 2003, the ICAO Air Navigation Commission, when taking action on recommendations of the fourth meeting of the Global Navigation Satellite System Panel (GNSSP), designated the Required Navigation Performance and Special Operational Requirements Study Group (RNPSORSG) to act as the focal point for addressing several issues related to required navigation performance (RNP).

The RNPSORSG reviewed the ICAO RNP concept, taking into account the experiences of early application as well as current industry trends, stakeholder requirements and existing regional implementations. It agreed on the relationship between RNP and RNAV system functionality and applications and developed the PBN concept, which allows global harmonization of existing implementations and creates a basis for harmonizing future operations.

The PBN concept described in Volume I should be viewed as more than just a remodelling or an extension of the RNP concept (see Chapter 1, 1.1.1). This volume should not be read in isolation as it is both an integral part of, and complementary to, Volume II - Implementing RNAV and RNP operations.

A regular review of the material would be necessary to accommodate future changes. The 5th edition has been updated to reflect new requirements, such as the use of RF legs and the introduction of RNP AR departures, as well as to provide additional or revised guidance on a range of subjects. Specific changes include:

a) clarification of the distinction between RNAV and RNP and related functionality; systematic use of the term RNP value, although it is understood that some industry standards continue using RNP with this specific meaning;

b) clarification and guidance on PBN versatility through its ability to enable multiple navigation applications for different airspace concepts from a navigation specification;

c) changes to the advanced RNP navigation (A-RNP) specification, including:

1) final approach segment no longer considered a part of A-RNP; and

2) scalability requirements replaced by use of RNP value of 0.3 NM outside of the final approach segment;

d) additional guidance on the implementation of A-RNP;

e) the RNP AR APCH specification is complemented by the RNP AR departure procedures (DP) with consequential changes relating to criteria for the development of AR DP procedures (Required Navigation Performance Authorization Required (RNP AR) Procedure Design Manual (Doc 9905)), charting requirements for RNP AR departures (Aeronautical Chart Manual (Doc 8697)), the process for authorization of new AR DP specifications (Performance-based Navigation (PBN) Operational Authorization Manual (Doc 99971)), and route spacing standards for AR Departures (Procedures for Air Navigation Services - Air Traffic Management (PANS-ATM, Doc 4444));

f) updates and additions to aircraft systems and equipment performance, functionality and capability (including speed transitions, MagVar, parallel offsets, etc) reflecting RTCA or EUROCAE documents are included in the navigation specification descriptions and attachments as appropriate;

g) refinement regarding use of the radius to fix leg, with consequential changes to Doc 9997, the Procedures for Air Navigation Services - Aircraft Operations (PANS-OPS, Doc 8168) with revised criteria for procedure design using RF legs, and PANS-ATM with route spacing standards for aircraft using RF leg;

1) this includes catering to the needs of General Aviation aircraft operations on PBN routes and procedures, resulting in amendments to certain navigation specifications and augmented text in various other parts of the manual;

h) additional positioning sources such as GBAS and dual frequency multiple constellation technologies are accounted for in RNP navigation specifications, which require use of a core global navigation satellite system (GNSS) constellation, supplemented by an augmentation system, as appropriate;

i) consideration and awareness on the development of GNSS reversion capability;

j) removal of references to the minimum navigation performance Standards (MNPS), which are no longer used;

k) review of applicable path terminators for navigation specifications and guidance on combinations of such path terminators in procedure design;

l) additional guidance on temperature correction;

m) RNP 0.3 navigation specification, now explicitly defined as helicopter-only

o) replacement of guidance and functional specifications for barometric VNAV across multiple flight phases with guidance and information for vertical navigation on the final approach segment;

p) guidance on ATC status monitoring for GNSS; and

q) clarification on the definition and the use of holding capabilities.

1. Formerly the Performance-based Navigation Operational Approval Manual, renamed in its third (forthcoming) edition.

Document History

9613
January 1, 2023
Performance-based Navigation (PBN) Manual
FOREWORD History of this manual The Special Committee on Future Air Navigation Systems (FANS) identified that the method most commonly used over the years to indicate required navigation capability...
January 1, 2013
Performance-based Navigation (PBN) Manual
Purpose and scope This manual identifies the relationship between RNAV and RNP applications and the advantages and limitations of choosing one or the other as the navigation requirement for an...
January 1, 2013
Performance-based Navigation (PBN) Manual
Purpose and scope This manual identifies the relationship between RNAV and RNP applications and the advantages and limitations of choosing one or the other as the navigation requirement for an...
January 1, 2008
Performance-based Navigation (PBN) Manual
This manual identifies the relationship between RNAV and RNP applications and the advantages and limitations of choosing one or the other as the navigation requirement for an airspace concept It also...
October 1, 1999
Manual on Required Navigation Performance (RNP)
A description is not available for this item.
January 1, 1999
Manual on Required Navigation Performance (RNP)
A description is not available for this item.
January 1, 1999
Manual on Required Navigation Performance (RNP)
A description is not available for this item.
January 1, 1999
Manual on Required Navigation Performance (RNP)
A description is not available for this item.
January 1, 1994
Manual on Required Navigation Performance (RNP)
A description is not available for this item.

References

Advertisement