27 Dec 2013: STINSON 108 1

27 Dec 2013: STINSON 108 1 (N8848K) — Unknown operator

No fatalities • Lodi, CA, United States

Probable cause

The fatigue failure of the crankshaft, which resulted in a total loss of engine power and subsequent forced landing.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHT On December 27, 2013, about 1055 Pacific standard time, a Stinson 108-1 airplane, N8848K, experienced a loss of engine power, and the pilot made a forced landing in an open field near Lodi, California. The owner/pilot operated the airplane under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. The pilot and one passenger were not injured. The airplane sustained substantial damage to its wings and fuselage when it struck a berm and nosed over during the landing roll out. The airplane had departed from the Kingdon Airpark (O20), Lodi, about 1030, and was destined for the Modesto City-County Airport-Harry Sham Field (MOD), Modesto, California. Visual meteorological conditions prevailed for the local area flight, and no flight plan had been filed.

According to a responding deputy from the San Joaquin Sheriff's Department, the pilot reported that shortly after takeoff the engine started to sputter. He turned back to the departure airport, and attempted to restart the engine. After switching fuel tanks, the engine regained full power, then quit completely. The pilot made a forced landing to an open field, which appeared to be free of obstructions. However, during the landing rollout, the airplane struck a berm and nosed over coming to rest inverted.

According to a Federal Aviation Administration (FAA) inspector, who responded to the accident site, the airplane traveled about 400 yards before impacting the ditch. The FAA inspector reported that the pilot had just put in new shoulder harness type seatbelts in the airplane.

The engine was examined at Plain Parts, Pleasant Grove, California, on January 10, 2014. A visual examination revealed that the right side of the engine crankcase near the accessory section had separated. The spark plugs, rocker box covers, and the top of the engine case were removed. The propeller was manually manipulated back and forth; however, full rotation could not be achieved due to damage to the crankshaft, but visible movement of the crankshaft was noted at the rear of the engine. Investigators reported that the crankshaft and cam shaft near the accessory section had broken, and several bearings had been damaged. The crankshaft with a portion of the number one connecting rod, crankshaft main journal bearing, crankshaft connecting rod journal bearing, and a camshaft were shipped to the National Transportation Safety Board (NTSB) metallurgical laboratory in Washington, DC, for further examination.

TEST AND RESEARCH

The NTSB metallurgical laboratory specialist documented the submitted components; the crankshaft was received in two fractured pieces. The fracture occurred through the web between the numbers one and two connecting rod journals. The fracture face was relatively flat with a thumbnail-shaped pattern, which was consistent with fatigue. The fatigue crack initiated at the crankshaft surface, with the primary fatigue crack propagating through 79 percent of the web cross-section. A second fatigue crack had propagated from the opposite side of the fractured crankshaft web and comprised about 5 percent of the web fracture surface. The remaining fracture surface had features consistent with overstress. The specialists reported that the primary fatigue crack propagated from the surface of the crankshaft near the edge of a darkened area on the number two connecting rod journal. According to the specialist, the fracture features of the camshaft were consistent with overstress. The specialists' report is attached to the public docket for this accident.

Maintenance records indicated that during the last annual inspection dated March 12, 2013, the engine had accumulated about 250 hours since the major overhaul.

Contributing factors

  • cause Fatigue/wear/corrosion
  • Contributed to outcome

Conditions

Weather
VMC, vis 4sm

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.