logo
NTSB hearings will focus on fatal Army helicopter-passenger jet crash. Here's what to know

NTSB hearings will focus on fatal Army helicopter-passenger jet crash. Here's what to know

WASHINGTON (AP) — The National Transportation Safety Board will hold three days of hearings starting Wednesday on January's midair collision between an American Airlines passenger jet and an Army helicopter over the nation's capital that killed 67 people.
The goal: Pinpoint exactly what went wrong and what can be done to avoid similar midair crashes between passenger planes and military aircraft. The accident was the nation's deadliest plane crash since November 2001.
The hearings in Washington will involve NTSB board members, investigators and witnesses. Panels will focus on military helicopter routes in the Washington area, collision avoidance technology and training for air traffic controllers at Ronald Reagan National Airport, among other subjects.
NTSB officials have already said the FAA failed to recognize a concerning pattern after there were 85 near misses in Washington airspace in just three years. The FAA has since banned some helicopter routes to make sure helicopters and planes no longer share the same airspace, but there have still been additional near misses in recent months.
Investigators have also said that the Army helicopter may have had inaccurate altitude readings, and the crew may not have heard key instructions from air traffic controllers.
Meanwhile, federal officials have raised concerns over the nation's overtaxed and understaffed air traffic control system. During January's mid-air crash above Washington, one controller was handing both commercial airline and helicopter traffic at the busy airport.
The hearings come at a time of heightened scrutiny of the safety of air travel amid the growing list of aircraft tragedies, mishaps and near misses in 2025. They include an Air India plane crash in June that killed at least 260 people as well as two unrelatedclose calls in the U.S. this month in which passenger jets took evasive action to avoid military planes.
What happened?
American Airlines Flight 5342 from Wichita, Kansas, was carrying 60 passengers and four crew members as it approached to land on a clear night at Ronald Reagan National Airport. Nearby, the Army Black Hawk, with three soldiers on board, was practicing emergency evacuation routes that would be used to ferry out key government officials in an emergency.
Investigators have said the helicopter crew was wearing night-vision goggles that would have limited their peripheral vision.
A few minutes before the twin-engine jet was to land, air traffic controllers asked if it could use a shorter runway. The pilots agreed, and flight-tracking sites show the plane turned to adjust its approach. The FAA has since permanently banned that particular helicopter route when planes are using that runway.
Shortly before the collision, a controller got an alert saying the plane and Black Hawk were converging and asked the helicopter if it had the jet in sight. The military pilot said yes and asked for 'visual separation' with the jet for a second time, allowing it to fly closer than if the pilots couldn't see the plane.
Controllers approved the request roughly 20 seconds before the collision.
The NTSB has said there were 85 dangerous close calls between planes and helicopters near Reagan National in the three years before the crash, and collision alarms had been ordering pilots to take evasive action at least once a month since 2011.
The investigation
NTSB Chairwoman Jennifer Homendy told reporters in February that the Black Hawk's cockpit recorder suggested an incomplete radio transmission may have left the crew unable to hear air traffic control tell them, just before the crash, to move behind the jet. She said the crew was unable to hear the words 'pass behind the' because its microphone key was pressed.
The radio altitude of the helicopter was 278 feet (85 meters) at the time, which would put it above its 200-foot (61-meter) limit for that location.
Cockpit conversations a few minutes before the crash indicate that the crew may not have had accurate altitude readings, with the helicopter's pilot calling out that they were at 300 feet (91 meters) but the instructor pilot saying 400 feet (122 meters), Homendy said.
That generation of Black Hawks typically has two types of altimeters: one relying on barometric pressure and the other on radio frequency signals bounced off the ground. Helicopter pilots typically rely on barometric readings while flying, but the helicopter's black box captures its radio altitude.
Almost immediately after the crash, President Donald Trump faulted the helicopter for flying too high. He also blamed federal diversity and inclusion efforts, particularly regarding air traffic controllers. When pressed by reporters, the president could not back up those claims. A few days later, he blamed an 'obsolete' air traffic control system.
January's crash prompted the Federal Aviation Administration in March to announce that helicopters would be permanently restricted from flying on the same route where the collision occurred.
However, concerns over Washington's airspace have persisted. On May 1, military air traffic controllers lost contact with an Army helicopter for about 20 seconds as it neared the Pentagon on a flight that caused two commercial jets to abort their landings. After that incident, the Army paused all flights into and out of the Pentagon as it works with the FAA to address safety issues.
The victims
The Army identified the Black Hawk crew as Capt. Rebecca M. Lobach, 28, of Durham, North Carolina; Staff Sgt. Ryan Austin O'Hara, 28, of Lilburn, Georgia; and Chief Warrant Officer 2 Andrew Loyd Eaves, 39, of Great Mills, Maryland. O'Hara was the crew chief, and Eaves and Lobach were pilots.
Among the jet's passengers were several members of the Skating Club of Boston who were returning from a development camp for elite junior skaters that followed the 2025 U.S. Figure Skating Championships in Wichita. A figure skating tribute event in Washington raised $1.2 million for the crash victims' families.
Others included a group of hunters returning from a guided trip in Kansas; four members of a steamfitters' union in suburban Maryland; nine students and parents from schools in Fairfax County, Virginia; and two Chinese nationals.
What about other crashes this year?
Besides the midair collision above Washington, a string of other recent crashes have brought attention to air travel, which remains overwhelmingly safe. The crashes include:
On Jan. 31 a medical transport jet crashed into a Philadelphia neighborhood, killing seven.
On Feb. 6 a small commuter aircraft went down off western Alaska, killing 10.
On Feb. 17, a Delta plane crashed and flipped over upon landing in Toronto but everyone survived. Two small planes collided in midair in Arizona on Feb. 19, killing two people.
On April 10, a New York City sightseeing helicopter broke apart in midair and crashed upside-down into the Hudson River, killing the pilot and a family of five Spanish tourists.
On April 11, three people were killed and one was injured when a small plane crashed in Boca Raton, Florida.
The crash of the Air India passenger plane in June occurred in the northwestern city of Ahmedabad, killing more than 240 people bound for London and others on the ground, officials said. A single passenger survived. The same month, a small plane crashed off the San Diego coast shortly after takeoff, killing all six people on board.
July included at least three fatal plane crashes. Two student pilots died when their single-engine planes crashed in midair south of Steinbach, in the Canadian province of Manitoba. A small plane crashed shortly after taking off from London Southend Airport, killing four people. A North Carolina family of four, including two school-age children, died when their small plane crashed as they flew back from Florida.
Orange background

