SBAS MOC

Scope

This is the top-level map for the SBAS knowledge base. It routes readers into the major branches: core concepts, aviation operations, standards and sources, regional systems, ASEAN implementation, GIPTA 2.0, and ionospheric research.

Use this page as the institutional navigation layer. Use index as the public landing page and SBAS-Research-MOC for research-program tracking.

Recommended reader paths

Reader path	Start here	Continue to
Beginner	What is SBAS	SBAS Architecture, SBAS Signal and Message Flow, SBAS Corrections and Integrity Separation, SBAS Ranging Sources and Time Reference, SBAS-Terminology
Core source routing	SBAS Core Claim Routing	SBAS Standards Source Matrix, SBAS Standards to Operations Evidence Ladder, SBAS Operational Validation Dashboard
Aviation operations	SBAS in Civil Aviation MOC	LPV-Approach-Procedure, Protection Levels, Alert Limits
Standards and source review	SBAS Standards Source Matrix	SBAS-Standards-Regulation, SBAS Source Backlog, Source - RTCA DO-229, Source - ICAO Doc 9849
Regional systems	SBAS-Systems-by-Region-MOC	WAAS, EGNOS, MSAS, GAGAN, BDSBAS, KASS, SouthPAN, SDCM
ASEAN implementation	ASEAN SBAS Adoption Landscape	ASEAN SBAS Readiness Heuristic, ASEAN SBAS Service-Model Options
GIPTA 2.0	GIPTA 2.0 MOC	GIPTA 2.0 and ASEAN SBAS Implementation Pathway, ASEAN SBAS Testbed
Ionospheric research	SBAS Ionospheric Threat — Empirical Evidence	IRI-2020 vs GNSS-RO Indonesia, GNSS Radio Occultation
Site governance	SBAS Knowledge Base Editorial and Source Policy	Institutional Upgrade Audit 2026-05-01, Institutional SBAS Knowledge Base Upgrade Roadmap

Core concept branch

• What is SBAS — beginner gateway.
• SBAS Architecture — system chain and institutional dependencies.
• SBAS Architecture Flow — compact flow diagram.
• SBAS Signal and Message Flow — observation-to-message-to-receiver chain without unsourced message-number details.
• SBAS Ranging Sources and Time Reference — GNSS/SBAS ranging and time-reference routing without timing or approval overclaiming.
• SBAS Corrections and Integrity Separation — correction, integrity, availability, and continuity boundary note.
• SBAS Satellite Orbit and Clock Corrections — satellite-related correction context without algorithms or service commitments.
• SBAS Ionospheric Grid Correction Concept — ionospheric correction routing separated from TEC research and operational GIVE/model claims.
• SBAS Correction Timescale Taxonomy — fast/long-term/ionospheric correction-category routing without update-interval tables.
• SBAS Integrity Data and User Bounds — integrity-data/user-bound routing between corrections, protection levels, and alert limits.
• SBAS Service Status and Operational Notices — current-status/notice routing without stale provider-specific duplication.
• SBAS Ground Segment and Airborne Receiver Responsibilities — responsibility split between service, receiver, procedure, and operation layers.
• SBAS Service Performance Concepts — accuracy, integrity, availability, continuity, coverage, and service-commitment boundaries.
• SBAS Service Volume and Coverage — coverage claims without procedure or approval overreach.
• SBAS Approach Capability Taxonomy — LP/LPV/LNAV/VNAV capability-label routing.
• SBAS Receiver Modes and Annunciation — receiver-mode and alert/annunciation routing without detailed MOPS claims.
• SBAS Core Claim Routing — source-family routing rules for core claims.
• SBAS-Terminology — controlled terminology.
• SBAS Integrity — integrity as the safety-relevant SBAS function.
• Protection Levels — bounded error concept.
• Alert Limits — operation-specific usability threshold.
• SBAS-vs-Other-Augmentation-Methods — SBAS, GBAS, ABAS, and related augmentation concepts.
• Safety-Terminology — safety vocabulary used in aviation notes.
• Communication-Terminology — communications and data vocabulary used in the vault.

Aviation operations branch

• SBAS in Civil Aviation MOC — civil-aviation operational map.
• LPV-Approach-Procedure — LPV learning note; quantitative details require source tightening.
• LNAV-VNAV-Approach-Procedure
• RNAV-Approach-Procedure
• RNP-Approach-Procedure
• GBAS-Approach-Procedure

