31JUL

UKMTO confirms one tanker hit near Bukha

3 min read

09:33UTC

Britain's maritime desk recorded a tanker struck off Oman and a projectile report with no damage off Iraq; the one named casualty, the Kuwait-flagged tanker Al Dasma, survived its second attack.

← Back to Insurers shut Bab el-Mandeb to Saudi hulls Jump to analysis ↓

EconomicDeveloping

Key takeaway

UKMTO has confirmed one tanker hit this week, far fewer than Tehran claims.

United Kingdom Maritime Trade Operations (UKMTO), the Royal Navy's merchant-shipping desk, reported a tanker struck about 11 nautical miles west of Bukha in Oman early on Wednesday 21 October, with the fire out and the crew safe⁠¹. A day earlier it recorded a master's report of an unknown projectile, with no damage, 30 nautical miles south-east of Al Faw, Iraq. It named neither ship.

That is the independent record set against the Islamic Revolutionary Guard Corps (IRGC), which claims to have hit far more ships this week without naming one. The JMIC (Joint Maritime Information Center, a US-led naval reporting cell) said of the IRGC's 17 October mine claims that "there is no substantiation" to them⁠². CENTCOM spokesman Captain Tim Hawkins told Fox News Digital that the "vast majority" of Iranian attacks had failed and that about 97% of ships seeking transit got through, a figure CENTCOM did not break down⁠³.

One ship does have a name. An unknown projectile hit the Kuwait-flagged product tanker (one carrying refined fuel) Al Dasma in the strait, on 21 October local time by India's account and on 20 October by the International Maritime Organization's (IMO), its second attack on the IMO's list⁠⁴. New Delhi says its Indian crew came through unhurt.

The counts of the wider campaign do not match. The IMO put confirmed maritime security incidents at 119, with 24 seafarers killed, by 22 October⁠⁵; the JMIC counted 153 confirmed incidents since 1 March in its 18 October advisory⁠⁶. Neither body explains the gap, so no single official tally of attacks on shipping exists. IMO Secretary-General Arsenio Dominguez said about 6,000 seafarers remain trapped, down from about 11,000 when Iran shut the evacuation corridor in June, and urged ships not to transit "until we have guarantees"⁠⁷.

Deep Analysis

In plain English

The United Kingdom Maritime Trade Operations (UKMTO) is a Royal Navy office that collects reports from ships about attacks and threats. The International Maritime Organization (IMO) is the UN agency that sets rules for world shipping. Since the war began, many ships and their sailors have been unable to leave The Persian Gulf safely. Attacks keep happening, and the people on board those ships are often from India, the Philippines and other countries far from the fighting.

Deep Analysis

Root Causes

Seafarers stay trapped because leaving needs three things at once: a safe route, an owner willing to risk the hull, and insurers who will cover the voyage. Removing any one of them keeps the ship at anchor.

Flag states add a second constraint. Crew welfare rests with the flag state, yet many trapped ships fly open-registry flags such as Panama or Liberia, whose states have no navy in The Gulf and little leverage over Tehran.

What could happen next?

Risk
A second strike on the same named tanker raises the chance that attackers are selecting ships by owner or flag, not at random.
Consequence
Crew rotation problems on trapped ships are likely to become a labour and welfare dispute between unions, owners and flag states.

Source Landscape

This story draws on neutral-leaning sources from United States

United States×3

LeftRight

Primary parallel: When Egypt closed the Suez Canal in June 1967, 15 merchant ships were trapped, 14 of them in the Great Bitter Lake, the so-called Yellow Fleet. When the canal reopened in 1975 only two could leave under their own power.

Counter-parallel: At the start of Russia's 2022 invasion, about 2,000 seafarers were stuck in Ukrainian ports. A UN-brokered humanitarian corridor and the Black Sea Grain Initiative moved most ships out within months, because both belligerents had an export interest in the sea lane.

A ship stuck at anchor still pays crew wages, provisions and running costs while earning nothing, and its charter may be suspended under war clauses. Owners face a choice between paying to wait and paying war-risk premiums to run.

The Al Dasma's second listed attack also raises its own repair and insurance profile. A twice-hit hull becomes harder to charter at normal rates even after repair.

Consensus view: The Joint War Committee of London underwriters lists 'areas of perceived enhanced risk', where owners must notify underwriters of voyages; premiums are then negotiated ship by ship.

Counter-view: The International Transport Workers' Federation has documented pay delays, abandonment and supply shortages for seafarers trapped in The Gulf this year. None of that harm appears in an incident count, which logs attacks on hulls.

Key tension: Whether official tallies should count attacks on hulls or the condition of the 6,000 people aboard ships that cannot leave.

First Reported In

Update #182 · Iran says it mined Hormuz and hit 7 ships

gCaptain· 22 Oct 2026

Read original →

Causes and effects

Caused by

GFS Pride sinks in the Strait of Hormuz

Projectile attacks in the strait continued after the GFS Pride sinking, with the Al Dasma hit.

Occurred 13 Oct 2026

Read story →

This Event

UKMTO confirms one tanker hit near Bukha

The independent record of attacks on Gulf shipping is far thinner than the IRGC's claims, and the official tallies do not agree.

Led to

India says Saudi attacks must stop

India's shipping minister reported on the Indian crew of the struck Al Dasma.

Occurred 22 Oct 2026

Read story →

UKMTO reports tanker disabled in Hormuz

UKMTO's report of a disabled tanker on 23 October followed its logs of strikes off Bukha and Al Faw.

Occurred 23 Oct 2026

Read story →

JMIC warns of renewed mining in Hormuz

The JMIC warned of renewed mining eight days after finding no substantiation for IRGC mine claims.

Occurred 25 Oct 2026

Read story →

Different Perspectives

Gulf oil producer

Secured OPEC's confirmed 188,000 b/d September increment with the next meeting set for 6 September, but the Secretariat's own 2 August release says nothing about the fourth quarter. Output guidance beyond September remains undisclosed even as delegate sourcing keeps filling that gap.

Money manager positioned in WTI

Added 28,964 lots to a 92,943 net long in NYMEX WTI in the week to 28 July, against just 1,485 added to Brent's 15,740, a roughly twenty-to-one split. Conviction sits in the American benchmark even as the European diesel story sets the record.

Indian refiner buying Urals

Bought Russian crude at a discount that narrowed to $1-2 a barrel in the week to 29 July from over $10, as Hormuz risk pushed it toward Urals. If that risk eases with the strike now called off, the discount it is currently enjoying could re-widen just as fast.

Russian diesel exporter

Novak tied any lifting of the diesel export ban, due to lapse 31 July, to an unspecified market recovery with no date, and pushed the gasoline ban to end-2026. An open-ended constraint suits an exporter benefiting from the record European crack it feeds.

War-risk underwriter

Withdrew war-risk cover for Saudi-linked hulls on 24 July and has not reinstated it, holding Bab el-Mandeb tanker transits near 7.5 a day. A cancelled strike does not by itself trigger the committee review needed to re-accept the class.

Northwest European refiner

Sources only 17% of diesel imports from Saudi Red Sea ports against the Mediterranean's 24%, so the ARA crack at $85.86 trails the Med print by $5.81. Lower Red Sea exposure is cushioning it against the rerouting cost, not eliminating it.

Written with AI from Lowdown's published reporting. Not individually reviewed by an editor. Editorial standards.