Dark Vessel Detection System Using SAR Imagery and ML
defense_innovation_unit · Government · 2023 · source Agentic: no · promotional bias: low · source-backed · extracted with prompt 0.5.6 (schema v2)
Generated from extraction.json — do not edit by hand. Every claim cites verbatim source evidence; stated means the quote directly asserts the claim, implied means it supports it indirectly.
Problem
Domain: Maritime surveillance and illegal fishing detection
The Defense Innovation Unit needed to detect illegal, unreported, and unregulated fishing vessels that turn off AIS transponders, across ocean areas too large for patrol vessels or manual image review to cover.
Constraints:
- Illegal vessels can disable AIS and become invisible to transponder-based monitoring.
- The ocean and exclusive economic zones are too large for continuous patrol coverage.
- SAR imagery has artifacts, polarizations, shore effects, and large 20,000-by-20,000-pixel scenes.
- Useful models require large annotated datasets and task-specific metrics.
- Operational value depends on deploying detections into maritime-domain systems used by many countries.
Architecture
DIU and partners built a SAR-based dark-vessel detection pipeline: collect large open-source SAR scenes and co-registered metadata, annotate vessels with automated and manual quality checks, release a public challenge around detection/classification/shoreline-weighted metrics, train models, wrap the best model with preprocessing, and deploy detections into SeaVision for maritime-domain awareness users.
Diagram confidence: explicit (topology described by the source).
flowchart LR sar-satellite-imagery["SAR satellite imagery"] --> annotation-dataset["Annotation dataset"] annotation-dataset --> public-challenge["Public challenge"] public-challenge --> dark-vessel-model["Dark vessel model"] sar-satellite-imagery --> dark-vessel-model dark-vessel-model --> preprocessing-pipeline["Preprocessing pipeline"] dark-vessel-model --> ais-correlation["AIS correlation"] preprocessing-pipeline --> seavision["SeaVision"] ais-correlation --> seavision
Components
| Component | Role | Interacts with |
|---|---|---|
SAR satellite imagery |
Radar imagery source that can observe vessels through cloud cover, night, and visual concealment. | Annotation dataset, Dark vessel model |
Annotation dataset |
Quality-checked SAR scenes with automated and manual vessel annotations plus co-registered channels. | SAR satellite imagery, Public challenge |
Public challenge |
Prize-backed model-development process for vessel detection, sizing, classification, and shoreline performance. | Annotation dataset, Dark vessel model |
Dark vessel model |
ML detector that identifies candidate vessels in SAR imagery. | SAR satellite imagery, Public challenge, Preprocessing pipeline, AIS correlation |
Preprocessing pipeline |
Operational wrapper around model inputs and inference. | Dark vessel model, SeaVision |
AIS correlation |
Compares SAR detections against known AIS broadcasts to identify uncorrelated vessels. | Dark vessel model, SeaVision |
SeaVision |
Maritime domain awareness platform where users view AIS tracks and dark-vessel detections. | Preprocessing pipeline, AIS correlation |
Data flow
SAR satellites capture radar scenes. The project assembles multimodal SAR data, bathymetry, wind, land/ice masks, and annotations. Challenge participants train vessel-detection models against task-specific metrics. DIU wraps the chosen model with preprocessing, correlates SAR detections against AIS broadcasts, and surfaces uncorrelated detections as dark vessels in SeaVision.
Why this architecture
SAR was chosen because vessels cannot evade it with clouds, nighttime, or visual covers, and because AIS-only monitoring misses vessels that turn off transponders. The public challenge created model improvements on a specialized dataset, and SeaVision delivered the detections into an existing operational platform.
Models used: Faster R-CNN baseline model · Challenge-submitted SAR vessel detection models
Scale
- The dataset included about 243,000 annotations and 82 million square kilometers of imagery.“we ended up with something like 243,000 annotations and 82 million square kilometers of imagery”transcript, stated
- The SAR scenes were very large, about 20,000 by 20,000 pixels each.“that data set it was 991 scenes now these are Big these are each 20,000 pixels by 20,000 pixels”transcript, stated
- The deployed SeaVision system is used by over 100 countries.“we deployed this thing um to a system called C Vision that is used by hundreds of countries around the world by over 100 countries around the world”transcript, stated
- The speaker said one in five fish caught worldwide originates from illegal, unreported, and unregulated fishing.“one in five fish caught around the world originate from illegal unreported and unregulated fishing”transcript, stated
Alternatives considered (roads not taken)
Rely on AIS broadcasts
Rejected because: Illegal vessels can turn AIS off, leaving no transponder signal to monitor.
Rely on patrol vessels and manual image review
Rejected because: The ocean is too large, resourcing is uneven, and manual image analysis is slow and unreliable.
Use standard optical imagery only
Rejected because: SAR provides all-weather/night capability and detects metal vessels in conditions optical imagery cannot.
Patterns
data-quality-loop (data)
The project combined automated and manual annotations with quality checks before model training and challenge release.
eval-driven-development (evaluation)
The challenge task and metric were designed around operational needs such as object detection, size, vessel class, and near-shore performance.
batch-offline-processing (operations)
The system processes satellite imagery and queues inference to provide dark-vessel detections efficiently at large geographic scale.
Tradeoffs
Use SAR imagery for dark-vessel detection
Chose space-based radar detections over AIS-only or optical-only monitoring.
Rationale: SAR can reveal vessels that disable AIS and is robust to cloud, night, and visual concealment.
Use public challenges for model development
Chose released dataset, task, and prize-backed competition over only internal government model development.
Rationale: The challenge attracted broad participation and improved performance over time.
Gotchas (what bit them)
SAR images are not ordinary computer-vision inputs.
Root cause: Radar reflectivity, polarizations, shore artifacts, wind farms, and oil slicks create different visual artifacts from optical imagery.
Resolution: Design SAR-specific data augmentation, task metrics, and multimodal co-registered channels.
Large SAR scenes make local chipping lose important context.
Root cause: Mother-ship patterns and vessel arrays may depend on long-range spatial relationships.
Resolution: Treat long-range context as a systems requirement rather than a standard object-detection detail.
Operational maritime AI still needs ongoing model maintenance.
Root cause: Sensors, environments, and bureaucratic deployment processes change over time.
Resolution: Continue surveying model performance, updating models, and managing operational refresh processes.
Evaluation
The task evaluated vessel detection, object size, vessel-vs-non-vessel classification, fishing-vessel classification, and near-shore performance with a weighted metric; deployment also requires ongoing model performance surveillance.
Metrics: Object detection · Object size · Vessel classification · Fishing-vessel classification · Near-shore weighted performance · Operational model health
Outcomes
- The project produced a large annotated SAR dataset for dark-vessel detection.
- Public challenges drew thousands of submissions and improved performance over time.
- The model and preprocessing pipeline were deployed into SeaVision.
- SeaVision users can see SAR detections not correlated with AIS and identify likely dark vessels.
- The approach supports lower-cost monitoring for countries with limited patrol resources.
The operational platform is used by over 100 countries and the dataset covered 82 million square kilometers of imagery.