NTSB investigations: Continental O-470 series, MN

8 cases on aircraft whose registry engine model is Continental O-470 series, where the first occurrence was “Loss of control - on ground/water”. 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, MN per year, 1982–2026: 8 cases
19821
19851
19911
19952
20001
20051
20061

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.\"eventStateOrRegion\" = 'MN' AND c.\"eventCountry\" = 'USA'
    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\" = 260))
  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 CHI06LA101Accident · No injuriesLimited investigationFinal reportCessna 180G · Eveleth, MNThe pilot's failure to maintain directional control during the landing rollout, which resulted in the airplane departing the left side of the runway. Contributing to the accident was the airport fence and the drainage ditch.Mar 26, 2006 · N1250W · Substantial damageNTSB CHI05CA195Accident · No injuriesData collectionFinal reportCessna 180 · Bowstring, MNThe unsuitable water conditions for takeoff selected by the pilot and his inability to maintain aircraft control in the rough water. Contributing factors were the aborted takeoff initiated by the pilot, the rough water conditions and the high, gusty winds.Jul 17, 2005 · N4652B · Substantial damageNTSB CHI00LA190Accident · No injuriesLimited investigationFinal reportCessna 180 · Saint Cloud, MNdirectional control not being maintained by the pilot during landing rollout.Jul 9, 2000 · N4940A · Substantial damageNTSB CHI95LA169Accident · Serious injuriesLimited investigationFinal reportCessna 180 · Clear Lake, MNfailure of the pilot to maintain directional control of the airplane during the takeoff roll. The proximity of trees to the runway was a related factor.Jun 4, 1995 · N3149D · Substantial damageNTSB CHI95TA174Accident · No injuriesFinal reportCessna 180 · Orr, MNthe pilot's inadequate compensation for the crosswind weather condition. A factor was the crosswind.May 12, 1995 · N9336C · Substantial damageNTSB CHI91LA255Accident · No injuriesLimited investigationFinal reportCessna 180 · Walker, MNDirectional control after landing was not maintained by the pilot. Factors related to the accident were a gusty crosswind and a downhill embankment (ditch).Aug 6, 1991 · N1637C · Substantial damageNTSB CHI86LA059Accident · No injuriesLimited investigationFinal reportCessna 180J · Hibbing, MNThe plt landing in a direct 90 deg x-wind, lost directional control, struck a snowbank and nosed over inverted.Dec 30, 1985 · N180HS · Substantial damageNTSB CHI82DA104Accident · No injuriesFinal reportCessna 180 · Duluth, MNThe student pilot was making touch and go landings on RUNWAY09 while preparing for a flight check. After landing, he proceeded to open the cowl flaps and push in the carburetor heat control. He stated that at that time, he let the ailerons go to a neutral…Mar 29, 1982 · N4649B · Substantial damage