RNP (Required Navigation Performance)

RNP was developed by ICAO in the 1990s and codified through successive editions of Doc 9613 as part of the Performance-Based Navigation (PBN) concept, which moved global airspace navigation requirements away from sensor-specific mandates ("use VOR", "use ILS") toward performance-specific requirements ("navigate to within X nautical miles of intended track 95 percent of the time, with onboard alerting if performance degrades"). The PBN framework defines two main specification families: RNAV specifications, which require lateral accuracy but not onboard performance monitoring and alerting (RNAV 10, RNAV 5, RNAV 2, RNAV 1); and RNP specifications, which require both accuracy and onboard performance monitoring and alerting (RNP 4, RNP 2, RNP 1, RNP APCH, RNP AR APCH). The number in the specification name indicates the required lateral accuracy in nautical miles — RNP 4 requires the aircraft to remain within ±4 nautical miles of the intended track 95 percent of the time, with onboard monitoring that alerts the crew when this accuracy is not assured.

The defining technical distinction between RNAV and RNP is the onboard performance monitoring and alerting capability. An RNAV-capable aircraft computes its position using the available sensor inputs (GNSS, DME/DME, VOR/DME, INS) and follows the FMS-computed track, but it does not continuously assess whether the position computation accuracy meets the airspace requirement, nor does it alert the crew when it does not. An RNP-capable aircraft adds the Actual Navigation Performance (ANP) versus Required Navigation Performance (RNP) comparison: the system continuously estimates its current lateral accuracy and compares it to the required value, displaying an alert if ANP exceeds RNP. This onboard integrity provision allows RNP-capable aircraft to operate in airspace where lateral separation standards are tighter and where loss of navigation accuracy must be communicated to the crew without depending on ATC surveillance.

The key operational RNP specifications include RNP 10 (oceanic and remote continental, 10 nautical mile accuracy), RNP 4 (improved oceanic separation, 4 nautical mile accuracy), RNP 2 (en-route continental and improved oceanic), RNP 1 (terminal and arrival), RNP APCH (approach without authorisation required, supporting LNAV, LNAV/VNAV, and LPV minima), and RNP AR APCH (approach with authorisation required, the highest-precision PBN approach specification permitting curved final approach paths, lateral accuracies below 0.3 nautical miles, and operations into terrain-challenged airports). RNP AR APCH approvals are aircraft-and-operator specific, require specific aircraft equipment beyond the baseline RNP capability, and require operator demonstration of training, procedures, and operational compliance — the AR ("Authorisation Required") designation signals this elevated approval threshold.

The regulatory framework for RNP approvals differs by jurisdiction in implementation detail while remaining aligned on the underlying PBN concepts. The FAA addresses RNP operational approval through AC 90-100A (US Terminal and En Route Area Navigation), AC 90-101A (Approval Guidance for RNP Procedures with AR), AC 90-105A (Approval Guidance for RNP Operations and Barometric Vertical Navigation), with operator approval issued through OpsSpecs. EASA addresses RNP under AMC and GM material to Part-NCO, Part-NCC, Part-CAT, and Part-SPA Subpart C (PBN Approval), with operator approval issued through Operations Manual approval. ICAO Doc 9613 Volume II provides the underlying performance-based airspace concept that national authorities implement.

For a flight school operating in modern PBN airspace, RNP capability and training are increasingly central to instrument flight syllabi. Initial Instrument Rating training under FAA Part 61 and Part 141 includes RNAV (GPS) approach training as a standard syllabus item, and many training operators integrate RNP APCH content into the IFR module covering LNAV, LNAV/VNAV, and LPV minima — the three minima types served by RNP APCH procedures depending on the aircraft equipment. The transition from training-aircraft RNP capability (typically RNP APCH only, sometimes with WAAS-augmented LPV) to airline-aircraft RNP capability (RNP 1, RNP APCH, often RNP AR APCH on contemporary types) is a significant content jump in type rating training.

For an ATO running advanced PBN content, the GNSS receiver landscape and FMS implementation differences across aircraft types create syllabus complexity. The basic Garmin GTN/GNS WAAS receivers in training aircraft, the Honeywell and Collins FMS implementations in airline aircraft, and the various retrofitted FMS systems in operators' fleets each implement RNP capability with subtly different crew procedures and capability boundaries. Training records must capture the aircraft-specific RNP capability profile against which the pilot was trained, supporting the operational currency tracking that RNP-capable operations require.

Aviatize's training management module supports RNP-specific syllabus items as competency-based training elements with aircraft-equipment-specific content. A lesson plan covering RNP APCH on a Garmin GTN-equipped training aircraft can be configured distinctly from the equivalent lesson on an airline-fleet FMS-equipped aircraft, with the post-lesson competency assessment captured against the ICAO core competencies and the specific equipment profile.

The ground training and checking module integrates the underlying PBN theoretical knowledge — Performance-Based Navigation concepts under ICAO Doc 9613, ANP versus RNP comparison, RNAV versus RNP distinction, LNAV/VNAV/LPV minima types — into the IFR and CPL/IR theoretical syllabi, with knowledge checks aligned to the FAA Knowledge Test ACS and EASA theoretical examination matrix. The KPI reporting module surfaces cohort progression on RNP and PBN content, supporting the school's quality monitoring of an increasingly complex IFR training area.