This bill directs the Federal Aviation Administration to create standardized procedures and a reporting system for incidents involving unidentified anomalous phenomena (UAP) observed by aviation personnel, and to preserve relevant data for timely investigation. It also requires the FAA to coordinate with defense, intelligence, science, and weather agencies and to share archived information with the Department of Defense’s All‑Domain Anomaly Resolution Office.
Beyond data collection, the Act builds procedural protections: it bars use of UAP reports for enforcement (except accidents or crimes), shields airmen and medical certificates from being penalized for reporting, forbids reprisal actions by government employers and commercial operators, and requires a communications plan to reduce stigma and encourage reporting.
At a Glance
What It Does
The bill requires the FAA to adopt standardized collection, reporting, investigation, and archival procedures for UAP-related incidents, and to decide whether to route reports through the existing Aviation Safety Reporting Program or a new dedicated intake system with fields for object description and apparent kinematics.
Who It Affects
Pilots, flight crews, air traffic controllers, dispatchers, maintenance personnel, air carriers and airports are the primary reporters and subjects of new reporting rules; the FAA and multiple federal agencies (DoD, DNI, NASA, DHS, NOAA, NSF, DOE) must coordinate on analysis and information sharing.
Why It Matters
The statute creates an official, non‑punitive pathway for recording and analyzing anomalous encounters in the national airspace, couples civilian reporting with defense analysis, and inserts legal protections intended to reduce stigma that has previously discouraged reporting.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The Safe Airspace for Americans Act directs the FAA to move quickly—within 180 days of enactment—to build a coherent process for handling sightings or encounters that aviation personnel cannot immediately identify. The FAA must adopt common reporting fields, a process for archiving time‑sensitive data (such as pilot‑controller audio, radar, and air traffic management system logs), and procedures to ensure incidents are investigated in a timely fashion and integrated into broader analysis.
The bill forces a choice about intake: the FAA must decide whether to use the current Aviation Safety Reporting Program (ASRP) or to create a separate reporting system dedicated to UAP events. If the ASRP is used, the FAA has an explicit one‑year window to consider making intake changes so reports capture object descriptions and kinematic behavior; a new system must include these fields from the start.
The statute also requires the FAA to allow report submission via an electronic flight bag if doing so is safe and does not interfere with flying duties.To broaden analytical capacity, the FAA must coordinate with a long list of civilian and national security agencies—DoD, the Office of the Director of National Intelligence, NASA, DHS, NOAA, NSF, and DOE—and to share reports and archived incident data with the Department of Defense’s All‑Domain Anomaly Resolution Office. At the same time, the bill constrains downstream use of reports: the FAA may not use reports (or information derived from them) in enforcement actions, except when the information relates to accidents or criminal offenses.The Act also erects worker and credential protections.
Reporting a UAP cannot be held against airmen when evaluating mental fitness for medical certificates under 14 C.F.R. part 67, nor can it be used in competency evaluations for airmen certificates under 49 U.S.C. § 44709. The law bars reprisals—including revocation or suspension of clearances—by federal employees, contractors, air carriers, and commercial operators; it specifically forbids carriers from issuing cease‑and‑desist letters to individuals or organizations that report sightings.
Finally, the statute defines ‘‘unidentified anomalous phenomena’’ to include airborne objects not immediately identifiable, transmedium objects (those transitioning between space, air, and water), and submerged devices that display related behavior.
The Five Things You Need to Know
The FAA must complete initial procedures, reporting and archival capabilities, and a communications strategy within 180 days of enactment.
The Administrator must decide whether to accept reports through the current Aviation Safety Reporting Program or establish a new, exclusive UAP intake system; if ASRP is used, the FAA must consider intake updates within one year.
The FAA must coordinate with DoD, DNI, NASA, DHS, NOAA, NSF, and DOE, and share all incident reports and archived data with the Department of Defense’s All‑Domain Anomaly Resolution Office.
Reports submitted under the statute cannot be used in enforcement actions except when the information pertains to accidents or criminal activity, and the law bars reprisal actions (including clearance suspension or termination) against federal employees, contractors, and aviation employees who report.
The bill prevents the spotting or reporting of UAP from being considered in medical certificate evaluations under 14 C.F.R. part 67 and in competency evaluations for airmen certificates under 49 U.S.C. § 44709.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
A single‑line provision identifying the statute as the "Safe Airspace for Americans Act." This is only the formal name; it does not change substantive obligations but frames the Act’s focus on aviation safety.
FAA duties: standardize reporting, archive data, and assess threat
Subsection (a) lays out the FAA’s core deliverables: develop synchronized procedures for collecting and analyzing incidents that may involve UAP, create reporting channels for FAA employees and other aviation personnel, immediately archive time‑sensitive data (radar, voice, traffic management logs) to support investigations, and evaluate whether incidents pose a safety threat to the national airspace. Practically, this requires the FAA to define reporting fields, set retention practices, and build internal workflows for triage and follow‑up investigations.
Interagency coordination and mandatory sharing with DoD
The FAA must coordinate its work with a suite of federal partners—Defense, Intelligence, NASA, Homeland Security, NOAA, NSF, and Energy—reflecting the multidisciplinary nature of UAP analysis (safety, meteorology, science, and national security). Subsection (c) requires the FAA to transmit reports and archived materials to DoD’s All‑Domain Anomaly Resolution Office, formalizing a civilian‑to‑defense data channel that will shape how incidents are reviewed at the national security level.
Limits on use of reports for enforcement
This provision forbids the FAA from using reports (or information derived from them) in enforcement proceedings except when data relate to accidents or criminal offenses. The practical effect is to try to preserve the non‑punitive nature of the intake system so that safety‑oriented witnesses will not fear regulatory consequences for reporting anomalous events.
Communications, intake options, and electronic flight bag submissions
Within the same 180‑day window the FAA must publish and implement a communications strategy to publicize reporting channels and reduce stigma. The statute gives the Administrator two intake options: use the existing Aviation Safety Reporting Program or create a new, dedicated system. Either way, forms must capture object descriptions and apparent kinematic behavior; if ASRP is chosen, the FAA must consider upgrades within one year. The bill also permits report submission via an electronic flight bag if the FAA determines it is safe and does not interfere with flying duties, creating a potential low‑friction intake method for crews.
Protections for airmen, medical certificates, and anti‑reprisal rules
These subsections shield reporters from credential and employment penalties: reporting or spotting a UAP cannot be used against applicants or holders in medical certificate evaluations under 14 C.F.R. part 67 or in competency assessments under 49 U.S.C. § 44709. The statute also bars federal managers, contractors, and air carriers from taking personnel actions or issuing cease‑and‑desist letters as reprisals for reporting, and explicitly prohibits threats like clearance revocations tied to reporting.
Definitions: unidentified anomalous phenomena and transmedium objects
The Act codifies a working definition of UAP to include (A) airborne objects not immediately identifiable, (B) transmedium objects that move between space, atmosphere, and bodies of water, and (C) submerged devices that exhibit related behavior. It defines 'transmedium' as an object transitioning between space and atmosphere or atmosphere and water and not immediately identifiable, which sets a broad diagnostic scope for qualifying incidents.
This bill is one of many.
Codify tracks hundreds of bills on Transportation across all five countries.
Explore Transportation in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Pilots and flight crews — gain a non‑punitive, formal pathway to report unexplained sightings with legal protections that prevent those reports from being used against medical or competency credentials.
- Air traffic controllers and dispatchers — receive standardized reporting templates and archival requirements that preserve time‑sensitive data (voice, radar, system logs) needed to reconstruct incidents.
- FAA safety and investigative units — get higher‑quality, integrated datasets and formal interagency channels that can improve root cause analysis and risk assessment for anomalous encounters.
- Defense and intelligence analysts (including the All‑Domain Anomaly Resolution Office) — receive a steady, civil‑aviation‑sourced stream of incident data to inform national security assessments.
- Aviation safety researchers and scientific agencies (NOAA, NSF, NASA) — benefit from structured metadata and object description fields that enable scientific study of anomalous kinematics and environmental conditions.
Who Bears the Cost
- Federal Aviation Administration — must fund and staff new procedures, IT systems (or ASRP modifications), secure archival storage, and cross‑agency coordination, potentially within tight 180‑day deadlines.
- Air carriers and commercial operators — must update internal policies to avoid reprisals and may need to train staff on reporting protocols and retention of operational records requested for investigations.
- Small operators and general aviation pilots — could face operational friction if demanded to furnish additional data or if carriers impose new reporting workflows that were designed around larger operators.
- Department of Defense and All‑Domain Anomaly Resolution Office — will receive increased data inflow that requires analysis capacity and classification decisions, imposing processing and security costs.
- Privacy and records managers — agencies must handle sensitive audio, radar, and potentially classified information, creating compliance burdens around storage, access controls, and information release.
Key Issues
The Core Tension
The central dilemma is between maximizing reporting (which requires strong non‑punitive protections, low friction intake, and privacy safeguards) and ensuring actionable national security and safety analysis (which requires broad interagency access, data sharing, and sometimes classification). Encouraging candid civilian reporting while simultaneously routing that information to defense and intelligence communities creates unavoidable conflicts over confidentiality, evidence use, and resource prioritization.
The Act tries to thread a narrow needle: it encourages broad, non‑punitive reporting while simultaneously requiring robust interagency sharing with defense and intelligence elements. That combination raises operational and legal questions.
For instance, the statute mandates sharing reports with DoD’s All‑Domain Anomaly Resolution Office but also forbids use of reports in enforcement—how will agencies reconcile national security classification requirements with the FAA’s promise of non‑punitive handling? Practical problems include establishing clear access controls, redaction rules, and retention schedules for archived pilot‑controller communications and radar data.
The statutory definitions are deliberately expansive and operationally ambiguous. "Unidentified anomalous phenomena" and "transmedium" capture a wide range of events from sensor errors and misidentified conventional craft to genuinely unexplained behavior; absent a standardized taxonomy or triage protocol, the FAA and partner agencies risk flooding analytical queues with low‑value reports. The bill’s protections against reprisals and for medical/airmen certificates are strong in principle but lack an explicit enforcement or remedial mechanism for victims of retaliation, potentially leaving affected individuals to pursue existing labor or administrative remedies that can be slow or uneven.
Finally, the choice between leveraging the ASRP and building a separate system presents a policy tradeoff: ASRP carries an existing non‑punitive framework but may need technical changes to capture kinematics, while a new dedicated system can be tailored to UAP reporting but must recreate trust and legal protections that make reporting safe for aviation personnel.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.