DroneLedger

Airport disruption

Changi runway operations disrupted after reported drones on 18–19 June 2019

Singapore · 18 Jun 2019 · event date · approximate location

Reported unauthorised drones disrupted operations on one runway at Singapore Changi Airport during the night of 18–19 June 2019. The airport continued operating; this was not a complete airport closure. [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

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

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

You are viewing revision 2 as published on 29 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?

Reported unauthorised drones disrupted operations on one runway at Singapore Changi Airport during the night of 18–19 June 2019. The airport continued operating; this was not a complete airport closure.

Facts at a glance
Drone type
  • No named drone type is recorded in this dossier.
Effects
  • According to CNA, citing TODAY operational reporting, Intermittent suspension of one runway was described
Who reported what
  • mot.gov.sg: Assessment of drone involvement
  • CNA: Assessment of drone involvement; reported outcome
Source families
  • 2 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.
  • Where did it happen? The record has no location more precise than a country or region.
Check the evidence
Source passage
  • Singapore Ministry of Transport · “The recent drone intrusions are the first confirmed intrusions into Changi Airport” mot.gov.sg
  • CNA / TODAY operational reporting · “two runways had been suspended for short periods.” CNA
  • Singapore Acting Minister for Transport, parliamentary written reply · “There was no evidence to suggest that these drone incursions were national security threats.” mot.gov.sg
  • Singapore Defence Minister, interviewed by TODAY · “neutralise these drones” CNA

Claims and evidence

3 sources · 4 original statements

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

ClaimOriginal sourceAssessment
Drone

The transport ministry described the June events as confirmed intrusions.

[1]
Source passage
“The recent drone intrusions are the first confirmed intrusions into Changi Airport”

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

Singapore Ministry of Transport via Singapore Ministry of TransportSupports the report

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

Impact

CNA describes intermittent suspension of one runway.

[2]
Source passage
“two runways had been suspended for short periods.”

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

CNA / TODAY operational reporting via CNA / TODAYSupports the report

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

Context

Later official assessment: no evidence suggesting the two 2019 Changi incursions were national-security threats.

[3]
Source passage
“There was no evidence to suggest that these drone incursions were national security threats.”

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

Singapore Acting Minister for Transport, parliamentary written replySupports the report

Retrospective official assessment, not a court finding.

Context

In a June 2019 interview the defence minister said SAF assets were trying to neutralise drones. The same interview describes military deployment as an initial response, not the long-term or most economical solution.

[2]
Source passage
“neutralise these drones”

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

Singapore Defence Minister, interviewed by TODAY via CNA / TODAYSupports the report

Original minister interview reported by TODAY and republished on CNA. Separate original statement from the later transport-ministry assessment; shared government setting is explicit. No capability specifications or tactics reproduced.

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. Singapore Ministry of Transport
    • Singapore Ministry of Transport: parliamentary reply [1] · Relayed statement
  2. CNA / TODAY operational reporting
    • CNA / TODAY: defence-minister interview and airport disruption [2] · Relayed statement
  3. Singapore Acting Minister for Transport, parliamentary written reply
    • Singapore Ministry of Transport: retrospective parliamentary reply on security assessment [3] · Direct account
  4. Singapore Defence Minister, interviewed by TODAY
    • CNA / TODAY: defence-minister interview and airport disruption [2] · Relayed statement
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
The transport ministry described the June events as confirmed intrusions.[1]Support remains visible
CNA describes intermittent suspension of one runway.[2]Support remains visible
Later official assessment: no evidence suggesting the two 2019 Changi incursions were national-security threats.[3]Support remains visible
In a June 2019 interview the defence minister said SAF assets were trying to neutralise drones. The same interview describes military deployment as an initial response, not the long-term or most economical solution.[2]Support remains visible

What we know

CNA reports 37 delayed flights and one diversion for 18–19 June, with one runway suspended for short periods. The ministry later gives 55 delays and eight diversions across two separate June nights; those combined figures are not totals for this event.

The transport ministry’s parliamentary reply and CNA’s defence-minister interview are separate original statements. Operational numbers partly share the same government and airport accounts; this is not independent technical identification. Drone presence remains attributed official reporting. On 14 October 2025, the transport ministry reported no evidence suggesting the two 2019 Changi incursions were national-security threats. This later official assessment and the earlier defence-minister interview are separate statements; shared government origins remain explicit.

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

What remains unknown

The start date represents the local night beginning 18 June, extending into 19 June, not the July reply date. The separate 24 June disruption must not be combined as one incident. Operator identity, device type and precise number are not established. Later references to prosecutions in other drone cases do not establish an arrest or conviction for this incident. The retrospective reply identifies no operator or case-specific prosecution; absence of evidence of a security threat does not establish harmless intent.

No operator or responsible organisation established by the reviewed sources.

How the story changed

  1. Reported unauthorised drones disrupted operations on one runway at Singapore Changi Airport during the night of 18–19 June 2019. The airport continued operating; this was not a complete airport closure. [1]

  2. 2025 ministry assessment: no evidence suggesting a national-security threat in the two 2019 incursions. [3]

Original sources (3)

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

1Singapore Ministry of Transport: parliamentary reply08 Jul 2019 · source family: Singapore mot2CNA / TODAY: defence-minister interview and airport disruption30 Jun 2019 · source family: Mediacorp3Singapore Ministry of Transport: retrospective parliamentary reply on security assessment14 Oct 2025 · source family: Singapore mot

Editorial changes

  1. Revision 2 · 29 Oct 2026Added the 14 October 2025 retrospective ministry security assessment, distinguishing it from the initial 2019 response and unresolved operator or prosecution outcomes.
  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. “Changi runway operations disrupted after reported drones on 18–19 June 2019.” Dossier changi-airport-drone-disruption-2019-06-18, revision 2, updated 29 Oct 2026. https://droneincidents.com/incident/changi-airport-drone-disruption-2019-06-18/v2/

APA

DroneLedger editorial team. (29 Oct 2026). Changi runway operations disrupted after reported drones on 18–19 June 2019 (Dossier changi-airport-drone-disruption-2019-06-18, revision 2). https://droneincidents.com/incident/changi-airport-drone-disruption-2019-06-18/v2/

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

Cite this version

Maker
DroneLedger editorial team
ID
changi-airport-drone-disruption-2019-06-18
Revision or edition
2
Release
20261102T055221362217-c8d330
Publication date
29 Oct 2026
Accessed
09 Nov 2026
Permanent URL
https://droneincidents.com/incident/changi-airport-drone-disruption-2019-06-18/v2/
Hashed file
JSON · SHA-256 de650e571541860210631a6b0cc4308f90f614f2411fb76aef331ed2b2caf645

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. Changi runway operations disrupted after reported drones on 18–19 June 2019. ID changi-airport-drone-disruption-2019-06-18; revision or edition 2; release 20261102T055221362217-c8d330; published 29 Oct 2026. https://droneincidents.com/incident/changi-airport-drone-disruption-2019-06-18/v2/ Accessed 09 Nov 2026. SHA-256 de650e571541860210631a6b0cc4308f90f614f2411fb76aef331ed2b2caf645 (https://droneincidents.com/data/citations/incident/changi-airport-drone-disruption-2019-06-18/r2/de650e571541860210631a6b0cc4308f90f614f2411fb76aef331ed2b2caf645/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