DroneLedger

Airport disruption

Newark arrivals paused after nearby suspected drone reports

Newark · 22 Jan 2019 · event date · approximate location

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][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 · Dossier updated 16 Oct 2026

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

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.

Facts at a glance
Drone type
  • No named drone type is recorded in this dossier.
Context
  • According to Time, citing United Airlines, United described the impact as minimal at the time of its statement
Effects
  • According to aopa.org, citing AOPA reporting / airport operations, AOPA records a ground stop at the affected Newark airport
Who reported what
  • aopa.org: Assessment of drone involvement; reported outcome
  • Time: 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.
Check the evidence
Source passage
  • AOPA reporting / airport operations · “prompting a ground stop at nearby Newark Liberty International Airport” aopa.org
  • United Airlines · “The impact to our operations has been minimal so far.” Time
  • Pilot report relayed by AOPA · “looks like a drone” aopa.org

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.

ClaimOriginal sourceAssessment
Impact

AOPA records a ground stop at the affected Newark airport.

[1]
Source passage
“prompting a ground stop at nearby Newark Liberty International Airport”

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

AOPA reporting / airport operations via AOPASupports the report

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

Impact

United described the impact as minimal at the time of its statement.

[2]
Source passage
“The impact to our operations has been minimal so far.”

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

United Airlines via TIMESupports the report

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

Drone

The object was described as resembling a drone, not technically identified.

[1]
Source passage
“looks like a drone”

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

Pilot report relayed by AOPA via AOPASupports 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.

  1. AOPA reporting / airport operations
    • AOPA: pilot reports and identification uncertainty [1] · Relayed statement
  2. United Airlines
    • TIME: FAA and United Airlines statements [2] · Relayed statement
  3. Pilot report relayed by AOPA
    • AOPA: pilot reports and identification uncertainty [1] · 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
AOPA records a ground stop at the affected Newark airport.[1]Support remains visible
United described the impact as minimal at the time of its statement.[2]Support remains visible
The object was described as resembling a drone, not technically identified.[1]Support remains visible

What we know

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.

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

What remains unknown

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.

How the story changed

  1. 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]

Original sources (2)

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

1AOPA: pilot reports and identification uncertainty23 Jan 2019 · source family: AOPA2TIME: FAA and United Airlines statements23 Jan 2019 · source family: TIME

Editorial changes

  1. Revision 2 · 16 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. “Newark arrivals paused after nearby suspected drone reports.” Dossier newark-airport-drone-report-2019-01-22, revision 2, updated 16 Oct 2026. https://droneincidents.com/incident/newark-airport-drone-report-2019-01-22/v2/

APA

DroneLedger editorial team. (16 Oct 2026). Newark arrivals paused after nearby suspected drone reports (Dossier newark-airport-drone-report-2019-01-22, revision 2). https://droneincidents.com/incident/newark-airport-drone-report-2019-01-22/v2/

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

Cite this version

Maker
DroneLedger editorial team
ID
newark-airport-drone-report-2019-01-22
Revision or edition
2
Release
20261109T002636372024-fb099f
Publication date
16 Oct 2026
Accessed
09 Nov 2026
Permanent URL
https://droneincidents.com/incident/newark-airport-drone-report-2019-01-22/v2/
Hashed file
JSON · SHA-256 4ba9b0082adb954dd6354f9e058064a0bce4e927208acc3a9bbae74d10de661a

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. Newark arrivals paused after nearby suspected drone reports. ID newark-airport-drone-report-2019-01-22; revision or edition 2; release 20261109T002636372024-fb099f; published 16 Oct 2026. https://droneincidents.com/incident/newark-airport-drone-report-2019-01-22/v2/ Accessed 09 Nov 2026. SHA-256 4ba9b0082adb954dd6354f9e058064a0bce4e927208acc3a9bbae74d10de661a (https://droneincidents.com/data/citations/incident/newark-airport-drone-report-2019-01-22/r2/4ba9b0082adb954dd6354f9e058064a0bce4e927208acc3a9bbae74d10de661a/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