NTSB investigations: Grumman G-164
15 cases on aircraft the registry lists as Grumman G-164, where the first occurrence was “In flight collision with object”. 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 |
|---|---|
| 1986 | 1 |
| 1988 | 1 |
| 1992 | 1 |
| 1994 | 1 |
| 1995 | 2 |
| 1996 | 2 |
| 1997 | 1 |
| 1998 | 1 |
| 2000 | 1 |
| 2003 | 1 |
| 2004 | 2 |
Where
Latest 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\" = 220))
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" = 220))
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 FTW04CA185Accident · Serious injuriesData collectionFinal reportGrumman G-164 · Havana, ARThe pilot's failure to maintain clearance with the power lines while maneuvering during an aerial application flight.NTSB SEA04LA093Accident · Minor injuriesLimited investigationFinal reportGrumman G-164 · Rexburg, IDThe pilot's failure to maintain clearance from an object while maneuvering during an aerial application flight. Contributing factors were the pilot's diverted attention and the irrigation pivot.NTSB NYC03LA120Accident · No injuriesLimited investigationFinal reportGrumman G-164 · Shiloh, NJThe pilot's improper in-flight decision to not jettison his load when he realized that he would not clear the trees. A factor was the pilot's inattention to his airspeed at liftoff and on climb.NTSB CHI00LA210Accident · No injuriesLimited investigationFinal reportGrumman G164 · Mcville, NDthe pilot's failure to maintain clearance with the power lines. A factor associated with the accident was the power line.NTSB FTW98LA161Accident · Serious injuriesLimited investigationFinal reportGrumman G-164 · St. Joseph, LAThe pilot's failure to maintain clearance from the trees. A factor was the lack of suitable terrain for the ensuing forced landing.NTSB CHI97LA150Accident · Serious injuriesLimited investigationFinal reportGrumman G164 · Illinois City, ILfailure of the pilot to see and maintain clearance from a static wire. The proximity of the wire was a related factor.NTSB ATL96LA111Accident · Minor injuriesLimited investigationFinal reportGrumman G-164 · Montezuma, GAfailure of the pilot to maintain adequate visual look out, while maneuvering on an aerial application run, which result in his failure to see-and-avoid a power line.NTSB ATL96LA110Accident · Minor injuriesLimited investigationFinal reportGrumman-Schweizer 164 · Bainbridge, GAThe pilot's misjudgment of the clearance from the trees during the swath run that resulted in the collision.NTSB SEA95LA191Accident · No injuriesLimited investigationFinal reportSchweizer G-164 · Nyssa, ORthe pilot's inadequate ground reconnaissance.NTSB FTW95LA331Accident · No injuriesLimited investigationFinal reportGrumman G-164A · St.Francisville, LAThe pilot's failure to maintain clearance with the obstruction on short final. A factor was the low visibility.NTSB CHI94LA166Accident · Serious injuriesLimited investigationFinal reportGrumman G-164 · Hillsboro, NDthe pilot's failure to maintain clearance from a tree.NTSB FTW92LA123Accident · Serious injuriesLimited investigationFinal reportGrumman G164 · Bayside, TXThe pilot's inadequate visual lookout.NTSB DEN88LA131Accident · No injuriesLimited investigationFinal reportGrumman G-164 · Ayr, NDNTSB FTW86FRG24Accident · No injuriesFinal reportGrumman G-164 · La Feria, TXAs the plt was making a swath run, he started to cross under power lines, but saw the profile view of a road marker. When he pulled up to avoid the road marker, the acft struck the wires, rolled to the left & collided with the ground.NTSB LAX82DVG26Accident · No injuriesFinal reportGrumman G-164 · Williams, CAThe pilot was applying a granular herbicide to a rice field with low voltage wires on the west border and high voltage lines located diagonally across the field. During a pass from west to east, he crossed over the low voltage wires and lowered the nose to…