NTSB investigations: Grumman Acft ENG Cor-Schweizer G-164B, 1993
14 cases on aircraft the registry lists as Grumman Acft ENG Cor-Schweizer G-164B. 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
| 1976 | 4 |
|---|---|
| 1977 | 16 |
| 1978 | 24 |
| 1979 | 13 |
| 1980 | 23 |
| 1981 | 23 |
| 1982 | 14 |
| 1983 | 17 |
| 1984 | 16 |
| 1985 | 5 |
| 1986 | 8 |
| 1987 | 11 |
| 1988 | 11 |
| 1989 | 14 |
| 1990 | 14 |
| 1991 | 13 |
| 1992 | 10 |
| 1993 | 14 |
| 1994 | 18 |
| 1995 | 14 |
| 1996 | 7 |
| 1997 | 4 |
| 1998 | 11 |
| 1999 | 9 |
| 2000 | 9 |
| 2001 | 10 |
| 2002 | 7 |
| 2003 | 1 |
| 2004 | 6 |
| 2005 | 6 |
| 2006 | 7 |
| 2007 | 2 |
| 2008 | 6 |
| 2009 | 4 |
| 2010 | 13 |
| 2011 | 3 |
| 2012 | 2 |
| 2013 | 4 |
| 2014 | 4 |
| 2015 | 2 |
| 2016 | 4 |
| 2017 | 2 |
| 2018 | 4 |
| 2019 | 1 |
| 2020 | 2 |
| 2021 | 3 |
| 2023 | 6 |
| 2024 | 4 |
| 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\") = 1993
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3952802'))
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") = 1993
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3952802'))
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 MIA93LA178Accident · Minor injuriesLimited investigationFinal reportSchweizer G-164B · Benton, MSThe pilot-in-command's failure to maintain proper visual outlook.NTSB FTW93LA238Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Pioneer, LAThe failure by both pilots to maintain visual lookout. Factors were the inadequate radio communications by both pilots, and the departing pilot's failure to follow procedures and directives.NTSB SEA93LA168Accident · Serious injuriesLimited investigationFinal reportCessna A150L · Ephrata, WAInadequate visual lookout by both pilots, resulting in their failure to see-and-avoid each other's aircraft. A factor related to the accident was: failure of the Grumman 164B pilot to adequately monitor the UNICOM frequency.NTSB CHI93LA303Accident · No injuriesLimited investigationFinal reportSchweizer G167B · Borup, MNthe loss of engine power due to a cracked cylinder head.NTSB CHI93LA263Accident · No injuriesLimited investigationFinal reportGrumman G164B · Wyndmere, NDthe pilot's decision to land on unsuitable terrain. Factors in the accident are the wet and soft turf runway.NTSB CHI93LA254Accident · No injuriesLimited investigationFinal reportGrumman G164B · Eldred, MNthe pilot's failure to maintain directional control during the takeoff roll.NTSB FTW93LA179Accident · No injuriesLimited investigationFinal reportGrumman-Schweizer G-164B · Kaplan, LAThe pilot's failure to have the airplane properly attended during start when people were available. A factor was the inadequate tie down rope.NTSB FTW93LA175Accident · No injuriesLimited investigationFinal reportGrumman G-164B · St. Martinville, LAThe pilot's and tractor driver's inadequate visual lookoutNTSB FTW93LA174Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Stuttgart, ARThe pilot's selection of the downwind runway for landing. Factors were the wind conditions and the left brake malfunction for undetermined reasonsNTSB FTW93LA172Accident · Serious injuriesLimited investigationFinal reportGrumman G-164B · Walnut Ridge, ARThe pilot's failure to maintain adequate clearance.NTSB LAX93LA226Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Madera, CAThe pilot's failure to maintain directional control. A factor related to this accident was the left quartering tailwind.NTSB FTW93LA167Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Stuttgart, ARPilot's failure to maintain clearance from the electrical wires.NTSB FTW93LA153Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Arnaudville, LAThe loss of engine power for undetermined reasons. A factor was the unsuitable terrainNTSB FTW93LA089Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Indian Village, LALanding performed short of the runway threshold. Factor was wet grassy terrain