2026-06-06 — JWC 2026 Listed Areas expansion: war-risk underwriting trigger

핵심 요약

Core topic: 2026년 3월 Joint War Committee(JWC) Listed Areas 확장/경계 변경이 해상보험 언더라이팅 판단에 미치는 영향.

• Fact: LMA/IUA Joint War Committee Circular JWLA-033, 3 March 2026은 Hull War, Piracy, Terrorism and Related Perils Listed Areas에 Bahrain, Djibouti, Kuwait, Oman, Qatar를 추가하고, Persian/Arabian Gulf, Gulf of Oman, Indian Ocean, Gulf of Aden and Southern Red Sea 수역 경계를 변경했다.
• Fact: 해당 정의 수역은 Red Sea 남위/북위 기준선, Pakistan coastline, Indian Ocean high seas points, Somalia border 좌표로 광범위하게 설정되어 있다. 명시 국가는 원칙적으로 항만 및 연안 12해리까지 포함한다는 정의가 붙어 있다.
• Fact: TT Club은 JWC 변경을 반영해 War Risks, Piracy, Strikes Riots & Terrorist Risks 관련 excluded/listed areas 변경 효력을 2026-03-12로 안내했고, Forwarders Cargo covers의 War/Strikes/Riots/Civil Commotions 위험 변경 효력을 2026-03-13로 안내했다.
• Inference: 이 변경은 단순한 지리 정보 업데이트가 아니라, 항해통보·추가보험료(AP)·항해제한·제재/합법성 점검·누적관리의 자동 트리거로 취급해야 한다.

Facts / source notes

1. JWC JWLA-033 (2026-03-03)
   • Added listed areas: Bahrain, Djibouti, Kuwait, Oman, Qatar.
   • Amended regional listed water: Persian/Arabian Gulf, Gulf of Oman, Indian Ocean, Gulf of Aden and Southern Red Sea.
   • Note: “The application of this list on individual contracts will be a matter for specific negotiation.”
2. TT Club listed area page
   • War risk exclusions/listed areas updated with effect from 2026-03-12 for War Risks, Piracy, Strikes Riots & Terrorist Risks.
   • Forwarders Cargo covers updated with effect from 2026-03-13 for War, Strikes, Riots and Civil Commotions Risks, reflecting LMA JCC Global Cargo Watch List dated 2026-03-04.
3. Industry commentary (SAFETY4SEA)
   • Indicates likely higher additional war-risk premiums and more restrictive voyage terms.
   • Notes that Strait of Hormuz was not formally closed in the commentary, but the operating environment became more restrictive.

Underwriting impact

1) Cargo underwriting

• Risk selection: Cargo voyages involving Gulf / Gulf of Oman / Gulf of Aden / Southern Red Sea / affected Middle East ports should not be accepted on routing description alone. Require named load/discharge/transshipment ports, expected route, vessel name, flag, ownership/management, AIS behavior, convoy/security plan if relevant, and whether any sanctioned nexus exists.
• Coverage wording: Confirm whether ICC(A/B/C), War, Strikes, SRCC, delay, rejection, confiscation, sanctions limitation, and voyage deviation clauses are attached or excluded.
• Pricing: Listed-area entry should trigger AP or referral, not flat annual-rate treatment, especially for high-value, accumulation-prone cargo or cargo susceptible to delay/deterioration.
• Claims posture: War/strikes proximate cause disputes may increase where cargo loss arises from rerouting, port closure, delay, detention, missile/drone attack, piracy/terrorism, or state action. Exact wording/proximate cause treatment is 검증 필요 for each policy.

2) Hull / war underwriting

• Voyage approval: Require pre-entry notice into listed areas and explicit voyage approval terms where policy wording allows.
• Accumulation: A single geographic expansion can concentrate exposure across hull war, P&I, cargo, port/terminal, offshore, and reinsurance layers. Track vessels loitering/anchored near risk chokepoints.
• Cancellation / termination: War risk clauses often include short cancellation provisions or changed-risk mechanisms, but exact notice period and legal effect depend on clause form — 검증 필요.

3) P&I / liability

• Operational liabilities: Diversion, unsafe port disputes, crew injury, pollution, wreck removal, GA/salvage, collision, and cargo liability exposure may arise even where physical damage does not.
• Club response: P&I clubs may issue separate circulars, declarations, or exclusions; do not assume cargo/hull listed-area treatment automatically equals P&I cover position.

