CEN13LA229
2013-04-15 · Warren, Arkansas, United States · Minor · 1 aircraft · Status: Completed
Airport 3M9
Aircraft involved
Probable cause & findings
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.
Factual 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. The pilot reported that the engine lost power during the initial climb. He then established a glide in an attempt to return to the airport; however, due to "strong" wind, the airplane landed "abruptly short of the runway." A postaccident engine examination revealed that the crankshaft had fractured due to fatigue through the No. 3 cheek immediately aft of the No. 2 main bearing journal. Portions of the saddle bore diameter at the nose of the crankshaft were oversized. The crankcase No. 2 main bearing saddle exhibited longitudinal deformation adjacent to the bore with fretting and galling on the saddle landings. The No. 1 main bearing shells were deformed; the No. 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 had been worn away except around the oil transfer holes. The appearance of the main bearing shells was consistent with the bearings shifting during operation due to insufficient crush, which was likely caused by the oversized main saddle bore diameters. Maintenance records indicated that the engine was disassembled about 15 months before the accident due to a propeller strike. At that time, maintenance personnel cut the crankcase mating surfaces and resized the saddle bores. The engine had accumulated about 16.5 hours since the engine was reinstalled. It is likely that maintenance personnel improperly resized the saddle bores during the engine maintenance. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Aircraft-Aircraft power plant-Engine (reciprocating)-Recip eng cyl section-Failure - C
- C Aircraft-Aircraft power plant-Engine (reciprocating)-Recip eng cyl section-Fatigue/wear/corrosion - C
- C Aircraft-Aircraft power plant-Engine (reciprocating)-Recip eng cyl section-Incorrect service/maintenance - C
- C Personnel issues-Task performance-Maintenance-(general)-Maintenance personnel - C
Verbatim from NTSB's published report. Source file
NTSB_2013_CEN13LA229.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (stall, maintenance). All research papers
- Embry-Riddle Scholarly Commons 2023 · Conference paper The Value of Strong Partnerships to Build a Successful Aviation Maintenance Career Pathway Program for Transitioning Military Service Members
The aerospace industry is competing with other industries for a qualified workforce, and many of those competing industries are investing heavily in creating workforce development pipelines.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA) From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- NASA NTRS 2026 · Conference Paper Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Semantic Scholar 2026 · Article (Reliability Engineering & System Safety) Understanding human error in military aviation maintenance: The role of Performance shaping factors, cognitive workload and error orientation
- Semantic Scholar 2025 · Article (Applied Sciences) Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Semantic Scholar 2024 · Article (Defence Science Journal) Modelling of Human Factors in Aviation Maintenance Using HFACS ME Human Factors Analysis and Classification System Maintenance Extension and Bayesian Network
Aircraft maintenance is a complex task involving a skilled human workforce, spare parts, and various other resources. Human factors are an inherent element of the human workforce.