🔔 Subscribe to ShipUniverse Weekly →
The United Kingdom Maritime Trade Operations Centre says it is struggling to establish the true number of attacks on commercial shipping around the Strait of Hormuz because the majority of vessels attacked are not reporting directly to UKMTO. In its October 16 weekly assessment, the Royal Navy-linked organization said it knows of additional incidents through other sources but cannot publish some of them because it lacks sufficient verification. UKMTO recorded 12 attacks during the week covered by that report, while Seatrade Maritime counted 29 UKMTO warnings covering 28 incidents in October through October 18 and 153 reported incidents since March 1. UKMTO has not disclosed how many additional attacks it believes remain outside the verified public count.
An Attack Can Happen Without Ever Becoming a UKMTO Warning
UKMTO says most attacked vessels are not reporting directly. Some incidents can still be reconstructed from military, flag-state, company or other sources, but others cannot be publicly verified.
Projectile, UAV, RPG, mine or other hostile event.
Master or CSO may report to UKMTO. UKMTO says most attacked vessels currently do not.
Flag state, military, security company, owner, AIS evidence or another reporting centre may surface the event.
Without enough corroboration, UKMTO says it can be aware of an incident but unable to publish it.
Inside the Reporting Gap
UKMTO has confirmed the under-reporting. It has not publicly identified the motives of individual owners. Several mechanisms can nevertheless be separated into documented facts and reasonable hypotheses.
| Factor | How It Could Affect Reporting | Evidence Level | Important Qualification |
|---|---|---|---|
| Reporting is voluntary | A master or company can transit the VRA without participating in UKMTO's voluntary scheme. | DOCUMENTED | UKMTO strongly encourages reporting because non-participation can delay assistance. |
| Commercial or national constraints | Operators may have internal, state or contractual restrictions on which security centres receive information. | DOCUMENTED | Joint UKMTO/MSCIO guidance explicitly acknowledges national and commercial reporting constraints. |
| Reporting to another authority | An incident can be reported to a flag state, military force, coastal authority, insurer or MSCIO without the vessel making a direct UKMTO report. | DOCUMENTED | This is not necessarily secrecy. It can still leave UKMTO waiting for verification. |
| Commercial confidentiality | Attack details may reveal route, cargo, charterer, STS activity or voyage strategy during an unusually sensitive market. | PLAUSIBLE | UKMTO says information submitted through its scheme is treated in strict commercial confidence. |
| Insurance and claims management | Owners may prefer tightly controlled casualty communications while insurers, surveyors and lawyers establish facts. | PLAUSIBLE | There is no evidence owners are avoiding UKMTO simply to avoid premiums. Insurance policies can separately require prompt casualty notification. |
| Sanctions / blacklist sensitivity | Public attention to an attack may expose trading relationships, Iranian-list status or politically sensitive route choices. | PLAUSIBLE | UKMTO has not identified this as a cause of current non-reporting. |
| Emergency workload | Firefighting, casualty evacuation, machinery damage and getting the ship to safety take precedence immediately after a strike. | PLAUSIBLE | This can explain delay better than permanent non-reporting. |
| Fear of political consequences | Some operators could view reporting to a Royal Navy-linked centre as sensitive during an active Iran-US conflict. | UNPROVEN | No public evidence shows this is driving the majority of refusals. |
Hormuz Incident Visibility Model
Test how a minority direct-reporting rate can affect the apparent October attack count when some non-reporting incidents are later recovered through third-party verification.
Visible vs. potentially hidden events
We welcome your feedback, suggestions, corrections, and ideas for enhancements.
Please click here to get in touch