# Accident 20100812042449A: Piper PA-28-161, Garberville, CA, August 12, 2010

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 12, 2010, 13:00 local time
- Place: Garberville, CA
- Airport: Garberville
- Damage: Substantial damage
- Phase of flight: Landing: Rollout
- Operating rules: General operating rules (Part 91)
- Location: 40.0847° N, 123.8086° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=40.0847&lon=-123.8086&mi=10
- Aircraft: N9353C, a cancelled registration (https://openairdocs.org/deregistered/N9353C-2013-08-21) (OpenAirDocs)
- Registry model: Piper PA-28-161 (registry code 7102803, https://openairdocs.org/model/piper-pa-28-161) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA-28-161
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 200 total, 180 in this make and model, 30 in the last 90 days
- NTSB investigation: [NTSB WPR10CA372](https://openairdocs.org/ntsb/WPR10CA372) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20100812042449A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

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 N9353C. WHILE ATTEMPTING TO LAND AT THE GARBERVILLE AIRPORT, THE AIRCRAFT RAN OFF THE RUNWAY END, VEERED DOWN AN ENBANKMENT, AND STRUCK A FENCE CAUSING SUBSTANTIAL DAMAGE TO THE AIRCRAFT. NO INJURIES TO PILOT OR THE PASSENGER.  DURING MR HONEYCUTT'S INTERVIEW, HE SAID THE FOLLOWING:-HIS PASSENGER ^PRIVACY DATA OMITTED^ WAS FROM THE GARBERVILLE AIRPORT-HE (HIMSELF) HAD NEVER BEEN TO THE GARBERVILLE AIRPORT-HE WAS DOWNWIND 36-HE SAW THE WIND SOCK FAVOR 36-HE WAS AT 8,000 FEET-HE STAY HIGH BECAUSE HE DIDN'T WANT TO GET TOO CLOSE TO THE TREES-WHILE LANDING HE NOTICED THAT HIS AIRSPEED WAS TOO HIGH-THE AIRCRAFT KEPT FLOATING-THE RUNWAY SLOPED AWAY-HE DID NOT FEEL COMFORTABLE GOING AROUND BECAUSE HE WASN'T FAMILIAR WITH THE AIRPORT-HE WAS ON THE BRAKES-HE STARTED APPLYING THE BRAKES LIGHTLY-THE AIRCRAFT GOT LOOSE SO HE LET OFF THE BRAKES ALITTLE-HE DUMPED THE FLAPS OUT-HE GOT BACK ON THE BRAKES, BUT THE AIRCRAFT KEPT GOING-HE WASN'T ABLE TO STOP THE AIRCRAFT AND IT ROLLED OVER THE HILL-WHEN HE EXITED THE AIRCRAFT AND WAS BACK UP ON THE RUNWAY, HE NOTICE THAT HE COULD FEEL THE WIND AT HIS BACK-THAT MEANT THEY HAD A TAILWIND AND HE DIDN'T KNOW IT-HE DIDN'T FILE A FLIGHT PLAN BUT HE USED FLIGHT-FOLLOWING -HE THOUGHT HE CHOSE THE BETTER OF TWO OPTIONS HE SAID HE HAD AT THE TIME BECAUSE HE DIDN'T HAVE ENOUGH RUNWAY LEFT AT THE TIME OF DECISION   1. TRY TO LAND AND STOP THE AIRCRAFT   2. GO AROUND AND TRY AGAIN-HE SAID HE LEARNED THREE THINGS   1. START LEARNING ABOUT THE AIRPORT YOU ARE FLYING INTO BEFORE YOUR FLIGHT   2. ALWAYS DO A GO-AROUND AT AN AIRPORT HE HAS NEVER BEEN TO   3. DON'T TRUST A PERSON TO GIVE YOU GUIDANCE ABOUT LANDING AT AN AIRPORT IF YOU HAVE NOT RESEARCH THE AIRPORT YOURSELF.

## The NTSB's investigation of this event (1)

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.

- [NTSB WPR10CA372](https://openairdocs.org/ntsb/WPR10CA372), Aug 12, 2010: Piper PA-28-161 (N9353C), Garberville, CA, substantial damage. 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.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.