Why can't my country simply buy maritime surveillance data from a commercial provider like Planet or Spire instead of building its own satellites?

Commercial providers operate under the laws of their home jurisdiction and can be directed by that government to suspend, degrade or re-price services during a geopolitical crisis — precisely when a chokepoint nation needs the data most. Sovereign ownership means the tasking schedule, the raw data and the analytic pipeline remain under national control with no counterparty risk. The upfront capital cost is higher, but the strategic optionality is qualitatively different.

What orbit and sensor combination is most effective for chokepoint surveillance?

A mixed LEO constellation of SAR microsatellites (for all-weather, day/night imaging) paired with RF-geolocation payloads (to detect non-broadcasting or spoofing vessels) is the workhorse architecture. GEO is generally too low a resolution for individual vessel identification. A 12-to-24 satellite LEO constellation at 500–600 km altitude with inclinations tuned to the chokepoint latitudes delivers sub-30-minute average revisit and can be supplemented with S-AIS receivers at marginal additional cost per satellite.

Is satellite-based AIS reliable enough to track every vessel passing a chokepoint?

Space-based AIS (S-AIS) captures the vast majority of compliant vessels but has two structural weaknesses: vessels can switch off their transponders, and bad actors increasingly spoof position data. ITU-R M.1371-5 governs AIS technical characteristics but cannot enforce compliance. A credible sovereign capability layers S-AIS with SAR imagery and RF-geolocation (as demonstrated commercially by HawkEye 360) to detect dark vessels and flag positional inconsistencies.

How does a sovereign chokepoint surveillance constellation integrate with international maritime law frameworks?

Satellite-derived imagery and signals intelligence support, but do not replace, enforcement actions governed by UNCLOS (particularly Articles 17–26 on innocent passage, Article 58 on EEZ rights, and Article 110 on the right of visit). The data a sovereign constellation generates provides actionable grounds for flag-state notifications through IMO channels or bilateral arrangements; it does not itself confer interdiction authority. Nations must also comply with ITU Radio Regulations for payload frequency use.

What is the realistic build-and-launch timeline and cost for a minimum viable chokepoint surveillance constellation?

A minimum viable constellation of 6–8 SAR microsatellites with integrated S-AIS and RF-geolocation payloads can realistically be designed, built and launched within 3–5 years from programme start, at a total mission cost in the range of $150M–$400M depending on domestic versus foreign industrial content and launch vehicle selection. A follow-on replenishment tranche every 5–7 years is needed to maintain coverage as satellites age. ESA's Φ-sat and ICEYE's fleet economics provide useful public benchmarks.

Can a small or mid-sized nation afford this, or is it only viable for large maritime powers?

Cost-sharing consortia — analogous to the EUMETSAT model for meteorological satellites — allow groups of chokepoint-adjacent nations (e.g., Red Sea littoral states or ASEAN members) to jointly procure and task a constellation while each retaining sovereign access rights to data covering their own waters. The World Bank's PROBLUE programme and regional development banks have also begun financing maritime domain awareness infrastructure as a public good, reducing the capital burden on individual states.

How do we handle the cyber and information-security dimension of the data this constellation produces?

Surveillance data from this type of constellation is operationally sensitive and in some cases classifiable; it must be handled under a ground-segment security architecture consistent with NIST SP 800-53 (for nations aligned with US frameworks) or equivalent national standards. IMO MSC.428(98) mandates cyber-risk management in safety management systems but does not cover intelligence-grade satellite ground segments. Nations should design ground stations with air-gapped analytic enclaves and strict need-to-know access controls from day one.

What happens to surveillance coverage during a satellite failure or anti-satellite threat?

Constellation resilience is a core design requirement, not an afterthought. A sovereign operator should design for N+2 redundancy at minimum — meaning two satellite failures in the worst-case orbital plane should not degrade coverage below an agreed threshold. On-orbit sparing, rapid-replenishment launch agreements and graceful-degradation operating procedures (prioritising the highest-risk chokepoint segments) are standard practice in defence-grade mission design following ECSS standards published by ESA.

4.6.5Live

Strategic Chokepoint Surveillance

Coast guard officers in a control room watching radar screens tracking ships through a narrow maritime chokepoint — Satellite monitoring of container ships and oil tankers at busy sea bridges helps secure vital global trade corridors.

Satellite Watch Over Strategic Maritime Chokepoints

1
SAR & AIS Constellation
Detects vessels day, night, all weather
2
Ground Station Downlink
Raw imagery and AIS burst data received
3
Fusion & Anomaly Detection
AI flags dark vessels, spoofing, loitering
4
Maritime Operations Centre
Commanders receive real-time chokepoint picture

Radar satellites and AIS receivers fuse data to expose unlawful or suspicious vessel movements through critical global chokepoints.

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

4.6.4 · Previous

Smuggling Route Intelligence

All in maritime security

4.6.6 · Next

Yacht & Marine Recreation Tracking

Bring this into your sovereign programme.

All solutions Speak with engineering