DroneLedger

Airport disruption

Drone-like object report disrupts Delhi airport operations

New Delhi · 20 Aug 2017 · event date · approximate location

A pilot reported an unidentified drone-like object near Delhi’s Indira Gandhi International Airport on 20 August 2017. Contemporary police, airline and air-traffic accounts describe precautionary flight restrictions and diversions; a later government answer disputes an airport-wide shutdown. [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 · 17 Oct 2026 · Dossier updated 17 Oct 2026

You are viewing revision 2 as published on 17 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 pilot reported an unidentified drone-like object near Delhi’s Indira Gandhi International Airport on 20 August 2017. Contemporary police, airline and air-traffic accounts describe precautionary flight restrictions and diversions; a later government answer disputes an airport-wide shutdown.

Facts at a glance
Drone type
  • No named drone type is recorded in this dossier.
Effects
  • According to The Indian Express, citing Delhi Police via Indian Express, Contemporary police account describes precautionary restrictions
  • According to The Times of India, citing Air India via Times of India, Air India separately reported diverted services
Who reported what
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
  • AirAsia via Indian Express · “spotted unidentified object flying close to aircraft” The Indian Express
  • Delhi Police via Indian Express · “operations at all the three runways were closed as a precautionary measure” The Indian Express
  • Air India via Times of India · “Two of our flights to Delhi, including one on a wide body, had to be diverted.” The Times of India

Claims and evidence

3 sources · 3 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

AirAsia described an unidentified object rather than establishing drone identity.

[1]
Source passage
“spotted unidentified object flying close to aircraft”

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

AirAsia via Indian Express via Indian ExpressSupports the report

Short literal passage read on public source page; original evidence origins are distinguished in evidence.

Impact

Contemporary police account describes precautionary restrictions.

[1]
Source passage
“operations at all the three runways were closed as a precautionary measure”

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

Delhi Police via Indian Express via Indian ExpressSupports the report

Short literal passage read on public source page; original evidence origins are distinguished in evidence.

Impact

Air India separately reported diverted services.

[2]
Source passage
“Two of our flights to Delhi, including one on a wide body, had to be diverted.”

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

Air India via Times of India via Times of India / TNNSupports the report

Short literal passage read on public source page; original evidence origins are distinguished in evidence.

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. AirAsia via Indian Express
    • Indian Express: Delhi Police and AirAsia statements [1] · Relayed statement
  2. Delhi Police via Indian Express
    • Indian Express: Delhi Police and AirAsia statements [1] · Relayed statement
  3. Air India via Times of India
    • Times of India / TNN: air traffic and Air India accounts [2] · Relayed statement
  4. Unknown dependency
    • Rajya Sabha: civil aviation written answer338, printed page154 [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
AirAsia described an unidentified object rather than establishing drone identity.[1]Support remains visible
Contemporary police account describes precautionary restrictions.[1]Support remains visible
Air India separately reported diverted services.[2]Support remains visible

What we know

Contemporary reports describe disrupted flights and diversions. A later parliamentary answer says only one runway was suspended while others continued operating. The exact extent and duration of the restrictions remain disputed.

Indian Express relays Delhi Police and AirAsia statements. The Times of India’s separate TNN report interviews an air-traffic official and Air India about disruption. AirAsia’s unidentified-object statement is shared, not independent drone identification. A later official parliamentary answer provides a conflicting account of the restriction’s extent.

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

What remains unknown

No technical drone identification or operator established. Reports variously give about 40 minutes and 46 minutes and refer to an earlier separate scare that day. No exact closure duration, airport-wide shutdown or observation clock adopted. The parliamentary answer dated19December2017 concerns20August but contradicts contemporary all-runway accounts.

No operator established in the selected reporting.

How the story changed

  1. Unidentified-object report leads to precautionary restrictions and diversions; exact extent disputed. [1]

  2. Parliamentary answer disputes an airport-wide shutdown and describes a single-runway suspension. [3]

Original sources (3)

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

1Indian Express: Delhi Police and AirAsia statements20 Aug 2017 · source family: Indian Express2Times of India / TNN: air traffic and Air India accounts21 Aug 2017 · source family: Times of india3Rajya Sabha: civil aviation written answer338, printed page15419 Dec 2017 · source family: India parliament

Editorial changes

  1. Revision 2 · 17 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. “Drone-like object report disrupts Delhi airport operations.” Dossier delhi-airport-drone-like-object-2017-08-20, revision 2, updated 17 Oct 2026. https://droneincidents.com/incident/delhi-airport-drone-like-object-2017-08-20/v2/

APA

DroneLedger editorial team. (17 Oct 2026). Drone-like object report disrupts Delhi airport operations (Dossier delhi-airport-drone-like-object-2017-08-20, revision 2). https://droneincidents.com/incident/delhi-airport-drone-like-object-2017-08-20/v2/

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

Cite this version

Maker
DroneLedger editorial team
ID
delhi-airport-drone-like-object-2017-08-20
Revision or edition
2
Release
20261109T002636372024-fb099f
Publication date
17 Oct 2026
Accessed
09 Nov 2026
Permanent URL
https://droneincidents.com/incident/delhi-airport-drone-like-object-2017-08-20/v2/
Hashed file
JSON · SHA-256 6a7d37f2cdc6cc74c6d0a7ca3422538a9ee207fc2d15ea50fa664c9ca7e32e7c

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. Drone-like object report disrupts Delhi airport operations. ID delhi-airport-drone-like-object-2017-08-20; revision or edition 2; release 20261109T002636372024-fb099f; published 17 Oct 2026. https://droneincidents.com/incident/delhi-airport-drone-like-object-2017-08-20/v2/ Accessed 09 Nov 2026. SHA-256 6a7d37f2cdc6cc74c6d0a7ca3422538a9ee207fc2d15ea50fa664c9ca7e32e7c (https://droneincidents.com/data/citations/incident/delhi-airport-drone-like-object-2017-08-20/r2/6a7d37f2cdc6cc74c6d0a7ca3422538a9ee207fc2d15ea50fa664c9ca7e32e7c/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