If your business involves helicopter operations near a major airport, the regulatory landscape changed recently – and the implications are already significant.

On March 18, 2026, the Federal Aviation Administration (FAA) and Transportation Secretary Sean Duffy announced a consequential airspace safety overhaul. Following a year-long analysis triggered by the January 2025 DCA midair collision over the Potomac River – in which an Army Black Hawk helicopter struck American Airlines Flight 5342, killing 67 people – the FAA is now suspending the use of visual separation between airplanes and helicopters in busy terminal airspace, requiring controllers to use radar separation instead.

This isn't a tweak to a local procedure. The new requirement applies to the nation's busiest airports, extending a restriction already in place at Ronald Reagan Washington National Airport.

What changed - and why 

For decades, air traffic controllers in congested terminal areas could manage helicopter–airplane conflicts using “visual separation” – essentially, pointing out nearby traffic and allowing pilots to maintain safe distance by sight. The NTSB’s final report on the DCA crash blamed the collision in part on the system’s “overreliance on visual separation,” as well as the failure of the helicopter crew to apply it effectively. Investigators concluded that the crew likely never saw the plane before impact.

The FAA said its review found an overreliance on pilot “see-and-avoid” practices in high-traffic areas where helicopters routinely cross final approach or departure paths. Two recent near misses drove the urgency: on February 27, 2026, a police helicopter had to turn to avoid an American Airlines flight landing at San Antonio International Airport, and on March 2, 2026, a similar close call occurred at Hollywood Burbank Airport. These are not the only recent close calls involving helicopters. The FAA is investigating a near miss between a plane and a military helicopter at John Wayne Airport in California on March 24, 2026 that reportedly triggered an anti-collision alert in the plane’s cockpit.

Under the new directive, controllers at covered airports must now actively manage helicopter–airplane spacing using specific radar-defined lateral or vertical distances – not just pilot eyesight.

Key legal risks and open questions 

Standard of care. The FAA’s public acknowledgment that visual separation procedures are inadequate in these environments is a significant evidentiary development. Plaintiffs’ attorneys may argue that this admission affects the standard of care in any future incidents. Operators and insurers should assess how this framing affects claims.

Congressional legislation is still in motion – and could go further. In December 2025, the Senate unanimously passed the ROTOR Act, which would require broader use of Automatic Dependent Surveillance-Broadcast (ADS-B) technology and implement NTSB safety recommendations following the DCA crash, but it narrowly failed in the House on February 24, 2026, after the Pentagon withdrew its support, stating that the bill could create “unresolved budgetary burdens and operational security risks.” The House has now introduced the ALERT Act, which sponsors say addresses all 50 NTSB recommendations. However, the NTSB believes that “many key provisions fall short of fully implementing all of the NTSB’s recommendations,” including recommendations on the use of ADS-B. Whichever bill passes will likely impose additional equipment mandates on operators – particularly ADS-B for operators who are not currently required to carry it. Notwithstanding these concerns, two House committees voted to advance the ALERT Act on March 26, 2026. 

Operational disruption and contract exposure. Helicopter operators with existing service agreements – such as air medical transport contracts and offshore support arrangements at coastal airports – may face route modifications, schedule changes, or capacity constraints as the new radar separation standards are operationalized. Whether those changes constitute a force majeure event or a breach trigger depends on how the underlying contracts are drafted.

Practical considerations and key takeaways 

• Audit your operational footprint against the covered airports. Identify every route, base, or service contract that involves Class B, Class C, or Terminal Radar Service Area operations where your helicopters travel across arrival or departure corridors. The FAA’s general notice applies broadly, and the operational details are still being worked out at individual facilities.
• Track the ROTOR Act and ALERT Act closely. A change in ADS-B requirements for helicopters – if it clears Congress – could require significant capital expenditure on a compressed timeline. Model the cost scenarios now so that you’re not caught flat-footed if and when a bill moves.
• Review your service contracts for operational change provisions. Engage counsel to assess whether new routing restrictions or capacity changes at specific airports trigger notice obligations, cost-sharing provisions, or renegotiation rights in your existing agreements.