FAA Removes See-And-Avoid Rule for Helicopters in Class B Airport Airspace

(UNITED STATES) — U.S. Transportation Secretary Sean P. Duffy and FAA Administrator Bryan Bedford announced on March 18, 2026, that the Federal Aviation Administration had suspended visual “see and avoid” separation between helicopters, powered-lift aircraft and fixed-wing aircraft in some of the nation’s busiest controlled airspace.

The nationwide General Notice, GENOT JO 7110.801, took effect immediately in Class B airspace, Class C airspace and Terminal Radar Service Areas, or TRSAs. Air traffic controllers must now use radar to maintain standard lateral or vertical separation distances where helicopter traffic crosses arrival or departure paths near major airports.

The move ends a long-used practice in those settings in which controllers could authorize pilots to rely on visual separation, often described as see and avoid, in mixed-traffic environments. Under the new policy, controllers no longer authorize pilots to use that method in the covered airspace.

Bryan Bedford, FAA administrator, said the change followed a year-long safety review that found overreliance on visual separation had become a risk factor. “Today, we are proactively mitigating risks before they affect the traveling public,” Bedford said.

Sean P. Duffy, transportation secretary, said the agency was implementing reforms following the 2025 midair collision, including data tools to identify nationwide risk areas. The review used AI-driven data analysis of cross-traffic and incident reports.

The change applies nationwide, not only around Washington. It covers Class B airspace, Class C airspace and TRSAs, and it includes helicopters and powered-lift aircraft operating alongside fixed-wing traffic near airports where arrivals and departures can intersect with rotorcraft routes.

That broad scope marks an expansion of measures the FAA first imposed around Ronald Reagan Washington National Airport, known as DCA, after a deadly collision in January 2025. Those earlier restrictions focused on one of the country’s most complex pieces of airspace. The new order extends radar-based separation standards across the country in mixed-traffic airport environments.

The policy stems from the January 2025 midair collision near DCA, where American Airlines Flight 5342 struck a helicopter, killing 67 people. That crash set off a chain of restrictions, route changes, safety recommendations and regulatory actions that culminated in the nationwide order announced this week.

In January 2025, the FAA restricted helicopter traffic over the Potomac River around DCA to Wilson Bridge and temporarily eliminated visual separation at DCA. A month later, in February 2025, the agency began a nationwide review of airports with high mixed-traffic volumes.

That review widened the focus from one airport to a national system problem. By March 2025, the National Transportation Safety Board had issued two safety recommendations, and the FAA had established procedures to eliminate mixed traffic near DCA while amending procedures to ban visual separation within 5 nautical miles.

The changes continued through the rest of the year. In October 2025, the FAA updated helicopter routes and zones at DCA, Washington Dulles Airport, known as IAD, and Baltimore/Washington International Airport, or BWI, and implemented Time Based Flow Management, or TBFM, at Washington Center.

Then, on January 23, 2026, the FAA published an Interim Final Rule permanently restricting helicopters and powered-lift from certain DCA areas unless for essential operations, including no operations over Runways 15/33. The agency invited public comments before issuing a final rule.

Several DCA-specific measures now remain in place as permanent parts of that January 2026 Interim Final Rule. They include the closure of Route 4 between Hains Point and Wilson Bridge, a requirement for military ADS-B Out broadcasting, the discontinuation of Pentagon Heliport takeoffs until procedures are updated, and the relocation of helicopter zones farther from DCA flight paths.

The FAA also increased staffing and oversight at DCA. Those steps reflected a strategy that moved from immediate restrictions after the crash to more durable changes in how helicopters and fixed-wing aircraft share constrained airspace.

The nationwide order announced on March 18 follows the same logic. Instead of allowing a helicopter crew and an airplane crew to maintain spacing visually where routes cross, controllers must now separate them using radar and standard distances.

That shifts more responsibility onto the control system in areas where traffic density, converging paths and speed differences can compress decision time. It also places the same standard across airports covered by Class B, Class C and TRSA rules, rather than limiting the approach to one high-profile corridor in the Washington region.

