When an earthquake, cyclone or flood strikes, the first casualty is usually the communications grid. Cell towers fall, fibre cuts, power fails, and the agencies that most need to coordinate — civil defence, medical services, military engineers — are suddenly isolated from each other and from national command. The window in which that silence kills people is measured in hours, not days.
A sovereign LEO constellation changes the equation the moment the disaster occurs. Nanosatellites carrying L-band narrowband and VHF/UHF bent-pipe payloads pass overhead every 30–90 minutes, providing store-and-forward messaging and, in a denser constellation, near-continuous voice and low-rate IP to handheld terminals that fit in a field responder's vest pocket. No ground repeater, no fixed gateway, no foreign operator approval required — just a clear view of the sky.
The operational outcome is that the incident commander at a collapsed building and the logistics officer at a field hospital 200 km away are on the same network within minutes of a pass. Damage assessment data, survivor location pings and resource requests flow on the same links. Nations that depend on foreign commercial constellations for this capability have learned, repeatedly, that service prioritisation, export controls and crisis-driven congestion make those links unreliable precisely when reliability is non-negotiable.
Frequently asked
Why can't a government just purchase airtime from a commercial operator like Starlink or Iridium during a disaster?
Commercial operators can throttle, reprioritise, or withdraw service under their own terms of service, foreign export-control regimes, or commercial pressure — exactly when a government needs guaranteed access most. A sovereign system means the government controls prioritisation, encryption, and service continuity. Dependence on a foreign commercial provider also exposes sensitive command-and-control traffic to a third party's jurisdiction.
What orbit should a disaster communications constellation use?
LEO (400–1,200 km) is the right default: latency of 20–40 ms is compatible with voice and video coordination, link budgets are far smaller than GEO, and a constellation of even 12–24 microsatellites can cover a nation's territory with acceptable revisit. GEO is not ideal because a single point of failure covers everything or nothing, and link-budget demands make cheap user terminals impractical for widespread field deployment.
How many satellites does a nation actually need to guarantee continuous coverage?
Continuous single-satellite coverage of a mid-latitude nation (roughly 40°N to 40°S) typically requires a minimum of 20–30 small satellites distributed across 3–6 orbital planes. A 6-satellite starter constellation offers useful but intermittent coverage — adequate for scheduled data relay but not for real-time voice coordination. Nations should plan for phased build-out rather than waiting for full constellation funding.
How does a sovereign disaster communications satellite integrate with COSPAS-SARSAT?
COSPAS-SARSAT is an intergovernmental programme (operated by agencies including NOAA, the Russian Space Agency, ESA, and the Indian Space Research Organisation) that detects 406 MHz distress beacons from aircraft, ships, and personal locator beacons. A sovereign LEO constellation can host compatible repeater payloads, feeding alerts into the national Mission Control Centre and directly into the global COSPAS-SARSAT network. This piggyback approach delivers search-and-rescue alerting with minimal additional payload cost.
What role do nanosatellites and microsatellites play versus traditional large satellites?
Nano- and microsatellites (1–100 kg) have democratised the sector: launch costs per kilogram have dropped from roughly $54,000/kg on the Space Shuttle to under $3,000/kg on dedicated rideshare missions. For disaster communications, this means a government can field a constellation incrementally, replace failed units quickly, and refresh technology every 5–7 years rather than operating a single large satellite for 15 years. The trade-off is smaller antenna aperture and lower power, which constrains throughput per satellite.
How long does it take to build and launch a sovereign disaster communications constellation?
A well-funded national programme using proven commercial smallsat platforms and existing ground infrastructure typically takes 4–6 years from programme authorisation to initial operational capability. Spectrum coordination with the ITU is often the longest-lead item. Nations with existing space agencies and ground networks (e.g., ISRO in India, KARI in South Korea) have consistently achieved faster timelines than those starting from scratch.
What cybersecurity standards govern satellite-based emergency communications?
There is no single mandatory global standard, but the ITU-T X.800 series, NIST SP 800-53, and the European Space Agency's ECSS-E-ST-70-41C space-communications security standard all provide applicable frameworks. The IMO resolution MSC.428(98) requires maritime operators to embed cyber risk management in their safety management systems, which extends to satellite-dependent GMDSS equipment. Nations should mandate end-to-end encryption and authenticated command uplinks as minimum baselines.
Can a sovereign disaster communications constellation also serve day-to-day civilian broadband, or should it be dedicated?
Dual-use architectures are common and financially sensible: leasing spare capacity to government agencies, remote schools, or rural health clinics during non-disaster periods generates revenue that can offset operational costs and keeps ground infrastructure and trained operators in continuous use. The risk is that commercial traffic loads may complicate rapid surge reprioritisation when a disaster strikes, so quality-of-service contracts and pre-emption rules must be hard-coded at the network level.