NTSB investigations: Continental 0-200 series, 1990

8 cases on aircraft whose registry engine model is Continental 0-200 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 0-200 series, 1990 per year, 1982–2026: 136 cases
19827
198310
19848
19858
19863
19874
19887
19896
19908
19913
19926
19935
19945
19953
19964
19972
19984
19998
20005
20016
20024
20034
20044
20054
20063
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\") = 1990
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17020')
      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 FTW91LA021Accident · Serious injuriesLimited investigationFinal reportCessna 150E · Amarillo, TXAn underpowered takeoff attempt due to incorrectly set magnetos. Contributing was the transmission lines.Dec 7, 1990 · N3956U · DestroyedNTSB SEA90FA182Accident · 1 fatalField investigationFinal reportCessna 150M · Prospect, ORThe pilot's failure to maintain a proper altitude during his approach. The dark night condition was a contributing factor.Sep 14, 1990 · N3420V · DestroyedNTSB MIA90LA179Accident · Minor injuriesLimited investigationFinal reportCessna 150J · Geneva, FLThe pilots failure to retract the flaps to the takeoff setting during a touch-and-go landing.Sep 6, 1990 · N61133 · Substantial damageNTSB CHI90LA179Accident · No injuriesLimited investigationFinal reportCessna 150 · Columbia, MOInadequate visual outlook by the PIC.Jul 20, 1990 · N16088 · Substantial damageNTSB LAX90LA192Accident · No injuriesLimited investigationFinal reportCessna 150F · Franklin, CAThe fixed base operator mechanic used improper bolt/nut during repair of the elevator system.May 20, 1990 · N27G · Substantial damageNTSB ATL90FA109Accident · 1 fatalField investigationFinal reportCessna 150L · Stockbridge, GAThe pilot's failure to maintain the proper clearance from objects on the ground.May 5, 1990 · N10790 · DestroyedNTSB MKC90LA052Accident · No injuriesLimited investigationFinal reportCessna 150 · Clear Lake, MNFailure of the pilot to maintain proper alignment with the runway, his delay in initiating a go-around, and his premature raising of the flaps. Factors related to the accident were the adverse wind conditions and the tree.Feb 9, 1990 · N7359G · Substantial damageNTSB NYC90LA070Accident · Serious injuriesLimited investigationFinal reportCessna 150 · Duanesburg, NYThe failure of the flight instructor to adequately monitor the actions of the student pilot and apply corrective action in a timely manner.Feb 8, 1990 · N4768X · Substantial damage