NTSB investigations: Continental IO-520 series, 2000

8 cases on aircraft whose registry engine model is Continental IO-520 series, where the first occurrence was “Loss of control - on ground/water”. 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 IO-520 series, 2000 per year, 1982–2026: 213 cases
19828
198314
198414
19856
198610
19876
19888
19898
19906
19914
19928
19936
19945
19958
199613
19975
199812
199911
20008
20015
20027
200310
200411
200511
20064
20075

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\") = 2000
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17032')
      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\" = 260))
  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 CHI01LA059Accident · No injuriesLimited investigationFinal reportBeech F33A · Winona, MNThe pilot not maintaining directional control during the landing roll. A factor was the snowbank.Dec 20, 2000 · N282R · Substantial damageNTSB ANC01LA017Accident · No injuriesLimited investigationFinal reportCessna 207A · Bethel, AKThe pilot's failure to use all available runway. Factors associated with the accident were the pilot's inadequate preflight planning/preparation, a short runway, a tailwind, and a slush-covered runway.Nov 3, 2000 · N7336U · Substantial damageNTSB FTW00LA261Accident · Minor injuriesLimited investigationFinal reportCessna 185F · Burnet, TXThe pilot's failure to maintain directional control of the airplane while landing. A factor was the crosswind.Sep 16, 2000 · N34NC · Substantial damageNTSB DEN00LA140Accident · No injuriesLimited investigationFinal reportCessna A188 · Gallup, NMThe pilot's failure to compensate for the wind conditions. Factors were the pilot's selection of the wrong runway, and the tailwind/crosswind weather conditions.Jul 29, 2000 · N8188V · Substantial damageNTSB SEA00LA147Accident · No injuriesLimited investigationFinal reportCessna A185F · Tillamook, ORThe pilot's failure to maintain directional control.Jul 28, 2000 · N7485C · Substantial damageNTSB FTW00LA180Accident · No injuriesLimited investigationFinal reportCessna A185F · New Orleans, LAThe pilot's failure to maintain directional control during landing roll, which resulted in a ground loop.Jun 12, 2000 · N61441 · Substantial damageNTSB IAD00LA028Accident · No injuriesLimited investigationFinal reportBellanca B17-30A · Shenandoah, VAthe pilot's failure to maintain control during landing roll-out. A factor was the pilot's lack of total experience.Mar 24, 2000 · N146Q · Substantial damageNTSB FTW00LA110Accident · No injuriesLimited investigationFinal reportCessna A188B · Perryton, TXThe pilot's failure to maintain directional control during the takeoff roll. A factor was the crosswind.Mar 13, 2000 · N4833Q · Substantial damage