Correct AIS data without trusting AIS position blindly
AIS broadcasts identity and voyage information, but its dynamic position can inherit a false GNSS input. JMIC reported hundreds of vessels with abnormal positional behavior during severe regional interference, including impossible speeds and tracks.
Check:
- MMSI, IMO number, name and call sign; - ship type and dimensions; - navigational status; - draft and destination; - position-source selection; - heading and rate-of-turn inputs; and - transmission alarms.
Correct static or voyage data only through authorized controls and log the change. Do not repeatedly alter destination text to send informal messages.
Compare AIS position with radar, visual bearings, echo sounder, independent receivers and dead reckoning. If the position is unreliable, report that fact to VTS and relevant authorities. State the fixing method and confidence.
Other forces may see the corrupted track. A clear radio report that “AIS position is affected; vessel verified at...” can reduce ambiguity if transmitted through authenticated channels.
Do not switch AIS off merely to hide a false position without applying the applicable regulations and documented risk assessment.
Authenticate directed VHF communications
UKMTO warned of potential VHF hailing and directed communications as well as interference and unofficial advisories. A caller can sound official without being genuine.
When hailed:
1. note channel, time, position and exact words; 2. identify the calling station and claimed authority; 3. acknowledge identity without volunteering sensitive data; 4. verify through VTS, UKMTO or established naval channels where possible; 5. assess the instruction against navigation safety and law; 6. state any inability to comply safely; and 7. log the response and subsequent action.
Use standard marine phrases and closed-loop readback. Avoid political argument on open radio.
An urgent collision-avoidance action may precede authentication. A direction to alter into unsafe water, stop in a threat area or disclose protected cargo details needs heightened verification.
Record audio where systems permit. Report suspicious communications promptly.
Register through recognized reporting systems
Follow the applicable voluntary or authority reporting arrangements for the region. Provide accurate entry, position and incident reports to UKMTO and coordinate with relevant VTS and coastal authorities.
A reporting trail helps recognized centers distinguish the vessel's intended movement from anomalous electronic data. It also gives the master a contact when suspicious hails occur.
Do not assume that one report reaches every naval or coastal actor. Understand which center handles security awareness, which controls traffic and which coordinates rescue.
Update material changes such as destination, route, prolonged stop, loss of AIS or communications, and casualty. Avoid excessive low-value messages that overload channels.
Preserve confirmation of receipt. If no acknowledgment arrives, use the alternate method in the ship's plan.
The company security officer should maintain shore contact without flooding the bridge with duplicate reporting.
Sanctions and ownership ambiguity can amplify suspicion
Complex ownership, recent flag changes, false documentation and sanctioned trade concerns can affect how a ship is perceived by banks, ports and authorities. A legitimate vessel may still trigger a false positive.
Conduct screening before the voyage across ship, owner, manager, charterer, cargo parties, banks and ports as required. Record data sources, time, match logic and resolution.
Distinguish:
- confirmed sanctioned party; - potential name match; - historical ownership link; - database lag; - unverified allegation; and - cleared false positive.
Do not transmit a full compliance file over open radio. Provide competent authorities a controlled contact for further verification.
If commercial databases show outdated ownership, prepare documentary evidence and request correction. Do not claim databases are all wrong without checking the underlying registry and transaction.
Compliance clearance reduces legal ambiguity. It does not guarantee military recognition or physical safety.
“Neutral” is not a magic signal
A merchant ship may describe itself as civilian and not participating in hostilities. Flag, cargo and voyage can support that description.
Painting “neutral,” changing AIS text or broadcasting a political statement does not create protection by itself and may produce misunderstanding. The legal status of ships in armed conflict is complex and fact-specific.
Use normal internationally recognized identity, lights, signals and reporting. Do not display unauthorized markings or imitate protected vessels.
Masters should not answer political questions beyond operational need. Refer complex requests to the company and flag State while maintaining navigation and safety communications.
A charterer's assertion that cargo is neutral should be verified through documents and legal review. Cargo description can also be security-sensitive.
The safest message is consistent fact, not improvised legal advocacy.
Prepare for communications failure
If VHF, satellite or AIS fails, the vessel still needs a recognizable behavior and backup plan.
Predefine:
- alternate channels and equipment; - scheduled reporting windows; - visual and sound signals; - navigation-light checks; - authority phone and email contacts; - company escalation time; - loss-of-communications route or holding plan; and - conditions that require abort.
Protect GMDSS reserve energy. Carry the identity pack and reporting forms offline. Ensure portable radios are charged and configured.
A total radio silence intended as security can increase misidentification. Use it only under lawful, ship-specific advice that considers the tradeoff.
When communications return, send a concise outage report with verified positions and movement history. Do not allow an automated backlog to create conflicting live messages.
Bridge teams need a hail decision card
Stress can make crews disclose too much, obey unsafe instructions or argue. A one-page card can guide the first response.
Include:
- ship identification phrase; - current verified position and fix method; - course, speed and destination; - nature of any navigation anomaly; - request for station identification; - safe-compliance wording; - inability-to-comply wording; - verification contacts; - security escalation; and - log requirements.
Train with realistic interference and accents. Do not rehearse secret code words on open channels.
The master decides action. The officer handling the radio should not commit the ship to an unsafe route without confirmation.
After a suspicious hail, review whether the ship's electronic and visual presentation remains consistent.
A controlled scenario
A tanker transiting near military activity sees its AIS track jump 18 miles while radar and visual fixes remain stable. A caller claiming to be a naval unit orders it to alter toward shallow water.
The bridge reports the GNSS anomaly, gives a radar-verified position and asks the caller to authenticate. It contacts VTS and UKMTO through established details, maintains a safe course and logs the exchange. The company sends the identity pack through a controlled authority channel. The master remains ready to take immediate collision-avoidance action.
This is a hypothetical scenario, not a report of a specific ship or instruction.
Commercial conclusion
Misidentification risk grows when identity, position, communications and behavior tell different stories. Consistency reduces ambiguity but cannot guarantee protection.
Owners should maintain an offline identity pack and corrected records. Masters should verify position independently and authenticate hails. Charterers and compliance teams should resolve ownership and sanctions discrepancies before sailing. Naval liaison centers need timely, disciplined reports.
ZeaClub can reconcile identity fields, log anomalies, hails, verification and authority contacts. It cannot confer neutrality, authenticate a military unit or guarantee that another actor identifies the ship correctly.
This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.
Sources
- JMIC Advisory Update, 5 March 2026Accessed 2026-11-19
- UKMTO Advisory 003-26 Update 002, 1 March 2026Accessed 2026-11-19
- JMIC Advisory Update, 7 March 2026Accessed 2026-11-19
- JMIC Advisory Update, 16 March 2026Accessed 2026-11-19
- Industry Guidance on Safe Management of Vessel Transit through the Strait of Hormuz, May 2026Accessed 2026-11-19
- IMO, No safe passage: Strait of Hormuz remains highly volatileAccessed 2026-11-19