NTSB investigations: Lycoming 0-320 series, 2005, AZ

9 cases on aircraft whose registry engine model is Lycoming 0-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 0-320 series, 2005, AZ per year, 1964–2026: 383 cases
19647
19656
19666
19675
19687
19693
19707
197111
19723
19736
19744
19757
19769
19775
197814
19799
19809
198110
198214
19832
19842
19857
19867
19872
19882
19899
19906
19918
19924
19933
19946
19955
19964
199710
19988
19995
20006
20017
200213
20036
20046
20059
200611
200710
20087
20096
20104
20113
201210
20135
20147
20151
20161
20173
20184
20194
20204
20216
20225
20234
20244
20251
20264

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\") = 2005
    AND 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'))
  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 LAX06CA026Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Payson, AZa loss of engine power due to fuel exhaustion, which was caused by the pilot's inadequate preflight and in-flight planning, his inadequate fuel consumption calculations, and his failure to divert to an alternate airport before the fuel situation became…Nov 7, 2005 · N2111P · Substantial damageNTSB LAX05CA230Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Tucson, AZthe student pilot's failure to maintain clearance from a fuel truck, and the flight instructor's inadequate supervision.Jul 12, 2005 · N9886K · Substantial damageNTSB LAX05LA180Accident · No injuriesLimited investigationFinal reportCessna 172M · Tucson, AZThe student pilot's improper flare that induced a porpoise, which resulted in the overload failure of the nose wheel assembly.May 18, 2005 · N9017H · Substantial damageNTSB LAX05LA159Accident · Minor injuriesLimited investigationFinal reportBeech 23 · Tucson, AZa loss of engine power due to the fatigue fracture and separation of the mixture control cable. The fatigue crack resulted from inadequate installation techniques by unknown maintenance personnel.May 7, 2005 · N2388Q · Substantial damageNTSB LAX05CA121Accident · No injuriesData collectionFinal reportPiper PA-18-150 · Chandler, AZthe pilot's failure to maintain directional control.Mar 22, 2005 · N4101E · Substantial damageNTSB LAX05CA098Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Chandler, AZthe students pilot's failure to maintain directional control resulting in a collision with the taxiway sign.Feb 17, 2005 · N80565 · Substantial damageNTSB LAX05CA067Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Tucson, AZthe pilot's failure to maintain directional control during landing rollout.Jan 8, 2005 · N8351W · Substantial damageNTSB LAX05CA066Accident · No injuriesData collectionFinal reportPiper PA-28-151 · Tucson, AZthe pilot's failure to maintain directional control during landing rollout.Jan 8, 2005 · N151MM · Substantial damageNTSB LAX05FA061Accident · 2 fatalField investigationFinal reportVail Lancair 235 · Sacaton, AZThe pilot's failure to maintain an adequate airspeed while maneuvering, which resulted in a stall/spin.Jan 6, 2005 · N64BV · Destroyed