NTSB investigations: Lycoming 0-320 series, 1992

15 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, 1992 per year, 1982–2026: 240 cases
198215
198322
198419
198512
19865
19876
198810
198911
199014
199110
199215
199312
19949
19957
19963
19978
19984
19998
20008
20014
20029
20039
20047
20056
20065
20072

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 year(c.\"eventDate\") = 1992
    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 FTW93LA060Accident · No injuriesLimited investigationFinal reportCessna 172P · Little Rock, ARThe certified flight instructor's failure to attain the proper touchdown point.Dec 28, 1992 · N64943 · Substantial damageNTSB NYC93LA051Accident · No injuriesLimited investigationFinal reportCessna 172 · Andover, NJThe pilot's failure to abort the landing which resulted in a overrun of the runway. Contributing was the pilot's misjudgement of distance and an improper touchdown point.Dec 22, 1992 · N54102 · 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 CHI93LA003Accident · No injuriesLimited investigationFinal reportCessna 172P · Kokomo, INThe pilot's delayed remedial action.Oct 3, 1992 · N51829 · Substantial damageNTSB ANC92LA177Accident · No injuriesLimited investigationFinal reportPiper PA-18-150 · North Pole, AKPilot's decision to attempt takeoff without removing snow from aircraft surfaces. Factor related to the accident was the snow contaminated wing and other flight surfaces.Sep 13, 1992 · N3692Z · Substantial damageNTSB FTW92LA195Accident · No injuriesLimited investigationFinal reportBeech 19A · Mounds, OKThe student pilot's failure to execute a go around when he realized he was going to land long.Jul 30, 1992 · N7642R · Substantial damageNTSB MIA92LA157Accident · No injuriesLimited investigationFinal reportCessna 172P · Valkaria, FLExcessive airspeed on final approach by the pilot in command resulting in failure to attain the proper touchdown point and running off the runway colliding with a tree.Jul 29, 1992 · N89900 · Substantial damageNTSB SEA92LA166Accident · No injuriesLimited investigationFinal reportPiper PA-28-160 · Sisters, ORThe improper use of flight controls by the PIC during an aborted takeoff. Factors relating to the accident were the unfavorable wind (windshift) encountered during takeoff ground roll, the tailwind and high da weather conditions.Jul 27, 1992 · N5639W · Substantial damageNTSB CHI92LA174Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-140 · Rockford, ILThe flight instructor's premature liftoff. Related factors are the instructor's lack of total experience in the accident make and model airplane, and the unsuitable terrain encountered during the roll-out.Jun 14, 1992 · N56311 · Substantial damageNTSB FTW92LA151Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Truth Or Cons, NMThe pilot's inability to stop due to worn brakes and low brake fluid.Jun 5, 1992 · N4547A · Substantial damageNTSB BFO92LA066Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Caldwell, NJThe pilot's improper IFR operation. Contributing was the pilot's lack of recent instrument flight time.May 16, 1992 · N54860 · DestroyedNTSB BFO92LA053Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Amelia, VAThe pilot's misjudgement of distance and altitude that resulted in an landing overrun and collision with an embankment. Contributing was failure to initiate a go around and inadequate supervision.May 1, 1992 · N20209 · DestroyedNTSB NYC92LA084Accident · No injuriesLimited investigationFinal reportCessna 172N · New Madison, OHThe pilot's failure to attain a proper touchdown point. Contributing to the accident was the pilot inadequately planned his approach and his failure to perform a go-around.Apr 23, 1992 · N733XP · Substantial damageNTSB CHI92LA121Accident · No injuriesLimited investigationFinal reportCessna 172M · Osage Beach, MOThe pilot-in-command's failure to use all th eavailable runway and his misjudgment of the proper touchdown point during landing.Apr 4, 1992 · N9568V · Substantial damageNTSB ATL92LA037Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Griffin, GAThe excessive speed used by the pilot to land on the short private airstrip. A factor was unfavorable wind.Jan 12, 1992 · N6101D · Substantial damage