Tailstrike Accident Boeing 737-8Q8 (WL) N734MA,
ASN logo
ASN Wikibase Occurrence # 292824
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Saturday 19 November 2005
Time:23:18 LT
Type:Silhouette image of generic B738 model; specific model in this crash may look slightly different    
Boeing 737-8Q8 (WL)
Owner/operator:Miami Air International
Registration: N734MA
MSN: 30039/701
Year of manufacture:2000
Fatalities:Fatalities: 0 / Occupants: 127
Aircraft damage: Substantial
Category:Accident
Location:State College, Pennsylvania -   United States of America
Phase: Unknown
Nature:Passenger
Departure airport:Lansing-Capital Region International Airport, MI (LAN/KLAN)
Destination airport:State College-University Park Airport, PA (SCE/KUNV)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
During the approach, the captain had disconnected the autopilot, but had left the autothrottles engaged in what is known as "mixed-mode" method of flight control in which control of the flight path is mixed between manual and automatic means. During this time, the autothrottle began to track an airspeed which had been previously selected in the mode control panel speed window. The captain disconnected the autothrottles, but did not retard the throttles to idle. Therefore, automatic speedbrake deployment did not take place during the first touchdown. During the resultant bounce, the captain then retarded the thrust levers to idle, the speedbrakes deployed, there was a loss of lift and nose up pitching moment, and a tailstrike resulted. The airplane manufacturer recommended autothrottle use only when the autopilot was engaged. They also advised if the airplane bounced while landing, the pilot should hold or re-establish a normal landing attitude and add thrust as necessary to control the rate of descent, and that thrust need not be added for a "shallow skip or bounce," however, if a "high, hard bounce" occurred, the pilot should initiate a go-around. Information concerning the dangers of mixed-mode operations and bounced landing recovery was available to the operator and Federal Aviation Administration (FAA); however there were no prohibition on mixed-mode operations, nor were bounced landing recovery guidance required to be listed in any of the operator's FAA approved manuals. Two months prior to the accident, the Safety Board issued a recommendation to the FAA; to require air carriers to incorporate bounced landing recovery techniques in their flight manuals and to teach these techniques during training. As a result the FAA issued a Safety Alert for Operators (SAFO), which "recommended" each airline, include bounced landing recovery techniques in their manuals and training; however since the SAFO was not mandatory, the Safety Board requested the FAA survey air carriers to establish how many had adopted the SAFO. The Safety Board advised the FAA that until the results of the SAFO were known, the Safety Board's recommendation would remain classified; Open Acceptable Response.

Probable Cause: The pilot's improper touchdown and recovery from a bounced landing. Factors to the accident were the operator's failure to provide sufficient information on the use of autothrottles and bounced landing recovery techniques, along with the Federal Aviation Administration's failure to require the inclusion of mixed-mode flight control guidance and bounced landing recovery techniques in operator pilot training programs and flight manuals.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: 
Status: Investigation completed
Duration: 1 year and 10 months
Download report: Final report

Sources:

NTSB NYC06LA033

History of this aircraft

Other occurrences involving this aircraft
26 September 2018 S2-AJA US-Bangla Airlines 0 Chittagong-Shah Amanat International Airport (CGP) sub

Revision history:

Date/timeContributorUpdates
09-Oct-2022 09:35 ASN Update Bot Added

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org