This article provides general information, not legal, regulatory or financial advice. Requirements depend on the applicable contract, authority and jurisdiction.
One missing line has many causes
An apparent AIS gap can arise from equipment failure, antenna shadow, power loss, reception limits, data aggregation, safety-related switching, spoofing or deliberate concealment. Compliance should investigate the alternatives before assigning intent.
AIS has a safety purpose
IMO guidance treats AIS as an additional navigation and identification tool with operational limitations. Sanctions teams should not demand behavior that conflicts with lawful safety decisions by the master.
Transmission duties are not absolute in every circumstance
SOLAS and IMO guidance address continuous operation and circumstances in which a master may switch AIS off when safety or security is compromised, subject to recording and restoration expectations.
Public tracking is not the ship receiver
Commercial maps depend on terrestrial or satellite reception, processing and licensing. A gap on a website does not prove the transponder stopped transmitting.
Coverage varies by geography
Terrain, antenna density, satellite pass, message collision and congestion affect reception. Establish expected coverage before labeling a gap abnormal.
Provider filters can hide data
Platforms may suppress positions, interpolate tracks or merge identities. Obtain raw or multi-provider evidence where the conclusion matters.
Timestamps need scrutiny
Received, processed and displayed times can differ. A clock or feed delay may create an apparent jump that did not occur onboard.
Identity errors mimic disappearance
Wrong MMSI, IMO number, call sign or name can split one voyage into several tracks. Search historical identities and verify the immutable vessel number.
Spoofing can create a false presence
A transmitter or data manipulation can place a vessel where it is not. Correlate radar, satellite, port, draft and document evidence.
GNSS interference can displace genuine AIS
The ship may transmit honestly from a corrupted position source. A physically impossible jump can indicate PNT failure rather than sanctions evasion.
Power loss has operational evidence
Blackout, equipment defect or maintenance should appear in logs, alarms, VDR, repairs or reports. Seek contemporaneous records rather than a retrospective assertion alone.
Antenna faults can be intermittent
Cable, connector, water ingress and shadowing can reduce range without total failure. Technical history may explain a repeating heading-dependent pattern.
Congestion can reduce reception
High traffic produces many messages in limited radio capacity. Missing points near Hormuz may reflect channel load, though an unusual long gap still warrants review.
A security decision is not blanket permission
The documented exception should be necessary and limited. Commercial desire to hide a transfer or destination is not a navigational safety reason.
Company instructions need care
Shore teams should not order AIS off to reduce public visibility without legal and safety analysis. The master retains responsibility for safe operation.
A gap near STS is a stronger indicator
Timing around a rendezvous, speed change and draft change can raise risk. It remains an indicator requiring corroboration.
Location matters
Transfers in known anchorages, terminals or lightering zones have different context from unexplained meetings in remote waters.
Counterpart identity matters
Screen the other vessel's IMO number, ownership, manager, flag, history and cargo role. A clean counterpart does not resolve all risk, but an opaque one increases it.
Draft provides imperfect corroboration
Changes can support cargo transfer while ballast and sea conditions complicate estimates. State source and uncertainty.
Satellite imagery can fill some gaps
Optical or radar imagery may locate a vessel during darkness. Identification, time, resolution and weather limits must be documented.
Port records provide independent anchors
Pilot, tug, berth, terminal, agent and customs data can confirm arrival and movement. Reconcile their local times and vessel identifiers.
Cargo records test the narrative
Ullages, bills, meter tickets, samples and tank plans can support or contradict the claimed activity during the gap.
Financial records reveal benefit
Invoices, freight, demurrage and payments may connect an unexplained movement to a party or cargo. AIS alone cannot show the commercial principal.
Voyage orders reveal intent cautiously
Contemporaneous instructions are relevant, but intent should not be inferred from one ambiguous message. Preserve the full chain.
Repair records require verification
Check technician, parts, dates, defect reports and restoration. A generic invoice created after inquiry is weak evidence.
VDR may preserve ship-side facts
Where available and retained, VDR and AIS interface records can show onboard data, alarms and bridge decisions. Preserve them before overwrite.
Re-screen on identity change
Name, flag, MMSI, ownership or manager changes around a gap should trigger enhanced review. Legitimate transactions also produce changes.
Pattern analysis is stronger than one event
Repeated gaps at transfers, identical routes, rapid reflagging or implausible tracks can strengthen concern. Avoid assuming every past gap shares one cause.
Risk scoring must remain explainable
State which indicator raised the score, its data source and what evidence could resolve it. A black-box red flag cannot support a defensible decision alone.
Do not demand impossible continuity
Public AIS coverage is never a perfect global record. Compliance standards should focus on reasonable evidence and anomalies, not an unattainable dot every minute.
Escalate before irreversible performance
Pause nomination, loading, payment or claim settlement when the gap is material and unresolved. Define the information and deadline needed for a decision.
Preserve the original data
Keep provider, query, export, timestamps, identifiers and screenshots with metadata. A later map may change as the platform reprocesses information.
State the conclusion precisely
Write unexplained AIS gap consistent with several causes, or evidence supports safety-related switching. Do not write sanctions evasion confirmed without adequate proof.
Owners need an AIS exception procedure
Define authority, safety assessment, log entries, notifications, restoration and shore reporting. Keep compliance access to the relevant facts.
Charterers need lawful transparency
Provide voyage and cargo information needed to resolve anomalies without pressuring the master to compromise security.
Brokers should avoid rumor amplification
A missing public track is not proof the vessel went dark. Attribute the provider and time, and send the matter for verification.
Insurers need contemporaneous records
Cover and reporting may depend on navigation and sanctions facts. Preserve technical, operational and commercial evidence before taking a position.
Traders need multi-source review
Combine AIS, imagery, documents, corporate data and payments. A single compelling graphic can still tell the wrong story.
Hypothetical: the coverage gap
One provider loses a track for six hours while another and port records show continuous normal transit. The compliance alert is resolved as data coverage.
Hypothetical: the safety shutdown
The master switches AIS off during a documented threat, records the decision and restores transmission afterward. The exception is assessed separately from cargo legality.
Hypothetical: the concealed transfer
A gap coincides with remote rendezvous, draft change, conflicting bills and payment to an opaque intermediary. The combined evidence justifies escalation far beyond the gap alone.
Forecast
AIS analytics will integrate satellite imagery and behavior models, while spoofing grows more sophisticated. Human review will need to distinguish sensor truth, data-pipeline artifacts and commercial inference.
ZeaClub view
Treat an AIS anomaly as a question generator. Establish whether the ship transmitted, whether the provider received, what the vessel did physically, who benefited and whether the explanation fits independent records. Compliance is strongest when it neither ignores darkness nor mistakes missing pixels for a legal judgment.
This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.
Sources
- IMO, Revised guidelines for onboard operational use of shipborne AIS, A.1106(29)Accessed 2026-11-19
- IMO, SOLAS ConventionAccessed 2026-11-19
- U.S. Treasury OFAC, Sanctions Compliance Guidance for the Maritime Shipping IndustryAccessed 2026-11-19
- UK Government, Maritime guidance on sanctions, export controls and counter-evasionAccessed 2026-11-19
- Council of the European Union, EU Best Practices for restrictive measuresAccessed 2026-11-19