Gatwick flight cancellations after drone reports

Operational effects

• The chief constable account recorded a 30-hour airport closure.

  closed for 30 hours

  Sussex Police chief constable, in PCC meeting minutes · Source [2]

  As of: Time not established

  Historical account of the December 2018 closure, not a live count. The source does not supply exact start/end timestamps or a rolling count cutoff.

Investigation and legal follow-up

• 18 Oct 2019 The meeting minutes recorded an earlier police statement that there were no further realistic lines of enquiry at that time.

  there are no further realistic lines of enquiry at this time

  Sussex Police, quoted in PCC meeting minutes · Source [2]

  As of: Time not established

  The date is the documented meeting update, not a finding that the investigation formally closed on that date. No identified suspect or conviction is inferred.

What we know

Hundreds of flights were cancelled between 19 and 21 December 2018.

Reuters’ contemporary airport reporting describes the disruption and the return toward normal operations. The Sussex Police and Crime Commissioner’s minutes of 18 October 2019 record the chief constable’s account of witness evidence, police inquiries and the scale of disruption. The minutes distinguish sighting reports, witnesses and investigated people: none of those totals is a count of separate drones. Police described credible witness evidence of incursions, but the selected public record does not supply technical identification of an operator or aircraft model. The Home Office’s later policy discussion reuses the incident as an example; it is not an independent accident investigation.

What remains unknown

The October 2019 account said realistic lines of inquiry had been exhausted while allowing reassessment if new information emerged. That is a dated investigation position, not proof that the sightings were fabricated or that a culprit was identified. The Reuters article’s publication date must not be used to infer later legal outcomes absent from its text. The dossier does not reproduce private suspects’ identities or precise flight positions. Large passenger and flight totals describe operational consequences, not proof of a particular drone type.

Not established in the cited sources.

How the story changed

1. 19 Dec 2018

   The period of cancellations following reported sightings began. [1]

2. 21 Dec 2018

   Last day of the disruption period described in the government response. [1]

3. 18 Oct 2019

   Official meeting minutes recorded that police had reported no further realistic lines of enquiry at that time. [2]

4. 18 Oct 2019

   Chief constable’s published meeting account describes the evidence, exhausted realistic inquiries and scope for reassessment if new information emerges. [2]

Original sources (4)

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

Editorial changes

1. Revision 8 · 27 Oct 2026Updated the explanation of evidence and its limitations.
2. Revision 7 · 16 Oct 2026Added a sourced general counter-drone measure at this location.
3. Revision 6 · 16 Oct 2026Added a historical report from the verified publisher channel; playback is optional and evidence assessments are unchanged.
4. Revision 5 · 15 Oct 2026Added a no-thumbnail publisher source link; no hosted image or video and no evidence-state change.
5. Revision 4 · 15 Oct 2026Map now shows the named airport as given in the sources (a static facility reference, not a drone or impact position). Evidence status unchanged.
6. Revision 3 · 15 Oct 2026Added sourced operational effects, the investigation follow-up and the airport archive link.
7. Revision 2 · 12 Oct 2026Added claim-level evidence: each key claim with its source passage, original source and assessment; passages checked word for word against the sources.
8. Revision 1 · 12 Oct 2026Initial dossier imported after source review.