Significance
10 measured / 10 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 10 events
Connected Situation / Through 2026-10-07
Black Sea Commercial Vessel Attacks and Responses
- stories
- 13
- events
- 10
- entities
- 54
- connections
- 13
Evidence so far on 2026-10-07 UTC · updated 2026-10-07 03:23 UTC · analysis as of 2026-10-07 01:26 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
The Events dated 2026-10-05 describe an unidentified drone operator striking a Turkish grain ship near the Pescarus offshore platform, with two fatalities reported, and a Turkish-owned grain vessel sunk in the Black Sea, with no fatalities reported; these descriptions do not establish whether they refer to one incident. On 2026-10-06, the headline “Drone strikes sink one ship and hit another off Bulgaria’s Black Sea coast” reported attacks on commercial vessels, while “Drone strike sinks Turkish cargo ship off Romania, killing two sailors” gave a different location and toll detail. Rumen Radev said the drone origins remained unclear; the Story headline said they might be Russian or Ukrainian, without identifying an operator. India’s Ministry of External Affairs condemned the attack on MV Royad Mammadov, and Angel Naydenov described attacks in Bulgaria’s zone as attacks on the state. Péter Magyar’s headline said Hungary stood with Bulgaria, while a separate Story reported Zelensky’s comments on the attacks at sea near Bulgaria. [Citations are attached to the corresponding evidence IDs.]
Footnotes[8][9][1][2][12][5][13][10][11][3][4]Assessment
The central facts are reported drone attacks on commercial vessels and public responses. The accounts concerning the Turkish-linked vessels and attacks near Bulgaria do not establish who operated those drones. Separately, a coded Event linked to the Bulgaria attack Story describes Russian Armed Forces striking a cargo ship at Yuzhny port; that record does not establish who operated the drones in the Turkish-vessel reports. The two 2026-10-05 Events describe different vessel and casualty details; the Story connection classifying the Romanian sinking report with the Bulgaria attack coverage does not resolve those discrepancies. Radev’s statement preserves uncertainty about the origin of the attacks he discussed, and Vazrazhdane’s characterization of an alleged Russian attack is not independent attribution. The India condemnation names MV Royad Mammadov, while the other ship-attack accounts name different vessels; these records do not establish that they concern the same ship. The linked India condemnation Event is attached to Péter Magyar’s Hungary-support Story, a connection that does not match that Story’s headline and should not be read as evidence that Magyar made the condemnation.
Footnotes[8][9][16][12][5][10][2][1][10][3][17]Explanation originally captured 2026-10-07 · Evidence through 2026-10-07 UTC · Source edition sed_94d2a050c36f55f8f591950854046814
What informs this explanation
- Complete retained Story and Event membership
- Daily reporting and coded-occurrence time steps
- Event taxonomies, metrics, units, and denominators
- Canonical Entities and recorded actor/target bindings
- Typed reporting, membership, and incident edges
- Changes against the preceding retained edition
- Permitted macro, public-record, and asset facts only when they were retained with an explicit source and observation date
Quantitative
Evidence in numbers
- Scope
A 3-day Situation represented by 10 coded Events carried across 13 member Stories.
- Coded activity
The coded activity is led by AIR/DRONE STRIKE (5) and 01 · Make Public Statement (3).
- Prominent subjects
Rumen Radev is prominent in the retained actor and relationship evidence.
- Entity coverage
54 canonical Entities are linked to this edition.
Metric coverage. 10 coded Events · 4 CAMEO+ · 6 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude3.3
min 3max 4
Systemic importance0.09
min 0.07max 0.1
Propagation potential0.27
min 0.25max 0.3
Market sensitivity0.05
min 0.05max 0.05
Dot = mean · shaded span = observed range · position uses each metric’s defined scale.
All 8 scores, distributions & definitions
How the coder scored the full retained Event set
10 coded events — 4 CAMEO+ (4 political) · 6 conflict
- Significance · 100.31min 0.17max 0.45
- Magnitude · 43.3min 3max 4
- Systemic · 40.09min 0.07max 0.1
- Propagation · 40.27min 0.25max 0.3
- Market · 40.05min 0.05max 0.05
- Goldstein · 10-6min -10max 0
- Fatalities · 60min 0max 2
- Confidence · 100.66min 0.34max 0.91
Quad class over those 10 events · Material Conflict 6 · Verbal Cooperation 3 · Verbal Conflict 1. The four CAMEO+ scores are over the 4 CAMEO+ events only; the 6 conflict events have no such column.
Magnitude
4 measured / 4 eligible · 0 missing · 6 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across the 4 of 10 events coded in the CAMEO+ family; the conflict family has no such column
Systemic
4 measured / 4 eligible · 0 missing · 6 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 4 of 10 events coded in the CAMEO+ family; the conflict family has no such column
Propagation
4 measured / 4 eligible · 0 missing · 6 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 4 of 10 events coded in the CAMEO+ family; the conflict family has no such column
Market
4 measured / 4 eligible · 0 missing · 6 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 4 of 10 events coded in the CAMEO+ family; the conflict family has no such column
Goldstein
10 measured / 10 eligible · 0 missing · 0 not applicable
score (-10 to 10) · Event-level distribution, not a Situation risk score.
across the 10 of 10 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics
Fatalities
6 measured / 6 eligible · 0 missing · 4 not applicable
reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.
across the 6 of 10 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event
Confidence
10 measured / 10 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 10 events
This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.
Day by day3 reporting days · click a day to open or close it
2026-10-07from the recordslatest
Russia launches drone attacks on commercial ships in Bulgaria's Black Sea zone
3 Stories and 0 coded Events (-7 / -7 against the day before). Widest coverage: Russia launches drone attacks on commercial ships in Bulgaria's Black Sea zone (10 articles).
- 3-7
- Stories · vs day before
- 0-7
- Events · vs day before
- 13
- articles
The lay of the land
Situation timeline
Threads
All 3 daysarticlesstoriesevents
10-0510-0610-07
Loading Situation timeline…
What kind of event · 4 coded types
over 10 coded events on this edition
- Conflict6
- AIR/DRONE STRIKE5
- SHELLING/ARTILLERY/MISSILE ATTACK1
- Political4
- 01 · Make Public Statement3
- 111 · Criticize or Denounce1
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
AnalystAttacks on commercial vessels
The two attack Stories and the linked coded Events report strikes on Turkish-linked grain vessels, while differing on location and casualty detail.
- development
AnalystUncertain drone origins and maritime-security responses
Radev said the drone origins remained unclear; associated Stories also cover Bulgaria’s security deliberations and public comments on the attacks.
- development
AnalystStatements beyond Bulgaria
Stories describe Hungary’s stated support for Bulgaria and India’s call to end shipping strikes; the linked India condemnation Event is attached to the Hungary Story.
Key actors
- RR
Key Events
contextAnalystDrone operator strikes Turkish grain ship in Black Sea
Dated 2026-10-05, this Event describes an unidentified drone operator striking a Turkish grain ship near the Pescarus offshore platform and reports two fatalities.
Dated 2026-10-05, this Event describes an unidentified drone operator striking a Turkish grain ship near the Pescarus offshore platform and reports two fatalities.
Footnotes[8]contextAnalystA drone hits and sinks a Turkish-owned grain vessel
Dated 2026-10-05, this Event describes an unidentified drone operator striking and sinking a Turkish-owned grain vessel in the Black Sea; no fatalities were reported.
Dated 2026-10-05, this Event describes an unidentified drone operator striking and sinking a Turkish-owned grain vessel in the Black Sea; no fatalities were reported.
Footnotes[9]
contextAnalystRumen Radev says drone origins remain unclear
Dated 2026-10-06, Rumen Radev said the drone origins remained unclear.
Dated 2026-10-06, Rumen Radev said the drone origins remained unclear.
Footnotes[12]
contextAnalystIndia condemns attack on MV Royad Mammadov
Dated 2026-10-06, India’s Ministry of External Affairs condemned the attack on MV Royad Mammadov.
Dated 2026-10-06, India’s Ministry of External Affairs condemned the attack on MV Royad Mammadov.
Footnotes[10]contextAnalystAngel Naydenov calls ship attacks in Bulgaria’s zone attacks on state
Dated 2026-10-06, Angel Naydenov called attacks in Bulgaria’s zone attacks on the state.
Dated 2026-10-06, Angel Naydenov called attacks in Bulgaria’s zone attacks on the state.
Footnotes[11]
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
The Story supports the Event describing a strike on a Turkish grain ship near Pescarus. · reporting linkAnalystDrone strikes sink one ship and hit another off Bulgaria’s Black Sea coast → Drone operator strikes Turkish grain ship in Black Sea
The Event lists this Story as support.
The Romanian sinking Story is also linked to the Event describing the Turkish grain ship strike. · reporting linkAnalystDrone strike sinks Turkish cargo ship off Romania, killing two sailors → Drone operator strikes Turkish grain ship in Black Sea
The Event lists this Story as support; the link does not settle the Stories’ differing location and casualty details.
The Story supports the Event describing a Turkish-owned grain vessel sunk in the Black Sea. · reporting linkAnalystDrone strikes sink one ship and hit another off Bulgaria’s Black Sea coast → A drone hits and sinks a Turkish-owned grain vessel
The Event lists this Story as support.
How a Situation is put together13 Stories · 10 Events · 13 membership connections · 113 graph edges
A retained time step
This edition freezes the complete served membership and analysis available through its UTC cutoff. Later repairs or identity changes do not rewrite what this edition showed.
Stories, Events, and cast
Stories are reporting clusters. Events are coded occurrences within that reporting. The cast contains 54 canonical people and organizations linked to the retained evidence.
Typed connections
Story-to-Event edges identify supporting reporting. Entity-to-Event edges identify recorded actor or target participation. Mentions and analytical roles stay visibly distinct from recorded participation.
Core, precursor, and continuation labels organize the reading. They do not by themselves establish causation. Collapsed graph groups and paginated evidence change presentation only; counts use the complete retained edition.