Try Our AI Features

Explore what Daily8 AI can do for you:

Comments

No comments yet...

Related Articles

Tensions Flare Between Two Federal Agencies Charged With Aviation Safety
Tensions Flare Between Two Federal Agencies Charged With Aviation Safety

New York Times

timean hour ago

  • New York Times

Tensions Flare Between Two Federal Agencies Charged With Aviation Safety

The relationship between the National Transportation Safety Board, the government entity that investigates civilian airplane accidents, and the Federal Aviation Administration, the agency responsible for aviation safety, can frequently be contentious, especially after a major national tragedy. Last week, a rift between those two main regulators of aviation safety spilled out into public view. Frustrations — and sometimes tempers — flared in uncommonly raw fashion during the board's marathon of investigative hearings into the deadly midair crash between a military helicopter and a commercial jet near Ronald Reagan National Airport in January. Board members grilled witnesses, including air traffic controllers and F.A.A. managers, over three days and 30 hours of public testimony. Jennifer Homendy, the N.T.S.B. chair, led other board members in accusing the F.A.A. of knowingly stymieing efforts to improve safety at Reagan National Airport and stonewalling parts of the board's investigation into the crash. And Ms. Homendy directly accused the agency of fostering a culture among the air traffic control operation that discouraged employees from raising legitimate safety concerns, including by wielding the threat of retaliation. 'There is and always has been a healthy tension between the two agencies,' said Jeff Guzzetti, a former accident investigator for the F.A.A. and the N.T.S.B. And while the level of public outrage on display during board hearings depends largely on the proclivities of its members, he added, 'in this particular case, it's a shift.' Ms. Homendy and the other board members were careful not to direct their ire toward Sean Duffy, the transportation secretary, or Bryan Bedford, the F.A.A. administrator. Still, the very public airing of grievances raised questions about the working relationship between the two agencies at a critical juncture. The N.T.S.B. makes safety recommendations, but it is up to the F.A.A. to put them into place. The crash at Reagan National Airport, and a series of near misses and tower outages at major airports in the months since, have dampened public confidence in the safety of flying, intensifying the need for cooperation. 'Warning signs were ignored, or just not known or identified or sought, which is quite tragic,' Ms. Homendy told reporters late Wednesday, after the first day of testimony. In a statement, the F.A.A. said officials 'have and will continue to fully support the N.T.S.B.'s investigation,' stressing that the agency had been proactive about addressing concerns and adopting the board's early recommendations. The statement added that 'if there has been any stonewalling, withholding of information or intimidation — those actions will be identified and remedied without hesitation.' The gloves had already begun to come off in the final hours of the hearing on Wednesday. Ms. Homendy lost her patience with F.A.A. managers who claimed they never knew that air traffic officials from Reagan National Airport had urged higher-ups to address the potential risks posed by a helicopter route, known as Route 4, that crossed under the descent path for airplanes landing on a supplementary runway, No. 33. The Army Black Hawk that crashed into the commercial jet on Jan. 29 was flying along Route 4, and at the time of impact, was 78 feet higher than the F.A.A.-mandated ceiling of 200 feet. A number of witnesses testified that the devices pilots relied upon to measure their altitude frequently were off by about 100 feet of helicopters' actual flying height. Air traffic controllers, knowing the risks, sought to make changes as part of a helicopter-focused working group at the airport — but were told by district managers that doing so would be seen as 'too political,' according to the transcript of an interview included in an N.T.S.B. report. 'Every sign was there that there was a safety risk, and the tower was telling you that,' Ms. Homendy told F.A.A. officials. She accused agency managers of routinely dismissing safety concerns raised by employees in the airport's air traffic control tower and of reassigning people who had previously voiced concerns after the accident. She also said they used F.A.A. bureaucracy as an excuse to avoid making needed changes. 'Are you kidding me? Sixty-seven people are dead,' she said, denouncing the F.A.A.'s process for reviewing safety recommendations. 'Fix it. Do better,' she added. By the last day of the hearings, Ms. Homendy was accusing F.A.A. officials outright of trying to stymie the N.T.S.B.'s investigation by withholding documents and data the board had been requesting for months. 'I think you're interfering in the investigation,' she charged, 'because you're basically telling us 'no' every way you can.' Aviation safety experts said it was understandable for tensions to run unusually high after the collision because of the magnitude and rarity of the tragedy — it was the first fatal crash involving a major American airline in over 15 years. But part of the N.T.S.B.'s visible agitation in the hearings could also be strategic, those experts said. The fact that the crash happened just outside the nation's capital — along with the fact that power brokers from the Trump administration and Congress are eager to respond — has created a unique opportunity for the board to influence sweeping changes. 'The intensity has increased partly because of the visibility of this particular catastrophe and the proximity to Washington,' said Alan Diehl, a former aviation safety official with the N.T.S.B. and the F.A.A. 'By doing that, the N.T.S.B. hopes to convince both the F.A.A. and Congress that we need a revolution,' he added, 'in both personnel policies within the F.A.A. as well as the funding policies.' Ms. Homendy, who spent more than 14 years on Capitol Hill before President Trump nominated her to fill one of the Democratic slots on the board, has a keen understanding of Washington dynamics, according to board watchers. She is known for being more public-facing and, at times, being more comfortable adopting an adversarial posture than some of her predecessors. But she was not alone last week in being pointedly critical of the F.A.A. J. Todd Inman, a Republican member of the N.T.S.B, also accused the agency of stonewalling the investigation. The F.A.A. withheld documents about staffing at the control tower for months, he charged, dumping thousands of pages on the board on the Friday before the hearing, only after Ms. Homendy appealed to agency and Transportation Department leaders for help. At another point, Mr. Inman lost his patience with officials' promises to do better. 'We'd like to be treated privately the same way we are publicly,' he said. Mr. Inman also accused the F.A.A. of refusing to share critical data about real-time flight tracking technology, forcing the safety board to spend $50,000 annually to evaluate it 'because the F.A.A. does not consider N.T.S.B. a trusted government partner.' F.A.A. officials in the hot seat frequently defended their agency. Nick Fuller, the F.A.A.'s acting deputy chief operations officer, responded to allegations that the agency had withheld documents and data by arguing that some of the board's requests had been unclear, and that 'in fact, we just gave you the latest and greatest' information. Mr. Fuller also pushed back on accusations from all three presiding board members that after the Jan. 29 accident, the F.A.A. had removed managers at Reagan National's control tower who had previously raised concerns about traffic, staffing or other safety pitfalls. He argued that staffing changes had not been retaliatory, but rather executed in the interest of solving the problem quickly. 'I was given a task to fix the facility risk between helicopters and fixed wing,' Mr. Fuller said, referring to airplanes, 'and it wasn't to work through a collaborative process and allow a few months — it was to get the job done immediately.' On several occasions during the hearings, Ms. Homendy sought assurances that F.A.A. employees who were called as witnesses in the investigation would not be retaliated against for their testimony — a step prompted by reports that some who had critical things to say were being harassed, she told reporters on Thursday after that day's testimony. 'Nobody can take what is clearly a safety issue and get it up through the offices that should be making the decision to ensure safety in the airspace — or somebody's ignoring them,' she told reporters. 'You raise a red flag, and two things happen: You don't get it, you don't get the safety change that you have asked for, or you're transferred out after an accident occurs.' But experts warned against assuming that the acrimony of the hearing would disrupt the two agencies' expert staff members from being able to work together. 'Overall, the process is healthy,' said John Cox, a former airline pilot who runs a safety consulting firm. 'Is there friction? Yes. Is it normal? Yes. Was last week a little more so than normal? Yes,' he added. 'Will that encourage F.A.A. to move more quickly? I hope.'

