SBAS Standards Source Matrix

Scope

This matrix is the institutional source-routing layer for the SBAS knowledge base. It classifies which source families can support which kinds of claims and identifies documents that earlier drafts used incorrectly.

This page is not an operational standards table. It does not provide procedure minima, aircraft eligibility, crew authorization, service availability, receiver certification status, or alert-limit values. Those require the applicable official standards, regulator material, service-provider documents, AIP/procedure publications, aircraft/avionics documentation, and operator approvals.

Executive summary

The current source-hardening work has produced eleven high-value outcomes:

Source - RTCA DO-229 is the strongest current public-product-and-regulatory-signal-reviewed anchor for GPS/SBAS airborne equipment, but it remains a routing note rather than an official-text extraction.
Source - ICAO Doc 9849 is the better ICAO GNSS implementation-guidance anchor than the previously cited Doc 9854/9855 pair.
Source - FAA TSO-C145e and TSO-C146e and Source - EASA ETSO-C145e and ETSO-C146e now separate FAA/EASA article-approval context from DO-229 MOPS, aircraft installation approval, and operational approval.
Source - RTCA DO-242, Source - RTCA DO-289, Source - ICAO Doc 9854, and Source - ICAO Doc 9855 are now red-flagged as mis-scoped for SBAS technical/integrity claims based on public catalog signals.
Source - ICAO APAC GBAS-SBAS Implementation Forums is elevated from starter scaffold to partially-verified regional coordination anchor, with ITF/7 (May 2025, A3-WP05 rev3) as the first confirmed public ICAO APAC SBAS working paper. Confirmed signals: LP/LPV/LNAV/VNAV/LNAV operational types, Class 3/4 SBAS avionics, six-year advance-notice requirement, SBAS architecture components.
UPDATED — 2026-05-03: service-provider routing now has dedicated child source notes with direct public-source extraction or bounded source-posture review for the current major-system set: Source - WAAS, Source - EGNOS, Source - GAGAN SBAS Operation, Source - MSAS, Source - BDSBAS, Source - KASS, Source - SouthPAN, and Source - SDCM. These source notes support system-specific identity and selected implementation/service/development signals only; they do not support cross-system performance comparisons, operational authorization, procedure availability, or procedure minima without regulator/AIP/service-performance extraction.
SBAS Operational Validation Dashboard now separates service-provider evidence from regulator, ANSP, AIP, procedure, aircraft, and operator evidence so system notes cannot drift into unsupported operational claims.
The practical service-provider posture is now stronger but still conservative: first-layer child-source coverage exists; deeper regulator/AIP/performance extraction is still required before publishing operational claims.
SBAS Core Claim Routing now owns core claim-family routing so concept pages can explain SBAS architecture, message flow, correction/integrity separation, protection levels, alert limits, and responsibility boundaries without duplicating standards text or service-provider evidence.
UPDATED — 2026-05-04: second-layer core routing now separates service-performance concepts, service volume/coverage, approach-capability labels, receiver modes/annunciation, and the standards-to-operations evidence ladder without adding new numerical requirements or operational approval claims.
UPDATED — 2026-05-04: third-layer core mechanism routing now separates ranging/time-reference, satellite orbit/clock correction, ionospheric grid-correction context, correction timescale, integrity-data/user-bound, and service-status/notice claims without adding message tables, algorithms, numerical tolerances, current NOTAM/outage facts, or operational-use claims.

The practical consequence is conservative: the KB should continue to explain SBAS concepts clearly, but it should not publish exact numerical operational requirements until each number is tied to the right official source family.

Source identity and claim-routing matrix

