The ROTOR Act requires any aircraft already subject to the ADS‑B Out mandate to install and operate ADS‑B In equipment that gives pilots traffic awareness and alerts, with a statutory fleetwide compliance date of December 31, 2031. The bill also narrows the existing regulatory exception that lets some government and military flights turn off ADS‑B Out transmissions, excludes routine training and lower‑level official travel from that exception, and directs the FAA to promulgate updated rules and memoranda of agreement.
Beyond equipage, the bill layers transparency and oversight: agencies that use ADS‑B Out exceptions must file detailed, periodic reports; the Government Accountability Office and Inspector General offices must review exception use and FAA oversight; the FAA must create or designate an FAA–DOD coordination office and complete targeted safety reviews of airport airspace (starting with Reagan National); and the bill requires MOUs with military departments to enable safety data sharing. It also repeals the 2019 NDAA carve‑out for certain DOD aircraft ADS‑B requirements.
At a Glance
What It Does
Requires aircraft already required to broadcast ADS‑B Out to be equipped with ADS‑B In and operating it (deadline: Dec. 31, 2031), establishes performance standards and low‑cost alternatives for light aircraft, tightens the ADS‑B Out ‘sensitive government mission’ exception, and creates multiple reporting, audit, and safety‑review obligations for FAA and Federal agencies.
Who It Affects
Commercial transport operators, rotorcraft and general aviation owners/operators whose aircraft are subject to 14 C.F.R. §91.225; avionics and aircraft manufacturers; the Department of Defense and other Federal agencies that previously relied on ADS‑B Out exceptions; and the FAA’s Air Traffic Organization and oversight bodies.
Why It Matters
The bill shifts the baseline from one‑way ADS‑B surveillance toward two‑way airborne situational awareness, changes how and when military/government flights may disable broadcasts, and forces greater transparency and interagency data sharing—altering equipage economics, operational practices, and FAA oversight priorities.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The ROTOR Act builds on the existing ADS‑B Out regulatory regime by making ADS‑B In a mandatory operational capability for any aircraft already required to have ADS‑B Out. The FAA must issue a final rule within two years and set a compliance deadline of December 31, 2031; the bill requires the rule to include minimum performance requirements so ADS‑B In provides traffic advisories and alerting both airborne and on the airport surface.
For small aircraft (max takeoff weight under 12,500 lbs operating under part 91) the FAA must certify acceptable low‑cost alternatives — for example portable receivers or EFB displays — provided they meet performance criteria and do not impair airworthiness or other avionics.
To limit blind spots caused by intentional ADS‑B Out shutdowns, the bill narrows the phrase "sensitive government mission" in 14 C.F.R. §91.225(f)(1) so that routine training, proficiency flights, and travel by Federal officials below Cabinet level do not qualify. The FAA has one year to revise §91.225(f), update memoranda of agreement with other agencies, and then must collect quarterly attestations and detailed flight‑level reports from any agency that still uses an exception.
The FAA must also submit biannual reports to Congress, and GAO will analyze exception usage and trends within two years.Oversight is reinforced by a sequence of audits and enforcement steps: the Comptroller General will compare exception use before and after the rule change; the DOT Inspector General must begin annual audits of FAA oversight starting three years after enactment; and the Army Inspector General must initiate a separate audit of Army rotorcraft ADS‑B Out practices within 60 days. The FAA must also stand up an Office of FAA–DOD Coordination to manage military‑civil flight interactions and lead prioritized safety reviews of airport airspace — Reagan National gets the first 120‑day review window — and the Secretary of Transportation must pursue MOUs with military services to enable safety information sharing.Operational changes beyond equipage include FAA rulemaking on separation standards that exploit ADS‑B capabilities, controller training updates, and an action plan for ACAS‑X deployment.
The bill contemplates use of negotiated rulemaking or stakeholder consultation for standards, allows phased retrofit relief in limited circumstances, and includes a presumption that ADS‑B In is cost‑beneficial absent strong contrary evidence. Finally, the text repeals the 2019 statutory provision that had created certain ADS‑B exemptions for DOD aircraft.
The Five Things You Need to Know
The bill sets December 31, 2031 as the deadline for aircraft already required to have ADS‑B Out to be equipped with and operating ADS‑B In, with the FAA’s final rule effective no later than 60 days after publication.
It narrowly construes the ADS‑B Out ‘sensitive government mission’ exception so that training, proficiency flights, and flights by Federal officials below Cabinet level are not covered, and directs the FAA to revise §91.225(f) within one year.
Federal, State, local, and Tribal agencies that use ADS‑B Out exceptions must submit quarterly attestations plus a flight‑level list (airport, airspace, date, time, duration, mission type); the FAA must report to Congress biannually and issue special notifications if an agency uses an exception 5+ times in a month.
The Comptroller General must review exception utilization and report within two years; the DOT Inspector General must begin annual audits of FAA oversight of exception use starting three years after enactment, and the Army IG must start an Army‑specific audit within 60 days.
The FAA must create an Office of FAA–DOD Coordination, conduct prioritized safety reviews (Reagan National review to start within 30 days and finish in 120 days), and execute MOUs with military departments to enable safety data sharing.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Names the measure the “Rotorcraft Operations Transparency and Oversight Reform Act” or the “ROTOR Act.” This is the formal label and has no operative effect beyond identifying the legislation.
Definitions
Provides definitional anchors used throughout the bill: Administrator/FAA, ADS‑B In and ADS‑B Out, affected aircraft (those governed by §91.225), rotorcraft, powered‑lift, transport airplane, and unmanned aircraft system. These definitions matter because they limit who must comply (for example, excluding UAS from the ADS‑B In mandate) and tie regulatory references to existing CFR sections and U.S.C. provisions.
Tightening the ADS‑B Out exception for 'sensitive government missions'
Directs the FAA to construe §91.225(f)(1)'s “sensitive government mission” narrowly, explicitly excluding training flights, proficiency flights, and flights by Federal officials below Cabinet level. The Administrator must revise the regulation and any FAA MOUs within one year, or report to Congress explaining the delay. The bill also triggers a GAO review of exception utilization (compare before/after), requires FAA determinations about agencies’ continued use of exceptions following the GAO report, and establishes quarterly agency reporting and FAA biannual reporting to Congress—mechanics designed to surface routinized or unsafe use of shutdowns.
ADS‑B In requirement, performance standards, alternatives, and implementation mechanics
Imposes a rulemaking obligation requiring ADS‑B In for any aircraft already required to have ADS‑B Out, with a final rule within two years and fleet equipage by Dec. 31, 2031. The FAA must set performance standards (visual/aural advisories, surface and airborne alerting), identify acceptable low‑cost alternatives for <12,500 lb part‑91 aircraft (including portable receivers/EFB displays), and publish guidance. The text authorizes negotiated rulemaking with a wide stakeholder list (air carriers, OEMs, avionics, pilot and ATC labor, general aviation groups), or at minimum stakeholder consultation if negotiated rulemaking is not used. It also provides a limited phased retrofit process allowing operators to apply for up to one additional year past the deadline where necessary to avoid significant transportation disruption, establishes a presumption that ADS‑B In is cost‑beneficial, and requires FAA briefings to Congress every 90 days while rulemaking and implementation proceed.
Army Inspector General audit
Directs the Army Inspector General to begin an audit within 60 days assessing Army coordination with FAA, pilot training and qualification standards, Army ADS‑B Out policy and usage, maintenance and calibration practices (e.g., UH‑60 systems), compliance with a specific 2021 Letter of Agreement, and loss‑of‑separation incidents in the NCR. The audit must be transmitted and publicly released to committee(s) without redactions except for national security reasons, and interim briefings to congressional committees are required every 180 days until conclusion.
FAA–DOD coordination office and prioritized safety reviews of airspace
Requires the FAA to establish or designate an Office of FAA‑DOD Coordination to manage military‑civil airspace interaction, consider consolidating safety data, and lead safety reviews. The bill requires an immediate safety review of military, law‑enforcement, rotorcraft, powered‑lift, fixed‑wing, and UAS operations affecting operations at Reagan National (initiate within 30 days, complete within 120 days) and staged reviews of Class B, C and certain Class D airports using explicit risk criteria (radar presence, OPSNET ops, TCAS RA rates, VFR corridors, helicopter corridors). Each review must include consultations with DOD, carriers, labor, emergency response, and produce reports to Congress with findings, corrective actions, and recommendations.
MOUs to share safety data with military departments
Mandates MOUs between FAA and the Army within 60 days, and with Navy, Air Force, and Coast Guard within 90 days, to enable sharing of military aviation safety information with FAA systems. The purpose is to close information gaps that hinder civil‑military safety analysis. The Administrator must notify key congressional committees within 7 days of entering each MOU.
Repeal of 2019 NDAA ADS‑B provision
Repeals section 1046 of the John S. McCain NDAA for FY2019 (49 U.S.C. 40101 note), removing the earlier statutory language that had provided certain DOD exceptions or guidance concerning ADS‑B equipage. This restores Congress’s stated intent to fold DOD considerations back under the revised regulatory and oversight framework created by the bill.
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
- Commercial airline operators and passengers — improved airborne and surface traffic awareness from widespread ADS‑B In and associated separation standard changes should reduce near‑midair conflicts and runway/surface incursions involving transport aircraft.
- Air traffic controllers and the FAA Air Traffic Organization — more consistent broadcast traffic data and ACAS‑X/ADS‑B‑enabled procedures create tools for efficiency and safety, and the bill funds clearer training and updated orders to use those tools.
- General aviation pilots flying in busy airspace — access to traffic advisories, including on small‑aircraft displays or portable receivers (if approved), improves situational awareness when operating near busy airports or in mixed traffic environments.
- Aviation safety analysts and oversight committees — mandatory reporting, GAO and IG reviews, and enhanced civil–military data sharing will provide richer datasets for root‑cause analysis and safety improvements.
- Avionics and aircraft equipment manufacturers — a regulatory mandate and FAA performance standards create a clear market for ADS‑B In hardware, portable receivers, EFB integration, and ACAS‑X upgrades.
Who Bears the Cost
- Aircraft owners and operators — primary equipage costs fall on operators, especially regional carriers, rotorcraft operators, and private owners of older aircraft who must install ADS‑B In or approved alternatives before the 2031 deadline.
- Small general aviation owners (part‑91, <12,500 lb) — even with low‑cost alternative pathways, many owners face outlays for portable receivers, EFB upgrades, or panel modifications that may be significant relative to aircraft value.
- The Department of Defense and other government operators — narrowed ADS‑B Out exceptions, new reporting requirements, MOUs, and increased oversight (including Army audits) impose administrative burdens and potential operational constraints for sensitive missions.
- The FAA — rulemaking, negotiated rulemaking facilitation, standing up the FAA–DOD Coordination Office, conducting prioritized airspace reviews, updating orders and controller training, and expanded oversight all require staffing and budget resources.
- Avionics installers and maintenance facilities — a surge in retrofit demand will strain available installer capacity and may create scheduling bottlenecks, particularly near the compliance deadline and for complex rotorcraft installations.
Key Issues
The Core Tension
The central dilemma is balancing aviation safety and system transparency (the public and commercial interest in consistent airborne broadcasts and oversight) against operational security, mission flexibility, and cost burdens (the military and some government operators’ need to conceal movements and the financial strain on small aircraft owners). The bill favors safety/transparency through reporting and equipage mandates but leaves unresolved how much classified or security‑sensitive material will be withheld and who ultimately pays for rapid fleet modernization.
This bill pushes hard on two levers at once: mandatory equipage for situational awareness and much tighter transparency around when broadcasts are turned off. That combination exposes a few implementation wrinkles.
First, equipage costs and installation logistics for thousands of small and specialized aircraft could create capacity bottlenecks at installers and manufacturers; the bill provides a limited phased retrofit pathway and asks for low‑cost alternatives for light aircraft, but success depends on credible performance standards and timely certification of those alternatives. Second, the bill increases reporting and oversight of government and military flights, yet national security classification and operational security concerns will constrain what data the military is willing to share; the MOUs and the Army IG’s and GAO’s reviews will reveal how much can be shared in practice and how much must remain protected.
Second, narrowing the “sensitive government mission” exception improves transparency but creates operational tension: some DOD and law‑enforcement activities legitimately require non‑broadcast modes for safety or security, and the bill does allow continued exceptions where justified, subject to reporting. Determining what is "clearly and compellingly" necessary will test FAA‑DOD coordination and likely produce disputes about operational autonomy versus civil safety.
Finally, the bill presumes ADS‑B In is cost‑beneficial; that presumption places a thumb on the regulatory scale in favor of equipage and may constrain the FAA’s willingness to weigh lifecycle cost impacts for owners of older or unusual airframes.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.