NTSB investigations: Continental IO-360 series, 2010

8 cases on aircraft whose registry engine model is Continental IO-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 IO-360 series, 2010 per year, 1964–2026: 692 cases
19641
196511
196612
196717
196818
196916
197019
197115
197212
197312
197413
197520
197612
197717
197829
197920
198019
198113
198217
198310
198414
198512
19868
198711
198810
198910
19908
19919
19928
199313
19945
199511
19966
19979
19986
19999
20008
200112
200213
200312
20049
200517
200613
20076
200815
200912
20108
201111
20126
20139
20145
20158
20167
20176
20187
201911
20206
20213
20229
20237
20248
20258
20264

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 ('17025', '17045'))
  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 ANC10LA081Accident · No injuriesLimited investigationFinal reportStinson 108-2 · Port Alsworth, AKThe overstress fracture and failure of a main landing gear wheel during landing, resulting in the right wing striking the ground.Aug 29, 2010 · N9569K · Substantial damageNTSB CEN10LA502Accident · Serious injuriesLimited investigationFinal reportCirrus Design SR20 · Porter, TXThe pilot's delay in performing a go-around, which resulted in an impact with trees.Aug 24, 2010 · N8154M · Substantial damageNTSB CEN10CA305Accident · No injuriesData collectionFinal reportCessna 337 · Custer, SDA partial loss of engine power due to fuel starvation as a result of the pilot's inadequate fuel mismanagement.Jun 5, 2010 · N2267X · Substantial damageNTSB ERA10LA284Accident · Minor injuriesLimited investigationFinal reportCessna 337G · High Springs, FLThe pilot's failure to follow the published engine-out procedures after a total loss of power in the rear engine. Contributing to the accident was the inadequate maintenance and inspection of the engine by the pilot and maintenance personnel.May 27, 2010 · N72268 · Substantial damageNTSB CEN10CA191Accident · No injuriesData collectionFinal reportMaule M-5-210C · Bismarck, NDThe pilot’s failure compensate for the crosswinds resulting in a loss of directional control while landing.Apr 5, 2010 · N62040 · Substantial damageNTSB CEN10CA267Accident · No injuriesData collectionFinal reportCessna R172E · Alamogordo, NMAn unknown event that resulted in damage to the airplane's firewall.Mar 22, 2010 · N7871N · Substantial damageNTSB ERA10LA177Accident · No injuriesLimited investigationFinal reportCessna T337G · Shelby, NCThe pilot's improper landing flare and touchdown during landing in gusty crosswind conditions.Mar 15, 2010 · N74E · Substantial damageNTSB CEN10CA132Accident · No injuriesData collectionFinal reportCessna 172 · Davis, OKThe flight instructor’s improper recovery from a bounced landing.Feb 28, 2010 · N72TN · Substantial damage