NTSB investigations: Grumman Acft ENG Cor-Schweizer G-164B, 1996

7 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

19762026
NTSB investigations: Grumman Acft ENG Cor-Schweizer G-164B, 1996 per year, 1976–2026: 426 cases
19764
197716
197824
197913
198023
198123
198214
198317
198416
19855
19868
198711
198811
198914
199014
199113
199210
199314
199418
199514
19967
19974
199811
19999
20009
200110
20027
20031
20046
20056
20067
20072
20086
20094
201013
20113
20122
20134
20144
20152
20164
20172
20184
20191
20202
20213
20236
20244
20251

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\") = 1996
    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.

NTSB CHI96LA287Accident · No injuriesLimited investigationFinal reportGrumman-Schweizer G-164B · Wellfleet, NEfailure of the pilot to maintain aircraft control, while maneuvering at low latitude. The hilly (rolling) terrain and unfavorable wind were related factors.Aug 9, 1996 · N6966K · DestroyedNTSB FTW96LA232Accident · Minor injuriesLimited investigationFinal reportGrumman G-164B · Newport, ARfailure of the pilot to maintain clearance from the power line.May 31, 1996 · N6678Q · Substantial damageNTSB FTW96LA231Accident · No injuriesLimited investigationFinal reportGrumman-Schweizer G-164B · Bunkie, LAThe pilot's failure to maintain control of the airplane.May 31, 1996 · N188TB · Substantial damageNTSB SEA96LA103Accident · No injuriesLimited investigationFinal reportSchweizer G164B · Moscow, IDinflight loss of an unsecured access plug from the engine crankcase, which resulted in a loss of engine oil and a forced landing. Factors relating to the accident were: hilly terrain, and foreign material (engine oil) on the windscreen which limited forward…May 29, 1996 · N48559 · Substantial damageNTSB CHI96LA186Accident · No injuriesLimited investigationFinal reportGrumman-Schweizer G-164B · Crookston, MNcatastrophic engine failure.May 25, 1996 · N48518 · Substantial damageNTSB FTW96LA205Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Iowa, LAthe pilot's selection of an unsuitable area for takeoff. The high vegetation (tall grass) was a related factor.May 10, 1996 · N6832K · Substantial damageNTSB LAX96LA124Accident · No injuriesLimited investigationFinal reportSchweizer G-164B · Tracy, CAoverheating and failure of the engine's master rod and master rod bearing due to oil starvation. A factor relating to the accident was: the lack of suitable terrain for an emergency landing.Feb 21, 1996 · N6674Q · Substantial damage