Back to Bills

Stricter Aircraft Tracking and Transparency Rules

Full Title:
ROTOR Act

Summary#

The ROTOR Act would require more aircraft to carry and use traffic‑awareness gear and would tighten when government flights can turn off public tracking. It aims to improve air safety, especially around busy airports, and increase transparency for government flight operations.

Key changes:

  • Requires most crewed aircraft that now must have ADS‑B Out to also have and use ADS‑B In (traffic‑in) by December 31, 2031, with performance standards set by the FAA.
  • Tightly limits when government flights can turn off ADS‑B Out for “sensitive missions” (no longer allowed for training, proficiency, or flights of officials below Cabinet level).
  • Orders regular reporting to the FAA and Congress on all government uses of ADS‑B Out exceptions, and independent reviews by GAO and the DOT Inspector General.
  • Sets up FAA rulemaking to use ADS‑B for improved separation standards and updates air traffic controller training to match.
  • Directs safety reviews of helicopter, powered‑lift, fixed‑wing, and drone routes near Reagan National (DCA) and other Class B/C/D airports, and creates an FAA–DoD coordination office.
  • Requires FAA–military data‑sharing agreements on aviation safety information and repeals a prior law related to ADS‑B equipment on certain DoD aircraft.

What it means for you#

  • Air carriers and cargo operators

    • Must add and use ADS‑B In across fleets that operate where ADS‑B Out is already required (for example, around big airports and above certain altitudes).
    • May apply for up to a 1‑year extension past December 31, 2031, only if delay is needed to avoid major disruption, you show progress, and you have no uncorrected FAA violations.
    • Can expect new separation standards that use ADS‑B to improve safety and efficiency, and updated controller procedures.

  • General aviation owners and pilots (Part 91)

    • If you fly where ADS‑B Out is required today, you would also need ADS‑B In by the deadline.
    • For aircraft under 12,500 lbs, the FAA must allow lower‑cost ways to comply (for example, approved portable receivers and displays on an electronic flight bag) if they meet set performance goals and do not harm other avionics.
    • The FAA will publish guidance on what equipment counts.

  • Rotorcraft and powered‑lift operators

    • Included in the ADS‑B In requirement if you operate in ADS‑B Out airspace.
    • Your operations near major airports may be reviewed, and routes/procedures could change to reduce conflict with air carrier traffic.

  • Pilots and flight crews

    • Cockpit systems (or approved alternatives) must provide traffic advisories and alerts in flight and on the surface (visual and/or aural), per FAA performance standards.
    • Expect procedure and phraseology updates as separation rules evolve.

  • Federal, State, local, and Tribal agencies using ADS‑B exceptions

    • You can no longer cite “sensitive mission” to turn off ADS‑B Out for training, proficiency, or non‑Cabinet‑level official travel.
    • You must file quarterly reports to the FAA listing each flight when ADS‑B Out was off, with time, location, duration, and mission type, and attest that your other operations transmit ADS‑B Out.
    • Heavy use of the exception (5+ flights in a month) triggers notice to Congress.

  • Department of Defense

    • Subject to tighter ADS‑B Out exception limits and new safety information‑sharing MOUs with the FAA.
    • The Army Inspector General must audit Army training, coordination with the FAA, ADS‑B Out use, maintenance practices, and certain DC‑area operations, and publicly release findings (with only national security redactions).

  • Air traffic controllers

    • Training will be revised to apply any new ADS‑B‑enabled separation standards and surface movement uses.

  • Airports and communities near major airspace

    • The FAA will review routes and operations of helicopters, powered‑lift, fixed‑wing, and drones around DCA and other busy airports. This could lead to route or procedure changes to reduce risk to air carrier traffic.

Expenses#

No publicly available information.

  • Aircraft owners and operators would face equipage and installation costs for ADS‑B In or approved low‑cost alternatives, plus any display or integration work.
  • Large fleets may incur planning, certification, downtime, and training costs; smaller operators may have lower costs if portable solutions qualify.
  • FAA would incur costs to run multiple rulemakings, publish guidance, set performance standards, oversee compliance, conduct airport safety reviews, and stand up an FAA–DoD coordination office.
  • GAO, the DOT Inspector General, and the Army Inspector General would incur audit and reporting costs.
  • Government agencies that use ADS‑B exceptions would face reporting and compliance workload.

Proponents' View#

  • Requiring ADS‑B In appears intended to reduce mid‑air and surface conflicts by giving pilots real‑time, standardized traffic alerts, likely improving safety across busy airspace.
  • Setting performance standards and allowing low‑cost options for small Part 91 aircraft could spread safety benefits widely while controlling costs.
  • Using ADS‑B capabilities to update separation standards could improve both safety and efficiency (for example, smoother flows and better surface awareness).
  • Narrowing government exceptions and adding regular reporting may increase transparency and accountability without blocking truly sensitive missions.
  • Coordinated safety reviews around DCA and other major airports could identify and fix risky interactions among helicopters, powered‑lift, drones, and air carriers.
  • FAA–DoD data sharing and an action plan for modern collision‑avoidance systems (ACAS‑X) could speed adoption of proven safety technologies.

Opponents' View#

  • One concern is cost and timing: equipping tens of thousands of aircraft by December 31, 2031, may strain avionics supply chains and installation capacity, especially if cockpit alerting and surface features are required.
  • It is unclear which portable or “low‑cost” solutions will meet the FAA’s performance standards; uncertainty could delay purchases or force later upgrades.
  • The bill presumes ADS‑B In is cost‑beneficial, which may be seen as prejudging the FAA’s economic analysis and limiting flexibility if benefits vary by aircraft type or operation.
  • Tighter limits on ADS‑B Out exceptions and detailed reporting could reduce operational discretion for law enforcement and military flights, raising security or mission‑confidentiality concerns.
  • The FAA faces many short deadlines for rules, safety reviews, and training updates; compressed timelines may challenge thorough analysis and stakeholder engagement.
  • Repealing a prior DoD‑related ADS‑B provision may remove flexibility the military has relied on; the safety and security balance is not fully explained in the bill text.