# NTSB WPR13CA301: Cessna 170B, N2600D, Fallbrook, CA, June 30, 2013 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: June 30, 2013, 13:50 local (20:50 UTC) - Place: Fallbrook, CA - Coordinates: 33.354167, -117.250831 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=33.3542&lon=-117.2508&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining event: [Takeoff: Aerodynamic stall/spin](https://openairdocs.org/ntsb-events/241) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report September 5, 2013 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration FSDO - NTSB case key (mKey): 87330 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR13CA301 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/87330/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=87330 - Page: https://openairdocs.org/ntsb/WPR13CA301 ## Probable cause The pilot’s failure to maintain adequate airspeed during the takeoff, and his loss of aircraft control during the subsequent stall recovery. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 170B, 13 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=2072306), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/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 170B, 91 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072306), [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: Aerodynamic stall/spin](https://openairdocs.org/ntsb-events/241) (defining event); cases with it: [Cessna 170B, 9 cases](https://openairdocs.org/ntsb-events/241/sequence.md?model=2072306), [All aircraft, 1,529 cases](https://openairdocs.org/ntsb-events/241/sequence.md) - [Takeoff: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Cessna 170B, 13 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=2072306), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md) - [Takeoff: Loss of control in flight](https://openairdocs.org/ntsb-events/240); cases with it: [Cessna 170B, 19 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=2072306), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 170B, 52 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072306), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot intended to perform a short-field takeoff in the tailwheel equipped airplane for both practice, and as a demonstration to the passenger. His intention was to climbout at the airplane's best angle of climb airspeed (48 mph). He stated that the airspeed indicator was not accurate at low airspeeds, and that an indicated airspeed of 40 mph was actually 50 mph true. He selected 20 degrees of flaps, and observed the angle of wind vary during both the run-up, and while lining the airplane up on the runway. As he began the takeoff roll, the wind moved to a direct headwind, and he initiated rotation at an indicated airspeed of 40 mph. He maintained that airspeed, and once they reached an altitude of 150 feet agl, the airframe began to shudder. The airplane began to descend, and he applied forward elevator control in an effort to regain control. After doing so, the runway came into view, and concerned that they might collide with the ground, he released elevator pressure. The airplane subsequently settled just left of the runway and ground looped, coming to rest on its nose. The pilot stated that the accident could have been avoided if he increased the takeoff airspeed to counter for the wind conditions, and applied more down elevator pressure during the subsequent recovery. The airplane sustained substantial damage to both wings, and the pilot reported no preimpact mechanical malfunctions or failures with the airframe or engine that would have precluded normal operation. ## Factual narrative The pilot intended to perform a short-field takeoff in the tailwheel equipped airplane for both practice, and as a demonstration to the passenger. His intention was to climbout at the airplane's best angle of climb airspeed (48 mph). He stated that the airspeed indicator was not accurate at low airspeeds, and that an indicated airspeed of 40 mph was actually 50 mph true. He selected 20 degrees of flaps, and observed the angle of wind vary during both the run-up, and while lining the airplane up on the runway. As he began the takeoff roll, the wind moved to a direct headwind, and he initiated rotation at an indicated airspeed of 40 mph. He maintained that airspeed, and once they reached an altitude of 150 feet agl, the airframe began to shudder. The airplane began to descend, and he applied forward elevator control in an effort to regain control. After doing so, the runway came into view, and concerned that they might collide with the ground, he released elevator pressure. The airplane subsequently settled just left of the runway and ground looped, coming to rest on its nose. The pilot stated that the accident could have been avoided if he increased the takeoff airspeed to counter for the wind conditions, and applied more down elevator pressure during the subsequent recovery. The airplane sustained substantial damage to both wings, and the pilot reported no preimpact mechanical malfunctions or failures with the airframe or engine that would have precluded normal operation. ## Aircraft - Registration: [N2600D](https://openairdocs.org/aircraft/N2600D), registered now, S/N 20752, built 1952 (OpenAirDocs) - Reported make and model: CESSNA 170B - Registry model: [Cessna 170B](https://openairdocs.org/model/cessna-170b) (registry code 2072306) (OpenAirDocs) - Registry engine: [Continental C145 series](https://openairdocs.org/engine/continental-c145-series) (registry code 17012, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 20752 - Airframe hours: 3930 - Engines: CONT MOTOR C145 SERIES 145 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, September 15, 2012, 34 hours before - Departed: L18, Fallbrook, CA - Destination: AJO, Corona, CA - Airport: L18, Fallbrook, runway 18, 2,160 × 60 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 46; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review September 6, 2012; seat: left; flight hours: 216 total, 82 in this make and model, 176 as pilot in command, 11 in the last 90 days, 1 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 77 °F, dew point 63 °F - Altimeter: 29.79 inHg - Observed at: KNFG, 6 nm away ## 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 20130630012229A](https://openairdocs.org/incident/20130630012229A), Jun 30, 2013: Cessna 170B, Fallbrook, CA, Substantial damage. Pilot statement: on Sunday June 30, 2013, at approximately 1000 hours (PST), my friend, [privacy data omitted] and I departed corona airport (ajo) and flew to… ## Docket (2 files) The files NTSB released with the investigation on August 12, 2013, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=87330. 3.6 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 3.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40397434&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Photo 1 – Airplane Damage (item 2, .PDF, 355 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40397428&FileExtension=.PDF&FileName=Photo%201%20%E2%80%93%20Airplane%20Damage-Master.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.