RNP vs. RNAV: Performance-Based Navigation Guide
Short answer: Under FAA Aeronautical Information Manual (AIM 1-2-1 and 1-2-2), both RNAV and RNP require maintaining a specified lateral accuracy for at least 95 percent of flight time. The core difference is that RNP requires onboard performance monitoring and alerting (OBPMA), which actively alerts the flightcrew if navigation requirements are not met. On US approach plates, standard RNP APCH procedures are charted as RNAV (GPS), while RNP Authorization Required procedures are titled RNAV (RNP).
The Core Distinction Under the PBN Framework
When an airline interview panel asks you to explain the difference between RNAV and RNP, start with the umbrella concept. Performance-Based Navigation (PBN) shifts navigation requirements from specific ground-based sensors to defined performance standards. Under AIM 1-2-1, PBN exists under the umbrella of area navigation and is divided into two main categories of navigation specifications (NavSpecs): RNAV specifications and RNP specifications.
Both categories use a numerical designation that states the required lateral navigation accuracy in nautical miles. The aircraft must achieve that lateral accuracy at least 95 percent of the flight time.
The single dividing line between the two is onboard performance monitoring and alerting (OBPMA). An RNP specification is an RNAV system that includes OBPMA capability, such as Receiver Autonomous Integrity Monitoring (RAIM). Because the aircraft monitors its own integrity and alerts the flightcrew when accuracy degrades, RNP allows reduced reliance on air traffic control radar intervention and procedural separation.
US Standard RNAV and RNP Navigation Specifications (FAA AIM 1-2-1, AIM 1-2-2, and AC 90-105A)
| NavSpec | Typical Application | 95% Lateral Accuracy (NM) | OBPMA Required? |
|---|---|---|---|
| RNAV 10 / RNP 10 | Oceanic and remote operations (supports 50 NM lateral and longitudinal separation) | 10.0 | No (grandfathered RNAV application) |
| RNP 4 | Oceanic and remote areas with performance-based horizontal separation | 4.0 | Yes |
| RNAV 2 | En route operations (such as Q-routes and T-routes) | n/a | No |
| RNP 2 | Domestic, offshore, oceanic, and remote en route operations | 2.0 | Yes |
| RNAV 1 | Terminal Departure Procedures (DPs) and Standard Terminal Arrivals (STARs) | n/a | No |
| RNP 1 | Terminal arrivals, departures, and initial/intermediate/missed approach segments | 1.0 | Yes |
| RNP 0.3 | All authorized phases of flight for rotorcraft (not for oceanic, remote, or final approach) | 0.3 | Yes |
| RNP APCH | Standard instrument approaches charted in the US as RNAV (GPS) | 1.0 terminal/missed, scaling to 0.3 on final | Yes |
| RNP AR APCH | Authorization Required approaches charted in the US as RNAV (RNP) | Below 1.0 terminal/missed, scaling to 0.3 to 0.1 on final | Yes |
Why US Chart Titles Confuse Pilots: RNAV (GPS) vs. RNAV (RNP)
One of the most common traps in a technical interview is confusing the International Civil Aviation Organization (ICAO) NavSpec name with the title printed at the top of a US approach plate. In the United States, every standard GPS approach you fly is actually an RNP operation.
Under FAA charting policy and AC 90-105A Appendix A, standard RNP Approach (RNP APCH) procedures are titled RNAV (GPS) on US charts. Even though the chart title says RNAV, the underlying NavSpec is RNP APCH because your GPS or Wide Area Augmentation System (WAAS) receiver provides onboard performance monitoring and alerting via RAIM or a Space-Based Augmentation System (SBAS).
These procedures used to be labeled Special Aircraft and Aircrew Authorization Required (SAAAR). If an interviewer asks whether you have flown an RNP approach, you can clarify that any pilot who has flown a standard RNAV (GPS) approach has flown the RNP APCH specification, whereas procedures charted as RNAV (RNP) are RNP AR approaches that require specific FAA operational approval.
Onboard Performance Monitoring, Alerting, and Total System Error
To give a complete interview answer on how RNP works, you need to explain what the avionics are actually measuring. Total System Error (TSE) is the difference between the aircraft's true position and its desired position. TSE is the vector sum of three error components.
- Path Definition Error (PDE): The difference between the defined path in the database and the desired path at a specific point. Due to database integrity processes and crew verification procedures, PDE is considered negligible and assumed to be zero.
- Flight Technical Error (FTE): Also called Path Steering Error (PSE), this is the accuracy with which the aircraft is controlled as measured by the indicated aircraft position relative to the indicated command or desired position. It includes display error but does not include pilot blunder errors.
- Navigation System Error (NSE): Also called Position Estimation Error (PEE), this is the difference between the aircraft's true position and its estimated position.
Cockpit Monitoring and Error Containment
Compliance with the OBPMA requirement does not mean the aircraft has an automated monitor for Flight Technical Error. Instead, the onboard monitoring and alerting system combines an automated algorithm that monitors Navigation System Error (NSE) with a lateral deviation display in the pilot's primary field of view so the crew can monitor FTE.
In the cockpit, airborne systems express current estimated navigation performance as Estimate of Position Uncertainty (EPU), Actual Navigation Performance (ANP), or Estimate of Position Error (EPE). As long as your ANP or EPU stays below the active RNP value and you keep your cross-track deviation within limits, containment is assured.
RNP APCH: Standard RNAV (GPS) Procedures and Minima
On a standard US RNAV (GPS) chart built to the RNP APCH specification, lateral accuracy starts at 1.0 NM in the initial and intermediate segments, scales down to 0.3 NM (or 40 meters with SBAS) on the final approach segment, and expands back to 1.0 NM in the missed approach segment. GPS is the primary navigation sensor for RNP APCH. DME/DME-based systems are not acceptable for RNP APCH, though the missed approach segment may use a conventional NAVAID like a VOR, DME, or NDB.
Standard RNP APCH procedures offer four main lines of minima to match aircraft equipage.
- Lateral Navigation (LNAV): A nonprecision approach minimum descent altitude (MDA) supported by GPS with or without SBAS.
- LNAV/Vertical Navigation (LNAV/VNAV): Uses a decision altitude (DA) based on LNAV lateral guidance paired with vertical path guidance from either approved barometric VNAV (baro-VNAV) or SBAS. Pilots flying baro-VNAV must be able to readily distinguish if cross-track deviation exceeds the RNP value or if vertical deviation exceeds 75 feet.
- Localizer Performance (LP): Requires SBAS (such as WAAS) to provide lateral-only precision without vertical guidance.
- Localizer Performance with Vertical Guidance (LPV): Requires SBAS to fly to a decision altitude using both lateral and vertical WAAS guidance.
RF Legs and GLS Procedures Under RNP APCH
Radius to Fix (RF) curved turns are optional in RNP APCH eligibility, meaning you may only fly an RNP APCH procedure containing an RF leg if RF capability is specifically listed in your Aircraft Flight Manual (AFM) or avionics documents.
Ground Based Augmentation System (GBAS) Landing System (GLS) procedures are also constructed using RNP APCH NavSpecs and provide precision approach capability.
RNP AR APCH: Authorization Required Procedures and RF Legs
RNP AR APCH procedures, charted as RNAV (RNP), are designed to navigate around steep terrain, obstacles, or congested airspace where standard obstacle evaluation areas will not fit. RNP AR approaches require special FAA operational authorization (via Operations Specifications, Management Specifications, or a Letter of Authorization) similar to Category II or Category III ILS operations.
Two avionics capabilities that are optional in standard RNP APCH are mandatory in RNP AR APCH: lateral scalability and Radius to Fix (RF) leg capability. An RF leg is a constant-radius circular path around a defined turn center that starts and terminates at a fix. Lateral accuracy on an RNP AR approach can scale below 1.0 NM in the terminal and missed approach segments and down to 0.3 NM or lower (such as RNP 0.15 or RNP 0.10) on the final approach segment. Vertical guidance is provided by baro-VNAV or SBAS.
When an RNP AR approach includes RF legs or requires RNP less than 0.3 on final, or when the missed approach requires RNP less than 1.0, no single point of failure can cause a loss of guidance compliant with the RNP value. Typically, the aircraft must have at least dual GNSS sensors, dual Flight Management Systems (FMS), dual air data systems, dual autopilots, and a single Inertial Reference Unit (IRU). In addition, an operable Class A Terrain Awareness and Warning System (TAWS) is required for all RNP AR procedures.
Under AC 90-101A paragraph 6, an operator receiving initial RNP AR approval is ordinarily granted an interim authorization restricted to minima associated with RNP 0.3 for 90 days and until accumulating 100 RNP AR approaches in each aircraft type.
RNP APCH vs. RNP AR APCH Comparison (FAA AIM 1-2-2, AC 90-105A, and AC 90-101A)
| Feature | RNP APCH | RNP AR APCH |
|---|---|---|
| US Approach Chart Title | RNAV (GPS) | RNAV (RNP) |
| Governing FAA Advisory Circular | AC 90-105A (and AC 90-107 for LP/LPV) | AC 90-101A |
| Terminal and Initial/Intermediate Accuracy | 1.0 NM | 1.0 NM or lower (down to 0.1 NM) |
| Final Approach Segment Accuracy | 0.3 NM (or 40 meters with SBAS) | 0.3 NM down to 0.1 NM |
| Missed Approach Segment Accuracy | 1.0 NM | 1.0 NM or less than 1.0 NM (down to 0.1 NM) |
| Radius to Fix (RF) Leg Capability | Optional | Mandatory |
| Scalable RNP Lateral Accuracy | Fixed at 1.0 NM and 0.3 NM | Mandatory (scalable down to 0.1 NM) |
| Included in PBN Authorization Bundling? | Yes | No (excluded from bundling) |
Cockpit Execution, Deviation Limits, and Go-Around Triggers
Interviewers frequently move from definitions to a cockpit scenario: you are cleared for an RNAV (RNP) approach, ATC gives you a shortcut, or a deviation develops on final. Strict operational rules govern flying RNP AR procedures that every airline applicant should know.
First, the entire RNP AR procedure must be loaded by name from a current, validated onboard navigation database. You are prohibited from modifying the lateral flight plan path, with one exception: you may accept a clearance to go direct to a fix, provided that fix is prior to the final approach fix (FAF) and does not immediately precede an RF leg. You cannot take a radar vector or a direct-to clearance to the fix right before an RF turn because the aircraft needs lead distance to establish on the entry track tangent to the arc. The only other permitted modification to the loaded procedure is changing altitude or airspeed constraints on the initial, intermediate, or missed approach segments to comply with an ATC instruction.
Second, you must manage your lateral and vertical deviations within strict numerical boundaries. Use the checklist below, which our team built from AC 90-101A Appendix 4, to organize your briefing and flying calls during simulator evaluations and technical interviews.
- Verify equipment and RNP value: Check the Minimum Equipment List (MEL) and Required List of Equipment, verify Class A TAWS is operable, and confirm the smallest required RNP value for the approach or missed approach is entered into the FMS before initiating the procedure.
- Check baro-VNAV temperature limits: Cold temperatures reduce the effective glidepath angle while high temperatures increase it. Unless your aircraft has airworthiness approval for automatic temperature compensation or uses SBAS for vertical guidance, you must operate within the charted temperature limits.
- Maintain 0.5x RNP in normal operations: During normal RNP AR operations, limit your cross-track deviation to plus or minus one-half (0.5x) the navigation accuracy associated with the current segment. Brief overshoots or undershoots during and immediately after turns up to a maximum of 1x RNP are allowable.
- Crosscheck below RNP 0.3: On any approach with an RNP value less than 0.3, crosscheck the lateral and vertical flight guidance against independent displays such as TAWS or weather radar.
- Execute an immediate missed approach at 1x RNP or 75 feet: You must execute a missed approach if your lateral deviation exceeds 1x RNP or your vertical deviation exceeds 75 feet, unless you have acquired the visual references required to continue to the runway.
- Handle GNSS loss and sensor reversion: GNSS updating is required to initiate all RNP AR approaches. If GNSS updating is lost and the system cannot comply with the active RNP value (for example, triggering an UNABLE REQ NAV PERF or NAV ACCUR DOWNGRAD alert), you must abandon the approach unless visual conditions exist. DME/DME updating may be used as a reversionary mode if not prohibited by the chart and if the system maintains the required RNP value, but VOR updating is never authorized on public RNP AR approaches.
NavSpec Bundling, A-RNP, and Flight Planning Rules
When reviewing aircraft qualification documents during an interview, remember the fundamental rule: NavSpecs are considered different from one another, not better or worse based on the lateral accuracy number. Each NavSpec eligibility must be listed in the AFM or avionics documentation. For instance, RNP 1 eligibility does not automatically mean RNP 2 or RNAV 1 eligibility unless granted through operational approval bundling.
When an operator applies for operational authorization, the FAA uses a bundling concept for terminal and en route phases of flight. An operator granted RNP 1 authorization is also granted RNAV 1 authorization. An operator granted domestic RNP 2 authorization is also granted RNAV 2 and RNAV 5 authorizations. Furthermore, RNP 4 eligibility automatically confers RNP 10 and RNAV 10 eligibility. Advanced RNP (A-RNP) is a NavSpec requiring three mandatory functions in the United States: RF turns, scalable RNP, and parallel offset flight path generation. An aircraft eligible for A-RNP is typically eligible for RNP APCH, RNP/RNAV 1, RNP/RNAV 2, RNP 4, and RNP/RNAV 10. However, RNP AR APCH and RNP AR DP are excluded from bundling and require a separate approval.
For flight planning and alternate airports, regulations distinguish between basic GPS receivers (TSO-C129 or TSO-C196) and WAAS receivers (TSO-C145 or TSO-C146). Operators using TSO-C129 or TSO-C196 equipment with fault detection and exclusion (FDE) who perform a preflight RAIM prediction may file based on a GPS-based instrument approach at either the destination or the alternate airport, but not at both locations. Pilots with TSO-C145 or TSO-C146 WAAS equipment are not bound by that restriction and may plan a GPS-based approach at both destination and alternate, provided alternate flight planning is based on LNAV or circling MDA (or LNAV/VNAV DA or RNP 0.3 DA if properly equipped and authorized with approved baro-VNAV). For multisensor aircraft with operating GPS and DME/DME/IRU, a preflight RAIM check is not required for continental en route and terminal operations if critical DMEs are functioning, but a RAIM check is still required when planning an RNP APCH.
Finally, crews must maintain vigilance against GPS jamming and spoofing. Indications of interference include sudden changes in actual navigation performance (ANP), aircraft clock errors, large shifts in displayed GPS position, and Primary Flight Display (PFD) or Navigation Display (ND) position error warnings. If you encounter GPS degradation, cross-check your position using conventional NAVAIDs such as the VOR Minimum Operational Network (MON), prepare to transition to conventional instrument procedures, and promptly notify ATC.
Practice example
Walk me through the difference between an RNAV approach and an RNP approach, and explain how they are titled on US approach charts.
Example answer, written by us. It is not a real applicant's story. Under the FAA Performance-Based Navigation framework in AIM 1-2-1, both RNAV and RNP define a lateral accuracy in nautical miles that the aircraft must stay within for at least 95 percent of the flight time. The key difference is that RNP is RNAV with onboard performance monitoring and alerting (OBPMA). That means an RNP system continuously monitors its Navigation System Error. It alerts the cockpit if the required accuracy is not being met. In the United States, the chart titles can look counterintuitive at first. A standard approach built to the RNP APCH specification is titled RNAV (GPS) on the plate. It scales from 1.0 NM in terminal segments down to 0.3 NM on final, offering LNAV, LNAV/VNAV, LP, and LPV minima. When a US chart is titled RNAV (RNP), it is an RNP Authorization Required approach under AC 90-101A. Those procedures require specific FAA authorization and crew training. They mandate Radius to Fix turn capability and lateral scalability down to 0.10 NM. They also require an immediate go-around if lateral deviation exceeds 1x RNP or vertical deviation exceeds 75 feet.
This answer directly states the 95 percent accuracy standard and names onboard performance monitoring and alerting as the core discriminator. It then resolves the US charting convention between RNAV (GPS) and RNAV (RNP) and finishes with concrete operational limits from AC 90-101A.
Practice this on Fourstripe. Pick your airline and a captain runs the interview out loud: TMAAT, about-you, technical and scenario questions, with real follow-ups. You get a scored report on every answer. 7-day trial, then from $149 a week. Start a practice interview
Frequently asked questions
What is the primary difference between an RNAV approach and an RNP approach?
RNP is Area Navigation (RNAV) with the added requirement for onboard performance monitoring and alerting (OBPMA). While both require the aircraft to stay within a specified lateral accuracy for 95 percent of the flight time, an RNP system actively monitors its achieved navigation performance and alerts the pilot if the operational requirement is not met.
Why are standard RNP approaches titled RNAV (GPS) in the United States?
Procedures built to the ICAO RNP Approach (RNP APCH) specification are titled RNAV (GPS) on US charts to indicate the lateral guidance sensor used on final approach while providing LNAV, LNAV/VNAV, LP, and LPV minima. Procedures titled RNAV (RNP) on US charts are RNP Authorization Required (RNP AR APCH) procedures that mandate special FAA authorization, crew training, RF leg capability, and lateral scalability.
When must a pilot execute a missed approach on an RNP AR approach?
A pilot must execute an immediate missed approach on an RNP AR procedure if the lateral cross-track deviation exceeds 1x the active RNP value or if the vertical deviation exceeds 75 feet, unless the visual references required to continue to the runway have been acquired. A missed approach is also required if GNSS updating is lost and the navigation system cannot maintain the required RNP value.
Can you accept a direct-to clearance to any waypoint on an RNP AR approach?
No. Pilots may not modify the lateral path of a loaded RNP AR procedure except to go direct to a fix that is prior to the final approach fix (FAF) and does not immediately precede a Radius to Fix (RF) leg.
Sources
- FAA Aeronautical Information Manual (AIM) Chapter 1, Section 2: Performance-Based Navigation (PBN) and Area Navigation (RNAV)
- FAA Advisory Circular 90-105A: Approval Guidance for RNP Operations and Barometric Vertical Navigation
- FAA Advisory Circular 90-101A Change 1: Approval Guidance for RNP Procedures with AR
- International Civil Aviation Organization: Doc 9613 Performance-based Navigation (PBN) Manual
- Electronic Code of Federal Regulations: Title 14 Part 97 Standard Instrument Procedures
- faa.gov
- faa.gov
- faa.gov