10.2 RNAV, RNP & Performance-Based Navigation (PBN)

10.2 RNAV, RNP & Performance-Based Navigation (PBN)

Aviation navigation has evolved from flying along point-to-point radials between ground-based navaids to flying flexible, optimized trajectories enabled by airborne computers and satellite constellations. This paradigm is standardized globally by the International Civil Aviation Organization (ICAO Doc 9613) and the FAA as Performance-Based Navigation (PBN). For the 14 CFR Part 121 aircraft dispatcher, PBN governs route construction, fuel burn optimization, terminal arrival slot coordination, and minimum navigation equipment dispatch legality under FAA Operations Specifications (OpSpecs).

---

The Performance-Based Navigation (PBN) Framework

Under legacy navigation, routes were defined by physical ground beacons (e.g., fly Victor 3 from VOR A to VOR B). PBN decouples navigation paths from specific ground sensors, defining flight operations in terms of required accuracy, integrity, continuity, and availability.

The Three Pillars of PBN

1. Navigation Application: The operational domain in which the flight takes place (e.g., Oceanic/Remote, Continental En Route, Terminal Arrival/Departure, or Approach).
2. Navigation Specification: The formal standard prescribing airborne equipment requirements, flight crew training, and performance metrics, designated as either RNAV 'X' or RNP 'X' (where X denotes lateral accuracy in nautical miles).
3. Navigation Infrastructure: The underlying sensor network supporting positioning, including Global Navigation Satellite Systems (GNSS), Distance Measuring Equipment networks (DME/DME), and Inertial Reference Units (IRU).

---

RNAV vs. RNP: The Core Distinction

A fundamental question on the FAA ADX exam concerns the technical and legal difference between Area Navigation (RNAV) and Required Navigation Performance (RNP).

Definitions & Performance Monitoring

• Area Navigation (RNAV): A method of navigation that permits aircraft operation on any desired flight path within the coverage of ground- or space-based navigation aids, or within the limits of self-contained airborne systems, or a combination of these. Crucial Rule: RNAV specifications do not require on-board performance monitoring and alerting.
• Required Navigation Performance (RNP): An advanced form of RNAV that mandates On-Board Performance Monitoring and Alerting (OBPMA).

On-Board Performance Monitoring & Alerting (OBPMA)

OBPMA provides real-time integrity confidence to the flight crew. The Flight Management System (FMS) continuously computes the Total System Error (TSE), which is the vector sum of three independent error components:

$\text{Total System Error (TSE)} = \sqrt{(\text{Path Definition Error})^2 + (\text{Flight Technical Error})^2 + (\text{Navigation System Error})^2}$

• Path Definition Error (PDE): Geometric error in the digital navigation database.
• Flight Technical Error (FTE): Accuracy with which the pilot or autopilot tracks the commanded flight path.
• Navigation System Error (NSE): Difference between the true aircraft position and the position estimated by the navigation sensors.

The Containment Standard

For an RNP system designated as RNP X:

1. Accuracy Standard: The Total System Error must remain within ±X nautical miles for at least 95% of the total flight time.
2. Containment & Alerting Standard: If equipment failures, satellite geometry degradation, or tracking errors cause the navigation error to exceed the containment boundary of 2 × X nautical miles, the system must illuminate an alert message in the primary field of view of both pilots with a containment integrity probability of 99.999% ($10^{-5}$). RNAV systems have no such automated alerting mandate.

---

Global Navigation Satellite System (GNSS / GPS) Architecture

The U.S. Global Positioning System (GPS), operated by the United States Space Force, is the primary satellite constellation supporting PBN.

Constellation Architecture (Space Segment)

• Baseline Constellation: Consists of a minimum of 24 operational satellites disposed across 6 orbital planes, inclined at 55° relative to the equator.
• Orbit Dimensions: Satellites orbit at a semi-synchronous altitude of approximately 10,898 nautical miles (20,200 km) above the Earth with an orbital period of 11 hours and 58 minutes (12 sidereal hours).
• Geometry: This constellation configuration guarantees that at least 4 to 8 satellites are in direct line-of-sight from any point on Earth at any time.

Satellite Ranging and Satellite Counts

Airborne GPS receivers calculate pseudo-ranges to visible satellites by measuring the transit time of synchronized pseudo-random noise (PRN) radio codes transmitted on the L1 (1575.42 MHz) and L2/L5 frequencies:

