The ADS-B Mandate That Congress May Not Finish This Year, the ROTOR Act Delay Senator Moran Is Warning About, and What It Means for the Traffic Picture Every Pilot Is Already Trusting

Senator Jerry Moran warns the ROTOR Act - which would expand ADS-B requirements to drones - may not pass Congress until 2027, leaving a known gap in pilot traffic awareness.

Aviation News Analyst

Senator Jerry Moran of Kansas, a member of the Senate Commerce Committee, recently told Flying Magazine that it would not be a shock if debate over the ROTOR Act extends into 2027. For pilots, that means the legislation designed to close a known gap in ADS-B coverage - the gap where drones and other unequipped aircraft operate invisibly to your traffic display - is likely delayed by at least a year.

What the ROTOR Act Actually Does

The ROTOR Act is broader than its name implies. It addresses drone integration, airspace management, and critically, expanded ADS-B requirements for categories of aircraft currently exempt from the existing mandate. The rotorcraft reference is almost a footnote. The substance that matters to the working pilot is the drone piece.

The bill would require certain drones - particularly those operating near airports, above specific altitudes, or within controlled airspace - to carry equipment compatible with the broader ADS-B ecosystem. The goal is a traffic display that shows you the full picture, not just the mandated and equipped portion of it.

The Original ADS-B Mandate and What It Left Out

The FAA finalized the ADS-B Out mandate in 2010, setting a compliance deadline of January 1, 2020. The rule was straightforward: if your aircraft was previously required to carry a transponder, it now needed ADS-B Out. That covered Class A, Class B, Class C, and Class E airspace above 10,000 feet MSL - essentially anywhere the traffic density and airspace structure demanded it.

The decade-long implementation window paid off. By the time the deadline arrived, equipping rates were high enough that the system worked as designed. Ground stations received signals. The FAA’s Traffic Information Service began broadcasting targets back to cockpits. Pilots in equipped aircraft could, for the first time, see nearby traffic without depending entirely on radar coverage.

What the mandate did not reach: ultralights, certain light sport aircraft, drones, and smaller aircraft operating below the floor of mandated airspace. Those categories were left outside the requirement entirely.

Why the Gap Matters

The aircraft absent from your ADS-B display tend to operate at the altitudes where midair collision risk is statistically concentrated. Below Class E, in the uncontrolled airspace where pattern work, training, banner towing, and low-level operations converge, equipped and unequipped aircraft share the same sky. Some targets appear on your display. Others do not. The ones that don’t appear aren’t necessarily doing anything wrong - they’re simply operating where the mandate doesn’t apply.

The FAA now estimates hundreds of thousands of registered drones operating in the national airspace, with commercial operations growing every year. Delivery platforms, inspection drones, aerial survey systems running pipeline routes and power line corridors - these are real aircraft in real airspace, some with no means of advertising their position to manned traffic.

Why Remote ID Doesn’t Solve This

The FAA’s Remote ID rule, which took effect in 2023, requires most drones to broadcast their identity and location. It was intended to address part of this problem. It doesn’t, in the way most pilots assume.

Remote ID and ADS-B are not interchangeable. They broadcast on different frequencies, using different standards, to different receiver ecosystems. The ADS-B In display in your cockpit does not receive Remote ID signals from drones. A drone flying a fully compliant Remote ID broadcast is effectively invisible on your traffic awareness display. The two systems exist in parallel. They do not integrate.

Why the Legislation Is Stalling

Senator Moran’s signal that the ROTOR Act may not advance this session reflects a legislative reality, not a policy failure. Moving a bill from committee markup through floor vote, conference, and presidential signature is a slow process even with bipartisan support. Aviation legislation in particular tends to get absorbed into broader spending fights and reauthorization battles unrelated to the bill’s substance.

The FAA reauthorization cycle is an instructive example. Those bills are supposed to pass on a regular multi-year schedule. They almost never do on time. Extensions, continuing resolutions, and last-minute omnibus riders are the norm.

There’s also a legitimate substantive debate still underway. The drone industry has pushed back on equipment mandates that would raise per-unit costs - particularly for smaller commercial operators and recreational users. A $50 recreational drone and a $50,000 commercial platform don’t carry the same risk profile, and identical equipment standards for both is an argument that doesn’t hold up. The ROTOR Act was attempting to draw those distinctions, targeting ADS-B requirements at higher-risk operational categories rather than applying a blanket mandate. Whether the final language satisfies both safety advocates and industry stakeholders is part of what negotiations are still working through.

What This Means for Pilots Right Now

A slip to 2027 does not change your compliance status. The existing ADS-B Out requirements remain in force and are not under threat. If you’re already equipped, nothing changes operationally.

What doesn’t change is the expectation of a more complete traffic picture. That improvement is deferred.

Two parallel developments are worth watching. First, the FAA retains independent rulemaking authority that doesn’t require an act of Congress. If the legislative path stalls, the agency could potentially advance some of these provisions through notice and comment rulemaking - a slower road with its own procedural requirements, but a viable one. Second, some commercial drone manufacturers have already begun voluntarily incorporating ADS-B-compatible equipment into higher-end platforms, anticipating a mandate that is eventually coming and treating early compliance as a market advantage.

Flying in the Gap

The core discipline requirement here predates ADS-B by decades. When TCAS became standard on airline fleets, crews had to be explicitly reminded that the system only detected transponder-equipped traffic. The same principle applies to your EFB traffic display today.

ADS-B is an excellent tool for what it covers. The professional requirement is knowing precisely what it doesn’t cover. At uncontrolled airports, announce your position, listen actively for traffic, and treat the absence of a target on your display as absence of information - not absence of traffic. Eyes outside. Scan ongoing.

The mandate isn’t dead. It’s delayed. The policy direction hasn’t changed; the timeline has slipped. In Washington, that’s a meaningful distinction.


Key Takeaways

  • Senator Jerry Moran warned Flying Magazine that the ROTOR Act, which includes expanded ADS-B requirements for drones, could slip to 2027
  • The original ADS-B Out mandate (compliance deadline: January 1, 2020) explicitly excluded ultralights, certain light sport aircraft, and drones
  • The FAA Remote ID rule (2023) does not integrate with ADS-B - drone Remote ID signals are invisible on cockpit traffic displays
  • The ROTOR Act aimed to require ADS-B-compatible equipment on drones in higher-risk operational environments, not all registered drones
  • Existing ADS-B Out requirements are unaffected; the delay impacts only the anticipated expansion to currently-exempt aircraft
  • The FAA retains independent rulemaking authority and could act without Congress if the legislative path stalls

Radio Hangar. Aviation talk, built by pilots. Listen live | More articles