NTSB investigations: Lycoming 0-320 series, AZ

8 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the first occurrence was “Loss of engine power”. 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, AZ per year, 1982–2026: 8 cases
19821
19921
19941
19961
20001
20022
20041

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\" = 'AZ' 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\" = 350))
  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 LAX04LA109Accident · No injuriesLimited investigationFinal reportPiper PA 22-160 · Carefree, AZThe pilot's inadequate fuel management by his failure to switch the fuel tank selector position, which resulted in fuel starvation, a loss of engine power.Jan 17, 2004 · N8718D · Substantial damageNTSB LAX03LA015Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Queen Creek, AZa loss of engine power for undetermined reasons.Oct 21, 2002 · N4332W · Substantial damageNTSB LAX02FA191Accident · 3 fatalField investigationFinal reportPiper PA-23-160 · Rio Rico, AZa loss of engine power in the left engine for undetermined reasons, and the failure of the flying pilot to maintain an adequate single engine minimum control airspeed and aircraft control. Also causal was the decision of all three of the pilots to continue…Jun 8, 2002 · N4302P · DestroyedNTSB LAX00LA143Accident · No injuriesLimited investigationFinal reportMuxlow Pitts S-1C · Phoenix, AZA loss of engine power for undetermined reasons. Factors were the lack of suitable terrain for a forced landing and the rough/uneven terrain on which the airplane landed.Apr 5, 2000 · N27DM · Substantial damageNTSB LAX97LA040Accident · Serious injuriesLimited investigationFinal reportMoody RV-6 · Cottonwood, AZloss of engine power for undetermined reason(s).Nov 14, 1996 · N12033 · Substantial damageNTSB FTW94LA173Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Page, AZThe total loss of engine power for undetermined reason. A factor was the lack of suitable terrain at the pilot's disposal.May 23, 1994 · N1422E · Substantial damageNTSB LAX93LA074Accident · Minor injuriesLimited investigationFinal reportPiper PA-22-20 · Florence, AZThe pilot's poorly planned approach; his failure to attain the proper touch down point; and, delay in executing a go-around. Contributing to this accident was the partial loss of power for undetermined reasons.Dec 23, 1992 · N9436D · Substantial damageNTSB LAX82DA095Accident · No injuriesFinal reportCessna 172N · Mammoth, AZThe pilot was on a solo cross-country flight in preparation for his commercial pilot certificate. He had begun a descent from 10,500 ft for landing at his destination airport when the engine quit. Attempts to restart the engine were unsuccessful and a forced…Mar 7, 1982 · N734GH · Substantial damage