Fatal NTSB investigations: Grumman G-164
10 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
| 1968 | 2 |
|---|---|
| 1970 | 2 |
| 1971 | 2 |
| 1973 | 1 |
| 1983 | 1 |
| 1990 | 1 |
| 1997 | 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 ('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."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 ('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 FTW97FA304Accident · 1 fatalField investigationFinal reportGrumman G-164 · Wilmot, ARThe loss of engine power due to a fractured throttle cable because the cable housing prevents an inspection of the cable by maintenance personnel. Factors were the pilot's impairment due to a heart attack, the lack of suitable terrain for the forced landing,…NTSB LAX90DUG05Accident · 1 fatalFinal reportGrumman G-164B · Blythe, CAFailure of the pilots of N6708K and N10222 to maintain adequate visual lookout and failure of the pilot of N6708K to follow a prearanged procedure for reversing the direction of flight.NTSB MIA84FA051Accident · 1 fatalField investigationFinal reportGrumman C-164 · South Bay, FLAs the acft initiated a turn to start dusting, it was observed to lose altitude rapidly & collide with the ground. The acft was 470 lbs over max gross takeoff weight. The area was affected by gusty winds from the south, & the plt's initial turn to the field…NTSB LAX73FVA40Accident · 1 fatalClosedGrumman G-164 · Edison, CANTSB MIA71FKA12Accident · 1 fatalClosedGrumman G-164 · Ponce, PRNTSB OAK71FVA77Accident · 1 fatalClosedGrumman G-164 · Madera, CANTSB LAX71FUJ16Accident · 1 fatalClosedGrumman G-164 · Yuma, AZNTSB SEA70FWG14Accident · 1 fatalClosedGrumman G-164 · Touchet, WANTSB SEA69F0086Accident · 1 fatalClosedGrumman G-164 · Walla Walla, WANTSB LAX69D0132Accident · 1 fatalClosedGrumman G-164 · Lancaster, CA