Seven last listed missing after Black Sea tanker fire

Wine Trader caught fire with 12 sailors aboard. Five were recovered. Seven were still missing in the last detailed rescue accounting—a Romanian Naval Authority communiqué issued on October 15, not a fresh confirmation of their fate on October 18. ^{15 29}

The San Marino-flagged tanker is one of two chemical tankers reported struck by drones near Romania’s Danube coast in successive evening-and-morning incidents. Their fires have sharpened two questions for Romania, Bulgaria and NATO: have attacks on commercial shipping crossed into a member’s territorial waters, and what protection will ships receive? Neither has a settled answer.

Boats and helicopters joined the search in rough seas. BBC News reported on October 16 that five sailors had been airlifted to hospital, but the naval authority’s communiqué confirms recovery without establishing their evacuation method or medical condition. No independently verified rescue accounting for October 17 or 18 establishes what happened afterward. ^{15 3 29}

An October 15 BBC România report put the missing at eight. The authority’s communiqué, issued at 13:07 that day, and subsequent reporting gave seven. Seven is the latest supported count; no explicit explanation for the earlier figure has been established. ^{18 29 30}

The other tanker, the Comoros-flagged Yara J, reportedly suffered a drone strike and fire near Sulina on the evening of October 14. Wine Trader’s incident followed the next morning. Yara J’s crew total and rescue outcome remain unconfirmed. The seven-person missing list belongs to Wine Trader—not to both ships separately, and not to an established combined casualty ledger. ^{17 15 20}

The territorial question matters enormously, but the available location descriptions cannot resolve it. BBC reporting placed Wine Trader 13 nautical miles, or 24 kilometres, east of the Danube’s mouth at Sulina. The naval authority’s accessible communiqué instead says approximately 13 nautical miles southeast, with its reference point missing from the excerpt. A secondary account supplies Sulina. ^{15 29 31}

Reporting also differs on jurisdiction. The Guardian’s October 18 photograph caption places Wine Trader in Romanian territorial waters near Sulina; Reuters’ October 15 report carried by Dawn includes an ARSVOM handout caption using the same territorial description. Arab News, however, describes the incidents as just outside Romania’s territorial waters. Exact coordinates and the applicable legal baseline have not been established, leaving that difference unresolved. ^{2 12 33}

Romania’s territorial sea extends 12 nautical miles from its legal baseline. That is not the same as drawing a circle around Sulina or measuring from the river mouth. A reported position 13 nautical miles from either landmark does not, by itself, prove that a ship was inside or outside the boundary. Yara J has also been described as inside Romanian territorial waters, without a verified position sufficient to settle the claim. An attack inside NATO territory therefore remains unconfirmed. ^{5 20}

Responsibility requires another set of distinctions. Romanian officials reported Russian drones entering the country’s airspace, but initially stopped short of linking those detections to the tanker fires. President Nicușor Dan subsequently described both ships as struck by drones while declining to blame Russia. Detecting a drone nearby, establishing a strike and identifying its launcher are three different evidentiary tasks. ^{10 21}

Dan’s condemnation was unambiguous: attacking commercial ships “is unacceptable and has to stop,” The Guardian reported on October 15. That statement does not resolve attribution. ⁶

Unnamed NATO military sources cited by Reuters, and reported by Global News, attributed the drones to Russia. That is a military assessment, not a publicly documented alliance finding supported here by disclosed technical evidence. Maritime risk firm Ambrey’s estimate that Russian forces were responsible for 80% of attacks, reported by The Guardian and associated with senior analyst Tomas Alexa, lacks an established denominator and precise period. It cannot identify the attacker in either tanker incident on its own. ^{1 2}

The same Guardian account reports Bulgaria’s position that there was no clear and conclusive evidence to blame either side, while arguing that the outcome benefits Russia. Those propositions can coexist: an assessment of who benefits is not proof of who launched a particular attack. ²

The wider sequence has brought burning vessels, sinkings and rescues to commercial routes used by Ukraine. But the human toll cannot responsibly be reduced to one large number. The Guardian’s October 18 standfirst describes six attacks in ten days—not necessarily six distinct ships. Ship Universe’s October 16 account lists seven merchant vessels hit, three sunk and at least 30 sailors dead or missing. No complete incident ledger reconciles those scopes. ^{2 28}

Channel 4 News reported 23 people dead or missing over the preceding ten days on October 15. Global News described more than 20 missing on October 16. These accounts differ in category as well as number; the later wording is not a demonstrated revision of the earlier toll. Neither figure should be added to individual ships’ missing-person lists. ^{4 1}

Alfa Watan, a Turkish-owned, Togo-flagged vessel bound for Sulina, sank after reported drone strikes on October 6. Its explosion was placed about 70 miles from Byala, in Bulgaria’s exclusive economic zone—an area extending beyond territorial waters. The Guardian’s latest detailed account says a responding ferry failed to find its ten crew members. Their ultimate fate remains unresolved. A separate search-closure report mentions ten missing after a sinking but does not clearly link that number to the named ship. ^{22 25 2 42}

There were successful rescues elsewhere: 18 crew members were reported rescued after the Palau-flagged Able caught fire. That outcome cannot explain what happened to another vessel’s missing crew. ²⁵

The sharpest casualty discrepancy concerns Guinea-Bissau-flagged HS Dignity. The Guardian’s October 18 account places its attack on October 12 and says 11 crew members died. AFP’s incident reporting instead dates the attack sequence to October 13; Arab News and CGTN reported 16 aboard, five rescued and 11 missing on October 13–14. Missing is not a confirmed death classification. ^{2 36 40 35}

Fourteen aboard HS Dignity were Syrian nationals. Four rescued sailors—three Syrians and one Egyptian—reached Varna and were described as in relatively good condition. Those four arrivals were part of a five-person rescue total, not a replacement for it. ^{40 35}

Vessel Hunter reported on October 15 that Bulgaria had ended the search the previous day at 15:00 local time, but gave ten missing rather than 11, without explaining the change. No verified body-recovery record, identification or official death declaration establishes the 11-dead claim. Ending a search does not settle every missing person’s fate. ³⁸

HS Dignity was reportedly struck minutes after Ukrainian-owned Chelsea 3, which AFP described as hit by three aerial drones. Rescued Chelsea 3 sailors reached Varna on October 13, but a complete casualty accounting for that vessel remains unavailable. ^{36 38 26}

Romania’s clearest documented immediate response was search and rescue. The political response included Romanian and Bulgarian leaders meeting NATO Secretary General Mark Rutte. Romanian MEP Dan Barna told Channel 4 that he and Bulgarian colleagues had written to EU and NATO officials urging them to treat the Black Sea as a critical part of the alliance’s eastern flank. His description of the incidents as Russian attacks remains his assessment. ^{7 4}

Barna described a further NATO meeting in the following days; France 24 reported a timetable pointing to the following week. Neither establishes a firm date or a completed protection decision. No Article 4 request, Article 5 invocation or collective-defence operation has been established. Meetings and calls for action are not evidence that military protection has been authorized. ^{4 11 16}

The commercial exposure predates these fires. Insurance Business reported that the London insurance market expanded its Black Sea high-risk area in September, less than three weeks before the October 6 attacks. The available account does not establish a measurable premium increase. Higher insurance costs, fewer willing ships and disrupted Ukrainian agricultural exports are risks—not quantified losses demonstrated by this reporting. ^{23 2}

The boundary dispute deserves an answer, as does attribution. But commercial crews do not become less exposed because a strike falls outside a territorial line. The immediate test for Romania, Bulgaria and NATO is whether they can turn concern into credible shipping protection while accounting for the missing. Neither task is finished.