# NTSB WPR11LA260: Grumman G-164A, N5286, Buttonwillow, CA, June 14, 2011 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: June 13, 2011, 18:25 local (Jun 14, 2011, 01:25 UTC) - Place: Buttonwillow, CA - Coordinates: 35.427776, -119.486663 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=35.4278&lon=-119.4867&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report September 19, 2011 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 80752 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR11LA260 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/80752/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=80752 - Page: https://openairdocs.org/ntsb/WPR11LA260 ## 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. ## 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: [Grumman G-164A, 3 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=3952704), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Alertness/Fatigue: fatigue due to work schedule](https://openairdocs.org/ntsb-findings/02013520): Personnel issues › Physical · Pilot (probable cause); cases with it: [Grumman G-164A, 1 case](https://openairdocs.org/ntsb-findings/02013520/cases.md?model=3952704), [All aircraft, 25 cases](https://openairdocs.org/ntsb-findings/02013520/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Grumman G-164A, 2 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=3952704), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/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: [Grumman G-164A, 1 case](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=3952704), [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 roll: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Grumman G-164A, 2 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=3952704), [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: [Grumman G-164A, 9 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=3952704), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis 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. ## Factual narrative On June 13, 2011, about 1825 pacific daylight time, a Grumman G-164A, N5286 sustained substantial damage when it departed the runway and collided with two dumpsters at a private airstrip in Buttonwillow, California. The airplane was registered to Slikker Flying Service, Inc., and operated by Vince Dusters under the provisions of 14 Code of Federal Regulations Part 137 as an aerial application flight. Visual meteorological conditions prevailed and no flight plan was filed. The commercial pilot was not injured. The flight originated from a private field in Buttonwillow, California at 1000. The airplane maintenance records indicated that the airplane's last annual inspection was performed on December 1, 2010 and the log books were annotated that the airplane was airworthy. The airplane was not flown after the annual inspection until a day before the accident when the company owner test flew the airplane and reported that the airplane was airworthy and the brakes were operating normally. 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 the airplane's 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. Immediately after the accident the owner/operator checked the brakes and found them to be operating normally. Three days after the accident, an inspector from the Federal Aviation Administration (FAA) noted that the right brake would not hold pressure and was leaking brake fluid from the right master cylinder. The left brake would hold pressure after about 8 pumps, but was leaking brake fluid from the b-nut at the hard line to the flex line at the caliper. The continuity of the brake system was not checked at that time. ## Aircraft - Registration: [N5286](https://openairdocs.org/aircraft/N5286), registered now, S/N 562, built 1968 (OpenAirDocs) - Reported make and model: GRUMMAN G-164A - Registry model: [Grumman G-164A](https://openairdocs.org/model/grumman-g-164a) (registry code 3952704) (OpenAirDocs) - Registry engine: [Pratt & Whitney R-985 series](https://openairdocs.org/engine/pratt-whitney-r-985-series) (registry code 52008, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 562 - Airframe hours: 13921 - Engines: P&W R 1340 AN-1 600 horsepower reciprocating - Damage: Substantial damage - Flight: Aerial application, Part 137 - Operator: Vince Dusters, Inc. - Registered owner: Slikker Flying Service, Inc. - Airworthiness certificate: Special, Restricted (Special) - Last inspection: Annual, December 1, 2010, 6 hours before - Departed: PVT, Buttonwillow, CA - Destination: PVT, Buttonwillow, CA - Flight plan: Unknown - Airport: PVT, Vince Dusters Private Strip, runway 16, 2,640 × 20 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 53; injuries: none; commercial; airplane ratings: single-engine land; medical: class 2; last flight review February 25, 2011; seat: single; flight hours: 2,400 total, 310 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: 284° at 10 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 90 °F, dew point 52 °F - Altimeter: 29.97 inHg - Observed at: KBFL, 20 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 20110613010709A](https://openairdocs.org/incident/20110613010709A), Jun 13, 2011: Grumman G-164A, Buttonwillow, CA, Substantial damage. The pilot stated that he landed the aircraft slightly long. He stated that he could not stop the aircraft due to left brake fade, causing the aircraft to turn… ## Other investigations on N5286 (2) 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 SEA75DYG47](https://openairdocs.org/ntsb/SEA75DYG47), Jun 29, 1975: Grumman G-164A (N5286), Deary, ID, substantial damage - [NTSB SEA72DYA34](https://openairdocs.org/ntsb/SEA72DYA34), May 13, 1972: Grumman G-164A (N5286), Ontario, OR, minor damage ## Docket (10 files) The files NTSB released with the investigation on July 1, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=80752. 3.2 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 595 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350338&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Record of Conversation - Owner/Operator (item 2, .PDF, 49 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350265&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Owner%2FOperator-Master.PDF - Record of Conversation - Pilot (item 3, .PDF, 49 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350275&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Pilot-Master.PDF - Owner/Operator Statement (item 4, .PDF, 31 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350270&FileExtension=.PDF&FileName=Owner%2FOperator%20Statement-Redacted.PDF - FAA Inspector Statement (item 5, .PDF, 38 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350280&FileExtension=.PDF&FileName=FAA%20Inspector%20Statement-Master.PDF - Work Orders (item 6, .PDF, 74 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350271&FileExtension=.PDF&FileName=Work%20Orders-Redacted.PDF - Maintenance Records (item 7, .PDF, 175 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350303&FileExtension=.PDF&FileName=Maintenance%20Records-Redacted.PDF - Photo 1 - Front View Airplane. FAA Photo. (item 8, .PDF, 694 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350282&FileExtension=.PDF&FileName=Photo%201%20-%20Front%20View%20Airplane.%20FAA%20Photo.-Master.PDF - Photo 2 - Right Wing. FAA Photo. (item 9, .PDF, 804 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350283&FileExtension=.PDF&FileName=Photo%202%20-%20Right%20Wing.%20FAA%20Photo.-Master.PDF - Photo 3 - Right Wing Underside. FAA Photo (item 10, .PDF, 679 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350284&FileExtension=.PDF&FileName=Photo%203%20-%20Right%20Wing%20Underside.%20%20FAA%20Photo-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.