DroneLedger

Airport disruption

Runaway test drone prompts Riga airspace restrictions

Riga · 02 May 2020 · event date · approximate location

A test drone lost control in Latvia on 2 May 2020. Airspace restrictions affected Riga Airport on 3 May while authorities searched for it. [1][2]

Drone presence is reported. The consequences are established. The operator is not established.

Drone presenceReported[1][2]
ImpactConfirmed[1][2]
AttributionNot established

DroneLedger editorial team, publisher and editor responsible for this project.

AI-assisted editorial source review. This label records the editorial workflow, not a personal check of every source or sentence. Method and corrections

3 source families · a count of sources is not a verification score

AI-assisted editorial source review · Dossier updated 16 Oct 2026

You are viewing revision 2 as published on 16 Oct 2026. The dossier text, evidence states, claims and sources of this revision are fixed; catalogue context such as cost estimates is not shown here. View the current version

What do we know now?

A test drone lost control in Latvia on 2 May 2020. Airspace restrictions affected Riga Airport on 3 May while authorities searched for it. Later examination of the recovered drone showed that it had already landed on 2 May.

Facts at a glance
Drone type
  • No named drone type is recorded in this dossier.
Effects
  • According to LSM, citing Latvian transport minister / airport operations, Closure of Riga Airport airspace was reported
Who reported what
  • LSM: Assessment of drone involvement; reported outcome
  • caa.gov.lv: Assessment of drone involvement
Source families
  • 3 source families are recorded; republication is not independent confirmation

Further details are not known from the cited sources.

Timeline

Three clocks, one reading line

Shared calendar-day axis, from left to right. Bars mark days or reporting windows, not durations. Publication and revision clocks are not event clocks. Missing clocks remain unknown; the table gives all available precision and source links. The plot follows recorded calendar dates; time zones may differ. It establishes neither within-day order nor causality.

Three clocks, one reading line
TrackRecorded date / time
1 · Event
  • · Calendar day; time unknown
2 · Source publication
3 · Dossier revisions

What remains uncertain?

  • Was a drone established? A published investigation or identification could resolve this.
  • Who operated it, and why? An attributed investigation finding is missing.
Check the evidence
Source passage
  • Latvian transport minister / airport operations · “Slēgta arī lidostas "Rīga" gaisa telpa” LSM
  • Latvian Civil Aviation Agency · “drons nolaidās 2. maijā” caa.gov.lv

Claims and evidence

3 sources · 2 original statements

Sources that repeat the same original statement count once: a number of articles is not a number of independent confirmations.

ClaimOriginal sourceAssessment
Impact

LSM reports closure of Riga Airport airspace.

[1]
Source passage
“Slēgta arī lidostas "Rīga" gaisa telpa”

Passage checked word for word against the source on 16 Oct 2026.

Latvian transport minister / airport operations via LSMSupports the report

Short literal passage read on the public source page; reported drone presence is not technical identification.

Drone

The CAA states that the drone landed on2May.

[2]
Source passage
“drons nolaidās 2. maijā”

Passage checked word for word against the source on 16 Oct 2026.

Latvian Civil Aviation Agency via Latvian CAASupports the report

Short literal passage read on the public source page; reported drone presence is not technical identification.

Source genealogy

Grouped by recorded original statement, not by publisher. Unmapped sources have unknown dependency; linked statements may also share an earlier origin. This is not an independence score.

  1. Latvian transport minister / airport operations
    • LSM: airport and manufacturer accounts via LETA [1] · Relayed statement
  2. Latvian Civil Aviation Agency
    • Latvian CAA: recovered drone and recorded landing date [2] · Relayed statement
  3. Unknown dependency
    • Riga: general response context [3]
Show source graph

Left: publishers; right: recorded original statement. Converging lines show shared origin, not publication order. Dashed nodes have unknown dependency.

Read with a source omitted

Reading aid: switch off a source or family to inspect the remaining visible support below. Evidence status is not recalculated.

How to read this table

Reading aid only. Switch off a source or its recorded family to inspect the remaining visible support for exact claim texts. Evidence status is not recalculated. Shared wording or a shared family does not prove independence. Only recorded links labelled “supports” count here; context and contradiction links are not support. The dossier itself is unchanged.

