The FAA's Secret UAP Files: Commercial Airlines Were Already Reporting

The Federal Aviation Administration was systematically documenting UAP encounters involving major commercial carriers throughout 2023, starting with Southwest Flight 1307 on March 22 — eight months before Congress knew about any coordinated federal response.

While Pentagon officials testified about establishing new UAP protocols in late 2023, the National Archives reveal a different timeline. The FAA had already created Record Group 615, a dedicated filing system for "Unidentified Anomalous Phenomena Records Collection," and was processing reports from American Airlines, Delta, Southwest, and United flights as routine aviation safety matters.

The earliest documented case involves Southwest Flight 1307. March 22, 2023. Whatever the crew reported that day became the first entry in what we now know was an active, ongoing documentation system — one that nobody in Congress seemed aware of during public hearings about UAP transparency.

The Paper Trail Nobody Mentioned

Twenty-nine incident reports sit in the National Archives. Each one a single page. Each one catalogued with clinical precision: flight number, date, "UFO-UAP ACTIVITY." The metadata tells a story federal officials haven't shared publicly.

American Airlines appears most frequently. AAL1913, AAL2054, AAL2928, AAL821. Four separate incidents spanning July 2023 through July 2024. Delta follows with three reports. Southwest logged four encounters, including that initial March incident that started the whole collection.

Here's what's interesting about the filing system. Some reports reference specific flights — DAL2665, UAL1560, JBU811. Others reference locations instead of aircraft: "Birmingham, AL UFO-UAP Activity," "Goffs, CA UFO-UAP Activity," "Rio Grande, NJ UFO-UAP Activity." The location-based files suggest ground radar or tower observations, not just pilot reports.

Then there's the document labeled "CONUS UFO-UAP Activity" from October 12, 2023. CONUS means Continental United States. That's not a single incident. That's a summary of nationwide activity, implying coordination between multiple FAA facilities across the country.

The Restricted File

Twenty-eight documents are fully accessible to the public. One isn't. The master file — "Records from the Federal Aviation Administration Relating to Unidentified Anomalous Phenomena" — carries a "Restricted - Partly" designation. Zero pages available for public viewing.

This matters because unrestricted incident reports typically contain operational details that agencies consider safe for public release. The restricted master file likely contains protocols, procedures, or analytical summaries that someone decided the public shouldn't see yet.

The FAA hasn't explained what operational guidance pilots and air traffic controllers were following during this period. When American Airlines Flight 1913 encountered something unusual on July 5, 2024, what procedures did the crew follow? Who did they contact? What happened next?

The Timeline Gap

Pentagon officials told Congress that systematic UAP data collection began in earnest after the All-Domain Anomaly Resolution Office launched its public mission in December 2023. But Southwest Flight 1307's March 2023 encounter predates that by nine months.

Either the FAA was running its own UAP program independently, or federal agencies were coordinating on UAP documentation well before they told Congress about it. Both possibilities raise questions about what other systematic data collection was happening behind the scenes.

The frequency pattern suggests routine processing, not crisis response. Reports arrive steadily throughout 2023 and into 2024. April, May, July, August, September, October, November, December. Then January, February, July of 2024. This isn't a handful of unusual incidents. This is ongoing documentation of what appears to be regular phenomena.

What Air Traffic Control Knew

The most revealing detail might be the mix of commercial carriers represented. American, Delta, Southwest, United, JetBlue, Alaska Airlines. Plus corporate jets with tail numbers like N781CW and N268CA. Even FedEx Flight 64 appears in the collection.

This wasn't isolated to one airline or one region. UAP encounters were happening across the commercial aviation system frequently enough that the FAA established a dedicated record-keeping process. The question is whether passengers on these flights knew their aircraft had reported anomalous phenomena.

Commercial aviation operates under strict safety protocols. Pilots don't file incident reports casually. Air traffic controllers don't create documentation for routine events. The existence of these files suggests UAP encounters had become common enough to warrant systematic tracking within the aviation safety framework.

The Archive Advantage

While Congress debates UAP transparency and Pentagon officials brief classified committees, the National Archives has been quietly processing Freedom of Information Act releases. Record Group 615 appeared without fanfare. No press releases. No congressional notifications. Just methodical archival work making government records accessible to anyone who knows where to look.

The FAA documents join eight decades of UAP files already sitting in College Park, Maryland. Air Force records, CIA documents, Navy reports — all catalogued and available. The biggest UAP disclosure might not come from a whistleblower or a congressional hearing. It might come from a filing cabinet.

The Southwest Flight 1307 incident from March 2023 is now part of the permanent federal record. So are the other twenty-eight cases that followed. Whatever those crews saw, whatever air traffic controllers tracked, whatever protocols they followed — it's all documented somewhere in the federal system.

The question isn't whether the government takes UAPs seriously. The archives prove they do. The question is what operational procedures were already in place while officials testified about establishing new ones.

Stay curious.

Follow @boggleriley • Subscribe at spacedew.com