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 · 30 Oct 2026 · Dossier updated 30 Oct 2026

You are viewing revision 4 as published on 30 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
  • Latvian Civil Aviation Agency · “netika veikts atļaujas ietvaros” caa.gov.lv
  • Riga Airport spokesperson, interviewed by Latvian Radio · “kopumā ietekmēja trīs reisus.” LSM
  • Latvian Radio reporting on the armed forces search contribution · “aptuveni 25 tūkstošus eiro” LSM

Claims and evidence

5 sources · 5 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 on 2 May.

[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.

Context

The CAA said the 2 May flight was outside the restored Penguin C permit, involved a different model and remained subject to administrative proceedings.

[4]
Source passage
“netika veikts atļaujas ietvaros”

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

Latvian Civil Aviation AgencySupports the report

Permit restoration is not an exoneration or court judgment.

Context

In a later Latvian Radio interview, the airport said the 2–5 May restrictions affected three flights; lost revenue was undisclosed.

[5]
Source passage
“kopumā ietekmēja trīs reisus.”

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

Riga Airport spokesperson, interviewed by Latvian Radio via Latvian RadioSupports the report

Three affected flights is not three diversions or an additional count.

Context

Latvian Radio reported about EUR 25,000 for the military search contribution, not the overall incident cost or compensation paid.

[5]
Source passage
“aptuveni 25 tūkstošus eiro”

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

Latvian Radio reporting on the armed forces search contributionSupports the report

A reported component cost; not a total damages bill.

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. Latvian Civil Aviation Agency
    • Latvian CAA: permit and administrative-investigation follow-up [4] · Direct account
  4. Riga Airport spokesperson, interviewed by Latvian Radio
    • Latvian Radio: airport interview and military search-cost reporting [5] · Relayed statement
  5. Latvian Radio reporting on the armed forces search contribution
    • Latvian Radio: airport interview and military search-cost reporting [5] · Direct account
  6. 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 on 2 May.[2]Support remains visible
The CAA said the 2 May flight was outside the restored Penguin C permit, involved a different model and remained subject to administrative proceedings.[4]Support remains visible
In a later Latvian Radio interview, the airport said the 2–5 May restrictions affected three flights; lost revenue was undisclosed.[5]Support remains visible
Latvian Radio reported about EUR 25,000 for the military search contribution, not the overall incident cost or compensation paid.[5]Support remains visible

What we know

The airport initially reported a diversion. In a 29 May Latvian Radio interview it said restrictions during 2–5 May affected three flights; these are not three diversions or additional flights to add to the earlier report. Its calculated lost revenue was undisclosed; an intended claim against the manufacturer is not an award or payment. Latvian Radio put the armed forces’ search contribution at about EUR 25,000, not the total incident bill. No injury or physical airport damage established.

The original LSM/LETA report carries separate airport and manufacturer accounts; the CAA later examined the recovered aircraft and its data. The CAA audit notice is a regulatory finding. Latvian Radio’s later reporting adds its own airport interview and search-cost account. Repeated CAA statements are one chain, while the airport and defence sources are distinct contributions.

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 a 2 May landing. Do not describe a multi-day continuous flight. The aircraft was found 15 May and the notice published 17 May. 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. The lost experimental aircraft was not the Penguin C model covered by the permit restored on 25 May. The CAA said the flight lay outside that permit and that an administrative case remained ongoing. Restoration did not decide liability; no later fine, judgment or payment is established here.

UAVFactory was identified as the aircraft’s manufacturer and owner. That identifies the organisation associated with the test, not a named pilot or a final liability finding. No hostile intent or state sponsorship established.

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: found 15 May, recorded landing 2 May. Search duration is not flight duration. [2]

  4. CAA restores the Penguin C permit but says the lost aircraft was a different model and outside that permit; administrative proceedings continue. [4]

  5. The airport reports three flights affected during 2–5 May; Latvian Radio reports approximate military search costs, not a total damages award. [5]

Original sources (5)

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 airport4Latvian CAA: permit and administrative-investigation follow-up25 May 2020 · source family: Latvia caa5Latvian Radio: airport interview and military search-cost reporting29 May 2020 · source family: Latvian public media

Editorial changes

  1. Revision 4 · 30 Oct 2026Added the later CAA permit-scope finding and separate airport/search-cost follow-up; distinguished permit restoration, unresolved liability and component costs.
  2. Revision 3 · 21 Oct 2026Typography: added missing spaces in dates and times (live-site audit 21 Oct 2026); no change of content.
  3. Revision 2 · 16 Oct 2026Added a sourced general counter-drone measure at this location.
  4. Revision 1 · 16 Oct 2026Curated dossier created after checking the cited sources line by line.

Cite this dossier

Permanent page · Revision 4

Chicago

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

APA

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

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
4
Release
20261102T055221362217-c8d330
Publication date
30 Oct 2026
Accessed
09 Nov 2026
Permanent URL
https://droneincidents.com/incident/riga-airport-runaway-drone-2020-05-02/v4/
Hashed file
JSON · SHA-256 4e2df7f1c77e4a17a9e78f088d5ba10083a62f62233b5edecfc9e5a1edbb3ea6

Dataset DOI for this exact version: 10.5281/zenodo.23877662 · 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 4; release 20261102T055221362217-c8d330; published 30 Oct 2026. https://droneincidents.com/incident/riga-airport-runaway-drone-2020-05-02/v4/ Accessed 09 Nov 2026. SHA-256 4e2df7f1c77e4a17a9e78f088d5ba10083a62f62233b5edecfc9e5a1edbb3ea6 (https://droneincidents.com/data/citations/incident/riga-airport-runaway-drone-2020-05-02/r4/4e2df7f1c77e4a17a9e78f088d5ba10083a62f62233b5edecfc9e5a1edbb3ea6/data.json). Exact archived dataset version: https://doi.org/10.5281/zenodo.23877662.

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