NTSB investigations: Grumman G-164A, ID
9 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 |
| 1979 | 1 |
| 1985 | 2 |
| 1987 | 1 |
| 1992 | 1 |
| 1997 | 1 |
| 1998 | 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\" = 'ID' 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" = 'ID' 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 SEA98LA140Accident · No injuriesLimited investigationFinal reportGrumman-Schweizer G-164A · Caldwell, IDThe pilot-in-command's misjudgment of clearance with a power line, resulting in a collision with the line. Factors included a power line and dark night light conditions in the spray area.NTSB SEA97LA172Accident · 1 fatalLimited investigationFinal reportGrumman G-164A · Pingree, IDThe pilot-in-command's failure to maintain adequate clearance with the power lines. A contributing factor was the unmarked power lines.NTSB SEA92LA174Accident · No injuriesLimited investigationFinal reportGrumman G-164A · Paul, IDThe pilot's selection of unsuitable terrain. The soft terrain was a factor.NTSB SEA87LA121Accident · No injuriesLimited investigationFinal reportGrumman G-164A · Viola, IDDuring an aerial applications maneuver a total loss of power occurred due to the internal failure of the supercharger impeller. During the forced landing the left main gear collapsed causing the aircraft to nose over inverted.NTSB SEA85LA187Accident · No injuriesLimited investigationFinal reportGrumman 164A · Shelley, IDThe safety broke in the carburetor and the seat backed out causing fuel starvation. The carburetor had been overhauled 350 hours prior to the accident.NTSB SEA85LA098Accident · No injuriesLimited investigationFinal reportGrumman G-164A · Kendrick, IDThe plt stated that he had completed a spray application & was making a normal landing when the left main gear failed. Subsequently, the acft veered off the left side of the rwy & nosed over. AD 76-13-10, pertaining to a dye penetrant inspection of the main…NTSB SEA79DYP32Accident · Serious injuriesClosedGrumman G-164A · Lewiston, IDNTSB SEA75DYG47Accident · No injuriesClosedGrumman G-164A · Deary, IDNTSB SEA70D0030Accident · No injuriesClosedGrumman G-164 · Minidoka, ID