Natural Catastrophe·ActiveEscalating
Tropical Storm Arthur tracks along Texas Gulf Coast
🇺🇸 Texas Gulf Coast, centered near Houston, Texas· Area17 Jun
84 reportsPROPMHMC+2
MediumAI Refreshed
MonitoringLow impactAI Refreshed
Vessel Attack Leaves 2 Indian Sailors Dead, Chief Engineer Missing
Occurred 8 Jun 2026·Detected 17 Jun 2026·
🇮🇳 Location unspecified in source; vessel attack waters unknown128 reportsCAT 26AA
MarinePolitical Violence & WarWar & Armed ConflictEnergy & InfrastructurePolitical RiskMarine HullMarine CargoEnergyTerrorism & Political ViolencePolitical RiskCasualty & LiabilityLife & HealthWar Risk
A vessel attack in the Gulf of Oman / Strait of Hormuz area has killed Indian seafarers, with the chief engineer unaccounted for. Reporting attributes the attack to a US naval strike (unconfirmed), and three Indian-crewed vessels have been attacked in the same waters within four days. India's MEA has summoned the US Charge d'Affaires for a second time. Vessel identity, flag, ownership, cargo, and insured values remain undisclosed; no hull total loss has been confirmed.
AI-generated from linked source reports. See our correction policy.
Impact verdict
Low impact. Crew P&I and crew personal accident exposure is the most plausible loss pathway given confirmed Indian-national fatalities, but loss scale is constrained by undisclosed vessel identity, insured value, and hull status. Marine hull war risk and energy transport relevance is elevated by the JWC-listed war risk zone and Hormuz chokepoint location, and by the three-attack-in-four-days pattern, though no hull damage, vessel identification, or cargo has been disclosed. Attribution to US armed forces is asserted but unconfirmed; substantiation would materially shift war risk and liability treatment. Potential impact remains low on available information.
View assessment methodologyHow we grade what we know -- Known · Reported · Uncertain. Methodology →
Intelligence ledger
Each line expands in place to its underlying sourced claim.
Known13 lines
Two Indian sailors confirmed dead▾
structured lineknown
No separate sourced-claim record is available for this line yet.
Chief engineer reported missing▾
structured lineknown
No separate sourced-claim record is available for this line yet.
Event classified as a vessel attack▾
structured lineknown
No separate sourced-claim record is available for this line yet.
Indian nationals among crew affected▾
structured lineknown
No separate sourced-claim record is available for this line yet.
Two Indian sailors confirmed dead in a vessel attack, with the chief engineer reported missing; some sources reference three Indian fatalities when aggregating across the three-ship incident pattern.▾
vessel_attack_indian_fatalities_confirmedloss indicationsvalid from 18 Jun 2026, 19:31Marine - P&I
Market relevance: Crew P&I and crew personal accident exposure; war risk P&I for Indian-crewed vessels
Two Indian sailors were confirmed dead in the vessel attack near Oman.▾
two_indian_sailors_confirmed_deadcrew liabilityvalid from 18 Jun 2026, 01:58Marine
Market relevance: Crew P&I and life exposure pathway activated; scale below commercial threshold without further disclosure.
initial source · 18 Jun 2026, 03:25
“Third ship with Indian crew attacked near Oman in four days” — thehindu.com · 11 Jun 2026, 09:30 · mainstream media
Two Indian sailors were confirmed killed in the attack.▾
casualty_indian_sailor_fatalitiescrew liability exposurevalid from 11 Jun 2026, 00:00Marine
Market relevance: Crew fatality count drives P&I crew life and death & disability exposure, though individual crew sums are typically below commercial threshold.
“All three missing Indian sailors confirmed dead” — moneycontrol.com · 11 Jun 2026, 07:30 · mainstream media
Two Indian sailors were killed in an attack on a vessel.▾
vessel_attack_two_indian_sailors_killedinsured lossvalid from 11 Jun 2026, 05:00Marine - P&I
Market relevance: Crew P&I claims may arise dependent on flag state and crew contract terms.
“Two Indian sailors dead, chief engineer missing after attack on vessel near Hormuz” — newkerala.com · 11 Jun 2026, 05:00 · mainstream media
India's Ministry of External Affairs has summoned the US Charge d'Affaires for a second time over reported US naval strikes on vessels with Indian crew members.▾
india_us_diplomatic_escalation_charge_daffaires_summonedregulatory riskvalid from 18 Jun 2026, 19:31Marine - P&I
Market relevance: Sanctions/trade restriction tail risk between India and US; secondary geopolitical risk indicator
“MEA summons US Charge d'Affaires Jason Meeks for second time over strikes on vessels with Indian seafarers” — russiaherald.com · 12 Jun 2026, 13:00 · mainstream media
“India summons US Charge d'Affaires, lodges strong protest over attacks on vessels carrying Indian seafarers” — aninews.in · 12 Jun 2026, 11:15 · mainstream media
A vessel was attacked off the coast of Oman near the Strait of Hormuz, with casualties among the crew.▾
incident_type_vessel_attackzone war risk attentionvalid from 11 Jun 2026, 00:00Marine
Market relevance: Incident location within a JWC-listed war risk zone elevates underwriter attention to marine hull war and crew P&I covers.
“All three missing Indian sailors confirmed dead after tanker attack near Hormuz” — moneycontrol.com · 11 Jun 2026, 07:30 · mainstream media
The vessel carried 28 crew members, of whom 24 were Indian nationals; 21 Indians were reported rescued.▾
crew_composition_indian_totalcrew liability exposurevalid from 11 Jun 2026, 00:00Marine
Market relevance: Crew nationality mix informs P&I club exposure and repatriation obligations.
“28 crew members, 24 Indians, 21 Indians have been rescued” — moneycontrol.com · 11 Jun 2026, 07:30 · mainstream media
Event is classified as a vessel attack.▾
event_classification_vessel_attackcoverage triggervalid from 18 Jun 2026, 01:58Marine
Market relevance: Defines applicable war risk vs standard marine coverage triggers.
initial source · 18 Jun 2026, 03:25
“Third ship with Indian crew attacked near Oman in four days” — thehindu.com · 11 Jun 2026, 09:30 · mainstream media
Potential impact assessed as low on available information given the absence of disclosed insured values, no confirmed hull total loss, and undisclosed vessel/cargo details.▾
potential_impact_severity_low_data_constrainedseverity assessmentvalid from 18 Jun 2026, 19:31Marine - P&I
Market relevance: Quantification is constrained; crew P&I is the most plausible loss pathway
Reported28 lines
Arrests have been made in connection with the incident▾
structured linereported
No separate sourced-claim record is available for this line yet.
Authorities and negotiations are involved in response▾
structured linereported
No separate sourced-claim record is available for this line yet.
The vessel's chief engineer is reported missing following the attack; one corroborating source later indicated all three missing were confirmed dead, which would supersede the missing status.▾
casualty_chief_engineer_missingcrew liability exposurevalid from 11 Jun 2026, 00:00Marine
Market relevance: Missing-status outcome affects P&I crew life and recovery exposure but is not a hull impact.
“All three missing Indian sailors confirmed dead” — moneycontrol.com · 11 Jun 2026, 07:30 · mainstream media
“chief engineer missing after attack on vessel near Hormuz” — webindia123.com · 11 Jun 2026, 07:15 · mainstream media
The chief engineer of the vessel is reported missing following the attack.▾
vessel_attack_chief_engineer_missinginsured lossvalid from 11 Jun 2026, 05:00Marine - P&I
Market relevance: Search/rescue and recovery costs may be relevant under P&I.
“Two Indian sailors dead, chief engineer missing after attack on vessel near Hormuz” — newkerala.com · 11 Jun 2026, 05:00 · mainstream media
Per Indian government figures cited in reporting, 562 Indian crew members are working aboard vessels navigating conflict-affected waters, with 13 Indian nationals among 329 personnel on affected ships.▾
indian_seafarer_population_at_risk_contextexposure scalingvalid from 12 Jun 2026, 13:00Marine - P&I
Market relevance: Indicates scale of Indian-crewed exposure in the war risk zone
India's MEA, Ministry of Ports, and Seamen Welfare Fund Society are engaged in diplomatic and welfare response; consultations and negotiations are underway.▾
india_diplomatic_response_consultations_underwaycontextvalid from 12 Jun 2026, 13:00Marine - P&I
Market relevance: Background context only
Three ships carrying Indian crew have reportedly been attacked in the same waters within four days, including the fatal incident.▾
three_indian_crewed_vessels_attacked_four_daysrisk environment changevalid from 18 Jun 2026, 19:31Marine - Hull War
Market relevance: Pattern frequency elevates marine war risk and crew P&I pricing considerations
The vessel attack occurred in waters near Oman, reported in the Gulf of Oman / Strait of Hormuz area, inside a JWC-listed war risk zone at a critical maritime chokepoint.▾
vessel_attack_location_gulf_of_omanrisk environment changevalid from 18 Jun 2026, 19:31Marine - Hull War
Market relevance: Marine war risk zone designation drives additional premium and exclusion triggers
Indian officials and ministers (incl. Shipping Minister Sarbananda Sonowal) engaged on the incident.▾
indian_diplomatic_response_activecontextvalid from 11 Jun 2026, 09:30Political Risk / Political Violence
Market relevance: Diplomatic engagement affects state-to-state liability and crew repatriation pathways.
Ceasefire collapse threatened per regional reporting citing Indian claims.▾
ceasefire_collapse_threat_reportedwar risk pricingvalid from 18 Jun 2026, 00:58Political Risk / Political Violence
Market relevance: Ceasefire instability elevates political violence and war risk underwriting across regional marine and energy lines.
Iran has launched retaliatory strikes following US attacks, with a new tanker reported on fire, per regional reporting.▾
iranian_retaliation_tanker_fire_reportedwar risk pricingvalid from 18 Jun 2026, 00:58Marine
Market relevance: Retaliation and tanker fire escalate regional war risk and energy transport underwriting concern; not directly tied to specific insured vessel.
“Stigla osveta Irana za udare. Indija: SAD nam ubio pomorce, danas gori novi tanker” — index.hr · 11 Jun 2026, 09:15 · mainstream media
A third ship carrying Indian crew has been attacked in waters near Oman within four days, indicating a pattern of maritime incidents in the Arabian Sea / Gulf of Oman.▾
pattern_three_attacks_in_four_dayswar risk pricingvalid from 18 Jun 2026, 01:58Marine
Market relevance: Pattern detection elevates war risk zone rating and may trigger additional premiums or policy responses for Hormuz transit.
“Third ship with Indian crew attacked near Oman in four days” — thehindu.com · 11 Jun 2026, 09:30 · mainstream media
Incident reported inside a JWC-listed war risk zone within a critical global shipping chokepoint at or near the Strait of Hormuz / Gulf of Oman.▾
location_jwc_war_risk_zone_hormuzwar risk pricingvalid from 18 Jun 2026, 01:58Marine
Market relevance: Elevates marine hull war risk, marine cargo war risk, and energy transport underwriting relevance.
“The escalating attacks in a JWC-listed war risk zone and critical maritime chokepoint” — thehindu.com · 11 Jun 2026, 09:30 · mainstream media
United Kingdom Maritime Trade Operations (UKMTO) referenced in regional reporting on Arabian Sea incidents.▾
ukmto_awareness_indicatedcontextvalid from 11 Jun 2026, 09:30Marine
Market relevance: UKMTO advisories inform war risk zone ratings and transit guidance.
United Kingdom Maritime Trade Operations (UKMTO) is referenced in reporting related to the incident.▾
response_ukmto_awarenesszone war risk attentionMarine
Market relevance: UKMTO awareness is consistent with a JWC-listed war risk zone notification but does not itself quantify loss.
“United Kingdom Maritime Trade Operations” — moneycontrol.com · 11 Jun 2026, 07:30 · mainstream media
One source attributes the attack to US armed forces; this attribution is reported but not independently corroborated.▾
attack_attributed_to_us_forcesattribution uncertaintyvalid from 11 Jun 2026, 00:00Marine
Market relevance: If substantiated, attribution to a state actor materially shifts war risk and liability considerations.
“Seamen's Union of India claims US knew crew nationalities” — webindia123.com · 11 Jun 2026, 07:15 · mainstream media
“US armed forces strike on a vessel off the coast of Oman” — vz.ru · 11 Jun 2026, 07:15 · mainstream media
The attack occurred off the coast of Oman near the Strait of Hormuz, within a critical chokepoint and a JWC-listed war risk zone.▾
location_gulf_of_oman_hormuzzone war risk attentionvalid from 11 Jun 2026, 00:00Marine
Market relevance: Location places the event inside JWC-listed war risk waters, material to marine hull war and P&I war risk underwriting.
One source characterises the vessel as a tanker; this characterisation is not independently corroborated.▾
vessel_type_tanker_reportedvessel type pendingMarine
Market relevance: If confirmed as an oil or chemical tanker, cargo and pollution considerations may arise under P&I and charterers' liability covers.
Arrests have been reported in connection with the incident and authorities / negotiations are involved in response.▾
response_arrests_conductedresponse ongoingMarine
Market relevance: Detention and crew repatriation scenarios may affect P&I exposure but no asset value impact is implied.
The attack area falls within waters commonly associated with JWC-listed war risk zones for marine hull and crew covers.▾
war_risk_zone_jwc_listedzone war risk attentionMarine
Market relevance: JWC listing anchors war risk premium and policy trigger considerations for hull and P&I war covers.
The vessel attack occurred near the Strait of Hormuz / Omani waters based on GDELT location signals.▾
vessel_attack_location_near_hormuz_omancontextvalid from 11 Jun 2026, 05:00Marine - Hull War
Market relevance: Determines whether hull war risk or standard marine hull applies; affects underwriting zone and premiums.
21 of the 24 Indian crew members have been rescued.▾
vessel_attack_21_rescuedinsured lossvalid from 11 Jun 2026, 05:00Marine - P&I
Market relevance: Indicates crew survivorship and potential P&I liability for injuries.
The vessel carried 24 Indian crew members at the time of the attack.▾
vessel_attack_total_crew_indian_24insured lossvalid from 11 Jun 2026, 05:00Marine - P&I
Market relevance: Defines scale of P&I exposure to crew claims.
One source attributes the attack to US armed forces; attribution is not independently corroborated.▾
attacker_attribution_us_armed_forces_unconfirmedwar risk classificationvalid from 18 Jun 2026, 01:58Political Risk / Political Violence
Market relevance: If substantiated, materially shifts war risk and liability treatment including political violence and bilateral state responsibility.
“Indien: Drei tote Seeleute nach US-Angriff auf Tanker gefunden” — n-tv.de · 11 Jun 2026, 09:15 · mainstream media
Arrests have been reported in connection with the incident.▾
arrests_made_reportedcontextvalid from 18 Jun 2026, 01:58Political Risk / Political Violence
Market relevance: May indicate state or military involvement; relevant to attribution and war risk classification.
initial source · 18 Jun 2026, 03:25
Authorities and negotiations are involved in response.▾
authorities_negotiations_involvedcontextvalid from 18 Jun 2026, 01:58Political Risk / Political Violence
Market relevance: Diplomatic engagement context; relevant to ceasefire stability and escalation assessment.
initial source · 18 Jun 2026, 03:25
Indian authorities and the Ministry of External Affairs are engaged in negotiations regarding the incident.▾
vessel_attack_negotiations_underwaycontextvalid from 11 Jun 2026, 05:00Marine - P&I
Market relevance: Government response may influence hostage/kidnap liability treatment under P&I and K&R policies if applicable.
Arrests have been made in connection with the incident.▾
vessel_attack_arrests_madecontextvalid from 11 Jun 2026, 05:00Marine - P&I
Market relevance: Suggests criminal/maritime security response; not directly an insured loss.
Uncertain21 lines
Vessel name, flag state, ownership, and operator▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Location of the attack (waters, port, or anchorage)▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Nature of the attack (piracy, armed robbery, military strike, or other)▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Whether the vessel was hijacked, detained, or continued voyage▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Cargo type and value▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Whether the vessel sustained hull damage or total loss▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Chief engineer reported as missing by one source and as confirmed dead by another.▾
chief_engineer_status_conflictcrew liabilityvalid from 18 Jun 2026, 01:58Marine
Market relevance: Affects crew fatality count and P&I exposure quantification.
initial source · 18 Jun 2026, 03:25
“Indien: Drei tote Seeleute nach US-Angriff auf Tanker gefunden” — n-tv.de · 11 Jun 2026, 09:15 · mainstream media
Indian officials attribute one of the three attacks to a US naval strike, reportedly involving Hellfire missiles; this attribution is not independently corroborated by the available sourcing.▾
attack_attribution_us_naval_strike_hellfire_unconfirmedliability determinationvalid from 18 Jun 2026, 19:31Marine - Hull War
Market relevance: Confirmation would materially shift war risk and liability treatment
The vessel name, flag state, ownership, and operator have not been disclosed in available reporting; no hull total loss has been confirmed.▾
vessel_identity_ownership_undisclosedvaluation constraintvalid from 18 Jun 2026, 19:31Marine - Hull War
Market relevance: Limits ability to quantify insured value exposure
Location of the attack (specific waters, port, or anchorage) is not specified in source.▾
vessel_location_waters_unknowncoverage triggervalid from 18 Jun 2026, 01:58Marine
Market relevance: Precise location affects war risk zone classification and policy trigger.
initial source · 18 Jun 2026, 03:25
Cargo type, quantity, and value are not disclosed in available sources.▾
cargo_status_unknownidentification gapMarine
Market relevance: Without cargo data, cargo and pollution liability pathways cannot be assessed.
Vessel name, flag state, ownership, operator, and registered tonnage are not disclosed in the available sources.▾
vessel_identification_unknownidentification gapMarine
Market relevance: Without vessel identification, insured value, flag, and tonnage cannot be determined, limiting the London Market loss pathway assessment.
Vessel name, flag state, ownership, operator, and IMO number are not disclosed in the source.▾
vessel_attack_vessel_identity_unknowncontextMarine - Hull
Market relevance: Without vessel identification, insured value and policy attachment cannot be confirmed.
Whether the attack constitutes piracy, armed robbery, or another incident type is not specified in the source.▾
vessel_attack_nature_of_attack_uncertaincontextMarine - Hull War
Market relevance: Determines applicability of piracy/armed robbery clauses under hull and P&I policies.
Cargo type and value are not disclosed in the source.▾
vessel_attack_cargo_unknowncontextMarine - Cargo
Market relevance: Cargo-related losses and cargo policy exposure cannot be assessed.
Whether the vessel sustained hull damage or total loss is unconfirmed.▾
hull_damage_or_total_loss_unconfirmedexposure identificationvalid from 18 Jun 2026, 01:58Marine
Market relevance: Without hull damage confirmation, marine hull war risk loss cannot be quantified.
initial source · 18 Jun 2026, 03:25
No source confirms hull damage, total loss, or commercial asset impact to the vessel.▾
hull_damage_status_unknowndamage pendingMarine
Market relevance: Absent confirmed hull damage or total loss, marine hull war exposure cannot be sized.
No information on hull damage, total loss, or remaining operational status of the vessel is available.▾
vessel_attack_hull_damage_unknowncontextMarine - Hull
Market relevance: Without damage evidence, hull loss pathway cannot be confirmed.
Vessel name, flag state, ownership, and operator are not disclosed in available sources.▾
vessel_identity_undisclosedexposure identificationvalid from 18 Jun 2026, 01:58Marine
Market relevance: Without vessel identification, insured value and policy attachment cannot be assessed.
initial source · 18 Jun 2026, 03:25
Cargo type and value are not disclosed in available sources.▾
cargo_undisclosedexposure identificationvalid from 18 Jun 2026, 01:58Marine Cargo
Market relevance: Without cargo disclosure, marine cargo war risk exposure cannot be quantified.
initial source · 18 Jun 2026, 03:25
Without identified vessel, insured value, trading area confirmation, or hull damage assessment, a concrete London Market hull loss pathway cannot be established; crew P&I exposure is plausible but scale is unclear.▾
london_market_loss_pathway_constrainedpathway constrainedMarine
Market relevance: Loss-pathway uncertainty constrains market materiality; P&I crew-life exposure is most plausible but unquantified.
Affected countries
🇦🇪 United Arab Emirates🇧🇭 Bahrain🇮🇳 India🇮🇷 Iran🇰🇼 Kuwait🇴🇲 Oman🇶🇦 Qatar🇸🇦 Saudi Arabia
+2 more
Latest developments
- Multiple sources confirm Indian seafarer fatalities from a vessel attack in the Gulf of Oman area. — aninews.in
- Location corroborated to Gulf of Oman waters near Oman. — russiaherald.com
- Reporting describes a pattern of three Indian-crewed vessel attacks within four days in the same waters. — russiaherald.com
- India has summoned the US Charge d'Affaires for a second time over the vessel strikes. — russiaherald.com
- Attribution to US forces is asserted by Indian officials but not independently corroborated. — aninews.in
- Vessel identity, flag, and ownership remain undisclosed in available reporting. — russiaherald.com
- Indian officials cite hundreds of Indian crew members deployed on vessels in affected waters. — russiaherald.com
- Multiple Indian ministries are engaged in the diplomatic and welfare response. — russiaherald.com
Timeline
Status Change19 Jun 2026, 10:31
Status changed to monitoring
Auto-transitioned: no updates for 6 hours
active -> monitoring
Intelligence Refresh18 Jun 2026, 19:34
Intelligence Refresh18 Jun 2026, 03:25
Intelligence Refresh17 Jun 2026, 15:29
Status Change17 Jun 2026, 05:01
Status changed to active
hygiene_sweep: re-evaluated after confidence recalibration
developing -> active
Status Change17 Jun 2026, 05:01
Status changed to developing
evidence_trigger: corroboration >= 2
signal -> developing
Corroboration17 Jun 2026, 04:14
A maritime vessel was attacked near the Strait of Hormuz resulting in two Indian sailor fatalities and one chief engineer missing, according to the Seamen's Union of India. The incident occurs in one of the world's most critical chokepoints for global energy shipments and lies within a JWC-listed war risk area. This represents a direct insured loss event with implications for marine hull, war risk, and P&I underwriters operating in the Persian Gulf.
Source: indiatimes.com (Mainstream Media) · View source
Corroboration17 Jun 2026, 04:12
Two Indian sailors are dead and the chief engineer is missing following an attack on a vessel in waters near the Strait of Hormuz, a critical chokepoint for global energy shipments. The incident, which also involves crew detentions, raises concerns about escalating maritime violence in the Persian/Arabian Gulf corridor and has direct implications for war risk, marine hull, and P&I insurance markets operating in JWC-listed waters.
Source: timesofoman.com (Mainstream Media) · View source
Lloyd's classifications
Tracking this kind of risk? Get an email when Marine events escalate.
Get alerts