Fatal NTSB investigations: Swearingen SA226TC
6 cases on aircraft the registry lists as Swearingen SA226TC. 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
| 1980 | 1 |
|---|---|
| 1984 | 1 |
| 1987 | 1 |
| 1993 | 1 |
| 2000 | 1 |
| 2006 | 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 ('8780404'))
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 ('8780404'))
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 ATL06FA045Accident · 1 fatalField investigationFinal reportSwearingen SA-226-TC · Paris, TNThe pilot's inflight loss of control following a reported fuel asymmetry condition for undetermined reasons.NTSB CHI01FA032Accident · 1 fatalField investigationFinal reportSwearingen SA226TC · Fort Wayne, INThe indicated failure of the right hand AC bus during takeoff with low ceiling. The factors were the low ceiling, night, and the execssive workload the pilot experienced on takeoff with an electrical failure without a second in command.NTSB NYC93FA159Accident · 2 fatalField investigationFinal reportSwearingen SA-226-TC · Hartford, CTFailure of the copilot (second-in-command) to follow the checklist, assure the gear was extended for landing and attain or maintain adequate airspeed (VMC); and failure of the pilot-in-command (PIC) to properly supervise the flight and take sufficient…NTSB ATL87FA123Accident · 2 fatalField investigationFinal reportSwearingen SA-226TC · Wilmington, NCThe right engine failed during takeoff immediately after rotation 3000' down the 7,002' rwy 16. The plt continued the flt and the landing gear remained extended. The unauthorized plt rated pax made xmissions to the tower. Witnesses rpted that the acft reached…NTSB DCA84AA015Accident · 3 fatalFinal reportSwearingen SA226TC · Terre Haute, INAfter taking off from rwy 23, the acft crashed ssw of the arpt about 6300 ft from the departure end of the rwy & about 1800 ft to the left of the rwy centerline. Impact occurred while the acft was in a steep descent. The wreckage path was scattered along a…NTSB DCA80AA019Accident · 13 fatalClosedSwearingen 226TC · Valley, NE