2.2.5 — Aviation Navigation — maturity: live
Aviation Safety Monitoring
Continuous satellite-based surveillance of aircraft position, distress signals, and airspace anomalies to prevent mid-air collisions and accelerate emergency response.
When an aircraft deviates, depressurises, or loses contact, space-based safety monitoring is the layer that sees it first — and sovereign nations cannot afford to depend on someone else's eyes.
National aviation authorities are accountable for every aircraft in their airspace, yet radar coverage collapses over oceans, deserts, and mountainous terrain. When a flight deviates, declares an emergency, or simply goes silent, controllers relying on ground-based systems are blind. Satellite-based ADS-B reception, emergency locator transmitter (ELT) detection, and RF anomaly monitoring close that gap, giving authorities continuous positional awareness regardless of geography.
A sovereign LEO constellation augments — and in remote regions replaces — ground radar by collecting ADS-B-Out transponder data from aircraft at all altitudes, detecting 406 MHz Cospas-Sarsat ELT activations with sub-10-minute latency, and cross-checking RF signatures for spoofing or transponder manipulation. Onboard processing filters raw messages before downlink, reducing ground-segment bandwidth and enabling near-real-time alerting. The payload suite can also monitor VHF datalink (VDL Mode 2) and ACARS to detect abnormal message gaps that precede incidents.
The operational outcome is an always-on safety net that a national air navigation service provider (ANSP) controls end-to-end. Incident timelines compress from hours to minutes: search-and-rescue assets receive a precise last-known position within one orbital pass rather than waiting for a maritime patrol aircraft to sweep a search box. Crucially, that data never transits a foreign aggregator whose access policies, outage windows, and pricing terms are outside the state's control.
Frequently asked
Why can't a nation just buy Aireon data and call it done?
Aireon provides excellent global coverage, but buying data-as-a-service means accepting the vendor's terms, data latency, and access policies — including potential denial or throttling during a conflict or sanctions regime. Sovereign operation means the raw signals land in your own ground station, processed by your own software, with no intermediary who can switch you off. For a nation managing its own FIR (Flight Information Region), that distinction is operationally decisive.
What orbit should a national aviation safety constellation use?
Low Earth orbit (LEO), specifically 780–850 km inclined orbits, is the standard — it provides the geometry needed to receive 1090 MHz ADS-B uplinks at useful signal-to-noise ratios while keeping revisit times under 10 seconds. A constellation of 6–12 microsatellites in complementary planes can achieve continuous coverage over a single Flight Information Region, scaling to global coverage at 60–80 spacecraft. GEO is unsuitable: path loss at 35,786 km makes 1090 MHz reception from unmodified aircraft transponders impractical.
Can one constellation serve both safety monitoring and search-and-rescue alerting?
Yes, and it should. The Cospas-Sarsat MEOSAR/LEOSAR frequencies (406 MHz distress beacons) can be hosted as a secondary payload alongside ADS-B receivers on the same microsatellite bus. Nations including France, the US, and India already fly combined payloads. A dual-mission design shares launch and operations costs and gives a sovereign state direct access to distress-beacon data over its territory without routing through another country's mission control.
What is the minimum viable constellation for a mid-sized nation's FIR?
Analysis by ICAO's SITAONAIR and Aireon data suggests that for a FIR the size of Australia's oceanic region (~11 million km²), continuous coverage with sub-10-second updates requires approximately 6–8 satellites in two complementary LEO planes. A phased deployment — starting with 3 satellites for partial coverage — reduces upfront capital while the regulatory and ground-segment work matures. Microsatellite buses in the 50–150 kg class are sufficient to host the required payload.
How does space-based ADS-B improve search and rescue response times?
Before global space-based ADS-B, an aircraft that disappeared over ocean could only be localised to a 30-minute positional corridor — the area it could have reached from its last voice report. Aireon's deployment in 2019 demonstrated that space-based ADS-B compresses the last known position uncertainty to under 1 nautical mile at 8-second update rates. For MH370-type events, this means search areas shrink from hundreds of thousands of square kilometres to tens, potentially saving weeks of search time and hundreds of millions in SAR costs.
What ground infrastructure does a sovereign constellation need?
At minimum: one or two ground stations with S-band or UHF command/telemetry links, a data processing centre capable of ADS-B demodulation and track fusion, and a secure interface to the national Air Navigation Service Provider (ANSP) and the regional ICAO ADS-B ground network. Nations with existing space infrastructure (e.g., an earth-observation ground station) can repurpose significant elements. The data processing software stack is available under open or commercial licence from vendors such as Spire Global and Unseenlabs.
How do we handle aircraft that cross from our FIR into a neighbour's — do we lose the track?
No, not if the constellation design covers adjacent regions and data-sharing agreements exist. ICAO encourages bilateral and multilateral data-sharing under its Global Aeronautical Distress and Safety System (GADSS) framework. A sovereign constellation can provide data to neighbours via standard ATS message formats (ASTERIX Cat. 21), maintaining track continuity through FIR boundaries. This actually creates diplomatic leverage: your data becomes something neighbours value, reinforcing cooperative relationships.
What cybersecurity risks apply to space-based safety data, and how are they mitigated?
The primary risks are: spoofed ADS-B signals injected into the satellite uplink, interception of the satellite downlink, and intrusion into the ground processing centre. EUROCAE ED-129B and RTCA DO-260C outline signal authentication approaches currently under development. Sovereign operators should encrypt the satellite-to-ground downlink (CCSDS-standard AES-256), operate the processing centre on an air-gapped or tightly firewalled network, and cross-validate space-derived tracks against independent data sources (radar, MLAT) to detect anomalous injection.