# NTSB WPR10CA323: Cessna 172M, N64427, Twin Falls, ID, July 1, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: June 30, 2010, 20:08 local (Jul 1, 2010, 02:08 UTC) - Place: Twin Falls, ID - Coordinates: 42.481945, -114.487777 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=42.4819&lon=-114.4878&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report October 21, 2010 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 76508 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10CA323 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/76508/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=76508 - Page: https://openairdocs.org/ntsb/WPR10CA323 ## Probable cause The student pilot's improper landing flare. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Student/instructed pilot (probable cause); cases with it: [Cessna 172M, 123 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072418), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172M, 37 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072418), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/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: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [Cessna 172M, 30 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072418), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing-landing roll: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Cessna 172M, 10 cases](https://openairdocs.org/ntsb-events/094/sequence.md?model=2072418), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md) ## Analysis The pilot reported that on landing he touched down on the main landing gear but with the nose low. The airplane ballooned slightly, and the pilot applied power to ease the descent. The main landing gear touched down a second time and the pilot held "as much back pressure" as he could on the yoke. When the nose gear touched the ground the pilot heard a "grinding" noise and the airplane "began to buck," then veered to the left but stayed on the runway. The propeller then struck the runway, resulting in substantial damage to the firewall. When the pilot climbed out of the airplane, he observed that the nose gear tire was flat and the oleo strut was empty of fluid. The pilot reported that there was no mechanical malfunction or failure with the airplane before the accident. ## Factual narrative The pilot reported that on landing he touched down on the main landing gear but with the nose low. The airplane ballooned slightly, and the pilot applied power to ease the descent. The main landing gear touched down a second time and the pilot held "as much back pressure" as he could on the yoke. When the nose gear touched the ground the pilot heard a "grinding" noise and the airplane "began to buck," then veered to the left but stayed on the runway. The propeller then struck the runway, resulting in substantial damage to the firewall. When the pilot climbed out of the airplane, he observed that the nose gear tire was flat and the oleo strut was empty of fluid. The pilot reported that there was no mechanical malfunction or failure with the airplane before the accident. ## Aircraft - Registration: [N64427](https://openairdocs.org/aircraft/N64427), registered now, S/N 17265219, built 1975 (OpenAirDocs) - Reported make and model: CESSNA 172M - Registry model: [Cessna 172M](https://openairdocs.org/model/cessna-172m) (registry code 2072418) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17265219 - Airframe hours: 9823 - Engines: LYCOMING O-320 SERIES 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: AvCenter Inc. - Registered owner: Teton Leasing LLC - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, June 21, 2010 - Departed: KBOI, Boise, ID - Destination: KTWF, Twin Falls, ID - Flight plan: VFR - Airport: KTWF, Magic Valley, runway 25, 8,703 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 24; injuries: none; student; medical: class 3, without waivers/limitations; seat: left; flight hours: 33 total, 33 in this make and model, 4 as pilot in command, 9 in the last 90 days, 5 in the last 30 days, 4 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 290° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 82 °F, dew point 39 °F - Altimeter: 29.86 inHg - Observed at: TWF ## 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 20100630036539A](https://openairdocs.org/incident/20100630036539A), Jun 30, 2010: Cessna 172M, Twin Falls, ID, Substantial damage. The student pilot landed on runway 25 with a slight right crosswind. He flared and touched down mains first but slightly nose low. When the nose touched the… ## Other investigations on N64427 (1) 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. - [NTSB SEA03LA047](https://openairdocs.org/ntsb/SEA03LA047), Mar 17, 2003: Cessna 172M (N64427), Idaho Falls, ID, substantial damage. Probable cause: The student pilot's failure to maintain proper runway alignment (centerline tracking) during a go around maneuver resulting in the aircraft impacting a runway light. Contributing factors were the… ## Docket (1 files) The files NTSB released with the investigation on August 3, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=76508. 601 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 601 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40333559&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.