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-24
Lithuania Drone Crash and Cross-Border Response
- stories
- 18
- events
- 16
- entities
- 86
- connections
- 18
Frozen through 2026-10-24 UTC · published 2026-10-25 02:28 UTC · analysis as of 2026-10-24 02:29 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, and Lithuania asked Poland to investigate the crash jointly; “Lithuania asks Poland to investigate a drone incident” reported the request. [The crash] is described in “Lithuanian president convenes security meeting after drone incident.” Lithuania also kept an air-attack alert in Panevėžys while lifting warnings elsewhere, as “Lithuania keeps air-attack alert in Panevėžys, lifts warnings elsewhere” reported. On 19 October, Deividas Matulionis said the drone crossed Poland’s border, while Poland’s Defence Ministry rejected a report about the drone’s launch site. [The same date], the Lithuanian Armed Forces bolstered protection of critical infrastructure, and Władysław Kosiniak-Kamysz contacted Lithuania’s defence minister. On 20 October, Donald Tusk sought Ukraine’s help with the probe and Gitanas Nausėda said disclosure must wait; “Poland and Lithuania clash over a Ukrainian drone incident” covered the dispute. Lithuania also sought NATO talks on expanded authority to shoot down airspace intruders, while Blue/Yellow transferred interceptor drones to the Lithuanian Riflemen’s Union.
Footnotes[14][15][12][8][10][20][18][22][17][16][19][4]Assessment
The coded crash description calls the drone Ukrainian, but neither that label nor Matulionis’s statement that it crossed Poland’s border establishes who launched or diverted it. Poland’s Defence Ministry rejected a report about the launch site; that statement does not by itself resolve the route claim. Lithuania’s joint-investigation request and the Polish-Lithuanian defence-minister contact establish cooperation alongside the “clash” framing, not a settled account of bilateral relations. Lithuania’s NATO talks were sought, not an adopted change to shootdown rules. Blue/Yellow’s transfer of interceptor drones is a separate air-defence action and does not establish the crash’s origin. The crash Event reports no fatalities.
Footnotes[14][20][18][15][17][4][9][5][13][6]Explanation originally captured 2026-10-24 · Evidence through 2026-10-24 UTC · Source edition sed_0cbbf476d0fc0659c6b18c5640059ca5
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-22analystlatest
Lithuanian prime minister’s Article 5 statement
The Lithuanian prime minister said Russia was testing NATO Article 5 limits. This is an attributed political statement, not an established finding about responsibility for the drone crash.
- 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, Lithuania’s request for Polish investigative cooperation, statements about the route, and official security measures make this the central incident thread.
- development
AnalystNATO consultation and drone-readiness debate
Lithuania’s proposed consultation on shootdown authority and the reported concern about readiness against drone swarms document a related policy discussion.
- development
AnalystInterceptor-drone support
Blue/Yellow transferred interceptor drones to the Lithuanian Riflemen’s Union; this air-defence support is distinct from crash attribution.
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 describes it as Ukrainian and reports no fatalities.
On 18 October 2026, a drone carrying explosives crashed in Lithuania; the Event describes it as Ukrainian and reports no fatalities.
Footnotes[14]
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[15]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[20]contextAnalystPoland’s Defence Ministry rejects report on drone launch site
On 19 October 2026, Poland’s Defence Ministry rejected a report about the drone’s launch site.
On 19 October 2026, Poland’s Defence Ministry rejected a report about the drone’s launch site.
Footnotes[18]contextAnalystPolish defense minister contacts Lithuanian counterpart over drone incident
On 19 October 2026, Władysław Kosiniak-Kamysz contacted Lithuania’s defence minister about the incident.
On 19 October 2026, Władysław Kosiniak-Kamysz contacted Lithuania’s defence minister about the incident.
Footnotes[17]
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
said the drone crossed Poland’s border · recorded participationAnalystDeividas Matulionis → Deividas Matulionis says drone crossed Poland’s border
The Event identifies Deividas Matulionis as the actor making 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 actor.
said disclosure about the drone incident must wait · recorded participationAnalystGitanas Nausėda → Nausėda says disclosure on drone incident must wait
The Event identifies Gitanas Nausėda as the actor making the statement.
sought Ukraine’s help with the drone probe · recorded participationAnalystDonald Tusk → Donald Tusk seeks Ukraine's help in Lithuania drone probe
The Event identifies Donald Tusk as the actor seeking Ukraine’s help.
is linked to “Lithuanian president convenes security meeting after drone incident” · reporting linkAnalystUkrainian drone carrying explosives crashes in Lithuania → Lithuanian president convenes security meeting after drone incident
The crash Event links to the Story about the Lithuanian president’s security meeting.
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.