NTSB investigations: Continental C145 series, 2010

10 cases on aircraft whose registry engine model is Continental C145 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 C145 series, 2010 per year, 1964–2026: 1,190 cases
196468
196553
196652
196754
196845
196941
197021
197135
197230
197334
197426
197544
197629
197729
197833
197927
198018
198123
198213
198322
198415
198517
198615
198721
198816
198912
199021
199117
199211
199310
19948
19959
199616
199718
199816
19998
20007
20018
200211
200311
200410
20057
20069
200710
20088
200915
201010
201111
20128
201316
201411
201511
20169
201714
20188
20198
202015
20217
20226
20237
202412
20258
20266

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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17012'))
  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 ANC11CA002Accident · No injuriesData collectionFinal reportCessna 170B · Minto Flats, AKThe pilot's selection of unsuitable terrain for takeoff, resulting in a loss of control.Oct 3, 2010 · N2792C · Substantial damageNTSB WPR10CA394Accident · Minor injuriesData collectionFinal reportCessna 170 · Salt Lake City, UTThe pilot’s failure to maintain aircraft control during the landing roll.Aug 9, 2010 · N179MM · Substantial damageNTSB WPR10CA350Accident · No injuriesData collectionFinal reportCessna 170 · Truckee, CAThe pilot’s failure to maintain directional control during an aborted landing, resulting in a collision with obstacles.Jul 14, 2010 · N3967V · Substantial damageNTSB WPR10LA312Accident · Minor injuriesLimited investigationFinal reportCessna 170B · Parker, AZThe pilot's failure to maintain directional control while landing with a crosswind.Jun 23, 2010 · N432PB · Substantial damageNTSB ERA10CA310Accident · Serious injuriesData collectionFinal reportCessna 170 · Campbellsville, KYThe pilot’s failure to maintain directional control during an aborted landing.Jun 13, 2010 · N4273V · Substantial damageNTSB ANC10CA052Accident · No injuriesData collectionFinal reportCessna 170B · Palmer, AKThe pilot's failure to maintain directional control while landing in variable wind conditions.Jun 12, 2010 · N2886C · Substantial damageNTSB WPR10CA243Accident · No injuriesData collectionFinal reportCessna 170B · Moab, UTThe pilot's failure to maintain directional control during the landing roll.May 15, 2010 · N8379A · Substantial damageNTSB WPR10LA221Accident · No injuriesLimited investigationFinal reportCessna 170A · Minden, NVA main landing gear collapse during the landing roll due to fatigue cracking and corrosion of the strut.Apr 30, 2010 · N5765C · Substantial damageNTSB WPR10LA194Accident · No injuriesLimited investigationFinal reportCessna 170B · Columbia, CAThe pilot's failure to maintain directional control during landing roll.Apr 7, 2010 · N2629D · Substantial damageNTSB WPR10CA177Accident · No injuriesData collectionFinal reportCessna 170 · Kingman, AZThe pilot’s failure to maintain directional control during landing rollout. Contributing to the accident was flight control interference by the passenger.Mar 24, 2010 · N4200V · Substantial damage