Bill brief/S2503/119th Congress
Most aircraft would need new traffic-warning equipment by 2031
Official title
ROTOR Act
S.2503, the ROTOR Act, is a bill to require most aircraft that already use ADS‑B Out tracking to also carry and use ADS‑B In equipment. It narrows when government aircraft can turn off public tracking, increases data sharing and audits for military operations, and orders broad safety reviews of airspace around busy airports. The bill has been reported out of the Senate Commerce Committee with an amendment.
Bill
S2503
Introduced
Date not available
Sponsor
Sponsor not listed
Chamber
Senate
What the bill does
What this bill does
The bill requires the Federal Aviation Administration (FAA) to issue a rule so that, by the end of 2031, almost all aircraft that must broadcast their position using ADS‑B Out must also be able to receive traffic information using ADS‑B In. The FAA must set performance standards for this equipment, allow lower‑cost options for smaller general aviation planes, and give technical guidance so operators know what systems qualify. Operators can request up to one extra year to comply in limited cases if needed to avoid major disruption and if they have a clean safety record.
The bill sharply narrows when government aircraft can claim a “sensitive government mission” exception that lets them turn off ADS‑B Out broadcasting. Training, practice flights, and flights of officials below Cabinet level would no longer qualify. Agencies that use these exceptions must report regularly to the FAA, and the FAA must report to Congress, flagging heavy users of the exceptions. The Department of Transportation’s Inspector General must audit how the FAA oversees these exceptions every year.
The FAA must also use ADS‑B technology and other tools to update aircraft separation standards and related air traffic controller procedures, and then retrain controllers. The bill directs the FAA to create an action plan to deploy the next‑generation Airborne Collision Avoidance System (ACAS‑X) and to work with industry, labor, the military, and foreign aviation regulators on standards and rollout. It also tasks an advisory committee to study whether aircraft in Class D airspace should be required to carry ADS‑B Out and ADS‑B In.
The bill orders the Army Inspector General to audit Army helicopter operations in the National Capital Region, including training, coordination with the FAA, compliance with policies, and maintenance of UH‑60 Black Hawk helicopters. The audit results must be shared with Congress and, with limited national security redactions, with the public, with interim progress briefings every 6 months. The FAA must create an Office of FAA‑DOD Coordination to oversee how military and civil aviation share airspace and safety data.
That office must conduct detailed safety reviews of military, law enforcement, emergency, and civil helicopter, powered‑lift, fixed‑wing, and drone operations around Washington, DC’s Ronald Reagan Washington National Airport and then around other busy Class B, C, and certain Class D airports. These reviews use specific risk factors and must result in reports to Congress with findings and any needed corrective actions.
Finally, the Administrator must sign data‑sharing agreements with the Army and other military departments so FAA and the military can exchange aviation safety information, and a prior law about ADS‑B equipment on some Department of Defense aircraft is repealed.
Key provisions
- The FAA would have to write a final rule within 2 years. That rule would require ADS-B In on every aircraft that already must carry ADS-B Out, except unmanned aircraft, unless air traffic control allows otherwise.
- The new ADS-B In rule would start no later than 60 days after it is published. All covered aircraft would have to comply by December 31, 2031, though some aircraft already in service could get a one-year extension under strict rules.
- Pilots would need equipment that can show nearby traffic and give alerts. The FAA would set those standards for in-flight and airport-surface warnings and approve lower-cost options for general aviation aircraft under 12,500 pounds.
- Government aircraft would have fewer ways to turn off public tracking. Training flights, practice flights, and flights for federal officials below Cabinet level could no longer use the sensitive government mission exception.
- Agencies would have to report every time they shut off ADS-B Out under the exception. Federal, state, local, and Tribal agencies would send quarterly flight lists to the FAA, and the FAA would send Congress summary reports twice a year plus special alerts.
- The Government Accountability Office would check whether agencies are following the new exception rules. It would compare use before and after the changes, and the FAA would then decide if agencies that break the rules can keep using the exception.
- Congress would get yearly audits of how the FAA oversees flights that use the ADS-B exception. The Department of Transportation inspector general would do those audits and brief Congress each year.
- The FAA would have to change how it separates aircraft and trains controllers. It would update major FAA orders, including Order 7110.65, to use ADS-B and other tools for both safety and efficiency.
- The FAA would need a national rollout plan for ACAS-X, the next collision-avoidance system. The plan would have to cover research, funding, certification, outside input, and work with other countries.
- Army helicopter operations around Washington, DC, would face a detailed audit. The Army inspector general would review ADS-B Out use, UH-60 Black Hawk maintenance, and compliance with a 2021 Pentagon-Reagan National helicopter agreement, with public release limited only by national security concerns and interim briefings every 6 months.
Impact
Why it matters—and who it affects
Why it matters
The bill aims to increase situational awareness for pilots and air traffic controllers by making ADS‑B In common across much of the U.S. fleet. When aircraft can both broadcast and receive position and traffic information, they can better see nearby traffic on cockpit displays, which may reduce the risk of midair conflicts and runway incursions. Updated separation standards and controller training built around these tools could also affect how efficiently busy airspace and airport surfaces are managed. Tightening the rules on when government aircraft can turn off ADS‑B broadcasting may increase transparency for other airspace users and for the public, while still allowing exceptions for truly sensitive missions. Regular reporting, audits, and new safety reviews focused on military and rotorcraft operations near large commercial airports respond to concerns about “loss of separation” incidents and complex mixed traffic. The required safety data‑sharing between the FAA and the Department of Defense could change how quickly risks are spotted and addressed, but the exact safety impact will depend on how these new offices, rules, and technologies are implemented in practice. For aircraft owners and operators, especially in general aviation, the ADS‑B In mandate could mean new equipment costs, installation downtime, and training needs. The bill attempts to address this by allowing lower‑cost alternatives for smaller aircraft, phasing in deadlines, and allowing limited extensions. However, the overall cost and operational impact on different types of operators will depend on the final FAA rules and available technology options.
Who it affects
This bill mainly affects aircraft owners and operators, especially airlines, cargo carriers, and smaller general aviation pilots who may need new equipment. It also directly affects military units, police and emergency aviation teams, and other government agencies that sometimes turn off tracking signals. Air traffic controllers and the FAA would have new rulemaking, training, reporting, and review duties. People who fly near busy airports could also be affected if routes or operating rules change after the safety reviews.
The debate
The case for it—and the concerns
These are the main arguments surrounding the bill, not Modern Action’s position.
Arguments in support
- Making ADS‑B In as common as ADS‑B Out could give pilots in both commercial and general aviation aircraft much better real‑time awareness of nearby traffic, potentially reducing midair and ground‑movement risks.
- Narrowing the “sensitive government mission” exception and adding reporting, audits, and GAO review may limit overuse of tracking exemptions and improve transparency and safety oversight for government and military flights.
- Creating a dedicated FAA‑DOD coordination office and formal data‑sharing agreements could help civil and military aviation share risk information more quickly and consistently, improving how mixed traffic is managed near busy airports.
- The phased deadlines, allowance for low‑cost alternatives in small aircraft, and limited extension process may help reduce financial and operational burdens while still moving the fleet toward common safety technology.
- Focused safety reviews around Reagan National and other Class B, C, and certain Class D airports use defined risk metrics and broad consultation, which may help target fixes where complex traffic patterns create the greatest hazards.
- An action plan for ACAS‑X and updated separation standards could position the U.S. to use newer collision‑avoidance and surveillance technologies more fully, potentially enhancing both safety and airspace capacity over time.
Concerns and tradeoffs
- Requiring ADS‑B In on all affected aircraft by a fixed date may impose significant costs on airlines, cargo carriers, and especially small general aviation owners, which some may view as too heavy a burden relative to the expected safety gains.
- Narrowing the “sensitive government mission” exception and adding detailed reporting could be seen as limiting flexibility for law enforcement, homeland security, and defense missions that prefer to minimize public visibility, even when not at Cabinet‑level.
- The bill adds multiple new reporting, briefing, and audit requirements for the FAA, the Army, GAO, and the DOT Inspector General, which some may view as adding bureaucracy and diverting resources from direct safety work.
- Creating a new FAA office and conducting extensive nationwide safety reviews of airspace around many airports could require additional staffing and funding, and might lead to route changes or restrictions that some operators view as disruptive.
- Some stakeholders may argue that technology mandates should be driven by cost‑benefit analyses and voluntary adoption rather than a statutory presumption that ADS‑B In is cost‑beneficial.
- Increased data‑sharing between the FAA and military services may raise concerns about handling of sensitive operational information, even with safeguards and national security exceptions in place.
- The bill does not itself set exact technical specifications for ADS‑B In; it instead requires the FAA to define performance standards and then presumes, by law, that ADS‑B In is cost‑beneficial unless there is “clear and compelling” evidence otherwise, which is an unusual statutory direction for a safety technology.
- Although the bill focuses on rotorcraft in its title, many provisions apply broadly to fixed‑wing aircraft, powered‑lift, and, in some reviews, unmanned aircraft systems across the national airspace system.
Check the details
Key facts
- Requires the FAA to issue a final rule within 2 years that mandates ADS‑B In equipment on all aircraft that are already required to have ADS‑B Out (with unmanned aircraft excluded), unless air traffic control authorizes otherwise.
- Sets an effective date for the ADS‑B In rule no later than 60 days after publication, and a fleet‑wide equipage deadline of December 31, 2031, with possible one‑year extensions for some in‑service aircraft under strict conditions.
- Directs the FAA to define performance standards for ADS‑B In, including visual and aural traffic advisories in the air and on the airport surface, and to approve lower‑cost alternative technologies for lighter general aviation aircraft under 12,500 pounds.
- Narrows the regulatory definition of “sensitive government mission” so that training and proficiency flights and flights of non‑Cabinet‑level Federal officials cannot use the ADS‑B Out exception.
- Requires Federal, State, local, and Tribal agencies using the “sensitive government mission” exception to file quarterly reports to the FAA listing each flight where ADS‑B Out was turned off, and requires the FAA to send semiannual aggregate reports and special notifications to Congress.
- Orders the Government Accountability Office to review and compare use of the ADS‑B exception before and after the new rules and to report on whether agencies are complying; the FAA must then decide whether non‑compliant users may continue using the exception.
- Requires the Department of Transportation Inspector General to conduct annual audits of FAA oversight of all ADS‑B exception operations and to brief Congress each year.
- Directs the FAA to update separation standards and revise key FAA Orders (including 7110.65) to use ADS‑B and other technologies for safety and efficiency, and to update initial and recurrent controller training accordingly.
Legislative record
How far the bill has moved
On the House floor
At the conclusion of debate, the Yeas and Nays were demanded and ordered. Pursuant to the provisions of clause 8, rule XX, the Chair announced that further proceedings on the motion would be postponed. · Feb 23, 2026
- Introduced
- Senate Committee
- Senate Floor Vote
- Passed Senate
- 5House Review
- 6Passed Both Chambers
- 7Signed into Law
Contact Congress
Send a message about this bill
Choose your position, add what matters to you, and send a message to the officials who can act on this bill.
Contact your representative