NTSB investigations: Grumman G-164A, 1989
4 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\") = 1989
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") = 1989
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 FTW89DQG05Accident · No injuriesFinal reportSchweizer G-164A · Sunray, TXA total power loss for undetermined reasons. A factor was the rough uneven terrain in which the pilot had to make the forced landing.NTSB CHI89DEX06Accident · No injuriesFinal reportGrumman G-164A · Sullivan, INA failure of the supercharger oil seal which resulted in a partial loss of engine power during takeoff and the uncontrolled touchdown during the forced landing. Factors related to the accident were: partial failure of the supercharger and spark plub fowling.NTSB LAX89DUJ07Accident · No injuriesFinal reportGrumman G-164A · Eloy, AZInaequate preflight by the pilot, which resulted in fuel starvation during the climb after takeoff, due to very little fuel remaining in the tanks. The rough/uneven desert terrain was considered to be a contributing factor.NTSB FTW89DRD05Accident · Minor injuriesFinal reportGrumman G-164A · Gueydan, LAVisual lookout was not maintained by the pilot in command, which resulted in the collision with a power transmission line during a swath run.