NTSB investigations: Grumman Acft ENG Cor-Schweizer G-164B, 2005
6 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\") = 2005
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") = 2005
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 DFW05CA236Accident · Serious injuriesData collectionFinal reportGrumman G-164B · Epps, LAThe pilot's failure to maintain clearance with the power lines.NTSB DFW05CA212Accident · No injuriesData collectionFinal reportGrumman G164B · Alexandria, LAThe pilot's failure to maintain adequate airspeed which resulted in a stall. A contributing factor was the high density altitude.NTSB SEA05CA157Accident · No injuriesData collectionFinal reportGrumman G-164B · Paul, IDThe failure of the pilot to maintain direction control during the landing roll, which resulted in a nose over. Contributing factors included the weeds and the wet, soft terrain..NTSB CHI05LA176Accident · No injuriesLimited investigationFinal reportSchweizer G-164B · Buxton, NDA loss of engine power on takeoff due to undetermined reasons. A factor was the ditch that the airplane contacted during the forced landing.NTSB DFW05LA147Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Lake Charles, LAThe failure of the propeller governor which resulted in a forced landing. A contributing factor was the transmission wire.NTSB DFW05LA116Accident · No injuriesLimited investigationFinal reportGrumman-Schweizer G-164B · Fenton, LAThe loss of engine power due to fuel starvation as a result of blockage of the firewall fuel filter with an unknown contaminant. A contributing factor was the lack of suitable terrain for the forced landing.