NTSB investigations: Lycoming 0-320 series, MD

16 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the first occurrence was “Loss of control - in flight”. 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

19832026
NTSB investigations: Lycoming 0-320 series, MD per year, 1983–2026: 16 cases
19831
19851
19882
19891
19911
19921
19951
19961
19982
20001
20011
20021
20051
20071

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\" = 'MD' 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\" = 250))
  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 NYC08LA049Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Gaithersburg, MDThe student pilot's failure to maintain aircraft control during an attempted touch-and-go. Contributing to the accident was the instructor's delay in taking remedial action, and the presence of trees in proximity to the side of the runway.Dec 1, 2007 · N259ER · Substantial damageNTSB NYC05CA146Accident · No injuriesData collectionFinal reportCessna 172P · Mitchellville, MDThe pilot's failure to maintain directional control during landing.Sep 23, 2005 · N99137 · Substantial damageNTSB IAD02FA037Accident · 4 fatalField investigationFinal reportCessna 172P · Ocean City, MDThe pilot's spatial disorientation, which resulted in his subsequent loss of control of the airplane. A factor was the dark night, over water visual conditions.Mar 16, 2002 · N96811 · DestroyedNTSB NYC01LA163Accident · No injuriesLimited investigationFinal reportCessna 172P · Stevensville, MDThe pilot's improper flare and his improper recovery from a bounced landing.Jul 2, 2001 · N54576 · Substantial damageNTSB NYC01LA038Accident · No injuriesLimited investigationFinal reportCessna 172K · Hagerstown, MDThe pilot's failure to remove the gust lock from the control column before takeoff, and his failure to abort the takeoff.Nov 17, 2000 · N79054 · Substantial damageNTSB NYC98LA141Accident · Minor injuriesLimited investigationFinal reportChampion 7GCG · Neavitt, MDThe pilot's failure to maintain control of the airplane.Jul 4, 1998 · N9985Y · Substantial damageNTSB IAD98FA070Accident · 1 fatalField investigationFinal reportCessna 172N · Ocean City, MDThe pilot's failure to maintain control of the aircraft due to spatial disorientation. Contributing factors wer fog, dark night conditions, lack of recent experience, inadequate preflight planning, and flight into known adverse weather.Jun 22, 1998 · N5944E · DestroyedNTSB IAD96LA118Accident · No injuriesLimited investigationFinal reportCessna 172 · Frederick, MDthe private pilot's inadvertently stalling the airplane immediately after takeoff. A related factor was the pilot's improper procedures during lift-off.Jul 14, 1996 · N78149 · Substantial damageNTSB BFO95FA045Accident · 3 fatalField investigationFinal reportCessna 172M · Eldersburg, MDThe pilot's failure to maintain proper airspeed. Factors in the accident were the pilot's failure to remove carburetor heat during the go-around and the presence of a tailwind.Apr 7, 1995 · N20819 · DestroyedNTSB BFO92FA044Accident · 2 fatalField investigationFinal reportCessna 172P · Accokeek, MDThe pilot experienced spatial disorientation which resulted in loss of control of the airplane.Mar 19, 1992 · N65737 · DestroyedNTSB BFO91LA070Accident · Serious injuriesLimited investigationFinal reportGrumman AA5 · Oakland, MDThe pilot's failure to maintain adequate airspeed which resulted in an inadvertent stall.Jul 20, 1991 · N9599L · DestroyedNTSB BFO90FA003Accident · 2 fatalField investigationFinal reportCessna 177 · Mchenry, MDThe pilot's failure to obtain adequate takeoff airspeed as a result of an improper flap setting. Contributing factors were a takeoff with a tailwind, an upsloping runway, and high density altitude.Oct 29, 1989 · N30036 · DestroyedNTSB BFO89LA006Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Cambridge, MDThe stu plt did three takeoffs & lndgs with the instr aboard and then three more during solo flight. On his fourth takeoff try he used aileron and rudder to maintain directional control on the rwy. There was an 8 to 10 kt crosswind. The stu said when the acft…Oct 29, 1988 · N63019 · Substantial damageNTSB BFO88LA053Accident · No injuriesLimited investigationFinal reportCessna 172P · Gaithersburg, MDAccording to the plt, after touchdown the acft encountered a crosswind gust. The acft drifted left of the rwy where it collided with trees. The plt reported no mechanical malfunction.Jun 6, 1988 · N65720 · Substantial damageNTSB BFO86FA011Accident · Serious injuriesField investigationFinal reportPiper PA-28-140 · Westminster, MDThe student pilot was flying in a flight of three returning from having lunch at a nearby airport. The first pilot made a go-around after bouncing during touchdown on the downhill 1830 foot long by 30 foot wide airstrip. He then came aroundand made a…Dec 29, 1985 · N41204 · DestroyedNTSB ATL83FIG07Accident · 1 fatalFinal reportBellanca 8GCBC · Berlin, MDThe acft crashed into trees after the acfts landing gear became entangled in the banners tow bridle during an attempted banner pick-up. According to one witness who was a member of the banner crew on the field, the acft came in too low and caught the left…Sep 10, 1983 · N90916 · Destroyed