NTSB investigations: Continental TSIO-360 series, 2002

13 cases on aircraft whose registry engine model is Continental TSIO-360 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

19642026
NTSB investigations: Continental TSIO-360 series, 2002 per year, 1964–2026: 500 cases
19641
19671
19711
19741
19752
19762
19775
197818
19799
198020
198114
198216
198318
198415
198518
19868
198711
198814
19898
19908
199110
19926
19937
19947
19958
19966
199712
19989
199912
20006
200113
200213
200316
200411
200510
200611
200714
200812
20096
20107
20119
201210
20137
201411
20157
20165
20179
20188
20193
20207
20214
20227
202311
202410
20254
20262

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\") = 2002
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17019', '17023'))
  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 LAX03FAMS1Accident · 1 fatalMissing aircraftFinal reportPiper PA-34-200T · Pacific Ocean (Pacific Ocean)undetermined, missing aircraft.Dec 15, 2002 · N101YK · DestroyedNTSB DEN03LA024Accident · No injuriesLimited investigationFinal reportMooney M20K · Eagle, COthe pilot's failure to remove protective coverings from the engine air scoops during the preflight inspection, resulting in air starvation and a loss of engine power shortly after takeoff. A contributing factor was the lack of suitable terrain for a forced…Dec 10, 2002 · N252DR · Substantial damageNTSB FTW03FA051Accident · 5 fatalField investigationFinal reportPiper PA-34-220T · McAlester, OKThe pilot's failure to maintain the airplane's minimum controllable airspeed during a single-engine go-around which resulted in his loss of control. Contributing factors to the accident included the loss of power from the left engine as a result of…Nov 27, 2002 · N699WG · DestroyedNTSB SEA03LA009Accident · No injuriesLimited investigationFinal reportPiper PA-28-201T · La Grande, ORInadequate supervision and the premature raising of flaps before a positive climb was established.Nov 14, 2002 · N2208Y · Substantial damageNTSB SEA03LA003Accident · No injuriesLimited investigationFinal reportMooney M20K · Rexburg, IDThe pilot's failure to perform a go-around once it became evident that his remedial action was not adequate to overcome the porpoise/pilot-induced oscillation that occurred during the landing flare. Factors include the pilot's inadvertent repeated…Oct 12, 2002 · N231EH · Substantial damageNTSB CHI02LA257Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Kenmare, NDThe pilot's misjudgment of distance and speed. Factors associated with the accident were the sudden wind shift which resulted in a tailwind condition and the rough terrain encountered during the overrun landing.Aug 26, 2002 · N9696C · Substantial damageNTSB CHI02CA184Accident · No injuriesData collectionFinal reportPiper PA-34 · Lowell, MIThe probable cause of this accident was a failure to properly compensate for the current wind conditions. Excessive use of brakes was a contributing factor.Jul 7, 2002 · N52WP · Substantial damageNTSB FTW02FA130Accident · 2 fatalField investigationFinal reportPiper PA-34-200T · Alpine, UTThe pilot's failure to maintain clearance with terrain and continued flight into known adverse weather conditions. Contributing factors were the fog and rain weather conditions.Apr 27, 2002 · N132CP · DestroyedNTSB CHI02IA110Incident · No injuriesIncident investigationFinal reportPiper PA-34-220T · Sturgis, MIThe flightcrew not following the landing checklist, the flightcrew not lowering the landing gear, and the flight examiner's inadequate supervision of the flight.Apr 20, 2002 · N92721 · Minor damageNTSB IAD02FA043Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Oxford, CTThe pilot's failure to follow the published instrument approach procedure. Factors were the night and low ceiling conditions.Apr 13, 2002 · N82284 · DestroyedNTSB ATL02FA069Accident · 2 fatalField investigationFinal reportPiper PA-34-200T · Apex, NCThe pilot experienced spatial disorientation that resulted in the loss of control and the overload failure of the airframe. A factor was low visibility and ceilings.Mar 31, 2002 · N2BX · DestroyedNTSB FTW02FA095Accident · 2 fatalField investigationFinal reportPiper PA-28RT-201T · Marianna, ARThe pilot's continued flight into adverse weather conditions and his failure to maintain clearance with terrain while maneuvering. Factors were, the low cloud and mist weather conditions, and the dark night light conditions.Mar 13, 2002 · N84719 · Substantial damageNTSB LAX02FA061Accident · 1 fatalField investigationFinal reportCessna T337H · Buena Park, CAthe pilot's failure to maintain control of the airplane during the landing approach. Factors included the pilot's distraction when informed that his landing gear was not down, and his impairment from the effects of prescription drugs.Jan 5, 2002 · N1348L · Destroyed