Performance-Based Navigation (PBN)

Performance-Based Navigation (PBN) is the shift from prescribing what equipment an aircraft must carry to prescribing how well it must navigate. The framework is set out in ICAO Doc 9613, the Performance-Based Navigation Manual. Under the older, sensor-based approach, a route or procedure would require a specific piece of kit — say, a particular VOR/DME arrangement. Under PBN, the airspace or procedure instead calls for a navigation specification defining the performance the aircraft must achieve, and any equipment fit that can meet it is acceptable. That decoupling is what lets modern GNSS-based avionics, older ground-based aids, and inertial systems all serve the same procedure as long as they deliver the required performance.

A navigation specification details the performance an RNAV or RNP system must deliver in terms of accuracy, integrity, continuity, and functionality, together with the on-board functions, the navigation sensors that may be used, and the associated flight-crew training and operating requirements. PBN divides these specifications into two families, and the distinction is the single most-tested point in the concept. An RNAV (area navigation) specification requires the aircraft to hold a defined lateral accuracy but does not itself require the aircraft to monitor and warn when it is failing to do so. An RNP (Required Navigation Performance) specification adds exactly that: on-board performance monitoring and alerting, so that the crew is alerted when the system cannot guarantee, with sufficient integrity, the navigation performance the operation demands. In short, all RNP is RNAV with self-checking; RNAV without the monitoring-and-alerting requirement is not RNP.

Navigation specifications are named with a designator that expresses the required lateral accuracy in nautical miles. RNAV 1 and RNAV 5, for example, require the aircraft to remain within 1 or 5 nautical miles of the intended track for the defined proportion of flight time; RNP 4 and RNP 1 apply the same idea with the added monitoring-and-alerting requirement. Approach-phase specifications include RNP APCH, the widely used approach specification associated with GNSS-based approaches, and RNP AR (Authorization Required), a more demanding specification permitting tighter, often curved paths in challenging terrain, which requires specific operational approval and aircraft qualification.

PBN is the umbrella over the instrument approaches pilots fly every day. A single approach chart built on RNP APCH can offer several lines of minima according to the aircraft's capability: LNAV (lateral navigation only), LNAV/VNAV (lateral plus barometric or augmented vertical guidance), and LPV (Localizer Performance with Vertical guidance, delivered via satellite-based augmentation such as WAAS or EGNOS), which can approach ILS-like minima without any ground-based glideslope. Understanding PBN is therefore the conceptual key to why these approach types exist, how they relate, and why an aircraft's navigation authorization — not just its raw equipment — determines which lines of minima it may use.

For instrument-training providers, PBN is no longer an advanced niche; it is the mainstream of the instrument syllabus. Ground-based approaches are being decommissioned in many regions while GNSS-based RNP APCH procedures proliferate, so a competent instrument student has to understand navigation specifications, the RNAV-versus-RNP distinction, and how to read the multiple minima lines on a modern approach chart. A school that still teaches instrument approaches purely in ground-based terms is preparing students for an environment that is disappearing.

PBN also has an operational-approval dimension that flight schools and operators must track. Some specifications, particularly RNP AR, require specific operational authorization and demonstrated aircraft and crew qualification before the procedures can be flown. Even for the more routine RNP APCH, the currency and training records that show a pilot is qualified to fly a given specification are part of the compliance picture. Matching the right aircraft and a suitably qualified and current instructor to a lesson that includes PBN procedures is a scheduling as well as a training-standards question.

Aviatize's Training Management module records the PBN-related endorsements, authorizations, and currency that determine which navigation specifications a pilot or instructor is qualified to fly, so a school can see at a glance whether a student's planned instrument lesson is properly resourced. When a specification requires specific approval or recurrent training, the associated records are tracked alongside the pilot's other qualifications rather than living in a separate spreadsheet.

The Compliance & Auditing module keeps the evidence of operational approvals and the training standards behind them audit-ready, so that when an authority reviews how the organization delivers and documents PBN training and operations, the records are already assembled.