Why can't a government just buy commercial satellite backhaul from Starlink or Inmarsat during a disaster?

Commercial providers can terminate, reprice, or deprioritise government traffic under their own service terms, without notice, and several have done so during geopolitical crises. A sovereign government needs a contractual — ideally a physical — guarantee that capacity exists at the moment of need. Owning the constellation means the government sets the priority queue, not a foreign board of directors.

What throughput does an emergency backhaul satellite actually need to deliver?

UNHCR and ITU field studies suggest a minimum of 2 Mbps per active response cell site for voice and basic data, rising to 50 Mbps for a field hospital with telemedicine. A modern LEO microsatellite can provide 150–400 Mbps aggregate to a footprint; the design challenge is the number of simultaneous ground terminals competing for that capacity, not raw throughput.

How many satellites does a sovereign emergency backhaul constellation realistically need?

For continuous national coverage with one active satellite in view at all times, a mid-inclination LEO constellation requires roughly 6–12 satellites depending on the country's latitude and geographic size. Nations like Australia or Canada with extreme north-south extents may need 18–24 to guarantee sub-15-minute revisit. These figures assume 500–600 km altitude and modest beam-steering payloads.

How does satellite backhaul interact with Cell-on-Wheels (CoW) deployments?

A CoW provides a mobile LTE or 5G radio access network on the ground, but it is a radio island unless it has a backhaul link to the core network. Satellite backhaul is the standard solution: the CoW's router connects to a VSAT terminal, which uplinks to the satellite and onwards to an intact terrestrial point of presence. Without the satellite link, a CoW serves only voice calls within its own cell — no data, no external calls.

Can the same sovereign constellation serve routine commercial purposes outside disaster periods?

Yes, and it should. A constellation that only activates in emergencies will have outdated software, untested firmware, and rusty operations teams when it is needed most. Dual-use architectures — where the same satellites carry IoT, broadband, or government data traffic in peacetime — keep the system operationally current and defray operating costs, provided capacity-reservation agreements guarantee disaster-priority preemption.

What ground infrastructure does a sovereign programme need on top of the satellites?

At minimum: two geographically separated gateway earth stations (for redundancy), a satellite operations centre, a network operations centre, a pre-positioned stock of at least 200–500 deployable terminals, and a trained logistics and rapid-deployment unit. The ground segment typically costs 40–60% of total programme cost and is the component most often under-budgeted in early feasibility studies.

What regulatory approvals are needed to operate emergency satellite backhaul?

The operator must secure ITU frequency coordination for both the space and earth stations under the Radio Regulations, national spectrum licensing in every country where ground terminals will be deployed, and export control clearances if foreign-manufactured satellite components are used. In disaster scenarios, the ITU Resolution 646 framework allows expedited temporary spectrum use, but the underlying coordination must be completed in advance — it cannot be done in real time during a crisis.

How long does it take to build and launch a sovereign emergency backhaul constellation?

From programme authority to first operational satellite, realistic timelines range from 4 to 7 years for a first-time sovereign operator, including procurement, integration, testing, launch, and ground-segment commissioning. Nations that partner with established small-satellite integrators (e.g. using standard microsatellite bus platforms) can compress this to 3–5 years. Phased deployment — launching a partial constellation first — is strongly recommended to accelerate early operational capability.

6.7.1Live

Emergency Satellite Backhaul

Emergency relief workers setting up a portable satellite dish antenna at a disaster response camp — Volcanic eruption smoke mirrors the sudden communications blackouts satellite backhaul systems are built to overcome.

Satellite Backhaul Restoring Disaster Zone Connectivity

1
Satellite Constellation
LEO/GEO birds relay emergency traffic
2
Ground Gateway
Teleport links satellite to public internet
3
Deployable Terminal
VSAT dish at incident command post
4
Field Teams
Voice, data, video restored within hours

A satellite link bridges destroyed ground infrastructure, giving disaster responders reliable voice and data within hours of deployment.

Page in the build queue

This application has its place in the atlas. The full page — short and long descriptions, what-matters bullets, sovereignty rationale, and the eight-field architecture block — is being written next.

Maturity reading: Operational systems exist with paying customers. Phase 1 built §4.1 (Maritime Intelligence) end-to-end as the depth-and-format reference. Section 4 is the next section to graduate from scaffold to full content; the rest follow on the roadmap.

Related applications

All in disaster communications

6.7.2 · Next

Cell-on-Wheels Coordination

Bring this into your sovereign programme.

All solutions Speak with engineering