Editorial boundary: procedure notes are educational scaffolds unless explicitly tied to authoritative standards, regulator material, service-provider documentation, and aircraft/operator approvals.

Standards and source branch

• SBAS-Standards-Regulation
• SBAS-vs-Other-Standards
• SBAS Source Backlog
• SBAS Standards Source Matrix
• SBAS Core Claim Routing
• SBAS Standards to Operations Evidence Ladder
• SBAS Operational Validation Dashboard
• Source - RTCA DO-229
• Source - ICAO Annex 10 Volume I GNSS SBAS
• Source - ICAO Doc 9849
• Source - RTCA DO-242 — red-flagged as likely mis-scoped for SBAS claims.
• Source - RTCA DO-289 — red-flagged as likely mis-scoped for SBAS claims.
• Source - ICAO Doc 9854 — red-flagged as likely mis-scoped for SBAS technical claims.
• Source - ICAO Doc 9855 — red-flagged as likely mis-scoped for SBAS technical claims.

Priority source work is now direct extraction of the real SBAS standards backbone: Annex 10, official Source - RTCA DO-229 text, Source - ICAO Doc 9849, EASA ETSO material, procedure-design sources, service-provider documents, and operational validation sources. FAA-specific extraction is intentionally skipped in the current core-solidification block.

Regional systems branch

• SBAS-Systems-by-Region-MOC
• WAAS
• EGNOS
• MSAS
• GAGAN
• BDSBAS
• KASS
• SouthPAN
• SDCM
• WAAS vs EGNOS
• MSAS vs GAGAN
• Asia-Pacific SBAS Implementation Patterns

SDCM now exists as a source-routed development-context note. Future regional notes may cover ASECNA and other systems after source support is added.

ASEAN implementation branch

• ASEAN SBAS Adoption Landscape
• ASEAN SBAS Readiness Heuristic
• ASEAN SBAS Operational Demand Drivers
• ASEAN SBAS Deployment Barriers
• ASEAN SBAS Governance and Institutional Actors
• ASEAN SBAS Service-Model Options
• ASEAN SBAS Source Backlog

Country child notes are linked from ASEAN SBAS Readiness Heuristic. Treat country rankings and readiness groupings as cautious synthesis unless supported by country-specific sources.

GIPTA 2.0 source-linked branch

• GIPTA 2.0 MOC
• GIPTA 2.0
• GIPTA 2.0 and ASEAN SBAS Implementation Pathway
• ASEAN SBAS Testbed
• ASEAN SBAS Testbed to Operational Service
• GNSS Analyzer and SBAS Simulator
• GNSS RFI and Spoofing in ASEAN SBAS Deployment
• WRC-27 and GNSS-SBAS Spectrum Protection
• SBAS Non-Aviation Applications

Ionospheric research branch

• GNSS Radio Occultation
• Total Electron Content (TEC)
• Ionospheric Model Validation
• IRI-2020 vs GNSS-RO Indonesia
• SBAS Ionospheric Threat — Empirical Evidence
• Indonesian SBAS ION Paper Iterations

Boundary: GNSS-RO and IRI-2020 work is valuable for threat discovery and research prioritization. It is not itself an operational SBAS correction service or a certified integrity model.

Highest-value next-note targets

1. Directly extract the official text behind Source - ICAO Annex 10 Volume I GNSS SBAS.
2. Directly extract the official Source - RTCA DO-229 text and Source - ICAO Doc 9849.
3. Deepen EASA ETSO/public article-approval routing where receiver approval context is needed; keep FAA-specific extraction out of this cycle unless explicitly requested later.
4. Use SBAS Core Claim Routing, SBAS Service Performance Concepts, and SBAS Operational Validation Dashboard to prevent core concept pages from drifting into operational claims.
5. Deepen service-provider source notes with current performance/service-volume material where official public sources exist.
6. Continue ASEAN source-hardening through SBAS Source Backlog and ASEAN SBAS Source Backlog.

See also

• index
• SBAS-Research-MOC
• SBAS Knowledge Base Editorial and Source Policy
• Institutional SBAS Knowledge Base Upgrade Roadmap