Undersea cable and pipeline corridor monitoring

Space-based AIS and SAR surveillance watches the sea surface above critical subsea corridors, detecting vessel loitering and anchor-drag events before the cable or pipeline is already gone.

The dependence this ends: Finding out when the cable stops working

The damage happens before the alarm sounds

The standard sequence is familiar to every communications ministry and energy regulator that depends on undersea infrastructure: the service degrades, engineers investigate, a repair vessel is dispatched weeks later, and only then does anyone establish whether the break was accidental or deliberate. By that point, the question is academic. The cable is cut. The pipeline is breached. The disruption has already run its course.

Post-2022, the threat environment has sharpened considerably. The sabotage of the Nord Stream pipelines in September 2022 and the repeated Baltic cable incidents in 2023 and 2024 confirmed what maritime security analysts had argued for years: subsea infrastructure is exposed, and the surface activity that precedes an incident is often detectable if anyone is watching. Most governments are not watching systematically. Space-based surface surveillance changes that calculus, not by reaching through the water column, but by monitoring what happens above it.

What the mission actually monitors, and what it cannot

This mission watches the sea surface above defined corridor zones. It does not image the seabed, measure cable integrity directly, or detect divers. Those limits matter and should be stated plainly at the outset.

Space-based AIS receivers collect vessel identity and position broadcasts from ships carrying Class A or Class B transponders. Correlation against SAR imagery identifies vessels that are present but not broadcasting, the so-called dark ships that have switched off or spoofed their AIS signal. C-band SAR can detect vessels down to roughly 50 to 100 metres in length under most sea states, with detection probability falling in high sea states or for very small craft. RF signal-mapping payloads can detect active radar and communication emissions from vessels that are otherwise electronically quiet. Together, these three sensor types create overlapping coverage that is considerably harder to evade than any single layer.

The mission produces alerts, not verdicts. A vessel loitering for six hours directly above a cable route with AIS switched off is a significant indicator. It is not proof of intent. The alerting workflow must be designed with that ambiguity explicit, feeding into a maritime authority or coastguard response rather than an automated enforcement action. False positives will occur, particularly in busy fishing grounds that happen to overlay corridor routes. Revisit cadence matters: a pathfinder configuration with two to three satellites may achieve corridor passes every four to six hours, which is sufficient to characterise loitering but may miss a fast-moving anchor-drag event entirely.

The ambition ladder: pathfinder to operational constellation

A pathfinder programme, typically one or two satellites carrying AIS receivers and a SAR payload, establishes the surveillance baseline and validates alert thresholds against real corridor traffic. Small-satellite SAR missions of this class have publicly reported development and launch costs in the low to mid tens of millions of dollars, based on programmes such as ICEYE's early constellation builds and NovaSAR-1, which was developed for approximately £21 million according to published UK Space Agency records. A pathfinder is not operationally continuous. It demonstrates the detection logic, trains the analysis team, and produces the evidence base needed to justify a full programme to a finance ministry.

An operational constellation requires a minimum of four to six satellites to achieve revisit intervals short enough to characterise loitering with confidence across multiple corridor zones simultaneously. Ground infrastructure must be in-country: a receiving station, a processing node, and an alerting interface connected to the maritime operations centre. At this level, the programme is genuinely sovereign. The satellite tasking, the raw data, and the alert outputs do not transit a foreign commercial platform. That matters for corridors that are themselves classified infrastructure.

There is no constellation tier beyond this for most buyers. Unlike broadband or PNT missions, subsea corridor monitoring does not require global coverage. It requires persistent, high-confidence coverage of a defined set of routes, which a modest constellation can deliver.

What the customer owns at handover

The handover package for this mission is specific. The customer receives the satellites themselves, with full source-access terms for the software defined payloads agreed before contract signature. They receive the ground station, the in-country processing node, and the alert management interface. They receive trained operators: the people who can task the satellites, interpret SAR imagery, run AIS-dark-ship correlation, and manage the alert queue without external assistance.

