Significance
3 measured / 3 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 3 events
Connected Situation / Through 2026-09-15
NATO Drone Incident and Lithuanian-Polish Investigation
- stories
- 15
- events
- 3
- entities
- 41
- connections
- 15
Frozen through 2026-09-15 UTC · published 2026-09-16 01:29 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
As of 2026-09-15, the retained evidence describes a suspected drone incident near Vilnius, a subsequent NATO shootdown over Lithuania, and a Lithuania-Poland investigation. The drone’s precise location and attribution remain unsettled in the retained reporting.
Footnotes[11][9][2][8][1]Assessment
The structurally important sequence is the coded September 13 scramble, the coded September 14 shootdown, and the September 15 reported investigation. The evidence establishes NATO participation in the scramble and shootdown, but it does not establish who launched the unidentified drone.
Footnotes[11][9][2][12]Explanation originally captured 2026-09-15 · Evidence through 2026-09-15 UTC · Source edition sed_9454f80a60b00b0bd3c252a4b01f5fd9
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 3 coded Events carried across 15 member Stories.
- Coded activity
The coded activity is led by 01 · Make Public Statement (1) and AIR/DRONE STRIKE (1).
- Prominent subjects
NATO and Lithuanian Armed Forces are prominent in the retained actor and relationship evidence.
- Entity coverage
41 canonical Entities are linked to this edition.
Metric coverage. 3 coded Events · 1 CAMEO+ · 2 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude3
min 3max 3
Systemic importance0.13
min 0.13max 0.13
Propagation potential0.28
min 0.28max 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
3 coded events — 1 CAMEO+ (1 political) · 2 conflict
- Significance · 30.2min 0.13max 0.3
- Magnitude · 13min 3max 3
- Systemic · 10.13min 0.13max 0.13
- Propagation · 10.28min 0.28max 0.28
- Market · 10.05min 0.05max 0.05
- Goldstein · 3-3.8min -9.5max 0
- Fatalities · 20min 0max 0
- Confidence · 30.72min 0.46max 0.86
Quad class over those 3 events · Material Conflict 1 · Verbal Conflict 1 · Verbal Cooperation 1. The four CAMEO+ scores are over the 1 CAMEO+ events only; the 2 conflict events have no such column.
Magnitude
1 measured / 1 eligible · 0 missing · 2 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across the 1 of 3 events coded in the CAMEO+ family; the conflict family has no such column
Systemic
1 measured / 1 eligible · 0 missing · 2 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 1 of 3 events coded in the CAMEO+ family; the conflict family has no such column
Propagation
1 measured / 1 eligible · 0 missing · 2 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 1 of 3 events coded in the CAMEO+ family; the conflict family has no such column
Market
1 measured / 1 eligible · 0 missing · 2 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 1 of 3 events coded in the CAMEO+ family; the conflict family has no such column
Goldstein
3 measured / 3 eligible · 0 missing · 0 not applicable
score (-10 to 10) · Event-level distribution, not a Situation risk score.
across the 3 of 3 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics
Fatalities
2 measured / 2 eligible · 0 missing · 1 not applicable
reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.
across the 2 of 3 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event
Confidence
3 measured / 3 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 3 events
This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.
The lay of the land
Situation timeline
Threads
All 3 daysarticlesstoriesevents
09-1309-1409-15
Loading Situation timeline…
What kind of event · 3 coded types
over 3 coded events on this edition
- Conflict1
- AIR/DRONE STRIKE1
- Conflict1
- OTHER1
- Political1
- 01 · Make Public Statement1
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 detection, NATO response and shootdown
This thread contains the coded scramble, the coded shootdown, and the reporting that links the earlier suspected incursion to the later action.
- precursor
AnalystEarlier suspected incursion and air alert
The retained connections explicitly identify the suspected drone incursion and fighter scramble as antecedent material to the later shootdown.
- development
Key actors
- N
AnalystNATO
NATO is the only canonical Entity with recorded participation as an Event actor: the coded records identify it as the actor in the scramble and the shootdown.
Key Events
contextAnalystNATO scrambles fighter after suspected drone near Vilnius airport
On the coded occurrence date 2026-09-13, NATO scrambled a fighter after a suspected drone near Vilnius International Airport.
On the coded occurrence date 2026-09-13, NATO scrambled a fighter after a suspected drone near Vilnius International Airport.
Footnotes[11]contextAnalystNKVC chief regrets delay identifying air-alert object
On the coded occurrence date 2026-09-13, the NKVC chief publicly regretted a delay in identifying the air-alert object.
On the coded occurrence date 2026-09-13, the NKVC chief publicly regretted a delay in identifying the air-alert object.
Footnotes[10]
turning pointAnalystNATO fighter jet shoots down drone over Lithuania
On the coded occurrence date 2026-09-14, NATO shot down an unidentified drone over Lithuania; the coded record reports no fatalities.
On the coded occurrence date 2026-09-14, NATO shot down an unidentified drone over Lithuania; the coded record reports no fatalities.
Footnotes[9]
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
NATO is recorded as the source actor in the fighter scramble after the suspected drone · recorded participationAnalystNATO → NATO scrambles fighter after suspected drone near Vilnius airport
The Event record binds NATO to the scramble as source actor.
NATO is recorded as the source actor in the shootdown of the unidentified drone · recorded participationAnalystNATO → NATO fighter jet shoots down drone over Lithuania
The Event record binds NATO to the shootdown as source actor and identifies the target as an unidentified drone.
The suspected incursion is retained as antecedent reporting to the shootdown · reporting linkAnalystLithuanian official Vaikšnoras explains suspected drone incursion → NATO fighter jet shoots down drone over Lithuania
The supplied connection and edge explicitly classify story:41d1e7b5c663 as antecedent or precursor to the shootdown thread.
The Lithuania-Poland investigation is retained as a continuation of the shootdown reporting · reporting linkAnalystLithuania and Poland join forces to investigate drone incidents → NATO fighter jet shoots down drone over Lithuania
The supplied continuation edge links the investigation story to the September 14 shootdown story.
The investigation story is linked to the coded NATO shootdown Event · reporting linkAnalystLithuania and Poland join forces to investigate drone incidents → NATO fighter jet shoots down drone over Lithuania
The story record links to the coded shootdown Event, and the supplied edge identifies the story as sharing that incident.
How a Situation is put together15 Stories · 3 Events · 15 membership connections · 203 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 41 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.