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

9 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, 2000 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\") = 2000
    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 LAX00LA345Accident · No injuriesLimited investigationFinal reportGrumman-Schweizer G-164B · Tracy, CALoss of engine power due to failure and separation of the number one connecting rod.Sep 22, 2000 · N8981H · Substantial damageNTSB FTW00LA253Accident · No injuriesLimited investigationFinal reportGrumman-Schweizer G-164B · Erick, OKthe loss of engine power for undetermined reasons while maneuvering. A contributing factor was the lack of suitable terrain for the forced landing.Sep 7, 2000 · N8255K · Substantial damageNTSB FTW00LA239Accident · No injuriesLimited investigationFinal reportGrumman-Schweizer G-164B · Kaplan, LAthe failure of the supercharger during takeoff. A contributing factor was the lack of suitable terrain for the forced landing.Aug 21, 2000 · N6506K · Substantial damageNTSB LAX00LA285Accident · 1 fatalLimited investigationFinal reportGrumman G-164B · Tracy, CAThe pilot's failure to maintain adequate clearance from obstacles while maneuvering during an aerial application flight.Aug 1, 2000 · N6737K · DestroyedNTSB FTW00LA210Accident · 1 fatalLimited investigationFinal reportGrumman-Schweizer G-164B · Ville Platte, LAThe loss of control for an undetermined reason.Jul 15, 2000 · N428KG · DestroyedNTSB LAX00LA246Accident · No injuriesLimited investigationFinal reportGrumman G-164B · King City, CAThe loss of engine power for undetermined reasons.Jul 3, 2000 · N48456 · DestroyedNTSB SEA00LA099Accident · Serious injuriesLimited investigationFinal reportGrumman-Schweizer G-164B · Colfax, WAThe pilots failure to maintain clearance from power transmission lines.Jun 5, 2000 · N6549K · Substantial damageNTSB FTW00LA167Accident · No injuriesLimited investigationFinal reportGrumman-Schweizer G164B · Natchitoches, LAThe failure of the pilot to maintain directional control during the landing roll, which resulted in a ground loop. A factor was the crosswind.Jun 1, 2000 · N48723 · DestroyedNTSB MIA00LA168Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Monticello, MSThe failure of the pilot to maintain directional control during takeoff into crosswind conditions resulting in the collision with trees. A factor in the accident was the pilot's lack of familiarity with the aircraft.May 22, 2000 · N6744K · Substantial damage