San Diego FAA Records Describe a Runway Halt and a Military Call About a Drone
FAA occurrence reports released through FOIA document the September 4 disruption, multiple reporting aircraft and a North Island call about preparing to engage. They do not confirm a shootdown.
Location San Diego, California

The departures stopped before the tower could see what the pilots were reporting. That sequence is recorded in newly released FAA paperwork about the September 4, 2026 disruption at San Diego International Airport: aircraft on the ground kept calling in an object, while controllers initially could not find it themselves.
The documents also record a call from nearby Naval Air Station North Island saying military personnel were preparing to engage an unauthorized drone. That is a documented report of an intention, not confirmation that a drone was fired on or destroyed.
The event happened on September 4. The FAA’s FOIA response is dated October 22, and John Greenewald published the records through The Black Vault on November 3.
What the original reports say
We reviewed the FAA’s response letter and both released Mandatory Occurrence Reports directly. The longer report, ending in 0004, places the beginning of the airport event at 1:54 p.m. Phoenix time on September 4. San Diego was on Pacific daylight time that day, so the local clocks matched Phoenix.
Its narrative says multiple taxiing aircraft reported a drone near the departure end of the runway. It then states: “ALL DEPARTURES STOPPED.” The tower initially lacked a visual, while “AT LEAST 7 PLUS A/C KEPT REPORTING IT.”
That last phrase counts reporting aircraft. It does not mean seven objects, seven confirmed drones or seven independent instrument tracks.
At about 2:30 p.m. Phoenix, according to the narrative, the tower obtained a visual of a silver object north of the runway over Taxiway F. At 2:40 p.m. Phoenix, the ASTREA police helicopter reportedly obtained a visual too, but could not get video. The document records observations; it does not supply an image of the object.
A second sighting, not necessarily a second object
The longer report next describes a Southwest flight reporting a silver object off the departure end at 3 p.m. Phoenix. Another Southwest flight reported an object eight minutes later.
Crucially, the report says the tower had lost sight of the earlier object, so this could have been the same one. Its numbered headings are a way of organizing reports, not a settled inventory of separate aircraft in the sky.
The shorter report, ending in 0001, concerns Southwest Flight 1562. Its quality-assurance finding records a reported altitude of approximately 1,000 feet and says the closest proximity was not reported. Both reports mark the incident as not a verified near-midair collision.
There is a notation problem worth preserving rather than smoothing away. The longer narrative uses altitude entries such as “003” and “015” followed by “FEET,” while its later QA finding gives approximately 300 to 1,500 feet. We are not treating the narrative’s shorthand as independently established measurements or silently converting it into a precise flight path.
The call from North Island
The longer report separately records a North Island call at about 2:30 p.m. Phoenix. Its summary says the military had an unauthorized drone it was preparing to engage. That wording supports a narrow conclusion: the FAA recorded receiving that message.
It does not establish which object the military meant, whether it was connected to the airport sightings, what kind of response was contemplated, or whether an engagement occurred. No outcome is documented in that passage.
The released Ground Control recording (opens in new tab) contains a separate exchange at approximately 55:52 into the audio. A controller says: “I think there’s one over North Island that just got shot down.”
The opening “I think” matters. This is a controller relaying an uncertain report, not a corroborated military announcement that a drone was destroyed. The preparation-to-engage wording comes from the written occurrence report, not this audio exchange. Neither source establishes an actual shootdown, and this exchange does not settle the number or identity of the objects.
The FAA’s own response explicitly says no responsive transcripts were found. The Black Vault explains that its accompanying transcripts were generated with its software. They should not be labeled official FAA transcripts.
Where it started
This story starts with the FOIA release and its accompanying documents (opens in new tab), not a verified witness social-media post. No verified witness social thread accompanies the material reviewed. The written records and released audio are the underlying sources, rather than a public comment conversation.
The original Ground Control recording (opens in new tab) and Local Control recording (opens in new tab) are linked for readers. These are audio files, not encounter video; no verified embeddable encounter video was identified.
The response letter identifies four responsive records: two tower audio re-recordings and two occurrence reports. That inventory tells us what was released, not that every interpretation of the material has been verified. In particular, a recorded report of an intended action and a confirmed outcome are different kinds of evidence.
The strongest finding is operational: several aircraft reported suspected unmanned-aircraft activity, departures stopped, and law enforcement became involved. The objects’ identities, their operators and the outcome at North Island remain unresolved in the material reviewed. None of that establishes a nonhuman origin.
Sources
- FAA FOIA response, case 2026-05893, October 22, 2026 (opens in new tab) · FAA, archived by The Black Vault
- Mandatory Occurrence Report SAN-M-2026/09/04-0004 (opens in new tab) · FAA, archived by The Black Vault Primary PDF reviewed directly; narrative and QA findings distinguished.
- Mandatory Occurrence Report SAN-M-2026/09/04-0001 (opens in new tab) · FAA, archived by The Black Vault
- September 4 Ground Control audio, source offset approximately 55:52 (opens in new tab) · FAA, archived by The Black Vault The controller relays an uncertain shootdown report. This is not corroboration that a drone was destroyed; the preparation-to-engage entry is in the separate written occurrence report.
- FAA Records Reveal Military Prepared to Engage Drone During San Diego Airport Shutdown; ATC Audio References Possible Shootdown (opens in new tab) · The Black Vault John Greenewald, November 3, 2026. Accompanying software-generated transcripts are not FAA transcripts.