DroneLedger

Airport disruption

Reported drones prompt a temporary runway restriction at Stewart Airport

Newburgh, New York · 13 Dec 2024 · event date · approximate location

Reported drone activity led to a temporary runway restriction at New York Stewart International Airport on 13 December 2024. [1][2]

Drone presence is reported. The consequences are established. The operator is not established.

Drone presenceReported[1]
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 · 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?

Reported drone activity led to a temporary runway restriction at New York Stewart International Airport on 13 December 2024.

Facts at a glance
Drone type
  • No named drone type is recorded in this dossier.
Context
  • According to news12.com, citing Port Authority of New York and New Jersey, The airport operator says flight operations were not affected during the restriction
Effects
  • According to ny.gov, citing New York Governor, The governor describes a runway restriction of about an hour
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
  • New York Governor · “runways at Stewart Airfield were shut down for approximately one hour” ny.gov
  • Port Authority of New York and New Jersey · “There were no impacts to flight operations during the closure.” news12.com
  • Joint DHS/FBI/FAA/DoD statement · “stars mistakenly reported as drones” factcheck.org

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
Impact

The governor describes a runway restriction of about an hour.

[1]
Source passage
“runways at Stewart Airfield were shut down for approximately one hour”

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

New York GovernorSupports the report

Literal short passage checked in the original source; no independent confirmation inferred from republication.

Impact

The airport operator says flight operations were not affected during the restriction.

[2]
Source passage
“There were no impacts to flight operations during the closure.”

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

Port Authority of New York and New Jersey via News12Context only

Literal short passage checked in the original source; no independent confirmation inferred from republication.

Drone

The later regional assessment includes misidentified stars; it is not a finding for this individual alarm.

[3]
Source passage
“stars mistakenly reported as drones”

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

Joint DHS/FBI/FAA/DoD statement via FactCheck.orgContext only

FactCheck.org quotes the joint federal statement. One shared federal origin, not independent agency confirmations; regional context only.

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. New York Governor
    • New York Governor:14December statement about previous night [1] · Direct account
  2. Port Authority of New York and New Jersey
    • News12: Port Authority statement on operational effects [2] · Relayed statement
  3. Joint DHS/FBI/FAA/DoD statement
    • FactCheck.org: joint federal assessment quoted, regional context only [3] · 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
The governor describes a runway restriction of about an hour.[1]Support remains visible
The airport operator says flight operations were not affected during the restriction.No supporting link recordedNo supporting link recorded
The later regional assessment includes misidentified stars; it is not a finding for this individual alarm.No supporting link recordedNo supporting link recorded

What we know

The New York governor described a runway shutdown of about an hour. The Port Authority separately said there were no impacts to flight operations during the closure. A precautionary restriction is documented; delayed or cancelled flights are not established.

The governor and Port Authority supply separate official accounts of the restriction. This does not independently identify a drone. The later joint federal assessment, quoted by FactCheck.org, describes a regional mixture of lawful drones and misidentified aircraft or stars rather than identifying the object behind this specific alarm.

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

What remains unknown

Exact restriction boundaries and object identity remain unresolved. No operator, hostile purpose or link to other northeast incidents is established. Broader official explanations must not be treated as a case-specific debunk. The point represents Newburgh, not a drone location.

No operator or responsible organisation established by these sources; no criminal charge or conviction is asserted.

How the story changed

  1. The governor describes about an hour of runway closure on the preceding night. [1]

  2. News12 publishes the Port Authority statement that flight operations were not affected during the closure. [2]

Original sources (3)

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

1New York Governor:14December statement about previous night14 Dec 2024 · source family: Governor of New York2News12: Port Authority statement on operational effects16 Dec 2024 · source family: News123FactCheck.org: joint federal assessment quoted, regional context only19 Dec 2024 · source family: Annenberg factcheck

Editorial changes

  1. Revision 2 · 16 Oct 2026Added a sourced general counter-drone measure at this location.
  2. Revision 1 · 15 Oct 2026Curated dossier created after checking the cited sources line by line.

Cite this dossier

Permanent page · Revision 2

Chicago

DroneLedger editorial team. “Reported drones prompt a temporary runway restriction at Stewart Airport.” Dossier stewart-airport-drone-report-2024-12-13, revision 2, updated 16 Oct 2026. https://droneincidents.com/incident/stewart-airport-drone-report-2024-12-13/v2/

APA

DroneLedger editorial team. (16 Oct 2026). Reported drones prompt a temporary runway restriction at Stewart Airport (Dossier stewart-airport-drone-report-2024-12-13, revision 2). https://droneincidents.com/incident/stewart-airport-drone-report-2024-12-13/v2/

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

Cite this version

Maker
DroneLedger editorial team
ID
stewart-airport-drone-report-2024-12-13
Revision or edition
2
Release
20261109T002636372024-fb099f
Publication date
16 Oct 2026
Accessed
09 Nov 2026
Permanent URL
https://droneincidents.com/incident/stewart-airport-drone-report-2024-12-13/v2/
Hashed file
JSON · SHA-256 b74e958c09e0632d0d59b041afbfd254496487ad4d492553bc595fbfbb487f4e

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. Reported drones prompt a temporary runway restriction at Stewart Airport. ID stewart-airport-drone-report-2024-12-13; revision or edition 2; release 20261109T002636372024-fb099f; published 16 Oct 2026. https://droneincidents.com/incident/stewart-airport-drone-report-2024-12-13/v2/ Accessed 09 Nov 2026. SHA-256 b74e958c09e0632d0d59b041afbfd254496487ad4d492553bc595fbfbb487f4e (https://droneincidents.com/data/citations/incident/stewart-airport-drone-report-2024-12-13/r2/b74e958c09e0632d0d59b041afbfd254496487ad4d492553bc595fbfbb487f4e/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