NTSB investigations: Grumman G-164
6 cases on aircraft the registry lists as Grumman G-164, where the first occurrence was “Airframe/component/system failure/malfunction”. 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
| 1982 | 1 |
|---|---|
| 1984 | 1 |
| 1989 | 1 |
| 1992 | 1 |
| 1994 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('3952702')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 130))
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 ('3952702')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 130))
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 MIA97LA201Accident · No injuriesLimited investigationFinal reportGrumman G-164 · Altha, FLThe failure of the left main landing gear spring due to a preexisting fatigue crack resulting in the separation of the left main landing gear, and subsequent nose down during taxi.NTSB FTW94LA087Accident · No injuriesLimited investigationFinal reportGrumman G-164 · Almyra, ARThe partial failure of the brake master cylinder assembly for undetermined reasons. A factor was the soft terrain adjacent to the runway.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 FTW89DPJ08Accident · Serious injuriesFinal reportGrumman G-164 · Guymon, OKFailure of the upper right engine mount (firewall attach bolt) due to fatigue, and failure of the lower right mounting bolt for an unknown reason, which allowed overload failure of the two remaining mounting bolts and separation of the engine.NTSB FTW84LA366Accident · No injuriesLimited investigationFinal reportGrumman G-164 · Oak Grove, LAAircraft landed with a flat left main tire, veered left and nosed over inverted.NTSB LAX82DA127Accident · No injuriesFinal reportGrumman G-164 · Bakersfield, CAOn takeoff roll the right main tire blew causing the aircraft to veer to the right, leave the runway, and nose over in the soft mud.