NTSB investigations: Continental IO-520 series, 2000

6 cases on aircraft whose registry engine model is Continental IO-520 series, where the first occurrence was “In flight collision with object”. 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: 150 cases
19828
198310
19843
19858
19867
19874
19884
19897
19905
19913
199212
19935
19944
19954
19967
19973
19984
19997
20006
20017
20024
20037
20045
20055
20066
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\" = 220))
  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 FTW01FA020Accident · 1 fatalField investigationFinal reportCessna 185F · Jena, LAThe pilot's decision to land on a highway with vehicle traffic and obstacles and his failure to maintain proper clearance from the obstacles.Nov 15, 2000 · N6232E · DestroyedNTSB FTW01LA012Accident · Serious injuriesLimited investigationFinal reportCessna 188B · Stanton, TXThe failure of the pilot to maintain clearance with the power lines, while maneuvering during an aerial application flight.Oct 19, 2000 · N53211 · DestroyedNTSB CHI00LA289Accident · No injuriesLimited investigationFinal reportCessna A188B · Nickerson, KSaltidude/clearance not obtained/maintained by the pilot. Factors to the accident were the hay bale, the inadequate preflight planning/preparation by the pilot, the high-density altitude, and the high weight of the aircraft at the time of the accident.Sep 1, 2000 · N9326R · Substantial damageNTSB ANC00LA085Accident · No injuriesLimited investigationFinal reportCessna 207 · Anaktuvuk Pass, AKThe pilot's selection of an unsuitable landing area. Factors associated with the accident were a fuel drum, and a tailwind.Jul 7, 2000 · N1658U · Substantial damageNTSB CHI00LA141Accident · No injuriesLimited investigationFinal reportCessna C310R · Hibbing, MNthe deer incursion on the landing runway.May 23, 2000 · N87430 · Substantial damageNTSB MIA00LA112Accident · No injuriesLimited investigationFinal reportCessna A188B · Lake Placid, FLThe pilots inadequate visual outlook while performing aerial application resulting in the aircraft colliding with a piece of farm equipment which was parked in the field which caused the right main landing gear to separate and damage to the right wing during…Mar 19, 2000 · N84666 · Substantial damage