Fatal NTSB investigations: Grumman Acft ENG Cor-Schweizer G-164A
28 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
| 1972 | 1 |
|---|---|
| 1974 | 1 |
| 1975 | 2 |
| 1976 | 1 |
| 1977 | 1 |
| 1981 | 1 |
| 1982 | 2 |
| 1984 | 1 |
| 1986 | 2 |
| 1987 | 3 |
| 1989 | 1 |
| 1990 | 1 |
| 1992 | 1 |
| 1993 | 3 |
| 1995 | 1 |
| 1996 | 1 |
| 1997 | 1 |
| 1998 | 1 |
| 2012 | 1 |
| 2023 | 1 |
| 2024 | 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 c.\"highestInjuryLevel\" = 'Fatal'
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 c."highestInjuryLevel" = 'Fatal'
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 WPR24FA213Accident · 1 fatalClass 3 · FieldFinal reportGrumman Acft ENG Cor-Schweizer G-164A · Chamberino, NMAn aerodynamic stall and loss of control for reasons that could not be determined based on the available information.NTSB WPR23LA305Accident · 1 fatalClass 3 · LimitedFinal reportGrumman Acft ENG Cor-Schweizer G-164A · Davis, CAAn inflight loss of control during a low altitude operation for undetermined reasons.NTSB CEN12LA440Accident · 1 fatalLimited investigationFinal reportGrumman Acft ENG Cor-Schweizer G-164A · Darksville, MOThe pilot did not maintain clearance from a tree line at the completion of an agricultural spray run.NTSB LAX98LA240Accident · 1 fatalLimited investigationFinal reportGrumman G-164A · Tracy, CAThe failure of the pilot to maintain an adequate clearance with the telephone wires.NTSB FTW97LA136Accident · 1 fatalLimited investigationFinal reportGrumman G-164A · Swifton, ARthe pilot's improper in-flight planning/decision and failure to maintain positive control of the airplane, while performing an aerobatic maneuver.NTSB LAX96LA204Accident · 1 fatalLimited investigationFinal reportGrumman G-164 · Colusa, CAfailure of the pilot to remain clear of the power lines. Factors relating to the accident were: Lack of visual cues at dawn, and the power lines.NTSB SEA95LA165Accident · 1 fatalLimited investigationFinal reportGrumman G-164A · Buhl, IDThe loss of power due to the failure of an engine cylinder. The chemical load was not dumped for undetermined reasons and contributed to the severity of injuries.NTSB FTW93LA173Accident · 1 fatalLimited investigationFinal reportGrumman G-164A · Ganado, TXThe pilot's failure to maintain clearance with the power linesNTSB CHI93DCQ01Accident · 1 fatalFinal reportGrumman G-164A · Liberal, KSthe pilot's failure to maintain clearance with the powerlines. A factor related to the accident were the powerlines which were contacted during the aerial application operation.NTSB LAX93LA200Accident · 1 fatalLimited investigationFinal reportGrumman 164A · Biggs, CAFailure of the number 2 engine cylinder. A factor related to the accident was the lack of altitude for the pilot to make a successfull forced landing.NTSB LAX92LA274Accident · 1 fatalLimited investigationFinal reportGrumman G-164A · Tulare, CAAn inflight hopper compartment fire due to the incompatibility of the chemical loads, and, the failure of the operator follow the cautionary directives of the chemical manufacturer.NTSB FTW90DPG09Accident · 1 fatalFinal reportGrumman G164A · Osceola, ARThe pilot's failure to maintain proper clearance from the power lines.NTSB FTW89DRD03Accident · 1 fatalFinal reportSchweizer G-164A · Maxie, LAFailure of the pilot to maintain clearance from the trees. A factor related to the accident was: the presence of trees near the field where fertilizer was to be dispensed.NTSB FTW87DRD11Accident · 1 fatalFinal reportGrumman G-164A · Bastrop, LAThree flagmen were working with one spray plane and three fields. On this pass, two of the flagmen moved to the proper positions but the other one had moved too FAR laterally. The pilot stated to the sheriff that he had observed the flagman stepping off the…NTSB MIA87FA160Accident · 1 fatalField investigationFinal reportSchweizer G-164A · Dundee, MSWhile spraying a rice field, the acft was flying across svrl small dirt banks that had been furrowed for water ctl. Drg a swath run, it struck 3 furrowed banks that were close together, flipped over as it crashed, then burned. Witnessesrprtd the eng was…NTSB DEN87FA091Accident · 1 fatalField investigationFinal reportGrumman G-164A · Lamar, COThe aircraft had completed a formation aerial application operation and were in the process of single airplane spraying around the perimeters of a field. They collided at 10 feet above the ground on perpendicular flight paths, descended out of control and…NTSB MIA87FA022Accident · 1 fatalField investigationFinal reportGrumman G-164A · Orlando, FLWhile the plt was making a banner pick-up, witnesses saw the acft engage the banner & enter a climb. The plt released the banner, then the acft mushed into a partially built hangar, crashed & burned. The plt, who was on fire, exited the rgt canopy hatch.…NTSB FTW86FA066Accident · 2 fatalField investigationFinal reportGrumman G164A · Hankamer, TXTwo Grumman ag cats operated by the same air service collided in mid air. The accident occurred as one was departing and the other was returning to a temporary air strip adjacent to the fields they were fertilizing. Witnesses indicated that both pilot…NTSB FTW84LA145Accident · 1 fatalLimited investigationFinal reportGrumman G-164A · Abbeville, LAThe plt was employed as a professional corporate & charter plt; however, he had not flown agricultural acft in several years. He had receently purchased half interest in the air sevice & was on his 1st refresher flt since then. While the plt was practicing a…NTSB ATL82FIG07Accident · 1 fatalFinal reportGrumman G-164A · Frederick, MDThe pilot reported that 1 to 2 ounces of water was drained from the low point fuel sump, but no water was detected from the other sumps. He stated that he drained the sump until no water was detected. During the flight, the engine surged twice, then lost…NTSB FTW82FPG12Accident · 1 fatalFinal reportGrumman G-164 · Ethel, ARThe acft collided with power lines during the start of a swath run.NTSB FTW81FPG45Accident · 1 fatalClosedGrumman G-164A · Lonoke, ARNTSB FTW77FPG42Accident · 1 fatalClosedGrumman G-164A · Dumas, ARNTSB MIA77FKJ01Accident · 1 fatalClosedGrumman G-164 · Pansey, ALNTSB LAX75FVA73Accident · 1 fatalClosedGrumman G-164A · Taft, CANTSB FTW75FRA22Accident · 1 fatalClosedGrumman G-164A · El Campo, TXNTSB FTW74FRA31Accident · 1 fatalClosedGrumman G-164A · Buckeye, TXNTSB FTW72FPG84Accident · 2 fatalClosedGrumman G-164A · Crawfordsvlle, AR