United Airlines Pilot Issues ‘Mayday' After Reported Engine Failure Over Washington
United Airlines Pilot Issues ‘Mayday' After Reported Engine Failure Over Washington

Yahoo

time6 hours ago

  • Yahoo

United Airlines Pilot Issues ‘Mayday' After Reported Engine Failure Over Washington

A United Airlines flight carrying 230 people declared an emergency moments after taking off from Washington's Dulles International Airport, with an audio recording capturing the pilot's repeated 'mayday' call to air traffic control. Flight 108 was only moments into its June 25 ascent to Germany's Munich International Airport when its pilot reported an engine failure, according to a tower recording. 'Failure. Engine failure. Left Engine, United 108. Declaring an emergency. Mayday, mayday, mayday,' the pilot is heard saying in the recording obtained and published on YouTube by You Can See ATC. Air traffic control and the pilot discussed preparations for returning to the airport, including the need to dump fuel to adjust for the proper weight needed for landing, according to the audio. The Boeing 787-8 Dreamliner landed safely shortly after, with 'all passengers deplaned normally at the gate,' a spokesperson for United said in a statement Monday. 'The flight was subsequently canceled and we arranged alternate travel arrangements to take customers to their destination as soon as possible,' they said, while blaming the situation on a 'mechanical issue.' There were no disruptions to other flights, the Metropolitan Washington Airports Authority said in an email. The Federal Aviation Administration acknowledged the crew's report of possible engine issues in an email to HuffPost and said it is investigating. Related... NTSB Finds Army Chopper Was Flying Too High When It Collided With Plane Delta Pilot Arrested By Federal Agents After Landing Plane In San Francisco Passenger Plane Crashes In Russia's Far East Killing All 48 On Board SkyWest Plane Does 'Aggressive Maneuver' To Avoid Mid-Air Collision With B-52, Pilot Says

