NTSB investigations: Schweizer G-164B
5 cases on aircraft the registry lists as Schweizer G-164B, where the first occurrence was “On ground/water encounter with terrain/water”. 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
| 1988 | 1 |
|---|---|
| 1989 | 1 |
| 1990 | 1 |
| 1991 | 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.\"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\" = 320))
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" = 320))
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 FTW92LA119Accident · No injuriesLimited investigationFinal reportSchweizer G-164B · Brinkley, ARThe pilot's failure to achieve proper airstrip alignment for landing, and the resultant loss of directional control.NTSB LAX91LA362Accident · No injuriesLimited investigationFinal reportSchweizer G164B · Verona, CAThe pilot's improper planning/decision to depart from a runway with high vegetation along the edge and subsequent collision with terrain.NTSB MKC90LA076Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Newport, ARFailure of the pilot to maintain proper runway alignment, which resulted in an encounter with soft/wet (muddy) terrain and a subsequent nose over of the aircraft.NTSB FTW89DRG04Accident · No injuriesFinal reportSchweizer G-164B · Austwell, TXPilot's selection of an unsuitable landing area (terrain). High vegetation and rough terrain were contributing factors.NTSB LAX88DVG09Accident · No injuriesFinal reportSchweizer G-164B · Robbins, CADuring landing roll, after an aerial application flight, the sprayboom became entangled in weeds. The airplane ground looped and nosed over. There were no reported mechanical failures or malfunctions of the airplane at the time of the accident.