NTSB investigations: Grumman G-164, 1986
5 cases on aircraft the registry lists as Grumman G-164. 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
| 1964 | 27 |
|---|---|
| 1965 | 24 |
| 1966 | 20 |
| 1967 | 28 |
| 1968 | 24 |
| 1969 | 27 |
| 1970 | 18 |
| 1971 | 22 |
| 1972 | 17 |
| 1973 | 28 |
| 1974 | 20 |
| 1975 | 16 |
| 1976 | 20 |
| 1977 | 17 |
| 1978 | 9 |
| 1979 | 11 |
| 1980 | 9 |
| 1981 | 11 |
| 1982 | 7 |
| 1983 | 6 |
| 1984 | 4 |
| 1985 | 4 |
| 1986 | 5 |
| 1987 | 6 |
| 1988 | 2 |
| 1989 | 3 |
| 1990 | 1 |
| 1991 | 4 |
| 1992 | 4 |
| 1993 | 1 |
| 1994 | 4 |
| 1995 | 4 |
| 1996 | 3 |
| 1997 | 6 |
| 1998 | 4 |
| 2000 | 1 |
| 2001 | 1 |
| 2002 | 1 |
| 2003 | 2 |
| 2004 | 2 |
| 2005 | 3 |
| 2006 | 1 |
| 2008 | 3 |
| 2010 | 2 |
| 2011 | 1 |
| 2014 | 1 |
| 2017 | 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 ('3952702'))
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 ('3952702'))
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 MKC86LA177Accident · No injuriesLimited investigationFinal reportGrumman G-164 · Goodwin, ARThe ag acft was being used to spray nudrin on soybeans when the engine lost power. The plt made a forced landing in a rice field and the acft flipped forward to the inverted position. Investigation revealed the two-piece cam reduction gear came apart. An AD…NTSB FTW86LPJ10Accident · No injuriesFinal reportGrumman G-164 · Hooker, OKThe pilot stated that the aircraft flipped over when he landed in soft dirt on his recently extended private landing strip.NTSB DEN86LA162Accident · No injuriesLimited investigationFinal reportGrumman G-164 · Wessington, SDAccording to the plt, during maneuvering on a swath run, the acft he was piloting encountered a downdraft, forcing the acft down until contact with the ground.NTSB FTW86FRG24Accident · No injuriesFinal reportGrumman G-164 · La Feria, TXAs the plt was making a swath run, he started to cross under power lines, but saw the profile view of a road marker. When he pulled up to avoid the road marker, the acft struck the wires, rolled to the left & collided with the ground.NTSB LAX86FVG04Accident · No injuriesFinal reportGrumman G-164 · Butte City, CAThe acft made a forced landing off arpt after a power loss during takeoff. The operator stated that water was found in the fuel system.