NTSB investigations: Lycoming I0360 series, 1996

25 cases on aircraft whose registry engine model is Lycoming I0360 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 I0360 series, 1996 per year, 1964–2026: 2,882 cases
196428
196540
196658
196789
196873
196972
197080
197165
197267
197376
197468
197581
197676
197796
1978110
197970
198070
198178
198251
198357
198447
198533
198644
198736
198833
198933
199029
199127
199231
199326
199427
199526
199625
199722
199830
199937
200042
200159
200253
200351
200458
200537
200638
200746
200829
200928
201037
201127
201247
201335
201431
201535
201642
201731
201830
201943
202028
202122
202226
202322
202429
202525
202620

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\") = 1996
    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'))
  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 ATL97LA025Accident · No injuriesLimited investigationFinal reportBeech BE-24R · Doraville, GAThe loss of engine power for undetermined reasons.Dec 11, 1996 · N6988R · Substantial damageNTSB ATL97LA020Accident · Serious injuriesLimited investigationFinal reportLake LA-4-200 · St. Petersburg, FLFuel exhaustion for undetermined reasons.Nov 27, 1996 · N1109L · Substantial damageNTSB NYC97LA010Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Norwood, MAfailure of the pilot to perform a go-around, when an animal obstructed the runway; and his failure to maintain clearance from an obstruction (VASI). Factors relating to the accident were: darkness, an animal (deer) on the runway, and the proximity of the…Nov 2, 1996 · N1216T · Substantial damageNTSB LAX97FA032Accident · 5 fatalField investigationFinal reportPiper PA-34-200 · Halawa, HIthe pilot's inadvertent VFR flight into instrument meteorological conditions (IMC), and his failure to maintain sufficient clearance and/or altitude from mountainous terrain. Factors related to the accident were: darkness, adverse weather conditions, and…Nov 2, 1996 · N1701K · DestroyedNTSB ATL97LA007Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Olive Branch, MSThe farmer's failure to maintain security of his livestock/animals.Oct 16, 1996 · N16413 · Substantial damageNTSB CHI96LA356Accident · No injuriesLimited investigationFinal reportPiper PA-28R-201 · Chesterfield, MOimproper flare by the dual student during the landing, and delayed remedial action by the flight instructor (CFI).Sep 30, 1996 · N6008H · Substantial damageNTSB NYC96LA186Accident · No injuriesLimited investigationFinal reportMooney M20K · Islip, NYloss of engine power for undetermined reason(s), which resulted in an emergency/wheels-up landing.Sep 21, 1996 · N3375X · Substantial damageNTSB NYC96WA191Accident · 1 fatalForeign investigationLake LA-4 · Azores, PortugalSep 16, 1996 · N2664P · DestroyedNTSB 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 FTW96LA375Accident · No injuriesLimited investigationFinal reportHughes 269B · Frisco, TXThe pilot's improper touchdown procedure.Sep 1, 1996 · N9558F · Substantial damageNTSB SEA96LA204Accident · No injuriesLimited investigationFinal reportPrice Acro Sport II · Coeur D'Alene, IDthe pilot's improper inflight planning/decision, and his failure to properly monitor (manage) the fuel supply, which resulted in fuel exhaustion and a subsequent forced landing. Soft terrain in the forced landing area was a related factor.Aug 24, 1996 · N456HD · Substantial damageNTSB IAD96LA135Accident · No injuriesLimited investigationFinal reportMooney M20F · Hanover, PAthe pilot's delay in aborting the landing. Factors related to the accident were: the lack of braking action on the wet grass runway, the pilot's lack of experience in the make and model of airplane, and the sign near the departure end of the runway.Aug 15, 1996 · N9103V · Substantial damageNTSB MIA96LA205Accident · No injuriesLimited investigationFinal reportHampson Velocity · Dublin, GAthe failure of the exhaust of the cylinder Nos. 2 and 4 at each exhaust flange for undetermined reasons. The unsuitable terrain encountered during the forced landing was a factor.Aug 6, 1996 · N637KM · Substantial damageNTSB FTW96LA305Accident · No injuriesLimited investigationFinal reportStol UC-1 · Princeton, TXimproper adjustment of the left propeller governor which resulted in uncommanded feathering of the left propeller. Factors were: the airplane's inadequate engine out performance and the lack of suitable terrain for the forced landing.Jul 16, 1996 · N9507U · Substantial damageNTSB LAX96LA347Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Palm Springs, CAthe failure of a propeller blade as a result of undetected in-service mechanical damage that caused a stress point that progressed to a point of failure.Jul 13, 1996 · N5388L · Substantial damageNTSB LAX96LA256Accident · No injuriesLimited investigationFinal reportMooney M20E · Rio Linda, CAThe pilot's failure to attain/maintain the proper approach airspeed, his failure to attain the proper runway touchdown point, and his failure to initiate a go-around when a landing overshoot became apparent. A factor in the accident was the airport…Jul 1, 1996 · N3229F · DestroyedNTSB LAX96LA242Accident · No injuriesLimited investigationFinal reportPiper PA-34-200 · Avalon, CAThe failure of the left brake for undetermined reasons.Jun 23, 1996 · N507TH · Substantial damageNTSB SEA96FA130Accident · 1 fatalField investigationFinal reportHughes 269C · Eldon, WAfatigue failure of the connecting rod cap, which resulted in loss of engine power and ditching at sea.Jun 19, 1996 · N7400F · DestroyedNTSB LAX96LA217Accident · No injuriesLimited investigationFinal reportHughes 269B · Georgetown, CAloss of engine power for undetermined reason(s), while practicing an autorotation, which resulted in a forced landing; and the flight instructor's misjudged landing flare during the emergency autorotation/landing.Jun 1, 1996 · N9332F · Substantial damageNTSB IAD96FA074Accident · 1 fatalField investigationFinal reportLake LA-4-200 · Sunapee, NHthe pilot's failure to maintain control of the airplane. Factors in this accident were: the pilot's lack of currency in type and model airplane, and not following the requirement for the pilot to have a flight instructor onboard during water landings.May 9, 1996 · N5040L · DestroyedNTSB CHI96LA155Accident · No injuriesLimited investigationFinal reportPiper PA-28R-201 · Lafayette, INthe flight instructor's inadequate supervision and the dual student's failure to extend the landing gear. Factors were the distraction of the flight instructor and the student's failure to use checklist procedures.May 9, 1996 · N9816C · Substantial damageNTSB MIA96LA132Accident · Minor injuriesLimited investigationFinal reportAerotek Pitts S-2A · Reidsville, NCthe pilot failed to maintain control of the airplane while performing an acrobatic maneuver.Apr 27, 1996 · N8040 · DestroyedNTSB ATL96LA069Accident · No injuriesLimited investigationFinal reportPiper J3C-65 · Nashville, TNthe failure of the pilot of the Piper PA-28, N26046, to visually clear the intended taxi course.Mar 23, 1996 · N26046 · 2 aircraft · Substantial damageNTSB ATL96LA052Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Birmingham, ALthe pilot's failure to maintain directional control during landing,Feb 22, 1996 · N2590Q · Substantial damageNTSB MIA96LA075Accident · No injuriesLimited investigationFinal reportPiper PA-28R · Boca Raton, FLthe partial loss of engine power due to the fatigue failure of the number 3 cylinder hold down studs and nut. A factor was the pilot'e evasive maneuver to avoid golphers on a golf course.Feb 8, 1996 · N55329 · Substantial damage