NTSB investigations: Grumman G-164A
7 cases on aircraft the registry lists as Grumman G-164A, where NTSB found Not determined, general. 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
| 2008 | 3 |
|---|---|
| 2012 | 1 |
| 2015 | 1 |
| 2018 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3952704')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND starts_with(f.\"findingCode\", '05000000')))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3952704')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND starts_with(f."findingCode", '05000000')))
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 CEN24LA364Accident · No injuriesClass 4 · LimitedFinal reportGrumman G-164A · LaPlace, LATotal loss of engine power during the agricultural application flight for reasons that could not be determined.NTSB CEN18LA152Accident · No injuriesLimited investigationFinal reportGrumman G 164A · Garwood, TXA partial loss of engine power for reasons that could not be determined because postaccident examination of the engine did not reveal any anomalies that would have precluded normal operation.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 CEN12LA458Accident · No injuriesLimited investigationFinal reportGrumman G-164A · Egeland, NDThe partial loss of engine power for reasons that could not be determined during postaccident examinations.NTSB CHI08CA242Accident · No injuriesData collectionFinal reportSchweizer G-164A · Jefferson, IAThe loss of engine power for an undetermined reason and the unsuitable terrain encountered during the forced landing. The corn crop was a factor.NTSB DFW08CA192Accident · No injuriesData collectionFinal reportGrumman G-164A · Bovina, TXLoss of engine power for undetermined reasons.NTSB NYC08LA245Accident · 1 fatalLimited investigationFinal reportGrumman G-164A · Pelham, GAA partial loss of engine power for undetermined reasons which led to a forced landing in unsuitable terrain.