United Airlines Pilot Declared ‘Mayday' On Recent Flight—Nothing Unusual, Say Experts
United Airlines Pilot Declared ‘Mayday' On Recent Flight—Nothing Unusual, Say Experts

Forbes

time6 hours ago

  • Forbes

United Airlines Pilot Declared ‘Mayday' On Recent Flight—Nothing Unusual, Say Experts

A United Airlines pilot issued a mayday distress call after the Boeing 787 he was flying experienced engine failure shortly after taking off from Washington's Dulles airport for Munich on July 25, though 'mayday' calls are not unusual in aviation—letting air traffic controllers know when a flight needs priority handling. A United Airlines Boeing 737 airplane like this one suffered engine failure last month after taking off from Washington DC's Dulles airport. (Photo by Robert Alexander) Getty Images The flight 'returned to Washington Dulles shortly after takeoff to address a mechanical issue,' United Airlines confirmed in a statement shared with Forbes, adding that the plane landed safely, all passengers deplaned normally and the flight was subsequently canceled. 'Mayday' when repeated three times 'indicates imminent and grave danger and that immediate assistance is requested,' according to the Pilot/Controller Glossary published by the Federal Aviation Administration (FAA). 'That's by the book, exactly how it's to be done,' John Cox, aviation safety expert and retired commercial airline pilot, told Forbes of the United incident, adding that giving the mayday call tells air traffic controllers 'you need priority and to start moving airplanes away from you.' United Airlines flight 108 from Washington to Munich was operating a Boeing 787 with 219 passengers and 11 crew members on board, when one of the aircraft's two engines failed. 'Can the airplane fly just fine on a single engine? Yes, but that is something where you want to divert and get back on the ground,' Chad Kendall, an associate professor and FAA chief instructor in the Department of Aviation and Aerospace Science at Metropolitan State University of Denver, told Forbes. Pilots train repeatedly throughout their career for engine failure, multiple veteran pilots told Forbes. Air traffic controllers are used to 'mayday' calls, Cox told Forbes. 'And it's even more normal outside the U.S.' How Often Do Commercial Pilots Declare 'mayday'? 'Most of the public has probably seen a movie where there is a pilot in very dire straits using 'mayday, mayday, mayday,' but in terms of pilot training this is a phrase to convey the type of handling and resources from air traffic control that they need in a situation,' Kendall told Forbes. At least one other United Airlines flight issued a 'mayday' distress call last month, when a Boeing 737 on its way from Chicago O'Hare airport to Sarasota, Florida, on July 17 turned around after experiencing a mechanical issue, according to tower audio captured by Flight Follower. 375,000. That's the number of hours of operation per average turbine engine failure, according to the FAA. That translates to roughly one engine failure every 43 years of continuous flight. What Other Distress Calls Do Pilots Use? 'PAN-PAN,' repeated three times, 'indicates uncertainty or alert followed by the nature of the urgency,' according to the FAA's Pilot/Controller Glossary. 'PAN PAN is used in a lesser event, often for a mechanical issue that does not require urgency,' Kendall said. For example, in May, shortly after takeoff from New York's John F. Kennedy airport, a Lufthansa Airbus A340 crew reported that one of the aircraft's four engines failed while over the Atlantic, approximately 120 miles southeast of Boston. The pilot issued a 'PAN-PAN' distress call and requested to return to JFK, where it landed safely. Surprising Fact 'Mayday' comes from 'm'aidez,' which means 'help me' in French. The term 'PAN-PAN' originates from another French word, "panne,' which means "breakdown" or "failure." Both distress calls were adopted internationally in 1927. Further Reading Nervous About Flying? Here's How Aviation Safety Experts Mitigate Their Own Air Traffic Concerns (Forbes)

DOWNLOAD THE APP

Get Started Now: Download the App

Ready to dive into a world of global content with local flavor? Download Daily8 app today from your preferred app store and start exploring.
app-storeplay-store