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

16 cases on aircraft the registry lists as Grumman Acft ENG Cor-Schweizer G-164B, where the first occurrence was “In flight collision with terrain/water”. 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

19822026
NTSB investigations: Grumman Acft ENG Cor-Schweizer G-164B per year, 1982–2026: 16 cases
19822
19831
19843
19881
19911
19921
19941
19952
19992
20011
20061

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 c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3952802')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 230))
  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 SEA06CA145Accident · Minor injuriesData collectionFinal reportGrumman-Schweizer G-164B · Lamont, WAThe pilot's failure to maintain terrain clearance while maneuvering.Jul 23, 2006 · N8376K · Substantial damageNTSB FTW01LA119Accident · No injuriesLimited investigationFinal reportGrumman-Schweizer G-164B · Rosharon, TXthe pilot's failure to maintain aircraft control while maneuvering. Factors were the weather conditions and the muddy terrain.May 15, 2001 · N6778K · Substantial damageNTSB FTW99LA182Accident · Minor injuriesLimited investigationFinal reportGrumman G-164B · Iowa, LAThe pilot's failure to maintain clearance with the crops being sprayed. A factor was the pilot's diverted attention.Jul 6, 1999 · N6703Q · Substantial damageNTSB CHI99LA215Accident · No injuriesLimited investigationFinal reportGrumman-Schweizer G-164B · Page, NDthe pilot's failure to compensate for the wind conditions. Factors were the sudden windshift and the crops.Jul 3, 1999 · N6633K · Substantial damageNTSB FTW96LA070Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Pawnee, OKThe pilot's failure to maintain adequate clearance from the terrain.Dec 13, 1995 · N6642K · Substantial damageNTSB LAX96LA012Accident · Minor injuriesLimited investigationFinal reportGrumman G-164B · Lost Hills, CAthe pilot misjudged the aircraft's altitude.Oct 16, 1995 · N8247K · DestroyedNTSB ATL94LA104Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Memphis, TNThe pilot's failure to maintain clearance from the earthen dike during the swath run.May 20, 1994 · N6816Q · Substantial damageNTSB FTW92LA143Accident · Minor injuriesLimited investigationFinal reportGrumman G-164B · Walnut Ridge, ARThe pilot's failure to maintain adequate terrain clearance. A factor was the loss of power as result of the uncoupling of the engine and the propeller.May 23, 1992 · N8380K · Substantial damageNTSB LAX91LA301Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Eloy, AZThe failure of the pilot to maintain the terrain clearance of the aircraft while maneuvering for a potential emergency landing on a moonless dark night.Jul 9, 1991 · N6633K · Substantial damageNTSB FTW88DRA14Accident · No injuriesFinal reportGrumman G-164B · College Port, TXAcft was substantially damaged when it executed an off-arpt landing following takeoff FR0M a wet sod strip on an ag flt. The plt stated that he was taking off to the north and that during the t/o roll the wind shifted to out of the south. He further stated…Jun 6, 1988 · N6615Q · Substantial damageNTSB MKC84LA255Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Marianna, ARThe landing gear contacted the bean crop which was being sprayed with sodium chlorate and the acft nosed over.Aug 16, 1984 · N6730K · Substantial damageNTSB MKC84LA214Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Brule, NEAccording to the pilot, during the swath run the left wing dropped and the acft flew into the corn field. Density altitude was aprx 5,200 ft.Jul 13, 1984 · N6825K · Substantial damageNTSB MKC84LA143Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Silver Creek, NEThe plt stated he was making an end pass while spraying a pasture & collided with a hilltop on the opposite side of a draw. This occurred while the sun was obstructing his vision.May 23, 1984 · N6677Q · Substantial damageNTSB FTW83LA262Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Kaplan, LAWhile departing from a private strip, the plt took off to the north in calm winds. When he returned to land, the wind had begun blowing from the southwest at 20 KTS; thus, he elected to land toward the south. A truck was parked at the apch end of the strip,…Jun 3, 1983 · N48503 · Substantial damageNTSB LAX83LA057Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Westley, CAThe acft collided with a dirt berm during a swath run tearing off both main landing gear. The acft continued to fly & an emergency landing was made at crow's landing nas. The plt attributed his inability to maintain sufficient ground clearance to the haze &…Dec 9, 1982 · N6713Q · Substantial damageNTSB FTW82DA172Accident · No injuriesFinal reportGrumman G164B · Marvell, ARDuring an aerial application process the pilot allowed the aircraft to collide with a rice levy. The aircraft was destroyed and there were no injuries to the pilot.May 11, 1982 · N6625K · Destroyed