Significance
16 measured / 16 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 16 events
Connected Situation / Through 2026-10-22
Lithuania Drone Crash and Cross-Border Response
- stories
- 18
- events
- 16
- entities
- 86
- connections
- 18
Frozen through 2026-10-22 UTC · published 2026-10-23 02:31 UTC · analysis as of 2026-10-22 02:30 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
On 18 October 2026, a drone carrying explosives crashed in Lithuania; the coded Event labels it Ukrainian, while “Exploded drone may have damaged a civilian car, latest report says” qualifies possible car damage and “Lithuania keeps air-attack alert in Panevėžys, lifts warnings elsewhere” describes an alert retained in Panevėžys and warnings lifted elsewhere. Lithuania asked Poland to investigate the crash; the coded Event characterizes this as a joint-investigation request. On 19 October, Deividas Matulionis said the drone crossed Poland’s border, Defence Minister Robertas Kaunas explained why it was not shot down, and the Lithuanian Armed Forces bolstered protection of critical infrastructure. On 20 October, Donald Tusk sought Ukraine’s help with the probe and Gitanas Nausėda said disclosure about the incident must wait; “Poland and Lithuania clash over a Ukrainian drone incident” frames the bilateral fallout. Lithuania sought NATO consultations on broader authority to shoot down airspace intruders, including drones detected without visual confirmation; the 19 and 20 October headlines describe the same proposal, which was a request, not an adopted rule. On 21 October, “Tusk demands Ukraine explain Lithuania drone blast after it flew from Poland” reported a demand for an explanation.
Footnotes[9][6][5][10][16][14][17][4][11][15][2][29]Assessment
The crash Event labels the drone Ukrainian, and Matulionis’s statement attributes a route across Poland’s border; those claims do not establish who launched or diverted the drone. Poland’s Defence Ministry rejected a report about a launch site, which does not itself resolve the drone’s route or responsibility. Lithuania’s joint-investigation request and the Polish defence minister’s contact with his Lithuanian counterpart sit alongside the “clash” framing, so the headlines and actions show both diplomatic tension and cooperation without establishing a resolution. Lithuania’s NATO consultation proposal does not establish a change in engagement rules. Blue/Yellow’s interceptor-drone transfer is a separate defensive measure, not evidence about the crash’s origin.
Footnotes[9][16][13][10][12][2][29][27][8][3]Explanation originally captured 2026-10-22 · Evidence through 2026-10-22 UTC · Source edition sed_5a5cbf0cc5149bf9c19b6f3676f533eb
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 5-day Situation represented by 16 coded Events carried across 18 member Stories.
- Coded activity
The coded activity is led by 01 · Make Public Statement (5) and OTHER (3).
- Prominent subjects
Deividas Matulionis, Lithuanian Armed Forces, and Gitanas Nausėda are prominent in the retained actor and relationship evidence.
- Entity coverage
86 canonical Entities are linked to this edition.
Metric coverage. 16 coded Events · 11 CAMEO+ · 5 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude2.4
min 1max 3
Systemic importance0.12
min 0.1max 0.27
Propagation potential0.28
min 0.24max 0.34
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
16 coded events — 11 CAMEO+ (9 political) · 5 conflict
- Significance · 160.22min 0.13max 0.36
- Magnitude · 112.4min 1max 3
- Systemic · 110.12min 0.1max 0.27
- Propagation · 110.28min 0.24max 0.34
- Market · 110.05min 0.05max 0.05
- Goldstein · 14-0.5min -9.5max 8.3
- Fatalities · 50min 0max 0
- Confidence · 160.68min 0.28max 0.82
Quad class over those 14 events · Verbal Cooperation 8 · Verbal Conflict 3 · Material Conflict 2 · Material Cooperation 1. 2 sit outside POLITICAL, where Goldstein and quad class are undefined. The four CAMEO+ scores are over the 11 CAMEO+ events only; the 5 conflict events have no such column.
Magnitude
11 measured / 11 eligible · 0 missing · 5 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across the 11 of 16 events coded in the CAMEO+ family; the conflict family has no such column
Systemic
11 measured / 11 eligible · 0 missing · 5 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 11 of 16 events coded in the CAMEO+ family; the conflict family has no such column
Propagation
11 measured / 11 eligible · 0 missing · 5 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 11 of 16 events coded in the CAMEO+ family; the conflict family has no such column
Market
11 measured / 11 eligible · 0 missing · 5 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 11 of 16 events coded in the CAMEO+ family; the conflict family has no such column
Goldstein
14 measured / 14 eligible · 0 missing · 2 not applicable
score (-10 to 10) · Event-level distribution, not a Situation risk score.
across the 14 of 16 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics
Fatalities
5 measured / 5 eligible · 0 missing · 11 not applicable
reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.
across the 5 of 16 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event
Confidence
16 measured / 16 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 16 events
This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.
Day by day5 reporting days · click a day to open or close it
2026-10-22from the recordslatest
Lithuanian prime minister says Russia tests NATO Article 5 limits
1 Story and 1 coded Event (-2 / +1 against the day before). Widest coverage: Lithuanian PM says Russia is testing the limits of NATO's Article 5 (1 articles).
- 1-2
- Stories · vs day before
- 1+1
- Events · vs day before
- 1
- articles
The lay of the land
Situation timeline
Threads
All 5 daysarticlesstoriesevents
10-1810-1910-2010-2110-22
Loading Situation timeline…
What kind of event · 8 coded types
over 16 coded events on this edition
- Political9
- 01 · Make Public Statement5
- 0213 · Judicial2
- 04 · Consult1
- 072 · Provide Military Aid1
- Conflict4
- OTHER3
- DISRUPTED WEAPONS USE1
- Infrastructure2
- IN02 · Transport Disruption2
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
AnalystCrash, investigation and official response
The crash, alert reporting, investigation requests and official responses establish the incident’s immediate dimensions and cross-border diplomatic context.
- development
AnalystInterceptor-drone support
Blue/Yellow transferred interceptor drones to the Lithuanian Riflemen’s Union; the linked Story describes the Dronathon campaign as supporting air defense for Ukraine and Lithuania.
Key actors
- DM
- LA
- GN
- DT
Key Events
contextAnalystUkrainian drone carrying explosives crashes in Lithuania
On 18 October 2026, a drone carrying explosives crashed in Lithuania; the Event labels it Ukrainian.
On 18 October 2026, a drone carrying explosives crashed in Lithuania; the Event labels it Ukrainian.
Footnotes[9]
contextAnalystLithuania asks Poland to jointly investigate drone crash
On 18 October 2026, Lithuania asked Poland to investigate the drone crash jointly.
On 18 October 2026, Lithuania asked Poland to investigate the drone crash jointly.
Footnotes[10]contextAnalystDeividas Matulionis says drone crossed Poland’s border
On 19 October 2026, Deividas Matulionis said the drone crossed Poland’s border.
On 19 October 2026, Deividas Matulionis said the drone crossed Poland’s border.
Footnotes[16]contextAnalystLithuanian minister Kaunas explains why drone was not shot down
On 19 October 2026, Defence Minister Robertas Kaunas explained why the drone was not shot down.
On 19 October 2026, Defence Minister Robertas Kaunas explained why the drone was not shot down.
Footnotes[14]contextAnalystLithuanian Armed Forces bolster protection of critical infrastructure
On 19 October 2026, the Lithuanian Armed Forces bolstered protection of critical infrastructure.
On 19 October 2026, the Lithuanian Armed Forces bolstered protection of critical infrastructure.
Footnotes[17]
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
made the statement that the drone crossed Poland’s border · recorded participationAnalystDeividas Matulionis → Deividas Matulionis says drone crossed Poland’s border
The Event identifies Deividas Matulionis as the source actor for the statement.
bolstered protection of critical infrastructure · recorded participationAnalystLithuanian Armed Forces → Lithuanian Armed Forces bolster protection of critical infrastructure
The Event identifies the Lithuanian Armed Forces as its source actor.
is linked to the security-meeting Story · reporting linkAnalystUkrainian drone carrying explosives crashes in Lithuania → Lithuanian president convenes security meeting after drone incident
The crash Event is linked to “Lithuanian president convenes security meeting after drone incident.”
How a Situation is put together18 Stories · 16 Events · 18 membership connections · 186 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 86 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.