Why can't we just use Starlink or Iridium and rent the capacity rather than build our own satellites?

Renting capacity from a foreign commercial operator means mission data, command traffic, and vehicle locations transit infrastructure you do not control and cannot audit. In a security-sensitive deployment — pipeline inspection, submarine cable survey, naval mine countermeasures — a nation's adversary could request, and in some jurisdictions legally compel, that operator to intercept or deny service. Owning the relay constellation closes that exposure entirely.

What orbit type is best for AUV relay satellites?

LEO (400–600 km altitude) gives the shortest round-trip latency and highest link budget for the small Ku- or Ka-band terminals that fit on an uncrewed surface relay node. A constellation of 18–24 microsatellites in two polar-inclined planes achieves sub-60-minute revisit globally, which is sufficient for supervised-autonomy operations where the AUV runs a pre-loaded mission plan and surfaces for command updates at intervals.

What does the IMO say about autonomous underwater vehicles?

IMO's current MASS Code and its predecessor MSC-MEPC.2/Circ.10 address Maritime Autonomous Surface Ships only; AUVs fall outside that framework. IMO's Maritime Safety Committee has noted the gap (MSC 105, 2022) but has not yet issued binding guidance. Nations operating AUVs commercially or militarily currently rely on flag-state discretion, which is why sovereign legal clarity — backed by sovereign infrastructure — matters.

How does an AUV actually receive satellite commands if it is underwater?

It doesn't — directly. The standard architecture is a surface relay node (an uncrewed surface vehicle or anchored buoy) that maintains an acoustic link downward to the AUV and a satellite link upward to a ground control station. The relay node acts as a protocol converter, buffering commands and telemetry across the speed and latency mismatch between the acoustic and radio links.

How deep can AUVs operate and does depth affect the satellite control chain?

Commercial AUVs such as the Kongsberg Hugin operate to 6,000 m. Depth affects the acoustic link — attenuation increases and reliable bandwidth decreases with range to the surface relay. The satellite link is entirely unaffected by depth; the constraint is acoustic physics, not space-segment design. This is why sovereign programmes focus on improving acoustic modem performance alongside satellite capacity.

Is a constellation of 18–24 nanosatellites enough, or do we need hundreds?

For AUV relay, you need duty-cycle coverage — the AUV surfaces or uses a surface relay periodically, not continuously. A 24-satellite LEO constellation in two polar planes provides a contact window every 45–90 minutes at mid-latitudes, which is adequate for supervised-autonomy missions. Continuous real-time teleoperation would require a much larger constellation, but that operational model is inappropriate for subsea work given acoustic latency anyway.

What are the cybersecurity risks, and how does sovereign ownership help?

The command link to an AUV is a high-value target: a spoofed command could cause a vehicle to surface in the wrong location, flood a buoyancy chamber, or transmit false survey data. End-to-end encryption is standard, but the key management chain must be sovereign — if your encryption certificates are issued or can be revoked by a foreign commercial entity, you do not truly control the vehicle. A nationally owned constellation, operated under national PKI, closes that chain.

What data volumes are we talking about, and does that affect satellite sizing?

A typical AUV survey mission generates 10–50 GB of raw acoustic, optical, and sensor data per sortie. This is almost never transmitted in real time — it is offloaded at surface or port. The satellite link carries only command, status, and compressed alert data, averaging well under 1 Mbps. This means a modest LEO microsatellite with a 100 Mbps Ka-band payload is vastly oversized for AUV relay alone; the same satellite bus can simultaneously serve surface vessel AIS, environmental monitoring, and coastal surveillance applications.

4.7.3Soon

Autonomous Underwater Vehicle Control

Scientists on a research vessel lowering a yellow torpedo-shaped autonomous underwater vehicle into open ocean water — An oil tanker at sea illustrates the vast maritime routes where satellite-guided autonomous vehicles monitor underwater infrastructure.

Satellite Links Guiding Autonomous Underwater Vehicles

1
Satellite Constellation
GPS and Iridium relay positioning signals
2
Surface Gateway
Buoy or vessel receives, forwards commands
3
Mission Control
Operators update AUV waypoints and tasks
4
AUV Operations
Vehicle navigates, surveys, transmits data

Satellite signals reach a surface gateway that relays updated mission commands to autonomous underwater vehicles operating at depth.

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: Demonstrators flown or funded; service expected inside 36 months. 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.7.2 · Previous

Uncrewed Surface Vehicle Coordination

All in autonomous maritime systems

4.7.4 · Next

Remote Vessel Operation Centres

Bring this into your sovereign programme.

All solutions Speak with engineering