# NTSB CEN10CA231: Beech 35, N8SM, Boulder, CO, April 28, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: April 28, 2010, 11:30 local (17:30 UTC) - Place: Boulder, CO - Coordinates: 40.036945, -105.221946 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=40.0369&lon=-105.2219&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report July 1, 2010 - Report: Approved by Office Director - NTSB office: Central Region - Parties: FAA/FSDO - NTSB case key (mKey): 75886 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN10CA231 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/75886/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=75886 - Page: https://openairdocs.org/ntsb/CEN10CA231 ## Probable cause The pilot's failure to maintain directional control while landing in a crosswind. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Wind: crosswind](https://openairdocs.org/ntsb-findings/03034040): Environmental issues › Conditions/weather/phenomena · Response/compensation (probable cause); cases with it: [Beech 35, 3 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md?model=1151502), [All aircraft, 1,008 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Beech 35, 6 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=1151502), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters](https://openairdocs.org/ntsb-findings/01062000): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Beech 35, 1 case](https://openairdocs.org/ntsb-findings/01062000/cases.md?model=1151502), [All aircraft, 1,269 cases](https://openairdocs.org/ntsb-findings/01062000/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: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Beech 35, 2 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=1151502), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) ## Analysis The private pilot was attempting to land his single-engine airplane in a crosswind when the airplane drifted to the right of the runway and touched down. The left wing lifted and the pilot reacted by adding power for a go-around, but he then determined that a go-around was not a suitable option and reduced engine power. The airplane veered toward a fence and a road, so the pilot again added power in an attempt to lift the airplane over them. Subsequently, the left wing hit a telephone pole and a car. The pilot reduced power and the airplane skidded to a stop and remained upright on the landing gear. The pilot reported no mechanical deficiencies with the airplane and stated that he failed to maintain control of the airplane after touchdown while attempting to land in a crosswind. ## Factual narrative The private pilot was attempting to land his single-engine airplane in a crosswind, when the airplane drifted to the right of the runway and touched down. The left wing lifted and the pilot reacted by adding power for a go-around, but realized that a go-around was not a suitable option and reduced engine power. The airplane veered toward a fence and a road, so the pilot again added power in an attempt to lift the airplane over them. Subsequently, the left wing hit a telephone pole and a car. The pilot reduced power and the airplane skidded to a stop and remained upright on the landing gear. The pilot reported no mechanical deficiencies with the airplane and stated the he failed to maintain control of the airplane after touchdown while attempting to land in a crosswind. ## Aircraft - Registration: [N8SM](https://openairdocs.org/deregistered/N8SM-2015-11-30), registration cancelled 2015-11-30, S/N D-332, built 1947 (OpenAirDocs) - Reported make and model: BEECH 35 - Registry model: [Beech 35](https://openairdocs.org/model/beech-35) (registry code 1151502) (OpenAirDocs) - Registry engine: [Continental E185 series](https://openairdocs.org/engine/continental-e185-series) (registry code 17014, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: D-332 - Engines: CONT MOTOR E185 SERIES 205 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Curtis Charles - Registered owner: Curtis Charles - Airworthiness certificate: Standard, Normal - Departed: BDU, Boulder, CO - Destination: BDU, Boulder, CO - Flight plan: Unknown - Airport: BDU, Boulder, runway 26 ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 62; private; airplane ratings: single-engine land; medical: class 3; flight hours: 270 total, 113 in this make and model ## Weather - Conditions: Visual (VMC), Day - Observed at: BDU ## 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 20100428034319A](https://openairdocs.org/incident/20100428034319A), Apr 28, 2010: Beech 35, Boulder, CO, Substantial damage. Loss of control on takeoff. ## Docket (1 files) The files NTSB released with the investigation on June 3, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=75886. 640 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 640 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40329609&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.