NTSB investigations: Lycoming IO-320 series

12 cases on aircraft whose registry engine model is Lycoming IO-320 series, where the first occurrence was “In flight encounter with weather”. 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 IO-320 series per year, 1982–2026: 12 cases
19821
19831
19851
19861
19872
19881
20002
20031
20041
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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41509')
      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\" = 240))
  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 NYC07FA091Accident · 3 fatalField investigationFinal reportPiper PA-30 · Trappe, MDThe pilot's improper decision to fly into an area of thunderstorms, which resulted in a loss of aircraft control and subsequent in-flight breakup. Contributing to the accident was the thunderstorm.Apr 4, 2007 · N555EM · DestroyedNTSB DEN04FA074Accident · 2 fatalField investigationFinal reportPiper PA-30 · Evanston, WYthe pilot's failure to maintain terrain clearance. Contributing factors include snow, low ceiling, icing conditions, and the dark night.May 24, 2004 · N7460Y · DestroyedNTSB ATL03FA125Accident · 2 fatalField investigationFinal reportBellanca 7KCAB · Dover, TNThe pilot continued VFR flight into adverse weather conditions including instrument meteorological conditions and turbulence in thunderstorms, which resulted in a loss of control in flight and subsequent collision with terrain.Jun 14, 2003 · N68551 · Substantial damageNTSB ANC00LA070Accident · No injuriesLimited investigationFinal reportPiper PA-18-160 · Palmer, AKThe pilot's inadequate compensation for wind conditions. A factor associated in the accident was a variable wind.Jun 14, 2000 · N9963Q · Substantial damageNTSB DEN00LA041Accident · No injuriesLimited investigationFinal reportCessna 172P · Huntsville, UTThe snow shower, and the lack of suitable terrain for the precautionary landing.Jan 8, 2000 · N65710 · Substantial damageNTSB SEA88LA068Accident · Serious injuriesLimited investigationFinal reportBellanca 7KCAB · Palmer, WAWhile on a VFR cross country flight the pilot encountered instrument meteorological conditions along his route. The aircraft was not instrument equipped, even though the pilot is instrument rated. The pilot had to make two precautionary landings prior to the…Mar 28, 1988 · N86820 · DestroyedNTSB NYC87FA204Accident · 4 fatalField investigationFinal reportPiper PA-30 · Lincolnville, METhe plt was making an approach to knox county arpt, rockland me and after receiving a wx report from UNICOM that the local wx was below approach minimums he indicated that he would make a missed approach. There was no further communications from the acft. A…Jul 14, 1987 · N7617Y · DestroyedNTSB LAX87FA136Accident · 1 fatalField investigationFinal reportBellanca 7KCAB · Lebec, CAPrior to the flt, the plt rcvd 2 wx briefings & was adzd of low ceilings, restricted visibilities & mtn obscurement along the route. Also, he was adzd that VFR flt was not recommended. The surviving pax said that after entering the mtn area, they contd 'in…Mar 6, 1987 · N8713V · DestroyedNTSB BFO86FA042Accident · 3 fatalField investigationFinal reportPiper PA-30 · Bowleys Qrtrs, MDDrg arr, TRACON gave the plt the arpt wx & provided vectors for an ILS rwy 32 apch. The plt inquired about a cell that he understood was over the arpt & was advised to standby while the controller (ctlr) checked on it. The ctlr contacted twr psnl who adzd the…Aug 17, 1986 · N31AB · DestroyedNTSB MIA85FA123Accident · 2 fatalField investigationFinal reportAronson Falco F8L · Gainesville, FLThe plt received a wx briefing & filed an IFR clnc, then departed VFR. Except for a hdwnd, the 1st part of the flt was normal. In the vcnty of macon, GA, the plt requested & received an IFR clnc. Later, he elected to divert to the gaines- ville rgnl arpt &…Mar 17, 1985 · N545SF · DestroyedNTSB NYC83FA049Accident · 2 fatalField investigationFinal reportPiper PA-30 · Atlantic City, NJThe plt had landed at Atlantic City, NJ at aprx 1545 while en route to oxford, CT. Before taking off, he contacted two fss's and both advised that VFR flt was not recommended. The non-instrument rated plt took off at aprx 1920 local time with no flt plan. At…Jan 6, 1983 · N7619Y · DestroyedNTSB CHI82DA078Accident · No injuriesFinal reportPiper PA-30 · Valparaiso, INThe pilot reported encountering severe icing conditions after he had canceled his IFR flight plan and had the airport in sight. At that point, he felt that the safest alternative was to continue the approach. The approach was flown at 120 mph with no flaps.…Mar 5, 1982 · N34EE · Substantial damage