NTSB investigations: Swearingen SA-226AT
9 cases on aircraft the registry lists as Swearingen SA-226AT. 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
| 1975 | 1 |
|---|---|
| 1980 | 1 |
| 1986 | 1 |
| 1989 | 1 |
| 1995 | 1 |
| 2008 | 1 |
| 2010 | 1 |
| 2014 | 1 |
| 2021 | 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 ('8780405'))
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 ('8780405'))
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 ERA22FA086Accident · 1 fatalClass 3 · FieldFinal reportSwearingen SA226 · Bedford, NHThe pilot’s failure to secure and feather the left engine and increase power on the right engine after a perceived loss of engine power in the left engine, which resulted in a loss of control and impact with terrain just short of the runway. Contributing to…NTSB ERA14CA276Accident · Minor injuriesData collectionFinal reportSwearingen SA 226AT · Dayton, TNThe pilot's failure to extend the landing gear during the approach, which resulted in a gear-up landing.NTSB CEN10CA261Accident · No injuriesData collectionFinal reportSwearingen SA-226AT · West Memphis, ARFailure of both pilots to ensure that the airplane was properly configured for landing.NTSB CHI08CA074Accident · No injuriesData collectionFinal reportSwearingen SA-226AT · Ankeny, IAThe pilot's failure to maintain directional control during the takeoff roll. Contributing to the accident was the snow on the runway and the snowbank.NTSB CHI96LA053Accident · No injuriesLimited investigationFinal reportSwearingen SA-226AT · Detroit, MIthe pilot's failure to extend the landing gear. A factor in the accident was the pilot's diverted attention.NTSB MIA89FA138Accident · No injuriesField investigationFinal reportSwearingen SA-226-AT · Jacksonville, FLThe failure of the pilot in command to use the airplane landing checklist and assure that the landing gear was down and locked prior to landing.NTSB DEN86FA128Accident · 1 fatalField investigationFinal reportSwearingen SA226AT · Billings, MTWhile on an IFR flt plan in IMC, the plt executed a missed approach after flying a localizer back course 27 approach. During a subsequent ILS rwy 09L approach, radio and radar contact with the acft was lost lost. The acft wreckage was located on the inbound…NTSB NYC80FA025Accident · Minor injuriesClosedSwearingen SA226 · Glens Falls, NYNTSB IAD75AI057Accident · 2 fatalClosedSwearingen 226AT · Southern Pines, NC