OpenAirDocs.org

NTSB investigations: Continental GO-300 series

7 cases on aircraft whose registry engine model is Continental GO-300 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

19862026

Where

Open the map

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 ('17024')
      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 ANC07CA052Accident · No injuriesData collectionFinal reportCessna 175 · Stoney River, AKThe pilot's failure to maintain altitude/clearance during takeoff-initial climb, which resulted in the airplane colliding with a tree, and an uncontrolled descent.Jun 23, 2007 · N7624M · Substantial damageNTSB CHI03LA197Accident · No injuriesLimited investigationFinal reportCessna 175 · Wessington Spri, SDThe pilot not obtaining/maintaining clearance from the barbed wire fence during the go-around. Factors to the accident were the fence, and the brush.Jul 4, 2003 · N7256M · DestroyedNTSB CHI01LA200Accident · No injuriesLimited investigationFinal reportCessna 175 · Tomahawk, WIThe inadequate preflight preparation that did not include calculating the density altitude and the pilot not maintaining clearance from the second row of trees on initial climb. Factors include those trees and the high density altitude present at the time of…Jul 8, 2001 · N103DL · Substantial damageNTSB FTW98FA287Accident · 1 fatalField investigationFinal reportCessna 175 · Clovis, NMThe pilot's failure to maintain adequate obstacle clearance and the proper landing glide path. Also causal was his loss of aircraft control during an attempted go-around. Factors were the dark night light conditions, the pilot's recent lack of sleep, and the…Jun 28, 1998 · N7366M · DestroyedNTSB LAX94LA082Accident · 2 fatalLimited investigationFinal reportCessna 175 · Peoria, AZthe pilot's failure to attain sufficient altitude following takeoff. A factor in the accident was the pilot's failure to use all available runway for takeoff.Dec 26, 1993 · N6623E · DestroyedNTSB FTW88FA005Accident · Serious injuriesField investigationFinal reportCessna 175 · Crystal City, TXThe plt was attempting a night visual apch to his unlighted pvt strip when the acft struck trees, flew under a pwr line,struck additional trees & subsequently impacted the gnd. The acdnt occurred aprx 2.5 miles short of the threshold. Samples of the plt's…Oct 13, 1987 · N6512E · DestroyedNTSB MKC86LA104Accident · No injuriesLimited investigationFinal reportCessna 175 · Louisburg, KSDuring a fly-by over a pvt airstrip owned by the plt, the acft contacted power lines bordering the south end of the airstrip which the plt stated he forgot about. The plt reported he failed to pull up during the over fly and flew under the power lines. The…May 11, 1986 · N7027M · Substantial damage