NTSB investigations: Grumman G-164A, AZ
15 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 |
|---|---|
| 1972 | 2 |
| 1973 | 1 |
| 1974 | 1 |
| 1975 | 2 |
| 1976 | 1 |
| 1977 | 2 |
| 1978 | 1 |
| 1982 | 2 |
| 1989 | 1 |
| 1992 | 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\" = 'AZ' 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" = 'AZ' 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 LAX92LA358Accident · No injuriesLimited investigationFinal reportGrumman G-164A · Laveen, AZThe failure of the pilot to maintain directional control of the aircraft during the landing roll.NTSB LAX89DUJ07Accident · No injuriesFinal reportGrumman G-164A · Eloy, AZInaequate preflight by the pilot, which resulted in fuel starvation during the climb after takeoff, due to very little fuel remaining in the tanks. The rough/uneven desert terrain was considered to be a contributing factor.NTSB LAX82DA353Accident · No injuriesFinal reportGrumman G-164A · Magma, AZShortly after takeoff the eng became rough & losing power. The plt observed long streaks of red flame pouring from the exhaust. The pesticide was jettisoned & an attempt was made to return to the strip. The eng continued to lose power & quit completely just…NTSB LAX82DA271Accident · Minor injuriesFinal reportGrumman G-164A · Chandler, AZWhile spraying at night & during the fourth pass under power lines crossing the field, the acft contacted the wires. After the accident the flagger at the field informed the plt that the wind was causing the wires to whip up & down at times.NTSB LAX78FUJ87Accident · 1 fatalClosedGrumman G-164A · Buckeye, AZNTSB LAX77FUJ99Accident · Serious injuriesClosedGrumman G-164A · Casa Grande, AZNTSB LAX77FUJ44Accident · No injuriesClosedGrumman G-164A · Queen Creek, AZNTSB LAX76DUJ59Accident · No injuriesClosedGrumman G-164A · Yuma, AZNTSB LAX76DUJ32Accident · No injuriesClosedGrumman G-164A · Buckeye, AZNTSB LAX76FUJ21Accident · No injuriesClosedGrumman G-164A · Litchfld Park, AZNTSB LAX75DUJ34Accident · No injuriesClosedGrumman G-164 · Aguila, AZNTSB LAX74DUJ38Accident · No injuriesClosedGrumman G-164A · Tonopah, AZNTSB LAX73DUJ31Accident · No injuriesClosedGrumman G-164A · Queen Creek, AZNTSB LAX73FUJ06Accident · No injuriesClosedGrumman G-164A · Guadalupe, AZNTSB LAX70D0166Accident · No injuriesClosedGrumman 164A · Ltchfld Prk, AZ