
NTSB hearings will focus on fatal Army helicopter-passenger jet crash. Here's what to know
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 handling 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.
Here's a look at the crash, the investigation so far and other notable aircraft incidents this year.
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 at the time, which would put it above its 200-foot 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 but the instructor pilot saying 400 feet, 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.

Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles

Business Insider
44 minutes ago
- Business Insider
College wasn't right for me, so I joined the Marines. I was able to travel and avoid student loan debt.
Growing up in Memphis, I felt like I had to choose between college and the military. I decided to join the Marines because I wanted to travel and didn't want to wait four years. The Marines inspired me to be the person I am today, and it was the best option for me. Growing up in Memphis meant choosing between limited paths. If you were tall and skinny, you played basketball. Short and husky meant football. I loved soccer, but was talked out of it early. I tried basketball, but I never made the teams. I also tried my hand at rap, but I knew it would never pay the bills. Only two options were left for me: go to college or join the military. College was the default option, but I never planned for it. I also didn't want to wait four years to make money. When I took a step back, I realized all I wanted to do was travel and work. I asked myself: Why go to college when the military would let me do exactly that right now? I spent months researching the military The military offered adventure that college couldn't provide. The military appealed to me in ways college couldn't. I wanted structure and adventure, to serve something bigger while needing financial stability. College couldn't provide the experiences I craved. I wanted to ride helicopters, drive military trucks, and shoot machine guns. I wanted to live like an action star. The military would pay for education while providing immediate income. College meant student loan debt while waiting four years. When I finally decided on the military, I had to face the difficult choice of deciding which branch was right for me. I created pro and con charts, analyzing myself first and then each of the military branches. I also interviewed recruiters, veterans, and retirees. My decision narrowed down to the Marines or the Army. Unable to decide, I prayed for guidance. That night, I dreamed of myself wearing the blue uniforms, marching with a rifle. When I woke up, I had my answer. The dream told me I was already a Marine. Joining the military was one of the best decisions of my life People in my life tried to dissuade me from joining the Marines, worried I'd be sent to the front lines. But joining gave me the leg up I needed in life and let me live my childhood dreams. I got to be G.I. Joe in the real world. The military introduced me to incredible people and changed my outlook on many things. For example, I didn't like kids before joining, but the service opened me up to them. The Marines also helped me realize that my true dreams lay in travel. I would've never learned that if I stayed in the US on a college campus. I'd planned to do 20 years, but I departed early because I wanted to pursue a nomadic lifestyle. The military taught me I'm in control of my own life Thanks to the military, I have no student loan debt, so I'm free financially. With patience, initiative, and education, you can make anything happen. I had glimpses of this before the military, but service molded these traits in me. My decision to join the military instead of attending college allowed me to become someone I never could have imagined. It gave me the confidence to handle whatever life throws at me and showed me that the path that scares everyone else is often the path you're meant to take.

