Fatal NTSB investigations: Continental TSIO-520 series, 2010

13 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

19682026
Fatal NTSB investigations: Continental TSIO-520 series, 2010 per year, 1968–2026: 397 cases
19681
19721
19731
19741
19762
19772
197810
197910
198011
198111
198213
198310
19849
198510
198611
19879
198810
19892
19903
19919
19925
19934
19948
19956
19964
19978
19984
19994
20004
200111
200212
200320
200413
200510
200616
200711
20088
20093
201013
20118
20129
20139
20146
20153
20167
20179
20187
20194
20208
20217
20223
20236
20245
20255
20261

Latest 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\") = 2010
    AND c.\"highestInjuryLevel\" = 'Fatal'
    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.

NTSB CEN11FA133Accident · 2 fatalField investigationFinal reportPiper PA-46-310P · Milaca, MNThe pilot did not recover from an unusual attitude while operating in instrument meteorological conditions following a disconnect of the autopilot system for undetermined reasons. Contributing to the accident were the pilot’s lack of recent flight experience…Dec 30, 2010 · N9103N · Substantial damageNTSB CEN11FA075Accident · 1 fatalField investigationFinal reportHawker-Beechcraft A36 · Oklahoma City, OKThe pilot’s loss of control of the airplane during night instrument meteorological conditions, likely due to spatial disorientation.Nov 18, 2010 · N314DP · Substantial damageNTSB ERA11FA036Accident · 2 fatalField investigationFinal reportBeech B36TC · Rienzi, MSThe pilot's continued flight into known adverse weather conditions. Contributing to the accident was the air traffic controller's failure to provide precipitation information to the pilot as required.Oct 26, 2010 · N8045Y · Substantial damageNTSB WPR11FA029Accident · 3 fatalField investigationFinal reportCessna 340A · Morton, WAThe pilot’s failure to arrest the excessive rate of turn into the failed engine, which resulted in a loss of control and subsequent impact with terrain. Contributing to the accident was a partial loss of engine power for reasons that could not be determined…Oct 25, 2010 · N68718 · Substantial damageNTSB WPR10FA459Accident · 2 fatalField investigationFinal reportCessna T210N · Coeur d'Alene, IDThe pilot’s continued flight into instrument meteorological conditions and failure to maintain clearance with mountainous terrain while maneuvering in an area of low cloud ceilings.Sep 17, 2010 · N111NA · Substantial damageNTSB CEN10FA520Accident · 2 fatalField investigationFinal reportCessna T210 · Mountain Home, ARThe pilot’s decision to continue flight into a known area of heavy rain and his subsequent failure to maintain aircraft control.Sep 7, 2010 · N2081U · Substantial damageNTSB ANC10WA073Accident · 1 fatalForeign investigationBeech B36TC · Peace River, CanadaJul 24, 2010 · N64631 · Substantial damageNTSB ERA10GA320Accident · 3 fatalFinal reportCessna T210L · Lock Haven, PAThe total loss of engine power resulting from the fatigue failure of the engine's number 2 cylinder exhaust valve. The fatigue failure was due to valve guide wear that led to excessive clearance between the valve and valve guide. Contributing to the accident…Jun 21, 2010 · N30266 · Substantial damageNTSB CEN10FA324Accident · 5 fatalField investigationFinal reportCessna T310R · Ruidoso, NMThe pilot did not maintain proper airspeed on final approach for landing, which resulted in an aerodynamic stall and impact with terrain. Contributing to the accident was the pilot’s limited experience in the airplane make and model.Jun 17, 2010 · N310RH · Substantial damageNTSB CEN10FA180Accident · 2 fatalField investigationFinal reportBeech B36TC · Dayton, OHThe complete loss of engine power due to failure of the No. 1 main bearing, and the secondary failure of a crankcase through-bolt and the fuel pump drive coupling. Contributing to the accident was the pilot's decision to attempt a return to the airport for a…Apr 1, 2010 · N4BA · DestroyedNTSB ERA10FA195Accident · 1 fatalField investigationFinal reportPiper PA46 · Roanoke, VAA malfunction of the flight controls for undetermined reasons.Mar 30, 2010 · N6913Z · DestroyedNTSB ERA10FA161Accident · 1 fatalField investigationFinal reportCessna T303 · Louisa, VAThe pilot's failure to maintain aircraft control and secure the right engine during a loss of engine power after takeoff. Contributing to the accident was the loss of engine power on the right engine for undetermined reasons.Mar 4, 2010 · N9305T · Substantial damageNTSB ERA10FA140Accident · 5 fatalField investigationFinal reportCessna T337G · Farmingdale, NJThe pilots’ failure to adhere to the airplane’s operating limitations, which resulted in overload failure of the right wing. Findings of the investigation were the adverse effects of multiple supplemental type certificates (STC) to the airframe wing structure…Feb 15, 2010 · N12NA · Substantial damage