Risk transfer / claims / exposure implications

• Risk transfer: Listed-area status may shift part of the voyage risk from standard annual cover to separately priced/declared war-risk cover. If declaration is missed, breach/limitation issues may arise.
• Claims: Loss causation analysis should separate ordinary marine peril, war peril, strikes/riots/civil commotion, piracy/terrorism, sanctions/legality, and delay exclusions.
• Exposure: The same event can hit cargo, hull, loss of hire, P&I, salvage/GA, and reinsurance accumulation. Route/port risk scoring must feed portfolio-level accumulation, not just account-level acceptance.
• Reinsurance: Treaty/ facultative war exclusions, territorial limits, hours clauses, event definitions, and aggregation rules need alignment with the changed listed-area map — 검증 필요.

Checklist update

Link: [[JWC Listed Area Underwriting Checklist]]

Add or reinforce the following referral triggers:

• Voyage enters or calls any JWC listed country/defined waters.
• Port/country added or amended within last 30–60 days.
• Cargo value, vessel value, or multi-policy accumulation exceeds authority threshold.
• Any Iran/Syria/Russia/Yemen/Israel/Gulf state sanctions nexus or dual-use cargo concern.
• Route includes Bab el-Mandeb, Gulf of Aden, Southern Red Sea, Strait of Hormuz, Gulf of Oman, Arabian/Persian Gulf, or adjacent loitering/anchorage zones.
• Cover requested includes war/strikes/SRCC without explicit declared voyage terms.
• Vessel AIS gaps, unusual ownership/management chain, sanctioned beneficial owner, or high-risk flag/class issue.

AI/DX usecase

Usecase: Listed-area and sanctions-aware voyage underwriting assistant.

• Input: voyage route, ports, vessel IMO, cargo description/value, insured/beneficiary, policy wording, sanctions-screening result, current JWC/JCC/club circular data.
• Processing:
  1. Geofence planned route against current JWC/JCC listed-area polygons and named countries/ports.
  2. Extract war/strikes/sanctions/declaration/cancellation clauses from policy wording.
  3. Produce a structured referral memo: facts, inferred risk flags, missing information, recommended AP/terms, and claims/accumulation implications.
• Control: system should not auto-bind; it should create an underwriter decision pack with source citations and “검증 필요” flags where wording or law is uncertain.
• Data governance: raw circular PDFs/source copies should stay in source library/Zotero or source-data; Obsidian should keep curated interpretation and source pointers only.

Uncertainty / 검증 필요

• JWLA numbering discrepancy in secondary extraction: TT Club text mentions JWLA-032/JWC033 in places; primary circular reviewed here is JWLA-033 dated 2026-03-03. Confirm against LMA/IUA official current list before binding.
• Exact policy effect depends on attached clauses: Institute War Clauses, Institute Strikes Clauses, cancellation clause, trading warranty, sanctions limitation, held covered language, P&I club rules, and local law.
• Industry commentary about operational restriction is not the same as formal port closure or legal prohibition.
• Sanctions analysis must be current at underwriting/binding time; do not rely on nightly note for live sanctions clearance.

Next questions

1. For the current portfolio, which bound voyages enter newly added states or amended waters within the next 30 days?
2. Do current cargo/hull slips require listed-area declaration before entry, and what is the consequence of late/no declaration?
3. Are AP rates and authority limits updated by route segment and cargo/vessel accumulation?
4. Are sanctions-screening tools checking beneficial ownership, vessel history, cargo end-use, and transshipment—not just named insured?
5. Can the DX pipeline convert JWC circular coordinates into machine-readable geofences with audit logs?

Links

• [[JWC Listed Area Underwriting Checklist]]
• Source: LMA/IUA JWC Circular JWLA-033, 2026-03-03 — https://lmalloyds.com/wp-content/uploads/2026/03/JWLA-033_Iran.pdf
• Source: TT Club Listed Area / War Risk Exclusions — https://www.ttclub.com/listed-area
• Source: SAFETY4SEA industry summary — https://safety4sea.com/joint-war-committee-expands-listed-areas-raising-premiums-across-the-gulf