# NTSB WPR10CA007: Cessna 172N, N2219E, San Diego, CA, October 7, 2009 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: October 7, 2009, 14:52 local (21:52 UTC) - Place: San Diego, CA - Coordinates: 32.809444, -117.136947 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=32.8094&lon=-117.1369&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report March 3, 2010 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Adminstration - NTSB case key (mKey): 74870 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10CA007 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/74870/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=74870 - Page: https://openairdocs.org/ntsb/WPR10CA007 ## Probable cause The pilot’s improper flare and inadequate recovery from a bounced landing. ## 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 172N, 150 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072434), [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 172N, 38 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072434), [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: Hard landing](https://openairdocs.org/ntsb-events/092); cases with it: [Cessna 172N, 46 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072434), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) - [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Cessna 172N, 81 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072434), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 172N, 81 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072434), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis The student pilot stated that during landing on Runway 28R he lost control of the airplane after touchdown. The tower controller reported that, after touchdown, the airplane bounced a couple of times before the airplane exited the left side of the runway. During the excursion, the left main landing gear leg broke off and the left horizontal stabilizer sustained substantial damage. According to the airfield's automated weather report, winds at the time of the accident were estimated to be from 250 degrees at 10 knots. There was no report of a mechanical failure or malfunction with the airplane at the time of the accident. ## Factual narrative The student pilot stated that during landing on runway 28R, he lost control of the airplane after touchdown. The tower controller reported that after touchdown, the airplane bounced a couple of times before the airplane exited the left side of the runway. During the excursion, the left main landing gear leg broke off and the left horizontal stabilizer sustained substantial damage. According to the airfield's automated weather report, winds at the time of the accident were estimated to be from 250 degrees at 10 knots. There was no report of a mechanical failure or malfunction with the airplane at the time of the accident. ## Aircraft - Registration: [N2219E](https://openairdocs.org/aircraft/N2219E), registered now, S/N 17271189, built 1978 (OpenAirDocs) - Reported make and model: CESSNA 172N - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17271189 - Airframe hours: 6081 - Engines: LYCOMING O-320 SERIES 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Plus One Flyers, Inc - Registered owner: Icarus Aero Ventures Inc - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 15, 2009 - Departed: MYF, San Diego, CA - Destination: MYF, San Diego, CA - Airport: MYF, Montgomery Field Airport, runway 28R, 3,400 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 43; injuries: none; student; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review October 5, 2009; seat: left; flight hours: 69 total, 8 in this make and model, 7 as pilot in command, 25 in the last 90 days, 1 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 250° at 10 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 64 °F, dew point 52 °F - Altimeter: 29.94 inHg - Observed at: MYF ## Docket (1 files) The files NTSB released with the investigation on November 18, 2009, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=74870. 284 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 284 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40321002&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.