Air traffic controller overwhelmed before deadly DC crash
- An air traffic controller failed to notify the commercial plane about the approaching Army helicopter before the deadly crash.
- The controller managed communications for 21 aircraft shortly before the incident occurred over the Potomac River.
- Safety measures were questioned, leading to changes in FAA regulations following the tragedy.
In January 2023, a tragic collision occurred in Washington, D.C., claiming the lives of 67 people when a commercial plane struck an Army helicopter. According to testimony from officials during a National Transportation Safety Board (NTSB) hearing, the air traffic controller responsible for directing both the helicopter and the incoming commercial flight was overwhelmed by a high volume of traffic, handling communications with 21 different aircraft in a short span of 10 minutes prior to the collision. The crash took place over the Potomac River, highlighting the critical situation at DCA airport during that period. The overwhelming traffic was compounded by heavy helicopter activity, which raised concerns about the safety measures in place. NTSB chairwoman Jennifer Homendy indicated that the controller had reported feeling stressed and under pressure, especially about 15 minutes before the incident. Although traffic lessened temporarily, which gave the controller a moment of relief, the crucial minutes leading up to the crash revealed the daunting challenge of managing multiple air traffic communications effectively. Investigations revealed lapses in safety protocols, notably the failure of the air traffic controller to alert the commercial flight crew about the Army helicopter's visual separation, despite it being standard practice for helicopter operators to see and avoid airliners. Testimonies included Clark Allen, operations manager at the airport's control tower, asserting that the tactics used were jeopardizing safety. The controller's reliance on visual separation as a traffic management tool was called into question, especially since clear communication with both aircraft was essential in preventing such tragedies. In the aftermath of the crash, the FAA imposed stricter rules on the use of visual separation to prevent future incidents. Additionally, staffing levels at the airport remained an issue, with reports indicating that although 26 controllers were assigned to the tower, only 19 were available to work. These staffing constraints further complicated air traffic management, raising questions about the effectiveness of operational procedures and the pressure placed on controllers in high-traffic scenarios.