Human editorial review before publication · Member of the Intelligence.Navy Maritime Intelligence Team · 13 Oct 2026 · 15:54 UTC. Incident verification remains separate.
Research context & editorial review- Original source published
- 13 Oct 2026 · 08:00 UTC
- Analysis reviewed
- 13 Oct 2026 · 09:11 UTC
- Human review
- 13 Oct 2026 · 15:54 UTC
- Added to portal
- 13 Oct 2026 · 09:01 UTC
- Source check
- 13 Oct 2026 · 09:01 UTC
External source reporting used in this assessment
Key judgment
Bulgarian primary reporting confirms that Chelsea 3 was struck, its 15-person crew was evacuated and the ship became an unmanned hazard off Byala, while a coastal warning identifies the vessel by IMO and requires other ships to keep clear. The same official account reports a second ship sunk east of Krapets but does not identify it, and explicitly says Bulgaria lacks solid evidence to attribute the drones. The sustainable judgment is therefore a repeat commercial-shipping security event with a specific local navigation and rescue consequence, not a verified identity for the second casualty, a general route closure or proof of the attacker (E2, E3, E4, E5).
Chelsea 3 was reported struck east of Byala; all 15 crew were evacuated and five received medical assistance.
A coastal warning identifies Chelsea 3 as IMO 9361392, at anchor without crew at 02:30 UTC on 13 October, with a safety-distance instruction.
The Bulgarian government separately reported a second ship sunk east of Krapets with one crew member rescued, but did not identify that vessel in the primary statement.
SOURCE PHOTOGRAPHImage from the source publication.
What we learned
The Splash feed established that two more ships were reportedly hit but stopped mid-summary. Follow-up fixes the chronology and stable identity for Chelsea 3: a distress signal at about 01:30 local reporting, a named Malta-flagged ship, 15 crew recovered, five receiving medical assistance, and a later coastal warning giving IMO 9361392, a position and an unmanned-at-anchor status. It also separates the second reported sinking from Chelsea 3 and from the October 6 incidents. Unlike the previous ABLE draft, which assessed a damaged ship from the earlier attack, this is a new dated event and a different named vessel; however, the identity of the second sunken ship and responsibility for either October 13 attack remain unsettled (E1, E2, E3, E4, E5).
Maritime implication
For maritime activity, the immediate consequence is operationally bounded: vessels east of Cape Sveti Atanas should account for an unmanned casualty and a safety-distance warning, while Bulgarian search-and-rescue and surveillance resources are handling another reported sinking farther north. Repetition within one week raises planning, watchkeeping, insurance and diversion risk for commercial traffic near Bulgaria, but no retrieved primary source establishes a port closure, a closed coastal corridor or a Black Sea-wide suspension of trade (E2, E3, E4).
Confidence & evidence limits
MODERATE · Confidence is high in Chelsea 3's identity, crew evacuation and the local hazard because the Bulgarian Council of Ministers names the vessel and a reproduced coastal warning supplies the IMO and position. Overall confidence is moderate because the navigational warning was accessible only through an indexed mirror, the second ship remains unnamed in the primary account, casualty figures conflict across early reports, and Bulgaria says attribution evidence is not yet solid (E2, E3, E4, E5).
Evidence & analytical reasoning
Reported · Chelsea 3 was reported struck east of Byala; all 15 crew were evacuated and five received medical assistance.[2]
Reported · A coastal warning identifies Chelsea 3 as IMO 9361392, at anchor without crew at 02:30 UTC on 13 October, with a safety-distance instruction.[3]
Reported · The Bulgarian government separately reported a second ship sunk east of Krapets with one crew member rescued, but did not identify that vessel in the primary statement.[2]
Analytical inference · Early public accounts conflict over the identity of the second ship, so no name or IMO should be attached to that sinking yet.[2][5]
Analytical inference · The immediate proven maritime consequence is a local casualty and safety-distance requirement, not a verified closure of Bulgarian ports or a general coastal corridor.[2][3]
Analytical inference · Available primary statements do not establish which party launched the drones.[2][4]
Next decision indicators
- Official cancellation or update of NAVWARN 717/26, including a new Chelsea 3 position, towage, salvage or port-of-refuge decision.
- IMO-confirmed identity, flag, crew list and casualty status for the second sunken vessel east of Krapets.
- Search-and-rescue outcome and any transition from rescue to recovery operations.
- Pollution observations, cargo declaration and hull-condition reporting for both casualties.
- Recovered drone debris, forensic findings or an official investigative attribution.
- Bulgarian, Romanian or Turkish navigation restrictions, port measures or documented operator rerouting linked to the incidents.
Publication history · 1 captured version
Loading captured versions…
Evidence & references
- [1] Two more ships hit off BulgariaSource account
- [2] Bulgarian Council of Ministers: emergency Security Council meeting after a new attack 18 miles east of ByalaCandidate linkage · unconfirmed
- [3] Bulgaria Coastal NAVWARN 717/26: Chelsea 3 east of Cape Sveti AtanasCandidate linkage · unconfirmed
- [4] Bulgarian Council of Ministers: no hypotheses without evidence after the October 6 attacksContext reference
- [5] Bulgarian reporting notes competing identities for the second shipContext reference
Evidence scope & unresolved questions
- The second sunken ship is not named in the Bulgarian government's October 13 statement, and early secondary reports give conflicting identities.
- The total crew complement, missing-person count, cargo and pollution status for the second casualty were not established in the retrieved primary material.
- Chelsea 3's condition after the 02:30 UTC navigational warning, including damage, towage and pollution status, requires later official follow-up.
- The official Bulgarian MSI source for NAVWARN 717/26 was not accessible; only an indexed mirror was retrieved.
- No technical evidence retrieved attributes the drones to a state or non-state actor.
- No primary source retrieved establishes a port closure, route closure or quantified traffic disruption.
AI-assisted research, followed by recorded human editorial approval. Approval is not independent verification of the incident.. AI-assisted synthesis with recorded human editorial review; event verification remains limited by the attached sources.
Two more ships hit off Bulgaria: Indexed excerpt; live page content was not verified. The original page was not accessible to the retrieval tool; the portal retained only a truncated feed excerpt and it is not independent confirmation.
Bulgarian Council of Ministers: emergency Security Council meeting after a new attack 18 miles east of Byala: Indexed excerpt; live page content was not verified. Government press statement, not the final casualty, forensic or marine-investigation report; times are reported as published without a confirmed UTC conversion.
Bulgaria Coastal NAVWARN 717/26: Chelsea 3 east of Cape Sveti Atanas: Indexed excerpt; live page content was not verified. Indexed third-party reproduction of a coastal warning; the official Bulgarian MSI endpoint was not located, so status and later cancellation require official confirmation.
Bulgarian Council of Ministers: no hypotheses without evidence after the October 6 attacks: Indexed excerpt; live page content was not verified. Refers to the October 6 incidents rather than the October 13 attacks; it is used only to establish the unresolved investigative baseline.
Bulgarian reporting notes competing identities for the second ship: Indexed excerpt; live page content was not verified. Secondary report presenting unresolved competing accounts; neither vessel identity is treated as confirmed.