The symbol can look more certain than it is
An AIS target arrives with a name, course, speed and calculated closest point of approach. That polished presentation can hide stale manual entries, failed sensors, switched-off transmitters, common GNSS interference or deliberate manipulation. Treat the display as a report to test, not an instruction to obey.
IMO states the hierarchy clearly
Resolution A.1106(29) says AIS is an additional source of navigational information. It supports rather than replaces radar target tracking and vessel traffic services, and it does not remove the officer's duty to comply with the Collision Regulations.
The picture is inherently incomplete
The same IMO guidance warns that some craft, warships and shore stations may not carry AIS and fitted vessels may switch it off in certain circumstances. Absence from the screen is not absence from the sea.
Accuracy ends where the input fails
AIS accuracy is only as good as transmitted information. Poorly configured position, speed or heading sensors can create dangerous errors, while built-in integrity checks cannot validate every data value they process.
Gulf interference raises the stakes
US Coast Guard NAVCEN's GUIDE tool contains dated user reports from Gulf and nearby waters describing GNSS disruption or suspected spoofing. These entries document reports and evaluations, not proof that every anomaly has the same cause or actor.
Deliberate spoofing is a recognized threat
IMO's revised counter-piracy guidance describes AIS spoofing and false location information among risks relevant to conflict-affected navigation. A bridge team should be prepared for manipulated identity or position without alleging attribution from a single inconsistent target.
Radar supplies different evidence
Acquire the contact on radar, compare bearing trend, range, vector and aspect, and verify sensor alignment. Radar can also fail or be cluttered, but it does not simply repeat the target's broadcast claim.
Look out of the window
Visual bearings, lights, shapes and relative movement remain essential when visibility permits. A target transmitting the wrong navigational status cannot change its actual aspect.
Relative motion matters more than the label
Collision risk exists between physical vessels, not database identities. If the AIS name changes or duplicates another ship, continue tracking the radar and visual contact while resolving identity separately.
CPA values need lineage
An AIS CPA may use transmitted course and speed over ground, while radar plotting may use measured relative motion. Manoeuvre, current, sensor latency and smoothing can produce different answers. Understand each calculation before choosing the comforting one.
Class A does not mean infallible
Mandatory carriage and approved equipment improve standardization, not truth. Manual voyage data can be stale, sensors can be wrong and radio reception can be intermittent.
Static data can be misleading
Name, call sign, dimensions, destination and draft may be entered incorrectly or left from a prior voyage. Verify identity through call sign, MMSI, visual features and authenticated communication where operationally necessary.
Dynamic data can be stale
Update intervals vary with speed and manoeuvre. Packet collision, antenna shadow, congestion or interference can age the displayed vector. Bridge procedures should make target age visible and define when it becomes unusable.
AIS silence has several explanations
A target may be below carriage thresholds, masked, defective, security-silent or not detected because of radio conditions. Do not convert uncertainty into an allegation of sanctions evasion or hostile intent without supporting evidence.
Transmission can create security exposure
IMO has warned that unrestricted publication of ship AIS data can harm safety and security. A master's decision concerning AIS operation must follow applicable rules, flag and company guidance, be justified, and be recorded.
Collision rules still govern
Resolution A.1106(29) specifically preserves the officer's responsibility under COLREG rule 7. Use all available means appropriate to the circumstances and never let a negotiated AIS-based assumption replace a safe passing assessment.
VHF agreement does not rewrite COLREG
Radio can clarify identity or intention, but ambiguous language, wrong-ship replies and later manoeuvres can make arrangements unsafe. Monitor execution and take early action when the physical situation diverges.
Mine corridors compress decisions
In a narrow assessed route, avoiding one contact may move the vessel toward an uncleared area. Authorities, bridge teams and naval units need a shared traffic picture, but the master still must reconcile collision risk with corridor limits.
Congestion increases data ambiguity
JMIC's June 2026 advisory warned of congestion, mines and naval presence during a dated phase of Hormuz operations. Closely spaced targets, overlapping labels and heavy VHF traffic make disciplined correlation more important.
Establish target-correlation rules
Define how the bridge matches AIS, radar and visual contacts, how disagreement is flagged, who may merge or separate targets and when the master is called. Avoid silent manual fixes that erase evidence of uncertainty.
Preserve raw tracks
Save AIS messages, radar recordings, ECDIS screenshots, sensor status, time sources and bridge audio where law and policy permit. A clean screenshot after the event may hide the transient error that caused the decision.
Report facts before attribution
State time, position source, observed MMSI, displayed data, radar comparison, visual evidence and operational effect. Label spoofing as suspected unless a competent authority confirms it.
Owners need fleet-level comparison
One ship's anomaly may be equipment-specific; simultaneous reports across differently equipped ships may suggest wider interference. A shore team should normalize time and coordinates before drawing conclusions.
Brokers should avoid false precision
Public tracking gaps or jumps do not prove detention, deviation or dark activity. Use qualified language when advising counterparties and distinguish terrestrial reception gaps from onboard transmission decisions.
Insurers need the decision trail
Claims analysis may turn on what information the bridge had, how it cross-checked the target and why it manoeuvred. Preserve contemporaneous records rather than reconstructing certainty after a casualty.
Hypothetical: the crossing ghost
AIS shows a tanker crossing ahead at eight knots, but two radars show no contact and visibility is good. The bridge does not manoeuvre toward a mine boundary for the symbol; it records the anomaly and continues a verified lookout.
Hypothetical: the unnamed radar contact
A strong radar return has no AIS. The officer tracks it, reduces uncertainty and takes collision-avoidance action as required. Missing identity does not suspend physical risk.
Hypothetical: the duplicated MMSI
Two contacts broadcast one identity from different positions. The team separates radar tracks, avoids addressing either by name alone and reports the duplicated data without declaring which transmitter is malicious.
Forecast
IMO reported in 2026 that future VHF Data Exchange System capability can authenticate AIS messages, with the new framework expected to enter into force in 2028. Authentication can improve provenance, but it will not make sensor inputs, intentions or manoeuvres automatically correct.
ZeaClub view
AIS is extraordinarily useful when its limits remain visible. Correlate it with radar, sight, sound and verified communications; expose target age and sensor disagreement; preserve the raw evidence. The safest bridge is not the one with the most symbols, but the one that knows which claims each symbol can support.
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, AIS transpondersAccessed 2026-11-19
- IMO, Revised Industry Counter Piracy Guidance, MSC.1/Circ.1601/Rev.2Accessed 2026-11-19
- USCG NAVCEN, GPS User Issue Detection and Evaluation toolAccessed 2026-11-19
- IMO, Maritime Safety Committee 111th session summaryAccessed 2026-11-19