NTSB investigations: Lycoming 0-320 series, PA

13 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the first occurrence was “Overrun”. 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: Lycoming 0-320 series, PA per year, 1982–2026: 13 cases
19821
19841
19851
19881
19892
19901
19921
19931
19951
19971
19981
20021

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\" = 'PA' 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 ('41508')
      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\" = 340))
  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 NYC03LA034Accident · No injuriesLimited investigationFinal reportSocata TB 9 · Mount Union, PAThe pilot's delay in aborting the takeoff. A factor was the soft runway.Dec 31, 2002 · N136ER · Substantial damageNTSB IAD98LA020Accident · No injuriesLimited investigationFinal reportCessna 172M · Blue Bell, PAThe pilot's failure to attain the proper touchdown point, and his failure to make a go-around, while there was sufficient runway remaining.Jan 4, 1998 · N5135R · Substantial damageNTSB NYC97LA075Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Butler, PAthe pilot's misjudgment of distance and speed on final approach; his failure to attain the proper touchdown point; and his failure to perform a go-around, while there was still sufficient airspeed and runway remaining, which resulted in an overrun and…Apr 15, 1997 · N21123 · Substantial damageNTSB NYC95LA227Accident · No injuriesLimited investigationFinal reportCessna 172RG · Pittsburgh, PAthe pilot's failure to obtain the proper touchdown point and excessive airspeed which resulted in an overrun and a subsequent collision with a trailer off the departure end of the runway.Sep 29, 1995 · N9497B · Substantial damageNTSB NYC93LA179Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · West Mifflin, PAThe pilot's misjudgement of speed and distance, which resulted in a landing overrun of the runway. Factors were an embankment and the pilot not being able to abort the landing.Aug 29, 1993 · N2572U · Substantial damageNTSB NYC93LA034Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Woodstown, PAThe pilot's improperly planned approach and delayed decision to initiate a go-around, which resulted in a touchdown too FAR down the runway and the subsequent collision with a ditch. A factor related to the accident was the pilot's lack of recent flight…Nov 1, 1992 · N33146 · Substantial damageNTSB NYC90LA184Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Tunkhannock, PAThe pilot did not obtain the proper touchdown point which resulted in an overrun. The factors were altitude, wet runway, and go around not performed.Aug 4, 1990 · N7265F · Substantial damageNTSB NYC89LA124Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Dushore, PACollision with trees during a rejected takeoff from a private turf strip due to the pilots failure to take advantage of the existing wind.Apr 23, 1989 · N2127J · DestroyedNTSB NYC89LA117Accident · No injuriesLimited investigationFinal reportCessna 172M · Palmyra, PAThe pilot misjudged the airspeed and distance during the landing.Apr 14, 1989 · N9946Q · Substantial damageNTSB NYC88LA223Accident · No injuriesLimited investigationFinal reportCessna 172P · Freeport, PAThe plt said that he had landed on the 2268 ft long, sod strip on several previous occasions. He said there was a right crosswind at about 6 KTS. The acft was too high and go-arounds were made following the first two approaches. On the third approach, the…Aug 21, 1988 · N172RQ · Substantial damageNTSB NYC85LA212Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Doylestown, PAAccording to the plt, on touchdown the acft braking was ineffective due to morning dew on the grass rwy. The acft slid off the end of the rwy and collided with bushes.Aug 6, 1985 · N2960B · Substantial damageNTSB NYC84LA215Accident · No injuriesLimited investigationFinal reportCessna C172 · Patton, PAThe plt landed fast and long and before running off the end of the 1750 ft rwy he turned right toward the ramp. A gust of wind caught the acft and the acft collided with a ditch beside the ramp.Jun 14, 1984 · N738CN · Substantial damageNTSB NYC82DA154Accident · No injuriesFinal reportCessna 172M · Savage, PAAfter a cross country flight, the aircraft approached a 1900 foot landing strip for landing. After a fly-over to check the area, an approach to land ended in a go-around. On the second approach, the pilot was high and fast. He slipped the aircraft to lose…Jul 9, 1982 · N13119 · Substantial damage