Three Black Sea states promise better warning. The Constanța route lacks an escort plan

What the ministers put in the statement

Romania's ministry says the ministers discussed a common maritime picture, information exchange and coordination among their navies. The joint text reported by Anadolu promises measures to increase early-warning capability and intelligence sharing, with NATO coordination when necessary. Officials also anticipated later consultations in Ankara and Bucharest. They gave no timetable for putting the agreed measures into operation.

The three navies already cooperate through MCM Black Sea, a mine-countermeasures effort. Romania's release calls for its continuation. Mine hunting and clearing address a different hazard from a fast sea drone heading toward a moving ship. The Sofia meeting did not turn that existing mission into escorts, and the joint statement did not assign MCM vessels to protect the Constanța route.

The rescue and its limit as a protection test

According to the Bulgarian defence minister as reported by Reuters, three sea drones hit the CONTSHIP JET about 21 miles southeast of Shabla. The Liberian-flagged, Greek-owned vessel was travelling from Haifa to Constanța. That position was in Bulgaria's exclusive economic zone, not its territorial waters. The ship's destination makes the incident a direct concern for Romania even though the response began off Bulgaria.

Bulgarian authorities dispatched boats and evacuated all 18 crew members. That response brought people off a damaged ship after impact. The published account gives no time for the first detection or any warning before the drones arrived. Nor does it place an escort beside the CONTSHIP JET. The rescue is evidence that responders reached this crew, while pre-impact protection for the ship remains unmeasured.

From a shared track to action on the route

A coastal radar or patrol report could help neighbouring authorities follow an approaching object across areas watched by different services. That benefit depends on a common method for passing the track quickly enough to matter. The Sofia statement gives no lead state, alert recipient or response rule for a threatened ship. The ministers have not identified whether a coastal command, navy or civilian maritime authority would relay an alert to commercial traffic. Nor have they said which force could respond as a vessel approaches Constanța beyond national territorial waters. Information sharing can support a decision, but the published commitment leaves that decision chain undefined.

“The Sofia statement gives no lead state, alert recipient or response rule for a threatened ship.”

The attacker question is separate from the response design. Reuters reported no identified launcher for the 28 October strike. Examining recovered drone material, surveillance tracks and any communications would be needed to attribute this incident. Türkiye's warning to both warring parties and the three ministers' condemnation of ship attacks express their policy positions. Neither replaces evidence identifying who launched these three drones. Russia remains responsible for its aggression against Ukraine regardless of what an investigation finds about this ship.

Romania, Bulgaria and Türkiye committed to better sharing of maritime intelligence and earlier warnings, alongside their existing mine work. For vessels bound for Constanța, they have not yet provided a published escort, common interception procedure or shipmaster alert channel. A named operating centre, agreed alert and response rules, and incident records showing a warning delivered before impact or protective forces acting on a detected sea drone would demonstrate that the Sofia pledge has become a usable service. The successful evacuation of this crew establishes a rescue outcome, not that route-wide protection is already in place.