logo
Cause of failed Alaska Airlines landing gear that sent passengers screaming revealed

Cause of failed Alaska Airlines landing gear that sent passengers screaming revealed

New York Post30-05-2025
Nearly two years after passengers screamed while sparks flew down a runway during the landing of an Alaska Airlines flight, the cause has been revealed.
A final report by the National Transportation Safety Board (NTSB) released on Tuesday points to 'incorrect' maintenance work.
Advertisement
The flight, which departed from Seattle, Washington, made a hard touchdown in Santa Ana, Calif., during Tropical Storm Hilary after the left main landing gear collapsed on touchdown.
Video recorded by a passenger captured the plane slamming into the ground at high speed. Sparks were seen flying as the plane appeared to drag its left wing along the tarmac.
Investigators revealed that the incident was caused by a 'fatigue crack' of a metal trunnion pin, which is part of the left landing gear.
The fracture formed from excessive grinding during a 2018 maintenance overhaul, which introduced heat damage to the metal. While the crack was initially not visible, it grew over time and ultimately 'caused the pin to fracture during landing,' the NTSB report said.
Advertisement
5 First responders help passengers disembark the Alaska Airlines 737 after the rough landing at John Wayne Airport on Aug. 20, 2023.
Orange County Fire Authority
5 Alaska Airlines flight 1288 sits on the tarmac after
Orange County Fire Authority
'Results of this examination and previous NTSB investigations demonstrate that even relatively mild heat exposure from grinding and/or machining during overhaul can lead to cracking, which can lead to fatigue crack growth and failed landing gear components, as occurred in this accident,' the report stated.
The report added that the pin had endured more than 4,000 landing cycles since undergoing the 2018 maintenance work.
Advertisement
The crack itself had likely been present for approximately 800 landing cycles, the NTSB found.
5 A passenger aboard the flight captured the moment the plane sparked during the landing.
bhi Amineni/Youtube
5 Sparks and smoke shoot off the plane after the landing in Orange County, California.
bhi Amineni/Youtube
Although the aircraft sustained substantial damage from the hard landing, all 112 passengers and crew members were able to deplane safely and without injury.
Advertisement
Alaska Airlines previously said, 'our focus is taking care of our guests who were on board, including retrieving their checked bags.'
'We apologize for the inconvenience and appreciate their patience during this situation.'
5 Although the aircraft sustained substantial damage from the hard landing, all 112 passengers and crew members were able to deplane safely and without injury.
Orange County Fire Authority
Alaska Airlines did not immediately respond to a request for comment from Fox News Digital.
Fox News' Chris Pandolfo contributed to this report.
Orange background

Try Our AI Features

Explore what Daily8 AI can do for you:

Comments

No comments yet...

Related Articles

U.S. probes Army helicopter altitude data in fatal January crash with jet
U.S. probes Army helicopter altitude data in fatal January crash with jet

CNBC

timean hour ago

  • CNBC

U.S. probes Army helicopter altitude data in fatal January crash with jet

