SBAS Standards and Regulation

Scope

This page is an institutional orientation to SBAS standards and regulatory source families. It is designed to help readers understand which documents and institutions may support which types of claims.

It is not an operational compliance manual. Do not use this page to determine procedure minima, aircraft eligibility, receiver certification, crew authorization, service availability, or regulatory compliance. Those decisions require the applicable official standards, regulator material, service-provider documentation, aircraft/avionics approval basis, AIP/procedure publications, and operator procedures.

Current source posture

This standards branch has moved from a draft list of document names to a source-disciplined map. The most important correction is that several earlier document mappings were too broad or apparently incorrect.

Use SBAS Standards Source Matrix as the current routing table.

Standards source families

Source familyTypical claim boundaryCurrent KB anchor
ICAO SARPs / technical provisionsGlobal aviation baseline for aeronautical telecommunications, GNSS, and augmentation requirementsSource - ICAO Annex 10 Volume I GNSS SBAS is the current public-catalog-reviewed source-family anchor; official text extraction still needed
ICAO implementation guidanceState introduction of GNSS operations, implementation considerations, monitoring/assessment/reportingSource - ICAO Doc 9849
RTCA / EUROCAE airborne equipment standardsReceiver/equipment performance, equipment classes, test methods, and avionics capabilitySource - RTCA DO-229 is the current GPS/SBAS airborne-equipment MOPS anchor
FAA / EASA TSO-ETSO article-approval layerRegulator article approval, approval-basis routing, jurisdiction-specific modifications, and manufacturing/design approval contextSource - FAA TSO-C145e and TSO-C146e and Source - EASA ETSO-C145e and ETSO-C146e now separate approval context from installation and operational approval
Procedure-design criteriaProcedure construction, minima design, coding assumptions, obstacle assessmentDedicated PANS-OPS / procedure-design source notes still needed
Regulator / ANSP / AIP sourcesState implementation, operational approval, published procedures, and actual availabilityRegional and country source notes still being built
Service-provider documentsService definition, coverage, performance, NOTAM/status practices, system-specific operational commitmentsFuture service-provider source notes needed for each SBAS system

Confirmed correction register

Earlier in-vault mappingCurrent correctionResulting editorial rule
ICAO Doc 9855 as SBAS technical specificationPublic ICAO catalog identifies Doc 9855 as Guidelines on the Use of the Public Internet for Aeronautical ApplicationsDo not cite Doc 9855 for SBAS technical claims
ICAO Doc 9854 as SBAS/GBAS performance testing and monitoringPublic ICAO catalog identifies Doc 9854 as Global Air Traffic Management Operational ConceptDo not cite Doc 9854 for SBAS performance-testing claims
RTCA DO-242 as GNSS augmentation/integrity standardPublic catalog identifies DO-242 as ADS-B relatedDo not cite DO-242 for SBAS integrity or augmentation-system claims
RTCA DO-289 as SBAS performance-testing standardPublic catalog identifies DO-289 as aircraft surveillance applicationsDo not cite DO-289 for SBAS monitoring or testing claims

These corrections are intentionally preserved as red-flag source notes rather than deleted, so future editors can see why older draft references changed.

Current high-confidence anchors

RTCA DO-229

Source - RTCA DO-229 is the current public-product-and-regulatory-signal-reviewed anchor for GPS/SBAS airborne equipment. It can route claims about airborne receiver/equipment source-family support, but detailed numerical requirements and equipment-class specifics still require direct extraction from the official RTCA standard. FAA/EASA article-approval context is now routed through Source - FAA TSO-C145e and TSO-C146e and Source - EASA ETSO-C145e and ETSO-C146e. Aircraft installation approval, operational approval, and compliance interpretations still require additional official approval material.

ICAO Annex 10, Volume I

Source - ICAO Annex 10 Volume I GNSS SBAS is the current public-catalog-reviewed anchor for the ICAO SARPs/technical-provisions source family relevant to GNSS/SBAS claim routing. Public ICAO Store metadata supports document identity, edition/amendment signal, and broad scope only; detailed Annex requirements still require official-text extraction before reuse.

ICAO Doc 9849

Source - ICAO Doc 9849 is the current public-catalog-reviewed anchor for ICAO GNSS implementation guidance. It is useful for state implementation and GNSS/SBAS introduction context, but it must not be used alone as a normative requirements source.

FAA/EASA TSO-ETSO source layer

Source - FAA TSO-C145e and TSO-C146e and Source - EASA ETSO-C145e and ETSO-C146e now provide the regulator/article-approval routing layer for GPS/WAAS or GPS/SBAS airborne equipment. They should not be treated as aircraft installation approvals or operational approvals.

Claim boundaries by topic

TopicWhat this page may say nowWhat remains source-pending
SBAS concept and architectureSBAS is a GNSS augmentation architecture involving ground monitoring, correction/integrity processing, broadcast, and receiver useExact SARPs, message definitions, service commitments, and performance values
Airborne SBAS equipmentDO-229 is the correct current source-family anchor for GPS/SBAS airborne-equipment MOPS; FAA/EASA source notes route article-approval contextRevision-specific requirements, tests, equipment classes, alerting details, direct FAA TSO text, and deeper EASA section mapping
LPV and approach operationsLPV operational use depends on service, equipment, procedure, approval, and real-time integrity conditionsMinima, eligibility, procedure-design rules, and country/operator approval details
Integrity / protection levels / alert limitsThe conceptual relationship can be explained safelyExact definitions, thresholds, and operation-specific values
System comparisonsSource posture can be comparedPerformance rankings and availability claims require service-provider evidence

Immediate institutional source-building needs

  1. Direct extraction of Source - ICAO Annex 10 Volume I GNSS SBAS for exact GNSS/SBAS SARPs/technical-provisions mapping.
  2. Direct extraction of the official Source - RTCA DO-229 text for airborne-equipment, equipment-class, test-method, and receiver-integrity language; direct FAA TSO-C145e/C146e text extraction; deeper EASA ETSO-C145e/C146e section mapping.
  3. Direct extraction of Source - ICAO Doc 9849 for state GNSS implementation and SBAS monitoring guidance.
  4. Procedure-design source notes before further expanding LPV/LNAV/VNAV/RNAV/RNP/GBAS procedure pages.
  5. Service-provider source notes for WAAS, EGNOS, MSAS, GAGAN, BDSBAS, KASS, SouthPAN, and other systems before comparative performance tables.

See also