NTSB investigations: Lycoming IO-320 series, 2005

8 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, 2005 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\") = 2005
    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 DFW06FA037Accident · 3 fatalField investigationFinal reportPiper PA-30 · Raymond, MSThe pilot's failure to maintain Vmc (velocity minimum control) on initial climb resulting in a loss of control. Contributing factors were the loss of engine power to the right engine and the prevailing gusty wind conditions.Dec 1, 2005 · N7315Y · DestroyedNTSB ANC05CA134Accident · No injuriesData collectionFinal reportChampion 7KCAB · Fairbanks, AKThe pilot's selection of unsuitable terrain for landing, which resulted in a nose over during the landing roll. A factor contributing to the accident was a depression/ditch in the landing surface.Sep 3, 2005 · N63995 · Substantial damageNTSB SEA05CA183Accident · No injuriesData collectionFinal reportBellanca 7KCAB · Chiloquin, ORThe failure of the left chain link which permits the pilot to control the tailwheel, and the subsequent inability of the pilot to control the airplane during the landing roll.Aug 27, 2005 · N11661 · Substantial damageNTSB CHI05FA189Accident · 3 fatalField investigationFinal reportPiper PA-30 · Aurora, MOThe pilot not maintaining adequate airspeed and aircraft control during initial climb, which resulted in an inadvertent stall/spin at a low altitude. A factor to the accident was the pilot operating the airplane over its certified maximum gross weight.Jul 18, 2005 · N7868Y · Substantial damageNTSB ATL05CA125Accident · No injuriesData collectionFinal reportCessna 172P · Monroeville, ALThe student pilot's failure to maintain directional control and the subsequent collision with the ground during landing.Jul 7, 2005 · N98530 · Substantial damageNTSB MIA05CA061Accident · No injuriesData collectionFinal reportCessna 172 · Brooksville, FLThe pilot's improper landing flare which resulted in substantial damage during the subsequent hard landing.Feb 21, 2005 · N98636 · Substantial damageNTSB ATL05FA043Accident · 1 fatalField investigationFinal reportPiper PA-30 · Charleston, SCThe pilot's inadequate preflight and mismanagement of the fuel supply, which resulted in fuel exhaustion.Jan 11, 2005 · N7654Y · Substantial damageNTSB NYC05LA056Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Millville, NJThe flight instructor's failure to lower the landing gear during landing.Jan 10, 2005 · N7547Y · Substantial damage