Why can't we just buy SOTM capacity from a commercial provider like Starlink or Inmarsat?

Commercial operators retain the right to refuse, suspend or geo-fence service under their own terms and home-country law — Starlink's documented restriction of service over Crimea in 2022 is the clearest recent example. A nation that has committed forces to an operation cannot accept that its command link could be switched off by a foreign CEO or foreign government. Owning the constellation removes that veto entirely.

What orbit is right for tactical SATCOM-on-the-move?

LEO (400–1,200 km) is the default: it delivers 18–35 ms latency, requires less transmit power from a vehicle-mounted terminal, and reduces signature compared with a high-gain dish pointing at GEO. The trade-off is that you need enough satellites to guarantee continuous coverage; for a regional power, a 30–60-satellite constellation in polar or inclined orbits typically suffices.

How many satellites does a sovereign constellation actually need?

Coverage analysis for continuous, sub-5-minute revisit at latitudes between 60°S and 72°N typically requires a minimum of 48–72 satellites in multiple orbital planes, based on Walker constellation geometry. A 24-satellite architecture can achieve continuous coverage at lower latitudes but leaves polar and high-latitude gaps that matter enormously for Arctic operations. Nations should model worst-case gap durations before committing to a bus count.

What bandwidth can a vehicle-mounted terminal realistically achieve?

A 60 cm electronically steered array terminal on a moving vehicle can sustain 8–20 Mbps downlink and 2–5 Mbps uplink in a clear-sky LEO link, broadly consistent with NATO STANAG 4677 minimums for a manoeuvre element. Real throughput degrades in rain, under electronic attack, or when the vehicle enters terrain masking such as urban canyons or valleys.

How do we handle handoffs between satellites without dropping calls or data sessions?

Modern LEO SOTM systems use inter-satellite link (ISL) meshing and IP mobility protocols — typically Mobile IP or SCTP multi-homing — so that the network layer maintains sessions across satellite handoffs transparent to the application. The terminal tracks the next satellite before the current one sets below the horizon, pre-establishing the link so the handoff takes under one second. This is a solved engineering problem but requires deliberate system design; buying a commodity terminal without ISL awareness will produce visible dropouts.

Can adversaries detect our vehicles by their SATCOM transmissions?

Yes. Any uplink transmission is an RF emission that can be detected and geolocated by signals-intelligence (SIGINT) satellites or ground receivers — HawkEye 360 publicly demonstrates 5–10 km geolocation accuracy from LEO on emitters in the field. Low-probability-of-intercept (LPI) waveforms, burst transmission, and spread-spectrum techniques reduce but do not eliminate this risk; operational discipline (emission control, EMCON) remains essential.

What is the realistic cost to develop and launch a sovereign military LEO SATCOM constellation?

A 48-satellite Ka/Ku-band military LEO constellation with ground segment and five years of operations is broadly estimated at $1.5–4B depending on satellite mass class, launch vehicle choice, and level of encryption and anti-jam hardening required. Microsatellite approaches (50–150 kg per bus) compress cost toward the lower end; hosted-payload options on existing commercial platforms can shave 20–30% off development costs at the expense of some operational independence.

How do we make our system interoperable with allied SATCOM without losing sovereign control?

The standard architecture is a gateway model: your constellation carries national traffic on sovereign waveforms and encryption, while a dedicated inter-coalition access portal — governed by a bilateral or multilateral COMSEC agreement — allows allied terminals to access a ring-fenced subset of capacity. NATO's Combined Enterprise Regional Information Exchange System (CENTRIXS) and the BICES network follow analogous logic. The key is designing the access-control layer before procurement, not retrofitting it.

7.6.1Live

Tactical SATCOM-on-the-Move

Armored military vehicle with roof-mounted antenna array moving across open terrain during a field operation — Colombian armored forces in operation demonstrate the critical need for reliable satellite connectivity to coordinate mobile military missions.

Satellite Connectivity for Forces on the Move

1
Satellite Constellation
GEO or LEO relay, Ku/Ka-band
2
SOTM Downlink
Steerable phased-array antenna on vehicle
3
Tactical Edge Node
Onboard router encrypts, prioritises traffic
4
Commander & Crew
Live ISR feeds, voice, situational maps

A vehicle-mounted phased-array antenna tracks the satellite continuously, delivering encrypted voice, data, and intelligence feeds to troops without halting movement.

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 battlefield connectivity

7.6.2 · Next

Forward-Deployed Networks

Bring this into your sovereign programme.

All solutions Speak with engineering