44 Seafarers Held and Somali Piracy Back: Which Policy Pays, Between Cargo, Hull War Risk and Kidnap and Ransom

On 6 July 2026 the IMO Secretary-General called for the urgent release of 44 seafarers held by Somali pirates. Eleven days later Al Jazeera reported that suspected Somali pirates had seized a tanker near Yemen amid what it described as a wave of hijackings. On 29 July 2026 India issued a fresh maritime security advisory, reported by ETV Bharat, directing merchant shipping to maintain enhanced vigilance and comply with anti-piracy measures.

That sequence matters for Indian cargo owners and shipowners because the exposed trades run straight through these waters: crude and product imports from the Gulf, fertiliser and project cargo through the Red Sea approaches, container traffic between west coast ports and Europe. A hijacking is not a single insured event with a single responding policy. It is several losses landing on several contracts: detention of the ship, detention of the cargo, a ransom demand for the crew, and months of extra cost keeping the adventure alive.

The market handled this during the 2008 to 2012 Somali cycle, and the coverage architecture built then still governs. But a decade of quiet let buying discipline decay: many Indian cargo owners have never checked which Institute clause set they hold, and many operators trading the region carry hull and war risk but no kidnap and ransom policy at all. This post works through which policy pays for what, how general average runs when a ransom is paid, what happens to cargo cover during a long detention, and what to demand in writing from any carrier trading the region.

Start with where piracy sits in each contract, because it sits in a different place in each.

Cargo: piracy is a marine peril under ICC (A) only

Under the Institute Cargo Clauses (A), the all-risks form, piracy is an insured peril: the war exclusion in clause 6.2 excludes capture, seizure, arrest, restraint or detainment, but with the words piracy excepted, which write piracy back into the marine cover. The restricted forms run the other way. ICC (B) and ICC (C) are named-peril clauses, piracy is not a named peril, and their war exclusion carries no piracy exception, so a cargo owner on (B) or (C) has no piracy cover unless it is added back by endorsement. The Institute War Clauses (Cargo) do not rescue the position either, because standard cargo war cover responds to war perils, not piracy. The most common gap in Indian cargo programmes trading this region is a (B) or (C) placement with neither a piracy write-back nor a considered decision to run the risk.

Hull: piracy is written out of marine and into war risk

Hull works in the opposite direction. The Institute Time Clauses (Hulls) 1/10/83 list piracy as a marine peril in clause 6.1.5, so on the printed form piracy is a hull risk. Market practice since the Somali cycle, however, deletes piracy from the marine hull cover by endorsement and places it under the war risk section, alongside the Institute War and Strikes Clauses perils, because war cover is priced by trading area with additional premium per listed-area transit and underwriters wanted piracy priced the same way. The piracy response on the hull side therefore follows the war risk placement: notification before entering a listed area, additional premium per transit, and the war underwriter, not the marine hull underwriter, on risk for the casualty. The mechanics of Indian war risk placements are covered in our post on marine war risk cover for Persian Gulf transits.

Ransom and response: neither policy. Neither the cargo policy nor the hull war risk policy is designed to fund a hostage negotiation. The ransom itself, the response consultants, the negotiator and the cost of delivering money to a ship anchored off the Somali coast sit in a separate kidnap and ransom (K&R) policy. Cargo and hull underwriters may bear a share of a ransom through general average, discussed below, but they do not advance it and pay nothing toward the negotiation that produces a release.

A marine K&R policy, typically written in the London and international specialty markets, does four things the marine policies cannot.

1. It reimburses the ransom payment itself, usually including loss of the ransom in transit, a real exposure when cash is delivered to a hijacked vessel.
2. It funds the response consultancy from the first hour: specialist responders who run the negotiation, manage proof-of-life, advise on offer strategy and handle delivery. Somali negotiations during the earlier cycle ran for months, and the response cost was a material share of the loss.
3. It pays additional expenses: crew salaries during captivity, medical and psychiatric care after release, repatriation, PR and legal costs, interest on money borrowed to fund the ransom.
4. It covers liability claims by crew or their families arising from the detention.

Two structural points matter for Indian buyers. K&R policies are reimbursement contracts: the insured pays and recovers, so the owner still needs liquidity. And they are strictly confidential, usually with a condition that disclosing the policy's existence can void cover, because a known K&R limit becomes the pirates' opening demand.

On legality: Indian owners sometimes assume a ransom payment to pirates is unlawful and therefore uninsurable. The English Court of Appeal held otherwise in Masefield AG v Amlin Corporate Member Ltd [2011] EWCA Civ 24, arising from the Somali hijacking of the Bunga Melati Dua: paying a ransom to pirates is not contrary to public policy under English law, which governs most of these placements, and a vessel in pirate hands is not an actual total loss where recovery by negotiation is likely. Sanctions screening still applies, since payments benefiting a listed entity are a separate legal risk the response consultants exist partly to manage. How Indian law treats ransom payments in the cyber context is examined in our post on ransom payments and insurance legality in India.

Suppose the negotiation succeeds and a ransom is paid to release ship, cargo and crew. Who ultimately bears it?

The settled position in adjusting practice is that a ransom paid to release ship and cargo from pirates is an extraordinary expenditure reasonably incurred for the common safety of the adventure, the definition of a general average act under Rule A of the York-Antwerp Rules. The Somali cases of 2008 to 2012 were routinely adjusted as general average. The consequences flow mechanically:

