SBAS Systems by Region MOC

Scope

This note maps regional SBAS systems and system-comparison research. It is a navigation and synthesis page, not a certified service-performance table.

Exact system status, coverage, performance, service levels, satellite payloads, procedure publication, and operational approvals must be checked against current service-provider, regulator, standards, and AIP/procedure material before use in formal analysis.

Primary regional system notes

SystemRegion / roleCurrent noteDedicated source noteSource posture
WAASUnited States / North America reference systemWAASSource - WAASOfficial FAA public WAAS material extracted; deeper status/performance/procedure evidence still required
EGNOSEurope reference systemEGNOSSource - EGNOSOfficial EGNOS SoL SDD material extracted; national authorization/AIP evidence still required
MSASJapan / Asia-Pacific comparatorMSASSource - MSASOfficial QZSS and ICAO APAC material extracted; current post-2023 LPV status still bounded
GAGANIndia / low-latitude regional comparatorGAGANSource - GAGAN SBAS OperationICAO APAC ITF/7 and AAI GEO FAQ extracted; exact service performance/procedure minima still bounded
BDSBASChina / BeiDou-linked Asia-Pacific comparatorBDSBASSource - BDSBASOfficial BDSBAS-B1C ICD extracted; CAAC aviation service/procedure evidence still required
KASSRepublic of Korea / Northeast Asia comparatorKASSSource - KASSKARI, ICAO APAC ITF/5, and bounded contractor-public certification signals extracted; Korean regulator/AIP evidence still required
SouthPANAustralia and New Zealand / early Open Services comparatorSouthPANSource - SouthPANOfficial GA/LINZ open-service and SIS Open Services material extracted; certified aviation SoL/AIP evidence still required
SDCMRussia / GLONASS augmentation research targetSDCMSource - SDCMGLONASS/IAC and historical ICAO development-context evidence extracted; current aviation operational evidence still required

Future source-backed notes may cover ASECNA and other SBAS or SBAS-like programs. Until dedicated notes exist, those systems should be discussed as candidate research targets rather than as completed source-routed pages.

Comparison and synthesis notes

ASEAN relevance

ASEAN does not currently appear in this knowledge base as a single deployed regional SBAS equivalent to WAAS or EGNOS. The ASEAN branch is instead an implementation-planning branch focused on readiness, governance, barriers, demand, source evidence, and service-model choice.

The system notes above should be used as bounded comparator evidence only. Do not transfer operational claims from WAAS, EGNOS, MSAS, GAGAN, BDSBAS, KASS, or SouthPAN into ASEAN planning without ASEAN-specific institutional, service-model, regulator, and implementation evidence.

Start with:

How to compare systems responsibly

Regional SBAS systems should not be compared only by headline accuracy or coverage numbers. A high-quality comparison should separate:

DimensionWhy it matters
Service definitionDefines what the provider claims and for which users
Aviation approval statusDetermines whether signals support actual operations
Coverage and geometryIndicates where service may be usable, not necessarily where procedures exist
Integrity conceptDetermines safety-relevant usability
Procedure inventoryShows where operational benefits are actually available
Aircraft equipageDetermines who can use the procedures
Regulatory environmentDetermines approval and oversight pathway
Ionospheric environmentEspecially important for low-latitude and equatorial regions
Institutional modelDetermines who operates, funds, monitors, and governs the service
Source maturityPrevents unsourced comparisons between systems with unequal evidence depth

Source posture

The current major-system layer now has first-layer dedicated source notes for WAAS, EGNOS, MSAS, GAGAN, BDSBAS, KASS, SouthPAN, and SDCM. SDCM is intentionally marked as development-context / GLONASS-source-posture evidence, not current operational aviation evidence.

Use SBAS Operational Validation Dashboard before upgrading any system page from service-provider/source-context evidence to operational aviation claims.

That does not mean the systems are fully verified for operational use. Priority source families still include:

  • service-provider definition documents and performance reports;
  • regulator and ANSP operational approval material;
  • AIP/procedure publications for airport/runway-specific claims;
  • ICAO APAC and regional planning documents;
  • RTCA/EUROCAE/ICAO standards scaffolds in SBAS Source Backlog;
  • ASEAN and GIPTA-specific source stacks in ASEAN SBAS Source Backlog and GIPTA 2.0 MOC.

Research priorities

  1. Deepen service-provider source notes with performance, service-volume, and status documents where official public sources exist.
  2. Verify each operational procedure claim against regulator/ANSP/AIP sources.
  3. Separate technical service availability from published aviation procedure availability.
  4. Deepen Asia-Pacific comparator evidence for ASEAN planning.
  5. Use SBAS Operational Validation Dashboard before upgrading service-provider/source-context claims into operational aviation statements.

See also