NTSB investigations: Continental TSIO-520 series, KS
17 cases on aircraft whose registry engine model is Continental TSIO-520 series. 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
| 1978 | 1 |
|---|---|
| 1980 | 1 |
| 1981 | 2 |
| 1983 | 1 |
| 1984 | 1 |
| 1988 | 1 |
| 1990 | 1 |
| 1994 | 1 |
| 1995 | 1 |
| 1996 | 1 |
| 1999 | 1 |
| 2003 | 1 |
| 2004 | 1 |
| 2007 | 1 |
| 2008 | 1 |
| 2015 | 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.\"eventStateOrRegion\" = 'KS' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17040'))
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."eventStateOrRegion" = 'KS' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17040'))
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 CEN15CA184Accident · No injuriesData collectionFinal reportCessna T188C · Burdett, KSThe pilot did not maintain directional control of the airplane in gusting wind conditions.NTSB DEN08FA059Accident · 2 fatalField investigationFinal reportCessna 414A · Benton, KSThe pilot's failure to maintain clearance from the trees. Contributing to the accident was the pilot's flight into known adverse weather conditions and the low clouds and visibility.NTSB DEN07LA135Accident · No injuriesLimited investigationFinal reportCessna T188C · Colby, KSThe pilot's failure to maintain directional control during the take-off roll resulting in a ground loop.NTSB CHI04CA135Accident · Minor injuriesData collectionFinal reportCessna T210L · Wichita, KSThe pilot's inadequate in-flight planning/decision which resulted in fuel exhaustion and the loss of engine power.NTSB CHI03LA159Accident · No injuriesLimited investigationFinal reportCessna T210N · Tribune, KSThe in-flight separation of the turbocharger exhaust band clamp resulting in an in-flight fire and uncommanded landing gear extension. Also causal was the improper maintenance by unknown personnel.NTSB CHI99FA177Accident · 2 fatalField investigationFinal reportCessna 340A · Phillipsburg, KSthe pilot not maintaining flying speed. Factors to the accident were the fuel transfer problem of unknown origin.NTSB CHI96FA171Accident · No injuriesField investigationFinal reportCessna 401 · Great Bend, KSthe failure of the exhaust header. Additional factors include the visual restrictions which prevented a detailed examination of the exhaust system, and the inadequate inspection procedures required in AD 75-23-08 R5.NTSB CHI95LA137Accident · Serious injuriesLimited investigationFinal reportCessna P210N · Dodge City, KSfatigue and subsequent catastrophic failure of the connecting rod originating from the decarburized area on the shank of the rod. Factors were the low cloud weather condition and the ditch.NTSB CHI94LA073Accident · Serious injuriesLimited investigationFinal reportCessna T210M · Olathe, KSthe pilot's failure to follow procedures and directives regarding the positioning of the fuel tank selector to the fullest tank for the landing portion of flight.NTSB MKC90FA044Accident · Serious injuriesField investigationFinal reportCessna P210N · Newton, KSLoss of engine power for an undetermined reason. Darkness and the resultant delay in flaring to land were related factors.NTSB MKC88LA048Accident · No injuriesLimited investigationFinal reportCessna T-188C · Goodland, KSWhile flying a certificated experimental ag acft, for purpose of compliance with FAR regulations, the employee of the federal aviation administration lost control during landing rollout. The wind conditions, relative to the runway, were about a 80 degree…NTSB MKC84LA107Accident · No injuriesLimited investigationFinal reportCessna 340 · Olathe, KSThe acft skidded off the rwy into slush covered terrain alongside the rwy, dragging the left gear in the mud. As the acft continued its fwd roll the main gear struck the edge of a taxiway & collapsed backwards. The rwy was covered with slush at the time of…NTSB MKC84LA008Accident · Minor injuriesLimited investigationFinal reportCessna P210N · Lawrence, KSThe plt reported that prior to flt, the fuel gages indicated both tanks were full; however, he did not visually verify the quantity of fuel. During flt, in the vicinity of emporia, KS, the eng lost power while using fuel from the left tank. The plt changed…NTSB MKC82DCQ04Accident · No injuriesClosedCessna P210N · Fort Scott, KSNTSB MKC81FCQ48Accident · Minor injuriesClosedCessna T210N · Wichita, KSNTSB MKC80DCQ24Accident · Minor injuriesClosedCessna 210P · Pratt, KSNTSB MKC78FCQ20Accident · Serious injuriesClosedCessna 210 · Marysville, KS