Start with what is verified
JMIC reported on 18 November that the regional maritime security threat remained severe. Its blockade update said masters should anticipate more VHF hailing, Iranian Revolutionary Guard Corps monitoring along transit routes, congestion near anchorages, and a sustained naval presence. It advised consideration of directions from blockading forces, crew health and safety, continuous monitoring of VHF Channel 16, clear transit intentions, AIS policy, and reporting unusual activity.
Those statements establish an operating environment, not the identity or legal authority of every caller. A voice claiming to be a warship may be genuine, mistaken, spoofed, or malicious. A boarding may be consensual, compelled, or disputed. The master needs a response that protects life, preserves evidence, and avoids an unnecessary escalation while the company obtains flag-state and legal support.
Hailing is not yet boarding
The first contact may request identity, flag, cargo, last port, next port, owner, charterer, or intentions. It may order a course alteration, speed reduction, stop, or movement to an anchorage. Each request creates a different navigational and security consequence.
The bridge should record the time, position, channel, caller's exact identifier, signal strength, language, questions, answers, requested action, and surrounding traffic. Where safe, a second officer should maintain the log while the master communicates. The team should avoid speculation and provide concise, consistent information already authorized by the ship security plan and company procedure.
Authenticate without provoking
Authentication should be built into the voyage plan. The ship can compare the caller's claimed identity with visual, radar, AIS, navigational-warning, and recognized reporting-centre information. UKMTO can receive reports of unusual activity. The company security officer can contact the flag administration or naval coordination channel designated for the voyage.
The ship should not demand sensitive challenge-and-response methods over an open channel unless those methods were formally provided. Nor should it broadcast commercially sensitive cargo or ownership information to everyone listening. A neutral response can acknowledge the call, state that the master is verifying the instruction, and request a safe working channel.
Safety remains the first bridge problem
Any order to stop or alter course must be tested against under-keel clearance, traffic, mines, weather, machinery limits, and collision rules. Immediate compliance may be physically unsafe even when the caller is genuine. The master should explain the hazard plainly and propose the safest practicable execution.
SOLAS regulation XI-2/8 preserves the master's professional judgment over decisions necessary to maintain ship security. IMO guidance also stresses that coordinated or military-supported passage does not transfer command of a merchant ship to military forces. That does not answer the legality of a specific order, but it confirms that safe navigation cannot be outsourced.
Use a prepared escalation tree
The company should define who is called and in what order: company security officer, designated person ashore, UKMTO, flag state, insurer, charterer, cargo interests, and legal counsel. The master needs a single shore coordinator rather than conflicting instructions from several departments.
The tree should include loss-of-communications contingencies and thresholds for security alerts. It should distinguish routine questioning, persistent monitoring, close approach, coercive order, warning shot, attempted boarding, actual boarding, diversion, and detention. Each stage should have pre-agreed actions, but the master must retain discretion for the conditions on scene.
Do not improvise physical resistance
Counter-piracy measures are not automatically suitable against identifiable state forces. Locking access, manoeuvring aggressively, deploying armed guards, or using deterrent equipment could be misread and rapidly increase danger. Revised industry counter-piracy guidance recognizes that state-actor boarding presents different circumstances and that specific mitigation should follow a validated threat assessment.
The default objective is crew survival and de-escalation. Any security team must operate under clear rules agreed with the company and consistent with flag, coastal, and port-state law. IMO does not generally endorse or condemn privately contracted armed personnel; their carriage and use depend on relevant state law and a voyage-specific assessment.
If boarding appears imminent
The master should make the crew accounting and communications plan effective before personnel come alongside. Non-essential crew can move to designated safe locations without creating the appearance of preparing an ambush. Essential documents should be accessible, but originals and electronic systems should be controlled according to the ship security plan.
The bridge should clarify where the boarding party intends to embark, what speed and lee it requires, whether weapons are present, and whether the ship may inform its flag and company. Safe pilot-ladder or accommodation-ladder arrangements remain important. A fall, collision, or propeller accident can kill regardless of the encounter's legal status.
During a visit or search
One designated ship representative should accompany the party where permitted. Crew should remain calm, avoid sudden movements, and not obstruct armed personnel. The representative should record names, ranks, unit markings, areas visited, documents inspected or taken, electronic devices accessed, statements made, and any damage, subject to personal safety and local instructions.
The master should not sign an inaccurate statement merely to accelerate release. If refusal creates immediate danger, the circumstances and any protest can be recorded when safe. Requests for passwords, cargo data, crew devices, or commercially sensitive files should be escalated, but life should not be put at risk to protect information.
Diversion and detention change the voyage
An order to proceed to another anchorage or port affects fuel, charts, pilotage, draft, bunkers, crew endurance, sanctions exposure, cargo care, and contractual performance. The master should request the destination, route, reporting interval, escort arrangements, and reason for diversion. The company should notify the flag state and preserve a continuous timeline.
Charterers and cargo interests need verified facts rather than a premature accusation. A message can state that the vessel is following a direction under protest or for safety, if advised, without characterizing the incident as seizure, arrest, capture, or lawful inspection before counsel assesses it.
Evidence must survive the crisis
Voyage-data-recorder retention, bridge audio, radar and ECDIS screenshots, VHF logs, AIS settings, emails, satellite messages, CCTV, photographs, deck logs, engine movements, and witness notes may later matter to authorities, insurers, charter-party disputes, and crew welfare reviews. Preservation should begin immediately without interfering with safe navigation.
Copies should be transferred ashore when secure and lawful. The company should record provenance and avoid editing original files. Public statements and social-media posts by crew can compromise negotiations, expose personal data, or create contradictory evidence, so a family and media communication plan is essential.
Commercial parties need disciplined notices
The owner should issue notices under the relevant charter-party and insurance clauses while facts are developing. It should identify the instruction received, operational response, delay, changed destination, crew status, cargo condition, and next reporting time. Rights can be reserved without exaggeration.
Charterers should avoid pressuring the master to disregard an on-scene security judgment. Brokers should keep a clean record of what each party knew and when. Insurers should receive prompt notice, particularly if there is detention, deviation, damage, ransom-like demand, sanctions concern, or a potential sue-and-labour expense.
A hypothetical encounter
Consider a product tanker hailed by a vessel claiming military authority and ordered to reduce speed for inspection. Radar shows a fast craft but no reliable AIS identity. The master acknowledges, states the ship's flag and transit intention, records the exchange, calls UKMTO and the company, and explains that an immediate stop would be unsafe in traffic. The caller provides a safe course and boarding point.
The company alerts the flag state and insurers. Crew muster discreetly, the boarding station is prepared, and evidence systems are preserved. The master cooperates to protect life while reserving the ship's position through shore channels. This is a hypothetical workflow, not a claim that such an incident occurred on 18 November.
ZeaClub view
The worst time to invent a boarding policy is when an armed craft is already alongside. A good plan separates authentication, navigation, crew protection, legal reservation, commercial notice, and evidence preservation. It gives the bridge short scripts and clear contacts without pretending that a checklist can decide every encounter.
Cooperation for immediate safety does not require careless legal admissions. Preserving rights does not require physical confrontation. The professional response is calm, documented, proportionate, and connected to qualified shore support from the first hail until the crew and vessel are released.
This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.
Sources
- JMIC/UKMTO, Advisory 017-26, 18 November 2026Accessed 2026-11-19
- IMO, Frequently Asked Questions on Maritime SecurityAccessed 2026-11-19
- IMO, Revised Industry Counter-Piracy Guidance, MSC.1/Circ.1601/Rev.2Accessed 2026-11-19
- IMO, Guide to Maritime SecurityAccessed 2026-11-19
- IMO, Private Armed SecurityAccessed 2026-11-19