NTSB investigations: Lycoming IO-540 series

30 cases on aircraft whose registry engine model is Lycoming IO-540 series, where the first occurrence was “In flight collision with object”. 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 IO-540 series per year, 1982–2026: 30 cases
19821
19831
19843
19851
19861
19871
19891
19902
19911
19921
19934
19951
19971
19991
20001
20012
20021
20032
20042
20062

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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41530', '41585')
      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\" = 220))
  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 DFW06FA102Accident · 2 fatalField investigationFinal reportRobinson R44 II · Fredericksburg, TXThe pilot's failure to maintain clearance with the power lines. Contributing factors were the dusk light condition and the pilot's non-compliance with standard taxi and takeoff procedures.Apr 13, 2006 · N123CK · DestroyedNTSB ATL06FA038Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Camden, ALThe pilots failure to maintain altitude and clearance during a visual descent which resulting in an in-flight collision with trees and the ground for undetermined reasons.Jan 28, 2006 · N38510 · DestroyedNTSB NYC04CA166Accident · No injuriesData collectionFinal reportRobinson R-44 II · Beverly, MAThe pilot's inadequate visual lookout, which resulted in a collision with transmission wires.Jul 11, 2004 · N277MC · Substantial damageNTSB CHI04LA052Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300 · Fishers, INThe pilot not maintaining altitude/clearance from the trees during the circling approach, his continued descent below minimum descent altitude, and the pilot not performing a missed approach. A factor was the trees the pilot impacted during the circling…Jan 2, 2004 · N21992 · Substantial damageNTSB ATL04LA014Accident · Minor injuriesLimited investigationFinal reportMcCan Velox Revolution II · Mooresville, NCThe pilot's inadequate in-flight planning/decision to conduct an aerobatic maneuver at an altitude too low to initiate a recovery.Oct 12, 2003 · N296VX · DestroyedNTSB IAD03FA070Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Factoryville, PAThe pilot's improper in-flight decision to descend below the published minimum descent altitude while executing a non-precision approach in instrument meteorological conditions, which resulted in collision with trees. A factor was the fog.Aug 8, 2003 · N6373C · DestroyedNTSB ANC02FA010Accident · 1 fatalField investigationFinal reportPiper PA-32 · Haines, AKThe pilot's continued VFR flight into instrument meteorological conditions, and subsequent collision with trees while in cruise flight. Factors in the accident were weather conditions consisting of freezing rain, mist, and low ceilings.Jan 15, 2002 · N30004 · Substantial damageNTSB IAD01FA070Accident · 1 fatalField investigationFinal reportPiper PA-32R-301 · Greenwich, CTThe pilot's failure to maintain control of the airplane while maneuvering in instrument meteorological conditions, due to spatial disorientation. Factors in the accident were the fog, and the pilot's use of a sedating medication.Jun 22, 2001 · N13VH · DestroyedNTSB ATL01FA019Accident · 1 fatalField investigationFinal reportCessna 206H · Vandiver, ALThe pilot's inflight decision to continued visual flight into instrument meteorological conditions resulted in the inflight collision with trees. Low ceilings and trees were factorsJan 12, 2001 · N2468G · DestroyedNTSB CHI00FA284Accident · 2 fatalField investigationFinal reportBeech K35 · Manitowish Watr, WIthe pilot not maintaining altitude/clearance from the trees during an approach on a dark, low overcast night, the pilot's improper use of an IFR procedure without clearance, and the pilot's improper in-flight decision to attempt an IFR approach without…Sep 2, 2000 · N3076C · DestroyedNTSB ANC99LA127Accident · No injuriesLimited investigationFinal reportMaule M-7 · Kotzebue, AKAn in-flight collision with a bird.Aug 28, 1999 · N770AS · Substantial damageNTSB NYC97FA080Accident · 2 fatalField investigationFinal reportPiper PA-60-601P · Waterford, VAfailure of the pilot to follow the published instrument (IFR) approach procedure, by failing to maintain the minimum altitude for that segment of the approach.Apr 28, 1997 · N885JC · DestroyedNTSB ANC95LA161Accident · No injuriesLimited investigationFinal reportMaule M-7 · Aniak, AKThe pilot's selection of unsuitable terrain for takeoff.Sep 9, 1995 · N61043 · Substantial damageNTSB ANC94LA013Accident · No injuriesLimited investigationFinal reportPiper PA-32-301 · Karluk, AKThe selection of unsuitable terrain for landing.Oct 20, 1993 · N4327P · Substantial damageNTSB CHI93LA185Accident · Minor injuriesLimited investigationFinal reportPiper PA-36-400 · Elbow Lake, MNthe pilot's failure to maintain an adequate visual outlook during aerial application manuevers.May 31, 1993 · N2342Y · Substantial damageNTSB BFO93FA082Accident · 1 fatalField investigationFinal reportPiper PA-32-300 · Lyburn, WVFailure of the pilot to attain sufficient altitude to remain clear of rising terrain and objects. Factors related to the accident were darkness and rising terrain.May 12, 1993 · N45087 · DestroyedNTSB LAX93LA114Accident · No injuriesLimited investigationFinal reportEagle DW-1 · Rachael, NVThe pilot poor preflight planning and preparation. The road sign was a factor relating to this accident.Feb 11, 1993 · N8805D · Substantial damageNTSB SEA92LA078Accident · No injuriesLimited investigationFinal reportMaule M-7 · Aravada, WYThe pilot's failure to maintain a visual lookout, and his diverted attention. Factors include a low pass, and a transmission wire in the path of flight.Apr 14, 1992 · N61043 · Substantial damageNTSB CHI91DTK05Accident · No injuriesFinal reportEagle DW1 · Hurley, SDThe failure of the pilot to maintain a visual lookout.Sep 10, 1991 · N8814L · Substantial damageNTSB CHI91FA031Accident · 4 fatalField investigationFinal reportPiper PA-32-RT300 · Gaylord, MIThe pilot's failure to maintain adequate terrain clearance. Factors which contributed to the accident were: the dark night, adverse weather conditions, and the pilot's overconfidence in continuing VFR flight into these conditions.Nov 22, 1990 · N9800K · DestroyedNTSB LAX90LA108Accident · No injuriesLimited investigationFinal reportPiper PA-32-R-300 · Sacramento, CAAn inadvertent collision with a large bird during the hours of darkness while in the landing pattern.Jan 20, 1990 · N38908 · Substantial damageNTSB MIA89FA113Accident · 1 fatalField investigationFinal reportPiper Aerostar 600 · Jacksonville, FLImproper use of the IFR procedure by the pilot, his failure to maintain a proper glide path, and his failure to identify the decision height.Mar 23, 1989 · N77BR · DestroyedNTSB MKC87LA088Accident · No injuriesLimited investigationFinal reportEagle DW-1 · Lincoln, KSThe plt was spraying 2/4/D when one spray nozzle stuck open. Rather than kill alfalfa and trees during the turnarounds, the plt elected to land on a dirt road and repair the nozzle. He misjudged the width of the road and on touchdown, the right wing touched…Apr 23, 1987 · N8802B · Substantial damageNTSB ATL86FA125Accident · 1 fatalField investigationFinal reportBellanca 17-31ATC · Winchester, TNThe plt made a VFR pattern at an uncontrolled arpt and noted a truck alongside the north end of the rwy. The plt did notsee any persons on the rwy. During the landing flare the plt noticed a man on the rwy near the right wingtip. A jolt was felt as the acft…May 6, 1986 · N28138 · Substantial damageNTSB CHI85LA336Accident · Minor injuriesLimited investigationFinal reportPiper PA-36-300 · Red Lake Falls, MNThe acft contacted wires during an aerial application flt. The plt stated he was maintaining extra alt to avoid tall weeds and the clearance below the wires was misjudged. The wires severed the vertical fin and rudder.Aug 6, 1985 · N2350Y · Substantial damageNTSB BFO85FA002Accident · 4 fatalField investigationFinal reportPiper PA-32R-301 · Salisbury, MDAfter contacting millville fss 4 times for wx info the acft departed lincoln park, NY, at 1858 EDT with destination listed on the IFR flt plan as easton, MD. En route the plt diverted to Salisbury, MD, due to wx. After being cleared forthe rwy 32 ILS the acft…Oct 25, 1984 · N81752 · DestroyedNTSB CHI84FA148Accident · No injuriesField investigationFinal reportPiper Aerostar 600 · Pontiac, MIDuring an ILS apch, the acft collided with treetops while it was slightly left of the apch course near the middle marker. The plt continued to fly the acft to the rwy & the plane touched down about 1000 ft beyond the threshold. At touchdown, the acft veered…Apr 4, 1984 · N3645T · Substantial damageNTSB ATL84FA083Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300 · Attalla, ALDuring a VOR approach to land in IMC wx, the acft collided with a tree. The non-instrument rated plt had filed an IFR flt plan on this and other occasions even though he was not qualified. During this approach, the descent was continued past the mda of 960…Jan 16, 1984 · N31844 · DestroyedNTSB MIA83LA056Accident · No injuriesLimited investigationFinal reportPiper PA-32-301R · Near Vero Beach, FLThe acft collided with tree tops during a night flight but the pilot was able to maintain control and land at a nearby airport. According to the pilot he was on approach to fort pierce airport when the accident occurred. However according to some witnesses…Jan 3, 1983 · N35590 · Substantial damageNTSB FTW82DA319Accident · No injuriesFinal reportEagle DW-1 · Cheneyville, LAThe acft was on the approach to spray a cottonfield when a collision with an unseen power line occurred. The collision forced the acft down and the pilot made a hard landing which damaged the landing gear and the right wing. The visibilitywas about 5 miles in…Aug 8, 1982 · N8807Z · Substantial damage