NTSB investigations: Continental TSIO-520 series, 2001
44 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\") = 2001
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") = 2001
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 LAX02LA055Accident · No injuriesLimited investigationFinal reportCessna T210M · Santa Rosa, CAThe pilot's inadequate preflight and in-flight planning/decision resulting in miscalculation of fuel consumption, fuel exhaustion and loss of engine power. Factors were rough terrain in a vineyard, power lines in the landing area, and night time.NTSB IAD02LA020Accident · No injuriesLimited investigationFinal reportCessna 401A · Martinsburg, WVthe owner/mechanic's failure to comply with an Airworthiness Directive, which resulted in a cracked fuel supply line and subsequent in-flight fire.NTSB LAX02FA049Accident · 1 fatalField investigationFinal reportCessna T210L · San Jacinto, CAThe pilot's loss of situational awareness and his failure to adhere to the prescribed instrument approach procedures, including the track and altitudes flown. The underlying reasons for the pilot's loss of situational awareness are unknown.NTSB FTW02FA054Accident · 2 fatalField investigationFinal reportCessna T210-M · Monticello, ARThe separation of the #2 connecting rod and subsequent catastrophic failure of the engine. A factor was the in-flight collision with a vehicle while maneuvering to a emergency landing area.NTSB DEN02LA012Accident · Minor injuriesLimited investigationFinal reportCessna T210N · Montrose, COthe loss of engine power during initial climb for undetermined reason. A factor was the lack of suitable terrain for a forced landing.NTSB SEA02LA015Accident · No injuriesLimited investigationFinal reportCessna 402B · Pasco, WAthe pilot's failure to keep the aircraft from touching down short of the displaced threshold, and his failure to maintain directional control after the aircraft's left main gear tire deflated as a result of impacting the lip at the beginning of the subject…NTSB LAX02FA028Accident · 2 fatalField investigationFinal reportCessna 340A · Santa Monica, CAThe pilot's failure to remove the control gust lock prior to takeoff and his failure to abort the takeoff with sufficient runway remaining to stop the airplane on the runway.NTSB DEN02TA011Accident · No injuriesFinal reportCessna 206 · Casper, WYfailure to maintain aircraft control during landing. Contributing factors were the crosswind and gusting wind conditions.NTSB LAX02FA018Accident · 1 fatalField investigationFinal reportCessna P210N · Mt. Charleston, NVthe pilot's failure to maintain an adequate airspeed after continuing flight into forecast adverse meteorological conditions consisting of turbulence, icing, and downdrafts, which resulted in a stall/spin.NTSB CHI02LA010Accident · No injuriesLimited investigationFinal reportBeech 58P · Columbus, NEThe exceeded aircraft performance and inadequate preflight planning/preparation by the pilot in command. The lack of recent experience in aircraft by the pilot in command was a contributing factor.NTSB LAX02FA004Accident · No injuriesField investigationFinal reportPiper PA-28-140 · Van Nuys, CAThe failure of the air traffic controller to provide effective separation on the runway surface as specified in FAA Order 7110.65, Paragraph 3-9-6.NTSB FTW01LA210Accident · No injuriesLimited investigationFinal reportCessna T188C · Aiken, TXthe application of silicon sealant to the crankcase mating surfaces by maintenance personnel, which resulted in improper torque on the bolts which mate the crankcase halves, vibration, and the subsequent failure of the #2 main crankshaft bearing. A factor was…NTSB SEA01LA165Accident · No injuriesLimited investigationFinal reportCessna T210L · Olympia, WAThe inability of the landing gear to fully extend due to the failure of a hydraulic hose in the nose gear extension system.NTSB LAX01FA297Accident · 1 fatalField investigationFinal reportCessna T210M · Watsonville, CAThe loss of engine power for undetermined reasons.NTSB CHI01LA299Accident · No injuriesLimited investigationFinal reportBeech 58P · Theodosia, MODiminished braking action due to standing water on the runway. A factor associated with the accident was the ditch which the airplane contacted.NTSB FTW01LA191Accident · 1 fatalLimited investigationFinal reportPiper PA-46-310P · Bulverde, TXthe pilot's failure to obtain airspeed after rotation, which resulted in a stall/mush. Contributing factors were the tailwind condition, high density altitude, and upsloping runway.NTSB FTW01LA185Accident · Minor injuriesLimited investigationFinal reportBeech A-36TC · Fort Worth, TXthe partial loss of engine power for an undetermined reason and the pilot's decision to initiate the takeoff downwind.NTSB CHI01LA309Accident · No injuriesLimited investigationFinal reportCessna T210N · Fargo, NDthe emegency procedure not followed by the pilot.NTSB IAD01WA081Accident · 2 fatalForeign investigationCessna T210M · Innsbruck, AustriaNTSB CHI01LA271Accident · Minor injuriesLimited investigationFinal reportPiper PA-46-310P · Milwaukee, WIthe rich fuel mixture and the unsuitable landing area encountered by the pilot. Contributing factors were the high output of the fuel pump and the low altitude.NTSB CHI01LA269Accident · Serious injuriesLimited investigationFinal reportCessna P210N · Mackinac Island, MIThe pilot's failure to maintain proper glidepath during the landing approach resulting in the pilot not maintaining clearance from the trees. Factors were the haze, the gusty winds, and the trees.NTSB LAX01FA270Accident · 1 fatalField investigationFinal reportBeech B36TC · Weaverville, CAthe pilot's selection of the wrong runway, which resulted in an attempted takeoff uphill in a prevailing tailwind toward rising terrain and high obstacles. Also causal was the pilot's loading of the airplane above maximum gross weight and his failure to…NTSB DEN01LA131Accident · Minor injuriesLimited investigationFinal reportCessna T210M · Spanish Fork, UTthe pilot's inadequate compensation for the wind conditions which resulted in a loss of control during landing. A contributing factor was the gusty crosswind.NTSB SEA01LA159Accident · No injuriesLimited investigationFinal reportCessna TU-206F · Minden, NVThe pilot's inadequate recovery from a bounced landing, and his improper remedial action after it became clear that he was not successfully salvaging the landing attempt. Factors include an improperly serviced nose gear strut.NTSB FTW01LA170Accident · No injuriesLimited investigationFinal reportCessna T210N · Amarillo, TXthe pilot's failure to verify that the landing gear was extended and locked before landing. A contributing factor was a tripped landing gear motor circuit breaker, which resulted in the failure of the main landing gear to fully extend and lock.NTSB NYC01LA180Accident · Minor injuriesLimited investigationFinal reportCessna TU206G · Garrettsville, OHThe airstrip owner/pilot's failure to use all of the available runway. Factors were a tailwind condition and a contaminated runway.NTSB ANC01LA103Accident · No injuriesLimited investigationFinal reportCessna 207 · Pilot Point, AKThe pilot's selection of an unsuitable takeoff area, and failure to maintain clearance. A factor associated with the accident was a vehicle mounted gantry.NTSB NYC01LA174Accident · Serious injuriesLimited investigationFinal reportPiper PA-46-310P · Stow, MAThe pilot's failure to maintain airplane control during a go-around.NTSB LAX01LA248Accident · Minor injuriesLimited investigationFinal reportCessna T210M · Marble Canyon, AZThe pilot's failure to use all the available runway and his failure to follow the prescribed short field takeoff procedure resulting in a loss of control during the takeoff roll. Factors were the short, rough, and rising runway, and the soft dirt surrounding…NTSB NYC01LA166Accident · Minor injuriesLimited investigationFinal reportCessna 402C · Boston, MAThe pilot's improper decision to waive the wake turbulence hold time, and his subsequent loss of control when wake vortex turbulence was encountered.NTSB NYC01FA141Accident · 3 fatalField investigationFinal reportCessna P210N · Honesdale, PAAn improperly manufactured torquemeter gearshaft assembly, which resulted in gearshaft assembly failure, an N2 overspeed, and a subsequent uncontained engine failure.NTSB SEA01LA105Accident · No injuriesLimited investigationFinal reportCessna T210M · Portland, ORA burst hydraulic line and consequent total loss of hydraulic fluid from the landing gear, which disabled landing gear operation.NTSB DEN01LA102Accident · No injuriesLimited investigationFinal reportCessna T207A · Kanab, UTthe pilot's inadequate fuel consumption planning, and the subsequent fuel starvation, which resulted in a loss of engine power.NTSB LAX01LA164Accident · No injuriesLimited investigationFinal reportCessna T210N · Truckee, CAThe pilot's failure to maintain the proper descent and his failure to maintain directioinal control during landing.NTSB NYC01FA109Accident · 2 fatalField investigationFinal reportBeech A-36 · Middletown, RIThe pilot's failure to maintain airspeed while landing.NTSB CHI01WA123Accident · 2 fatalForeign investigationCessna T310R · Madinah, Saudi ArabiaNTSB DEN01LA087Accident · No injuriesLimited investigationFinal reportMooney M20K · Bountiful, UTthe failure of the airplane's electrical system for an undetermined reason, which resulted in the collapse of the left main gear on landing.NTSB FTW01LA096Accident · No injuriesLimited investigationFinal reportCessna T210M · Abilene, TXthe loss of engine power while on final approach due to fuel starvation as a result of the pilot's improper use of the fuel selector. A contributing factor was the elevated runway edge.NTSB DEN01LA073Accident · No injuriesLimited investigationFinal reportCessna 340 · Alamosa, COThe in-flight collision with a large bird during downwind approach for landing.NTSB MIA01LA096Accident · Serious injuriesLimited investigationFinal reportCessna T210L · Brevard, NCan in-flight collision with a tree. Factors in this accident were the pilot's inadequate planned approach and excessive airspeed on the approach.NTSB SEA01LA052Accident · No injuriesLimited investigationFinal reportCessna 402B · Billings, MTBest rate-of-climb single-engine speed was not maintained. Delayed remedial action was a factor.NTSB MIA01LA080Accident · Serious injuriesLimited investigationFinal reportCessna P210N · Seminole, ALthe pilot's improper inflight planning/decision and failure to refuel en route and ensure an adequate supply of fuel to safely complete the flight to his destination with adequate reserves, which resulted in fuel exhaustion, subsequent engine failure, and a…NTSB DEN01LA042Accident · No injuriesLimited investigationFinal reportCessna P210N · Pagosa Springs, COfailure to maintain directional control of the aircraft after an encounter with adverse weather during landing roll. A factor was ground fog.NTSB SEA01LA038Accident · No injuriesLimited investigationFinal reportCessna 402B · Ontario, ORPilot's failure to maintain aircraft control while landing. Factors include a snow covered runway.