# NTSB CEN13CA142: Cessna 172S, N5113J, Peoria, IL, January 24, 2013 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: January 23, 2013, 20:50 local (Jan 24, 2013, 02:50 UTC) - Place: Peoria, IL - Coordinates: 40.664165, -89.693336 - Nearby events: https://openairdocs.org/map.md?lat=40.6642&lon=-89.6933&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining event: [Takeoff: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report June 19, 2013 - Report: Approved by Office Director - NTSB office: Central Region - Parties: FAA-Springfield FSDO - NTSB case key (mKey): 86077 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN13CA142 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/86077/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=86077 - Page: https://openairdocs.org/ntsb/CEN13CA142 ## Probable cause The pilot’s inadvertent activation of the electric trim to the nose-down position, which resulted in the airplane being improperly configured for takeoff, and the flight instructor’s incorrect remedial action that allowed the airplane to porpoise. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Instructor/check pilot (probable cause); cases with it: [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters: configuration](https://openairdocs.org/ntsb-findings/01062017): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [All aircraft, 80 cases](https://openairdocs.org/ntsb-findings/01062017/cases.md) - [Performance/control parameters: pitch control](https://openairdocs.org/ntsb-findings/01062022): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [All aircraft, 526 cases](https://openairdocs.org/ntsb-findings/01062022/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Takeoff: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Takeoff-rejected takeoff: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md) - [Takeoff-rejected takeoff: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The private pilot reported that during the takeoff, shortly after rotation, the airplane’s nose pitched downward and the airplane bounced on the runway. He stated that after the first bounce, the flight instructor took control and that the airplane bounced several more times before coming to rest on its nose. The flight instructor reported that preflight and pretakeoff checks were performed, no airplane deficiencies were noted, and the elevator trim was set for takeoff. He added that he took control after the first bounce and attempted to abort the takeoff. The airplane bounced violently four or five more times. The flight instructor attempted to stop the airplane by retarding the throttle, applying up elevator for aerodynamic braking, and trying to keep the nosewheel off of the ground. The airplane’s nose landing gear had collapsed and the firewall and fuselage had sustained damage. Although the flight instructor said that the elevator trim was set for takeoff, postaccident examination of the airplane revealed that the elevator trim was in the full nose-down position. Although it could not be definitively determined, it is likely that the pilot inadvertently actuated the electric trim switch on the yoke before takeoff. Examination of the airplane's control system revealed no anomalies that existed before the accident that would have precluded normal operation. ## Factual narrative The private pilot reported that after the airplane rotated for takeoff, the nose pitched downward and the airplane bounced on the runway. He stated that after the first bounce, the flight instructor took control and the airplane bounced several more times before coming to rest on its nose. The flight instructor reported that pre-flight and pre-takeoff checks were performed, no airplane deficiencies were noted, and the elevator trim was set for takeoff. He added that he took control after the first bounce and attempted to abort the takeoff. The airplane bounced violently four or five more times as he attempted to stop the airplane by retarding the throttle, applying up elevator for aerodynamic braking, and trying to keep the nosewheel off of the ground. Examination of the airplane after the accident revealed that the elevator trim was in the full nose down position. The airplane’s nose landing gear had collapsed and the firewall and fuselage had sustained damage. The lower portion of the fuselage/firewall was pushed rearward into the pilot compartment displacing the rudder pedals. Tests of the elevator trim system revealed no anomalies. Examination of the airplane's control system revealed no anomalies that existed prior to the accident. Federal Aviation Administration publication FAA-H-8083-3A, “Airplane Flying Handbook” stated the following in regard to recovery from a bounced landing: “The corrective action for a bounce is the same as for ballooning and similarly depends on its severity. When it is very slight and there is no extreme change in the airplane’s pitch attitude, a follow-up landing may be executed by applying sufficient power to cushion the subsequent touchdown, and smoothly adjusting the pitch to the proper touchdown attitude.” ## Aircraft - Registration: N5113J (not matched to a registry record) - Reported make and model: CESSNA 172S - Category: Airplane - Serial number: 172S10925 - Airframe hours: 1480 - Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: University Of Dubuque - Registered owner: University Of Dubuque - Airworthiness certificate: Standard, Normal - Last inspection: Annual, November 7, 2012 - Departed: PIA, Peoria, IL - Destination: DBQ, Dubuque, IA - Airport: PIA, Peoria International Airport, runway 31, 10,104 × 150 ft, concrete ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 20; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review December 11, 2012; seat: left; flight hours: 96 total, 2 in this make and model, 12 as pilot in command, 16 in the last 90 days, 2 in the last 30 days, 2 in the last 24 hours - Flight instructor; age 21; injuries: none; flight instructor, commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review May 3, 2012; seat: right; flight hours: 494 total, 155 in this make and model, 342 as pilot in command, 16 in the last 90 days, 2 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Night - Wind: 330° at 10 knots, gusting 19 - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 23 °F, dew point 9 °F - Altimeter: 30.23 inHg - Observed at: PIA ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20130123000599A](https://openairdocs.org/incident/20130123000599A), Jan 23, 2013: Cessna 172S, Peoria, IL, Substantial damage. Upon rotation, the aircraft reached an altitude of approximately 10 feet then abruptly decended back onto the runway. The aircraft bounced several times,… ## Docket (2 files) The files NTSB released with the investigation on April 29, 2013, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=86077. 3.4 MB in all. - Record of Conversation with FAA Inspector (item 1, .PDF, 25 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40390486&FileExtension=.PDF&FileName=Record%20of%20Conversation%20with%20FAA%20Inspector-Master.PDF - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 2, .PDF, 3.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40390488&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.