2026-06-10 — War P&I excess cover does not replace primary War P&I in Middle East war-risk transits

핵심 요약

Core topic: Middle East / Red Sea / Hormuz 계열 war-risk transit에서 P&I liability가 “P&I에 들어 있다”는 막연한 이해는 위험하다. Mutual P&I는 war risks를 기본적으로 제외할 수 있고, International Group 계열 excess War P&I는 보통 primary War P&I 위에 붙는 excess 구조라서, primary War P&I가 없으면 ground-up protection으로 자동 전환되지 않는다는 점이 underwriting 핵심이다.

• Fact: Britannia P&I 설명자료는 Class 3 mutual P&I에서 war risks가 Rule 25 등으로 제외될 수 있고, 별도 excess War Risks insurance가 International Group 재보험 구조와 함께 마련된다고 설명한다.
• Fact: Britannia 자료는 primary War P&I가 arranged되지 않은 경우 excess placement가 “drop down”하여 ground-up cover를 제공하지 않는다고 명시한다.
• Fact: London P&I는 Iran conflict 관련 페이지에서 Persian/Arabian Gulf, Strait of Hormuz, Red Sea, Gulf of Aden의 disruption, projectile/armed approach/IRGC gun boat 관련 UKMTO incident excerpts, jamming/spoofing, BMP guidance와 crew welfare 이슈를 언급한다.
• Fact: Ambrey 2026-01-13 threat circular는 Red Sea/Bab el-Mandeb transit 재개가 low-risk operator 중심으로 점진적·불균등하게 진행되며, Israeli-owned 또는 Houthi-designated shipping은 여전히 더 높은/검증되지 않은 risk로 남는다고 평가한다.
• Inference: Cargo underwriter도 P&I 구조를 알아야 한다. war-risk casualty가 발생하면 cargo loss, GA/salvage, pollution/wreck/crew liabilities, delay/diversion, port closure, sanctions payment block이 동시에 발생할 수 있고, vessel-side War P&I gap은 cargo claim recovery와 security process에 영향을 준다.
• Assumption: 이 note는 특정 고객·선박·항차가 아닌 reusable underwriting judgment record이다. 실제 quote/bind/claim에는 policy wording, vessel war H&M/P&I certificates, route security assessment, sanctions screening, reinsurance treaty response 확인이 필요하다.
• Recommendation: Red Sea / Bab el-Mandeb / Gulf of Aden / Gulf of Oman / Strait of Hormuz / Persian-Arabian Gulf exposure는 cargo-only pricing으로 끝내지 말고, primary War P&I evidence, excess attachment, war/strikes cargo clause, sanctions clause, GA/salvage security capability, aggregation clearance를 함께 referral checklist에 넣는다.

Facts / source notes

1. Britannia P&I — War Risks Explanatory Note, 17 March 2026

   • Source pointer: https://britanniapandi.com/wp-content/uploads/2026/03/War-Risks-Explanatory-Note-03-2026.pdf
   • The note addresses Iran–US/Israel conflict impacts on Gulf of Oman, Strait of Hormuz and Arabian/Persian Gulf shipping.
   • It explains that Class 3 mutual P&I war risks can be excluded under Rule 25 wording such as war, civil war, hostile act by or against a belligerent power, etc. 정확한 문언은 해당 Club Rules / Certificate / Endorsement로 검증 필요.
   • It describes excess War Risks cover arranged with International Group P&I Clubs, including a general USD 500m limit in the extracted summary, but warns that if primary War P&I is not arranged, excess placement does not “drop down” to cover from the ground up. Limits and attachment are placement/year-specific — 검증 필요.
   • It identifies exclusions/carve-outs such as chemical/biological/bio-chemical/electromagnetic/computer virus type risks and a crew-claims exception/sub-limit in the extracted summary. Exact exclusion and carve-back wording 검증 필요.