Source note	Public identity signal reviewed in this cycle	Safe current role in this KB	Do not use it for
Source - RTCA DO-229	RTCA GPS/SBAS airborne-equipment MOPS; public RTCA product signal identifies DO-229F as single-frequency GPS/SBAS airborne-equipment MOPS	Airborne receiver/equipment source-family anchor; LPV/LP/LNAV/VNAV equipment-capability routing; receiver-performance extraction target	SBAS ground-system certification, state approval, service availability, procedure minima, aircraft installation/operational approval, or DFMC requirements
Source - FAA TSO-C145e and TSO-C146e	FAA TSO/article-approval source family for GPS/WAAS sensors and stand-alone equipment; public FAA policy separates TSOA from installation approval	U.S. regulator/article-approval routing layer; future direct FAA TSO extraction target	Aircraft installation approval, operational approval, procedure minima, LPV availability, or EASA equivalence
Source - EASA ETSO-C145e and ETSO-C146e	EASA ETSO/article-approval source family for GPS/SBAS sensors and stand-alone equipment; public PDFs extracted and tied to DO-229E Section 2	European regulator/article-approval routing layer; extracted source-family boundary for C145e/C146e	Aircraft installation approval, operational approval, procedure minima, LPV availability, or FAA equivalence
Source - ICAO Doc 9849	ICAO Global Navigation Satellite System (GNSS) Manual	GNSS/SBAS implementation-guidance anchor for States and GNSS-based services	Detailed normative SARPs, aircraft equipment MOPS, exact LPV alert limits, direct operational approval
Source - ICAO Annex 10 Volume I GNSS SBAS	ICAO Annex 10, Volume I, Radio Navigational Aids; public ICAO Store signal identifies GNSS among covered radio-navigation-aid systems	ICAO SARPs/technical-provisions source-family anchor for GNSS/SBAS claim routing	Detailed Annex content, numerical SBAS values, procedure minima, aircraft eligibility, or operational approval claims until official text is extracted
Source - ICAO PANS-OPS Doc 8168 and Doc 9613 PBN Manual	ICAO procedure-design and PBN navigation specification source family; Doc 8168 Vol II 7th Edition (2020) and Doc 9613 5th Edition (2023)	Procedure-design and PBN navigation-specification routing anchor; LPV/LNAV/VNAV/RNAV/RNP procedure-design source-family target	Aircraft installation approval, operational approval, or procedure minima without official text extraction
Source - ICAO APAC GBAS-SBAS Implementation Forums	ICAO APAC GBAS/SBAS Implementation Task Force (ITF); verified ITF/7 (May 2025, A3-WP05 rev3) as first confirmed public ICAO APAC SBAS working document	Asia-Pacific regional coordination anchor; verified LP/LPV/LNAV/VNAV/LNAV operational-type and Class 3/4 SBAS avionics confirmation as of May 2025	ASEAN governance claims, LPV operational approval, or service-model endorsement without direct ITF/ITF working paper extraction
Source - FAA and EASA Procedure-Design and PBN Material	FAA Order 8260.3G TERPS (2024), FAA Order 8260.58D PBN Procedure Design (2025), EASA AMC/GM / Easy Access Rules for PBN operations	FAA/EASA procedure-design and PBN operational-approval routing layer	Airport-specific procedure minima, operational approval, or national equivalence without direct text extraction
Source - SBAS Service Providers	SBAS service-provider source family; WAAS (FAA), EGNOS (EUSPA/EGNOS SDD), MSAS/QZSS, GAGAN/AAI-ISRO, BDSBAS/CSNO, KASS/KARI-MOLIT, SouthPAN/GA-LINZ, SDCM/GLONASS-IAC + historical ICAO context	Service-provider routing anchor for system identity, coverage, availability, service commitments, child source-note routing, and source-posture boundaries; direct/bounded child notes now exist for WAAS, EGNOS, GAGAN, MSAS, BDSBAS, KASS, SouthPAN, and SDCM	Comparative performance tables without verified service-provider data; interoperability claims without bilateral agreements; operational approval or procedure availability without regulator/AIP evidence
SBAS Operational Validation Dashboard	Internal source-routing dashboard created from current source-family boundaries	Validation ladder separating service-provider evidence from regulator/ANSP/AIP/procedure/aircraft/operator evidence	Original evidence for any operational claim; it routes validation work but does not itself prove procedure availability or approval
SBAS Core Claim Routing	Internal core-claim routing dashboard created from standards/source-family boundaries	Source-family routing for architecture, message flow, corrections, integrity, receiver responsibility, performance concepts, coverage, receiver-mode, protection-level, alert-limit, service-provider, and operational-validation claims	Original evidence for standards or operational facts; detailed message definitions, numerical thresholds, equipment approval, or service commitments without primary source extraction
SBAS Standards to Operations Evidence Ladder	Internal evidence-ladder routing note	Separates standards concepts, service definitions, receiver capability, procedure design, AIP publication, aircraft/operator authorization, and current operational use	Original proof for any layer; it routes evidence but does not replace source extraction
Regulator / ANSP / AIP material	Partly present in regional source backlogs	Candidate source family for operational authorization, published procedures, and state implementation	Not inferable from technical standards alone
Source - ICAO Doc 9854	ICAO Global Air Traffic Management Operational Concept	High-level ATM modernization context only, if directly extracted later	SBAS performance testing, SBAS monitoring, LPV, alert limits, protection levels
Source - ICAO Doc 9855	ICAO public-internet guidance for aeronautical applications	Possible internet/aeronautical-applications context only, if directly extracted later	SBAS technical specifications, GNSS/SBAS architecture, integrity requirements
Source - RTCA DO-242	RTCA ADS-B / surveillance standard signal	ADS-B/surveillance provenance only, if needed later	SBAS augmentation-system or integrity claims
Source - RTCA DO-289	RTCA aircraft-surveillance-applications standard signal	Aircraft-surveillance provenance only, if needed later	SBAS performance testing or monitoring

