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

6 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, 2000, 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\") = 2000
    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 LAX01LA048Accident · No injuriesLimited investigationFinal reportCessna 172N · Marana, AZThe student pilot's improper flare and improper recovery from a bounced landing. A factor in the accident was the morning sun, which momentarily restricted the pilot's vision.Nov 30, 2000 · N8173E · Substantial damageNTSB LAX00LA309Accident · No injuriesLimited investigationFinal reportPiper PA-18-150 · Scottsdale, AZFailure of the pilot to maintain directional control on the landing rollout. Also causal to the accident was his failure to retract flaps during the aborted landing attempt, which lead to a loss of lift and a hard landing followed by a ground loop.Aug 21, 2000 · N91003 · Substantial damageNTSB LAX00LA305Accident · No injuriesLimited investigationFinal reportCessna 172 · Flagstaff, AZThe pilot's improper go-around procedure and his failure to maintain directional control on landing.Aug 18, 2000 · N2078E · Substantial damageNTSB LAX00LA256Accident · No injuriesLimited investigationFinal reportCessna 172 · Chandler, AZfailure of the pilot-in-command to adequately compensate for a crosswind condition and maintain directional control during the landing roll, resulting in the airplane departing the runway and colliding with a sign.Jul 8, 2000 · N1897V · Substantial damageNTSB 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 LAX00LA128Accident · Serious injuriesLimited investigationFinal reportAero Commander 100 · Buckeye, AZThe pilot's improper judgment and his failure to maintain clearance from the ground. A factor was the pilot's lack of recent experience.Mar 16, 2000 · N3896X · Substantial damage