{"id":912,"date":"2026-10-05T11:36:34","date_gmt":"2026-10-05T11:36:34","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/romania-sar-recovers-two-dead-after-royad-mammadov-sinks-in-the-black-sea\/"},"modified":"2026-10-05T11:36:34","modified_gmt":"2026-10-05T11:36:34","slug":"romania-sar-recovers-two-dead-after-royad-mammadov-sinks-in-the-black-sea","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/romania-sar-recovers-two-dead-after-royad-mammadov-sinks-in-the-black-sea\/","title":{"rendered":"Romania SAR recovers two dead after Royad Mammadov sinks in the Black Sea"},"content":{"rendered":"

Romania\u2019s Naval Authority said on Monday, 5 October, that it had been alerted at about 11:00 local time to a serious maritime incident outside Romanian territorial waters, and that the ship involved was Royad Mammadov. AGERPRES carried the statement. The authority said a fire had broken out on board, that the master was injured, and that 13 crew members were missing. MRCC Constan\u021ba requested the Romanian Agency for Saving Lives at Sea and mobilised SAR Apollo from Sulina and SAR Artemis from Dana 72, with SAR Ares also requested. Romania\u2019s Interior Ministry later said 11 crew had been rescued, two deceased persons had been identified, and that the structures of the ministry were carrying out a complex mission to rescue the crew of a ship that had sunk in the Black Sea. Injured people were winched by a General Aviation Inspectorate helicopter for emergency medical care.<\/p>\n

That is the working primary. Monday is a named-hull fire and sinking in the Romanian search-and-rescue region, not a rewrite of Saturday\u2019s unnamed Liberia-flag Odesa-region port strike. The useful facts for a DPA, a Black Sea master and a P&I desk are the name Royad Mammadov, the fire, the position outside territorial waters, the 11 rescued and two dead, and the fact that ANR\u2019s first product was a SAR alert, not a weapons finding. Do not treat a drone headline as an ANR attribution, and do not invent a cargo or a flag-state circular that the authority did not publish.<\/p>\n

What ANR and the Interior Ministry actually said<\/h2>\n

ANR\u2019s first note, also carried by Ziarul Amprenta from the authority\u2019s text, is short. Around 11:00 on 5 October, MRCC Constan\u021ba was alerted to a serious maritime incident outside Romanian territorial waters. The centre requested ARSVOM and the named salvage units. First information: master injured, 13 crew missing. The authority named Royad Mammadov. It described a fire. It did not, in that statement, name a weapon, a cargo, a load port, a destination or an IMO number. ARSVOM\u2019s own line, carried by Metro, timed the MRCC request at 10:37 and placed the ship in \u201cthe platform area.\u201d<\/p>\n

The Interior Ministry\u2019s later statement moved the human count and the ship\u2019s status. Eleven crew rescued. Two deceased identified. A helicopter winched the injured. The ministry said the ship had sunk. Coast Guard colour in the same Romanian reporting placed the fire in Romania\u2019s exclusive economic zone, about 30 nautical miles south of Sf\u00e2ntul Gheorghe, with a Coast Guard ship designated on-scene coordinator of the search. That EEZ line sits with ANR\u2019s \u201coutside territorial waters.\u201d It is not a finding that the casualty occurred inside 12 nautical miles, and it is not a Romanian territorial-sea closure.<\/p>\n

Reuters, as carried by Global Banking and Finance Review on Monday, restated the same official pair: two dead, others rescued, a fire that prompted rescue action for a sinking ship outside territorial waters, Interior Ministry on the 11 rescued, Naval Authority on Royad Mammadov and the fire. T\u00fcrkiye Today\u2019s 14:31 GMT+3 write-through added that further details about the cause, the ship\u2019s route and crew nationalities were not immediately available from the authorities. Stay with that gap. Do not fill it from a television chyron.<\/p>\n

Matching, not ANR naming: flag, IMO, voyage and the drone line<\/h2>\n

Open-register matching, not an ANR circular, identifies Royad Mammadov as IMO 9356969, MMSI 341609002, call sign V4LC7, Saint Kitts and Nevis flag, a 2006-built general cargo \/ mini-bulker of about 140 metres by 17 metres and about 6,933 dwt. T\u00fcrkiye Today called the ship Turkish-owned and St Kitts-flagged on that IMO. Several Romanian outlets also called it a Turkish ship. Use the IMO and the St Kitts flag as the working identifiers. \u201cTurkish\u201d is ownership or manning colour in secondary reporting. It is not ANR\u2019s flag line, and it is not a Turkish-flag casualty unless the flag state says so.<\/p>\n

Voyage colour is likewise secondary. Metro and Informat.ro said the ship had left Izmail, Ukraine, for Ravenna, Italy, with grain, and placed the strike about nine nautical miles from the Pesc\u0103ru\u0219 offshore platform, with some reports giving about 40 nautical miles off Constan\u021ba. Informat.ro\u2019s 10:23 piece said an explosion then a powerful fire, that the ship was in danger of sinking, and that the exact cause had not been officially established, with an initial hypothesis of a drone. PRO TV sources speaking of two or three drones were explicitly unconfirmed. Interior minister Radu Miru\u021b\u0103, in later Informat.ro coverage, said it had been reported that the ship was hit by a drone. Label that as a reported hypothesis. ANR\u2019s published product on Monday morning was a fire and a missing-crew count, not a confirmed weapon.<\/p>\n

Do not merge Monday\u2019s hull with a second, unverified drifting ship. Mediafax\u2019s English file mixed Royad Mammadov with unconfirmed talk of a motor ship Emil, a Bulgarian notice of an unmanned vessel drifting toward Bulgaria\u2019s exclusive economic zone, and a position east of Cape Shabla. Those are a different, still-unconfirmed file. Monday\u2019s ANR name is Royad Mammadov. Brief one casualty unless a second authority names a second IMO.<\/p>\n

What this sits on \u2014 and what it does not change<\/h2>\n

Saturday\u2019s dedicated 4 October 03:30 piece is a Ukrainian Sea Ports Authority casualty: a Liberia-flag cargo ship in an Odesa-region port, one motorman killed, three injured, 13 evacuated, hull unnamed by USPA. Local matching there was Jincheng, IMO 9378838. Monday is a different flag, a different authority, a different geography and a ship that ANR says caught fire outside Romanian territorial waters and that the Interior Ministry later said sank. Do not collapse the two into one Black Sea grain story.<\/p>\n

The Joint War Committee\u2019s JWLA-035 circular of 16 September already lists almost the entire Black Sea as a war-risk area, excluding territorial waters of adjoining countries other than Russia and Ukraine. A fire and sinking in the Romanian EEZ does not create that listing. It is evidence, on a named hull, that a dry ship leaving the Danube mouth remains a live crew and war-risk event after it has cleared Ukrainian berths. Liberia\u2019s Marine Security Bulletin 37\/2026 level-3 condition in Ukrainian ports does not apply to a St Kitts ship in the Romanian EEZ. The relevant screens here are the ship\u2019s own SSP, the charterparty war-risk clause, and whatever additional premium the underwriter already prices on JWLA-035.<\/p>\n

Keep Monday off the Hormuz desk. Warnings 150-26 and 151-26 are Sunday projectile and explosion products in the Strait of Hormuz and south of Mokha. They do not identify Royad Mammadov. A Danube-exit dry ship on fire in the Romanian EEZ is a Black Sea SAR and war-risk file, not a UKMTO warning.<\/p>\n

Operational implications<\/h2>\n

Two dead and a sunk hull after a fire in the approaches to the Danube mouth is a crew-welfare, wreck and war-risk event before it is a routing debate. Masters still bound out of Izmail, Reni or Sulina need a written watch for one-way-attack and fire in the Romanian EEZ, not only alongside a Ukrainian berth, and a mustered fire party that can reach the accommodation and the engine room while the ship is still making way. Charterers who have treated the Romanian EEZ as the safe part of a Ukrainian stem should not. JWLA-035 already priced the basin. Monday puts a named sinking on that map within a few hours of a Danube departure.<\/p>\n

Managers who recognise IMO 9356969 should assume flag, class, P&I and the Romanian investigator will ask for the crew list, the fire-and-abandon-ship record, whether a distress message named a weapon, and the last cargo documents. ANR did not publish an IMO. The matching number is still the number to put on the first notice of claim. A television \u201cTurkish grain ship\u201d line is not.<\/p>\n

SAR units were already at sea while the first missing-crew count was 13. The Interior Ministry\u2019s later 11 rescued \/ two dead is the working human tally until ANR or the flag state revises it. Do not brief the file as closed because a helicopter has winched the injured. Wreck position, pollution state and the cause of the fire were not in Monday\u2019s official products. A grain cargo in secondary reporting, if confirmed, is a wreck-removal and food-corridor problem. It is not yet a published MARPOL finding.<\/p>\n

Do not brief Monday as proof that every Danube-exit ship has been hit, that a drone attribution is settled, or that the Romanian EEZ is now inside 12 nautical miles for war-risk purposes. The confirmed facts are Royad Mammadov, a fire outside territorial waters, a sinking, 11 rescued and two dead.<\/p>\n

What Operators Should Note<\/h2>\n