Significance
11 measured / 11 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 11 events
Connected Situation / Through 2026-10-20
Lithuania Drone Incident and Security Response
- stories
- 12
- events
- 11
- entities
- 57
- connections
- 12
Evidence so far on 2026-10-20 UTC · updated 2026-10-20 06:25 UTC · analysis as of 2026-10-20 01: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; “Ukrainian drone carrying explosives crashes in Lithuania” labels it Ukrainian, while “Exploded drone may have damaged a civilian car, latest report says” leaves damage uncertain. Lithuania asked Poland to jointly investigate the crash, and the NATO air policing mission scrambled fighters over Lithuania. Latvian National Armed Forces deployed units as NATO jets scrambled, while “Lithuania keeps air-attack alert in Panevėžys, lifts warnings elsewhere” describes the alert remaining in Panevėžys and warnings being lifted elsewhere. On 19 October, Deividas Matulionis said the drone crossed Poland’s border, Lithuanian Defence Minister Robertas Kaunas explained why it was not shot down, and the Lithuanian Armed Forces bolstered protection of critical infrastructure. Władysław Kosiniak-Kamysz contacted Lithuania’s defence minister, and Poland’s Defence Ministry rejected a report about a drone launch site. “Lithuanian president convenes security meeting after drone incident” names Gitanas Nausėda as president; a separate report, “Lithuania seeks NATO talks on expanded authority to shoot down airspace intruders,” describes Lithuania seeking consultations, not an adopted change.
Footnotes[7][5][8][15][13][4][12][11][14][9][10][1]Assessment
The coded crash title calls the drone Ukrainian, while Matulionis’s statement gives a route across Poland’s border; those claims do not independently establish the drone’s origin or route. Poland’s Defence Ministry rejection concerns a report about a launch site and does not resolve responsibility. The car damage remains qualified as possible, and the reported NATO consultations concern broader authority rather than an implemented policy change. The described air-policing, alert, investigative and infrastructure measures establish a security response, but not who caused the crash.
Footnotes[7][12][10][5][2][15][4][14]Explanation originally captured 2026-10-20 · Evidence through 2026-10-20 UTC · Source edition sed_8700f4e43228cbe61ee1d2f8a65897ef
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 11 coded Events carried across 12 member Stories.
- Coded activity
The coded activity is led by 01 · Make Public Statement (3) and OTHER (3).
- Prominent subjects
Deividas Matulionis and Lithuanian Armed Forces are prominent in the retained actor and relationship evidence.
- Entity coverage
57 canonical Entities are linked to this edition.
Metric coverage. 11 coded Events · 6 CAMEO+ · 5 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude2.5
min 2max 3
Systemic importance0.11
min 0.1max 0.13
Propagation potential0.27
min 0.24max 0.28
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
11 coded events — 6 CAMEO+ (5 political) · 5 conflict
- Significance · 110.21min 0.13max 0.32
- Magnitude · 62.5min 2max 3
- Systemic · 60.11min 0.1max 0.13
- Propagation · 60.27min 0.24max 0.28
- Market · 60.05min 0.05max 0.05
- Goldstein · 10-1.9min -9.5max 3
- Fatalities · 50min 0max 0
- Confidence · 110.75min 0.68max 0.79
Quad class over those 10 events · Verbal Cooperation 5 · Verbal Conflict 3 · Material Conflict 2. 1 sit outside POLITICAL, where Goldstein and quad class are undefined. The four CAMEO+ scores are over the 6 CAMEO+ events only; the 5 conflict events have no such column.
Magnitude
6 measured / 6 eligible · 0 missing · 5 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across the 6 of 11 events coded in the CAMEO+ family; the conflict family has no such column
Systemic
6 measured / 6 eligible · 0 missing · 5 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 6 of 11 events coded in the CAMEO+ family; the conflict family has no such column
Propagation
6 measured / 6 eligible · 0 missing · 5 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 6 of 11 events coded in the CAMEO+ family; the conflict family has no such column
Market
6 measured / 6 eligible · 0 missing · 5 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 6 of 11 events coded in the CAMEO+ family; the conflict family has no such column
Goldstein
10 measured / 10 eligible · 0 missing · 1 not applicable
score (-10 to 10) · Event-level distribution, not a Situation risk score.
across the 10 of 11 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 · 6 not applicable
reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.
across the 5 of 11 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event
Confidence
11 measured / 11 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 11 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-20from the recordslatest
Poland and Lithuania clash over a Ukrainian drone incident
3 Stories and 0 coded Events (-3 / -5 against the day before). Widest coverage: Poland and Lithuania clash over a Ukrainian drone incident (9 articles).
- 3-3
- Stories · vs day before
- 0-5
- Events · vs day before
- 11
- articles
The lay of the land
Situation timeline
Threads
All 3 daysarticlesstoriesevents
10-1810-1910-20
Loading Situation timeline…
What kind of event · 7 coded types
over 11 coded events on this edition
- Political5
- 01 · Make Public Statement3
- 0213 · Judicial1
- 04 · Consult1
- Conflict4
- OTHER3
- DISRUPTED WEAPONS USE1
- Conflict1
- AIR/DRONE STRIKE1
- Infrastructure1
- IN02 · Transport Disruption1
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
AnalystDrone incident, alerts and official measures
The crash, air-attack alert, request for Polish investigative cooperation and security-meeting coverage describe the incident and its immediate official dimensions.
- development
AnalystPolicy consultation and alert preparations
The NATO consultation report and siren-preparation report extend the coverage to policy discussions and public-alert preparations connected to the drone incident.
Key actors
- DM
- LA
Key Events
contextAnalystUkrainian drone carrying explosives crashes in Lithuania
On 18 October 2026, a drone carrying explosives crashed in Lithuania; the event title identifies it as Ukrainian.
On 18 October 2026, a drone carrying explosives crashed in Lithuania; the event title identifies it as Ukrainian.
Footnotes[7]
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
is linked to the report about possible car damage from the exploded drone · reporting linkAnalystLithuania asks Poland to jointly investigate drone crash → Exploded drone may have damaged a civilian car, latest report says
The Event is linked to this Story.
is linked to the air-attack alert report · reporting linkAnalystNATO air policing mission scrambles fighters over Lithuania → Lithuania keeps air-attack alert in Panevėžys, lifts warnings elsewhere
The NATO scramble Event is linked to this alert Story.
acted as the source of the public statement about the Poland border · recorded participationAnalystDeividas Matulionis → Deividas Matulionis says drone crossed Poland’s border
The Event identifies Deividas Matulionis as its source actor.
is mentioned in the security-meeting Story · reporting linkAnalystGitanas Nausėda → Lithuanian president convenes security meeting after drone incident
Gitanas Nausėda is identified as president and is mentioned in the Story; the Entity has no supporting actor Event.
How a Situation is put together12 Stories · 11 Events · 12 membership connections · 127 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 57 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.