NTSB investigations: Continental GO-300 series, 2016

5 cases on aircraft whose registry engine model is Continental GO-300 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 GO-300 series, 2016 per year, 1964–2026: 395 cases
196427
196531
196626
196725
196812
196917
197011
197110
19728
197311
19749
197511
19768
19779
19789
19795
19809
19813
19823
19834
19846
19853
19864
19875
19886
19898
19902
19911
19923
19933
19946
19955
19963
19975
19985
19994
20001
20016
20025
200311
20043
20053
20062
20071
20083
20092
20105
20111
20123
20135
20142
20165
20171
20194
20201
20214
20223
20234
20241
20251
20261

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\") = 2016
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17024'))
  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 CEN17LA060Accident · Minor injuriesLimited investigationFinal reportCessna 175C · Millersburg, OHThe pilot's improper in-flight fuel management and his failure to switch the fuel selector to the “both” position in accordance with the Before Landing checklist, which resulted in a loss of engine power due to fuel starvation.Dec 21, 2016 · N8381T · Substantial damageNTSB CEN16FA210Accident · 1 fatalField investigationFinal reportCessna 175 · Pine Bluff, ARA loss of engine power during cruise flight for reasons that could not be determined because a test run of the engine did not reveal any mechanical malfunctions or anomalies that would have precluded normal operation. Contributing to the accident were the…Jun 8, 2016 · N6649E · Substantial damageNTSB ERA16LA157Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 175 · Wartburg, TNCatastrophic engine failure due to a fatigue fracture of the No. 6 connecting rod cap.Apr 14, 2016 · N6792E · Substantial damageNTSB GAA16CA122Accident · No injuriesData collectionFinal reportCessna 175 · Gold Beach, ORThe pilot's failure to maintain an approach angle of descent to avoid obstacles, resulting in the airplane striking the airport perimeter fence.Feb 8, 2016 · N6951E · Substantial damageNTSB GAA16CA097Accident · No injuriesData collectionFinal reportCessna 175 · Seeley Lake, MTThe pilot' failure to identify the plowed runway width in dusk and flat light conditions, which resulted in a touchdown left of the runway center, an impact with a snow berm, and a ground loop.Jan 5, 2016 · N9493B · Substantial damage