19JUN

First sailors die in the tanker war

2 min read

12:07UTC

The IRGC disabled two supertankers in Omani waters on 14 July, killing one seafarer by UAE count and two by the International Maritime Agency's, the first crew deaths of the shipping war.

← Back to Trump lifted the blockade, not the strait Jump to analysis ↓

ConflictDeveloping

Key takeaway

The first crew deaths give war-risk insurers a body count to cite, freezing even legally shippable Gulf cargoes.

The Islamic Revolutionary Guard Corps (IRGC) disabled two supertankers in Omani waters on 14 July, saying it acted after "repeated warnings" ¹. United Arab Emirates (UAE) reporting put the crew toll at one killed; the International Maritime Agency counted two seafarers dead ². Every prior tanker strike had produced damage without confirmed fatalities, from the Qatari carrier Al Rekayyat on 7 July to the container ship GFS Galaxy on 12 July, both of which left crews shaken but alive.

Those deaths sharpen the insurance squeeze that has strangled the strait since the first strike. London's Protection and Indemnity (P&I) clubs have held their Hormuz war-risk exclusion in force since Al Rekayyat , and a confirmed fatality gives underwriters a harder reason to keep it there. Licensed cargoes cannot sail while the exclusion stands, whatever a sanctions licence permits, so the human cost feeds straight back into the freight that is not moving.

One caution on the count itself. Neither the one-death nor the two-death figure has been independently corroborated, and the discrepancy between the UAE and the International Maritime Agency is unresolved ³.

Deep Analysis

In plain English

Ships have been damaged in the strait for months without anyone dying. This is different because sailors were actually killed, which raises the moral and legal stakes and makes any future strike harder to treat as an acceptable risk of doing business.

Deep Analysis

Root Causes

The competing casualty counts stem from parallel, uncoordinated reporting chains: UAE authorities report through their own maritime rescue apparatus while the International Maritime Agency compiles figures from vessel operators and insurers, with no shared methodology for confirming a death at sea.

A deeper cause is the absence of a sanctioned exit route: the IMO evacuation corridor has been suspended since the Ever Lovely strike in late June, leaving crews with no safe passage and raising the odds that any strike produces a confirmed fatality rather than a near-miss.

What could happen next?

Consequence
Confirmed deaths, rather than vessel damage, typically harden flag-state and insurer positions on a route permanently rather than provisionally, raising the odds that Hormuz war-risk premiums stay elevated even if the blockade itself eases.

Source Landscape

This story draws on centre-left-leaning sources from Qatar

Qatar

Primary parallel: A tugboat aiding the tanker Safeen Prestige was struck in March, killing eight crew, and US forces killed three Indian sailors aboard the tanker MT Settebello in June after it failed to comply with a boarding attempt; confirmed maritime deaths have accumulated on both sides of this war.

Counter-parallel: The GFS Galaxy and Al Rekayyat strikes attributed to the IRGC in the fortnight before this incident caused heavy damage but no confirmed deaths, making 14 July the point where that pattern broke.

Consensus view: The International Maritime Organization has tracked Hormuz incidents by vessels struck and seafarers killed since the war began; this is the first entry in that tally with a confirmed death rather than damage alone.

Counter-view: Gulf and Iranian commentary has stressed the IRGC's own account of 'repeated warnings' issued before the tankers were disabled, framing the deaths as the foreseeable result of ignoring an announced closure rather than a targeted killing of civilian mariners.

Key tension: Why the death count itself is contested, one under UAE reporting, two under the International Maritime Agency, a gap that matters for how the incident is classified and, potentially, prosecuted.

Sources:Al Jazeera

Mentions:Islamic Revolutionary Guard Corps (IRGC) →International Energy Agency →United Arab Emirates (UAE) →Oman →GFS Galaxy →MT Settebello →Al Rekayyat →London →International Maritime Organization →Protection and Indemnity (P&I) →

First Reported In

Update #154 · US enforces Hormuz closure with blockade

Al Jazeera· 15 Jul 2026

Read original →

Causes and effects

Caused by

IRGC missiles hit a Qatari gas tanker

The first confirmed tanker deaths follow the earlier Al Rekayyat strike, which caused damage but no fatalities.

Occurred 6 Jul 2026

Read story →

IRGC strikes GFS Galaxy, shuts Hormuz

Confirmed deaths follow the GFS Galaxy strike two days earlier, which left crew shaken but alive.

Occurred 12 Jul 2026

Read story →

This Event

First sailors die in the tanker war

A confirmed body count hardens the war-risk insurance exclusion that has kept licensed cargoes off the strait since the first tanker strike.

Different Perspectives

Lloyd's Market Association

War-risk underwriters price the Houthis' Red Sea attacks because the group announces its targets in advance, but the unclaimed Damietta drone gives insurers a hit with no author to price against. An attack nobody claims costs shipping more than one that is claimed, since premiums are set against a known pattern, not raw damage.

US Central Command

CENTCOM has announced no strike on Iran since resuming bombing on 30 July within hours of an IRGC salvo on Jordan, and centcom.mil did not respond to requests to confirm any pause. The command has gone quiet before while a larger operation was being weighed, so silence alone proves nothing about what it has or has not done.

Hengaw

Hengaw recorded at least 67 executions in Iran during July, of which the state acknowledged only eight, and reported the 1 August execution of protest detainee Arvin Kheirkhahan at Shahrud with no advance notice to his family. A family's first notice of a death sentence is now usually the instruction to collect a body.

Egypt

Egypt's government asked media on 2 August to report the Damietta attack accurately, named no author, and said no findings will be published before its own investigation concludes. Cairo holds the debris and jurisdiction over an attack on its own soil, and naming a culprit now would pull it into a dispute it has avoided for five months.

Iran's Foreign Ministry

Araghchi called the Hormuz talks with Oman final-stage on 2 August, four days after his own deputy rejected Oman's lane proposal, and denied the Damietta drone strike as an Israeli false flag while two Iranian officials privately claimed it for Tehran. Iran's public position now contradicts itself on both files at once.

Bahrain and Kuwait

Bahraini and Kuwaiti aircraft flew their own strikes on Iranian depots in July with Emirati air cover behind them, and Ynetnews reports some Gulf capitals wanted the 2 August strike to proceed rather than stop. States that have already taken fire see a closing window on Iranian weakness, not a reason to pause.