NTSB investigations: Grumman G-164A, OK
7 cases on aircraft the registry lists as Grumman 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
| 1969 | 1 |
|---|---|
| 1975 | 1 |
| 1982 | 1 |
| 1985 | 1 |
| 1986 | 1 |
| 2007 | 1 |
| 2015 | 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.\"eventStateOrRegion\" = 'OK' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3952704'))
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."eventStateOrRegion" = 'OK' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3952704'))
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 CEN15LA204Accident · Minor injuriesLimited investigationFinal reportGrumman G 164A · Maysville, OKThe loss of engine power for reasons that could not be determined because a postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation.NTSB DFW07CA129Accident · No injuriesData collectionFinal reportGrumman G-164A · Sayre, OKThe partial loss of engine power on takeoff-initial climb for an undetermined reason. A factor associated with the accident was the lack of suitable terrain for a forced landing.NTSB FTW86FPJ07Accident · No injuriesFinal reportSchweizer G-164A · Red Rock, OKThe acft nosed over during a forced lndg after a power loss. The plt was enroute to a spraying operation and attempted a landing in a pasture after the power loss. An on scene investigation revealed no discrepancies in the engine or fuel system. A successful…NTSB FTW85FPJ01Accident · Serious injuriesFinal reportGrumman AG CAT G-164 · Norman, OKThe acft collided with a high static wire on an electric transmission line before colliding out of control with the ground. The plt stated after the accident that he forgot about the static line and flew into it during a maneuver for aerial spraying.NTSB FTW82DA177Accident · No injuriesFinal reportGrumman G-164A · Elreno, OKDuring takeoff the pilot encountered standing water on the runway. The aircraft swerved left and nosed over.NTSB FTW75DPJ06Accident · Minor injuriesClosedGrumman G-164 · Pauls Valley, OKNTSB FTW70D0237Accident · Minor injuriesClosedGrumman 164 · Eva, OK