NTSB investigations: Schweizer G-164B
6 cases on aircraft the registry lists as Schweizer G-164B, 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
| 1986 | 1 |
|---|---|
| 1989 | 1 |
| 1998 | 2 |
| 2002 | 1 |
| 2003 | 1 |
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 ('8059055')
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 ('8059055')
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 FTW03CA180Accident · No injuriesData collectionFinal reportSchweizer G-164B · Vega, TXThe failure of the left brake for undetermined reasons.NTSB LAX02LA216Accident · No injuriesLimited investigationFinal reportGrumman-Schweizer G-164B · Sacramento, CAPropeller blade failure due to fatigue. A contributing factor was the rising embankment.NTSB SEA98LA106Accident · No injuriesLimited investigationFinal reportSchweizer G-164B · Oakdale, WAA fatigue failure of the number three cylinder exhaust rocker box assembly, compromising the ability of the exhaust valve to operate. Factors include a ditch at the end of the runway.NTSB FTW98LA252Accident · No injuriesLimited investigationFinal reportGrumman-Schweizer G-164B · Coy, ARfailure of the left main tire, which resulted in the pilot's inability to maintain directional control of the airplane during the landing roll.NTSB MKC89LA068Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Harrisburg, ARThe failure of the hydraulic line which rendered the brake system inoperative.NTSB MKC86LA061Accident · Minor injuriesLimited investigationFinal reportSchweizer G164-B · Colt, ARThis was a new acft which the owner was ferrying from the dealer to his private ag strip. The landing was made to the north on a half mile long grass strip and the wind was calm. The plt reports that the brakes were locked when the acft touched down and the…