NTSB investigations: Grumman G-164, MO
8 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 |
| 1975 | 1 |
| 1979 | 1 |
| 1981 | 1 |
| 1983 | 1 |
| 1992 | 1 |
| 2008 | 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\" = 'MO' 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" = 'MO' 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 DFW08LA178Accident · No injuriesLimited investigationFinal reportGrumman G-164 · Stotesbury, MOFracture of the engine's number eight cylinder barrel resulting in a loss of engine power. Contributing to the accident was the lack of suitable terrain for a forced landing.NTSB CHI92DCA01Accident · No injuriesFinal reportGrumman G-164 · Malden, MOThe pilot could not maintain directional control after one of the main landing gear brakes jammed during a landing roll. The operator did not comply with an airworthiness directive issued to prevent a possible braking system malfunction.NTSB MKC83LA213Accident · No injuriesLimited investigationFinal reportGrumman G-164 · Odessa, MOThe acft was making an aerial application turn when according to the pilot the engine quit. The landing was made in a stubble terraced field which collapsed the left main landing gear. During the landing the acft struck the rising terrainof a terrace and…NTSB MKC81FCA10Accident · Serious injuriesClosedGrumman G-164 · Neelyville, MONTSB MKC79FCA23Accident · No injuriesClosedGrumman G-164 · Neelyville, MONTSB MKC76DCA04Accident · No injuriesClosedGrumman G-164 · Randlees, MONTSB MKC71DCA09Accident · No injuriesClosedGrumman G-164 · Williamsville, MONTSB MKC66F0592Accident · No injuriesClosedGrumman G-164 · Charleston, MO