16JUN

Trump orders Navy to shoot mine-layers

3 min read

10:20UTC

Donald Trump instructed the US Navy to shoot any Iranian vessel laying mines in the Strait of Hormuz, with minesweepers tripled up. CENTCOM intercepts climbed to 31 vessels. No military order was published.

← Back to Iran deal signed, but no paper to show Jump to analysis ↓

ConflictDeveloping

Key takeaway

Verbal shoot-kill order leaves CENTCOM commanders executing rules of engagement no court can read.

Donald Trump on Thursday 23 April ordered the US Navy to "shoot and kill any Iranian vessel laying mines in the strait", with minesweepers to clear it "at a tripled up level"⁠¹. US Central Command (CENTCOM), which runs Middle East operations, saw its cumulative intercept count climb from 28 on Day 54 to 31 vessels directed to turn around or return to port by Friday. No published military order accompanied the instruction.

The instruction tightens rules of engagement in one of the world's most congested maritime chokepoints without anything a Navy lawyer can point to in writing. CENTCOM officers are operating on the 28 February strike authorisation that Congress never ratified, layered with verbal presidential force authority. No published military order and no Iran executive instrument accompany the command, the same paper gap that has run across 55 days of war.

The mine-clearance assumption sits awkwardly against prior Pentagon internal estimates that Hormuz mine clearance requires six months of sustained operations. "Tripled up" minesweeper cadence compresses that timeline only if deployment assets match the talking point, and at the moment those assets remain on escort duty rather than clearance. The ratio of talk to hull matters because every additional mine-layer attempt the Navy engages under verbal authority expands the legal exposure of the officers executing it.

Kingsley Wilson's refusal to comment on internal deliberations on the same day kept the Pentagon's written record deliberately thin. Three separate lines now converge on unsigned coercion: verbal force authority in the strait, unsigned sanctions via OFAC NSPM-2, and an internal Pentagon memo threatening allies. Each runs on paper that does not yet exist.

Deep Analysis

In plain English

On 23 April, President Trump told reporters the US Navy should 'shoot and kill' any Iranian vessel it catches laying mines in the strait of Hormuz, the narrow channel that most of the world's oil passes through. He also ordered minesweepers to work at triple their normal pace. No written military order accompanied either instruction. The Navy operates on detailed written rules specifying when it can open fire. Without a written order, individual ship commanders face a legal grey area: they have presidential words but no signed document. Trump has signed zero Iran-related executive documents across 55 days of war, and this order follows the same pattern.

Deep Analysis

Root Causes

The verbal shoot-kill order reflects the same no-signed-paper architecture that governs the broader campaign. CENTCOM's cumulative intercept count at 31 vessels rests on the 28 February strike authorisation, itself unsigned by Congress. Adding a new written force authority for mine-laying vessels would require either a new executive order or an AUMF, either of which creates a legal instrument that constrains The White House's later discretion on ceasefire terms.

The Pentagon briefed the House Armed Services Committee on 22 April that Hormuz mine clearance could take six months and would not begin until the war ends. A verbal engagement order against mine-layers is the executive response to a threat the military has already characterised as a six-month problem: it signals intent without creating the legal record that a mine incident followed by congressional inquiry would require The Administration to produce.

What could happen next?

Risk
A US Navy engagement of an Iranian mine-laying vessel without published rules of engagement creates simultaneous legal exposure for individual commanders under the UCMJ and political exposure for the administration under the War Powers Resolution.
Precedent
Verbal engagement orders for lethal force in the Strait of Hormuz, if uncontested by courts or Congress, establish that the president can authorise mine-warfare engagements through press-pool statements without producing a signed instrument.

Source Landscape

This story draws on centre-left-leaning sources from United States

United States

Primary parallel: In April 1988, during Operation Praying Mantis, the Reagan administration gave the US Navy verbal rules of engagement for the largest US naval engagement since World War II, destroying two Iranian oil platforms and sinking or disabling six Iranian vessels in a single day.

That operation had no signed congressional authorisation and rested on executive-branch self-defence claims under Article II. It established that US presidents can direct naval lethal force in the strait of Hormuz under verbal authority and have it judicially unreviewed.

