Six Monthly Airport Near Misses Persist With 270 Safety Recommendations Open

U.S. commercial aircraft were involved in at least 95 voluntarily reported near misses over roughly 16 months about six per month while 270 aviation-safety recommendations from the National Transportation Safety Board remained open. The parallel figures expose a structural tension in aviation oversight: hazards can be reported quickly, but converting lessons from accidents and incidents into operating requirements, equipment mandates or procedural changes can take years.

The count covers reports from Jan. 29, 2025, through May 2026. It is not a verified census of imminent collisions. Because flight-crew reporting is non-mandatory, the total is likely incomplete, and each submission reflects the reporting crew’s account rather than a completed official investigation. Reports named 33 airports; locations were not disclosed for nearly 50 other events.

That distinction matters. Voluntary safety reporting is designed to surface weak signals including confusing procedures, missed traffic advisories and unexpected aircraft proximity before they produce accidents. A report can identify a condition worth examining without establishing fault, cause or the precise collision risk. The dataset therefore supports concern about recurring aircraft-separation events, but it cannot by itself determine how many would have become accidents.

Why an NTSB recommendation is not an operating rule

The NTSB investigates accidents and proposes corrective action, but it does not operate the air-traffic system, certify aircraft or write binding aviation rules. Implementation belongs to the Federal Aviation Administration, Congress or another organization named in a recommendation. Readers can search the board’s investigations and recommendations through its public accident-data and recommendations resources.

This separation of authority is intentional: an independent investigative body can identify safety deficiencies without also defending the regulator’s previous decisions. The cost is that a recommendation is not self-executing. A proposed safeguard may require rulemaking, funding, equipment certification, installation across mixed fleets, controller training, revised military procedures or coordination among agencies. Those steps can be legitimate, but they also create multiple points where action can slow or stop.

The measured delay is substantial. Responsible organizations take more than 4.5 years on average after a crash to adopt an NTSB recommendation. Two recommendations originating with the 1994 Pittsburgh crash, which killed 132 people, were adopted in December 2025 31 years later. That extreme case does not establish that every open item has waited decades, but it shows how far the recommendation-to-implementation gap can extend.

Of the 270 open recommendations, 51 were associated with the Jan. 29, 2025, collision between an American Airlines flight and a military helicopter near Washington, D.C., which killed 67 people. An open designation does not mean no safety work has occurred, nor does it prove a recommendation would have prevented a particular later event. It means the recommended action has not been closed as fully implemented.

Helicopters create a recurring integration challenge

About 30% of the reported near misses during takeoff or landing involved helicopters. That concentration matters because airports must integrate aircraft with different speeds, flight paths, visibility constraints and operating missions into the same traffic picture. Safe separation depends on several layers working together: surveillance, controller awareness, clear communications, compatible procedures and cockpit traffic information.

One commercial crew reported that a helicopter passed within 100 feet during an October 2025 landing at Erie International Airport and said air traffic control had not alerted the crew. That remains an attributed voluntary report, not an official finding about separation, controller performance or cause. Other pilots criticized standards applied to military operations, but those comments likewise represent individual accounts rather than agency conclusions.

The policy dispute centers on how consistently surveillance and collision-prevention requirements should apply across civil and military aircraft while accommodating operational-security constraints. The ALERT Act listed by Congress would make location broadcasting the default for Defense Department helicopters in national airspace, subject to an operational-security exception, and require risk assessments and mitigations for certain exempt Washington-area missions. It also sets a 2031 target for broader installation of technology that receives traffic information. A separate proposal intended to align military and commercial aviation-safety rules failed in the House in February 2026.

Technology deployment is advancing in another part of the system. The FAA said in September that its Surface Awareness Initiative was operating at 100 towers, with another 44 installations planned by the end of 2026. The tool uses aircraft and vehicle broadcasts to help controllers track airport-surface traffic, including when visibility is poor. That is meaningful runway protection, but it should not be treated as a universal answer to airborne airplane-helicopter encounters; surveillance coverage, cockpit equipage, procedures and communications remain distinct layers.

The unresolved question is therefore not whether one device or rule can eliminate near misses. It is whether the U.S. can turn reported warning signs into coordinated, verified safeguards faster than its historical pace. With 270 recommendations still open and adoption averaging more than 4.5 years, implementation time itself remains part of the safety problem.

By Thomas Caldwell — AMI’s senior editor for mechanical and mobility engineering, covering vehicle electronics, systems integration, electrification, chassis systems, propulsion, and safety policy.