Claim-type matrix

Claim type	Primary source family needed	Current KB posture	Safe publication pattern
What SBAS is	ICAO GNSS implementation guidance; Annex 10 source note; service-provider descriptions; SBAS Core Claim Routing for claim boundaries	Conceptually strong, source-routed	Explain at high level; link to source notes and keep caveats
SBAS architecture	ICAO GNSS guidance; Annex 10; service-provider architecture documentation; SBAS Core Claim Routing	Conceptually strong, source-routed, direct standards extraction still pending	Describe chain: GNSS satellites, reference network, processing, uplink, GEO/space broadcast, receiver processing; do not publish detailed message/numeric requirements here
SBAS signal/message flow	Annex 10 technical-provisions source family; airborne-equipment standards for receiver use; SBAS Signal and Message Flow as concept note	Core concept note added; detailed message-field extraction still pending	Explain observation-to-message-to-receiver path without message-number tables or bit-level claims
Correction versus integrity	Annex 10 / GNSS implementation guidance; SBAS Corrections and Integrity Separation	Core boundary note added	Keep accuracy-improvement claims separate from integrity/use-or-non-use claims
Ground/airborne responsibilities	Service-provider source family for service side; airborne equipment standards and TSO/ETSO source family for receiver side; operational dashboard for approval side	Core responsibility note added	Separate ground service, receiver behavior, procedure publication, aircraft installation, and operator approval
Airborne SBAS equipment	RTCA/EUROCAE airborne equipment MOPS; regulator TSOs/ETSO material	DO-229 plus FAA/EASA TSO/ETSO source notes now exist	Link DO-229 for MOPS routing and FAA/EASA notes for article-approval routing; avoid installation or operational claims without additional sources
LPV operational use	Equipment MOPS + procedure design + service availability + aircraft/operator/regulator approvals	LPV page is educational and source-disciplined; procedure-design source notes now exist	State dependency layers; do not publish minima/eligibility as facts
Procedure design / PBN operations	ICAO Doc 8168 / Doc 9613; FAA Order 8260.3G/8260.58D; EASA AMC/GM; national AIP/procedure sources	Procedure-design source notes now exist as routing anchors	Link procedure-design source notes; avoid inferring minima, obstacle clearance, or eligibility without official text extraction
Protection levels and alert limits	Equipment standards + ICAO/RTCA/EUROCAE definitions + procedure/operation-specific material	Concept pages upgraded but still source-scaffold-linked	Explain relationship without numerical thresholds
Service performance concepts	Standards, service definitions, official performance reports, and operational-validation evidence where applicable	SBAS Service Performance Concepts added as core boundary note	Separate accuracy, integrity, availability, continuity, coverage, and service commitments; do not infer operational approval
Service volume and coverage	Service-provider service definitions and child source notes; operational sources only when converting coverage into use	SBAS Service Volume and Coverage added as core boundary note	Treat coverage as service/signal context, not procedure publication or aircraft/operator eligibility
Approach capability labels	DO-229 / ETSO / procedure-design / AIP evidence depending on claim layer	SBAS Approach Capability Taxonomy added as taxonomy boundary note	Use LP/LPV/LNAV/VNAV labels as capability/procedure-family labels only; do not infer runway procedure or operational approval
Receiver modes and annunciation	DO-229, ETSO, avionics/aircraft/operator evidence where detailed	SBAS Receiver Modes and Annunciation added as receiver-boundary note	Avoid cockpit, timing, algorithm, or pilot-action details without direct standards/avionics/operator sources
Ranging and time-reference context	Annex 10 / DO-229 / GNSS and service-specific source families	SBAS Ranging Sources and Time Reference added as mechanism-boundary note	Avoid generic timing tolerances, GEO ranging claims, or receiver-use claims without direct source support
Satellite orbit/clock corrections	Annex 10 / DO-229 / Doc 9849 source families; service-specific evidence where needed	SBAS Satellite Orbit and Clock Corrections added as correction-context note	Avoid equations, update intervals, validity periods, service commitments, or integrity claims from correction language alone
Ionospheric grid correction concept	Annex 10 / DO-229 source families; ionosphere research notes for threat discovery only	SBAS Ionospheric Grid Correction Concept added as ionospheric-correction routing note	Avoid GIVE values, grid definitions, operational interpolation rules, or certification claims from TEC/research evidence
Correction timescale taxonomy	Annex 10 / DO-229 / Doc 9849 source families	SBAS Correction Timescale Taxonomy added as category-boundary note	Avoid message-number/update-interval/degradation tables without direct source extraction
Integrity data and user bounds	Annex 10 / DO-229 source families, receiver evidence, procedure/operation evidence where operational	SBAS Integrity Data and User Bounds added as bridge between corrections, PL/AL, receiver behavior, and validation	Avoid numerical bounds, equations, alert timing, or operational approval without the applicable source layer
Service status and notices	service-provider, regulator, ANSP, AIS/AIP, NOTAM/status, aircraft/operator evidence as applicable	SBAS Service Status and Operational Notices added as status/notice routing note	Avoid stale current-status duplication in generic concept notes
Performance monitoring	ICAO GNSS manual / Annex 10 / service-provider performance reports	Source family not yet fully built	Discuss as a needed source branch, not as a verified table
Country or regional readiness	Regulator/ANSP/AIP/service-provider sources; institutional plans	ASEAN branch is cautious synthesis	Use readiness categories only with explicit evidence limits
System comparisons	Service definitions and performance reports from each system; Source - SBAS Service Providers plus dedicated child notes for individual systems; SBAS Operational Validation Dashboard for escalation rules	Source posture improved: WAAS, EGNOS, GAGAN, MSAS, BDSBAS, KASS, SouthPAN, and SDCM now have dedicated child/source-posture notes	Compare source posture first; avoid false precision; link to dedicated child source notes only for system-specific verified signals; avoid comparative availability/performance unless each system has equivalent official evidence

