There is no responsible one-word answer

“Keep AIS on” and “go dark” are both inadequate as universal instructions for the Strait of Hormuz. Automatic Identification System use sits at the intersection of collision avoidance, regulatory duties, coastal and naval awareness, company security policy, and the possibility that hostile actors can exploit broadcast data.

IMO’s revised operational guidelines say AIS should normally operate while a ship is underway or at anchor. They also recognize that a master may switch it off if continuous operation could compromise ship safety or security or when a security incident is imminent. The action and reason should be recorded, relevant reporting obligations considered, and AIS restarted when the danger has passed.

The May 2026 industry guidance for Hormuz takes the same risk-based approach. It says AIS policy should follow flag, company, and current official guidance; notes that active AIS may be a targeting factor; and preserves the master’s overriding authority. It also warns that surveillance systems may collect positional information through other means, so switching off AIS does not make a ship invisible.

The correct question is therefore: which configuration best protects this ship, crew, cargo, other traffic, and the environment under the current verified conditions?

AIS supports safety but has limits

AIS can help ships identify nearby traffic, exchange identity and voyage information, and improve situational awareness when combined with radar, visual lookout, and proper bridge practice. Authorities and reporting centers may use it to understand traffic flow and support coordination. In congested or constrained waters, removing a reliable information source can increase uncertainty for other ships.

AIS is not a collision-avoidance system by itself. Its position may depend on compromised GNSS inputs, manually entered fields can be wrong, transmissions can be delayed or missing, and hostile or erroneous signals can create false targets. MARAD has warned that AIS is open, unencrypted radio technology that can be spoofed. The bridge must cross-check it against radar, visual bearings, sound signals, charts, and other available means.

Turning AIS off also does not remove navigational-light obligations. The May guidance explicitly says lights must comply with the collision regulations throughout the transit. Nor does it relieve the ship of required communications or reporting. A vessel can be physically visible to aircraft, satellites, radar, shore sensors, and nearby ships even when it stops broadcasting AIS.

For this reason, “dark” should never be used as shorthand for safe, undetectable, or unaccountable.

Targeting and misidentification pull in opposite directions

JMIC’s October 8 assessment said ships transiting Hormuz with AIS on could expect elevated targeting risk and directed hails toward the northern route. It also noted risks to vessels remaining static with AIS active. That assessment gives owners a reason to evaluate broadcast exposure, especially for a ship whose flag, operator, cargo, trading history, or location may attract attention.

At the same time, reduced identification can create misidentification risk in a region with intense military activity. Naval forces, coastal authorities, and nearby merchant ships may need to determine what a vessel is doing. A ship that disables AIS without maintaining required alternative reporting could reduce the shared traffic picture and complicate deconfliction.

The balance is not static. AIS may be on during one phase, restricted under a documented security decision during another, and restored after the danger changes. The master needs current flag and official advice because governments may issue vessel-specific or nationality-specific instructions.

Companies should avoid imposing a blanket commercial rule. Charterers benefit from position visibility, but commercial convenience does not override the master’s safety and security judgment. Conversely, a master should not switch AIS off merely to hide a schedule from competitors if regulatory and safety conditions do not justify it.

Build an AIS decision card for the voyage

A practical decision card can list the current flag instruction, coastal-state requirement, company policy, security level, official threat assessment, reporting-center advice, traffic density, navigation-system integrity, and ship-specific exposure. It should state who must be notified before or immediately after a change.

The May industry guidance recommends that if AIS is switched off, UKMTO and NAVCENT NCAGS receive the vessel’s position every two hours or as otherwise directed. Operators must verify that this remains current and applicable before relying on it. Contact details and intervals can change.

The card should also include logbook requirements, position-report format, communications redundancy, restoration triggers, and the treatment of equipment failure. An intentional security shutdown and a technical fault are different events and should not be recorded as the same thing.

Bridge teams should rehearse navigation without trustworthy AIS or GNSS. Radar plotting, visual fixing, parallel indexing where appropriate, echo sounder awareness, paper-chart backup, and traffic communication require competence and sufficient manning. The industry guidance recommends planning on the assumption that GNSS may be unavailable or unreliable for the entire passage.

Any change should be communicated to the company security officer and relevant reporting authorities through verified channels. If the security reason for silence would be defeated by an open radio message, the plan needs a secure or otherwise suitable reporting method established in advance.

Preserve evidence without broadcasting more than necessary

Commercial teams should separate public tracking from authoritative ship reports. A missing commercial AIS track does not prove a vessel stopped, deviated, or suffered an incident. Brokers should not circulate a speculative casualty alert merely because a target disappeared.

Where clients require updates, the owner can provide controlled status information consistent with security and contract duties. Exact routes and timings should not be distributed more widely than necessary. Cargo interests may need assurance without receiving live tactical detail.

After the voyage, the company should review whether AIS decisions matched the plan, whether alternate reporting worked, whether other ships or authorities experienced confusion, and whether new interference or hailing patterns emerged. Lessons should update the next vessel’s risk assessment, not become a permanent rule detached from current conditions.

Zeaclub’s direction in AI shipbroking and agentic workflows can help distinguish an intentional, authorized AIS gap from stale commercial data, track reporting deadlines, and prevent an unverified position from entering a fixture model as fact. It should not tell a master to disable AIS automatically or reveal a protected position to unauthorized users. In Hormuz, information governance is part of physical safety.

This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.

Sources