US Retaliates Against Iran After Drone Attack on Cargo Ship in Strait of Hormuz

The Analysis

The article gives four usable facts and no price. A drone struck a commercial cargo vessel in the Strait of Hormuz. US forces carried out retaliatory strikes on 26 June. The 60-day ceasefire was described as violated. War-risk insurance premiums stayed elevated, and the UN-led evacuation of stranded seafarers was paused. There is no rate print anywhere in that list, so I am not going to invent one. What I can do is take the four facts apart and show which invoice line each one lands on.

I get asked for a Hormuz number every time something happens in that strait, and the honest answer is that there is no single number to give. War risk on this route is not quoted the way a freight rate is quoted. It is written per transit, it carries a validity measured in days rather than months, and it is applied to a value — the hull, the cargo, or both. A percentage with no base and no validity period is not information. It is a mood.

There are two war-risk charges inside one Hormuz booking, and different people write them against different values. Hull and machinery war risk sits with the shipowner's underwriter and is charged per transit against the insured value of the vessel; the shipowner recovers it from cargo interests as a war-risk surcharge on the freight invoice. Cargo war risk is a separate policy, on a separately declared value, which a shipper may buy or decline. Most shippers decline it and accept the surcharge instead, which is a defensible position right up until the moment it is not. The detail worth holding onto is that the first charge reaches you whether or not you agreed to a rate. It is a surcharge, it is passed at cost, and it is not part of the FAK figure your contract protects.

Now the part that makes this different from a rate story. A ceasefire runs on a political clock measured in 60 days. A war-risk quote on this route runs on a much shorter clock, because the underwriter is pricing the voyage in front of the vessel rather than the diplomacy behind it — per transit, repriced on short validity. Two clocks, different units. A 60-day ceasefire does not sell you 60 days of stable premium, and a premium repriced by the voyage can move twice inside a single ceasefire window. That mismatch is the real exposure in the booking, and no headline that reports the ceasefire and the premium in the same sentence can show it to you.

The paused evacuation is being reported as a humanitarian item, and it is one. It is also a cost item, and the mechanism is worth spelling out because it never appears on a freight invoice. Crew cannot be rotated out of the affected area while the evacuation is suspended. A crew that cannot be relieved stays aboard past the end of its contract, which triggers extended-service wages, and the vessel drops out of the pool of ships that can be re-crewed on normal terms. A ship that has to divert to complete a crew change burns time and bunkers nobody budgeted. None of that is a war-risk premium. All of it reaches the freight rate eventually, with a lag, and none of it is visible in a quote.

Who is exposed depends on which side of the invoice they sit on. An exporter selling FOB is largely insulated: freight and the war-risk surcharge land on the buyer's account, and the real exposure is a schedule that slips. An importer buying CIF or DDP has bought the whole stack and takes the surcharge, the diversion cost and the delay together. A small shipper with one sailing a month has no alternative routing and no volume to negotiate with, so it absorbs whatever the surcharge turns out to be. A larger program can split cargo onto a land route or a longer sea routing at the cost of transit time, and it will do so earlier, because it can see the trigger coming. Size does not decide who gets hurt. It decides who moves first.

On timing, the sequence runs backwards from what most people expect. The premium is written per transit, so the first voyage after 26 June already carries it, and that is the fastest invoice line to move. The freight rate follows, because surcharges get folded into all-in quotes once a carrier decides the condition is persistent rather than an event. The contract rate is slowest: existing FAK rates hold to their validity, and the change arrives at renewal, or through a renegotiation clause if the contract has one. A shipper waiting to see whether this escalates before acting has the order wrong. The surcharge is already on the water.

Here is what the coverage is not measuring. The test of this route is not how high the premium is; it is whether quotes are still being issued and how long they stay good. A premium that is expensive but firm for the whole transit is still a market — painful, but it clears, and cargo moves. A premium that is expensive and good for a day is a queue. That switch is the real threshold. At a high enough price the market still clears. When nobody will quote you a number at all, cargo stops. The thing that stops cargo has never been the expensive number. It is the absence of one. Which is why I read the validity period before I read the percentage.

Here is how I would size it without a published rate, and these are my assumptions, not the article's. Take a container of goods declared at $150,000 for cargo insurance, with a transit war-risk charge written as a rate against that declared value. Every 10 basis points on that rate is $150 a box. At 40 boxes a month, 10 basis points is $6,000 a month and 50 basis points is $30,000 a month. I do not know where this route is quoted this week and I am not going to pretend I do. The arithmetic still tells you the sensitivity: this exposure is small until it is not, and the crossover happens inside one quarter if the quote doubles twice. The same 10 basis points on a $15,000 container of low-value goods is $15 a box, which is why two shippers on the same vessel can describe the same surcharge as trivial and as fatal, and both be telling the truth.

If the strikes had not followed the drone attack, the premium would most likely have drifted back down within a few weeks, because a single event with no response is priced as an event. The response is what reclassifies it from incident to condition, and a condition is priced as a standing charge rather than a spike. That is the counterfactual that matters for a budget. You are not paying for the drone. You are paying for the fact that the drone got an answer. The mistake I see is a shipper building the budget on the event reading and then discovering, two invoices later, that it is being billed the condition.

Which leaves one clean instruction. Watch the validity period on your next war-risk quote, not the percentage. If the period shortens while the percentage holds, the market is telling you the constraint is turning from price into availability, and that is the point to move cargo early rather than pay more. If the period holds and the percentage falls, you were paying for a headline. Fix the routing decision before the quote gets shorter, not after.

↑ Back to the key points

— By Vivian Zhao