NTSB Makes Safety Recommendations Stemming From 757 Runway Excursion | Aero-News Network
Aero-News Network
RSS icon RSS feed
podcast icon MP3 podcast
Subscribe Aero-News e-mail Newsletter Subscribe

** Airborne/NBAA2014 10.22.14 ** HD iPad-Friendly -- Airborne/NBAA2014 10.22.14 **
** Airborne/NBAA2014 10.21.14 ** HD iPad-Friendly -- Airborne/NBAA2014 10.21.14 **
** Airborne/NBAA2014 10.20.14 ** HD iPad-Friendly -- Airborne/NBAA2014 10.20.14 **

Thu, Jun 07, 2012

NTSB Makes Safety Recommendations Stemming From 757 Runway Excursion

Mechanical Defects And A Breakdown In Monitoring Procedures Cited In The Wyoming Incident In 2010

The NTSB met Tuesday to develop a set of safety recommendations stemming from a 2010 runway excursion which occurred in Wyoming. On December 29, 2010, at about 1138 MST, American Airlines flight 2253, a Boeing 757-200, ran off the departure end of runway 19 during light snow after landing at Wyoming's Jackson Hole Airport (KJAC). The airplane came to rest about 730 feet past the departure end of the runway in deep snow. None of the 179 passengers and six crewmembers were injured; the airplane sustained minor damage. The flight originated from Chicago O'Hare Airport.

The board had earlier determined that mechanical defects that prevented the automatic deployment of speedbrakes, which assist in slowing the plane after landing, and the captain's failure to monitor and manually deploy them led to an overrun of a passenger jetliner off of a snowy runway. The incident was compounded by an anomaly with the thrust reversers.

"Through this investigation, all of us — the investigator, manufacturer, operator, and pilots, alike — all learned important safety lessons," Hersman said. "The recommendations we issue today will make valuable contributions to improving aviation safety."

The investigation found that the pilots, both of whom had flown into JAC on numerous occasions, were familiar with the challenging wintertime landing conditions there and had made thorough preparations for the approach and landing during what they described as an otherwise uneventful flight from Chicago.

The approach to the runway was normal and the airplane touched down about 600 feet beyond the approach threshold. The speedbrakes, which disrupt the airflow over the wings and greatly increase the wheel braking effectiveness, did not automatically deploy as designed. The CVR transcript showed that the captain, acting as the monitoring pilot, failed to identify the non-deployment and erroneously stated "deployed" shortly after touchdown. Immediately after this, the first officer, who was the pilot flying, tried to deploy the thrust reversers; when they did not initially deploy, the captain took over the thrust reverser controls and they deployed about 18 seconds after touchdown. Subsequently, the airplane continued off the departure end of the runway, coming to a stop in deep snow off the end of the paved surface.

American Airlines training and procedures require the pilot monitoring (in this case, the captain) to observe and call out the position of the speedbrake lever after landing; if the speedbrakes do not deploy automatically, the captain is to manually deploy them. Although the pilots could have manually deployed the speedbrakes at any time during the landing roll, neither pilot recognized that the speedbrakes had not automatically deployed because they were both trying to resolve the thrust reverser issue.

The landing performance analysis showed that under similar runway conditions, even without thrust reverser deployment, the airplane would have stopped about 4500 feet down the 6300-foot runway had the speedbrakes been promptly deployed.

The investigation revealed that the speedbrakes did not automatically deploy because of a latent assembly defect in one of the speedbrakes mechanisms. In addition, the NTSB determined that the thrust reversers did not initially deploy because of a rare mechanical/hydraulic interaction that occurred in the thrust reverser system as a result of an unloading event at the precise instant that the first officer commanded their deployment immediately after touchdown.

As a result of the investigation, the NTSB made the following new safety recommendations to the FAA: require that all transport category air carriers develop and incorporate training to address recognition of a situation in which the speedbrakes do not deploy as expected after landing; require all newly type-certificated air transport category airplanes to have an aural, or otherwise unique, alert that warns pilots that the speedbrakes have not deployed during the landing roll; and require Boeing to establish guidance for pilots of all relevant airplanes to follow when an unintended thrust reverser lockout occurs and to provide that guidance to all operators of those airplanes.

The NTSB also reiterated to the FAA three safety recommendations related to multiple emergency situation flight training and monitoring skills and workload management that it had made during investigations of previous accidents.

FMI: www.ntsb.gov

Advertisement

More News

Airborne at NBAA-10.22.14: Legacy 500, Universal InSight, BendixKing AeroWave

Also: GE Honda, Sagem's Active SideStick, Syberjet Update, Techno Aerospace Knows How to Party The FAA handed over certification papers for Embraer's Legacy 500 executive jet durin>[...]

ANN's Daily Aero-Linx (10.24.14)

Homebuilt Homepage: Clubs And Newsletters This page lists Homebuilt related Clubs and Newsletters.>[...]

ANN's Daily Aero-Term (10.24.14): Phase Separation – Aviation Fuel

Phase separation is when a combined liquid separates into two different liquids and may occur when autogas is used for aviation fuel.>[...]

Aero-News: Quote Of The Day (10.24.14)

“I’m excited and humbled by the trust that the ALPA Board of Directors has placed in me with this election.” Source: ALPA President-Elect Tim Canoll.>[...]

ANN FAQ: Q&A 101

A Few Questions AND Answers To Help You Get MORE Out of ANN!>[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

© 2007 - 2014 Web Development & Design by Pauli Systems, LC