NTSB investigations: Continental O-470 series, 2002

6 cases on aircraft whose registry engine model is Continental O-470 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 O-470 series, 2002 per year, 1982–2026: 97 cases
19825
19833
19843
19853
19866
19871
19882
19892
19903
19912
19925
19931
19943
19955
19961
19986
19994
20016
20026
20039
20047
20051
20066
20077

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\") = 2002
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17026')
      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 ATL03FA017Accident · 1 fatalField investigationFinal reportCessna 182Q · Cornelia, GAThe pilot's failure to follow IFR approach procedures and continue below the minimum descent altitude, which resulted in an inflight collision with trees, and the ground. A factor was the pilot's impairment from a prescription drug.Nov 20, 2002 · N58GH · Substantial damageNTSB ANC03LA013Accident · No injuriesLimited investigationFinal reportCessna 180 · Larson Bay, AKThe pilot's failure to maintain adequate clearance while landing, which resulted in an in-flight collision with a tree.Oct 29, 2002 · N5355D · Substantial damageNTSB MIA02CA174Accident · Minor injuriesData collectionFinal reportCessna 188B · Pikesville, NCThe inability of the pilot to see the .250 inch diameter unmarked cable resulting in the in-flight collision with the cable and substantial damage to the airplane.Sep 25, 2002 · N21689 · Substantial damageNTSB ANC02LA118Accident · No injuriesLimited investigationFinal reportCessna 180 · Port Heiden, AKThe pilot's inadequate compensation for wind conditions during initial climb, which resulted in an in-flight collision with trees. A factor associated with the accident was a variable wind.Sep 8, 2002 · N4563B · Substantial damageNTSB SEA02FA145Accident · 2 fatalField investigationFinal reportCessna 182A · Emmett, IDThe pilot's failure to maintain clearance from power transmission lines while maneuvering.Aug 5, 2002 · N4085D · Substantial damageNTSB CHI02LA146Accident · No injuriesLimited investigationFinal reportCessna 182J · Galesville, WIThe pilot failed to maintain clearance with the wires while on final approach. Factors associated with the accident were the low altitude, the downdraft, and the wires which the airplane contacted.May 31, 2002 · N3027F · Substantial damage