Editorial pack · DroneLedger
Newark arrivals paused after nearby suspected drone reports
Current state
Arrivals at Newark Liberty International Airport were briefly paused on 22 January 2019 after pilots reported an object thought to be a drone near Teterboro. Drone presence was not independently established.
Evidence states
| Drone presence | reported · sources [1], [2] |
|---|---|
| Impact | confirmed · sources [1], [2] |
| Attribution | none · sources none |
The FAA reported an arrival pause and delays to some departures for Newark. United Airlines described its operational impact as minimal. No full-airport closure duration is established here.
TIME relays separate FAA and airline statements. AOPA reports the operational response and its own aviation-security specialist’s doubts about visual identification. These are distinct reporting and operational origins, with shared pilot reports rather than two technical detections.
Claims
2 sources · 3 original statements. Sources that repeat the same statement count once.
| Claim and source passage | Original source | Assessment |
|---|---|---|
| AOPA records a ground stop at the affected Newark airport. “prompting a ground stop at nearby Newark Liberty International Airport” [1] | AOPA reporting / airport operations (relayed) | supports: Short literal passage read on the public source page; reported drone presence is not technical identification. |
| United described the impact as minimal at the time of its statement. “The impact to our operations has been minimal so far.” [2] | United Airlines (relayed) | supports: Short literal passage read on the public source page; reported drone presence is not technical identification. |
| The object was described as resembling a drone, not technically identified. “looks like a drone” [1] | Pilot report relayed by AOPA (relayed) | supports: Short literal passage read on the public source page; reported drone presence is not technical identification. |
Earlier matching archive records
Published archive records only, not all real-world incidents or a common cause.
30 days: 0
90 days: 0
As of: 2026-10-16T02:26:41+00:00
Not established
The reported sighting was near Teterboro; Newark is the affected airport, not a proven drone position. AOPA describes takeoff disruption as well, while TIME specifically describes arrivals: no claim that every operation stopped. Source publication on 23 January UTC is consistent with the 22 January local-evening event. No device count, type, operator or physical damage established.
No operator or responsible organisation established by the reviewed sources.
Chronology
- 22 Jan 2019: Arrivals at Newark Liberty International Airport were briefly paused on 22 January 2019 after pilots reported an object thought to be a drone near Teterboro. Drone presence was not independently established. [1]
Sources
- AOPA: pilot reports and identification uncertainty (2019-01-23, source family: aopa)
https://www.aopa.org/news-and-media/all-news/2019/january/23/flights-disrupted-after-drone-reports - TIME: FAA and United Airlines statements (2019-01-23, source family: time)
https://time.com/5510249/newark-airport-drone/
How to cite
DroneLedger. “Newark arrivals paused after nearby suspected drone reports.” Dossier newark-airport-drone-report-2019-01-22, revision 1, updated 16 Oct 2026. https://droneincidents.com/incident/newark-airport-drone-report-2019-01-22/v1/
Editorial changes
- Revision 1 (2026-10-16): Curated dossier created after checking the cited sources line by line.
Evidence states: confirmed = established by the cited evidence; reported = stated by a source, not independently established; inconclusive; debunked; unknown. A claim by a party to a conflict remains a claim. Methodology: https://droneincidents.com/methodology/