The Guinea-Bissau-flagged containership MV Baryon (IMO 9151412) was struck by a drone on 2 September 2026 while on passage from Novorossiysk to Karachi with 23 Indian seafarers on board. The unmanned aircraft hit the accommodation. A fire followed. The crew put the fire out and continued under the ship’s own power. A second drone was sighted during the incident. No injuries have been reported. Those facts, set out by the Forward Seamen’s Union of India (FSUI) and carried by SAFETY4SEA and Marine Insight, are now an operator problem rather than a one-off casualty note: on 7 September FSUI asked India’s Directorate General of Shipping, the Ministry of External Affairs and the Ministry of Ports, Shipping and Waterways to confirm the crew’s condition, to secure High Risk Area compensation, and to take the case up with the country concerned.
The attack sits on a Russia–Pakistan liner track that crosses more than one live war-risk theatre. Public reporting has not independently fixed the hit inside a named reporting box — Marine Insight noted it is not known whether Baryon was attacked in or near the Strait of Hormuz — so voyage files that treat “the Gulf” as the only UAV problem will mis-price the rest of the Novorossiysk–Karachi chain. Black Sea approaches, the Eastern Mediterranean, the Red Sea and Gulf of Aden, and the Gulf itself are all on or adjacent to that routing depending on canal versus Cape. A second drone in the vicinity is the operational tell: this was not a single stray airframe. Lookouts, the fire party and any citadel plan were under simultaneous pressure.
FSUI general secretary Manoj Yadav’s point is labour-supply-state, not flag-state. Guinea-Bissau is on the stern. The 23 seafarers are Indian. That split is now common on older feeder and handy container tonnage, and it is where HRA wage clauses fail. Many 2023–2024 ITF and house war-risk riders still point at the former Indian Ocean High Risk Area that the International Maritime Bureau retired in 2023, or at a Hormuz/Red Sea list that does not automatically pick up a UAV strike on a Black Sea or mid-voyage position. If the clause is silent, the owner still has a crew that fought an accommodation fire and then steamed on. The union’s ask — verify welfare, pay HRA rates, raise the matter with the concerned government — will land on the DGS desk whether or not the charter party contemplated it.
The Baryon case is also not isolated for Indian nationals. Marine Insight, citing ministry officials and earlier FSUI notices, lists a 22 April incident involving 21 Indian seafarers in the Strait of Hormuz; a 9 June U.S. strike on the Palau-flagged tanker Settebello in the Gulf of Oman; a 24 July attack on a Mozambique-flagged LPG tanker with 28 Indian crew in Iranian waters; the 20 August hijacking of Eritrea-flagged products tanker MT Sibu 1 about 30 nautical miles off Yemen, with 16 Indians among 20 crew; and two separate hijackings off Yemen and Somalia involving 22 Indian nationals. IMO Secretary-General Arsenio Dominguez has already called for immediate release of more than 90 seafarers held in the Gulf of Aden piracy wave. The labour market that supplies a large share of the world’s ratings is absorbing UAV, missile, boarding and hijack risk in parallel theatres. That is a crewing and insurance fact, not a political slogan.
Operationally, an accommodation hit is a different class of event from a deck or cargo strike. The fire load is cabins, insulation, cabling and the bridge block. The people who would run the citadel are in the space that is on fire. BMP Maritime Security and MSC.1/Circ.1601/Rev.2 still apply for piracy-prone waters, but they do not by themselves answer UAV detection, mustering under a second inbound airframe, or whether the master keeps the vessel in the traffic lane while the accommodation burns. Baryon’s crew extinguished the fire and proceeded. That is a credit to the shipboard team. It is not evidence that the next accommodation hit will leave a ship technically seaworthy, a bridge intact, or a crew willing to complete the voyage without relief. Owners who treat “continued under own power” as closure will under-prepare the next call from DGS, P&I and next-of-kin.
The commercial follow-through is already visible in the wider security stack this week: war-risk premia, extra insurance, and — on other trades — liner piracy and Suez surcharges. For a Guinea-Bissau-flagged boxship on a Russia–Karachi run the immediate controls are narrower. Confirm where the ship actually was when the UAV hit. Preserve CCTV, VDR, fire-log and medical records. Notify the flag, the Indian DGS because of the crew nationality, the relevant reporting centres for the waters in question, and the P&I club before the next port. Do not wait for a government statement that names a perpetrator. The union has already framed the incident as a seafarer-protection failure. Charterers and pooling partners will read it the same way.
What Operators Should Note
- Write the voyage as a multi-theatre UAV and boarding risk, not a single HRA box. Novorossiysk–Karachi can touch the Black Sea, Eastern Mediterranean, Red Sea/Gulf of Aden and the Gulf. If the war-risk rider only names Hormuz or the retired Indian Ocean HRA, it will not automatically cover Baryon-type hits.
- Treat an accommodation UAV strike as a fire-and-casualty case first. Citadel plans that pull the crew off the fire party are in conflict with an accommodation blaze. Drill the conflict now; do not discover it in the smoke.
- A second drone in the vicinity is a command problem, not a footnote. Lookouts, the bridge team and the fire party cannot all go heads-down. Assign who watches the sky while who fights the fire, and log the second airframe for P&I.
- Close the flag-versus-labour-supply gap on HRA pay before the next fixture. Guinea-Bissau on the flag, Indian crew on the articles, and a union already writing to DGS is a predictable claim. Name the waters, the wage trigger and who pays in the crew agreement, not in a later goodwill letter.
- Do not read “proceeded under own power” as all-clear. The ship can be technically seaworthy and the crew still due relief, medical screening and HRA compensation. Budget a crew change at the next safe port if DGS or the union requires it.
- Notify in parallel, not in sequence. Flag State, Indian DGS for Indian nationals, the relevant UKMTO/MSCHOA/JMICA-type centre for the waters, and the P&I club. FSUI has already copied three Indian ministries; the owner should not be the last to file.
- Preserve evidence as if a coastal State will ask. VDR, CCTV of the accommodation, fire-party times, drone sighting reports and AIS track. Attribution may stay disputed; the casualty file should not.
Regulas Shipping will keep lining UAV and boarding incidents that put Indian and other labour-supply crews in the fire line against the HRA clauses actually sitting in current crew agreements, so operators can see which voyages are covered on paper and which are only covered by luck.
