WPR11LA260 · Grumman G-164A
Vince Dusters Grumman G-164A · Accident: runway excursion during landing
From Buttonwillow, CA (private airstrip) to Buttonwillow, CA (private airstrip)
Event
- NTSB case
- WPR11LA260
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Grumman G-164A
- Aircraft type
- Grumman G-164
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N5286
- Operator
- Vince Dusters
- Onboard fatalities
- Unknown
- Route
- From Buttonwillow, CA (private airstrip)To Buttonwillow, CA (private airstrip)
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 137: Agricultural
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · landing roll
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Runway excursion
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that on the day of the accident, he had conducted numerous landings on the accident airstrip and the brakes where "a little worn out," but had operated well enough to allow stopping on the runway. The pilot further stated that he was fatigued and dehydrated after flying for nearly 8 hours. On the accident landing, the pilot reported that he was slightly fast on the approach with a tailwind of approximately 5-10 knots. Upon touchdown he was unable to stop the airplane before the end of the runway and exited the right side. After the airplane exited the runway, its right wing struck a dumpster. The initial impact with the dumpster caused the airplane to spin into a second dumpster with which the airplane came to rest against.
Probable cause
The pilot's misjudgment of the landing approach and subsequent long landing and overrun of the runway resulting in a collision with ground obstacles. Contributing to the accident was the pilot's likely fatigue and dehydration.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR11LA260
- Event ID
- 20110613X23244
- Case number
- WPR11LA260
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2011-06-14.
- API snapshot SHA-256: 5d9253fac68331932a4107c222e6f8679e277ce136ae8edc7bf1f2bb89865199; retrieved 2026-09-15T16:16:43.426Z.