15 Apr 2013: BEECH N35 — William M. Morris

15 Apr 2013: BEECH N35 (N35) — William M. Morris

No fatalities • Warren, AR, United States

Probable cause

The fatigue failure of the engine crankshaft due to oversized crankcase saddle bores, which resulted from maintenance personnel improperly resizing the saddle bores during engine maintenance.

— NTSB Determination

Accident narrative

On April 15, 2013, about 0945 central daylight time, a Beech model N35 airplane, N9414Y, was substantially damaged during a forced landing following a loss of engine power after takeoff from the Warren Municipal Airport (3M9), Warren, Arkansas. The pilot and passenger sustained minor injuries. The aircraft was registered to and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed for the flight. An instrument flight rules flight plan had been filed, but not yet activated. The flight was originating at the time of the accident. The intended destination was the Mena Intermountain Municipal Airport (MEZ), Mena, Arkansas.The pilot reported that he had departed from runway 21 (3,829 feet by 75 feet, asphalt) at 3M9 and climbed to 700 feet mean sea level (msl). As he started a right turn to the west, about 1,000 feet msl, the engine lost power. He established a glide in an attempted to return to the airport. However, due to "strong" winds, the airplane contacted the ground "abruptly short of the runway."

A postaccident engine teardown and subsequent metallurgical examination were conducted. The crankcase was cracked starting at the number 1 cylinder head mounting stud and continuing to the top of the case. The crankcase number 2 main bearing saddle exhibited longitudinal deformation adjacent to the bore, with fretting and galling on the saddle landings. The other saddles exhibited curvilinear marks on the split plane landings and helical marks on the saddle bores, consistent with machining marks. The crankcase was re-assembled and the saddle bore diameter at the nose of the crankshaft was measured. The bore diameter was within limits in the area centered 90-degrees from the split plane. However, the bore diameter was oversized in the area centered about 20-degrees from the split plane. The bore diameter measured 2.5660 inch; the bore diameter limits were 2.5625 inch to 2.5635 inch.

The crankshaft had fractured through the number 3 cheek, immediately aft of the number 2 main bearing journal. The fracture surfaces exhibited curvilinear crack propagation marks consistent with fatigue. The main bearing surface exhibited circumferential abrasion marks. The main bearing journal diameters measured within the limits for a reground crankshaft, with the exception of the number 2 journal.

The number 1 main bearing shells were deformed; the number 2 main bearing shells were worn, deformed and partially split. The remaining bearings exhibited helical lines that matched the machining lines on the crankcase main bearing saddles. The tin coating on the backside of the bearings had been worn away except around the oil transfer holes. Dimensional inspection of the number 3, 4 and 5 main bearing shells were within limits.

Engine maintenance records indicated that the engine was overhauled in January 2001, at 1,526.5 hours total time. According to the records, an annual inspection was completed on December 10, 2009, at 1,696.7 hours total time, with 170.4 hours since overhaul. The next entry indicated that the engine was removed from the previous airframe "for prop strike on or about 8 – 11." This entry noted the total time as 1,526.5 hours, which was the same as at overhaul about 9 years earlier. However, the time since overhaul was the same as at the December 10th annual inspection.

An entry dated January 10, 2012, noted that the engine had been disassembled due to a propeller strike. At that time, the crankshaft was magnetic particle inspected with negative findings. The crankcase mating surfaces were cut and the bores were resized to the manufacturer's limits. It was subsequently installed on the accident airplane on March 5, 2013. An annual inspection was completed at that time. The recording tachometer time was noted as 216.8 hours. There were no subsequent entries in the either the airframe or engine maintenance logbooks.

The recording tachometer indicated 233.31 hours after recovery of the airplane. Based on the tachometer time noted at the annual inspection, about 16.5 hours had accumulated since the inspection.

Contributing factors

  • cause Recip eng cyl section — Failure
  • cause Fatigue/wear/corrosion
  • cause Incorrect service/maintenance
  • cause Maintenance personnel

Conditions

Weather
VMC, wind 170/06kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.