NTSB investigations: Swearingen SA-226T
4 cases on aircraft the registry lists as Swearingen SA-226T, where the first occurrence was “In flight collision 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
| 1991 | 1 |
|---|---|
| 1993 | 1 |
| 1995 | 1 |
| 2001 | 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 ('8780122')
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\" = 230))
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 ('8780122')
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" = 230))
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 CHI01LA302Accident · No injuriesLimited investigationFinal reportSwearingen SA226-T · West Chicago, ILthe checklist not followed and the directional control not maintained by the pilot. A contributing factor was the left propeller’s start locks being engaged.NTSB LAX95FA338Accident · Minor injuriesField investigationFinal reportSwearingen SA-226T · Chino, CAThe pilot's improper IFR procedure by not initiating a missed approach at the outer marker, by attempting to intercept the glideslope from above after passing the outer marker, and by allowing the airplane to continue descending after reaching the decision…NTSB FTW93FA165Accident · 4 fatalField investigationFinal reportFairchild SA-226T · Santa Fe, NMThe pilot's poorly planned circling approach, and his failure to maintain an adequate altitude. Factors which contributed to the accident were: the dark night and a lack of visual reference.NTSB CHI92LA038Accident · No injuriesLimited investigationFinal reportSwearingen SA-226T · Iowa, IAThe pilot's failure to extend the landing gear which resulted in the propeller blades contacting the runway during the landing. A factor related to the accident was the pilot's failure to follow a checklist during the approach.