ASEAN SBAS Source Backlog
Purpose
This note tracks the highest-value source notes needed to support the ASEAN SBAS branch.
Boundary:
- This is not itself an authoritative source note.
- It does not verify ASEAN program status.
- It organizes which source stacks should be built first before the ASEAN branch is treated as stronger evidence rather than careful synthesis.
Why this backlog exists
The ASEAN branch now contains:
- regional framing
- governance hypotheses
- operational demand logic
- deployment barriers
- service-model options
- country child notes
What it still lacks is a dedicated source backbone specific to Southeast Asia and the ICAO APAC institutional layer.
Completed local GIPTA source-backbone pass — 2026-05-01
The GIPTA local document stack has now been converted into source scaffolds and linked concept/synthesis notes.
Highest-value GIPTA source anchors now available:
- Source - GIPTA 2.0 Timor-Leste Site Workshop
- Source - GIPTA 2.0 Project Introduction
- Source - ADB ASEAN SBAS Technical Assistance
- Source - ASEAN SBAS Implementation Roadmap GIPTA
- Source - ASEAN SBAS Testbed Development Proposal
- Source - GIPTA GNSS RFI Discussion
- Source - GIPTA WRC-27 Aeronautical Agenda
- Source - Indonesia InaCORS PBN GIPTA Presentation
- Source - Philippines GNSS Status GIPTA
Use GIPTA 2.0 MOC as the navigation hub for this source stack.
Priority 1 — governance and regional-institution sources
1. ICAO APAC GBAS/SBAS implementation forums
- Why this matters: the current ASEAN governance note relies on the claim that the clearest visible regional pathway runs through ICAO APAC structures.
- Current vault usage: ASEAN SBAS Governance and Institutional Actors, ASEAN SBAS Adoption Landscape
- Candidate source note: Source - ICAO APAC GBAS-SBAS Implementation Forums
- Verification need: identify which meetings, task forces, and workshop documents actually mention SBAS/GBAS implementation in ways relevant to ASEAN.
2. APANPIRG / CNS Sub-Group documentation relevant to SBAS
- Why this matters: the governance note currently references APANPIRG and CNS SG as likely decision-shaping layers.
- Current vault usage: ASEAN SBAS Governance and Institutional Actors
- Candidate future note: Source - APANPIRG and CNS SG SBAS References
- Verification need: distinguish broad CNS coordination from documents that actually bear on SBAS implementation planning.
Priority 2 — ASEAN-facing technical feasibility sources
3. Equatorial ionosphere and low-latitude SBAS performance references
- Why this matters: multiple ASEAN notes treat equatorial ionospheric conditions as a central regional issue.
- Current vault usage: ASEAN SBAS Adoption Landscape, ASEAN SBAS Deployment Barriers, ASEAN SBAS Service-Model Options
- Candidate future note: Source - Equatorial Ionosphere and SBAS Feasibility
- Verification need: tie the current heuristic claim to actual technical literature or implementation studies.
4. Asia-Pacific program documents relevant to Southeast Asian adoption questions
- Why this matters: the vault currently uses MSAS, GAGAN, and SouthPAN as comparators; this now has partial source backing but still needs boundary discipline.
- Current vault usage: Asia-Pacific SBAS Implementation Patterns, ASEAN SBAS Service-Model Options
- Current source anchors: Source - WAAS, Source - EGNOS, Source - GAGAN SBAS Operation, Source - MSAS, Source - BDSBAS, Source - KASS, Source - SouthPAN, and Source - ICAO APAC GBAS-SBAS Implementation Forums
- Verification need: separate deployed-system descriptions from documents that actually inform ASEAN service-model thinking; do not transfer operational claims from India/Japan/Australia-New Zealand/Europe/United States/Korea/China to ASEAN without ASEAN-specific implementation evidence.
- Current status: partial source extraction now exists for seven comparator/provider systems: WAAS (FAA WAAS public material), EGNOS (official SoL SDD), GAGAN (ITF/7 IP05b), MSAS (QZSS + CNS SG/24 IP15), SouthPAN (GA/LINZ Open Service definitions), KASS (KARI + ICAO APAC ITF/5), and BDSBAS (official BDSBAS-B1C ICD + bounded technical-public context).
Priority 3 — country-level evidence stacks
5. Country-level PBN and procedure-design readiness references
- Why this matters: the country child notes are intentionally heuristic and need replacement by source-backed evidence over time.
- Current vault usage: ASEAN SBAS Readiness Heuristic plus all country child notes
- Candidate future note: Source - ASEAN Country PBN Readiness Signals
- Verification need: determine which states actually show the strongest evidence of readiness, not just proxy-based plausibility.
- Starter note created: Source - ASEAN Country PBN Readiness Signals
6. Country-level airport access and network-geometry evidence
- Why this matters: the notes for Indonesia and Philippines rely heavily on archipelagic and distributed-network logic.
- Current vault usage: Indonesia, Philippines, ASEAN SBAS Operational Demand Drivers
- Candidate future note: Source - Archipelagic Airport Network Context in ASEAN
- Verification need: ground access claims in aviation-network evidence rather than geography alone.
- Starter note created: Source - Archipelagic Airport Network Context in ASEAN
Claim clusters needing source support
Governance claims
- whether ICAO APAC is in fact the clearest currently visible institutional layer
- whether ASEAN bodies have discussed SBAS directly
- whether coalition-of-willing or APAC-coordinated pathways have been discussed in formal documents
Technical-feasibility claims
- equatorial ionospheric difficulty for Southeast Asian SBAS adoption
- whether neighboring or comparator systems offer directly transferable lessons
- whether SouthPAN’s explicit north-of-20°S ionospheric limitation language should become a cautionary comparator for ASEAN low-latitude service-definition analysis
- whether GAGAN’s Indian ionosphere monitoring/DFO/DFMC-ready upgrade path provides a source-backed comparator for equatorial/low-latitude infrastructure planning without implying transferability
- whether KASS and BDSBAS provide useful Northeast Asian comparator signals for governance, certification, and signal-interface maturity without implying suitability for Southeast Asian service provision
- whether mature WAAS/EGNOS source material is useful mainly as service-definition/authorization-pattern evidence rather than as geographic or operational comparators for ASEAN
Country-readiness claims
- strongest first-mover candidates
- relative PBN maturity
- realistic distinction between high-benefit states and high-readiness states
Early evidence-aware upgrades now underway
- Singapore has initial institutional-readiness support through CAAS website signals
- Indonesia has initial archipelagic-context support through World Bank country-page wording
- Philippines has improved distributed-airport context support through CAAP references to CAAP-operated airports and a quantified nationwide commercial-airport-network signal
- Malaysia has initial PBN-readiness and AIS/governance support through official CAAM pages
- Thailand has initial PBN-readiness support through ICAO APAC reporting paths and a visible CAAT PBN guidance path
Suggested execution order
- Source - ICAO APAC GBAS-SBAS Implementation Forums — partially verified with ITF/7 metadata; next step is full ITF meeting-page/WP extraction.
- Source - APANPIRG and CNS SG SBAS References
- Source - Equatorial Ionosphere and SBAS Feasibility — now should incorporate SouthPAN north-of-20°S limitation signal and GAGAN ionosphere monitoring upgrade signal as comparator evidence, without claiming ASEAN transferability.
- Source - ASEAN Country PBN Readiness Signals
- Source - Archipelagic Airport Network Context in ASEAN
Related notes
- SBAS Source Backlog
- ASEAN SBAS Adoption Landscape
- ASEAN SBAS Governance and Institutional Actors
- ASEAN SBAS Deployment Barriers
- ASEAN SBAS Readiness Heuristic
- Source - ICAO APAC GBAS-SBAS Implementation Forums
- Source - APANPIRG and CNS SG SBAS References
- Source - Equatorial Ionosphere and SBAS Feasibility
- Source - SouthPAN
- Source - MSAS
- Source - GAGAN SBAS Operation
- Source - WAAS
- Source - EGNOS
- Source - BDSBAS
- Source - KASS
- SBAS MOC
- SBAS-Research-MOC
Open questions
- Which ASEAN-facing source note would most quickly convert the governance note from cautious inference to stronger evidence?
- Which country notes should be upgraded first once a source-backed readiness stack exists?
- Which ASEAN claims belong in implementation-report sources versus standards or technical-literature sources?