NTSB investigations: Grumman G-164A, 1986
9 cases on aircraft the registry lists as Grumman G-164A. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1966 | 2 |
|---|---|
| 1967 | 3 |
| 1968 | 4 |
| 1969 | 21 |
| 1970 | 12 |
| 1971 | 17 |
| 1972 | 21 |
| 1973 | 25 |
| 1974 | 26 |
| 1975 | 34 |
| 1976 | 30 |
| 1977 | 23 |
| 1978 | 20 |
| 1979 | 21 |
| 1980 | 8 |
| 1981 | 10 |
| 1982 | 9 |
| 1983 | 9 |
| 1984 | 13 |
| 1985 | 6 |
| 1986 | 9 |
| 1987 | 7 |
| 1988 | 7 |
| 1989 | 4 |
| 1990 | 13 |
| 1991 | 7 |
| 1992 | 4 |
| 1993 | 4 |
| 1994 | 4 |
| 1995 | 2 |
| 1996 | 4 |
| 1997 | 4 |
| 1998 | 2 |
| 1999 | 2 |
| 2000 | 5 |
| 2001 | 2 |
| 2002 | 3 |
| 2003 | 1 |
| 2004 | 3 |
| 2005 | 3 |
| 2006 | 3 |
| 2007 | 2 |
| 2008 | 4 |
| 2009 | 1 |
| 2011 | 3 |
| 2012 | 3 |
| 2013 | 2 |
| 2014 | 1 |
| 2015 | 3 |
| 2018 | 2 |
| 2023 | 1 |
| 2024 | 3 |
| 2025 | 1 |
Where
Open the mapLatest cases
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
WHERE year(c.\"eventDate\") = 1986
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3952704'))
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE year(c."eventDate") = 1986
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3952704'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB LAX87DVA02Accident · No injuriesFinal reportSchweizer G-164A · Fresno, CAThe airplane collided with telephone lines while conducting an aerial application operation. The pilot reported that he was familiar with the area. He surveyed the field, in flight, before he commenced the spraying activities. The pilot did not report, nor…NTSB DEN86LA220Accident · No injuriesLimited investigationFinal reportGrumman G-164A · Center, COThe plt reported that he was landing on a 50 ft wide dirt strip and allowed the acft to drift to the left during the landing roll. The left wing collided with wheat growing along the left side of the strip and the acft swerved further to the left. During the…NTSB FTW86LRD22Accident · No injuriesFinal reportGrumman G-164A · Franklin, LADuring aerial application, the pilot was maneuvering for alignment with a field, when the aircraft struck the ground. Nopreimpact mechanical malfunction or failure was evident.NTSB MIA86LA198Accident · Minor injuriesLimited investigationFinal reportGrumman G-164A · Okolona, MSWhile in cruise flt at 100 feet en route to the spraying area the engine 'spit' twice and quit completely. During a forced landing in a field the aircraft encountered mud and nosed over coming to rest inverted. The engine had 100 hours before it was to be…NTSB FTW86LRD12Accident · No injuriesFinal reportGrumman G-164A · Branch, LAShortly after takeoff, a partial power loss occurred & the plt made a forced landing in a soft plowed field, where the acft nosed over onto its back. The plt rprtd the loss of power was due to failure of the eng blower.NTSB MKC86LA108Accident · No injuriesLimited investigationFinal reportGrumman G-164A · Tekamah, NEThe pilot stated that as he was finishing his run spraying pine trees and was pulling up when the engine lost power. The right wings struck trees and the aircraft nosed over during the forced landing.NTSB SEA86LA109Accident · No injuriesLimited investigationFinal reportGrumman G164-A · Echo, ORA loss of power occurred shortly after takeoff on a downwind departure. A forced landing was accomplished onto a wheat field downhill. The aircraft nosed over during the landing roll. Post accident inspection of the aircraft disclosed fuel contamination.NTSB FTW86FPJ07Accident · No injuriesFinal reportSchweizer G-164A · Red Rock, OKThe acft nosed over during a forced lndg after a power loss. The plt was enroute to a spraying operation and attempted a landing in a pasture after the power loss. An on scene investigation revealed no discrepancies in the engine or fuel system. A successful…NTSB LAX86FVA03Accident · Minor injuriesFinal reportSchweizer G164A · Wasco, CAThe acft went off the left side of rwy during a downwind landing. The ag plts made a practice of landing downwind to speed up turn-around time. They relied on their brakes to maintain control. The acc acfts brake pads were worn and the rt brake was fluid…