The U.S. aircraft register, updated daily
Accidents · NTSB NYC06LA033 · Final report

Boeing 737-800 accident near State College, Pennsylvania, November 20, 2005

On November 20, 2005 at about 3:18 am local time, a Boeing 737-800, registered N734MA, was substantially damaged in an accident near State College, Pennsylvania (University Park Airport). It was flown under scheduled airline rules (Part 121). No one was hurt; 127 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
November 20, 2005 · about 3:18 am local time
Place
State College, Pennsylvania · University Park Airport · map
Type
Accident
Injuries
No one was hurt; 127 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Boeing 737-800 · all 737-800s on the register
Registration
N734MA · registry record · serial 30039
Damage
Substantial damage
Flight
Flight · scheduled airline rules (Part 121)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane; instrument: helicopter; rotorcraft: helicopter
  • Flight time: 8,141 hours in all; 1,258 in this make and model; 113 in the last 90 days; 71 in the last 30 days; 5,575 as pilot in command
  • Last flight review: November 1, 2004
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 3,072 hours in all; 105 in the last 90 days; 52 in the last 30 days; 748 as pilot in command
  • Last flight review: November 1, 2005
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 17,022 hours
  • Last inspection: continuous airworthiness programme, September 1, 2005; 381 hours since
  • Maximum gross weight: 79,242 lb
  • Seats: 183
  • Landing gear: retractable
  • Engine 1: Cfm International CFM56-7B26 (turbofan); 0 hours total
  • Engine 2: Cfm International CFM56-7B26 (turbofan); 0 hours total
  • Operator: Miami Air International

The flight

  • Departed from: LAN Lansing MI at 1:20 am
  • Destination: UNV State College PA
  • Flight plan: IFR
  • Runway 24, 6,701 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: night
  • Wind: from 260° at 4 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 37°F (3°C), dew point 21°F (-6°C)
  • Altimeter: 30.23 inHg
  • Observation at 3:20 am from UNV

Injuries

FatalSeriousMinorNone
Crew7
Passengers120

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.