Skip to content
Briefings are running a touch slower this week while we rebuild the foundations.See roadmap
European Tech Sovereignty
10JUN

Hellfire disables a cargo ship's engine

3 min read
10:31UTC

CENTCOM fired a Hellfire missile into the engine room of the Gambian-flagged M/V Lian Star in the Gulf of Oman around 30 May, the blockade's first disabling of a commercial hull by munition.

← Back to Sovereignty law adopted; $40bn US chip buyJump to analysis ↓
TechnologyDeveloping
Key takeaway

The blockade crossed a threshold: from redirecting ships to destroying a civilian hull's ability to move.

CENTCOM (US Central Command) disabled the Gambian-flagged bulk carrier M/V Lian Star in the Gulf of Oman around Saturday 30 May, firing a Hellfire missile into its engine room after the crew ignored more than 20 blockade warnings 1. The Hellfire is a US precision air-to-ground missile. CENTCOM is the US combatant command that has run the Hormuz blockade since mid-April.

CENTCOM disabled the ship rather than seizing it, leaving its civilian crew aboard a powerless hull, and its cumulative redirection count reached 116 vessels. Every prior interdiction had turned ships away or boarded them.

This is the first time the 90-day blockade has crossed into disabling a commercial hull by munition. The rules of engagement have hardened beyond the Bandar Abbas strikes on Iranian naval targets , which hit military boats and a missile site rather than a merchant ship.

The shift changes the risk calculus for civilian shipping near the blockade zone. A disabled hull adrift with crew aboard also widens Washington's legal exposure under maritime law, where a powerless ship in a busy strait is itself a hazard to other traffic.

Deep Analysis

In plain English

US forces fired a Hellfire missile (a precision weapon normally used to destroy tanks or targeted vehicles) into the engine room of a cargo ship, leaving it unable to move. In 90 days of blockade operations, CENTCOM had previously boarded or redirected 115 vessels. This is the first time it destroyed a commercial vessel's propulsion using a missile. Lian Star's crew, stranded on a powerless hull, cannot leave under their own power. The ship is registered in Gambia, not Iran, meaning the US struck a third-country commercial vessel. Under international maritime law, firing on a non-combatant commercial vessel requires proportionality and exhaustion of lesser means; CENTCOM issued more than 20 warnings before firing.

Deep Analysis
Root Causes

The Lian Star disabling reflects a rules-of-engagement progression that began at redirection (week 1), moved to boarding (week 2), then to Iranian-hull disabling (week 3), and has now reached third-flag hull disabling (week 11). Each step was preceded by a specific compliance failure. The Lian Star's crew ignored more than 20 warnings, which CENTCOM treated as sufficient justification for escalation to munition.

The underlying structural driver is that the blockade's earlier deterrent credibility eroded: 116 cumulative redirections still produced vessels attempting to run the zone. CENTCOM needed a cost-imposing action that fell short of sinking to restore deterrence without triggering a humanitarian crisis.

What could happen next?
  • Precedent

    Third-flag commercial vessels are now subject to propulsion-kill rules of engagement if they attempt to run the blockade zone after 20 warnings, a doctrinal expansion CENTCOM has not formally published.

    Immediate · Assessed
  • Risk

    Gambia as flag state faces liability questions for its vessels in the blockade zone; smaller flag-state registries may accelerate flag-switching away from the Gulf.

    Short term · Assessed
  • Consequence

    Lloyd's of London's war-risk underwriting committee will need to price a new risk category: propulsion-destruction of insured hulls by US munition, not just mine or missile damage from hostile actors.

    Short term · Assessed
Sources:CBS News·ABC News
Mentions:M/V Lian Star →CENTCOM (US Central Command) →Oman →Strait of Hormuz →Tanker War →Gulf of Oman →Operation Praying Mantis →Iran →IISS →RAND Corporation →US Navy →Washington →Bandar Abbas →Strait of Hormuz Toll System →Hellfire →
First Reported In

Update #113 · Trump signs nothing as a Hellfire hits a hull

CBS News· 31 May 2026
Read original →
Causes and effects
This Event
Hellfire disables a cargo ship's engine
Crossing from redirection to munition-disabling of a civilian ship hardens the blockade's rules of engagement beyond any prior interdiction, including the Bandar Abbas naval strikes.
Led to
CENTCOM hits Goruk and Qeshm Island
The Goruk/Qeshm strikes extend the kinetic lineage from the Hellfire strike on the Lian Star.
Occurred 31 May 2026
Read story →
Trump: blockade stays till deal signed
The Lian Star Hellfire disabling escalates the prior blockade-stays-till-signed posture from redirection to propulsion destruction by munition.
Occurred 24 May 2026
Read story →
US strikes Iran's naval base mid-talks
The Lian Star strike escalates beyond the prior CENTCOM Bandar Abbas strikes on Iranian naval targets to the first disabling of a commercial civilian hull by munition.
Occurred 25 May 2026
Read story →
Blockade hits 121 ships, one holed
CENTCOM's 116-vessel redirect total on 30 May was the baseline from which the 121-vessel figure on 1 June represents a continuation and widening.
Occurred 1 Jun 2026
Read story →
Different Perspectives
European cloud and open-source industry
European cloud and open-source industry
European cloud providers gain a binding procurement mandate from CADA, confirmed by Gartner's $12.6bn sovereign-cloud figure for 2026. The $40bn Pax Silica commitment signals Brussels will not extend sovereignty discipline to the silicon layer, and the missing €350m Sovereign Tech Fund leaves open-source maintenance infrastructure unfunded beneath those same clouds.
United Kingdom
United Kingdom
Science Secretary Kendall's £1.1bn Hardware Plan on 8 June chose demand-side instruments, advancing £150m to British chip startups via the British Business Bank, where Brussels chose supply-side alliance membership. Britain joined Pax Silica before the EU and has no collective EU procurement leverage; the Hardware Plan is the bilateral answer to the same silicon gap.
United States
United States
Pax Silica, a State Department initiative launched in December 2025, secured EU membership the same afternoon Brussels adopted its cloud sovereignty law. Ambassador Puzder had named CADA a red line against the EU-US trade framework; the narrowed CADA scope and the $40bn chip commitment together represent the settlement Washington sought.
France
France
France was the only EU state to oppose Pax Silica accession at COREPER on 3 June, asking the Commission to clarify the Council's steering role inside the alliance. Paris backed CADA and hosts Mistral AI; a $40bn US-chip commitment contractually narrows the commercial space for the sovereign AI model that France is trying to scale.
European Commission
European Commission
Von der Leyen framed CADA on 3 June as keeping 'most of our market open to like-minded partners', and the Commission's EVP Virkkunen simultaneously required majority-European ownership for the €4.12bn AI Gigafactories call. Brussels is managing rather than resolving the silicon dependency by asserting regulatory control at the cloud layer while formalising the chip relationship through Pax Silica.
European Central Bank
European Central Bank
The ECB's digital euro pilot drew more than 50 PSP applications and is naming 10 to 30 participants in July, advancing on its own monetary mandate without requiring a Commission act. Its trajectory this week is the inverse of CAIDA's: the sovereignty instrument that restricts no US firm is the only one keeping its published calendar.