The bill requires the Federal Aviation Administration to deliver an action plan—and publish it publicly—outlining how the agency will advance deployment of the Airborne Collision Avoidance System‑X family (ACAS‑X and its variants). Congress gives the FAA 180 days from enactment to produce the plan and requires a follow‑up briefing within 30 days of submission.
The mandated plan must include a strategic roadmap for adoption, an assessment of research, testing, standards, and funding needs for certification, explicit stakeholder engagement (from operators to labor and manufacturers), international coordination for harmonized certification, and analysis of ADS‑B In/Out interoperability. The bill also permits the FAA to begin implementing the plan and to recommend additional administrative or legislative steps.
At a Glance
What It Does
The bill directs the FAA to submit and publicly post an action plan within 180 days describing steps, funding needs, and stakeholder engagement required to deploy ACAS‑X and its variants across the national airspace. It specifies content requirements (roadmap, R&D and testing, standards, interoperability, safety assessment, and international coordination) and requires a congressional briefing 30 days after submission.
Who It Affects
Air carriers, general aviation and rotorcraft operators, avionics and aircraft manufacturers, pilot labor organizations, and the FAA’s certification and standards teams are directly affected. Foreign civil aviation authorities are implicated through requested harmonization efforts.
Why It Matters
ACAS‑X represents the next generation of onboard collision avoidance; the bill pushes the FAA to translate technology advances into a practical deployment timeline, to surface funding needs, and to coordinate stakeholders and international partners—potentially speeding adoption and shaping certification requirements industry‑wide.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill tasks the FAA with producing a concrete action plan focused on deploying ACAS‑X (and named variants) into the U.S. national airspace. That plan must set out a strategic roadmap explaining how operators could move from current equipment to ACAS‑X—identifying stages such as prototype testing, certification milestones, retrofit pathways, and recommended timelines.
The FAA must also publish the plan shortly after it sends it to Congress, making the agency’s approach visible to industry and foreign regulators.
Beyond timelines, the FAA must inventory the research, development, testing, evaluation, and standards work remaining to secure certification of ACAS‑X systems and estimate associated funding or resource needs. The bill requires the FAA to detail how it will engage a broad set of stakeholders—airframe and avionics manufacturers, airline and general aviation operators, pilot unions and their largest representatives, and external safety experts—to surface technical, operational, and human‑factor issues before wide deployment.The statute explicitly asks the FAA to coordinate with foreign civil aviation authorities so that certification and interoperability requirements align internationally, reducing the risk of divergent standards that could complicate cross‑border fleet operations.
It also directs the FAA to analyze how ACAS‑X will interact with existing surveillance technologies—specifically ADS‑B Out and ADS‑B In—so operators that already rely on those systems understand compatibility and upgrade implications.Finally, the bill gives the FAA authority to act on the plan where appropriate and requires a briefing to the two congressional committees within 30 days of submission. While it prescribes content and deadlines, the measure stops short of directing specific regulatory actions or funding appropriations; it is primarily a mandate for planning, analysis, and stakeholder coordination to prepare the ground for later certification and deployment steps.
The Five Things You Need to Know
The FAA must deliver an ACAS‑X action plan to Congress within 180 days of enactment and publish it publicly within 10 days after submission.
The mandated plan must quantify R&D, testing, standards development, and funding or resource needs necessary to certify ACAS‑X variants.
The bill lists a detailed stakeholder roster the FAA must engage, including avionics and airframe manufacturers, general aviation organizations, and the principal certified collective bargaining representative for airline pilots.
The FAA must describe ACAS‑X interoperability with ADS‑B Out/ADS‑B In equipment and lay out considerations for rotorcraft and other operator classes.
The Administrator may begin implementing the plan and must brief the House Transportation and Infrastructure Committee and the Senate Commerce Committee within 30 days of submitting the plan.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Provides the Act’s name: the Next‑Gen Collision Avoidance Act. This is purely titular but signals congressional intent to prioritize collision‑avoidance modernization.
Deadline and public posting requirement
Requires the FAA Administrator to submit an action plan within 180 days of enactment and to publish that plan in a publicly available format within 10 days of submission. Practically, that forces an internal timeline inside the agency and ensures industry, labor, and foreign partners can review the agency’s approach immediately after Congress receives it.
Required plan contents
Enumerates the plan’s components: a strategic deployment roadmap; identification of actions and funding for R&D, testing, evaluation, and standards; a prescribed stakeholder engagement list; international harmonization efforts; ADS‑B interoperability analysis; a safety benefits assessment; and any administrative or legislative recommendations. Each subpart organizes the FAA’s analytic work and makes those analyses explicit deliverables, not optional studies.
Implementation authority and congressional briefing
Grants the FAA discretion to act on the plan where appropriate and mandates a briefing to the two specified congressional committees within 30 days of submitting the plan. The implementation language gives the agency latitude to begin limited actions without additional statutory direction, while the briefing provides a near‑term accountability checkpoint for Congress.
Definitions and scope
Defines key terms used in the section—ADS‑B In, ADS‑B Out, appropriate congressional committees, FAA, and rotorcraft—by cross‑reference to existing CFR provisions. Those definitions clarify technical scope (for example, tying ADS‑B references to 14 CFR §§91.225/91.227) and ensure the plan addresses rotorcraft as well as fixed‑wing operations.
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
- Airlines and large commercial operators — receive a government‑led roadmap that can reduce certification uncertainty and coordinate retrofit pathways, helping fleet planning and capital allocation.
- Avionics and aircraft manufacturers — gain clarity about certification priorities and international harmonization that can guide product development and potential early‑market opportunities.
- General aviation and rotorcraft operators — get specific attention through required ADS‑B and rotorcraft considerations, which can surface tailored deployment paths rather than one‑size‑fits‑all mandates.
- Safety researchers and independent aviation experts — obtain a public plan and mandated engagement opportunities, giving them access to FAA analysis and chances to influence testing and human‑factors work.
Who Bears the Cost
- FAA — must marshal staff time and technical resources to produce a substantive plan and to conduct stakeholder and international engagement; the agency may need congressional appropriations for any implementation steps.
- Aircraft operators (airlines, GA, rotorcraft) — could face retrofit or equipment upgrade costs if the roadmap leads to recommendations or mandates for ACAS‑X equipage without targeted funding assistance.
- Avionics manufacturers — will need to invest in certification testing, product development, and documentation to align with FAA and international standards identified in the plan.
- Pilot labor organizations and training providers — may incur costs developing training curricula and operational procedures if operators move to adopt ACAS‑X, including simulator time and recurrent training.
Key Issues
The Core Tension
The central dilemma is speed versus readiness: Congress pushes the FAA to accelerate planning and stakeholder coordination to get ACAS‑X into service quickly, but rapid deployment risks incomplete certification work, unclear funding paths, and interoperability gaps that could impose heavy retrofit and training costs on operators or produce uneven safety outcomes.
The bill mandates robust analysis but does not appropriate money; the FAA may identify funding needs in the plan, but Congress would still have to allocate any new resources. That separation creates a common implementation trap: a detailed roadmap that cannot be executed without subsequent budgetary decisions.
The 180‑day turnaround is aggressive relative to the technical and international coordination work required for avionics certification, raising the risk the FAA will produce a preliminary plan rather than a fully operational roadmap.
Technical interoperability and certification work remain unresolved in statute. The bill requires analysis of ADS‑B In/Out interactions and rotorcraft considerations but does not specify whether the FAA should pursue rulemaking, amended advisory circulars, or consensus standards via RTCA/ICAO processes.
That ambiguity affects timelines and industry costs. International harmonization is necessary but politically and technically complex; relying on foreign authorities to align certification requirements could slow cross‑border operations or create interim incompatibilities.
Finally, the bill does not address liability, operational procedures for advisory versus resolution advisories, or how ACAS‑X advisories would integrate into existing air traffic management procedures—issues that materially affect operator adoption and training burdens.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.