NTSB investigations: Continental TSIO-520 series, 1990
26 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
| 1966 | 3 |
|---|---|
| 1968 | 1 |
| 1969 | 2 |
| 1970 | 1 |
| 1971 | 2 |
| 1972 | 3 |
| 1973 | 4 |
| 1974 | 12 |
| 1975 | 8 |
| 1976 | 22 |
| 1977 | 21 |
| 1978 | 37 |
| 1979 | 54 |
| 1980 | 44 |
| 1981 | 54 |
| 1982 | 60 |
| 1983 | 40 |
| 1984 | 44 |
| 1985 | 47 |
| 1986 | 55 |
| 1987 | 38 |
| 1988 | 29 |
| 1989 | 23 |
| 1990 | 26 |
| 1991 | 33 |
| 1992 | 24 |
| 1993 | 26 |
| 1994 | 35 |
| 1995 | 25 |
| 1996 | 34 |
| 1997 | 31 |
| 1998 | 23 |
| 1999 | 27 |
| 2000 | 35 |
| 2001 | 44 |
| 2002 | 39 |
| 2003 | 57 |
| 2004 | 42 |
| 2005 | 36 |
| 2006 | 56 |
| 2007 | 43 |
| 2008 | 38 |
| 2009 | 29 |
| 2010 | 48 |
| 2011 | 25 |
| 2012 | 27 |
| 2013 | 29 |
| 2014 | 22 |
| 2015 | 21 |
| 2016 | 20 |
| 2017 | 34 |
| 2018 | 29 |
| 2019 | 22 |
| 2020 | 26 |
| 2021 | 26 |
| 2022 | 22 |
| 2023 | 23 |
| 2024 | 17 |
| 2025 | 25 |
| 2026 | 13 |
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\") = 1990
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 year(c."eventDate") = 1990
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 MIA91WA054Accident · Serious injuriesForeign investigationCessna 401B · Marsh Harbor, BahamasNTSB CHI91LA036Accident · No injuriesLimited investigationFinal reportCessna T210M · Marshall, MIDirectional control not maintained by the PIC.NTSB NYC91LA031Accident · No injuriesLimited investigationFinal reportBeech B36TC · Caldwell, NJPremature rotation and an inadvertent stall. Factors include lack of total experience in this type of aircraft.NTSB CHI91LA019Accident · No injuriesLimited investigationFinal reportCessna 150 · La Crosse, WIInadequate visual outlook by the PIC.NTSB SEA91LA009Accident · No injuriesLimited investigationFinal reportCessna T210N · Laramie, WYThe pilot did not properly set the mixture control.NTSB DEN91LA006Accident · No injuriesLimited investigationFinal reportCessna T210M · Englewood, COEngine failiure resulting from maintenance discrepancies.NTSB DEN91FA002Accident · 1 fatalField investigationFinal reportCessna T210N · Gypsum, COThe pilot flying into known adverse icing and thunderstorm weather conditions which resulted in the loss of control of the aircraft.NTSB MIA90LA192Accident · No injuriesLimited investigationFinal reportCessna 402B · St. ThomasSeparation of the left main landing gear torque tube bracket assembly due to sheared rivets from a previous hard side load landing which was not reported.NTSB DEN90LA173Accident · No injuriesLimited investigationFinal reportCessna T-210-L · Edgewood, NMEngine failure due to a broken connecting rod. A factor was the rough uneven terrain available for the forced landing.NTSB DEN90DTE06Accident · Serious injuriesFinal reportCessna 188A · Holyoke, COA stall mush which occurred when the pilot retracted the flaps prematurely following takeoff, causing the aircraft to settle into the ground.NTSB ANC90LA132Accident · No injuriesLimited investigationFinal reportCessna C-T210 · Sleeper Bay, AKImproper fuel tank selection.NTSB LAX90LA258Accident · No injuriesLimited investigationFinal reportCessna 340-A · Truckee, CAThe pilots loss of brake performance due to hydroplaning.NTSB DEN90FA159Accident · 1 fatalField investigationFinal reportCessna P210R · Ogden, UTFailure of the #1 piston due to pre-ignition/detonation in the #1 cylinder, and inadequate visual lookout by the pilot (his failure to see-and-avoid the obstruction). The obstruction (power line) was a related factor.NTSB ATL90LA142Accident · No injuriesLimited investigationFinal reportCessna T210L · Memphis, TNFuel mismanagement by the pilot which resulted in fuel starvation during final approach.NTSB DEN90LA158Accident · No injuriesLimited investigationFinal reportCessna T-188 · Devils Lake, NDThe pilot's failure to refuel, resulting in fuel exhaustion. A forced landing in rough terrain is a factor.NTSB LAX90LA242Accident · No injuriesLimited investigationFinal reportCessna 340 · Salinas, CAThe failure of maintenance personnel to reinstall the landing gear retract/extension linkage and the failure of inspection personnel to detect the improper installation.NTSB DEN90LA150Accident · No injuriesLimited investigationFinal reportCessna T 188C · Wray, COThe failure of the pilot to maintain proper alignment proper alignment during landing.NTSB SEA90LA110Accident · No injuriesLimited investigationFinal reportCessna 340A · Priest River, IDThe pilot's misjudgement of distance and altitude and his failure to maintain an adequate airspeed during the landing approach.NTSB CHI90LA151Accident · No injuriesLimited investigationFinal reportCessna T210N · Wheeling, ILPilot-in-command's failure to obtain a proper flare attitude in the aircraft prior to touchdown.NTSB SEA90LA093Accident · No injuriesLimited investigationFinal reportCessna TU206G · Elk City, IDThe pilot did not maintain directional control of the airplane during the landing roll. The landing was made on a wet runway with excessive airspeed.NTSB CHI90DEM03Accident · No injuriesFinal reportCessna T188 · Williamsburg, MIA loss of engine power for undetermined reasons. The lack of suitable terrain for landing was a factor related to the accident.NTSB ATL90LA097Accident · No injuriesLimited investigationFinal reportCessna T210 · Lafayette, GAThe pilot's failure to properly manage his fuel supply, which resulted in a loss of engine power, due to fuel starvation.NTSB SEA90FA066Accident · 2 fatalField investigationFinal reportMooney M20K · Carson City, NVThe pilot failed to maintain airspeed during takeoff. A contributing factor was the high density altitude.NTSB LAX90LA136Accident · Minor injuriesLimited investigationFinal reportCessna T210L · Chino, CAFuel starvation due to the fuel tank outlets becoming unported as the aircraft maneuvered for landing. A factor was the pilot's preflight planning failed to insure that he had adequate fuel for the flight.NTSB MIA90LA099Accident · No injuriesLimited investigationFinal reportCessna P210N · Natchez, MSThe late extension of the landing gear by the pilot.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.