NTSB investigations: Lycoming 0-320 series, VA

13 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

19822026
NTSB investigations: Lycoming 0-320 series, VA per year, 1982–2026: 13 cases
19821
19843
19891
19942
20001
20021
20031
20052
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\" = 'VA' 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 MIA08LA004Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-160 · Hillsville, VAThe pilot's failure to maintain control of the airplane during a go-around.Oct 10, 2007 · N5235W · Substantial damageNTSB NYC06FA029Accident · 2 fatalField investigationFinal reportPiper PA-28-161 · Leesburg, VAThe flight instructor's failure to maintain airspeed, which resulted in an inadvertent stall and subsequent impact with trees and terrain.Nov 9, 2005 · N4171T · Substantial damageNTSB NYC05CA107Accident · No injuriesData collectionFinal reportCessna 172L · Tangier, VAThe pilot's failure to maintain directional control during landing.Jun 26, 2005 · N19681 · Substantial damageNTSB IAD03FA056Accident · 2 fatalField investigationFinal reportRobinson R-22 Beta · Montpelier, VAThe pilot's failure to maintain adequate main rotor rpm while maneuvering at a low altitude.Jun 3, 2003 · N23428 · Substantial damageNTSB NYC02FA098Accident · 3 fatalField investigationFinal reportBeech 23 · King George, VAThe pilot's improper in-flight decision to perform low passes; and his failure to maintain airspeed which resulted in a stall and collision with trees.May 19, 2002 · N2351Z · Substantial damageNTSB IAD00LA043Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Tappahannock, VAthe pilots's inability to maintain aircraft control after a loss of consciosness.May 16, 2000 · N1655E · Substantial damageNTSB NYC94LA115Accident · No injuriesLimited investigationFinal reportCessna 172P · Leesburg, VAThe student pilot's failure to attain adequate airpseed during an aborted landing which resulted in an inadvertent stall and collision with the ground. A factor is the the student pilot's inexperience.Jul 8, 1994 · N63021 · DestroyedNTSB NYC94LA107Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Newport News, VAThe pilot's (1) improper recovery from a bounced landing and (2) failure to maintain aircraft control.Jul 2, 1994 · N97000 · Substantial damageNTSB BFO89LA071Accident · No injuriesLimited investigationFinal reportRobinson R22 · Manassas, VAImproper use of the cyclic control by the student pilot and his failure to relinquish control of the helicopter to the instructor (CFI). A contributing factor was the student's lack of experience.Aug 17, 1989 · N8557H · Substantial damageNTSB BFO85FA009Accident · Serious injuriesField investigationFinal reportGrumman AA-5A · Manassas, VAAfter a higher and faster apch than usual due to conflicting traffic, the acft touched down on the nosewheel and began to porpoise, according to witnesses. After the second bounce, power was added for a go around, the pilot later stated. Witnesses saw the…Dec 17, 1984 · N14LC · DestroyedNTSB BFO84FA008Accident · Serious injuriesField investigationFinal reportPiper PA-28-140 · Bayse, VAAccording to witnesses, the acft became airborne after rolling only about 1500 ft. it was described a being 'behind the power curve' for a considerable distance before climbing abruptly. The acft then banked steeply to the left & collided with a ridge at aprx…Sep 23, 1984 · N75122 · DestroyedNTSB ATL84LA138Accident · No injuriesLimited investigationFinal reportRobinson R22A · Woodbridge, VAThe CFI stated that while hovering with a prospective student pilot using the cyclic control, the student pushed rapidlyforward on the cyclic control. The instructor pilot (CFI) attempted to regain control but the acft struck a tree and crashed.Apr 3, 1984 · N8415X · Substantial damageNTSB ATL83FA186Accident · 1 fatalField investigationFinal reportPiper PA-18 · Ft. Pickett, VAThe acft collided with the ground at ft Pickett shortly after a similiar acft was seen trying to approach blackstone army airfield. This acft made a go-around and disappeared to the south. The wrecked acft was found 3.5 miles south of the arpt 8 months later.…Aug 21, 1982 · N90910 · Destroyed