The conflict is not the counting unit

A tanker encounters GNSS interference, later strikes debris, then collides during a separate evacuation manoeuvre. Commercially, all three problems may be described as consequences of the Iran war.

Insurance deductibles are not necessarily applied to the conflict as a whole. Each policy defines the relevant casualty, event, occurrence, voyage, category, or waiting period.

A deductible is retained loss

Gard defines a deductible as the portion of an insured liability, loss, cost, or expense the member bears before compensation. It differs from a franchise, under which an above-threshold claim may be paid in full.

The schedule and certificate, not industry shorthand, determine the amount and application.

Hull commonly counts casualties

Nordic hull rules apply a deductible for each casualty. One engine-room fire spreading through the ship is normally one casualty; a grounding followed later by unrelated storm damage is normally two.

Rapid succession or strong causal connection makes the boundary fact-specific.

Repeated action by one peril may still split

A vessel can suffer damage from the same type of peril on clearly separate occasions. Repeated mine contacts, drone strikes, or spoofing episodes do not automatically merge because the actor, campaign, or conflict is common.

Time, place, continuity, causation, intervention, and whether the ship returned to safety can influence the analysis.

One casualty can produce many damage items

A single explosion may damage hull, machinery, cargo systems, and accommodation. Those are not automatically separate hull deductibles if they flow from one casualty.

Surveyors should trace the causal sequence rather than count invoices or repair specifications.

P&I may count by event and category

Gard's 2026 schedule applies standard deductibles by categories such as crew, cargo, pollution, collision, fines, and other liabilities, with many attaching to any one event. Cargo can apply per cargo-carrying voyage.

One casualty can therefore generate different retained amounts across liability categories.

Special agreed deductibles can override the standard

Members often negotiate deductibles reflecting fleet risk and premium. A certificate may impose a separate amount for a particular category or exposure.

The published club schedule is not proof of the deductible on one vessel. Review the entry terms and endorsements.

Mitigation costs usually follow the underlying claim

Skuld's rules state that legal and mitigation costs are subject to the deductible applicable to the claim for which they were incurred. Gard likewise aggregates relevant loss-prevention expense with the associated liability under its schedule.

Owners should not assume emergency spending creates a fresh standalone deductible, or that it escapes the underlying one.

Several categories can mean several retentions

A collision may injure crew, damage another ship, spill oil, and harm cargo. Depending on wording, category-specific deductibles can apply even when all liabilities arise from one event.

The claims estimate should show gross loss, applicable limit, and deductible by category rather than one net figure.

Loss-of-hire uses time

Loss-of-hire insurance commonly applies a deductible period for each casualty. If one casualty causes delays at the scene, during temporary repair, and during permanent repair, one time deductible can apply to the aggregated delay.

Two casualties repaired together may have deductible periods running partly or wholly in parallel rather than simply added end to end.

Simultaneous repair does not merge causation

An owner may repair missile damage and an earlier machinery breakdown in one yard stay. Operational convenience does not necessarily turn two casualties into one.

Time records must allocate delay and repair critical paths to each cause.

Policy limits and deductibles can use different tests

Nordic commentary warns that the casualty concept used for a sum-insured limit need not always have identical content to the deductible concept. Deterrence and contractual purpose can influence interpretation.

Never assume an aggregation victory on the deductible automatically multiplies or preserves the limit.

War and marine policies can disagree

The same sequence may be one event under a war policy and several casualties under hull terms, or the reverse. Primary and excess layers may also define occurrence differently.

Coverage counsel and adjusters should build a policy-by-policy event map before netting the claim.

Evidence decides the event boundary

Preserve precise times, positions, sensor data, repair history, restoration of safe operation, authority reports, and intervening decisions. Identify whether later damage was inevitable from the first event or arose independently.

Broad statements such as “continuous war conditions” are not a substitute for causation evidence.

Hypothetical three-stage transit

Assume a tanker suffers minor blast damage, reaches anchorage, is declared safe after temporary repair, and five days later grounds during a new spoofing episode. During refloating it collides with a tug.

This hypothetical is not a reported casualty. Hull, collision, crew, pollution, and loss-of-hire policies may count the stages differently.

Forecast: event clauses will receive more scrutiny

If repeated Gulf incidents affect the same vessels, renewals are likely to focus on event definitions, hours clauses, category deductibles, waiting periods, and aggregation across electronic and kinetic attacks.

This is a forecast, not a confirmed universal amendment.

Owners need a gross-to-net model

For each incident, list cause, time, place, policy, category, gross reserve, limit, deductible, waiting period, mitigation cost, and recovery. Run both one-event and multiple-event cases where facts remain unresolved.

Cash planning should use the more conservative plausible retention until markets agree.

Brokers should test cross-policy language

Compare “casualty,” “event,” “occurrence,” “series,” “originating cause,” “voyage,” and “each vessel” across every layer. Identify who has authority to determine event count and what dispute law applies.

Premium comparisons without retained-loss comparisons are incomplete.

Fleet retention needs catastrophe testing

Several ships can each incur a separate deductible during one coordinated attack. Even modest retentions then accumulate across the fleet before insurance pays. Treasury models should combine vessel-level deductibles, uninsured waiting periods, emergency expense, collateral, and delayed reimbursement under one regional stress scenario.

The ZeaClub view

The Iran war is a geopolitical frame, not an insurance aggregation clause. A Gulf operator can face one deductible for a spreading casualty, several for distinct attacks, different category retentions under P&I, and overlapping time deductibles under loss of hire.

Owners should preserve the causal chronology and model every policy separately. The commercial question is not “How many wars occurred?” It is “How many insured casualties, events, categories, voyages, and waiting periods does each contract recognise?”

This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.

Sources