# NTSB WPR10CA098: Cessna 172R, N35414, Ramona, CA, January 6, 2010 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Data collection · Final report - Date: January 6, 2010, 15:25 local (23:25 UTC) - Place: Ramona, CA - Coordinates: 33.039165, -116.915 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=33.0392&lon=-116.9150&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining event: [Takeoff: Nose over/nose down](https://openairdocs.org/ntsb-events/096) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report March 23, 2010 - Report: Approved by Office Director - NTSB office: Western Pacific Region - NTSB case key (mKey): 75234 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10CA098 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/75234/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=75234 - Page: https://openairdocs.org/ntsb/WPR10CA098 ## Probable cause The pilot's failure to maintain directional control during a touch-and-go landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172R, 37 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=2072401), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/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 172R, 75 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072401), [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. - [Takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Cessna 172R, 40 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072401), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Takeoff: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 172R, 39 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072401), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Takeoff: Nose over/nose down](https://openairdocs.org/ntsb-events/096) (defining event); cases with it: [Cessna 172R, 9 cases](https://openairdocs.org/ntsb-events/096/sequence.md?model=2072401), [All aircraft, 2,287 cases](https://openairdocs.org/ntsb-events/096/sequence.md) ## Analysis The student pilot reported that he was on his second solo flight and planned to do a touch-and-go landing. He reported that after a normal landing he immediately set the flaps to zero degrees and applied full power. After adding power, the airplane veered left. The pilot reduced power and steered the airplane back to the right. The pilot added power a second time and the airplane veered left, exited the hard surface runway, then encountered rough terrain and nosed over. The airplane sustained substantial damage to the tail and both wings. The pilot reported no preaccident mechanical failures or malfunctions with the airplane ## Factual narrative The student pilot reported that he was on his second solo flight and planned to do a touch-and-go landing. He reported that after a normal landing he immediately set the flaps to zero degrees and applied full power. After adding power, the airplane veered left. The pilot reduced power and steered the airplane back to the right. The pilot added power a second time and the airplane veered left, exited the hard surface runway, encountered rough terrain and nosed over. The airplane sustained substantial damage to the tail and both wings. The pilot reported no pre-accident mechanical failures or malfunctions with the airplane. ## Aircraft - Registration: [N35414](https://openairdocs.org/deregistered/N35414-2012-05-21), registration cancelled 2012-05-21, S/N 17281073 (OpenAirDocs) - Reported make and model: CESSNA 172R - Registry model: [Cessna 172R](https://openairdocs.org/model/cessna-172r) (registry code 2072401) (OpenAirDocs) - Category: Airplane - Serial number: 17281073 - Airframe hours: 5450 - Engines: Lycoming IO-360 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Pinnacle Aviation Services Inc - Registered owner: Pinnacle Aviation Services Inc - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, December 31, 2009, 5 hours before - Departed: KCRQ, Carlsbad, CA - Destination: RNM, Ramona, CA - Airport: RNM, Ramona Airport, runway 27, 5,001 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 57; injuries: minor; student; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; seat: left; flight hours: 31 total, 31 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: 300° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: none ## 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 20100106026539A](https://openairdocs.org/incident/20100106026539A), Jan 6, 2010: Cessna 172R, Ramona, CA, Destroyed. I interviewed the student pilot rick dixon on 01-07-2010. Dixon was on a solo practice flight at Ramona Airport. The reported winds were light and variable.… ## Docket (1 files) The files NTSB released with the investigation on January 25, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=75234. 334 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 334 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40324386&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.