February 1st, 2025

Air traffic controller 'left work early', one was left to handle the air traffic

An air traffic controller's early departure led to inadequate staffing during a midair collision at Ronald Reagan National Airport, resulting in 67 presumed deaths and new FAA flight restrictions.

Read original articleLink Icon
Air traffic controller 'left work early', one was left to handle the air traffic

An air traffic controller at Ronald Reagan National Airport left work early before a tragic midair collision between a passenger plane and an Army helicopter, resulting in the presumed deaths of all 67 individuals on board. Reports indicate that a single controller was managing air traffic, a task typically handled by two, due to a supervisor merging their responsibilities prematurely. The Federal Aviation Administration (FAA) confirmed that staffing levels were not adequate for the volume of traffic at the time. Investigators are examining the helicopter's flight patterns, which may have included flying above its designated altitude and off its approved path. The helicopter was reportedly above 300 feet when it should have been below 200 feet and was at least half a mile off course. Following the incident, the FAA announced indefinite restrictions on helicopter flights near the airport, allowing only police and medical helicopters in the area. The bodies of the three soldiers aboard the helicopter have been recovered, and both black boxes from the passenger plane have been retrieved for analysis.

- An air traffic controller left early, leading to inadequate staffing during a critical time.

- The helicopter may have been flying above its designated altitude and off its approved flight path.

- The FAA has imposed indefinite restrictions on helicopter flights near Ronald Reagan National Airport.

- All 67 individuals on both aircraft are presumed dead following the collision.

- Investigators are focusing on air traffic control staffing and the helicopter's flight patterns.

Link Icon 4 comments
By @exabrial - 3 months
The ATC is faultless in the incident: listen to the audio, he confirmed multiple times the handoff to visual separation. At the last second, he even asked if they had visual as he saw the potential collision and alarms were going off. Fairly certain the fault like 100% with the helicopter pilots.
By @johnneville - 3 months
so far there doesn't seem to be any evidence that the air traffic controller contributed to the accident. the article serves as a reminder that there is a shortage of air traffic controllers across the country and this shortage has the potential to reduce safety overall
By @xor-eax-eax - 3 months
I wouldn't be so eager to jump to this conclusion.

After listening to a former pilot on this type of aircraft, who flew this very aircraft into this very airport, the many problems are clear:

- This particular helicopter was flying too high when it should've been around treetop/obstacle-avoidance level where it was

- Helicopters shouldn't be flying through an approach path of a major airport

- TCAS won't do a damn thing <1000' AGL. Perhaps subsequent versions of TCAS should address traffic around airports and down to around 200' AGL

- DCA should scale back on its traffic volume

- The approach change from 01 to 33 is awkward

- The FAA needs to exhaust all avenues to encourage, hire, and train ATC to bolster its ranks rather than send emails about how to quit or allow commercial figures to pressure its leadership to resign

Also, I really want to know if:

- The AA jet got a TCAS TA (advisory) because they definitely didn't receive an RA (warning)

- The ATC controller was in ADS-B filter mode or was seeing all data

We'll never know if:

- The chopper pilot mistook another aircraft for the AA one or was giving the answer expected due to being on NVGs in busy airspace