SBAS Approach Capability Taxonomy

Purpose

This note owns only the high-level taxonomy boundary for SBAS-related approach-capability language. It prevents LP, LPV, LNAV/VNAV, LNAV, APV, and related labels from being used as if they automatically prove a published procedure or operational authorization.

It does not define minima, procedure-design criteria, avionics requirements, or country-specific procedure inventories.

Non-overlap ownership

TopicOwner
LPV learning pageLPV-Approach-Procedure
Procedure-design / PBN source familySource - ICAO PANS-OPS Doc 8168 and Doc 9613 PBN Manual
Receiver capability source familySource - RTCA DO-229, Source - EASA ETSO-C145e and ETSO-C146e
Service-provider evidenceSource - SBAS Service Providers and child notes
Operational proofSBAS Operational Validation Dashboard
Capability taxonomy boundarythis note

Capability-label caution

Capability labels are not operational proof.

Label familyWhat it can discuss at concept levelWhat must not be inferred
LP / LPVSBAS-supported approach-capability concepts where source families support the termthat a runway has a published LP/LPV procedure
LNAV/VNAVlateral plus vertical navigation approach conceptthat SBAS is the only vertical source or that a specific operation is authorized
LNAVlateral navigation approach conceptthat vertical guidance or SBAS integrity is available
APV / PBN languageapproach and navigation-specification contextexact criteria, minima, or state approval without procedure-design and AIP evidence

Safe wording pattern

The label identifies a capability or procedure family. Operational use requires evidence for the service, receiver, procedure, aircraft, operator, and regulator layers.

Source anchors

See also