Claim → supporting sources · recorded links
ClaimSupporting sourcesVisible support
LSM reports closure of Riga Airport airspace.[1]Support remains visible
The CAA states that the drone landed on2May.[2]Support remains visible

What we know

LSM reports an airport spokesperson confirming a diverted flight. These were precautionary aviation restrictions; they do not establish that the drone remained airborne throughout the search. No physical airport damage or injury established.

LSM relays separate airport-operator and manufacturer accounts through LETA. The CAA later examined the recovered aircraft and its data. The follow-up concerns the same drone, not a second event; overlapping CAA reporting is acknowledged.

Data
No structured detail recorded
Hit / damaged · Fell near · Intercepted (claimed) · Human consequences

What remains unknown

The initial report describes continued searches and an alleged later sighting, but the CAA says recorded data showed a2May landing. Do not describe a multi-day continuous flight. The aircraft was found15May and the notice published17May. Riga is the affected airport association, not a drone-position claim. No route, coordinates, altitude or recovery site reproduced. No hostile intent or state sponsorship established.

No operator or responsible organisation established by the reviewed sources.

How the story changed

  1. A test drone lost control in Latvia on 2 May 2020. Airspace restrictions affected Riga Airport on 3 May while authorities searched for it. Later examination of the recovered drone showed that it had already landed on 2 May. [1]

  2. Airport airspace restrictions and a diversion reported while the aircraft was still missing. [1]

  3. CAA publishes the recovery notice: found15May, recorded landing2May. Search duration is not flight duration. [2]

Original sources (3)

3 source families · a count of sources is not a verification score

1LSM: airport and manufacturer accounts via LETA03 May 2020 · source family: Latvian public media2Latvian CAA: recovered drone and recorded landing date17 May 2020 · source family: Latvia caa3Riga: general response context27 Jan 2025 · source family: Riga airport

Editorial changes

  1. Revision 2 · 16 Oct 2026Added a sourced general counter-drone measure at this location.
  2. Revision 1 · 16 Oct 2026Curated dossier created after checking the cited sources line by line.

Cite this dossier

Permanent page · Revision 2

Chicago

DroneLedger editorial team. “Runaway test drone prompts Riga airspace restrictions.” Dossier riga-airport-runaway-drone-2020-05-02, revision 2, updated 16 Oct 2026. https://droneincidents.com/incident/riga-airport-runaway-drone-2020-05-02/v2/

APA

DroneLedger editorial team. (16 Oct 2026). Runaway test drone prompts Riga airspace restrictions (Dossier riga-airport-runaway-drone-2020-05-02, revision 2). https://droneincidents.com/incident/riga-airport-runaway-drone-2020-05-02/v2/

Cite the revision you used: later revisions may change evidence states.

Cite this version

Maker
DroneLedger editorial team
ID
riga-airport-runaway-drone-2020-05-02
Revision or edition
2
Release
20261109T002636372024-fb099f
Publication date
16 Oct 2026
Accessed
09 Nov 2026
Permanent URL
https://droneincidents.com/incident/riga-airport-runaway-drone-2020-05-02/v2/
Hashed file
JSON · SHA-256 91733e2cf72cb2747635ba04baa56f6543fc12ef3da9e09001196d1aab233918

Dataset DOI for this exact version: Not yet in a DOI snapshot · DOI binding manifest

Dataset DOI (series, not this revision): 10.5281/zenodo.23345422

DroneLedger editorial team. Runaway test drone prompts Riga airspace restrictions. ID riga-airport-runaway-drone-2020-05-02; revision or edition 2; release 20261109T002636372024-fb099f; published 16 Oct 2026. https://droneincidents.com/incident/riga-airport-runaway-drone-2020-05-02/v2/ Accessed 09 Nov 2026. SHA-256 91733e2cf72cb2747635ba04baa56f6543fc12ef3da9e09001196d1aab233918 (https://droneincidents.com/data/citations/incident/riga-airport-runaway-drone-2020-05-02/r2/91733e2cf72cb2747635ba04baa56f6543fc12ef3da9e09001196d1aab233918/data.json). Not yet in a DOI snapshot.

Citation uses the English reference edition. Access date is the UTC date when this page was built; change it to your consultation date when reusing the citation.

Editorial pack (print / PDF)Follow this dossier (feed)Earlier versions