Airport disruption
Reagan National flights disrupted after reported drone
Arlington · 21 Jul 2022 · event date · approximate location
Flights at Ronald Reagan Washington National Airport were temporarily disrupted on 21 July 2022 after a reported drone sighting. The airport subsequently reported normal operations by 14:15 local time. [1][2]
Drone presence is reported. The consequences are established. The operator is not 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 · 21 Oct 2026 · Dossier updated 21 Oct 2026
What do we know now?
Flights at Ronald Reagan Washington National Airport were temporarily disrupted on 21 July 2022 after a reported drone sighting. The airport subsequently reported normal operations by 14:15 local time. Drone presence remains reported rather than independently identified here.
Facts at a glance
- Drone type
- No named drone type is recorded in this dossier.
- Effects
- According to arlnow.com, citing Reagan Airport operational update reproduced by ARLnow, The airport said normal operations had resumed by 14:15
- According to gao.gov, citing US Government Accountability Office, GAO describes a July 2022 halt after a drone sighting
- Who reported what
- arlnow.com: Assessment of drone involvement; reported outcome
- gao.gov: 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.
| Track | Recorded date / time |
|---|---|
| 1 · Event |
|
| 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
- ARLnow reporting on FAA notice · “The ground stop and delays follow reports of someone flying a drone in the area.” arlnow.com
- Reagan Airport operational update reproduced by ARLnow · “Normal operations resumed by 2:15 p.m.” arlnow.com
- US Government Accountability Office · “flight operations were halted at Reagan Washington National Airport” gao.gov
Claims and evidence
2 sources · 3 original statements
Sources that repeat the same original statement count once: a number of articles is not a number of independent confirmations.
| Claim | Original source | Assessment |
|---|---|---|
| Drone The local report links the ground stop to reported drone flying. [1]Source passage“The ground stop and delays follow reports of someone flying a drone in the area.” Passage checked word for word against the source on 16 Oct 2026. | ARLnow reporting on FAA notice via ARLnow | Supports the report Short literal passage read on the public source page; reported drone presence is not technical identification. |
| Impact The airport said normal operations had resumed by 14:15. [1]Source passage“Normal operations resumed by 2:15 p.m.” Passage checked word for word against the source on 16 Oct 2026. | Reagan Airport operational update reproduced by ARLnow via ARLnow | Supports the report Short literal passage read on the public source page; reported drone presence is not technical identification. |
| Impact GAO describes a July 2022 halt after a drone sighting. [2]Source passage“flight operations were halted at Reagan Washington National Airport” Passage checked word for word against the source on 16 Oct 2026. | US Government Accountability Office via US GAO | Supports 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.
- ARLnow reporting on FAA notice
- ARLnow: FAA notice and airport operational update [1] · Relayed statement
- Reagan Airport operational update reproduced by ARLnow
- ARLnow: FAA notice and airport operational update [1] · Relayed statement
- US Government Accountability Office
- US GAO: later official airport-safety overview [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 | Visible support |
|---|---|---|
| The local report links the ground stop to reported drone flying. | [1] | Support remains visible |
| The airport said normal operations had resumed by 14:15. | [1] | Support remains visible |
| GAO describes a July 2022 halt after a drone sighting. | [2] | Support remains visible |
What we know
ARLnow records a ground stop and departure delays, followed by the airport normal-operations update. GAO later confirms that flight operations were halted after a drone sighting. No fixed closure duration or verified diversion total is assigned; an average delay is not the duration of the stop.
ARLnow quotes the airport operational update and describes FAA notices. GAO provides a separate official safety review. Both may share the original sighting and operational records; separate publications are not two technical detections. No physical drone evidence is supplied in the reviewed passages.
Data
- No structured detail recorded
- Hit / damaged · Fell near · Intercepted (claimed) · Human consequences
What remains unknown
The local event date is 21 July in Arlington, Virginia, not a separately established drone position in Washington DC. ARLnow gives approximate FAA timing and a later normal-operations time; these do not establish continuous suspension until 14:15. Its quoted informal diversion reports are not official counts and are omitted. Operator, device type, precise count, physical harm and attribution remain unestablished.
No operator or responsible organisation established by the reviewed sources.
How the story changed
Original sources (2)
2 source families · a count of sources is not a verification score
1ARLnow: FAA notice and airport operational update21 Jul 2022 · source family: Local news now2US GAO: later official airport-safety overview27 Jun 2024 · source family: US GAOEditorial changes
- Revision 2 · 21 Oct 2026Typography: added missing spaces in dates and times (live-site audit 21 Oct 2026); no change of content.
- Revision 1 · 16 Oct 2026Curated dossier created after checking the cited sources line by line.
Cite this dossier
Chicago
DroneLedger editorial team. “Reagan National flights disrupted after reported drone.” Dossier reagan-national-airport-drone-report-2022-07-21, revision 2, updated 21 Oct 2026. https://droneincidents.com/incident/reagan-national-airport-drone-report-2022-07-21/v2/
APA
DroneLedger editorial team. (21 Oct 2026). Reagan National flights disrupted after reported drone (Dossier reagan-national-airport-drone-report-2022-07-21, revision 2). https://droneincidents.com/incident/reagan-national-airport-drone-report-2022-07-21/v2/
Cite the revision you used: later revisions may change evidence states.
Cite this version
- Maker
- DroneLedger editorial team
- ID
- reagan-national-airport-drone-report-2022-07-21
- Revision or edition
- 2
- Release
- 20261102T055221362217-c8d330
- Publication date
- 21 Oct 2026
- Accessed
- 09 Nov 2026
- Permanent URL
- https://droneincidents.com/incident/reagan-national-airport-drone-report-2022-07-21/v2/
- Hashed file
- JSON · SHA-256
a8a1bb2423f71757624643cc76699254b750c12a30e22f47af17e2f8e4c91b70
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. Reagan National flights disrupted after reported drone. ID reagan-national-airport-drone-report-2022-07-21; revision or edition 2; release 20261102T055221362217-c8d330; published 21 Oct 2026. https://droneincidents.com/incident/reagan-national-airport-drone-report-2022-07-21/v2/ Accessed 09 Nov 2026. SHA-256 a8a1bb2423f71757624643cc76699254b750c12a30e22f47af17e2f8e4c91b70 (https://droneincidents.com/data/citations/incident/reagan-national-airport-drone-report-2022-07-21/r2/a8a1bb2423f71757624643cc76699254b750c12a30e22f47af17e2f8e4c91b70/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