Red-flag correction register

Earlier draft mapping	Current correction	Impact
Doc 9855 as SBAS technical specifications	Public ICAO catalog identifies Doc 9855 as public-internet guidance for aeronautical applications	Remove as SBAS technical source; replace with Doc 9849 / Annex 10 source-building path
Doc 9854 as GBAS/SBAS performance testing and monitoring	Public ICAO catalog identifies Doc 9854 as Global ATM Operational Concept	Remove as SBAS performance-testing source; keep only as possible ATM concept source
DO-242 as GNSS augmentation-system/integrity source	Public catalog identifies DO-242 as ADS-B related	Stop using for SBAS integrity and augmentation claims
DO-289 as SBAS performance-testing source	Public catalog identifies DO-289 as aircraft surveillance applications	Stop using for SBAS testing/monitoring claims

Recommended source-building sequence

Directly extract Source - ICAO Annex 10 Volume I GNSS SBAS from the official Annex text, including exact edition/amendment baseline and GNSS/SBAS section mapping.
Directly extract the official Source - RTCA DO-229 text for equipment classes, LPV/LP/LNAV/VNAV capability, receiver integrity, alerting, and test-method language; map it separately from Source - EASA ETSO-C145e and ETSO-C146e, installation approval, and operational-approval sources. FAA-specific extraction is intentionally skipped in the current core-solidification block.
Directly extract Source - ICAO Doc 9849 sections relevant to GNSS implementation, SBAS introduction, monitoring/assessment/reporting, DFMC GNSS, and interference mitigation.
~~Create procedure-design source notes for the PANS-OPS / PBN side of LPV, LNAV/VNAV, RNAV, and RNP notes.~~ Completed 2026-05-03: Source - ICAO PANS-OPS Doc 8168 and Doc 9613 PBN Manual now exists as the primary ICAO procedure/PBN routing anchor; EASA material remains available through the mixed procedure-design source note where needed. FAA-specific extraction is intentionally skipped in the current core-solidification block.
~~Create service-provider source notes for WAAS, EGNOS, MSAS, GAGAN, BDSBAS, KASS, SouthPAN, and other systems before publishing comparative performance tables.~~ Substantially completed 2026-05-03 for the current major-system set: the family routing anchor is Source - SBAS Service Providers. Dedicated child/source-posture notes now exist for Source - WAAS, Source - EGNOS, Source - GAGAN SBAS Operation, Source - MSAS, Source - BDSBAS, Source - KASS, Source - SouthPAN, and Source - SDCM. Comparative performance tables remain prohibited until equivalent official performance/service evidence exists for each compared system.
Operational validation priority: use SBAS Operational Validation Dashboard before elevating any system page from source-context evidence to regulator/ANSP/AIP/procedure/aircraft/operator operational claims.
Core concept routing priority: use SBAS Core Claim Routing, SBAS Signal and Message Flow, SBAS Corrections and Integrity Separation, SBAS Ground Segment and Airborne Receiver Responsibilities, SBAS Service Performance Concepts, SBAS Service Volume and Coverage, SBAS Approach Capability Taxonomy, SBAS Standards to Operations Evidence Ladder, SBAS Receiver Modes and Annunciation, SBAS Ranging Sources and Time Reference, SBAS Satellite Orbit and Clock Corrections, SBAS Ionospheric Grid Correction Concept, SBAS Correction Timescale Taxonomy, SBAS Integrity Data and User Bounds, and SBAS Service Status and Operational Notices to keep core knowledge atomic and non-overlapping.
Next service-provider depth priority: extract non-FAA regulator/AIP/performance/service-volume sources for EGNOS, KASS, BDSBAS, MSAS, GAGAN, SouthPAN, and SDCM where operational procedure availability or service commitments are needed.
Regional governance priority: Directly extract Source - ICAO APAC GBAS-SBAS Implementation Forums for ITF/7 full meeting page and remaining ITF/6 through ITF/1 working papers; this remains the highest-value regional governance signal for ASEAN SBAS planning.
Only after the above, reintroduce numerical thresholds or performance values into concept and aviation pages.

