An EEZ is a legal construct that only becomes real when a state can see what is happening inside it. Most coastal nations — even mid-sized ones — lack the patrol vessel hours, maritime patrol aircraft and shore-based radar to cover their full 200 nm zone with anything approaching continuity. The result is a surveillance gap that foreign fishing fleets, illegal transshipment operations and state-sponsored survey vessels exploit routinely and with near-impunity.
A layered satellite stack closes that gap. Wide-swath synthetic aperture radar (SAR) detects vessels in all weather and at night, with daily revisit across the entire zone. RF survey payloads harvest AIS, VDES and radar emissions to classify and fingerprint vessels independently of their declared identity. Optical passes confirm identity and activity — net deployment, pumping operations, crew transfers — on targets already cued by radar or RF. The combination produces a recognised maritime picture that is both legally defensible and operationally actionable.
The operational outcome is a coast guard that can dispatch assets with purpose rather than on patrol schedules. Commanders receive cueing within minutes of a detection event, can cross-reference vessel history and flag-state data on a single console, and can document violations with satellite evidence admissible in flag-state proceedings. Nations that have deployed equivalent capability — Norway, Australia, Canada — report measurable deterrence effects within twelve months of full operations.
Frequently asked
Why can't a small nation just buy EEZ surveillance as a service from a commercial provider like Spire or HawkEye 360?
You can, and many do in the short term. The problem is that a commercial provider's tasking priorities, data retention policies, and export-licence obligations all sit outside your control. In a contested moment — a fisheries dispute, a grey-zone military incursion — the provider may deprioritise your requests, impose access restrictions under pressure from a third government, or simply go offline commercially. Owning the constellation means your tasking queue is sovereign and your data never leaves your ground station unless you choose.
How many satellites are actually needed to get meaningful EEZ coverage?
For AIS reception alone, four to six nanosatellites in sun-synchronous LEO can provide 90–120 minute revisit across most of a medium-sized EEZ. Add SAR for dark-vessel detection and you need a minimum of eight to twelve microsatellites to bring average revisit below three hours. A realistic sovereign starter programme for a mid-ocean island-state EEZ typically targets twelve to sixteen combined AIS/SAR satellites over a five-to-seven year build-out.
What is a 'dark vessel' and why does it matter for EEZ enforcement?
A dark vessel is one that has deliberately disabled or spoofed its AIS transponder. UNCLOS requires all vessels over 300 gross tonnes on international voyages to carry AIS (SOLAS Chapter V), but enforcement at sea is difficult. Dark vessels are disproportionately associated with IUU fishing, sanction evasion, and narcotics trafficking. SAR satellites detect vessel hulls regardless of transponder status, making them the primary tool for dark-vessel identification.
Does operating a surveillance satellite constellation require ITU frequency coordination?
Yes. Space-based AIS receivers operating on VHF maritime mobile frequencies must be coordinated under ITU-R M.1371-5 and notified through the ITU's space network filing process. In addition, SAR payloads using C-, X-, or L-band radar require ITU-R coordination for active sensor emissions. The filing process typically takes 18–36 months from first submission to confirmed coordination, so this must be planned at programme inception.
Can satellite surveillance data be used as legal evidence in fisheries prosecutions?
Yes, but with caveats. Courts in Australia, Norway, and several Pacific Forum nations have accepted satellite-derived vessel tracks combined with AIS logs as evidence in IUU prosecutions. The evidentiary chain must document data custody from satellite reception through ground processing, and imagery analysts may be required as expert witnesses. ISO 19115-compliant metadata tagging of all imagery significantly strengthens chain-of-custody arguments.
How does a sovereign constellation integrate with the existing international maritime surveillance architecture?
The IMO's Long-Range Identification and Tracking (LRIT) system and the joint INTERPOL/IMO Project BLUE NOTICE provide frameworks for sharing vessel-identity data internationally. A sovereign constellation feeds into these frameworks through national maritime rescue coordination centres (MRCCs) and can ingest LRIT data from the IMO Data Distribution Plan to cross-reference AIS detections. Bilateral data-sharing agreements with neighbours multiply the value of each satellite without sacrificing sovereign control.
What ground infrastructure does a sovereign EEZ surveillance programme require?
At minimum: one or two L/S-band ground station antennas for telemetry, tracking and command; an X-band or Ka-band downlink for SAR data; a satellite operations centre; and a maritime operations fusion centre that ingests satellite feeds alongside patrol vessel AIS, LRIT, and coastal radar. Cloud-based ground segment software from providers like Leaf Space or AWS Ground Station can reduce capital cost, but the data processing and storage should remain onshore for sovereignty reasons.
Is a sovereign EEZ constellation economically justified compared to simply expanding the coast guard fleet?
The comparison is not either/or. At roughly $52,000 per patrol-day for an offshore patrol vessel, a medium EEZ nation spends upwards of $18M annually just to maintain minimal physical presence. A twelve-to-sixteen satellite constellation providing near-continuous detection costs in the $80–150M range over a ten-year life cycle including launch and operations, but it eliminates the need for speculative patrol routing. Vessels only deploy when the constellation identifies a confirmed incursion, reducing patrol days and associated costs by an estimated 30–40% based on Norwegian and Australian pilot data.