NTSB investigations: Grumman Acft ENG Cor-Schweizer G-164A, 2006
5 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
Latest 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\") = 2006
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") = 2006
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 CHI06CA235Accident · No injuriesData collectionFinal reportGrumman-Schweizer G-164A · Gering, NEThe pilot's failure to maintain clearance from the power lines during the aerial application flight. Factors were the low altitude and power lines.NTSB NYC06LA180Accident · Minor injuriesLimited investigationFinal reportGrumman G-164A · Vineland, NJA loss of engine power due to foreign object damage for undetermined reasons. Contributing to the accident was the furrowed field.NTSB CHI06CA195Accident · No injuriesData collectionFinal reportGrumman G-164A · Lakeview, MIA loss of engine power for undetermined reasons. A factor associated with the accident was the low altitude at which the airplane was being operated when the loss of engine power occurred.NTSB DEN06CA088Accident · Minor injuriesData collectionFinal reportGrumman-Schweizer G-164A · Cokeville, WYthe pilot's failure to maintain directional control resulting in a ground loop. Contributing factors included the high winds and crosswind.NTSB ANC06CA039Accident · No injuriesData collectionFinal reportGrumman-Schweizer G-164A · Dixon, CAThe pilot's failure to attain altitude/clearance during takeoff/initial climb, which resulted in an in-flight collision with terrain. Factors associated with the accident were the pilot's inadequate evaluation of the weather, and unfavorable winds.