# NTSB WPR10LA194: Cessna 170B, N2629D, Columbia, CA, April 7, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: April 7, 2010, 15:30 local (22:30 UTC) - Place: Columbia, CA - Coordinates: 38.030277, -120.414443 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.0303&lon=-120.4144&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: 3 uninjured - Status: Completed, report August 12, 2010 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 75684 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10LA194 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/75684/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=75684 - Page: https://openairdocs.org/ntsb/WPR10LA194 ## Probable cause The pilot's failure to maintain directional control during landing roll. ## 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 170B, 74 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=2072306), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Cessna 170B, 84 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072306), [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 170B, 37 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072306), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Nose over/nose down](https://openairdocs.org/ntsb-events/096); cases with it: [Cessna 170B, 29 cases](https://openairdocs.org/ntsb-events/096/sequence.md?model=2072306), [All aircraft, 2,287 cases](https://openairdocs.org/ntsb-events/096/sequence.md) ## Analysis The pilot reported that after conducting a three-point landing on runway 17, the tailwheel-equipped airplane began to turn to the left. The pilot applied right rudder for correction and the airplane turned to the right. The pilot then immediately applied full power and left rudder with no result from either input. The aircraft continued to turn to the right and the left wingtip contacted the runway surface. The airplane exited the right side of the runway and nosed over, resulting in structural damage to the empennage and wings. The pilot reported that the wind at the time of the accident was from 160 degrees at 6 knots. Examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed no mechanical anomalies with the engine or airframe that would have precluded normal operation. ## Factual narrative On April 7, 2010, about 1530 Pacific daylight time, a Cessna 170B tailwheel equipped airplane, N2629D, was substantially damaged during landing roll at the Columbia Airport (O22), Columbia, California. The airplane was registered to Blue Oak LLC., of Wilmington, Delaware, and operated by the pilot. The commercial pilot and his two passengers were not injured. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight. The local flight originated from O22 about 20 minutes prior to the accident. The pilot reported that upon returning to O22 from the local practice area, he intended to conduct multiple full-stop landings. Prior to arriving at O22, the pilot obtained weather information from the local Automated Weather Observing System (AWOS) and noted the wind from 160 degrees at 6 knots. The pilot stated that he executed a three-point landing on runway 17 with no adverse results. The pilot taxied back to the departure end of runway 17 and proceeded to take off and remain within the airport traffic pattern. He configured the airplane for another full-stop landing by applying carburetor heat, selecting 20 degrees of flaps, and establishing an airspeed of 73 knots. Upon reaching the touchdown area, the pilot "transitioned the aircraft into a three-point landing configuration while maintaining runway heading." During the landing roll, the airplane began to turn to the left and the pilot applied "a bit of right rudder for correction." The pilot reported that the airplane "…continued to turn to the right. I then immediately applied full power and left rudder with no result from either input. The aircraft continued to turn to the right and the left wingtip contacted the runway surface." Subsequently, the airplane exited the right side of the runway and nosed over, which resulted in structural damage to the empennage and wings. Examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed that flight control continuity was established from the cockpit controls to all primary flight control surfaces and were free of binding. Continuity from the throttle, mixture, and carburetor heat controls to the engine was obtained. The engine was intact and exhibited no evidence of catastrophic failure. The bottom spark plugs were removed and exhibited normal operating signatures. The crankshaft was manually rotated by hand using the propeller, and thumb compression was obtained on all cylinders in firing order. Spark was produced on all ignition leads when the crankshaft was rotated. The carburetor remained attached to the engine and was intact. The mixture was placed in the full rich position, and when the throttle was advanced to the full open position, fuel was observed injecting into the carburetor throat. The carburetor fuel screen was free of debris. Residual fuel was drained from the carburetor float bowl and was free of debris. No anomalies were observed with the engine or airframe that wouldhave precluded normal operation. ## Aircraft - Registration: [N2629D](https://openairdocs.org/aircraft/N2629D), registered now, S/N 20781 (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: 20781 - Airframe hours: 7467 - Engines: CONT MOTOR O-360-AYM 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Christopher Miller - Registered owner: Blue Oak LLC - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 26, 2009, 27 hours before - Departed: O22, Columbia, CA - Destination: O22, Columbia, CA - Airport: O22, Columbia Airport, runway 17, 4,670 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 58; injuries: none; flight instructor, commercial; airplane ratings: single-engine sea, multi-engine sea, single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review April 21, 2008; seat: right; flight hours: 8,446 total, 92 in this make and model, 8,242 as pilot in command, 60 in the last 90 days, 33 in the last 30 days, 3 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 70 °F, dew point 39 °F - Altimeter: 30.12 inHg - Observed at: MOD, 35 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 20100407031439A](https://openairdocs.org/incident/20100407031439A), Apr 7, 2010: Cessna 170B, Columbia, CA, Substantial damage. Parapharsed pilot statementon April 7th, 2010 a Cessna 170 N-2629D departed Columbia, CA and flew the aircraft to a local practice area and demonstrated… ## Docket (2 files) The files NTSB released with the investigation on May 13, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=75684. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40329487&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Reports from Federal Agencies - FAA Inspector Statement (item 2, .PDF): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40329488&FileExtension=.PDF&FileName=Reports%20from%20Federal%20Agencies%20-%20FAA%20Inspector%20Statement-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.