Featured image: AI-generated editorial illustration; not an image or measured reconstruction of the incident.
Aircraft were waiting to depart San Diego when reports of objects near the runway brought operations to a halt. Newly published FAA records now show how uncertain the picture remained—even as controllers and military personnel responded.
The September 4, 2026 incident is receiving renewed attention because The Black Vault published the released records on November 3. The central distinction is simple: the files document an aviation disruption and reports of suspected drones. They do not establish an extraordinary craft or confirm that the military shot anything down.
What the written reports say
In occurrence report SAN-M-2026/09/04-0004, controllers recorded repeated reports from taxiing aircraft before the tower obtained its own visual contact. The summary describes a silver object north of the runway. A police helicopter crew reportedly saw it but could not obtain video.
The report groups the observations into three entries, including one concerning Naval Air Station North Island. That numbering should not be treated as a reliable count of three distinct aircraft: the same summary explicitly allows that a later sighting could have involved an earlier object.
North Island’s reported message was that personnel were preparing to engage an unauthorized drone. Preparing to act is not confirmation that an engagement occurred, and the report supplies no recovery account or verified outcome.
That leaves a real safety incident with an incomplete identification record. Multiple reports strengthen the evidence that people observed something worth investigating; they do not, by themselves, determine what it was.
One pilot report, and a limit on precision
The separate report concerning Southwest Flight 1562 records a suspected drone near the departure end. Its quality-assurance review gives an approximate altitude of 1,000 feet but says the closest proximity was not reported. It also marks the event as not a verified near-midair collision.
Those omissions matter. An approximate altitude is not a measured separation, and a pilot’s object report is not an identification of its operator. Retelling the episode as a precisely reconstructed close encounter would go beyond the released information.
Why the audio requires care
The Black Vault also reports a possible-shootdown remark in the ground-control audio. Its accompanying transcripts are software-generated working transcripts, not FAA-issued transcripts. PW has not independently audited that audio passage, so the remark is not treated here as confirmation of a military action.
The FAA’s October 22 response letter identifies two audio re-recordings and two occurrence reports. It says no responsive transcripts, facility logs, decisional documents or specified coordination records were found. That describes the scope of this release; it does not prove that no other agency holds relevant records.
Readers can examine the PDFs and listen through The Black Vault’s document and audio archive. The FAA notes that the recordings carry an encoded time source on the right channel, with voice audio available by moving the balance fully left.
What would resolve the uncertainty?
A confirmed identification would require evidence connecting an observation to a specific object. A confirmed shootdown would require corroboration of the action and its outcome. Neither follows merely from an urgent response or an uncertain radio remark.
The useful development here is access to the underlying record. It lets readers distinguish what personnel reported, what operations changed, and which questions remain unanswered—without turning those unanswered questions into an explanation.
Leave a Reply