# NTSB WPR10CA372: Piper PA-28-161, N9353C, Garberville, CA, August 12, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: August 12, 2010, 14:10 local (21:10 UTC) - Place: Garberville, CA - Coordinates: 40.08472, -123.808609 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=40.0847&lon=-123.8086&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Landing area overshoot](https://openairdocs.org/ntsb-events/380) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report December 20, 2010 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 76791 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10CA372 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/76791/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=76791 - Page: https://openairdocs.org/ntsb/WPR10CA372 ## Probable cause The pilot’s improper airspeed, misjudged approach, and failure to attain the proper touchdown point. Contributing to the accident was the pilot’s lack of familiarity with the airport. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Info processing/decision: identification/recognition](https://openairdocs.org/ntsb-findings/02041510): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-28-161, 6 cases](https://openairdocs.org/ntsb-findings/02041510/cases.md?model=7102803), [All aircraft, 559 cases](https://openairdocs.org/ntsb-findings/02041510/cases.md) - [Planning/preparation](https://openairdocs.org/ntsb-findings/02061000): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-28-161, 2 cases](https://openairdocs.org/ntsb-findings/02061000/cases.md?model=7102803), [All aircraft, 113 cases](https://openairdocs.org/ntsb-findings/02061000/cases.md) - [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Piper PA-28-161, 5 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=7102803), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md) - [Knowledge: knowledge of geographic area](https://openairdocs.org/ntsb-findings/02032030): Personnel issues › Experience/knowledge · Pilot (probable cause); cases with it: [Piper PA-28-161, 1 case](https://openairdocs.org/ntsb-findings/02032030/cases.md?model=7102803), [All aircraft, 24 cases](https://openairdocs.org/ntsb-findings/02032030/cases.md) - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-28-161, 8 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=7102803), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Landing area overshoot](https://openairdocs.org/ntsb-events/380) (defining event); cases with it: [Piper PA-28-161, 9 cases](https://openairdocs.org/ntsb-events/380/sequence.md?model=7102803), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper PA-28-161, 30 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7102803), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-28-161, 58 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7102803), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot reported that while on the base leg of the traffic pattern his view of the unfamiliar airport, located in a mountain valley, was inhibited due to a hill. As the airport came into view the pilot realized he was too high and he initiated a descent with reduced power and full flaps. The airplane approached the runway with higher than normal airspeed and by the time the airplane touched down; there was not enough runway to stop. The airplane exited the end of the runway and proceeded into a ditch, substantially damaging the firewall. The pilot reported no mechanical failures or malfunctions with the airframe or engine prior to the accident. The pilot further stated the accident could have been prevented by familiarizing himself with the airport. ## Factual narrative The pilot reported that while on the base leg of the traffic pattern his view of the unfamiliar airport, located in a mountain valley, was inhibited due to a hill. As the airport came into view the pilot realized he was too high and he initiated a descent with reduced power and full flaps. The airplane approached the runway with higher than normal airspeed and by the time the airplane touched down; there was not enough runway to stop. The airplane exited the end of the runway and proceeded into a ditch, substantially damaging the firewall. The pilot reported no mechanical failures or malfunctions with the airframe or engine prior to the accident. The pilot further stated the accident could have been prevented by familiarizing himself with the airport. ## Aircraft - Registration: [N9353C](https://openairdocs.org/deregistered/N9353C-2013-08-21), registration cancelled 2013-08-21, S/N 28-7816464, built 1978 (OpenAirDocs) - Reported make and model: PIPER PA-28-161 - Registry model: [Piper PA-28-161](https://openairdocs.org/model/piper-pa-28-161) (registry code 7102803) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28-7816464 - Airframe hours: 1995 - Engines: LYCOMING O-320 SERIES 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Honeycutt Daniel DBA - Registered owner: Honeycutt Daniel DBA - Airworthiness certificate: Standard, Normal - Last inspection: Annual, November 3, 2009, 25 hours before - Departed: KMYV, Marysville, CA - Destination: O16, Garberville, CA - Airport: O16, Garberville Airport, runway 36, 3,050 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 38; injuries: none; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review April 8, 2010; seat: left; flight hours: 200 total, 170 in this make and model, 150 as pilot in command, 38 in the last 90 days, 15 in the last 30 days, 3 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: variable at 4 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 55 °F, dew point 52 °F - Altimeter: 29.93 inHg - Observed at: KACV, 63 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 20100812042449A](https://openairdocs.org/incident/20100812042449A), Aug 12, 2010: Piper PA-28-161, Garberville, CA, Substantial damage. On 08/12/2010, Mr. Daniel l. honeycutt departed the yuba city airport (O52) enroute to the Garberville Airport (O16). Mr. Honeycutt was the pilot of aircraft… ## Docket (1 files) The files NTSB released with the investigation on September 16, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=76791. 625 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 625 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40336168&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.