{"id":926,"date":"2026-10-07T03:33:57","date_gmt":"2026-10-07T03:33:57","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/india-and-oman-name-on-peace-after-12-seafarers-are-injured-off-musandam\/"},"modified":"2026-10-07T03:33:57","modified_gmt":"2026-10-07T03:33:57","slug":"india-and-oman-name-on-peace-after-12-seafarers-are-injured-off-musandam","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/india-and-oman-name-on-peace-after-12-seafarers-are-injured-off-musandam\/","title":{"rendered":"India and Oman name On Peace after 12 seafarers are injured off Musandam"},"content":{"rendered":"

India’s Ministry of External Affairs said on Tuesday, 6 October, that a Panama-flagged commercial vessel, MT On Peace, IMO 9893204, had been struck by a projectile while transiting the Strait of Hormuz off the coast of Oman. The ministry named the hull, gave a crew count and published a casualty figure that Monday’s unnamed UKMTO products did not carry. Of 19 people on board, 17 were Indian nationals. Twelve crew were injured, including 11 Indian nationals. With Omani assistance, the injured had been evacuated and were receiving medical treatment in Khasab. The ministry thanked Omani authorities and did not name an attacker.<\/p>\n

Oman’s Ministry of Defence, in a Tuesday statement carried by Anadolu, Khaleej Times and Al Jazeera, identified the same hull as ON PEACE and placed the targeting about nine nautical miles northeast of Lima, in Musandam Governorate, overlooking the Strait of Hormuz. A fire broke out on board. The Royal Oman Air Force, in coordination with the relevant authorities, medically evacuated 10 crew members to Khasab Hospital. The ministry did not specify the nature of the attack, the condition of those evacuated, or who was responsible. World Ports, reviewing the official evacuation video, said the helicopter landed on the tanker’s deck rather than hoisting from a hover, and that at least two of those arriving at the hospital left the aircraft on stretchers. That is video colour on how the lift was done, not a published injury list.<\/p>\n

This is a named-hull, named-position, named-casualty file. It is not a reprint of Monday’s Warning 156-26, which remained an unnamed master report of an engine-room fire with no casualties at warning time, and it is not a reprint of Tuesday’s time-late Warning 157-26, which remained an unnamed outbound oil tanker with no casualty line. gCaptain said the On Peace incident appeared connected to Monday’s unnamed UKMTO attack, but that the link had not been formally confirmed. India and Oman timed their own products to Tuesday. Hold that gap. Do not brief On Peace as a UKMTO naming, and do not collapse 156-26, 157-26 and the Khasab medevac into one completed tape.<\/p>\n

What India and Oman published, and what they did not<\/h2>\n

The MEA statement, issued in New Delhi on Tuesday afternoon and posted by spokesperson Randhir Jaiswal, is the working primary on people. The opening line is a condemnation of “the attack earlier today” on MT On Peace off Oman, “struck by a projectile while transiting the Strait of Hormuz.” The useful numbers sit in the next two sentences: crew of 19, 17 Indian, 12 injured, 11 of those Indian. The evacuation sentence names Khasab and thanks Oman. The policy sentences are also the working language for a DPA writing to an Indian-crewed tanker: continuing attacks remain a cause of deep concern; an immediate cessation is required in the interests of peace and stability; targeting of commercial shipping, seafarers and civilian infrastructure must end; navigation and commerce through international waterways should be restored at the earliest. The ministry did not publish a cargo, a load port, a destination, a projectile type, a responsible party, or a pollution volume.<\/p>\n

Oman’s defence ministry is the working primary on geography and the lift. Nine nautical miles northeast of Lima is a coastal-state position, not a UKMTO lat\/long and not a NAVAREA. Lima, also rendered Limah in some English copy, sits on Musandam’s east-facing shore. A tanker nine miles off that coast is already in the southern Omani corridor that masters have been using to stay off the northern Iranian-controlled route. The fire line is Oman’s, not UKMTO’s. The lift of 10, not 12, is also Oman’s. India said 12 injured and that the injured had been evacuated; Oman said 10 were airlifted to Khasab Hospital. Do not invent a reason for the two-person gap, and do not treat the hospital arrival as a completed discharge.<\/p>\n

Seatrade Maritime News wrote that the 12 had suffered burns. India’s statement said injured. Stay with injured unless a flag-state, company or hospital bulletin revises the mechanism. NUSI, the National Union of Seafarers of India, condemned the attack and said no commercial voyage is more valuable than a seafarer’s life. That is a union statement, not a manning finding. The National reported that Onex, the Dubai owner, had not issued a comment when asked on Tuesday. Do not invent one.<\/p>\n

Two unnamed UKMTO products still sit beside the named hull<\/h2>\n

Warning 156-26, issued Monday, 5 October, at 1637 UTC and sourced to a master, said a tanker in the Strait of Hormuz had been struck by an unknown projectile, causing an engine-room fire the crew were fighting. No casualties and no environmental impact had been reported at the time of that warning. The official product named neither hull nor flag. That file is already the dedicated Monday piece. Tuesday’s named casualty revises the people picture on a hull India and Oman are willing to print. It does not authorise a rewrite of 156-26 as a completed On Peace warning, because UKMTO has not named the hull and because India and Oman timed their reports to Tuesday.<\/p>\n

Warning 157-26, issued Tuesday, 6 October, is a separate Attack product. UKMTO said it had received a time-late report of an incident in the Strait of Hormuz. A verified source, not a master, reported that an oil tanker transiting outbound had been struck by an unknown projectile on 5 October, time to be confirmed. Authorities were investigating. Vessels were advised to transit with caution and report suspicious activity. The official PDF carried no casualty line, no pollution line, no position and no name. gCaptain treated 157-26 as another 5 October attack and said no casualties were disclosed. Do not assign 157-26 to On Peace, and do not add it as a second named hull.<\/p>\n

Seatrade, in the same Tuesday file that named On Peace, listed other industry-named Hormuz hits since 3 October: LNG carrier Maran Gas Mystras on 5 October, LPG carrier Vela Gas on 4 October, and VLCCs Cameroon Prosperity and Ghana Prosperity on 3 and 4 October. Those names are matching colour on the week, not UKMTO namings, and they are not this article. World Ports called On Peace the twelfth likely Iranian attack since the previous Wednesday. That is a secondary count and a secondary attribution. Stay with projectile. Do not brief a confirmed IRGC naming from a count.<\/p>\n

On Peace also appears on the Persian Gulf Strait Authority list of ships Iran says have violated its Hormuz protocols. Seatrade put the list at 81; the same channel has already been the dedicated product on this desk. The PGSA list is existing coastal-state colour, not a new transit-rule instrument and not proof of who fired on Tuesday. Do not fold a Khasab medevac into a declaration-channel story.<\/p>\n

Open particulars, and what still is not published<\/h2>\n

Open registers matching IMO 9893204 describe On Peace as a Panama-flag crude-oil tanker, MMSI 370236000, call sign HO3021, about 250 by 44 metres, about 63,134 gross tons and 115,157 deadweight, built in 2021. World Ports called her a 115,000-dwt LR2. Registered owner is given as Onex Peace Inc, commercial manager Onex DMCC in Dubai, ISM manager Anglo-Eastern Tanker Management in Hong Kong. Seatrade used the same owner and ISM lines from Pole Star’s PurpleTrac. Those are open particulars, not a cargo finding on Tuesday’s voyage. India and Oman did not publish what she was carrying, where she had loaded, or where she was bound. AIS colour that still shows stale destinations from earlier in the year is not a Tuesday stem. Do not invent a cargo.<\/p>\n

The casualty figure is now the operational fact that Monday’s unnamed warnings did not give. Twelve injured out of 19, with a deck landing and a hospital in Khasab, is a different night order from “no reported casualties at the time of this warning.” A DPA still has to treat 156-26 and 157-26 as unnamed products. A DPA who recognises On Peace as theirs now has a named Indian-majority crew, a named Omani hospital, a fire on a tanker nine miles off Lima, and a ministry statement that will be read by charterers, P&I and next-of-kin before UKMTO prints a name.<\/p>\n

Operational implications<\/h2>\n

A projectile hit that produces a double-digit injury count and a coastal-state medevac is no longer only an after-end fire-main problem. Masters already in the southern Omani corridor, the Musandam approaches and the first miles toward Fujairah or Khor Fakkan need a written projectile watch, a fire-and-casualty drill that assumes the after end is the target, and a plan for a helicopter landing on deck if the ship is still able to offer a clear zone. Citadel, fire-main isolation, emergency generator, steering-gear redundancy and a disabled-hull lookout remain the standing orders. A live fire nine miles off Lima also means a possible request for tugs and a possible pollution watch even though neither India nor Oman published a MARPOL volume. That absence is a snapshot, not a completed environmental finding.<\/p>\n

Manning desks should read the MEA numbers as a reminder that Indian seafarers are heavily represented on the tankers still making the strait. Seventeen of 19 on this hull were Indian. NUSI’s statement will be seen by crews on other Onex and Anglo-Eastern ships. Do not wait for a UKMTO name before putting a casualty-evacuation line into the Hormuz night order. Do not brief the combination of restored regional export volumes and a named 12-injured file as a reason to drop BMP, war-risk clauses or the published 30-nautical-mile standoff from U.S. units.<\/p>\n

Hold the hygiene already on the bridge from JMIC Update 102, information cut-off 041500 UTC on 4 October, which still rated the strait SEVERE and stopped at 150-26. 153-26 through 157-26 sit outside that cut-off. Neutral transit is still the published permission. Oman’s Article 10 AIS-on rule inside territorial waters was not withdrawn. Dark mitigation against projectile risk remains a compliance problem inside 12 nautical miles. CENTCOM’s blockade count and Iran’s PGSA list are separate products. Tuesday’s file is a named tanker, a named Omani position, and a named Indian-majority casualty list.<\/p>\n

What Operators Should Note<\/h2>\n