NTSB investigations: Lycoming I0360 series

58 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
NTSB investigations: Lycoming I0360 series per year, 1982–2026: 58 cases
19826
19832
19842
19851
19861
19874
19881
19892
19902
19912
19921
19941
19952
19961
19994
20003
20016
20023
20034
20042
20053
20064
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.\"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 CHI06LA139Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Hale, MIThe pilot's inadequate compensation for the crosswind condition and failure to maintain clearance from the tree. Factors were the crosswind and the tree.May 25, 2006 · N3310P · Substantial damageNTSB 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 MIA05LA019Accident · No injuriesLimited investigationFinal reportScottish Bulldog 120/121 · Jacksonville, FLThe pilot's failure to maintain altitude/clearance with trees resulting in the in-flight collision with a tree, damage to the right main landing gear, and subsequent collapse of the right main landing gear during the emergency landing.Oct 28, 2004 · N556WH · Substantial damageNTSB 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 LAX04LA025Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R-200 · Pacoima, CAthe pilot's failure to maintain an adequate glide path on final approach and his failure to ensure adequate clearance from obstacles. The dark night was a factor.Oct 25, 2003 · N15192 · 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 NYC03LA142Accident · No injuriesLimited investigationFinal reportBeech 24 · Rome, NYThe pilot's failure to maintain directional control during a go-around which resulted in the airplane impacting trees. A factor in the accident was the shifting wind.Jun 25, 2003 · N1485L · Substantial damageNTSB DEN03LA004Accident · No injuriesLimited investigationFinal reportBeech C24R · Newcastle, UTthe pilot's failure to maintain clearance from the tree during takeoff. A factor was the reduced light conditions.Oct 9, 2002 · N18917 · Substantial damageNTSB CHI02LA295Accident · No injuriesLimited investigationFinal reportCessna 172R · Greenwood, ILThe CFI's poor inflight planning/decision to allow the airplane to get to too low of an altitude to assure a safe recovery from the simulated forced landing. Factors associated with the accident were the student pilot's delay initiating the go around and the…Sep 26, 2002 · N3510A · Substantial damageNTSB 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 FTW02LA038Accident · Serious injuriesLimited investigationFinal reportHughes 269C · Richmond, TXthe pilot's failure to maintain clearance from the power line while landing.Nov 17, 2001 · N9294F · Substantial damageNTSB 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 NYC01LA131Accident · Minor injuriesLimited investigationFinal reportHughes 269C · Fairfield, KYThe pilot's inadequate visual lookout during takeoff, and his inadequate reconnoiter of the area prior to takeoff.May 28, 2001 · N9660F · Substantial damageNTSB SEA01LA077Accident · No injuriesLimited investigationFinal reportCessna 172S · Renton, WAA Canadian goose which crossed the aircraft's flight path and impacted the left wing during the aircraft's final approach.Apr 24, 2001 · N435SP · Substantial damageNTSB NYC01LA092Accident · No injuriesLimited investigationFinal reportPiper PA-28R-180 · Lexington, VAThe pilot's inadequate compensation for the runway conditions. Factors included the soggy runway conditions, and the lack of available takeoff performance data in the owners manual.Apr 4, 2001 · N4586J · 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 FTW00LA133Accident · Minor injuriesLimited investigationFinal reportLake LA-4-200 · Claremore, OKThe pilot's premature raising of the flaps.Apr 28, 2000 · N5023L · Substantial damageNTSB NYC00LA115Accident · No injuriesLimited investigationFinal reportMooney M-20F · Parker, PAThe pilot's failure to maintain an adequate visual lookout, due to his distraction with a flock of birds. A factor was the pilot's improper in flight decision to continue the simulated engine failure to too low of an altitude.Apr 1, 2000 · N737HB · Substantial damageNTSB 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 CHI99LA225Accident · No injuriesLimited investigationFinal reportMooney M20J · Harbor Springs, MIthe pilot's inadequate compensation for the wind conditions and his failure to maintain clearance with the trees. Factors associated with the accident were the gusty winds, wind shear, and the trees.Jul 4, 1999 · N201HG · Substantial damageNTSB NYC99LA138Accident · Minor injuriesLimited investigationFinal reportEnstrom F-28 · Cincinnati, OHThe pilot's inadequate evaluation of the weather conditions at the time of departure, which resulted in a downwind takeoff. A factor in the accident was the change in wind direction.Jun 12, 1999 · N9588 · Substantial damageNTSB LAX96LA331Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Oxnard, CAthe instructor's inadequate supervision of the flight, and his delay in taking the controls and initiating a go-around. The student pilot's failure to maintain runway alignment and the proximity of the runway remaining marker were related factors.Sep 7, 1996 · N41331 · Substantial damageNTSB CHI95LA178Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Bay City, MIFailure of the pilot to maintain clearance from obstacles and his intentional buzzing.Jun 13, 1995 · N5256T · Substantial damageNTSB SEA95LA112Accident · Minor injuriesLimited investigationFinal reportHughes 269B · Caldwell, IDThe pilot's failure to maintain clearance from power lines. Factors include sunglare encountered when he turned into the sun.Jun 4, 1995 · N9474F · DestroyedNTSB FTW95LA011Accident · No injuriesLimited investigationFinal reportHughes 269C · Livingston, TXThe improper flare resulting in an undershoot of the intended landing area. A factor was the bird strike.Oct 10, 1994 · N9616F · Substantial damageNTSB SEA92IA040Incident · Minor injuriesIncident investigationFinal reportPiper PA-28R-200 · Anacortes, WAA bird impacting the aircraft.Jan 19, 1992 · N2742R · Minor damageNTSB CHI91LA186Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Pulaski, WIThe pilot's failure to select a proper touchdown point. A factor in the accident was inadequate runway maintenance by airport personnel.Jun 5, 1991 · N111CP · Substantial damageNTSB 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 FTW90LA099Accident · Minor injuriesLimited investigationFinal reportEnstrom F-28A · Danbury, TXPilot in command's failure to see and avoid wires during the final stage of an approach to a confined area. A contributing factor to the accident was the pilot's disregard of the operator's instructions after he landed the first time.Apr 22, 1990 · N287Q · Substantial damageNTSB CHI90LA094Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Wonder Lake, ILThe pilot's inadequate compensation for wind conditions, and his faiiure to maintain proper altitude on final approach to land. Factors related to the accident were: the trees & snowbank.Mar 3, 1990 · N55030 · Substantial damageNTSB LAX89LA175Accident · No injuriesLimited investigationFinal reportMooney M20E · Julian, CAThe inadequate preflight planning/preparation by the pilot. Contributing to the accident was the loose gravel runway and the fence which the airplane was unable to clear.Apr 30, 1989 · N9276V · Substantial damageNTSB ATL89LA115Accident · No injuriesLimited investigationFinal reportBeech B24R · New Carlisle, OHThe pilot's failure to clear the trees after the in-flight collision with an undetermined object. He allowed the altitude to decrease to the point of colliding with trees before initiating remedial action to maintain flight and land the airplane.Mar 26, 1989 · N283G · Substantial damageNTSB ATL88LA101Accident · No injuriesLimited investigationFinal reportRockwell 112A · Juliette, GAThe airplane struck a transmission cable over a river at about 100 ft AGL. The plt rptd that he inadvertently stalled the airplane while turning to reverse direction during an aerial photo flt, and that he felt a 'bump' during recovery. After returning to the…Jan 20, 1988 · N1432J · Substantial damageNTSB 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 CHI88LA020Accident · No injuriesLimited investigationFinal reportCessna 152 · New Hudson, MIThe student pilot was on his first solo flight. Before turning onto final approach to land, he noticed another aircraft ahead, already on final approach. The student decided to s-turn for spacing, but while maneuvering, altitude was lost. Subsequently, he saw…Nov 7, 1987 · N46065 · Substantial damageNTSB FTW87LA144Accident · No injuriesLimited investigationFinal reportGreat Lakes 2T-1A · Lago Vista, TXWhile maneuvering at approximately 50 feet AGL, the aircraft's landing gear contacted a 7200 volt powerline. Control of the aircraft was lost, and it descended out of control into about 2 feet of water, causing substantial damage.Jun 14, 1987 · N874K · Substantial damageNTSB BFO87LA018Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200R · West Point, VAAfter making a low pass over the uncontrolled airport the CFI decided to let the student pilot make a touch and go landing on runway 27 at West Point municipal airport. West Point, Virginia. The maneuver was successfully completed and the aircraft came around…Feb 2, 1987 · N33399 · Substantial damageNTSB FTW86LA157Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R-200 · Afton, OKThe pilot stated he was making a precautionary landing at night due to engine roughness and impacted electrical transmission wires. Investigation failed to disclose any reason for the reported engine roughness.Aug 30, 1986 · N214PR · Substantial damageNTSB BFO85LA033Accident · No injuriesLimited investigationFinal reportMooney M20E · Mitchellville, MDAfter experiencing a gusty crosswind on final approach to runway 18, the pilot employed standard crosswind landing technique. Once over the threshold, power was reduced to idle and the pilot commenced the flare. During the flare, a gust of wind blew the alft…Apr 5, 1985 · N2761W · Substantial damageNTSB CHI84LA360Accident · No injuriesLimited investigationFinal reportBeech B-24-R · Independence, WIThe acft collided with trees near the departure end of the field during an attempted go-around. A passenger reported that the go-around was initiated at about 100 ft AGL, 1/2 way down the fld. The plt said the fld was in a valley, it wasa hot (reported temp…Aug 25, 1984 · N2217L · Substantial damageNTSB 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 · Destroyed