JG Border/line Support the author ↗

Lithuania / 2026-10-18-lt-1

airspace incident: Juodžionys, Pasvalys district; temporary closure of Kaunas Airport (2026-10-18)

/ date of the event

What happened

On the morning of 18 October 2026, a drone crashed and exploded near Juodžionys in Pasvalys district. According to NKVC, debris damaged a passing car and its driver was unhurt. Scrambled NATO aircraft did not shoot the drone down: clouds prevented visual identification. Kaunas Airport was temporarily closed; precise times and affected flight counts are not verified. That evening, Defence Minister Robertas Kaunas preliminarily identified a Ukrainian drone connected with an attack on Saint Petersburg, saying Russian electronic warfare had caused it to deviate. Computer components were still being sought. This is the minister’s preliminary assessment, not a final technical report or proof of a deliberate attack on Lithuania. The minister distinguished the case from the attempted Starlink arson in Vilnius. Identity with the object sought near Lublin and an incursion into Latvia are not established. Exact coordinates are undetermined; the entry has no map point. On 19 October, Lithuania’s prime minister said debris and information from Ukraine confirmed the drone’s Ukrainian origin and that it carried explosives. According to Lithuania’s chronology, it was tracked in Poland from 05:47 and crossed the Lithuanian border at 06:02. This is Lithuania’s position, not a final jointly established flight path. On 20 October, Nausėda announced a joint Polish-Lithuanian defence-ministry group; final conclusions had not been presented. DORSZ continued analysing data and requested explanations from Ukraine without a final confirmation of entry into Poland. Poland’s defence ministry denied an unofficial account of a launch from Lithuania; that denial alone does not confirm the entire route. No Polish incident or route has been added. Operator identification remains a grade C assessment, the detailed FPV-1/FP-1 model is unresolved, and Russian jamming is not a published final forensic finding.

Responsibility and limits of the evidence

suspected

Someone has named a perpetrator, but this is neither a court finding nor a formal attribution by a state.

Named party: Ukraine, according to the Lithuanian minister’s preliminary identification

C - official suspicion

Minister obrony Litwy Robertas Kaunas, wypowiedź w LRT / 2026-10-18 / carrying out the act

The minister preliminarily identifies a Ukrainian drone linked to an attack on Saint Petersburg and attributes its deviation to Russian jamming. Examination continues; this does not establish a deliberate attack on Lithuania.

Premier Litwy Mindaugas Sinkevičius, cytowany przez Delfi/ELTA / 2026-10-19 / origin of the equipment

The prime minister identifies Ukrainian origin from debris and information from Ukraine, and an explosive payload. This is not a final joint examination establishing operator or the full route.

Impact

killed
not established
injured
0
damage
property damage

According to NKVC, the driver of the damaged car was unhurt; LRT reports no injuries. A separate final death toll is undetermined.

airport closed: Kaunas Airport

Source discrepancy

LRT literally quotes the preliminary designation “FPV-1”. It was not corrected to “FP-1” or adopted as a completed technical identification; the detailed model is omitted pending clarification.

Lithuania’s chronology describes flight from Poland at 05:47 and crossing Lithuania’s border at 06:02. DORSZ is still analysing data; the joint group has not presented final conclusions. A confirmed route or second incident in Poland is not established.

What happened next

On 19 October, Lithuania’s prime minister said debris and information from Ukraine confirmed the drone’s Ukrainian origin and that it carried explosives. According to Lithuania’s chronology, it was tracked in Poland from 05:47 and crossed the Lithuanian border at 06:02. This is Lithuania’s position, not a final jointly established flight path. On 20 October, Nausėda announced a joint Polish-Lithuanian defence-ministry group; final conclusions had not been presented. DORSZ continued analysing data and requested explanations from Ukraine without a final confirmation of entry into Poland. Poland’s defence ministry denied an unofficial account of a launch from Lithuania; that denial alone does not confirm the entire route. No Polish incident or route has been added. Operator identification remains a grade C assessment, the detailed FPV-1/FP-1 model is unresolved, and Russian jamming is not a published final forensic finding.

Sources

  1. Robertas Kaunas: nukritęs dronas - Ukrainos atakos prieš Sankt Peterburgą pasekmė

    LRT / BNS / 2026-10-18 / secondary source

    supports: the record, that it happened, the attribution

  2. Ukraina atsiprašo dėl drono Lietuvoje: jį galėjo nukreipti Rusija

    LRT / 2026-10-18 / secondary source

    supports: the record, that it happened, the date, the location, the impact

  3. Po drono incidento vyks NSK posėdis, Nausėda susitiks su žvalgybos, kariuomenės atstovais

    LRT / 2026-10-19 / secondary source

    supports: the record, that it happened, the date, the location, the impact

  4. UPDATE: Drone debris found in Lithuania after airspace breach

    Polskie Radio / PAP / Reuters / 2026-10-18 / secondary source

    supports: the record, that it happened, the date, the location, the disruption

  5. Premjeras: nėra abejonių, kad dronas įskrido iš Lenkijos, jis nešė sprogmenis

    Delfi / ELTA / 2026-10-19 / secondary source

    supports: the record, that it happened, the location, the impact, the attribution

  6. Nausėda: dėl nukritusio drono Lietuvos ir Lenkijos ministerijos sudarė bendrą darbo grupę

    LRT / BNS / 2026-10-20 / secondary source

    supports: the record, the attribution

  7. Nie wykluczamy żadnej hipotezy. Poszukiwania obiektu latającego na razie zakończone

    Radio Lublin / 2026-10-20 / secondary source

    supports: the record, the attribution