Pilots warned of safety concerns at Reagan National Airport for decades
Some of the reports warned that the flight space was "an accident waiting to happen" with others describing scenarios eerily close to what occurred when a military Black Hawk helicopter collided with American Airlines Flight 5342 last week as the passenger jet approached the airport.
"One of these incidents would have been too many," said former Air Force pilot and ABC News aviation consultant John Nance. "This barometer is in the red. It's telling us there is a real problem here. There is a very, very clear track record of something that needs to be fixed."
There are at least four reports of safety incidents associated with runway 33, the same runway that AA 5342 was approaching when the collision that took 67 lives occurred.
"This has been happening too many times over the years, and it's now led to a tragedy that could have been prevented," said Steve Ganyard, a former Marine Corps fighter pilot and ABC News contributor.
The safety reports were filed with the Aviation Safety Reporting System, a program established by the FAA and managed by NASA that enables professionals within the aviation community to voluntarily and confidentially report safety concerns and incidents in a non-punitive manner.
In response to questions from ABC News, the FAA said, "Due to the ongoing NTSB investigation, we cannot provide information at this time." The FAA added that ASRS reports are "one of many data sources we use to identify system-level safety risks."
The reports detail accounts of airplane flight crews at DCA who were surprised by helicopters flying too close, oftentimes describing near misses in the air within just hundreds of feet.
MORE: Grieving family members visit site of DC plane crash
One captain for a major carrier went so far as to call DCA "probably the most dangerous airport in the United States" in a report concerning their broader safety concerns about flying in and out of the airport.
In 2015, the flight crew of a regional jet reported a near mid-air collision when it was switched from landing on runway 1 to runway 33 at DCA, coming "within very close contact" of a helicopter also in air. The safety report continues, "This occurred about 400 feet off the ground to the point where the pilot monitoring had to take the controls to make a correction in order to prevent it from becoming a midair collision."
The reporting crew says that only after taking action to avoid a collision was the regional jet informed by DCA air traffic control of the close traffic, with the flight crew adding "at that point it would have been too late."
American Airlines Flight 5342 was also switched to runway 33 after lining up for runway 1, in order to keep traffic moving, a common practice at DCA.
It is not yet known whether air traffic control ever communicated the helicopter's close proximity to the American Airlines flight crew, though the Black Hawk helicopter was asked if they had the airplane in sight and replied that they did.
One airplane captain reported a near mid-air collision with a helicopter in April 2024, writing, "We never received a warning of the traffic from ATC so we were unaware it was there." The captain urged "better separation for DCA traffic on the river visual to the helicopter traffic that is flying up and down the river."
In 2013, an airplane captain reported coming within 200 feet of a military helicopter while approaching DCA to land, writing, "There are always numerous military and government helicopters running up and down that river at all times of the day and night. Because of this, what would normally be alarming at any other airport in the country has become commonplace at DCA. The FAA allows these aircraft to operate in this environment and we have no choice, but to accept it and deal with it."
The concerned airplane pilot in that incident continued, "I cannot imagine what business is so pressing that these helicopters are allowed to cross the paths of airliners carrying hundreds of people!"
Nance said this collection of safety incident reports "details a tale of dress rehearsals for what happened last week."
In a separate incident report filed in 1997, an airplane first officer detailing a close encounter with a military helicopter said, "I was not comfortable with the level of safety involved with flying within 400 ft [vertically] of a heli and that is considered a normal op."
In 1993, a captain of an airplane that came close to a helicopter flying above the Potomac River said, "This heli conflict around DCA is a daily prob!... This is an accident waiting to happen."
In 1991, yet another flight crew reporting a converging flight path with a military helicopter wrote, "Here is an accident waiting to happen."
MORE: DC plane crash: A timeline of the deadly collision
Nance said an examination of these reports illustrates "flight crew confusion at critical junctures in the approach caused by alarming interactions with helicopter traffic," "wildly variable altitudes flown by the helicopter traffic," and "overburdened tower controllers" who "appear to consider the pace of operations and the number of close calls with helicopters in critical areas as business as usual."
"The helicopter routes around DCA allow for little margin for error," Ganyard said. "You cannot have aircraft constantly flying so close together and expect to maintain safety."
"In the AA crash we see the consequences of a minor mistake becoming a tragedy," Ganyard added. "Step one for the FAA is to reroute helicopter traffic around DCA."
In the aftermath of the crash last week, the FAA restricted helicopter traffic over the Potomac River around DCA while the NTSB completes its preliminary investigation. At that point, the FAA said, it will review the airspace based on the NTSB's report.
The Aviation Safety Reporting System was established in 1976 to "support the FAA in its mission to eliminate unsafe conditions in the national aviation system, and prevent avoidable accidents," according to its website. The program is managed by NASA as an independent third party with no regulatory or enforcement role, which says it "ensures that de-identified incident data and the results of special studies are communicated to those responsible for aviation safety."
On its website, the FAA said it established it is "a positive program intended to ensure the safest possible system by identifying and correcting unsafe conditions before they lead to accidents."
In a report last year on near mid-air collisions, ASRA said, "Such incidents are independently submitted and are not corroborated by NASA, the FAA or NTSB. The existence in the ASRS database of reports concerning a specific topic cannot, therefore, be used to infer the prevalence of that problem within the National Airspace System."
Pilots warned of safety concerns at Reagan National Airport for decades originally appeared on abcnews.go.com
Hashtags
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
NBC News
4 hours ago
- NBC News
Night vision goggles may have hindered helicopter pilots before jet collision, experts say
The pilots of a U.S. Army helicopter that collided with a passenger jet over Washington in January would've had difficulty spotting the plane while wearing night vision goggles, experts told the National Transportation Safety Board on Friday. The Army goggles would have made it difficult to see the plane's colored lights, which might have helped the Black Hawk determine the plane's direction. The goggles also limited the pilots' peripheral vision as they flew near Ronald Reagan Washington National Airport. The challenges posed by night-vision goggles were among the topics discussed at the NTSB's third and final day of public testimony over the fatal midair crash, which killed all 67 people aboard both aircrafts. Experts said another challenge that evening was distinguishing the plane from lights on the ground while the two aircraft were on a collision course. Plus, the helicopter pilots may not have known where to look for a plane that was landing on a secondary runway that most planes didn't use. 'Knowing where to look. That's key,' said Stephen Casner, an expert in human factors who used to work at NASA. Two previous days of testimony underscored a number of factors that likely contributed to the collision, sparking Board Chairwoman Jennifer Homendy to urge the Federal Aviation Administration to 'do better' as she pointed to warnings the agency had ignored years earlier. Some of the major issues that have emerged so far include the Black Hawk helicopter flying above prescribed levels near the airport as well as the warnings to FAA officials for years about the hazards related to the heavy chopper traffic there. It's too early for the board to identify what exactly caused the crash. A final report from the board won't come until next year. But it became clear this week how small a margin of error there was for helicopters flying the route the Black Hawk took the night of the nation's deadliest plane crash since November 2001. Army Colonel Andrew DeForest told the NTSB that 'flights along the D.C. helicopter routes were considered relatively safe,' but some pilots in the 12th Battalion that flew alongside the crew that crashed told investigators they regularly talked about the possibility of a collision because of the congested and complicated airspace. The American Airlines jet arrived from Wichita, Kansas, carrying, among others, a group of elite young figure skaters, their parents and coaches, and four union steamfitters from the Washington area. The collision was the first in a string of crashes and near misses this year that have alarmed officials and the traveling public, despite statistics that still show flying remains the safest form of transportation. 'Significant frustration' NTSB members scolded FAA officials during Friday's hearing, accusing them of saying the right things about safety in public while failing to cooperate in private. They said the FAA has repeatedly refused to provide information requested by investigators. Board member Todd Inman said there was 'significant frustration between what's actually occurring' and 'what's being said for public consumption.' Frank McIntosh, the head of the FAA's air traffic control organization, said he would start working immediately to make sure the agency complies with the investigation. McIntosh also acknowledged problems with the culture in the tower at Reagan National, despite past efforts to improve compliance with safety standards. 'I think there were some things that we missed, to be quite honest with you, not intentionally, but I was talking about how certain facilities can drift,' McIntosh said. Homendy told McIntosh she believes agency leaders are sincere about wanting to improve safety, but the solution must be more than just sending a top-down message of safety and also actually listening to controllers in the field. Questions over lack of alcohol testing Tim Lilley, an aviation expert whose son Sam was a pilot on the passenger jet, said he's optimistic the tragic accident will ultimately lead to some positive changes. 'But we've got a long way to go,' he told The Associated Press. Lilley said he was particularly struck by the FAA's lack of alcohol testing for air traffic controllers after the crash. 'And they made a bunch of excuses why they didn't do it,' Lilley said. 'None of them were valid. It goes back to a whole system that was complacent and was normalizing deviation.' Homendy said during Thursday's hearings that alcohol testing is most effective within two hours of a crash and can be administered within eight hours. Nick Fuller, the FAA's acting deputy chief operating officer of operations, testified that the controllers weren't tested because the agency did not immediately believe the crash was fatal. The FAA then decided to forgo it because the optimum two-hour window had passed. Controller didn't warn the jet FAA officials testified this week that an air traffic controller should have warned the passenger jet of the Army helicopter's presence. The controller had asked the Black Hawk pilots to confirm they had the airplane in sight because an alarm sounded in the tower about their proximity. The controller could see from a window that the helicopter was too close, but the controller did not alert the jetliner. In a transcript released this week, the unidentified controller said in a post-crash interview they weren't sure that would have changed the outcome. Additionally, the pilots of the helicopter did not fully hear the controller's instructions before the collision. When the controller told the helicopter's pilots to 'pass behind' the jet, the crew didn't hear it because the Black Hawk's microphone key was pressed at that moment. 'Layer after layer of deficiencies' Jeff Guzzetti, a former NTSB and FAA crash investigator, told the AP that a combination of factors produced this tragedy, like 'holes that line up in the Swiss cheese.' Any number of things, had they been different, could have prevented the collision, he said. They include the Black Hawks having more accurate altimeters, as well as a key piece of locating equipment, known as ADS-B Out, turned on or working. In turn, air traffic control could have seen the problem earlier. Just a few feet could have made a difference, Guzzetti said. 'It just goes to show you that an accident isn't caused by one single thing,' Guzzetti said. 'It isn't caused by 'pilot error' or 'controller staffing.' This accident was caused by layer after layer of deficiencies that piled up at just the right moment.' Ex-official: FAA and Army share blame Mary Schiavo, a former U.S. Department of Transportation Inspector General, told the AP that both the Army and the FAA appear to share significant blame. The Black Hawks' altimeters could be off by as much as 100 feet and were still considered acceptable, she said. The crew was flying an outdated model that struggled to maintain altitude, while the helicopter pilots' flying was 'loose' and under 'loose' supervision. 'It's on the individuals, God rest their souls, but it's also on the military,' Schiavo said. 'I mean, they just seem to have no urgency of anything.' Schiavo was also struck by the air traffic controllers' lack of maps of the military helicopter routes on their display screens, which forced them to look out the window. 'And so everything about the military helicopter operation was not up to the standards of commercial aviation ... it's a shocking lack of attention to precision all the way around,' she said. Schiavo also faulted the FAA for not coming off as terribly responsive to problems. 'I called the Federal Aviation Administration, the Tombstone Agency, because they would only make change after people die,' Schiavo said. 'And sadly, 30 years later, that seems to still be the case.'
CBS News
4 hours ago
- CBS News
Colorado firefighting plane makes emergency landing due to mechanical issue with landing gear
A firefighting plane in Colorado had to make an emergency landing without the landing gear working properly on Friday. According to the Colorado Department of Fire Prevention and Control, the Pilatus PC-12 Multi-Mission Aircraft was returning from a detection mission along the western slope when the flight crew discovered a problem with the plane's nose landing gear. They declared an emergency as a precautionary measure and brought the plane in to land at Grand Junction Regional Airport. Despite the nose landing gear not locking into place, they were able to execute a controlled landing, bringing the aircraft to a stop on the runway. Officials said that no one was injured during the incident. They said the emergency landing will be investigated according to FAA and NTSB protocols.
New York Times
8 hours ago
- New York Times
Army Pilots Might Have Struggled to See Passenger Jet Before D.C. Crash
Before an Army Black Hawk crashed into a passenger jet on the night of Jan. 29, the helicopter pilots told the air traffic controller guiding them near Ronald Reagan National Airport that they saw a nearby jet and would steer clear of it. But experienced Army aviators told the National Transportation Safety Board during hearings on Friday that American Airlines Flight 5342 might have been difficult for the helicopter pilots to keep in their sights. Federal investigators will release their findings early next year about the cause of the midair collision, which killed 67 people — the worst airplane crash in the United States in nearly a quarter-century. But one question is whether the Army pilots ever actually saw the airplane that the air traffic controller flagged in his communications with them that night. In their testimony Friday, Army experts explained why that might have been difficult for the pilots, Capt. Rebecca M. Lobach, who was undergoing her annual flight evaluation, and her instructor, Chief Warrant Officer 2 Andrew Loyd Eaves. At night, light pollution from Washington, the Pentagon and the airport itself is a common problem for pilots. It can be worse when flying with night-vision goggles, as the Army pilots were using on the night of the crash, the aviators said. Further complicating matters were exterior lights on the commercial jet that were dimmer than those on more modern planes. Even the configuration of the Black Hawks can cause sightline problems. All those factors could have complicated the Black Hawk pilots' ability to keep their eyes on the correct airplane, even after telling the air traffic controller they could see it. Want all of The Times? Subscribe.
