🔔 Subscribe to ShipUniverse Weekly →
A small boat approached the Panama-flagged crude tanker LOUISE 1 in the Strait of Hormuz on October 29 and attached two explosive devices to its hull, triggering an engine-room fire that temporarily disabled the vessel approximately 25 nautical miles northeast of Khasab, Oman. The attack, reported by UK Maritime Trade Operations in Warning 187-26, occurred during an outbound transit. The crew extinguished the fire, no injuries or environmental damage were reported, and the tanker resumed its voyage. Three maritime-security sources identified the vessel to Reuters as LOUISE 1, a 159,092-dwt tanker built in 2004. The attacker's identity remains unconfirmed. Reuters describes this as the first known successful limpet-mine strike in the waterway since the U.S.–Iran war began in February, following an unsuccessful attempt in September.
Two Explosions. One Disabled Tanker. A New Close-Range Security Threat.
LOUISE 1 survived the incident, but the attack introduces a different protection problem for vessels navigating the crowded Strait of Hormuz: explosive devices placed directly against a ship rather than launched from a distance.
How the Incident Developed
UKMTO Warning 187-26 was initially issued as suspicious activity. A subsequent verified update established that explosives had been attached to the hull.
Outbound Strait of Hormuz passage on October 29, 2026. UKMTO did not name the vessel; three maritime-security sources identified it to Reuters.
A small craft approached the outbound tanker. A later verified report described two explosive devices attached to the hull.
The explosions caused a fire and temporarily disabled the tanker. UKMTO identified the affected area as the engine room.
The crew extinguished the fire. UKMTO subsequently confirmed that all crew members were safe.
The tanker continued toward its next port. No environmental impact was reported at the time of the update.
No crew injuries reported by UKMTO. The ship was able to get underway again.
Temporary loss of propulsion or operational capability. The complete repair scope and class requirements were not published.
Neither UKMTO nor Reuters established which organization carried out the attack.
Current cargo volume, loaded condition, destination, repair estimate and insurance claims remain unverified.
The Threat Has Changed, Not the Entire Risk Environment
Missiles, aerial drones and unidentified projectiles can strike vessels without an attacking craft approaching the hull.
A small craft at close proximity creates an additional detection, access-control and post-incident inspection concern.
Machinery inspections, insurance notifications, port acceptance and charter-party time may become material even when a ship remains afloat.
Do Not Confuse the Three October 29 Hormuz Incidents
The shipping-security record contains distinct reports involving a burning dhow, a projectile-damaged tanker and an explosive-device attack. Their outcomes, evidence and operational implications differ.
What the Strait's Oil Flow Data Actually Show
The latest published EIA quarterly comparison provides context for the wider security environment. These are average oil-product and crude flows, not October 29 measurements and not a count of attacked tankers.
Prewar reference period reported by EIA, including crude oil, condensate and petroleum products.
Postwar quarterly average. The difference is approximately 77%, but it should not be used as a measure of flows on the day of the new attack.
Later Kpler tracking reported that crude movement reached at least 10.1 million b/d in an early-October reporting week, demonstrating that throughput conditions can change materially from quarter to quarter. The October figure covers crude, not the identical all-liquids category, so it is not shown as a directly comparable third bar.
Where the New Costs Could Appear
Surveys, repairs, machinery tests and possible class or flag-state requirements following an explosion and fire.
Existing war-risk terms, transit notification and additional premiums depend on policy conditions and vessel circumstances.
Disabled machinery or inspection delays can affect hire, laytime and schedule obligations, depending on charter terms.
Subsequent ports may require evidence that damage has been assessed and the vessel remains safe to operate.
Owners and Company Security Officers may need to review small-craft surveillance, response procedures and reporting.
Sanctions screening, insurer participation and tanker history can influence practical vessel availability.
What Does Heightened Hormuz Security Cost a Tanker Fleet?
Model voyage-level war-risk premiums, security expenses and the additional cost of inspections or delays. Compare a cautious operating case with more extensive disruption scenarios, without assuming that every tanker will be attacked.
Operating Assumptions
Modeled Fleet-Wide Additional Expense
This is an illustrative added-cost budget across the selected number of tanker voyages. It does not represent expected accident losses or an estimate of actual October 29 claims.
Where the Extra Money Goes
Bar lengths are relative to the largest individual cost category. Insurance and security are modeled across every exposed voyage; time, survey and cargo-carrying costs apply only to the delayed subset.
How Much Does Delay Duration Change the Cost?
The comparison below holds the insured value, war-risk rate, security expense and share of affected vessels constant while varying additional delay time. Zero added days retains any survey allowance assigned to the affected subset.
| Extra Days | War Risk + Security | Vessel Time | Surveys + Cargo Carry | Total Incremental Expense |
|---|
The Questions a Cost Model Cannot Answer
We welcome your feedback, suggestions, corrections, and ideas for enhancements.
Please click here to get in touch