NTSB investigations: Grumman G-164, OK
9 cases on aircraft the registry lists as Grumman G-164. 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
| 1966 | 1 |
|---|---|
| 1970 | 1 |
| 1971 | 1 |
| 1974 | 1 |
| 1980 | 1 |
| 1986 | 1 |
| 1989 | 1 |
| 1997 | 1 |
| 2014 | 1 |
Where
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.\"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 ('3952702'))
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 ('3952702'))
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 CEN14LA319Accident · Minor injuriesLimited investigationFinal reportGrumman G 164 · Anadarko, OKThe total loss of engine power while climbing after takeoff for reasons that could not be determined based on the available information.NTSB FTW97LA117Accident · No injuriesLimited investigationFinal reportGrumman G-164 · Newkirk, OKThe partial loss of engine power due to failure of the blower (integral supercharger). A factor was the power line over which the pilot had to maneuver during the forced landing which resulted in insufficient airspeed to flare the airplane.NTSB FTW89DPJ08Accident · Serious injuriesFinal reportGrumman G-164 · Guymon, OKFailure of the upper right engine mount (firewall attach bolt) due to fatigue, and failure of the lower right mounting bolt for an unknown reason, which allowed overload failure of the two remaining mounting bolts and separation of the engine.NTSB FTW86LPJ10Accident · No injuriesFinal reportGrumman G-164 · Hooker, OKThe pilot stated that the aircraft flipped over when he landed in soft dirt on his recently extended private landing strip.NTSB FTW80DPJ22Accident · No injuriesClosedGrumman G-164 · Fairview, OKNTSB FTW74DPM28Accident · No injuriesClosedGrumman G-164 · Atoka, OKNTSB FTW71DPM32Accident · No injuriesClosedGrumman G-164 · Dustin, OKNTSB FTW71DPJ12Accident · No injuriesClosedGrumman G-164 · Boise City, OKNTSB FTW66F0692Accident · Serious injuriesClosedGrumman G-164 · Broken Arrow, OK