NTSB investigations: Lycoming IO-320 series, 2002

13 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, 2002 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\") = 2002
    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 MIA03CA037Accident · No injuriesData collectionFinal reportPiper PA-30 · Tallahassee, FLthe pilot's improper start procedure which resulted in an unintentional engine start, and unoccupied aircraft collision with hangar structure.Dec 26, 2002 · N752CF · Substantial damageNTSB CHI03LA039Accident · Serious injuriesLimited investigationFinal reportPiper PA-30 · Jackson, MIThe pilot's failure to follow the checklist and extend the landing gear resulting in a gear up landing.Dec 15, 2002 · N948SB · Substantial damageNTSB IAD03LA008Accident · Serious injuriesLimited investigationFinal reportPiper PA-30 · Middlesboro, KYThe pilot's operation of the airplane with a known deficiency. Factors related to the accident were the loss of engine power of the left engine due to a failure of the left engine-driven and electric fuel pumps, and inadequate maintenance.Oct 22, 2002 · N8770Y · Substantial damageNTSB DEN03LA011Accident · Minor injuriesLimited investigationFinal reportBellanca 7KCAB · Fort Collins, COThe pilot's improper recovery from a bounced landing, and his failure to maintain airspeed resulting in a stall.Oct 22, 2002 · N41807 · DestroyedNTSB MIA03LA003Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Immokalee, FLA loss of engine power on takeoff for undetermined reasons.Oct 8, 2002 · N7014Y · Substantial damageNTSB NYC02FA196Accident · 2 fatalField investigationFinal reportPiper PA-30 · Gilford, NHThe flight instructor's failure to maintain airplane control, which resulted in an uncontrolled collision with water.Sep 25, 2002 · N7106Y · DestroyedNTSB ATL02LA167Accident · No injuriesLimited investigationFinal reportPiper PA-30-30 · Winder, GAThe pilot's failure to maintain directional control during landing roll which resulted in the subsequent collision with an airport sign and the collapse of the main landing gear. the pilot's improper recovery from a bounced landing was a contributing factor.Sep 7, 2002 · N7817Y · Substantial damageNTSB ANC02LA087Accident · No injuriesLimited investigationFinal reportPiper PA-18 · Chugiak, AKThe pilot's inadequate compensation for wind conditions and his failure to maintain directional control during an aborted landing, which resulted in an in-flight collision with a culvert. A factor associated with the accident was a wind gust.Aug 1, 2002 · N4948 · Substantial damageNTSB CHI02LA219Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Abilene, KSThe pilot failed to achieve clearance over the trees and wires. Factors associated with the accident were the pilot failed to use all available runway, a downwind takeoff was performed, the tailwind, trees, and wires.Jul 29, 2002 · N90TC · Substantial damageNTSB CHI02FA215Accident · 1 fatalField investigationFinal reportPiper PA-30 · Marble Hill, MOThe solid fuel system contamination resulting in a loss of engine power. The inadequate emergency procedures, and the airspeed not maintained by the pilot were additional causes.Jul 25, 2002 · N8563Y · DestroyedNTSB FTW02LA164Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Jonesville, LAthe pilot's failure to attain the proper touchdown point, which resulted in a runway overrun and an on ground encounter with terrain.May 24, 2002 · N8302Y · Substantial damageNTSB SEA02LA081Accident · Minor injuriesLimited investigationFinal reportCook Coot A · Harrison, IDThe pilot's failure to detect an unsafe boat wake during the landing process, and his inadvertent initiation of a porpoise after coming in contact with the boat wake just after touchdown on a body of water. Factors include a large wake wave/swell created by…May 12, 2002 · N12QQ · Substantial damageNTSB MIA02LA055Accident · No injuriesLimited investigationFinal reportBellanca 7KCAB · Milton, FLThe inability of the pilot to maintain directional control of the airplane resulting in a ground loop. A finding in the investigation was a loose left rudder flight control cable.Jan 22, 2002 · N41686 · Substantial damage