Documentation rules for downstream pages

When editing downstream pages:

Use Source - RTCA DO-229 only for airborne GPS/SBAS equipment MOPS source-family routing.
Use Source - FAA TSO-C145e and TSO-C146e and Source - EASA ETSO-C145e and ETSO-C146e only for regulator/article-approval routing unless direct official text and aircraft/operator sources support stronger claims.
Use Source - ICAO Doc 9849 only for implementation-guidance routing until direct extraction is complete.
Keep Source - RTCA DO-242, Source - RTCA DO-289, Source - ICAO Doc 9854, and Source - ICAO Doc 9855 visible as red-flag notes so earlier draft confusion remains traceable rather than silently erased.
Use Source - SBAS Service Providers as the family router for service-provider claims; use Source - WAAS, Source - EGNOS, Source - GAGAN SBAS Operation, Source - MSAS, Source - BDSBAS, Source - KASS, Source - SouthPAN, and Source - SDCM only for their extracted system-specific signals and boundaries.
Use SBAS Core Claim Routing before adding or editing core concept claims; route architecture, message flow, ranging/time-reference, correction-category, orbit/clock, ionosphere-grid, integrity-data, receiver, service-performance, coverage, capability-label, service-status, protection-level, and alert-limit claims to the correct owner page instead of duplicating them.
Use SBAS Standards to Operations Evidence Ladder before moving from standards or service terminology into procedure, aircraft, operator, or current-use statements.
Use SBAS Operational Validation Dashboard to decide whether a claim needs regulator, ANSP, AIP, procedure, aircraft, or operator evidence before publication.
Do not create broken wikilinks for future standards notes. Mention future targets in plain text unless creating the note now.
If a number matters operationally, do not publish it without a direct source anchor and clear applicability conditions.

SBAS Knowledge Base

Explorer

SBAS Standards Source Matrix

SBAS Standards Source Matrix

Scope

Executive summary

Source identity and claim-routing matrix

Claim-type matrix

Red-flag correction register

Recommended source-building sequence

Documentation rules for downstream pages

See also

Graph View

Table of Contents

Backlinks