NTSB investigations: Lycoming IO-320 series, 2026

6 cases on aircraft whose registry engine model is Lycoming IO-320 series. 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

19642026
NTSB investigations: Lycoming IO-320 series, 2026 per year, 1964–2026: 889 cases
196417
196521
196634
196735
196825
196920
197033
197128
197234
197332
197427
197521
197620
197719
197836
197919
198022
198117
198217
198313
198418
198512
198615
198718
198810
198911
19909
19919
19925
19935
19943
19955
199610
19975
19986
19999
200011
200111
200213
200313
200410
20058
200612
200715
200810
200913
201010
201113
20127
201310
201410
20157
20164
20178
20186
20193
202010
20219
202210
20239
20245
20256
20266

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\") = 2026
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41509'))
  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 WPR27LA016Accident · No injuriesClass 4 · LimitedInvestigation openPiper PA-30 · Reno, NVOct 12, 2026 · N7571Y · Substantial damageNTSB CEN26LA248Accident · Serious injuriesClass 3 · LimitedPreliminary reportPiper PA-30 · Tulsa, OKOn July 9, 2026, about 1729 central daylight time, a Piper PA-30 airplane, N8154Y, was substantially damaged when it was involved in an accident near Tulsa, Oklahoma. The flight instructor and pilot under instruction were seriously injured. The airplane was…Jul 9, 2026 · N8154Y · Substantial damageNTSB CEN26LA225Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-30 · Meridian, MSThe total loss of power to both engines due to fuel exhaustion. Contributing to the accident was the pilot’s failure to verify the airplane’s fuel quantity before departure.Jun 15, 2026 · N8143Y · Substantial damageNTSB ERA26LA190Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-30 · Enterprise, ALThe pilot’s inadequate preflight and inflight fuel planning, which resulted in a total loss of engine power due to fuel starvation and subsequent forced landing into trees.Apr 26, 2026 · N8432Y · Substantial damageNTSB WPR26LA163Accident · Minor injuriesClass 3 · LimitedPreliminary reportPiper PA30 · Auburn, WAOn April 18, 2026, about 1330 Pacific daylight time, a Piper PA-30 Twin Comanche, N741TJ, was substantially damaged when it was involved in an accident near Auburn, Washington. The pilot and pilot-rated passenger sustained minor injuries. The airplane was…Apr 18, 2026 · N741TJ · Substantial damageNTSB WPR26LA107Accident · No injuriesClass 3 · LimitedPreliminary reportPiper PA-30 · Big Bear, CAOn February 23, 2026, at 1800 Pacific standard time, a Piper PA-30, N811LE, was substantially damaged when it was involved in an accident near Big Bear, California. The pilot and passenger were not injured. The airplane was operated as a 14 Code of Federal…Feb 24, 2026 · N811LE · Substantial damage