NTSB investigations: Continental TSIO-550-K, 2024
7 cases on aircraft whose registry engine model is Continental TSIO-550-K. 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
| 2014 | 2 |
|---|---|
| 2015 | 1 |
| 2016 | 2 |
| 2017 | 3 |
| 2018 | 5 |
| 2019 | 1 |
| 2020 | 2 |
| 2022 | 4 |
| 2023 | 4 |
| 2024 | 7 |
| 2025 | 15 |
| 2026 | 10 |
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 year(c.\"eventDate\") = 2024
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17410'))
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 year(c."eventDate") = 2024
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17410'))
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 WPR25LA041Accident · No injuriesClass 4 · LimitedFinal reportCirrus Design SR22T · Palm Springs, CAThe pilot’s failure to maintain clearance from a commercial airliner which resulted in an encounter with wake turbulence and subsequent loss of control resulting in impact with terrain.NTSB CEN24LA309Accident · No injuriesClass 4 · LimitedFinal reportCirrus SR22 · Salem, INThe pilot’s excessive airspeed during a landing, which resulted in a runway overrun and collision with terrain.NTSB CEN24LA308Incident · No injuriesClass 3 · LimitedFinal reportCirrus Design SR22T · Tulsa, OKThe mechanic’s improper installation of the alternator wiring connections, which resulted in electrical arcing and thermal damage to the airplane.NTSB CEN24LA236Accident · No injuriesClass 3 · LimitedFinal reportCirrus Design SR22T · Boerne, TXMaintenance personnel’s inadequate adjustment of fuel flow, which resulted in an excessively rich mixture, a rough-running engine, and a subsequent partial loss of engine power.NTSB CEN24LA190Accident · No injuriesClass 4 · LimitedFinal reportCirrus Design SR22T · Shreveport, LAThe airplane’s collision with a deer on the runway during landing.NTSB ANC24LA026Accident · Serious injuriesClass 4 · LimitedFinal reportCirrus Design SR22T · Paso Robles, CAThe flight instructor’s failure to maintain adequate airspeed during landing which resulted in a loss of directional control and runway excursion. Contributing to the accident was the pilot receiving instructions failure to maintain runway alignment.NTSB WPR24FA103Incident · No injuriesClass 3 · FieldFinal reportCirrus Design SR22T · Bellevue, WAA total loss of engine power due to a fatigue fracture of the crankshaft.