1. The shipowner declares general average and appoints an average adjuster.
2. Cargo is released at destination only against general average security: a GA bond signed by the receiver plus a GA guarantee from the cargo insurer. Uninsured cargo must post a cash deposit, which can mean finding several per cent of the cargo value in cash before goods are released.
3. The adjuster apportions the ransom, the response and delivery costs allowed in GA, port of refuge expenses, allowable crew wages during the detention, and the adjuster's own fee across ship, cargo and freight in proportion to contributory values at the termination of the adventure.
4. Each cargo insurer pays its cargo's contribution. Under ICC (A) the policy expressly covers general average and salvage charges incurred in connection with an insured peril, so an ICC (A) insurer pays the GA contribution arising from piracy. An ICC (B) or (C) insurer does not, because piracy is not an insured peril under those clauses, and the contribution falls on the cargo owner's own account.

The adjustment is slow: even a clean piracy GA takes 18 months or more to finalise, with cargo interests carrying outstanding security meanwhile. The mechanics of adjustment and security collection are set out in our companion post on marine hull general average claims.

On the hull side, the vessel's own proportion of general average falls to the policy covering the peril, which after the piracy write-back means the war risk underwriter. Sue and labour charges sit alongside the GA machinery: the cost of extra security measures after an attack begins, or of protecting cargo during the detention, can be recoverable as sue and labour under the responding policy.

Somali detentions during the earlier cycle ran from weeks to over a year. Three questions dominate the cargo position during that period.

Does the cover stay alive?

Yes, in the standard form. The transit clause (clause 8 of the ICC) keeps cover running during delay beyond the control of the assured, and a hijacking is exactly that, so ICC (A) cover continues through the detention and the onward voyage after release.

What the policy pays during and after the delay

Here is the trap: clause 4.5 of the ICC excludes loss, damage or expense proximately caused by delay, even where the delay is caused by an insured peril. Perishables that deteriorate while the ship sits at anchor for five months, market loss on goods that missed their season, demurrage and contractual penalties: none of it is recoverable, even under ICC (A). What remains covered is physical loss or damage from the piracy itself and the general average contribution described above. Owners of time-sensitive cargo must price that gap into routing and sales terms, because no standard marine clause fills it.

Getting the cargo moving again is a different question. Clause 12, the forwarding charges clause, pays the extra cost of unloading, storing and forwarding the cargo to destination where transit terminated at an intermediate port due to an insured peril. After a piracy release a vessel often needs a repair port first, and clause 12 funds transhipment onward, again only where the operative peril is insured, so only under ICC (A) in the piracy context. The sue and labour provision in clause 16 works alongside it: the cargo owner must take reasonable measures to avert or minimise loss, and the insurer pays the reasonable cost of those measures on top of the claim. How these questions played out in a war risk setting is worked through in our post on what a stranded-cargo war risk claim actually pays.

India's 29 July 2026 advisory told ships to maintain enhanced vigilance and comply with anti-piracy measures. In insurance terms, compliance with the industry Best Management Practices (consolidated in 2024 into a single BMP Maritime Security volume replacing BMP5) does two jobs: it moves premium before the voyage, and it decides arguments after a casualty.

On premium: war risk underwriters price listed-area transits per voyage. Evidence that the operator follows BMP, has a security assessment for the route, maintains hardening (razor wire, water cannon, a citadel with independent communications, hardened bridge), registers with the region's naval reporting constructs and, where appropriate, embarks a privately contracted armed team all moves the quoted rate. During the earlier Somali cycle underwriters discounted meaningfully for armed teams for a simple reason: no vessel with an embarked armed team was reported successfully hijacked. The formal industry High Risk Area designation for the Indian Ocean was withdrawn from 1 January 2023, but the Joint War Committee listed areas and the additional premium mechanism never went away, and the 2026 resurgence is repricing them.

On claims: piracy and war covers in this region typically carry warranties or conditions on routing, reporting and security measures. If the placement warrants BMP compliance, an embarked team or transit within a recognised corridor, the owner must be able to prove compliance after the event: passage plan, citadel drill records, hardening photographs dated before the transit, the security team contract, reporting logs. An owner who won a lower additional premium on the strength of measures not actually in place during the transit is inviting a declinature at the worst moment.

A cargo owner does not control the ship, but it chooses the carrier and holds the contract. Before booking cargo through the Gulf of Aden or western Indian Ocean, an Indian shipper or importer should require the following in writing from the carrier or its agent, and keep the answers with the shipment file:

1. War risk status. Confirmation that hull war risk cover including piracy is in force for the voyage and that listed-area additional premium has been or will be paid. A carrier that has not notified its war underwriter of the transit is a carrier whose casualty will become a coverage dispute.
2. Security posture. Confirmation of BMP compliance, whether a security team will be embarked, and that the vessel will report into the applicable naval reporting arrangements, consistent with India's 29 July 2026 advisory.
3. Routing. The intended track relative to recognised transit corridors, and an undertaking to notify material deviation.
4. General average terms. Which York-Antwerp Rules version the bill of lading incorporates, and the carrier's nominated average adjuster, so a GA declaration does not arrive as a surprise.
5. Contact protocol on detention. Who at the carrier communicates with cargo interests during a detention, and how often. Silence during a five-month negotiation delays cargo-side decisions.

Then fix the owner's side of the file. Confirm the cargo is on ICC (A) for any shipment routed through the region, or negotiate an explicit piracy write-back. Ask the broker to confirm in writing how the policy responds to a GA guarantee demand, so security can be posted quickly and the goods released. If the exposure is a programme rather than a single shipment, price a marine K&R placement alongside the cargo renewal, not after the first incident.

The 44 seafarers the IMO called to be released on 6 July 2026 are the human measure of this resurgence. The commercial measure is quieter: policies bought on the assumption that Somali piracy was history will decide who pays for the next hijacking. Read them before the transit, not after the phone call.