Fatal NTSB investigations: Lycoming I0360 series

22 cases on aircraft whose registry engine model is Lycoming I0360 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
Fatal NTSB investigations: Lycoming I0360 series per year, 1982–2026: 22 cases
19822
19831
19841
19871
19911
19992
20001
20012
20021
20032
20041
20053
20063
20071

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.\"highestInjuryLevel\" = 'Fatal'
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41515')
      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 CHI07LA150Accident · 2 fatalLimited investigationFinal reportWood Vans RV7A · Marysville, OHThe pilot's failure to maintain clearance from an object during a go-around and subsequent failure to maintain adequate airspeed. An airport sign and an inadvertent stall were factors.May 21, 2007 · N7259N · Substantial damageNTSB DEN06FA111Accident · 1 fatalField investigationFinal reportPiper PA-28R-201 · Salida, COthe pilot's inadequate preflight planning/preparation. Contributing factors in this accident were the pilot's lack of familiarity with the geographical area, his becoming lost/disoriented, his improper decision, the high density altitude, and the reduction in…Aug 7, 2006 · N6506C · Substantial damageNTSB NYC06FA169Accident · 3 fatalField investigationFinal reportPiper PA-28R-200 · Block Island, RIThe pilot's inadequate preflight decision making and his failure to maintain terrain clearance during departure. Contributing, were low ceilings, rain, and thunderstorms.Jul 5, 2006 · N5012S · Substantial damageNTSB NYC06FA156Accident · 1 fatalField investigationFinal reportPiper PA-28R-200 · Philipsburg, PAThe pilot's failure to comply with the published instrument approach procedure, which resulted in controlled flight into trees. Factors in the accident were the low cloud ceiling, and dark night conditions.Jun 26, 2006 · N56246 · DestroyedNTSB LAX06LA006Accident · 2 fatalLimited investigationFinal reportRobinson Helicopter R-22 Beta II · Eagar, AZThe pilots' inadequate in-flight planning, which led the helicopter toward rising terrain in excess of the performance capability of the helicopter. Contributing factors were the high density altitude, and the rapidly rising terrain.Oct 14, 2005 · N7196J · Substantial damageNTSB DFW05FA099Accident · 3 fatalField investigationFinal reportPiper PA-28R-200 · Jefferson, TXThe pilot's failure to maintain clearance from an unmarked transmission line. A contributing factor was the low altitude flight.Apr 10, 2005 · N2981R · DestroyedNTSB IAD05FA052Accident · 2 fatalField investigationFinal reportPiper PA-28R-201 · Green Creek, NJThe flight crew's failure to maintain terrain clearance while executing a practice published instrument approach in night visual meteorological conditions. A factor in the accident was the dark night.Apr 6, 2005 · N36725 · DestroyedNTSB NYC04FA100Accident · 2 fatalField investigationFinal reportPiper PA-28R-180 · Harrietstown, NYThe pilot's failure to follow instrument flight rules procedures resulting in a collision with a tree. Factors related to the accident were the dark night conditions, low visibility, and low cloud ceiling.Apr 3, 2004 · N4686J · Substantial damageNTSB FTW03FA182Accident · 2 fatalField investigationFinal reportCessna 172S · McKinney, TXThe CFI's failure to maintain airspeed sufficient for flight resulting in an inadvertent stall/spin during the forced landing. A contributing factor was the impact with a bird, which affected the performance of the airplane.Jul 8, 2003 · N166ME · DestroyedNTSB SEA03FA123Accident · 3 fatalField investigationFinal reportBeech A24-R · Yellow Pine, IDThe pilot's failure to maintain clearance. Factors include trees and mountainous terrain.Jul 4, 2003 · N254M · DestroyedNTSB CHI02FA262Accident · 3 fatalField investigationFinal reportPiper PA-28R-180 · Newaygo, MIThe altitude/clearance disregarded by the pilot and his ostentatious display. The wire and low altitude flight were a contributing factor.Aug 28, 2002 · N4988J · DestroyedNTSB NYC01FA217Accident · 2 fatalField investigationFinal reportCessna 172SP · Matawan, NJThe pilot's failure to maintain runway alignment during the initial climb. Factors were the pilot's failure to perform a go-around, the pilot's lack of flight experience in nighttime conditions, the nighttime conditions, and a tailwind.Aug 27, 2001 · N629PD · Substantial damageNTSB CHI01FA089Accident · 4 fatalField investigationFinal reportPiper PA-28R-201 · Webb Lake, WIthe pilot not maintaining altitude/clearance from the trees during takeoff. Factors were the trees, transmission wire, and the dark night.Feb 15, 2001 · N120CC · DestroyedNTSB CHI01FA025Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Gaylord, MIThe pilot not maintaining proper glideslope and localizer alignment during the precision instrument approach, the pilot continuing flight below the decision height, the pilot not performing a missed approach, and the pilot not maintaining altitude/clearance…Oct 25, 2000 · N15900 · DestroyedNTSB NYC99FA193Accident · 2 fatalField investigationFinal reportPiper PA28R-180 · Seven Springs, PAThe pilot's failure to obtain a rate of climb after takeoff due to spatial disorientation. Factors in this accident were low ceilings, fog, and the pilot's lack experience in instrument meteorological conditions.Aug 8, 1999 · N3892T · Substantial damageNTSB CHI99FA278Accident · 4 fatalField investigationFinal reportPiper PA-28R-200 · Grayslake, ILthe pilot not maintaining altitude and clearance. Factors were the light condition of night, the pilot's lack of recent experience in night operations, and the transmission wire.Aug 6, 1999 · N56718 · DestroyedNTSB NYC91FA140Accident · 1 fatalField investigationFinal reportPiper PA-28-151 · Shelburne, VTPremature lift-off by the pilot, which resulted in a subsequent stall/mush and collision with trees. Factors related to the accident were: the pilot's inadequate preflight planning/preparation, and the unfavorable wind condition.May 25, 1991 · N8433C · DestroyedNTSB FTW88FA038Accident · 1 fatalField investigationFinal reportPiper PA-28R-200 · Burnet, TXThe pilot arrived in the area of his planned destination and completed the outbound and inbound procedure turns for the NDB runway 17 approach without reported incident. Almost immediately thereafter, the aircraft impacted a large oak tree about 15 feet AGL…Dec 19, 1987 · N33007 · DestroyedNTSB SEA84FA123Accident · 1 fatalField investigationFinal reportPiper PA-34-200 · North Bend, ORThe acft was cleared for an ILS rwy 4 apch while 9 miles north of oth (North Bend) VOR. Instructions were given to cross oth VOR at or above 3700 ft MSL. 14 min later, the plt reported to North Bend fss 'my needle doesn't seem to be moving on my localizer…Jun 4, 1984 · N1067U · DestroyedNTSB FTW83FA079Accident · 2 fatalField investigationFinal reportMooney M20E · Cushing, OKThe acft collided with a powerline during a low flt down a river. The acft impacted 3 high tension cables spanning the river. Witnesses said the acft was flying low and fast. The collision produced a sound 'like a gunshot' and the acft fell to the ground and…Jan 9, 1983 · N7778M · DestroyedNTSB SEA82FAD01Accident · 1 fatalFinal reportLake LA-4-200 · Ketchikan Intl., AKDeparting under a special VFR clearance, the acft entered IMC within a period of approximately 15 secs after takeoff. The acft struck trees & the ground approximately 2 mi south of the airport.Jul 30, 1982 · N2708P · DestroyedNTSB LAX82DA185Accident · 2 fatalFinal reportRockwell 112TC · Fort Apache, AZThe aircraft was observed to fly between two parked campers in a left wing low attitude before hitting a pine tree. The aircraft then went into an inverted position before contacting the ground about 300 yards from the campers. Investigation revealed that the…May 20, 1982 · N4567W · Destroyed