{"id":685,"date":"2026-09-14T11:32:17","date_gmt":"2026-09-14T11:32:17","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/navarea-ix-names-el-gaia-after-a-hormuz-fire-and-oil-spill-as-one-indian-seafarer-remains-missing\/"},"modified":"2026-09-16T05:30:29","modified_gmt":"2026-09-16T05:30:29","slug":"navarea-ix-names-el-gaia-after-a-hormuz-fire-and-oil-spill-as-one-indian-seafarer-remains-missing","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/navarea-ix-names-el-gaia-after-a-hormuz-fire-and-oil-spill-as-one-indian-seafarer-remains-missing\/","title":{"rendered":"NAVAREA IX Names El Gaia After a Hormuz Fire and Oil Spill as One Indian Seafarer Remains Missing"},"content":{"rendered":"

Pakistan NAVAREA IX warning 319\/26 has named the Panama-flagged oil products tanker El Gaia as the ship involved in a Strait of Hormuz security incident on 13 September 2026. The notice reported fire, drift and an oil spill at 26\u00b026.50\u2032N, 056\u00b030.10\u2032E, about 3.6 nautical miles northwest of Jazirat Musandam. India\u2019s Ministry of External Affairs said 13 of the 14 Indian seafarers on board were rescued and shifted ashore. Search and rescue for one missing Indian national was still running on 14 September, with the Indian Embassy in Oman coordinating with Omani authorities.<\/p>\n

ClassNK lists El Gaia as IMO 9325336, official number 30982-05-CH, call sign 3ECL5, flag Panama. She is a 2005-built oil carrier of 28,799 gross tons and 47,999 deadweight tonnes, 179.99 metres overall, moulded 172.00 \u00d7 32.20 \u00d7 19.05 metres, with 57,289 cubic metres of cargo tank capacity. The registered owner is El Gaia Shipping Inc; the manager is Elsey Ship Management LLC. Former names are Nave Dorado and Kuroshio Express. She was built at Iwagi Zosen, hull 231, delivered on 23 August 2005, with a Mitsui Tamano 9,480 kW main engine. Those particulars matter for the casualty file: this is a mid-size products tanker, not an unnamed hull in a UKMTO sentence, and the oil-spill line in the NAVAREA is a pollution event as well as a security event.<\/p>\n

The naming also sits next to reports that operators should keep separate until official mapping is complete. UK Maritime Trade Operations Warning 134-26, received at about 2300 UTC on Saturday, logged an unidentified munition on an unnamed commercial vessel transiting the strait and later said a fire had broken out, with local authorities evacuating crew. Iranian local authorities reported a merchant vessel struck off Hengam and Qeshm around 0500 local on Sunday, with one person killed and several injured. Public reporting has not fully reconciled whether the Qeshm\/Hengam casualty, the unnamed UKMTO warning and the named El Gaia NAVAREA describe one ship or more than one attack in the same hours. Masters and company security officers should treat Musandam, Qeshm, Hengam and the Omani-side transit lane as a live threat area either way. A named tanker with a published position is the product that voyage orders, P&I and pollution response can act on today.<\/p>\n

India condemned the attack on El Gaia and called the targeting of commercial shipping, seafarers, civilians and civilian infrastructure unacceptable. New Delhi asked for immediate de-escalation and for free and safe navigation through regional waterways to be restored. The ministry did not identify those responsible and did not name the missing seafarer. Ten Indian seafarers are among Indians killed in the wider West Asia conflict, and Indian reporting has also recorded seafarer deaths in Black Sea strikes on merchant ships. For operators with Indian ratings, the El Gaia file is a crew-nationality and next-of-kin problem as well as a Hormuz routing problem. The embassy\u2019s SAR coordination with Oman is the consular channel; it is not a substitute for the company\u2019s ISM emergency response, flag notification, or P&I casualty advice.<\/p>\n

The operational implication is that Hormuz remains a projectile, fire and pollution waterway with no new corridor in force. Oman postponed the Salalah briefing that was due on Monday, 14 September, at which Iran had said it would present an Iran\u2013Oman arrangement for commercial traffic. There is still no IMO circular, no published traffic separation scheme, and no signed instrument that a master can put in the passage plan. Ships that move through the strait continue to do so against UKMTO, MSCIO, IFC-IOR and BMP Maritime Security reporting, not against a ministerial diary. A NAVAREA that names fire, drift and an oil spill 3.6 nautical miles off Musandam is a reason to keep fire-response, abandon-ship and SOPEP equipment live on approach, not a reason to wait for a later date in Salalah.<\/p>\n

The same 24-hour cycle turned the security picture into voyage economics. S&P Global and Platts assessed the 80,000-tonne Vancouver\u2013China Aframax route at a record 7.5 million dollars on 10 September, the highest since that assessment began on 2 February 2026. Reuters reported VLCC Gulf of Oman\u2013China rates around Worldscale 450, about 11.50 dollars a barrel, also a record for that series. A named tanker casualty with a missing seafarer and a published oil spill does not create those rates by itself. It does add another hull that charterers, war-risk underwriters and oil-spill responders have to take out of the available picture while Saudi Arabia\u2019s East\u2013West pipeline remains stopped and Bab el-Mandeb stays tightened after Mokha and Perim. Fixture desks that still price Gulf of Oman stems as if the weekend produced only an unnamed warning should reprice ballast, substitution, demurrage and laycan risk against a named Aframax-size products tanker off Musandam.<\/p>\n

For the ship manager, the first duty is the missing seafarer and the 13 ashore. Flag, P&I, hull, war-risk and oil-pollution insurers need the NAVAREA position, the ClassNK identity, the MEA crew count, and a clean distinction between verified El Gaia facts and the still-unreconciled Qeshm report. SOPEP activation, MARPOL reporting, and coastal-state notification follow the oil-spill line in 319\/26 whether or not the attacker is identified. Charterers should check whether the hull was on a voyage charter, a time charter or a pool stem, and whether deviation, war-risk, and pollution clauses respond to a security incident that also produced drift. A dark AIS picture around Musandam does not remove the ship from the projectile envelope, and it does not remove the operator from the duty to preserve VDR, bridge logs, AIS records and security communications for the investigation that will follow the SAR.<\/p>\n

What Operators Should Note<\/h2>\n