6.2 Performance-Based Navigation (PBN) & RNP/RNAV
Key Takeaways
- Performance-Based Navigation (PBN), governed by FAA AC 90-105A and ICAO Doc 9613, transitions airspace from sensor-specific ground navigation to aircraft performance-defined containment accuracy.
- The fundamental regulatory and technical distinction between RNAV and RNP is On-Board Performance Monitoring and Alerting (OBPMA), which is mandatory for all RNP specifications.
- Total System Error (TSE = sqrt(PDE^2 + FTE^2 + NSE^2)) must remain within +/-1 x RNP for at least 95% of total flight time, and within +/-2 x RNP outer containment with 99.999% integrity.
- RNP AR (Authorization Required) procedures permit approach minima down to RNP 0.10 and curved Radius-to-Fix (RF) legs, requiring dual FMCs, dual GNSS, dual autopilots/flight directors, TAWS Class A, and OpSpecs approval.
- RAIM requires 5 satellites for Fault Detection (FD) and 6 satellites (or 5 with baro-aiding) for Fault Detection and Exclusion (FDE); Baro-VNAV approaches mandate cold-temperature altimetry corrections below published chart temperature limits.
Performance-Based Navigation (PBN) & RNP/RNAV
Core Airline Transport Principle: Performance-Based Navigation (PBN) establishes aircraft lateral and vertical accuracy capabilities independent of specific ground-based navigation aids. For the airline transport pilot, understanding the operational boundaries of Required Navigation Performance (RNP), On-Board Performance Monitoring and Alerting (OBPMA), curved Radius-to-Fix (RF) legs, and GNSS RAIM integrity is vital for flying precision terminal procedures in high-density and terrain-critical airspace.
1. The PBN Framework & Regulatory Foundation
Under FAA Advisory Circular AC 90-105A and ICAO Document 9613, the aviation system transitioned from conventional sensor-specific routing (VOR radial and NDB bearing navigation) to Performance-Based Navigation (PBN).
+-----------------------------------------------------------------------------+
| PBN FRAMEWORK ARCHITECTURE |
| |
| [PBN FRAMEWORK] |
| | |
| +------------------+------------------+ |
| v v |
| [RNAV SPECIFICATIONS] [RNP SPECIFICATIONS] |
| (No OBPMA Required) (Mandatory OBPMA Alerting) |
| - RNAV 10 (Oceanic) - RNP 4 / RNP 2 (Oceanic/Enrt) |
| - RNAV 2 (Enroute) - RNP 1 (SIDs / STARs) |
| - RNAV 1 (SIDs / STARs) - RNP 0.30 (RNP APCH Final) |
| - RNP AR (0.30 down to 0.10) |
+-----------------------------------------------------------------------------+
Core Philosophy of PBN
PBN defines aircraft system performance requirements along a flight path rather than mandating specific onboard hardware or specific ground beacons. A PBN navigation specification encompasses:
- Accuracy: Lateral and along-track containment limits.
- Integrity: The ability of the system to provide timely warnings when navigation signals become untrustworthy.
- Continuity: The probability that the system performs without unscheduled interruption during an intended operation.
- Availability: The percentage of time navigation signals meet required accuracy, integrity, and continuity criteria.
2. RNAV vs. RNP: The OBPMA Distinction & Error Budgeting
Many pilots mistakenly treat RNAV (Area Navigation) and RNP (Required Navigation Performance) as interchangeable terms. The regulatory and engineering distinction is definitive:
[!IMPORTANT] The Critical Defining Difference: RNP requires On-Board Performance Monitoring and Alerting (OBPMA); RNAV does not.
OBPMA continuously monitors the estimated position error (Actual Navigation Performance - ANP / Estimated Position Uncertainty - EPU) against the required accuracy (RNP). If the system detects that ANP exceeds RNP, it immediately triggers visual and aural flight deck alerts (UNABLE RNPorNAV ACCUR DOWNGRAD).
+-----------------------------------------------------------------------------+
| RNP CONTAINMENT & TOTAL SYSTEM ERROR |
| |
| <------------------------- 2 x RNP (99.999% Containment) ------------------>|
| <------------ 1 x RNP (95% Accuracy) ------------> |
| -------------|-------------|--------+--------|----------------|------------|
| Obstacle Outer Alert Inner Intended Inner Outer |
| Clearance Containment Boundary Course Boundary Containment |
| Limit Boundary (-1 RNP) (CL) (+1 RNP) Boundary |
+-----------------------------------------------------------------------------+
Total System Error (TSE) Decomposition
Total System Error represents the total difference between the true aircraft position and the intended defined path. It consists of three statistically independent root-sum-square error components:
- Path Definition Error (PDE): The difference between the defined path in the navigation database and the desired path. Modern digital databases have near-zero PDE ($PDE \approx 0$).
- Flight Technical Error (FTE): The accuracy with which the pilot or autopilot tracks the displayed guidance (cross-track steering error).
- Navigation System Error (NSE): The error in the aircraft's estimated position relative to true position, driven by sensor inaccuracies (GPS satellite clock drift, atmospheric delay, DME multipath).
95% Accuracy vs. 99.999% ($2 \times \text{RNP}$) Containment
- Inner Accuracy Requirement (95% of Flight Time): The aircraft Total System Error must remain within $\pm 1 \times \text{RNP}$ of the centerline for at least 95% of the total flight time.
- Outer Containment Boundary (99.999% / $10^{-5}$ Integrity): The aircraft must remain within $\pm 2 \times \text{RNP}$ of centerline. If the estimated position exceeds $2 \times \text{RNP}$, the OBPMA system must alert the flight crew within seconds so an immediate missed approach or diversion can be executed.
3. PBN Navigation Specifications Matrix
+-----------------------------------------------------------------------------+
| PBN NAVIGATION SPECIFICATIONS & APPLICATIONS |
| |
| Specification Lateral Accuracy Primary Flight Phase / Airspace |
| ----------------------------------------------------------------------- |
| RNAV 10 (RNP 10) +/- 10.0 NM Oceanic & Remote (50 NM separation) |
| RNP 4 +/- 4.0 NM Oceanic & Remote (30 NM separation) |
| RNAV 2 +/- 2.0 NM Enroute Continental (Q/T Routes) |
| RNAV 1 +/- 1.0 NM Terminal: SIDs, STARs |
| RNP 1 +/- 1.0 NM Terminal: Mountainous SIDs / STARs |
| RNP 0.30 +/- 0.30 NM Approach: RNP APCH Final Approach |
| RNP AR APCH +/- 0.30 to 0.10 NM Special Authorization Final / Missed |
+-----------------------------------------------------------------------------+
- RNAV 10 (RNP 10): Used in oceanic and remote airspace (e.g., Pacific and North Atlantic routes). Requires dual independent Long-Range Navigation Systems (dual INS/IRU or GNSS). Despite the historical 'RNP 10' moniker, it is officially an RNAV specification because it lacks modern OBPMA.
- RNAV 1 / RNAV 2: The standard for domestic enroute high-altitude Q-routes, low-altitude T-routes, and standard radar-monitored SIDs/STARs.
- RNP 1: Used for complex terminal arrival and departure routing in terrain-challenged environments without requiring direct radar monitoring.
- RNP APCH (RNP 0.3): The standard non-AR approach specification flown to LNAV, LNAV/VNAV, or LPV (Localizer Performance with Vertical Guidance) minima.
4. RNP AR (Authorization Required) & Curved RF Legs
RNP AR (Authorization Required) represents the pinnacle of commercial PBN capability, governed by FAA AC 90-101A and airline Operations Specification (OpSpec) C384.
+-----------------------------------------------------------------------------+
| RNP AR CURVED RADIUS-TO-FIX (RF) LEG |
| |
| Turn Center |
| (o) |
| : |
| : Radius (R) |
| : |
| Fix A (Tangent) v Fix B (Tangent) |
| +=====================( Curved Arc )====================+ |
| Inbound Leg Outbound Leg |
| |
| * Constant radius arc around a precisely defined geographical center point|
| * Bank angle limited to 25 deg (or 30 deg above 400 ft AGL) |
| * Allows precision terrain avoidance in narrow mountain valleys |
+-----------------------------------------------------------------------------+
Key Technical Hallmarks of RNP AR
- Very Low RNP Values: Permits approach minima with lateral containment down to RNP 0.10 (and down to 0.05 under special approval), slashing obstacle evaluation areas to a fraction of conventional approaches.
- Radius-to-Fix (RF) Curved Legs: Enables curved approaches around mountains, terrain obstacles, and prohibited airspace directly onto short final runways.
- Missed Approach RNP $< 1.0$: Standard approaches revert to RNP 1.0 on a go-around; RNP AR procedures can require RNP 0.10 during the missed approach, requiring precision autopilot guidance and high climb gradients during engine-out go-arounds.
- Mandatory Equipment Redundancy:
- Dual independent FMCs and dual multi-sensor GNSS receivers.
- Dual Autopilot / Flight Director systems with automatic roll steering.
- TAWS Class A with high-resolution terrain database displaying active RNP path overlays.
- Operating cross-track error (FTE) display on primary flight displays (PFDs).
5. GNSS Integrity (RAIM/FDE) & Baro-VNAV Operations
Receiver Autonomous Integrity Monitoring (RAIM) & FDE
Because standard GPS satellite broadcasts do not provide instantaneous warning if a satellite clock drifts or ephemeris data corrupts, transport GNSS receivers use internal algorithms to verify satellite geometry and integrity:
+-----------------------------------------------------------------------------+
| RAIM VS. FDE SATELLITE CONSTELLATION NEEDS |
| |
| Algorithm Minimum Satellites Cockpit Action |
| ----------------------------------------------------------------------- |
| Basic Navigation 4 Satellites Computes 3D Fix (X,Y,Z,t)|
| Fault Detection (FD) 5 Satellites Alerts pilot of bad sat |
| (or 4 + Baro-Aiding) Abort RNP approach |
| Fault Detection & 6 Satellites Isolates corrupt sat, |
| Exclusion (FDE) (or 5 + Baro-Aiding) continues navigation |
+-----------------------------------------------------------------------------+
- Pre-Flight Predictive RAIM Check: Airlines are required to verify RAIM/FDE availability along the intended route and for the estimated time of arrival (ETA $\pm 15$ minutes) at the destination and alternate airports prior to dispatch.
Barometric Vertical Navigation (Baro-VNAV) & Temperature Errors
Baro-VNAV computes vertical guidance based on barometric pressure altitude. Unlike satellite-based vertical guidance (SBAS/WAAS), Baro-VNAV is subject to temperature-induced altimetry errors:
+-----------------------------------------------------------------------------+
| COLD TEMPERATURE BARO-VNAV GLIDEPATH HAZARD |
| |
| Warmer than ISA: True Flight Path is HIGHER than Indicated Path |
| Standard ISA: True Flight Path MATCHES Indicated 3.00 deg Path |
| Colder than ISA: True Flight Path is DANGEROUSLY LOWER than Indicated! |
| |
| Indicated 3.00 deg Path |
| - - - - - - - - - - - - - - > Altimeter reads OK |
| . |
| True Path (Cold) . ' (Flatter Angle, e.g. 2.5 deg) |
| ==================/ |
| /////////////////\ (Terrain Obstacles Penetrated!) |
+-----------------------------------------------------------------------------+
[!CAUTION] Cold-Temperature Altimetry Corrections: In uncompensated aircraft, flying a Baro-VNAV approach below the published Cold Temperature Limit on the approach chart (e.g., $-15^\circ\text{C}$) is strictly prohibited. Extremely cold air causes the true vertical path angle to shallow, flying the aircraft significantly closer to underlying obstacles. Modern advanced FMCs feature automatic Temperature Compensation that corrects waypoint constraint altitudes when enabled by the crew.
What is the primary technical and regulatory difference between an Area Navigation (RNAV) specification and a Required Navigation Performance (RNP) specification?
How many GPS satellites in view with adequate geometry are required for Receiver Autonomous Integrity Monitoring (RAIM) to perform Fault Detection (FD) versus Fault Detection and Exclusion (FDE)?
When flying an uncompensated Baro-VNAV approach into an airport with an ambient surface temperature of -30°C (well below standard ISA), what effect does the cold temperature have on the aircraft's true vertical flight path?