The National Transportation Safety Board said on Wednesday that testing showed faulty altitude data in U.S. Army helicopters like the one that collided with an American Airlines plane on January 29, killing 67 near Ronald Reagan Washington National Airport. The NTSB investigative hearing is looking at the Black Hawk aircraft's air data systems and altimeters -- including the potential it received faulty altitude data -- as well as the Federal Aviation Administration's oversight of Washington airspace and air traffic. "There is a possibility that what the crew saw was very different than what the true altitude was," NTSB Chair Jennifer Homendy said. The crash -- a half-mile southeast of the airport over the Potomac River -- was the deadliest U.S. air disaster in more than 20 years. Testing after the crash showed that Army helicopters in flight showed discrepancies of 80 to 130 feet versus actual altitude. Army officials said discrepancies of up to 100 feet were not a cause for concern in the Sikorsky-Black Hawk. NTSB board member Todd Inman questioned why the Army was not doing more testing and more to alert pilots about potential discrepancies. "Could you hurry it up?" Inman said. Homendy said that discrepancy was significant, especially given the margin of error was 75 feet at the edge of the helicopter route near Reagan. She also questioned if broader testing was needed and whether the issue could impact civilian Sikorsky helicopters. The NTSB played audio excerpts of communications between air traffic control towers during the minutes before the crash, including a request by controllers to the American Airlines plane to shift to a different runway. Previously, the NTSB said the helicopter's altitude was higher than it should have been for the area at the time of the crash. The maximum altitude for the route the helicopter was taking was 200 feet but the collision occurred at an altitude of around 300 feet. The Black Hawk, which was on a nighttime training flight, had a crew of experienced pilots wearing night vision goggles. In May, the FAA barred the Army from helicopter flights around the Pentagon after a May 1 close call that forced two civilian planes to abort landings. The FAA this week said the helicopter flights remained on hold even after the agency disclosed it had signed a new agreement with the Army on July 1.

Black Hawk Crew in Deadly Crash Had Wrong Altitude Data, Safety Board Reveals
Black Hawk Crew in Deadly Crash Had Wrong Altitude Data, Safety Board Reveals

Epoch Times

time2 hours ago

  • Epoch Times

Black Hawk Crew in Deadly Crash Had Wrong Altitude Data, Safety Board Reveals

WASHINGTON—The crew of the Army Black Hawk helicopter that collided with a commercial jet earlier this year in the nation's deadliest aviation accident in more than two decades was operating with incorrect altitude data, the National Transportation Safety Board (NTSB) revealed on July 30. The information was released during the first day of a three-day 'fact-finding' hearing by the NTSB, which is probing the Jan. 29 crash.

Some air traffic controllers wanted to close a helicopter route near Washington's airport. It was abandoned as ‘too political.'
Some air traffic controllers wanted to close a helicopter route near Washington's airport. It was abandoned as ‘too political.'

Politico

time3 hours ago

  • Politico

Some air traffic controllers wanted to close a helicopter route near Washington's airport. It was abandoned as ‘too political.'

The FAA could not immediately be reached for comment. The documents were released Wednesday on the first day of a three-day fact-finding hearing into the crash, where significant attention focused on the limitations of instruments on the Black Hawk helicopter involved in the crash and the complicated and congested nature of the airspace around the airport. NTSB investigators grilled Army witnesses about the Black Hawk's altimeters, an instrument that helps pilots gauge how high above the ground an aircraft is flying. But the Black Hawk's altimeter can be inaccurate by up to 130 feet — about equal to how much higher the helicopter was flying than it should have been when the crash happened. Preliminary data shows that the helicopter had been flying at about 300 feet above the ground — about 100 feet higher than it should have been — placing it on a collision course with the passenger airplane as it tried to land. The Army largely downplayed concerns about the discrepancy, saying it was within the expected flight parameters of the helicopter's capabilities. U.S. Army Chief Warrant Officer Kylene Lewis, testifying on behalf of the branch, said a discrepancy of 100 feet wouldn't be a 'cause for alarm' and would be acceptable for military helicopter operations. Documents made public Wednesday also showed that air traffic controllers had cleared the helicopter to approach the airport even though the passenger jet was crossing its flight path. Helicopter pilots who routinely fly in to the airport interviewed by the NTSB said that controllers typically instructed helicopters to wait to approach that particular runway if there was a plane about to take off or land. According to transcripts and interviews part of the agency's investigation, helicopter pilots flying south down the Potomac River said they had previously been instructed by controllers overseeing commercial air traffic to hold until the plane had landed on the specific runway 'regardless of whether they had the traffic in sight.' That guidance from air traffic controllers, however, did not happen that night. A controller instead cleared the helicopter to approach and simply alerted the crew that a plane was inbound and it should pass behind it. The helicopter crew acknowledged that it had a plane in sight. Moments later, the two aircraft collided.

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