OpenAirDocs.org

Fatal NTSB investigations: Continental 0-300 series

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

19822026

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.\"highestInjuryLevel\" = 'Fatal'
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17022')
      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 SEA04LA152Accident · 1 fatalLimited investigationFinal reportPaulick Wittman W-10 · Langley, WAThe pilot's inadequate preflight preparation to assure adequate takeoff performance to clear obstacles, and his failure to maintain obstacle clearance.Aug 1, 2004 · N70P · DestroyedNTSB IAD04FA031Accident · 1 fatalField investigationFinal reportCessna 172C · Edinburgh, NYThe pilot's occluded left main coronary artery, which resulted in a massive heart attack and sudden death in flight.Jul 11, 2004 · N8358X · Substantial damageNTSB ATL02FA104Accident · 3 fatalField investigationFinal reportCessna 172C · Ball Ground, GAThe flight instructor's failure to maintain adequate obstacle clearance, which resulted in an inflight collision with trees.May 23, 2002 · N1479Y · DestroyedNTSB FTW95FA349Accident · 4 fatalField investigationFinal reportCessna 172D · Tsaile, AZThe pilot's failure to maintain terrain clearance. Factors were the pilot's lack of mountain flying experience and the rising terrain.Apr 24, 1995 · N2587Y · DestroyedNTSB LAX95LA101Accident · 1 fatalLimited investigationFinal reportCessna 172G · Pope Valley, CAthe pilot's poor judgment to buzz the lake and his inadequate visual lookout.Feb 9, 1995 · N4345L · DestroyedNTSB SEA92FA002Accident · 4 fatalField investigationFinal reportCessna 172G · Miltonfreewater, ORInadequate in-flight planning. Factors to the accident were: mountainous terrain, clearance not maintained, lack of total flight experience, and lack of familiarity with geographical area.Oct 6, 1991 · N1372F · DestroyedNTSB ATL86FA133Accident · 1 fatalField investigationFinal reportCessna 172 · Douglasville, GAThe acft was observed flying at low alt & circling several houses. The plt landed on a grass strip, then after a short time, he & his passenger took off again. The acft was again observed circling several houses at low alt in an area near the strip. A witness…May 17, 1986 · N6839A · DestroyedNTSB CHI85FEV03Accident · 1 fatalFinal reportCessna 172 · Sweetwater, ILThe acft was observed flying at low alt parallel to a hiway before colliding with a tree before impacting the ground. The plts wife said that the plt had been under extreme stress for a few months and had not been to bed for 2 days preceding the accident. She…Sep 8, 1985 · N6236E · DestroyedNTSB CHI85FA356Accident · 1 fatalField investigationFinal reportCessna 172 · Rose Township, MIJust prior to the accident, several witnesses observed the acft flying at a very low alt in the vicinity of the crash site. The crash site was located across the road from the home of the plt's brother. According to witnesses, the acfts eng was operating…Aug 19, 1985 · N5146A · DestroyedNTSB NYC84FNC09Accident · 1 fatalFinal reportCessna 172 · Pownal, MEPrior to the accident, witnesses observed the acft making several low passes & maneuvering. During the last maneuver, the acft entered a dive & collided with trees before the plt recovered. Trees were broken or damaged over an area of about 200 ft. no…Aug 25, 1984 · N5091A · DestroyedNTSB NYC83FA260Accident · 3 fatalField investigationFinal reportCessna 170B · Livermore Falls, METhe acft collided with trees during a go-around at night in a ground fog. The plt had called his wife and discussed the weather. He decided on an alternate arpt if the weather created problems. He had flown into bowman field many times at night and knew the…Oct 1, 1983 · N2429D · DestroyedNTSB ATL83FIG03Accident · 1 fatalFinal reportCessna 172F · Hancock, MDThe aircraft collided with the top two wires of a powerline during a low altitude sight-seeing flight along the potomac river. The pilot stated he was maintaining visual contact with the ground should an emergency landing become necessary. He was staying high…Jan 2, 1983 · N8515U · Substantial damageNTSB MKC82FA096Accident · 1 fatalField investigationFinal reportCessna 170B · Tama, IAThe purpose of the flight was to take a family friend on a night airplane ride to see the lights of a neighboring city. The takeoff was made from a soft wet grass runway with an aircraft exceeding the maximum allowable gross weight and the center of gravity…Jun 6, 1982 · N8187A · DestroyedNTSB SEA82FYK07Accident · 1 fatalFinal reportCessna 172 · Lapine, ORWhen the pilot landed at lakeview,OR,he checked the weather but reported to his passenger that although the weather was bad he did not want to stay in lakeview. The aircraft departed lakeview, following a highway, when the weather conditions continued to…Jan 24, 1982 · N8172B · Destroyed