Significance
98 measured / 98 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 98 events
Connected Situation / Through 2026-10-24
Black Sea Commercial Shipping Attacks and Security Response
- stories
- 147
- events
- 98
- entities
- 316
- connections
- 147
Evidence so far on 2026-10-24 UTC · updated 2026-10-24 10:21 UTC · analysis as of 2026-10-24 05:32 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
On 5 October, an unidentified drone operator struck a Turkish grain ship near the Pescarus offshore platform; one Event record reports two fatalities. However, other Event records linked to overlapping ship reports give a different date, location or fatality count. On 6 October, “Drone strikes sink one ship and hit another off Bulgaria’s Black Sea coast” and “Drone strike sinks Turkish cargo ship off Romania, killing two sailors” reported attacks in different locations and with different tolls, but overlapping Story links and conflicting Event records do not establish that these were separate incidents. On 9 October, Rumen Radev said the evidence did not identify who struck the ships, while Turkey proposed Black Sea shipping corridors. On 13 October, Bulgaria asked the EU and NATO to help investigate the attacks, and Ursula von der Leyen condemned them. Romania proposed a joint NATO command in proposals reported on 14, 15 and 18 October; NATO announced additional patrol aircraft and drones on 21 October. On 23 October, “Drone strike sinks ship near Constanța, Romania; one sailor dead, three missing” reported a further fatal sinking, while the European Parliament’s call to assess a Black Sea naval mission remained a proposal.
Footnotes[24][19][20][42][16][39][33][9][40][21][1][36]Assessment
The accounts establish repeated reports of drone-related attacks on commercial shipping and a widening diplomatic and security response, but they do not establish that every account concerns a distinct incident or that one actor was responsible for all of them. A specific Event attributes a strike to Russian forces, while Radev said the evidence did not identify who struck the ships; neither statement establishes responsibility for all the reported attacks. Appeals for investigation, proposed corridors, a proposed joint command and the European Parliament’s call to assess a naval mission are not evidence that those proposals were implemented. Compared with the prior edition’s 22 October endpoint, the account now includes 23 October reporting on the Constanța-area sinking, regional security discussions and shipowners’ reported fuel-supply disruption.
Footnotes[19][20][24][25][18][42][40][36][1][2][3][30]Explanation originally captured 2026-10-24 · Evidence through 2026-10-24 UTC · Source edition sed_28f5ed73ada9ca63133966cea4370c32
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 21-day Situation represented by 98 coded Events carried across 147 member Stories.
- Coded activity
The coded activity is led by AIR/DRONE STRIKE (12) and 01 · Make Public Statement (10).
- Prominent subjects
NATO, European Union, and Rumen Radev are prominent in the retained actor and relationship evidence.
- Entity coverage
316 canonical Entities are linked to this edition.
Metric coverage. 98 coded Events · 84 CAMEO+ · 14 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude2.9
min 1max 7
Systemic importance0.14
min 0.05max 0.55
Propagation potential0.31
min 0.18max 0.51
Market sensitivity0.07
min 0.05max 0.38
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
98 coded events — 84 CAMEO+ (78 political) · 14 conflict
- Significance · 980.29min 0.13max 0.59
- Magnitude · 842.9min 1max 7
- Systemic · 840.14min 0.05max 0.55
- Propagation · 840.31min 0.18max 0.51
- Market · 840.07min 0.05max 0.38
- Goldstein · 92-0.6min -10max 8.3
- Fatalities · 140min 0max 2
- Confidence · 980.68min 0.3max 0.97
Quad class over those 92 events · Verbal Cooperation 56 · Material Conflict 19 · Verbal Conflict 15 · Material Cooperation 2. 6 sit outside POLITICAL, where Goldstein and quad class are undefined. The four CAMEO+ scores are over the 84 CAMEO+ events only; the 14 conflict events have no such column.
Magnitude
84 measured / 84 eligible · 0 missing · 14 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across the 84 of 98 events coded in the CAMEO+ family; the conflict family has no such column
Systemic
84 measured / 84 eligible · 0 missing · 14 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 84 of 98 events coded in the CAMEO+ family; the conflict family has no such column
Propagation
84 measured / 84 eligible · 0 missing · 14 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 84 of 98 events coded in the CAMEO+ family; the conflict family has no such column
Market
84 measured / 84 eligible · 0 missing · 14 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 84 of 98 events coded in the CAMEO+ family; the conflict family has no such column
Goldstein
92 measured / 92 eligible · 0 missing · 6 not applicable
score (-10 to 10) · Event-level distribution, not a Situation risk score.
across the 92 of 98 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics
Fatalities
14 measured / 14 eligible · 0 missing · 84 not applicable
reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.
across the 14 of 98 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event
Confidence
98 measured / 98 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 98 events
This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.
Day by day21 reporting days · click a day to open or close it
2026-10-24from the recordslatest
Russian forces strike cargo ship carrying supplies for Ukraine’s army
5 Stories and 2 coded Events (-7 / -4 against the day before). Widest coverage: Russia says it struck cargo ship bound for Odesa with supplies for Ukraine's army (10 articles). Recorded acting: Andrii Sybiha.
- 5-7
- Stories · vs day before
- 2-4
- Events · vs day before
- 15
- articles
The lay of the land
Situation timeline
Threads
All 21 daysarticlesstoriesevents
10-0410-0810-1210-1610-2010-24
Loading Situation timeline…
What kind of event · 37 coded types
over 98 coded events on this edition
- Political78
- 01 · Make Public Statement10
- 111 · Criticize or Denounce7
- 0256 · De-escalate Military5
- 04 · Consult5
- 041 · Discuss By Telephone5
- 02 · Appeal4
- 046 · Engage in Negotiation4
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
AnalystReported attacks on Black Sea commercial shipping
These accounts describe attacks, sinkings and missing or injured crew off Bulgaria and Romania; differences in vessel, location and toll do not establish that all reports refer to the same incident.
- development
AnalystInvestigation, diplomacy and security measures
Bulgaria appealed for investigative help, Romania proposed a joint NATO command, and NATO announced additional patrol aircraft and drones. Turkey’s shipping-corridor proposal and the European Parliament’s call to assess a naval mission were proposals, not established implementations.
Bulgaria appealed for investigative help, Romania proposed a joint NATO command, and NATO announced additional patrol aircraft and drones. Turkey’s shipping-corridor proposal and the European Parliament’s call to assess a naval mission were proposals, not established implementations.
Footnotes[39][40][21][16][36] - development
Key actors
- N
AnalystNATO
NATO announced additional patrol aircraft and drones for the Black Sea; Bulgaria also expressed intent to provide €80 million to NATO’s Drone Edge initiative.
- EU
- RR
- ND
AnalystNicușor Dan
Nicușor Dan took part in Black Sea security discussions with Mark Rutte and Rumen Radev.
Nicușor Dan took part in Black Sea security discussions with Mark Rutte and Rumen Radev.
Footnotes[26] - MR
AnalystMark Rutte
Mark Rutte took part in Black Sea security discussions with Nicușor Dan and Rumen Radev.
Mark Rutte took part in Black Sea security discussions with Nicușor Dan and Rumen Radev.
Footnotes[26]
Key Events
contextAnalystDrone operator strikes Turkish grain ship in Black Sea
An unidentified drone operator struck a Turkish grain ship near the Pescarus offshore platform; the Event reports two fatalities.
An unidentified drone operator struck a Turkish grain ship near the Pescarus offshore platform; the Event reports two fatalities.
Footnotes[24]
contextAnalystUnidentified drone operator attacks two merchant ships in Black Sea
An Event describes an unidentified drone operator attacking two merchant ships in Bulgaria’s exclusive economic zone.
An Event describes an unidentified drone operator attacking two merchant ships in Bulgaria’s exclusive economic zone.
Footnotes[25]
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
Romanian PNL MEPs sought European funding for Black Sea defenses from the European Commission. · recorded participationAnalystRomanian PNL MEPs seek European funding for Black Sea defenses → European Commission
The Event identifies the European Commission as the target of the funding appeal.
The Story reports Bulgaria’s appeal to the EU and NATO for help investigating drone attacks. · reporting linkAnalystBulgaria seeks EU and NATO help probing drone attacks on two Black Sea ships → Bulgaria asks EU and NATO to help investigate drone attacks
The Event lists the Story as supporting its account of Bulgaria’s investigative appeal.
How a Situation is put together147 Stories · 98 Events · 147 membership connections · 1,428 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 316 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.