San Diego Airport Drone Records Show Navy Prepared to Engage

When San Diego International Airport stopped its flights on the afternoon of Sept. 4, the public explanation was short. Airport officials said a drone and a weather balloon had been spotted nearby around 2 p.m., and that operations were back to normal by 4:30, ABC 10News reported. More than 400 flights were delayed at the start of Labor Day weekend, TechTimes reported, citing FlightAware.

The Federal Aviation Administration’s own paperwork tells a fuller story. On Oct. 22, the FAA released two incident reports and two tower audio recordings from that afternoon to John Greenewald of The Black Vault, under a Freedom of Information Act request he filed on Sept. 10. He posted them on Nov. 3. We read both reports in full. They describe three objects, a call from the Navy, and no balloon at all.

Three objects, one call from the Navy

The main report, numbered SAN-M-2026/09/04-0004 and flagged as a significant occurrence, sets out the afternoon object by object. The first was reported at 1:54 p.m. local time (20:54 UTC). Taxiing planes reported a drone over the departure end of the runway, and all departures were stopped. The tower couldn’t see it at first, but at least seven aircraft kept reporting it. About 2:30 p.m., after a United flight called it in, controllers spotted a silver object hovering north of the runway over a taxiway. A police helicopter, ASTREA, saw it at 2:40 p.m. but couldn’t get video.

The second object came at 3 p.m., when Southwest Flight 1562 reported a silver drone about a mile off the departure end of the runway. Another Southwest crew reported the same thing eight minutes later. By then the tower had lost sight of the first object, and the report says the two could be the same.

The third entry is two lines long. At 2:30 p.m., it says, Naval Air Station North Island, across the bay, called to say the military had an unauthorized drone that it was “preparing to engage.” The report doesn’t say what happened next.

The event ran from 1:54 to 4 p.m., according to the report. Controllers notified four contacts listed only by abbreviation, among them the FAA’s Domestic Events Network.

Not 10 feet, 1,000

The reports write altitudes the way controllers do, in hundreds of feet, so a drone “about 003 feet to 015 feet” over the runway means roughly 300 to 1,500 feet. The FAA’s own quality review says so, putting the reported altitude at approximately 300 to 1,500 feet. The second report, SAN-M-2026/09/04-0001, covers only the Southwest sighting and lists both the plane and the drone at 1,000 feet. Read literally, the shorthand would put a drone 10 feet above a runway, which is not what the FAA recorded.

The quality review adds one more detail. Pilots both in the air and on the ground reported a drone near the airport, it says, and the naval air station “also reported UAS activity during a one-hour time frame.” UAS is the FAA’s term for a drone.

What isn’t in the file

Neither report mentions a balloon, though Greenewald’s request asked about both. Some later accounts identified the balloon as a high-altitude research platform, which TechTimes attributed to the aviation site Simple Flying. We found nothing official confirming that.

The FAA also said it had nothing else to give. Its response letter says it found no transcripts, facility logs, decision records or records of coordination with the airport or law enforcement, “because the FAA did not create, maintain, or control these records.”

The most dramatic claim comes from the audio. Greenewald ran the ground control recording through transcription software and reports a voice saying, about 56 minutes in, that a drone over North Island “just got shot down.” We couldn’t confirm that line. The FAA released the audio without a transcript, the written report says only that the Navy was preparing to engage, and we found no statement from the Navy or the airport about any engagement. Who flew the drones, and whether any were brought down, isn’t in these records.

Primary source: FAA Mandatory Occurrence Report SAN-M-2026/09/04-0004 (PDF), with the Southwest 1562 report and the FAA’s FOIA response letter. Full context: The Black Vault’s release page, which also has the tower audio. Read them yourself.

Sources

Leave a Reply