The FAA pointed to more than the DCA collision in explaining why it acted. Among the incidents cited was a near-conflict between an American Airlines flight and a police helicopter in San Antonio.

Another example involved converging paths between a Beechcraft 99 and a helicopter near Hollywood Burbank Airport. That event was resolved by evasive maneuvers.

Those examples illustrated the same underlying concern: mixed traffic in busy terminal airspace can produce short-notice conflicts when one aircraft is crossing another’s arrival or departure path. In those conditions, the agency concluded that see and avoid was not enough.

Class B airspace generally surrounds the busiest airports in the United States, while Class C airspace covers airports with substantial traffic that do not meet Class B thresholds. TRSAs are areas where radar services support sequencing and separation around selected airports. By applying the policy in all three, the FAA reached a large share of airports where helicopters and airplanes routinely share constrained approach and departure corridors.

The order also specifically includes powered-lift aircraft. That places emerging aircraft types under the same separation rule when they operate in those mixed environments with fixed-wing traffic.

For controllers, the operational change is immediate. They must transition to radar-based separation in affected airspace whenever helicopter traffic crosses arrival or departure paths near major airports.

For operators, the effect is practical and immediate as well. Helicopter operators, powered-lift operators and fixed-wing crews working in or around Class B airspace, Class C airspace and TRSAs must review updated procedures and routes, especially at airports where helicopter corridors have historically intersected with airline traffic.

The agency framed the shift as preventive rather than reactive. Bedford’s statement cast the order as an attempt to address a risk pattern before it produces another fatal outcome.

The DCA measures offer a case study in how that approach evolved. The FAA first imposed localized restrictions after the January 2025 crash, then expanded its review to airports nationwide, then tightened procedures in stages through March and October, before publishing the January 23, 2026 Interim Final Rule and finally adopting the broader radar mandate this week.

The chronology also shows how safety findings moved through several channels. The NTSB issued recommendations. The FAA revised routes and procedures. Regulators then used the rulemaking process to lock in permanent restrictions at DCA while inviting public comments before the final rule.

Now the systemwide notice pushes the same concept beyond Washington. Mixed helicopter and fixed-wing traffic near large and midsize airports will no longer rely on pilot-applied visual separation in the affected airspace.

The order may prove especially relevant around airports where police, medical, military, corporate and scheduled airline traffic all converge in a small area. At such airports, helicopters can move laterally across final approach paths or departure corridors while fixed-wing aircraft climb or descend at much higher speeds.

That is the operating environment the FAA examined in its year-long review. The agency said its analysis of cross-traffic and incident reports showed overreliance on visual separation as a risk factor, leading it to replace that method with radar-based separation standards.

The Washington area remains the clearest example of how the agency has reshaped operations. Route 4 is closed between Hains Point and Wilson Bridge. Military aircraft must broadcast ADS-B Out. Pentagon Heliport takeoffs remain discontinued until procedures are updated. Helicopter zones have moved farther from DCA flight paths, and staffing and oversight have increased.

Those steps, once tied to one airport after one crash, now sit alongside a nationwide directive that changes controller practice across broad categories of terminal airspace. The FAA’s message is that the problem is not confined to one river corridor or one metropolitan area.

The Interim Final Rule published on January 23, 2026 remains part of that larger process. Public comments are still part of the path toward a final rule, while the General Notice already governs controller action now.

That means the agency is moving on two tracks at once: permanent DCA restrictions through rulemaking and immediate nationwide operating changes through GENOT JO 7110.801. Together, they reflect a broader rewriting of how helicopters, powered-lift aircraft and fixed-wing airplanes are separated near busy airports.

For passengers, the policy change will largely be invisible. For controllers and operators, it alters the basic method used to keep unlike aircraft apart in crowded terminal airspace.

And for an FAA still reshaping procedures after 67 people died near DCA, Bedford summed up the agency’s approach in one sentence: “Today, we are proactively mitigating risks before they affect the traveling public.”