NTSB investigations: Continental TSIO-520 series, CA

5 cases on aircraft whose registry engine model is Continental TSIO-520 series, where the first occurrence was “Loss of engine power(total) - mech failure/malf”. 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

19882026
NTSB investigations: Continental TSIO-520 series, CA per year, 1988–2026: 5 cases
19881
19931
19971
20021
20061

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 c.\"eventStateOrRegion\" = 'CA' 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')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 351))
  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 LAX06LA094Accident · Minor injuriesLimited investigationFinal reportCessna T210N · Mariposa, CAThe failure of the maintenance personnel to follow the procedures in the TCM maintenance manual and adequately torque the engine through-bolts, which led to the separation of the No. 6 cylinder and the catastrophic failure of the engine.Jan 24, 2006 · N4791C · Substantial damageNTSB LAX02FA163Accident · 2 fatalField investigationFinal reportCessna T210M · Groveland, CAa catastrophic engine failure due to the fatigue fracture and failure of the crankshaft. A factor contributing to the accident was the unsuitable nature of the mountainous terrain for a successful forced landing. The precipitating cause of the fatigue…May 13, 2002 · N761LX · DestroyedNTSB LAX97LA307Accident · No injuriesLimited investigationFinal reportCessna T210M · San Martin, CAInstallation of improper connecting hardware by maintenance personnel, and, the inadequate inspection of the installed hardware by inspection personnel resulting in separation of the engine throttle linkage.Aug 29, 1997 · N761HQ · Substantial damageNTSB LAX93LA194Accident · Serious injuriesLimited investigationFinal reportCessna P210N · Oakland, CAthe pilot's poor decision to continue flying the airplane with a known deficiency and the poorly performed major overhaul of the engine. The failed crankshaft due to fatigue are factors in this accident.May 1, 1993 · N731HP · DestroyedNTSB LAX88LA159Accident · Minor injuriesLimited investigationFinal reportCessna TU206G · Coarsegold, CAWhile at cruise flight, the engine surged twice then quit. During the emergency landing, the airplane collided with the terrain. Inspection of the engine revealed that the number three connecting rod broke.Apr 13, 1988 · N735SU · Substantial damage