A substantive revision. v3 refines the definition of "sensitive government mission" for ADS-B Out exceptions, adds new notification requirements for military flights in Class B airspace, and introduces a new section to formally treat the DOD-FAA Memorandum of Agreement regarding ADS-B equipment. It also expands eligibility for alternative ADS-B In equipment to qualifying military aircraft and mandates new safety information sharing.
ROTOR Act
- Sponsor
- Sen. Cruz, Ted [R-TX]
- Committees
- Commerce, Science, and Transportation Committee (primary)
- Last action
- Feb 24, 2026
Bottom line
The ROTOR Act significantly enhances aviation safety by mandating advanced collision avoidance technology for most aircraft and increasing transparency and oversight of government flight operations, particularly in sensitive airspace.
What it actually does
This bill mandates that most aircraft currently equipped with Automatic Dependent Surveillance-Broadcast Out (ADS-B Out) also install and operate with ADS-B In technology by December 31, 2031, to enhance aviation safety and situational awareness. It also tightens exceptions for government aircraft not transmitting ADS-B Out, particularly for 'sensitive government missions,' and requires increased reporting and oversight of such exceptions. Furthermore, the bill establishes an FAA-DOD coordination office, mandates safety reviews of airspace around key airports, and requires information sharing agreements between the FAA and military branches.
Proponents argue
Supporters argue that mandating ADS-B In will dramatically improve aviation safety by providing pilots with real-time awareness of nearby air traffic, thereby reducing the risk of mid-air collisions. They also contend that increased transparency for government flights, especially in congested airspace like the National Capital Region, is crucial for public safety and accountability. The bill's provisions for low-cost alternatives and phased implementation aim to mitigate burdens on smaller operators.
Opponents contend
Critics, particularly from some government agencies, may raise concerns about the potential impact of increased transparency requirements on sensitive or classified missions, arguing it could compromise national security operations. Some general aviation groups might express reservations about the financial burden of mandating new avionics, even with provisions for low-cost alternatives, and the timeline for compliance.
The bill is moderately technical but its core provisions are understandable, allowing an informed reader to grasp its implications within the typical legislative review timeframe.
Section 3(a)
ADS-B Out Reforms and Sensitive Government Missions
This provision narrowly construes the 'sensitive government mission' exception for aircraft not transmitting ADS-B Out, explicitly excluding routine, non-classified, or proficiency flights, and flights by officials below Cabinet Member rank. It requires operating agencies to notify Air Traffic Control when not transmitting ADS-B Out during such missions and to report monthly to Congress on sensitive government missions conducted within Class B airspace. The FAA is mandated to revise regulations and agreements within one year to comply.
Supporters argue
Proponents argue this reform enhances aviation safety by reducing the number of 'dark' aircraft in the national airspace, especially in congested areas. It addresses concerns about government aircraft operating without full visibility, which can pose risks to commercial and general aviation. The reporting requirements ensure accountability and allow for better oversight of these exceptions.
Critics contend
Some government agencies might argue that a narrow definition of 'sensitive government mission' and increased reporting could compromise operational security or flexibility for critical national security or law enforcement activities. They might contend that detailed reporting could inadvertently reveal sensitive operational patterns.
Tradeoffs
This provision balances the need for aviation safety and transparency with the operational requirements and potential security concerns of government agencies conducting sensitive missions. It aims to prevent the misuse of exceptions while acknowledging legitimate needs for non-disclosure in specific, high-stakes scenarios.
Section 4(a)-(f)
Mandatory ADS-B In Equipage
This section requires all aircraft (except unmanned) that are already equipped with ADS-B Out to also be equipped with and operate ADS-B In equipment. The FAA must issue a final rule within two years, with a compliance deadline of December 31, 2031. The rule must establish performance standards for ADS-B In, including visual and aural traffic advisories, and provide for acceptable alternative equipment, particularly low-cost options for aircraft under 12,500 pounds and qualifying military aircraft. A process for a one-year compliance extension is also included.
Section 4(g)
New Separation Standards and Controller Training
This section requires the FAA Administrator to issue a proposed rulemaking within 18 months of the ADS-B In rule's effective date to establish new separation standards that leverage ADS-B Out and In capabilities. It also mandates revisions to FAA Orders and air traffic controller training within one year of the ADS-B In compliance deadline to ensure controllers are proficient in applying these new standards and procedures, considering human factors and surface movement applications.
Section 6
Inspector General of the Army Audit
This section mandates the Inspector General of the Army to conduct an audit within 60 days of enactment. The audit will evaluate the Army's coordination with the FAA, pilot training and qualification standards, and adherence to policy, regulation, and law regarding ADS-B Out usage. It specifically focuses on operations in the National Capital Region (NCR), maintenance protocols for UH-60 Black Hawk helicopters, compliance with a 2021 Letter of Agreement, and reviews of loss of separation incidents. The audit results, without redactions (except for national security), must be publicly disclosed and reported to Congress.
Section 7
FAA-DOD Coordination and Airspace Safety Reviews
This section establishes an 'Office of FAA-DOD Coordination' within the FAA to manage military airspace usage and coordinate with FAA lines of business. It mandates safety reviews of all military, law enforcement, and civilian rotary wing, powered lift, fixed wing, and unmanned aircraft system operations in the Washington D.C. Metropolitan Area Special Flight Rules Area (including Ronald Reagan Washington National Airport) and other high-risk Class B, C, and D airports. These reviews will assess risks to commercial transport airplane operations, analyze air traffic management, evaluate coordination levels, and review incident data. Reports with findings and recommendations must be submitted to Congress.
Section 8
FAA-DOD Safety Information Sharing MOUs
This section requires the Administrator to enter into Memoranda of Understanding (MOUs) with the Department of the Army within 60 days, and with the Departments of the Navy, Air Force, and the Coast Guard within 90 days. These MOUs will facilitate the sharing of aviation safety information between the military branches' Safety Management Information Systems and the FAA's various safety analysis systems. The goal is to improve communication, analysis of impacts on civil aviation, and risk mitigation in the national airspace system. Congress must be notified within 7 days of any MOU being signed.
Narrows the definition of 'sensitive government mission' for ADS-B Out exceptions, specifically excluding routine, non-classified, or proficiency flights, and flights by Federal officials below the rank of Cabinet Member or Chairman of the Joint Chiefs of Staff.
Section 3(a)(1)(A)
Why it matters:This is standard legislative practice for modifying existing regulations, but the specific exclusions are significant and could be overlooked by a casual reader focusing on the broader ADS-B mandates.
Case for: Proponents argue this specificity prevents the broad or casual use of the 'sensitive government mission' exception, ensuring that most government flights contribute to overall airspace transparency and safety. It clarifies legislative intent and limits discretion.
Case against: Some government agencies might argue that such a precise, narrow definition could inadvertently restrict legitimate, albeit non-classified, operational flexibility or training requirements that benefit national security or public safety missions.
Estimated impact: Significantly reduces the number of government flights that can legally operate without transmitting ADS-B Out, particularly in Class B airspace, leading to increased visibility for air traffic control and other aircraft.
Establishes a presumption, absent clear and compelling evidence to the contrary, that ADS-B In equipment is cost beneficial and improves aviation safety.
Section 4(a)(4)(E)
Why it matters:This phrasing is a legislative tool to guide regulatory agencies, establishing a default position for the FAA's rulemaking process. It's a common way to signal congressional intent and reduce the burden on the agency to justify the core policy.
Case for: Proponents argue this presumption streamlines the rulemaking process, preventing unnecessary delays or challenges based on re-litigating the fundamental benefits of ADS-B In, which they believe are well-established. It reinforces the safety imperative.
Case against: Critics might argue that such a presumption could pre-empt thorough cost-benefit analysis, potentially overlooking unforeseen economic burdens on certain segments of the aviation community, especially if 'clear and compelling evidence' is a high bar to meet.
Estimated impact: Shapes the regulatory environment for ADS-B In, making it easier for the FAA to implement the mandate and harder for opponents to challenge it on cost-benefit grounds.
Repeals Section 373(a) of the National Defense Authorization Act for Fiscal Year 2026, and applies Chapter 157 of title 10, United States Code, as if those amendments had not been enacted.
Section 5
Why it matters:This is an unusual legislative maneuver, essentially pre-empting or reversing a provision that has not yet taken effect. It could be a way to ensure the current bill's policy direction takes precedence over anticipated future legislation, or to correct a known future conflict.
Case for: Proponents would argue that this pre-emptive repeal ensures consistency in aviation safety policy and prevents conflicting mandates from future legislation. It allows the ROTOR Act's comprehensive approach to ADS-B and rotorcraft oversight to proceed without interference.
Case against: It's difficult to make a direct 'case against' a repeal of a future act without knowing the content of the repealed section. However, critics might argue that legislating against future acts is procedurally unusual and could complicate future legislative processes or create unintended consequences if the context of the FY26 NDAA provision changes.
Estimated impact: Ensures that the specific provisions of the ROTOR Act regarding rotorcraft safety and transparency are the governing law, overriding any potentially conflicting or less stringent requirements that might have been included in the future NDAA.