Five Different Claims Often Become One Headline
An incident assessment should separate at least five propositions:
1. an event occurred; 2. the ship suffered a specified effect; 3. a particular mechanism caused that effect; 4. an actor was responsible; 5. the actor intentionally selected that ship for a stated reason.
Each proposition requires different evidence. A verified explosion and hull breach may establish an attack classification, while the weapon and attacker remain unknown. Fragment analysis may identify a weapon family without proving the launch unit. A public claim of responsibility may be genuine, opportunistic, or deliberately misleading.
Commercial decisions do not always need all five answers. A nearby verified attack can justify protective action before attribution is complete. Claims, sanctions, recovery, diplomatic response, and public allegations usually require a higher evidentiary threshold.
Confirmation of an Incident Is the First Rung
The IMO says its Gulf attack data are compiled through a rigorous validation process involving flag states, coastal states, and credible verified third-party sources. Its confirmed-incident list provides ship names, IMO numbers, dates, locations, and concise consequences.
That methodology makes the list useful for establishing that an event occurred. It does not mean every row proves the attacker or motive. Many entries record damage and pollution or casualty status without attribution.
JMIC and UKMTO likewise update classifications as information develops. UKMTO's incident records show cases initially reported with an unknown projectile and later reclassified after confirmation of a UAV strike. That is evidence of a functioning process, not inconsistency. A preliminary label should change when stronger evidence arrives.
The Ship's Evidence Must Be Preserved Before It Is Interpreted
The first responsibility is life safety, damage control, reporting, and prevention of further harm. Evidence preservation follows within those constraints.
Useful material can include bridge and engine logs, voyage data recorder data, radar and ECDIS recordings, AIS messages, VHF audio, CCTV, photographs, alarm histories, machinery data, witness accounts, fragments, impact geometry, fire patterns, and the exact times of communications.
The chain of custody matters. A fragment moved without documentation or an image stripped of metadata may lose investigative value. Crew interviews should be recorded separately before accounts converge through group discussion. Investigators, flag states, coastal authorities, class, insurers, and security specialists may have different roles, but all benefit from an unaltered primary record.
Crew should not be asked to speculate beyond what they directly saw, heard, or recorded. "A flash was observed on the port side" is stronger evidence than an unsupported conclusion about the weapon.
Weapon Identification Is Not Actor Attribution
A projectile's fragments, flight profile, acoustic signature, or damage pattern may support a technical assessment. Yet weapons can be copied, transferred, captured, modified, or launched by different forces.
The US Maritime Administration's September 2026 advisory identified a broad Iranian threat set that included missiles, armed UAVs, armed unmanned surface vessels, small boats, and helicopters. That national advisory is an important operational source for US-flagged shipping. It is not a substitute for incident-specific forensic evidence in every casualty.
Analysts should state the level of confidence and basis. "Damage is consistent with a UAV strike" is different from "a UAV strike was confirmed." Both differ from "the UAV was launched by actor X." Those distinctions should survive into board papers, insurer notices, and client communications.
Public Attribution Depends on the Source and Its Mandate
Different authorities may publish different kinds of conclusions.
UKMTO and JMIC focus on maritime awareness and operational risk. Flag and coastal states may investigate casualties or security incidents. Military authorities may possess classified sensor data. A national maritime advisory may attribute a threat for protective guidance. IMO may verify an incident while calling for a full and transparent investigation.
After the fatal attack on MT SETTEBELLO, IMO confirmed the attack and casualties, described a reported projectile strike, condemned the act by any party, and called for investigation into the circumstances. The statement did not need immediate final attribution to establish that seafarers had been killed and that shipping faced an unacceptable hazard.
Commercial teams should identify who made an attribution, what evidence the source says it used, whether the conclusion is preliminary, and what jurisdiction or mandate it has. Two official statements may answer different questions rather than contradict one another.
Association Is Not Proof of Target Selection
A ship can be associated with a country through flag, ownership, management, finance, charterer, cargo, ports, crew, or historical trading. These links may affect perceived exposure, but they do not prove why a particular incident occurred.
JMIC reported on 6 March that among incidents it assessed since 1 March, it had identified a US association with one vessel while other identified attacks lacked confirmed US or Israeli associations. That finding challenged a simple assumption that all attacks followed an obvious affiliation rule.
A company should therefore test multiple hypotheses: deliberate selection, misidentification, collateral damage, opportunistic attack, geographic exposure, or an incident unrelated to hostilities. It should not force the facts into the first narrative circulating online.
A Four-Level Attribution Ladder
ZeaClub recommends four levels for commercial reporting.
Level A, event verified: A credible authority or primary evidence confirms an incident and material effect. Cause and actor may remain unknown.
Level B, mechanism assessed: Evidence supports a cause or weapon type. The assessment should state whether it is confirmed, probable, or merely consistent with the damage.
Level C, actor assessed: A competent authority attributes responsibility with an explicit or inferable confidence level. Commercial teams should record the source and whether supporting evidence is public.
Level D, intent assessed: Evidence supports why the ship was selected or whether it was deliberately targeted. This is often the hardest conclusion and should not be inferred solely from ownership, flag, or cargo.
The level should appear beside every incident in an internal dashboard. If an update advances or lowers the level, the prior version should remain auditable.
Safety Decisions Can Precede Final Attribution
A ship does not need to know the attacker before taking cover, reporting, changing readiness, or avoiding a recent incident location. JMIC warned in March that active missile, UAV, and stand-off threats remained credible and that follow-on strikes and collateral harm were possible.
Risk controls should respond to verified capability, geography, and behavior. If an unknown projectile strikes a tanker in the intended route, the owner can pause and reassess without asserting who fired it.
This principle prevents two opposite errors: waiting for impossible certainty before protecting people, and making a public allegation because a safety decision had to be made quickly. Operational caution is not proof of attribution.
Commercial and Insurance Uses Require Careful Language
An owner notifying insurers can provide confirmed facts, preliminary assessments, preserved evidence, and outstanding questions. It should avoid presenting rumor as fact. Underwriters and P&I correspondents may appoint surveyors, investigators, or experts and specify evidence requirements.
Charter-party disputes may turn on causation, danger, orders, delay, or damage rather than geopolitical blame alone. Sanctions screening may require actor attribution, but a provisional media report should not automatically determine legal treatment. Specialist counsel is needed where restrictions or reporting obligations may apply.
Traders and brokers should use qualified language in market updates. "UKMTO reports an attack by an unknown projectile" preserves the source's actual conclusion. Rewriting it as a definitive state attack creates legal, reputational, and commercial risk.
Electronic Interference Can Corrupt the Narrative
GNSS spoofing, AIS anomalies, and communications disruption can produce misleading tracks, timestamps, and location assumptions. JMIC has repeatedly described these hazards in the region.
Investigators should distinguish transmitted AIS data from independently derived position and preserve raw records where possible. A map shared online may be based on corrupted or delayed data. Apparent course changes may result from spoofing rather than evasive maneuvering or compliance with an attacker.
This uncertainty does not make attribution impossible. It means navigation data must be cross-checked against radar, visual observations, logs, satellite information, and other sources before being used to assign responsibility or intent.
A Hypothetical Casualty Review
Assume a bulk carrier reports a blast near the waterline while transiting the Strait. The crew photographs damage, but no weapon is seen. A social account attributes the event to a state, while a second account claims a mine.
At Level A, the company verifies the incident through the master and reports it to appropriate authorities. It preserves VDR, radar, ECDIS, AIS, communications, photographs, and witness accounts. It does not repeat either public attribution.
Later, an authority confirms an uncrewed aerial vehicle strike, moving the assessment to Level B. Unless a competent source identifies the operator, Level C remains open. Even if an actor is later assessed, Level D still requires evidence that this particular ship was intentionally selected.
The ship's safety response was justified at Level A. The public and legal conclusions waited for higher rungs.
Correcting the Record Is Part of Good Analysis
Wartime information changes. A company should issue a dated correction when an incident is reclassified, a casualty count changes, or attribution weakens. Quietly overwriting a dashboard destroys the audit trail and leaves counterparties working from different versions.
Corrections should say what changed and why: new flag-state confirmation, forensic analysis, a coastal-state report, or withdrawal of an earlier claim. They should not imply that uncertainty itself was a failure.
JMIC warned that several public strike claims in March remained unverified and directed mariners to official channels. That remains a useful discipline. Fast reporting has value only when its confidence is visible.
The ZeaClub View
Attribution is a ladder, not a switch. Incident, effect, mechanism, actor, and intent should be assessed separately, with the source and confidence attached to each conclusion.
Commercial teams can act safely on verified hazard information before the attacker is known. They should be slower when assigning blame, alleging motive, invoking sanctions, or communicating publicly.
The strongest maritime intelligence product is not the one that names an actor first. It is the one that preserves evidence, shows what is known, marks what is alleged, updates transparently, and supports the right decision at each level of certainty.
This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.
Sources
- IMO, Middle East information and incident-validation methodologyAccessed 2026-11-19
- IMO, Highlighted confirmed incidents in the Middle EastAccessed 2026-11-19
- UKMTO, Recent incidentsAccessed 2026-11-19
- JMIC Advisory Update 007, 7 March 2026Accessed 2026-11-19
- JMIC Advisory Update 006, 6 March 2026Accessed 2026-11-19
- US MARAD Advisory 2026-011Accessed 2026-11-19
- IMO, Statement on the attack on MT SETTEBELLO, 11 June 2026Accessed 2026-11-19