9 hours ago
Broken altimeter, ignored warnings: Hearings reveal what went wrong in DC crash that killed 67
Over three days of sometimes contentious hearings this week, the National Transportation Safety Board interrogated Federal Aviation Administration and Army officials about a list of things that went wrong and contributed to a Black Hawk helicopter and a passenger jet colliding over Washington, D.C., killing 67 people. The biggest revelations: The helicopter's altimeter gauge was broken, and controllers warned the FAA years earlier about the dangers that helicopters presented. At one point NTSB Chairwoman Jennifer Homendy scolded the FAA for not addressing safety concerns. 'Are you kidding me? Sixty-seven people are dead! How do you explain that? Our bureaucratic process?' she said. 'Fix it. Do better.' Victims of the January crash included a group of elite young figure skaters, their parents and coaches and four union steamfitters from the Washington area. Here is a look at the major takeaways from the hearings about the collision, which alarmed travelers before a string of other crashes and close calls this year added to their worries about flying: The helicopter was flying at 278 feet (85 meters) — well above the 200-foot (61-meter) ceiling on that route — when it collided with the airliner. But investigators said the pilots might not have realized that because the barometric altimeter they were relying on was reading 80 to 100 feet (24 to 30 meters) lower than the altitude registered by the flight data recorder. The NTSB subsequently found similar discrepancies in the altimeters of three other helicopters from the same unit. An expert with Sikorsky, which makes the Black Hawks, said the one that crashed was an older model that lacked the air data computers that make for more accurate altitude readings in newer versions. Army Chief Warrant Officer Kylene Lewis told the board that an 80- to 100-foot (24- to 30-meter) discrepancy between the different altimeters on a helicopter would not be alarming, because at lower altitudes she would be relying more on the radar altimeter than the barometric altimeter. Plus Army pilots strive to stay within 100 feet (30 meters) of target altitude on flights, so they could still do that even with their altimeters that far off. But Rick Dressler of medevac operator Metro Aviation told the NTSB that imprecision would not fly with his helicopters. When a helicopter route like the one the Black Hawk was flying that night includes an altitude limit, Dressler said, his pilots consider that a hard ceiling. Both tried to deflect responsibility for the crash, but the testimony highlighted plenty of things that might have been done differently. The NTSB's final report will be done next year, but there likely will not be one single cause identified for the crash. 'I think it was a week of reckoning for the FAA and the U.S. Army in this accident,' aviation safety consultant and former crash investigator Jeff Guzzetti said. Army officials said the greater concern is that the FAA approved routes around Ronald Reagan International Airport with separation distances as small as 75 feet (23 meters) between helicopters and planes when planes are landing on a certain runway at Reagan. 'The fact that we have less than 500-foot separation is a concern for me,' said Scott Rosengren, chief engineer in the office that manages the Army's utility helicopters. Army Chief Warrant Officer David Van Vechten said he was surprised the air traffic controller let the helicopter proceed while the airliner was circling to land at Reagan's secondary runway, which is used when traffic for the main runway stacks up and accounts for about 5% of flights. Van Vechten said he was never allowed to fly under a landing plane as the Black Hawk did, but only a handful of the hundreds of times he flew that route involved planes landing on that runway. Other pilots in the unit told crash investigators it was routine to be directed to fly under landing planes, and they believed that was safe if they stuck to the approved route. Frank McIntosh, the head of the FAA's air traffic control organization, said he thinks controllers at Reagan 'were really dependent upon the use of visual separation' to keep traffic moving through the busy airspace. The NTSB said controllers repeatedly said they would just 'make it work.' They sometimes used 'squeeze plays' to land planes with minimal separation. On the night of the crash, a controller twice asked the helicopter pilots whether they had the jet in sight, and the pilots said they did and asked for visual separation approval so they could use their own eyes to maintain distance. Testimony at the hearing raised serious questions about how well the crew could spot the plane while wearing night vision goggles and whether the pilots were even looking in the right spot. The controller acknowledged in an interview that the plane's pilots were never warned when the helicopter was on a collision path, but controllers did not think telling the plane would have made a difference at that point. The plane was descending to land and tried to pull up at the last second after getting a warning in the cockpit, but it was too late. An FAA working group tried to get a warning added to helicopter charts back in 2022 urging pilots to use caution whenever the secondary runway was in use, but the agency refused. The working group said 'helicopter operations are occurring in a proximity that has triggered safety events. These events have been trending in the wrong direction and increasing year over year.' Separately, a different group at the airport discussed moving the helicopter route, but those discussions did not go anywhere. And a manager at a regional radar facility in the area urged the FAA in writing to reduce the number of planes taking off and landing at Reagan because of safety concerns. The NTSB has also said the FAA failed to recognize a troubling history of 85 near misses around Reagan in the three years before the collision, NTSB Chairwoman Jennifer Homendy said 'every sign was there that there was a safety risk and the tower was telling you that.' But after the accident, the FAA transferred managers out of the airport instead of acknowledging that they had been warned. 'What you did is you transferred people out instead of taking ownership over the fact that everybody in FAA in the tower was saying there was a problem,' Homendy said. 'But you guys are pointing out, 'Welp, our bureaucratic process. Somebody should have brought it up at some other symposium.''
Yahoo
12 hours ago
- Yahoo
Broken altimeter, ignored warnings: Hearings reveal what went wrong in DC crash that killed 67
APTOPIX Aircraft Down Investigation Over three days of sometimes contentious hearings this week, the National Transportation Safety Board interrogated Federal Aviation Administration and Army officials about a list of things that went wrong and contributed to a Black Hawk helicopter and a passenger jet colliding over Washington, D.C., killing 67 people. The biggest revelations: The helicopter's altimeter gauge was broken, and controllers warned the FAA years earlier about the dangers that helicopters presented. At one point NTSB Chairwoman Jennifer Homendy scolded the FAA for not addressing safety concerns. 'Are you kidding me? Sixty-seven people are dead! How do you explain that? Our bureaucratic process?' she said. 'Fix it. Do better.' Victims of the January crash included a group of elite young figure skaters, their parents and coaches and four union steamfitters from the Washington area. Here is a look at the major takeaways from the hearings about the collision, which alarmed travelers before a string of other crashes and close calls this year added to their worries about flying: The helicopter's altimeter was wrong The helicopter was flying at 278 feet (85 meters) — well above the 200-foot (61-meter) ceiling on that route — when it collided with the airliner. But investigators said the pilots might not have realized that because the barometric altimeter they were relying on was reading 80 to 100 feet (24 to 30 meters) lower than the altitude registered by the flight data recorder. The NTSB subsequently found similar discrepancies in the altimeters of three other helicopters from the same unit. An expert with Sikorsky, which makes the Black Hawks, said the one that crashed was an older model that lacked the air data computers that make for more accurate altitude readings in newer versions. Army Chief Warrant Officer Kylene Lewis told the board that an 80- to 100-foot (24- to 30-meter) discrepancy between the different altimeters on a helicopter would not be alarming, because at lower altitudes she would be relying more on the radar altimeter than the barometric altimeter. Plus Army pilots strive to stay within 100 feet (30 meters) of target altitude on flights, so they could still do that even with their altimeters that far off. But Rick Dressler of medevac operator Metro Aviation told the NTSB that imprecision would not fly with his helicopters. When a helicopter route like the one the Black Hawk was flying that night includes an altitude limit, Dressler said, his pilots consider that a hard ceiling. FAA and Army defend actions, shift blame Both tried to deflect responsibility for the crash, but the testimony highlighted plenty of things that might have been done differently. The NTSB's final report will be done next year, but there likely will not be one single cause identified for the crash. 'I think it was a week of reckoning for the FAA and the U.S. Army in this accident,' aviation safety consultant and former crash investigator Jeff Guzzetti said. Army officials said the greater concern is that the FAA approved routes around Ronald Reagan International Airport with separation distances as small as 75 feet (23 meters) between helicopters and planes when planes are landing on a certain runway at Reagan. 'The fact that we have less than 500-foot separation is a concern for me,' said Scott Rosengren, chief engineer in the office that manages the Army's utility helicopters. Army Chief Warrant Officer David Van Vechten said he was surprised the air traffic controller let the helicopter proceed while the airliner was circling to land at Reagan's secondary runway, which is used when traffic for the main runway stacks up and accounts for about 5% of flights. Van Vechten said he was never allowed to fly under a landing plane as the Black Hawk did, but only a handful of the hundreds of times he flew that route involved planes landing on that runway. Other pilots in the unit told crash investigators it was routine to be directed to fly under landing planes, and they believed that was safe if they stuck to the approved route. Frank McIntosh, the head of the FAA's air traffic control organization, said he thinks controllers at Reagan 'were really dependent upon the use of visual separation' to keep traffic moving through the busy airspace. The NTSB said controllers repeatedly said they would just 'make it work.' They sometimes used 'squeeze plays' to land planes with minimal separation. On the night of the crash, a controller twice asked the helicopter pilots whether they had the jet in sight, and the pilots said they did and asked for visual separation approval so they could use their own eyes to maintain distance. Testimony at the hearing raised serious questions about how well the crew could spot the plane while wearing night vision goggles and whether the pilots were even looking in the right spot. The controller acknowledged in an interview that the plane's pilots were never warned when the helicopter was on a collision path, but controllers did not think telling the plane would have made a difference at that point. The plane was descending to land and tried to pull up at the last second after getting a warning in the cockpit, but it was too late. FAA was warned about the dangers of helicopter traffic in D.C. An FAA working group tried to get a warning added to helicopter charts back in 2022 urging pilots to use caution whenever the secondary runway was in use, but the agency refused. The working group said 'helicopter operations are occurring in a proximity that has triggered safety events. These events have been trending in the wrong direction and increasing year over year.' Separately, a different group at the airport discussed moving the helicopter route, but those discussions did not go anywhere. And a manager at a regional radar facility in the area urged the FAA in writing to reduce the number of planes taking off and landing at Reagan because of safety concerns. The NTSB has also said the FAA failed to recognize a troubling history of 85 near misses around Reagan in the three years before the collision, NTSB Chairwoman Jennifer Homendy said 'every sign was there that there was a safety risk and the tower was telling you that.' But after the accident, the FAA transferred managers out of the airport instead of acknowledging that they had been warned. 'What you did is you transferred people out instead of taking ownership over the fact that everybody in FAA in the tower was saying there was a problem,' Homendy said. 'But you guys are pointing out, 'Welp, our bureaucratic process. Somebody should have brought it up at some other symposium.'' ___ Associated Press writer Leah Askarinam contributed. Solve the daily Crossword