NTSB investigations: Continental TSIO-520 series, 2004

7 cases on aircraft whose registry engine model is Continental TSIO-520 series, where the first occurrence was “In flight encounter with weather”. 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

19822026
NTSB investigations: Continental TSIO-520 series, 2004 per year, 1982–2026: 78 cases
19827
19838
19846
19853
19866
19872
19884
19891
19901
19912
19921
19941
19962
19971
19983
20011
20022
20034
20047
20054
20066
20076

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\") = 2004
    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\" = 240))
  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 LAX05FA045Accident · 1 fatalField investigationFinal reportCessna T310R · Flagstaff, AZThe pilot's decision to attempt flight into known adverse weather conditions beyond the capability of the airplane and his failure to ensure that the airplane's wings were free of ice and/or snow contamination that accumulated while the airplane was on the…Dec 8, 2004 · N592DM · DestroyedNTSB CHI05FA016Accident · 2 fatalField investigationFinal reportCessna P210N · Wautoma, WIThe pilot not maintaining airplane control during cruise flight in instrument meteorological conditions after reporting a loss of gyros leading to his exceeding the design load limits of the wings. Factors were the clouds, the deteriorated vacuum manifold…Oct 26, 2004 · N5485W · DestroyedNTSB ATL04FA159Accident · 4 fatalField investigationFinal reportBeech 36TC · Sylvester, GAThe pilot's inadequate in-flight planning/decision resulting in flight into thunderstorms resulting in an in-flight breakup of the airframe.Jul 18, 2004 · N1525M · DestroyedNTSB NYC04FA144Accident · 1 fatalField investigationFinal reportCessna P210N · Dunkirk, NYThe pilot's loss of aircraft control and the subsequent overstress and separation of the wing during an encounter with convection induced turbulence.Jun 22, 2004 · N99HW · DestroyedNTSB ATL04FA077Accident · 2 fatalField investigationFinal reportPiper PA-46-310P · Arlington, ALThe pilots inadequate in-flight planning/decision and his failure to maintain aircraft control, resulting in an in-flight encounter with a thunderstorm and exceeding the design limits of the aircraft.Feb 23, 2004 · N9103Z · DestroyedNTSB LAX04FA113Accident · 3 fatalField investigationFinal reportCessna 414A · Laupahoehoe, HIthe pilot's disregard for an in-flight weather advisory, his likely encounter with marginal VFR or IMC weather conditions, his decision to continue flight into those conditions, and failure to maintain an adequate terrain clearance altitude resulting in an…Jan 31, 2004 · N5637C · DestroyedNTSB NYC04LA067Accident · No injuriesLimited investigationFinal reportCessna 421 · Ravenna, OHThe pilot's failure to maintain airspeed, which resulted in an inadvertent stall and subsequent hard landing. A factor in the accident was degraded aircraft performance due to the airframe ice accumulation.Jan 14, 2004 · N300FB · Substantial damage