Airport disruption
Drone report prompts flight restrictions at San Diego airport
San Diego · 04 Sep 2026 · event date · approximate location
San Diego International Airport experienced flight restrictions on 4 September 2026. Airport officials reportedly linked the disruption to sightings of a drone and a weather balloon; an FAA advisory independently records a security-related ground stop. [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 · 17 Oct 2026 · Dossier updated 17 Oct 2026
What do we know now?
San Diego International Airport experienced flight restrictions on 4 September 2026. Airport officials reportedly linked the disruption to sightings of a drone and a weather balloon; an FAA advisory independently records a security-related ground stop.
Facts at a glance
- Drone type
- No named drone type is recorded in this dossier.
- Reported outcome
- According to FAA, citing FAA ATCSCC, A security-related ground stop was recorded, in a report published on 4 September 2026
- Who reported what
- FAA: Reported outcome
- techtimes.com: Assessment of drone involvement
- 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
- FAA ATCSCC · “IMPACTING CONDITION: OTHER / SECURITY” FAA
- San Diego Airport spokesperson via NBC7, relayed by TechTimes · “a drone and a weather balloon were observed near the airport” techtimes.com
Claims and evidence
2 sources · 2 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 |
|---|---|---|
| Impact The FAA records a security-related ground stop. [1]Source passage“IMPACTING CONDITION: OTHER / SECURITY” Passage checked word for word against the source on 16 Oct 2026. | FAA ATCSCC | Supports the report FAA advisory independently establishes restriction; not drone identification. |
| Drone The airport spokesperson reportedly described drone and balloon sightings. [2]Source passage“a drone and a weather balloon were observed near the airport” Passage checked word for word against the source on 16 Oct 2026. | San Diego Airport spokesperson via NBC7, relayed by TechTimes via TechTimes | Supports the report Explicitly secondhand spokesperson statement; no operational positions reproduced. |
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.
- FAA ATCSCC
- FAA ATCSCC advisory164: San Diego ground stop [1] · Direct account
- San Diego Airport spokesperson via NBC7, relayed by TechTimes
- TechTimes: airport spokesperson via NBC7 [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.
What we know
An FAA advisory records a ground-stop program for San Diego that afternoon, with arrival delays. This confirms an operational restriction, not the identity of every reported object or the cause of every delayed flight.
The FAA operational advisory is a primary record of the ground stop. TechTimes relays a San Diego airport spokesperson’s statement to NBC7 about drone and balloon sightings. FAA operations and the airport spokesperson are distinct origins for disruption; drone identification remains reported, not independently confirmed.
Data
- No structured detail recorded
- Hit / damaged · Fell near · Intercepted (claimed) · Human consequences · Effects
What remains unknown
The FAA advisory classifies the cause as security without naming a drone. The news article discusses a separate balloon; no assumption that every object was a drone. Its approximate onset/all-clear and aggregate delay totals are not adopted as exact incident times or drone-only effects. NBC page unavailable in web tool; ordinary GET returned an incomplete response, so no complete original NBC article read. TechTimes relay is explicit.
No operator established in the selected reporting.
How the story changed
FAA security ground stop and reported airport drone/balloon sightings. [1]
Original sources (2)
2 source families · a count of sources is not a verification score
1FAA ATCSCC advisory164: San Diego ground stop04 Sep 2026 · source family: Us faa2TechTimes: airport spokesperson via NBC706 Sep 2026 · source family: TechTimesEditorial changes
- Revision 2 · 17 Oct 2026Added a sourced general counter-drone measure at this location.
- Revision 1 · 16 Oct 2026Curated dossier created after checking the cited sources line by line.
Cite this dossier
Chicago
DroneLedger editorial team. “Drone report prompts flight restrictions at San Diego airport.” Dossier san-diego-airport-drone-report-2026-09-04, revision 2, updated 17 Oct 2026. https://droneincidents.com/incident/san-diego-airport-drone-report-2026-09-04/v2/
APA
DroneLedger editorial team. (17 Oct 2026). Drone report prompts flight restrictions at San Diego airport (Dossier san-diego-airport-drone-report-2026-09-04, revision 2). https://droneincidents.com/incident/san-diego-airport-drone-report-2026-09-04/v2/
Cite the revision you used: later revisions may change evidence states.
Cite this version
- Maker
- DroneLedger editorial team
- ID
- san-diego-airport-drone-report-2026-09-04
- Revision or edition
- 2
- Release
- 20261102T055221362217-c8d330
- Publication date
- 17 Oct 2026
- Accessed
- 09 Nov 2026
- Permanent URL
- https://droneincidents.com/incident/san-diego-airport-drone-report-2026-09-04/v2/
- Hashed file
- JSON · SHA-256
1c9c22e3d8d63008a5b9a6b34c4680c3a871e352bd974c0533408d8dc62b87b0
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. Drone report prompts flight restrictions at San Diego airport. ID san-diego-airport-drone-report-2026-09-04; revision or edition 2; release 20261102T055221362217-c8d330; published 17 Oct 2026. https://droneincidents.com/incident/san-diego-airport-drone-report-2026-09-04/v2/ Accessed 09 Nov 2026. SHA-256 1c9c22e3d8d63008a5b9a6b34c4680c3a871e352bd974c0533408d8dc62b87b0 (https://droneincidents.com/data/citations/incident/san-diego-airport-drone-report-2026-09-04/r2/1c9c22e3d8d63008a5b9a6b34c4680c3a871e352bd974c0533408d8dc62b87b0/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