SELECT LANGUAGE BELOW

Air traffic controller did not alert aircraft prior to DC crash that resulted in 67 fatalities

Air traffic controller did not alert aircraft prior to DC crash that resulted in 67 fatalities

Investigation into DC Plane Crash Highlights Communication Failures

In January, a tragic incident in Washington, DC, resulted in the death of 67 people when an Army helicopter collided with a commercial aircraft. Recently, federal aviation officials revealed that air traffic controllers did not inform the plane’s crew about the helicopter’s proximity before the crash.

This disclosure emerged during a National Road Safety Commission hearing focused on the factors leading to the airborne collision. On the second day of the hearings, officials discussed the challenges of managing helicopter traffic amid numerous takeoffs and landings, as reported by the Washington Post.

On the night of the crash, controllers often allowed helicopter crews to rely on their judgment to navigate safely, avoiding certain runways to minimize risks.

A testimony pointed out that the controller managing both the Black Hawk helicopter and American Airlines flights was overwhelmed just before the collision. Ten minutes prior to the accident, the controller was juggling communications with 21 different aircraft. However, they noted that traffic seemed to ease a bit shortly before the incident, which made them feel more comfortable.

At the hearing, NTSB Chair Jennifer Homendy pressed FAA officials on whether the controllers communicated the helicopter’s presence to the jets. These jets included one operated by local carrier PSA. The FAA’s Nick Fuller confirmed that controllers were indeed supposed to notify the airline crews about the helicopter using visual separation.

With as many as 80 aircraft departing per hour, the airspace was indeed very busy, and the operational tactics employed that night were scrutinized. Clark Allen, the operations manager at the airport tower, acknowledged that the controller’s actions were effectively “pushing the line” regarding safety.

Even though the controller claimed not to feel external pressure, FAA officials explained that the tight schedules set by airlines like American Airlines compounded the problem. A few minutes prior to the crash, the controller sought a pilot willing to land on a secondary runway to alleviate congestion on the main one. However, this decision inadvertently directed aircraft directly into the helicopter’s flight path.

The FAA has noted that the current maximum arrival rate at the airport has been reduced to 30 aircraft per hour in light of the incident.

During the hearings, it was revealed that visual separation—a method where helicopter operators visually identify commercial aircraft to maintain safe distances—was commonly used, but in this instance, the helicopter crew did not see the approaching jet before the collision occurred.

Following the crash, the FAA has since imposed stricter guidelines on the use of visual separation in air traffic control to enhance safety measures moving forward.

With other ongoing investigations, it’s clear that many controllers have expressed concerns about staffing numbers, pointing to issues within the air traffic control system that need addressing to prevent future accidents.

Facebook
Twitter
LinkedIn
Reddit
Telegram
WhatsApp

Related News