NTSB investigations: Continental E185 series

8 cases on aircraft whose registry engine model is Continental E185 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 E185 series per year, 1982–2026: 8 cases
19821
19831
19891
19901
19911
20001
20021
20051

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 c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17014')
      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 ATL05LA042Accident · 1 fatalLimited investigationFinal reportBeech 35 · Knoxville, TNThe pilot's failure to maintain adequate obstacle clearance, which resulted in the in-flight collision with trees. A factor was dark night.Jan 9, 2005 · N501B · Substantial damageNTSB SEA02FA109Accident · 2 fatalField investigationFinal reportBeech A35 · Atlanta, IDClearance from an object was not maintained during an aborted landing. Trees and mountainous terrain were factors.Jun 22, 2002 · N658B · Substantial damageNTSB CHI00FA200Accident · 1 fatalField investigationFinal reportBeech 35 · Columbus, NEthe failure of the pilot to maintain clearance from the power line. Factors were the sunglare and the wire.Jul 15, 2000 · N947V · DestroyedNTSB SEA91FA110Accident · 1 fatalField investigationFinal reportBeech 35 · Harrison, IDImproper preflight planning/preparation by the pilot. The terrain condition and the pilot's lack of total experience were related factors.May 20, 1991 · N3842N · DestroyedNTSB FTW90LA104Accident · No injuriesLimited investigationFinal reportRyan Navion A · Denison, TXPilot's attempted takeoff with conditions in excess of the airplane's performance capabilities. Contributing to the accident was the high density altitude and the uphill runway.Apr 29, 1990 · N4442K · Substantial damageNTSB SEA90FA021Accident · 2 fatalField investigationFinal reportBeech B35 · Bremerton, WAThe pilot's improper IFR procedure, his failure to maintain proper alignment on the ILS approach, and his failure to initiate a missed approached after reaching the lateral limits of the ILS system or decision height. Darkness and deteriorating weather were…Nov 23, 1989 · N8918A · DestroyedNTSB CHI84LA023Accident · No injuriesLimited investigationFinal reportBeech B35 · Northfield, OHDuring takeoff, the acft collided with trees. According to the arpt manager, the acft was rotated prematurely during the takeoff & the plt flew the acft on the back side of the power curve until tree impact. Reportedly, there was no preimpact part failure or…Oct 16, 1983 · N8719A · Substantial damageNTSB FTW82FPJ10Accident · 1 fatalFinal reportNavion A · Chickasha, OKThe aircraft departed from a private airport 2 miles south of Chickasha at 0330. At 0336 power was interrupted on electric power lines southwest of Chickasha. The wreckage was found 6 miles south and 4 and 1/2 miles west of Chickasha a few feet west of a 35…Jan 2, 1982 · N4876K · Destroyed