2. London P&I — Iran conflict page, 6 March 2026, with incident excerpts

   • Source pointer: https://www.londonpandi.com/insights-resources/iran-conflict
   • The page notes disruption to cargo availability, production, transport and commercial shipping in Persian/Arabian Gulf, Strait of Hormuz, Red Sea and Gulf of Aden.
   • It emphasizes thorough risk assessments, monitoring advisories, BMP Maritime Security guidance, crew welfare, and alertness to electronic navigation interference including jamming/spoofing.
   • Extracted UKMTO examples include a 1 June 2026 Strait of Hormuz report of a cargo vessel struck by an unknown projectile, April 2026 armed approaches / firing incidents near Oman and Somali/Yemen waters, and warnings to report suspicious activity.

3. Ambrey — Threat Circular, 13 January 2026

   • Source pointer: https://ambrey.com/ara130126tc
   • Red Sea and Bab el-Mandeb transits were assessed as resuming gradually and unevenly, led by selective trial voyages by lower-risk operators.
   • Israeli-owned, Israel-linked or Houthi-designated vessels remained higher risk / not fully tested. Premiums reportedly fell for some US/UK-associated shipping but not significantly for Israeli-owned shipping in the extracted summary.
   • This supports case-by-case underwriting rather than a binary “route reopened / route closed” conclusion.

Underwriting impact

1) Cargo underwriting cannot ignore vessel-side War P&I

• Problem: Cargo placement may include ICC(A) plus War/Strikes clauses, but a war-risk event can trigger vessel liabilities and security demands outside cargo policy boundaries.
• Impact: If the carrying vessel lacks primary War P&I, Club excess War P&I may not respond ground-up. This can weaken the casualty response, complicate GA/salvage security, delay cargo release, and increase practical loss severity even where cargo insurance responds.
• Underwriting action: For high-risk corridors, ask for evidence of vessel war H&M / War P&I and relevant Club confirmation where material cargo values or accumulation exist.

2) Route-risk pricing must be dynamic, not static

• Problem: Red Sea/Bab el-Mandeb activity can improve for some operators while remaining unacceptable for others depending on perceived Israel/US/UK nexus, Houthi designation, flag, ownership/control, cargo, charterer, and sanctions optics.
• Impact: A generic additional premium for “Red Sea” may underprice high-risk affiliations or overprice genuinely lower-risk trial voyages.
• Underwriting action: Rate and referral should be route + vessel + operator + ownership/control + cargo + timing specific. Keep AP subject to no material change before listed-area entry.

3) Claims causation and performance must be separated

• Problem: A casualty may involve concurrent marine peril, war peril, piracy/terrorism, strikes/SRCC, sanctions, confiscation, delay, GA/salvage and sue-and-labour issues.
• Impact: Claims handlers need early evidence preservation and sanctions/legal screening before payment, guarantee, security or recovery.
• Underwriting action: Bind decision memo should already record which covers are intended and which are excluded/sublimited. Ambiguity creates avoidable disputes.

Risk transfer / claims / exposure implications

• Risk transfer: War P&I gap can shift practical risk back to cargo interests even if cargo policy covers physical loss, because cargo release, salvage security or recovery path may depend on vessel-side liability/security arrangements.
• Claims: Require proximate-cause analysis: projectile/drone/mine/hostile act vs ordinary marine peril vs piracy/armed robbery vs government restraint vs delay. Exact clause classification is 검증 필요.
• GA/salvage: War-risk incidents often lead to deviation, refuge port, salvage, firefighting, pollution prevention and GA. Cargo insurer exposure includes guarantee issuance and contribution handling; sanctions screening must occur before security/payment.
• Accumulation: Multiple cargo certificates on the same vessel/convoy/port closure can create correlated cargo, delay, GA, storage, forwarding, and reputational exposure. Portfolio view by vessel IMO and chokepoint is needed.
• Reinsurance: Treaty/fac response may contain war, terrorism, sanctions, aggregation, event limit, listed-area or notice conditions. Confirm before accepting large exposed values — 검증 필요.

Checklist update

Link: [[War P&I Evidence Checklist for Cargo Underwriters]]

Add/refine referral triggers for Red Sea / Bab el-Mandeb / Gulf of Aden / Gulf of Oman / Strait of Hormuz / Persian-Arabian Gulf transits:

• Vessel route enters or may enter current JWC/JCC listed/watched waters, high-threat port approaches, or naval advisory zones.
• Cargo value, stock-throughput accumulation, or project cargo severity makes GA/salvage/security delay material.
• War/Strikes/SRCC cover is requested, but vessel War P&I evidence is absent or outdated.
• Carrying vessel is Israeli-owned/linked, Houthi-designated, sanctioned/sanctions-sensitive, recently renamed/reflagged, dark-fleet-like, or has AIS gaps.
• Transit plan relies on “security situation improved” without current voyage-specific risk assessment.
• Policy wording includes non-standard war, strikes, sanctions, cancellation, held-covered, deviation, delay, or trading-limit wording.
• Claim or pre-loss advice may require GA guarantee, salvage security, payment to port/salvor/repairer, or recovery against sanctioned/high-risk parties.

AI/DX usecase

Usecase: war-risk corridor underwriting copilot for cargo declarations and open-cover referrals.

• Inputs: cargo declaration/application, policy wording, War/Strikes clauses, sanctions clause, vessel name/IMO, owner/manager/operator/charterer, voyage legs, ETA/ETD, cargo/value, war H&M/War P&I certificate evidence, P&I Club, source advisories, JWC/JCC areas, sanctions screening, portfolio accumulation by vessel/chokepoint.
• Processing:
  1. Extract route and entities from documents; normalize vessel identity by IMO and prior names.
  2. Geofence route against versioned listed/watched areas and chokepoints.
  3. Detect whether War/Strikes requested and whether vessel-side War P&I evidence is attached.
  4. Produce memo sections: facts, inference, assumptions, recommendations, uncertainty, and source pointers.
  5. Flag “no autonomous bind” if sanctions unresolved, primary War P&I absent for high-value transit, route enters active incident zone, or aggregation exceeds authority.
• Controls: AI must not decide cover/bind. It prepares evidence and highlights missing information. Final decision remains with underwriter/compliance/legal.
• Data governance: Store raw circulars/advisories in source library/Zotero/source-data; Obsidian keeps curated judgment and source pointers only.

Uncertainty / 검증 필요

• Exact Britannia / Club wording, limits, attachment points, exclusions, special circulars and policy-year conditions are placement-specific.
• Current JWC/JCC listed areas, naval advisories, war-risk market pricing and local security conditions can change rapidly.
• Whether an incident is war, piracy, terrorism, strikes/SRCC, malicious damage, marine peril, government action or excluded delay depends on exact facts and wording.
• Sanctions restrictions may prevent premium, claim, guarantee, salvage security, recovery or reinsurance payments even where physical cover appears available.
• Ambrey/London/Britannia sources are not substitutes for official current security advisories, policy documents, legal review or vessel-specific due diligence.

Next questions

1. For high-risk cargo declarations, do we require vessel IMO plus evidence of primary War P&I before binding War/Strikes cover?
2. Should open-cover systems block certificate issuance if route geofence intersects Red Sea/Bab el-Mandeb/Hormuz watch zones and no war-risk AP/referral is recorded?
3. What minimum evidence is acceptable for vessel-side War P&I: certificate, broker confirmation, Club circular, or owner declaration?
4. Do cargo wordings clearly exclude delay/loss of market arising from war-risk diversion or port closure unless expressly bought back?
5. Can claims workflow detect GA/salvage/security requests involving sanctioned/high-risk parties before guarantee/payment is issued?

Links

• [[War P&I Evidence Checklist for Cargo Underwriters]]
• [[JWC Listed Area Underwriting Checklist]]
• [[Marine Cargo Sanctions Screening Checklist]]
• Source pointer: Britannia P&I — War Risks Explanatory Note, https://britanniapandi.com/wp-content/uploads/2026/03/War-Risks-Explanatory-Note-03-2026.pdf
• Source pointer: London P&I — Iran conflict, https://www.londonpandi.com/insights-resources/iran-conflict
• Source pointer: Ambrey — Threat Circular: Houthis Signal Operational Pause, https://ambrey.com/ara130126tc