NTSB investigations: Grumman Acft ENG Cor-Schweizer G-164A, 1991
17 cases on aircraft the registry lists as Grumman Acft ENG Cor-Schweizer 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
| 1971 | 1 |
|---|---|
| 1972 | 11 |
| 1973 | 15 |
| 1974 | 22 |
| 1975 | 31 |
| 1976 | 41 |
| 1977 | 38 |
| 1978 | 41 |
| 1979 | 35 |
| 1980 | 25 |
| 1981 | 25 |
| 1982 | 22 |
| 1983 | 19 |
| 1984 | 24 |
| 1985 | 14 |
| 1986 | 12 |
| 1987 | 18 |
| 1988 | 22 |
| 1989 | 23 |
| 1990 | 11 |
| 1991 | 17 |
| 1992 | 21 |
| 1993 | 17 |
| 1994 | 12 |
| 1995 | 19 |
| 1996 | 15 |
| 1997 | 8 |
| 1998 | 10 |
| 1999 | 7 |
| 2000 | 2 |
| 2001 | 6 |
| 2002 | 5 |
| 2003 | 1 |
| 2004 | 3 |
| 2005 | 10 |
| 2006 | 5 |
| 2007 | 3 |
| 2008 | 5 |
| 2009 | 4 |
| 2010 | 1 |
| 2011 | 6 |
| 2012 | 3 |
| 2013 | 1 |
| 2014 | 1 |
| 2015 | 5 |
| 2016 | 4 |
| 2017 | 3 |
| 2019 | 1 |
| 2020 | 2 |
| 2022 | 1 |
| 2023 | 1 |
| 2024 | 3 |
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\") = 1991
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3952801'))
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") = 1991
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3952801'))
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 FTW92LA020Accident · No injuriesLimited investigationFinal reportGrumman G-164A · Epps, LAThe loss of 1/2 of a propeller blade. Factors were powerplant vibration and resultant powerplant separation.NTSB LAX91LA413Accident · Minor injuriesLimited investigationFinal reportGrumman G164A-450 · Queen Creek, AZFailure of the engine cylinder, producing a loss of power. Contributing to the accident was the location of an irrigation ditch next to the landing area and a dark night light condition.NTSB CHI91DEP12Accident · No injuriesFinal reportSchweizer G-164-A · Elkhorn, WIThe pilot in command's failure to maintain adequate altitude.NTSB FTW91DPG19Accident · No injuriesFinal reportGrumman G-164A · Allport, ARA loss of power for undetermined reason. A factor was the terrain on which the pilot made the forced landing.NTSB FTW91DPG18Accident · No injuriesFinal reportGrumman G-164A · Dewitt, ARThe pilot's failure to maintain proper glidepath. A factor was the berm at the approach end of the runway.NTSB SEA91LA195Accident · No injuriesLimited investigationFinal reportGrumman G-164A · Genesee, IDThe pilot's failure to maintain alignment with the strip. Contributing to the accident was the glare of a bright horizon at dawn.NTSB SEA91LA191Accident · No injuriesLimited investigationFinal reportGrumman G-164A · Hamer, IDThe pilot's failure to maintain runway aligment. Factors include high vegetation, and an inadverent ground loop/swerve.NTSB MIA91LA183Accident · No injuriesLimited investigationFinal reportGrumman G-164A · Greenwood, FLThe inadequate preflight which resulted in debris in the cockpit which reduced the pilot's visual lookout. Unsuitable terrain encountered during the landing was a factor.NTSB MIA91LA170Accident · Minor injuriesLimited investigationFinal reportGrumman G-164A · Falcon, MSIn flight encounter with weather, high density altitude. Contributing to the accident was aircraft gross weight which was exceeded.NTSB CHI91DCJ03Accident · No injuriesFinal reportGrumman G-164-A · Edgar, NEThe pilot's inadequate aircraft preflight inspection.NTSB FTW91DRG03Accident · Serious injuriesFinal reportGrumman G-164A · Weslaco, TXFailure of the pilot to maintain clearance.NTSB DEN91LA077Accident · Serious injuriesLimited investigationFinal reportGrumman G-164A · Ville Platte, LAPremature pull up from an aerial application swath run resulting in a collision with an electrical transmission line.NTSB FTW91DPG11Accident · No injuriesFinal reportGrumman G-164A · Holly Grove, ARThe pilot's failure to maintain directional control. Factors were the wet runway and the ditch struck after control was lost.NTSB SEA91LA105Accident · Serious injuriesLimited investigationFinal reportGrumman G-164A · Lapwai, IDThe pilot's misjudgment of an aerial application swath run. Factors include a downdraft condition and soft terrain.NTSB FTW91DPG06Accident · No injuriesFinal reportGrumman G-164A · Gillett, ARThe windshiled becoming obscured by aerial application spray and the resultant limited vision from the cockpit.NTSB FTW91DRD03Accident · No injuriesFinal reportGrumman G-164A · Bonita, LAA power loss due to a cracked cylinder. A factor was the soft terrain in which the forced landing was performed.NTSB FTW91DPG02Accident · No injuriesFinal reportGrumman G-164A · Light, ARThe pilot's selection of the downwind runway for landing. A factor was the tailwind.