EUROPE / FOREIGN DRONE EVENTS

Alert / other · Lithuania

Suspected drone alert disrupts Vilnius airport and rail in Lithuania

Unresolved-origin alert

On 20 May 2026 an air-danger warning linked to a suspected drone (UAV) was issued for Vilnius, Lithuania, and its surrounding airspace. The warning, which included a call to shelter, triggered protective closures in the capital. The airport, rail services, the parliament and schools were reportedly disrupted, and authorities imposed temporary traffic restrictions.

How many suspected drones were involved, and of what model, was not specified, and the route is unknown. Who operated the drone, and from which country it came, has not been established; no final attribution has been made.

No confirmed impact was reported.

Show on the interactive map →

Image from the Reuters via AOL report: Baltic and Finnish drone chronology, 15 September 2026
Image · Reuters via AOL · Open report ↗

Attribution and uncertainty

Origin / operator / attribution
Nationality/operator unresolved
Investigation / uncertainty
No confirmed impact or final attribution in collected record.

Sources · 2

  1. Reuters ↗Baltic and Finnish drone chronology, updated 15 September 2026
  2. Reuters via AOL ↗Baltic and Finnish drone chronology, 15 September 2026

Full record

Alert / other

Map positions are approximate anchors for the named place, not verified incident coordinates.

Reported date
2026-05-20
Date basis
20 May; EEST
Location / jurisdiction
Vilnius and surrounding airspace; EU territory
Event categories
Drone detection; shelter warning; airport/rail/institution disruption
What was reported
Air-danger warning triggered protective closures.
Aircraft / vessel / quantity
Suspected UAV; count/model unspecified
Origin / operator / attribution
Nationality/operator unresolved
Damage / casualties / disruption
Airport, rail, parliament and schools reportedly disrupted
Response / outcome
Warnings and temporary traffic restrictions.
Investigation / uncertainty
No confirmed impact or final attribution in collected record.
Route / entry mechanism
Route unresolved
Explosive payload
Not reported
Counting / links
One incident record; no duplicate stages added.
Research provenance
Prior research; not independently rechecked in full for this export

Record E023. Record fields keep the register’s original wording.