1. 3 Satellites: Yields a two-dimensional horizontal position (latitude and longitude) only if altitude is fixed or independently known.
2. 4 Satellites: Solves four mathematical unknowns: Latitude (X), Longitude (Y), Altitude (Z), and Receiver Clock Bias Error (T). Four satellites are the absolute minimum required for a valid three-dimensional IFR position fix.
3. 5 Satellites (or 4 Satellites + Barometric Altimeter Aiding): Provides Receiver Autonomous Integrity Monitoring (RAIM) Fault Detection (FD). The receiver cross-checks independent pseudo-range solutions to detect if one satellite is providing corrupted or erroneous data, issuing an integrity warning to the crew.
4. 6 Satellites (or 5 Satellites + Baro-Aiding): Provides RAIM Fault Detection and Exclusion (FDE). The receiver detects the anomalous satellite, mathematically isolates and excludes it from the navigation solution, and continues uninterrupted IFR navigation without crew intervention.

---

Satellite-Based & Ground-Based Augmentation (SBAS & GBAS)

Wide Area Augmentation System (WAAS / SBAS)

• Architecture: A network of approximately 38 ground reference stations across North America monitors GPS satellite signals and relays timing and atmospheric error data to master stations. Master stations compute differential corrections and uplinks them to geostationary communication satellites, which broadcast correction signals across North America on the GPS L1 frequency.
• Performance Benefits:
  • Provides sub-meter lateral and vertical positioning accuracy.
  • Eliminates ionospheric propagation delay errors.
  • Generates Localizer Performance with Vertical Guidance (LPV) approaches, providing precision-like vertical guidance down to decision altitudes as low as 200 feet HAT and 1/2 SM visibility (equivalent to ILS Category I).
  • Dispatch Impact: WAAS-equipped aircraft are exempt from mandatory preflight RAIM prediction checks along domestic routes.

Ground-Based Augmentation System (GBAS / LAAS)

• Architecture: Installed directly at major airport hubs, consisting of four ground reference GPS receivers, a central processing facility, and a Very High Frequency Data Broadcast (VDB) transmitter (108.025 to 117.950 MHz).
• Performance Benefits: Provides localized differential corrections with extreme accuracy (<1 meter), supporting Category I, II, and III precision approaches without requiring traditional ILS sensitive/critical area surface restrictions, while enabling curved, segmented approach transitions.

---

PBN Navigation Specifications Matrix

---

Published RNAV Airway Systems

1. Q-Routes (High-Altitude RNAV Airways):
   • Extend from 18,000 feet MSL (FL 180) up to and including Flight Level 450 (FL 450) across the contiguous United States and Alaska.
   • Require RNAV 2 or RNP 2 navigation equipage.
   • Depicted on IFR En Route High Altitude charts; optimized to provide direct, fuel-efficient routings bypassing congested VOR facilities.
2. T-Routes (Low-Altitude RNAV Airways):
   • Extend from 1,200 feet AGL up to but not including 18,000 feet MSL.
   • Require RNAV 2 navigation equipage.
   • Depicted on IFR En Route Low Altitude charts (in blue or cyan); provide transition corridors through congested Class B and Class C terminal airspace and over mountainous terrain where ground VOR signals are obstructed.
3. TK-Routes & Y-Routes:
   • TK-Routes: Low-altitude RNAV routes established in Alaska.
   • Y-Routes: RNAV routes established over the Gulf of Mexico and offshore coastal sectors.

---

RAIM Availability Checks & Part 121 Dispatch Requirements

Under 14 CFR § 121.533 and FAA Advisory Circular AC 90-100A, the aircraft dispatcher shares joint responsibility with the pilot-in-command for verifying navigation equipage and route legality prior to signing the dispatch release.

OpSpec B034 & B035 Operational Mandates

When dispatching an aircraft on an RNAV or RNP route where navigation depends on GPS (without WAAS):

• Mandatory Preflight RAIM Prediction: The dispatcher must execute a certified preflight RAIM prediction check for the planned route, destination, and alternate airports covering the estimated time of arrival (ETA) ±1 hour.
• The 5-Minute Outage Rule: If the RAIM prediction software indicates a continuous predicted loss of satellite fault detection (RAIM outage) exceeding 5 minutes along any portion of the planned route, the flight cannot be dispatched as filed on that RNAV/RNP route.
• Dispatcher Corrective Actions:
  1. Delay departure until satellite geometry improves.
  2. Amend the flight release to file along conventional ground-based airways (Victor or Jet routes) using terrestrial VOR/DME facilities.
  3. Verify that the aircraft possesses an approved multi-sensor FMS with DME/DME/IRU position-updating capability that meets navigation performance requirements without GPS input (in accordance with OpSpec B034).
• Dispatch Release Notation: The dispatcher must ensure that the flight plan filed with ATC contains the appropriate ICAO PBN designators in Field 10a (e.g., R for PBN approval) and Field 18 (e.g., PBN/A1B1C1D1L1O1S1).