Fatal NTSB investigations: Swearingen SA-226T
8 cases on aircraft the registry lists as Swearingen SA-226T. 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
| 1977 | 2 |
|---|---|
| 1981 | 1 |
| 1982 | 1 |
| 1985 | 1 |
| 1988 | 1 |
| 1993 | 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.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('8780122'))
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."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('8780122'))
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 FTW98FA073Accident · 1 fatalField investigationFinal reportSwearingen SA226-T · Byers, COThe pilot inadvertently stalling the airplane and his subsequent spatial disorientation which prevented him from maintaining airplane control. Factors were excessive workload on the pilot and the dark night light conditions.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 CHI88FA041Accident · 3 fatalField investigationFinal reportFairchild SA226T · Pontiac, MIAcft was scheduled for an instructional flt. During the wx briefing, the CFI told the fss specialist that the flt would include eng-out practice. Witness statements indicate that the acft rolled sharply to the rt and nosed down after attaining about 100 ft of…NTSB FTW85LAMS2Accident · 1 fatalFinal reportSwearingen SA-226T · MissingA distress message was received from the pilot stating he was 100 miles south of grand isle, LA, and had lost an eng andwas unable to maintain altitude. A second message was received shortly afterwards stating that the aircraft was at 1500 feet and the pilot…NTSB DCA82AA012Accident · 3 fatalFinal reportSwearingen SA226-T(B) · Rockport, TXPrior to the faf during a vor/dme approach, the merlin was cleared to change to the UNICOM freq. The plt of the merlin contacted UNICOM & requested an arpt advisory. The UNICOM operator replied that there was a PIREP of 500 ft over the field with 2 mi…NTSB FTW81FA105Accident · 2 fatalClosedSwearingen SA226T · Cameron, LANTSB MIA77RA036Accident · 1 fatalClosedSwearingen SA226T · Nassau, Burkina FasoNTSB FTW77FA033Accident · 2 fatalClosedSwearingen SA266T · Beckmam, TX