Short answer: On Oct 28, 2026, uncrewed surface vessels (USVs) sank the small feeder ship Contship Jet in Bulgaria's exclusive economic zone (EEZ). It was the fifth drone attack in Bulgaria's EEZ this month (AP). The ships hit don't share an owner or a flag. They share a corridor. Our read: the target is the route, not any single ship. The drones were spotted in time to warn the crew, but Bulgaria says it had no mandate to act outside its territorial waters. That points to a gap in authority and response time more than in sensing.
What happened
- Around noon local time on Oct 28, 2026, USVs hit the Liberian-flagged, Greek-managed Contship Jet roughly 16 to 21 nautical miles off Cape Kaliakra. It was carrying 421 containers from Haifa to Constanța. All 18 crew were rescued, and the ship sank around midnight (BTA; gCaptain/Reuters). Three drones were involved. Reports differ on whether all three struck or whether one was destroyed by small-arms fire.
- A French Navy Atlantique 2 patrol aircraft detected the drones and warned the crew and Bulgarian authorities (ziare.com, quoting the French General Staff). One report puts the warning at about 30 minutes before the attack.
- On Oct 30, 2026, Bulgaria joined NATO's project on lower-level air threats (NATO). Nothing announced so far deals with drone boats or with authority to intercept in the EEZ.
Why couldn't anyone stop the drones?
The drones were moving at about 26 knots, according to Bulgaria's Navy commander, Rear Adm. Kiril Mihaylov. "We did not have the forces and means in the nearby area that could go quickly and intercept and destroy them," he said (Fakti). Bulgaria's chief of defence, Adm. Emil Eftimov, put the legal limit plainly: "Do we act outside territorial waters? No. We don't have a mandate for that" (translated, via ziare.com).
Who attacked the Contship Jet?
That's unproven. The maritime risk firm Ambrey assessed the drone as "likely a variant of, or derived from" Russia's Murena-300S design (Reuters via gCaptain). Prime Minister Rumen Radev said, "Logic leads there, but ... we cannot prove it" (Fakti). Moscow denies involvement. The ship's Israeli links (a Haifa origin and a ZIM charter) are facts. Nothing shows they were the motive: the same pattern has hit Turkish, Ukrainian and other ships.
Why we say the target is the route
The five ships hit in Bulgaria's EEZ this month flew the flags of Togo, Palau, Malta, Guinea-Bissau and Liberia, under a mix of owners, on different voyages. What they share is the western Black Sea corridor.
One pattern we're testing is a hypothesis, not a finding. Where we know the destinations, they're Romanian and Danube ports (Constanța, Brăila, Sulina, Giurgiulești), which carry trade tied to Ukraine. If that holds, "the route" could mean Ukraine's alternative export corridor specifically. We don't know where two of the ships were headed, so we can't say yet.
Count the cost-exchange ratio per corridor, not per shot
Per ship, the trade looks modest. Three drones like Ukraine's Magura cost an estimated $0.75M to $0.9M (USNI Proceedings prices one at $250K to $300K). One automated valuation, low-confidence, puts a 2007 feeder at about $2M. That's a cost-exchange ratio of only about 2 or 3 to 1, and cargo value is unknown.
The bigger bill may land on every ship using the lane, and every navy guarding it:
- War-risk premiums reportedly rose from about 0.1% to 0.5% of hull value in two weeks (Splash247, via Forwarder News), and to 0.6% to 1% on some voyages (Capital.bg). These are market reports, not official rates.
- Hugging the coast adds about 90 to 100 nm each way, roughly $20,000 per Istanbul–Constanța round trip, by an unnamed estimate reported by Capital.bg.
- Defenders pay for patrol aircraft, radars and drones.
We can't total that yet, because we don't have voyage counts for the corridor. And trade hasn't been deterred so far. Before Oct 28, the Port of Varna reported volumes up year on year, and Turkish insurers said there's "no general suspension" of cover (World Ports Organization). The cost is rising. The lane is still open.
What it means for you
- Defense acquisition and planners: the requirement gap looks like the response, not the sensor. The drones were seen and the crew was warned, but no one close enough had both the assets and the authority to stop them. In our search, we found no dedicated US counter-USV program announced in 2026. That's an absence of evidence, not proof. The Defense Innovation Unit's (DIU) SWAP-USV Sprint 2 is counter-air from drone boats, not defense against them (Navy DRPM RAS).
- Investors, including government-backed funds: counter-USV is possible whitespace. We found no dedicated program, which is absence of evidence, and there's no named buyer or budget yet. Be wary of sensor-only pitches; sensing wasn't what failed here (our view).
- LA founders: Torrance's Epirus has a high-power microwave (HPM) system, Leonidas H₂O, that disabled outboard motors in a Navy test at about half power (Epirus; Defense News). Whether it fits Murena-type drones is unproven.
Open questions we're tracking
- Is the pattern skewed toward Ukraine-linked trade? That needs voyage and port-call counts.
- Have insurance and freight costs kept rising since Oct 28?
- What would Bulgaria's draft peacetime-powers changes allow in its EEZ?
- Has any US program bought defenses against drone boats this year?
The question we're asking: who has the authority and the assets to act on a detected threat in an ally's EEZ, inside about 30 minutes of warning?
Your turn: if you work on maritime defense, rules of engagement or counter-USV systems, reply with your answer, and follow LA Robotics Network for updates as this story develops.