Audit rights over the hardware supply chain are agreed upfront. This is not a courtesy. For a mission whose explicit purpose is detecting interference with national infrastructure, a buyer has every reason to know what is inside the payload stack.

What remains with Satellize after handover is the ongoing engineering relationship the customer chooses to maintain. Software updates, anomaly resolution, and payload reconfiguration are available under a separate support arrangement. They are not a condition of continued operation. A fully handed-over programme can be operated independently. That is the point.

Integrating the alert into a response

The satellite layer is only the detection element. An alert that a dark vessel has been loitering above a cable corridor for eight hours is useful only if it reaches a maritime patrol authority in time to act. Designing the alerting workflow, the thresholds, the escalation paths, and the interface to coastguard or naval operations is as consequential as the satellite design itself.

In-country processing is not optional for this mission. Routing raw SAR data to an offshore cloud platform for analysis introduces latency, creates a dependency on commercial terms that can change, and raises classification concerns for corridors that governments would prefer not to advertise. Processing sovereign data on sovereign infrastructure, with sovereign-trained analysts making the call, is the architecture this mission is built around.

What this mission is built from

Space-based AIS receivers: Collects vessel identity and position broadcasts over corridor zones, forming the baseline traffic picture against which dark-ship anomalies are identified.
C-band SAR payloads: Provides all-weather, day-night radar imaging of the sea surface to detect vessels not broadcasting AIS, with detection capability down to approximately 50 to 100 metres vessel length under typical sea states.
RF signal-mapping payloads: Detects active radar and communication emissions from vessels that are otherwise electronically quiet, adding a third detection layer that is independent of AIS or optical visibility.
In-country data processing: Runs AIS-SAR correlation, dark-ship detection logic and loitering-alert generation on sovereign infrastructure, keeping raw sensor data and alert outputs within national jurisdiction.

What you end up owning

One or more satellites with AIS, SAR and RF payloads, with source-access terms and hardware audit rights agreed before signature
In-country ground receiving station sized to the corridor coverage requirement
In-country processing node running the correlation and alert-generation software
Alert management interface connected to the national maritime operations centre
Trained national operator team capable of independent satellite tasking, imagery interpretation and alert management
Full data sovereignty: raw sensor data and alert outputs remain within national jurisdiction

Handover proceeds in stages: the national team shadows Satellize engineers through the first operational period, takes primary responsibility for tasking and alert management during a parallel-run phase, and assumes full independent operation at a defined programme milestone. After handover, Satellize retains no standing access to the satellite systems or data. Ongoing engineering support is available under a separate arrangement at the customer's discretion.

Programme parameters

Pathfinder configuration	1 to 2 satellites carrying AIS receiver and C-band SAR payload, arranged and integrated with launch and bus partners
Operational constellation	4 to 6 satellites for persistent corridor coverage across multiple defined routes
Orbit	Low Earth orbit, 500 to 600 km, sun-synchronous preferred for SAR illumination geometry
Corridor revisit (pathfinder)	Approximately 4 to 6 hours per corridor pass; insufficient to catch fast anchor-drag events reliably
Corridor revisit (constellation)	1 to 2 hours per corridor pass across defined zones, depending on corridor latitude and satellite phasing
SAR vessel detection floor	Approximately 50 to 100 metres vessel length under sea states up to Beaufort 5; detection probability falls for smaller craft and higher sea states
Ground infrastructure	1 in-country receiving station, 1 in-country processing node, interface to national maritime operations centre
Operator team to sustain	Typically 4 to 8 trained national operators for a pathfinder; 8 to 16 for a full constellation programme
Pathfinder timeline	18 to 36 months from contract to first operational pass, depending on payload heritage and launch availability
Constellation build timeline	36 to 60 months from contract to full operational capability

Sources

One contract, one accountable engineer

Commissioned as one programme, not a stack of contracts: spacecraft, launch, ground segment, mission control, training and handover are priced together. Source-access terms and audit rights are agreed in writing before signature. Request a corridor-coverage assessment.