# NTSB CEN10CA025: Cessna 172S, N519ND, Grand Forks, ND, October 20, 2009 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: October 20, 2009, 12:20 local (17:20 UTC) - Place: Grand Forks, ND - Coordinates: 47.947223, -97.173889 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=47.9472&lon=-97.1739&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report April 19, 2010 - Report: Approved by Office Director - NTSB office: Central Region - Parties: Federal Aviation Administration - Fargo FSDO - NTSB case key (mKey): 74944 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN10CA025 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/74944/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=74944 - Page: https://openairdocs.org/ntsb/CEN10CA025 ## Probable cause The student pilot's improper landing flare and recovery from a bounced landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Cessna 172S, 99 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072439), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172S, 206 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072439), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Cessna 172S, 102 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072439), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) - [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); cases with it: [Cessna 172S, 77 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072439), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) ## Analysis The accident occurred during the student pilot's second landing on his first solo flight. He stated that the airplane was on a stabilized approach as it crossed over the runway threshold at 63 knots. He reduced engine power and began to flare as the airplane was abeam the Precision Approach Path Indicator (PAPI) system. He reported that the landing flare was "somewhat short" and that the airplane landed hard on its main landing gear. He reduced his back pressure on the control yoke and the nose wheel contacted the runway. The airplane then bounced several times, alternating between the nose and main landing gear, before stabilizing on a landing rollout. A postaccident inspection of the aircraft revealed the lower engine firewall and forward floorboards were substantially deformed. The student pilot reported that there were no preimpact mechanical malfunctions or failures that would have precluded normal operation of the airplane. ## Factual narrative The accident occurred during the student pilot's second landing on his first solo flight. He stated that the airplane was on a stabilized approach as it crossed over the runway threshold at 63 knots. He reduced engine power and began his landing flare as the airplane was abeam the Precision Approach Path Indicator (PAPI) system. He reported that the landing flare was "somewhat short" and that the airplane landed hard on its main landing gear. He reduced his backpressure on the control yoke and the nose wheel contacted the runway. The airplane then bounced several times, alternating between the nose and main landing gear, before stabilizing on a landing rollout. An after-flight inspection revealed the lower engine firewall and forward floorboards were substantially deformed. The student pilot reported that there were no preimpact mechanical malfunctions or failures that would have precluded normal operation of the airplane. ## Aircraft - Registration: [N519ND](https://openairdocs.org/aircraft/N519ND), registered now, S/N 172S10810, built 2008 (OpenAirDocs) - Reported make and model: CESSNA 172S - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S10810 - Airframe hours: 992 - Engines: Lycoming IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: UND Aerospace Foundation - Registered owner: UND Aerospace Foundation - Airworthiness certificate: Standard, Normal - Last inspection: AAIP, October 13, 2009 - Departed: KGFK, Grand Forks, ND - Destination: KGFK, Grand Forks, ND - Airport: KGFK, Grand Forks International, runway 35L, 7,349 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 19; injuries: none; student; medical: class 2, without waivers/limitations; seat: left; flight hours: 19 total, 19 in this make and model, 1 as pilot in command, 19 in the last 90 days, 12 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 110° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: 3,500 ft overcast - Temperature: 45 °F, dew point 39 °F - Altimeter: 30.13 inHg - Observed at: KGFK ## 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 20091020050699A](https://openairdocs.org/incident/20091020050699A), Oct 20, 2009: Cessna 172S, Grand Forks, ND, Substantial damage. On October 20, 2009, at approximately 1220 hours, central daylight time, a Cessna 172S aircraft, N519ND, operated by a student pilot, sustained substantial… ## Docket (1 files) The files NTSB released with the investigation on January 19, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=74944. 532 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 532 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40323770&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.