Counter-parallel: The 1964 Gulf of Tonkin incident demonstrates the inverse: a disputed naval engagement in ambiguous waters produced a congressional resolution (the Gulf of Tonkin Resolution) that the Johnson administration used as the statutory basis for the entire Vietnam escalation. The difference in 2026 is that Congress has now voted down the War Powers mechanism five times without producing an AUMF, creating a record of affirmative non-authorisation rather than passive acquiescence.

Consensus view: Quincy Institute scholar Trita Parsi assesses that a verbal shoot-kill order issued via press pool and not embedded in a published rules of engagement document creates an operational ambiguity the US Navy cannot resolve through standing procedures: Rules of Engagement Annexes require written authorisation at combatant command level; absent that annex, individual commanding officers face personal liability under the Uniform Code of Military Justice if an engagement produces civilian casualties or damages a third-flag vessel.

Counter-view: Istituto Affari Internazionali (Rome) analyst Silvia Francescon argues the verbal order is legally coherent within the existing 28 February strike authorisation framework, which Congress never ratified but also never formally rejected. The verbal order supplements a pre-existing unsigned force authority rather than creating an entirely new one, making it harder to challenge than it appears.

Key tension: Whether a verbal presidential order to 'shoot and kill' meets the constitutional and statutory threshold for lethal force engagement in a conflict where no formal declaration of war or AUMF has been signed.

First Reported In

Update #78 · Allies flagged, adversaries listed, nothing signed

Time· 24 Apr 2026

Read original →

Causes and effects

Caused by

Pentagon gives Congress Hormuz clock Trump has not

Shoot-kill order escalates from the Pentagon HASC mine-clearance briefing describing a six-month post-war operation

Occurred 22 Apr 2026

Read story →

IRGC boards three ships inside Hormuz

Shoot-kill order directly responds to the 22 April IRGC seizures and firings in Hormuz

Occurred 22 Apr 2026

Read story →

This Event

Trump orders Navy to shoot mine-layers

Rules of engagement in a contested waterway now run on verbal presidential authority rather than signed paper.

Led to

CENTCOM intercepts reach 33 in the Strait

CENTCOM intercepts reaching 33 escalates from 31 in update #78, maintaining the one-to-two per day pace

Occurred 25 Apr 2026

Read story →

Sentinel-2 catches 33 IRGC boats off Kargan

The Sentinel-2 recording of 33 IRGC fast-attack craft north of Hormuz on 23 April sits in the same posture as Trump's verbal shoot-kill order for Iranian mine-layers, with both sides concentrating assets without paper governing their use.

Occurred 23 Apr 2026

Read story →

Third US carrier reaches CENTCOM theatre

Trump's verbal shoot-kill order for Iranian mine-layers preceded and contextualised the deployment of the third carrier completing three-carrier concentration.

Occurred 24 Apr 2026

Read story →

Different Perspectives

United States (Joint Maritime Information Center)

The JMIC, the US-led naval reporting cell, rated the Hormuz threat "severe" in its 25 October advisory, as reported by gCaptain, and warned of possible renewed mining. Eight days earlier it found no substantiation for the Guards' mine claims, while US-facilitated transits ran at about 34 a day.

United Kingdom (CPS and Counter Terrorism Policing)

The CPS charged two men under the National Security Act 2023 over the RAF Fairford incident, and Counter Terrorism Policing said it believes the foreign intelligence service involved is Iran's, LBC reported. The case now runs through the courts; both men are charged, not convicted.

Aden and Yemen's recognised government

The Houthis told people to leave Aden airport, in the government-held south, before a missile fell there on 28 October, AFP reported, and police reported a second attack that afternoon. The fight between Riyadh and the Houthis is landing on the south's main civilian airport.

Qatar (mediators)

Qatar-led mediators put new terms to Iran this week, which an Iranian official called "ideas, not a proposal". Riyadh framed the Tehran meeting as support for Qatari and Pakistani mediation, keeping Doha at the centre of the indirect channel.

Korea Shipowners' Association

The association said the ships Iran listed were sub-chartered to an overseas oil company, not owned by Sinokor, carried no South Korean crew, and that Sinokor was unaware of the warning. South Korea's shipowners are contesting whose vessels the notice covers before it takes effect.

Kuwait (foreign ministry)

Kuwait summoned Iran's ambassador, Mohammad Toutounji, and handed him a protest note over the embassy's denial that its citizen took part in the alleged plot against Interior Minister Fahad Al-Yousef. Kuwait is answering through its courts and a diplomatic protest, citing international law and the UN Charter.

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