ERA16FA023
2015-10-24 · Worcester, Massachusetts, United States · Fatal · 1 aircraft · Status: Completed
Airport ORH
Aircraft involved
Probable cause & findings
A total loss of engine power during the initial climb due to a fatigue failure of the engine's crankshaft. Contributing to the accident was the pilot's failure to maintain control of the airplane, which resulted in an aerodynamic stall.
Factual narrative
HISTORY OF FLIGHTOn October 24, 2015, at 0753 eastern daylight time, a Mooney M20M, N243CW, was substantially damaged when it impacted terrain shortly after taking off from Worcester Regional Airport (ORH), Worcester, Massachusetts. The airline transport pilot was fatally injured. The airplane was registered to and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed, and no flight plan was filed for the local personal flight. There was no radar coverage of the area. Airport security cameras captured partial segments of the flight and showed that the airplane took off from runway 11. One camera showed the airplane in flight, climbing over the intersection of runway 15 about 1,500 ft from the departure end of the 7,000-ft-long takeoff runway. Using the height of the airplane's tail as a reference, the estimated altitude of the airplane was about 80 to 90 ft above the runway surface at that point, climbing in a slight right turn. The airplane then flew out of view and reappeared about 16 seconds later headed in the roughly the opposite direction of takeoff. Based on the approximate height of the control tower, the airplane appeared to be about 200 ft above the ground in a shallow, climbing right turn. The airplane's nose then began dropping, and the right bank angle increased. The airplane continued to turn to the right in an increasingly nose-down attitude as it descended into a stand of trees. PERSONNEL INFORMATIONAccording to Federal Aviation Administration (FAA) records, the pilot held an airline transport pilot certificate with ratings for airplane single- and multi-engine land, as well as a flight engineer certificate. He held an FAA third-class medical certificate, issued July 11, 2014. On the application for this medical certificate, the pilot reported a total flight experience of 7,217 hours. The pilot's logbook was not recovered. AIRCRAFT INFORMATIONThe four-seat, low-wing airplane was manufactured in 1996. It was powered by a 310-horsepower Lycoming TIO-540 engine and equipped with a three-blade, constant-speed McCauley propeller. A review of maintenance records revealed that the airplane's most recent annual inspection was completed on April 14, 2015. At that time, the airframe had accumulated 2,872.8 total flight hours. The engine logbooks could not be located. According to engine manufacturer data, the engine was manufactured in 1993 and returned once to their facility where it was overhauled in December 2001. According to the manufacturer's records, the engine was placed in service on the accident airplane on March 1, 2002. The investigation could not determine if the engine received a subsequent overhaul at another facility. The manufacturer recommended that the engine be overhauled every 2,000 hours or 12 years, whichever occurred first. METEOROLOGICAL INFORMATIONThe 1154 recorded weather observation at ORH included wind from 350° at 8 knots, visibility 10 miles, overcast skies at 2,700 ft, temperature 1°C, dew point -3°C, and altimeter 30.39 inches of mercury. AIRPORT INFORMATIONThe four-seat, low-wing airplane was manufactured in 1996. It was powered by a 310-horsepower Lycoming TIO-540 engine and equipped with a three-blade, constant-speed McCauley propeller. A review of maintenance records revealed that the airplane's most recent annual inspection was completed on April 14, 2015. At that time, the airframe had accumulated 2,872.8 total flight hours. The engine logbooks could not be located. According to engine manufacturer data, the engine was manufactured in 1993 and returned once to their facility where it was overhauled in December 2001. According to the manufacturer's records, the engine was placed in service on the accident airplane on March 1, 2002. The investigation could not determine if the engine received a subsequent overhaul at another facility. The manufacturer recommended that the engine be overhauled every 2,000 hours or 12 years, whichever occurred first. WRECKAGE AND IMPACT INFORMATIONThe accident site was located in flat, wooded terrain, and the wreckage was confined to an area extending about 100 ft. There was no wreckage path; the airplane came almost straight down through the trees. There was no evidence of smoke or fire. The propeller and spinner were found together, separated from the main wreckage, and mostly buried in the ground. The spinner exhibited fore-to-aft crushing, and none of the three propeller blades exhibited evidence typical of engine power at impact. All flight control surfaces were accounted for at the accident site. The left wing was separated from the fuselage about 4 ft from the wing root, and the right wing was mostly still attached. The left horizontal stabilizer was separated from the airplane, and the right horizontal stabilizer remained attached. Flight control continuity was confirmed from the flight control surfaces to the cockpit. The engine remained attached to the airframe and was subsequently removed and taken to a maintenance garage for further examination. The starter ring did not exhibit any evidence of powered rotation at impact. The crankshaft was rotated by hand at the flange; it rotated a few revolutions before it jammed and could not be rotated in either direction. The oil suction screen was removed and found to be contaminated with metal fragments. The accessory case housing was removed, and the No. 5 main bearing was found partially extruded out through the crankshaft gear. Holes were also noted in internal portions of the crankcase halves, and the No. 6 connecting rod was broken. The engine was subsequently disassembled, and the crankshaft was fractured between the No. 5 and No. 6 cheeks. The camshaft was also broken near the crankshaft fracture, and the interiors of the case halves were gouged rotationally, consistent with the damage having occurred while the engine was still operating. The engine was sent to the manufacturer's materials laboratory for further investigation. According to the manufacturer's report, the metallurgical examination revealed that the crankshaft failed in fatigue, with crack initiation from the rear fillet radius of the No. 5 crankpin journal, followed by stable fatigue crack growth through nearly the entire section thickness of the No. 8 cheek. Fracture surface markings indicated a likelihood of multiple fatigue crack initiation sites. Multiple origins typically indicate high stress conditions; however, the majority of crack growth through the No. 8 cheek occurred under high-cycle fatigue loading, consistent with relatively lower nominal stress conditions. This cracking pattern suggested that overstress conditions of relatively short duration acted to initiate the fatigue cracks. The report stated that the root cause for this overstress was not determined, but it was not related to any material non-conformance. The crankshaft conformed to engineering drawing requirements for alloy chemistry, case hardness, case depth, and case and core microstructure. It was slightly below the core hardness specification, but this was not considered relevant for this fracture. Charpy impact test bars cut from the undamaged regions of the No. 8 cheek were free of any honeycomb or microcrack features, indicating the steel had not been exposed to excessively high temperatures during billet forging or crankshaft forging. The crankshaft journal diameters conformed to engineering specifications. The crankshaft journals also conformed for roundness, except for the No. 1 and No. 3 crankpin journals, which exceeded the specification tolerance for out-of-round; however, these crankpin journals were undamaged. The JPI 700 engine monitor was sent to the NTSB Records Laboratory for download. Due to internal buffering of the data before being written to non-volatile memory, the final portion of the flight was not recorded. The data that was captured, was from the time of the master avionics switch was turned and, after engine start when the oil, cylinder head, turbine inlet, and exhaust gas temperatures were just starting to climb during warm-up. Then the data showed the temperatures climbing, representing the take-off, and an initial power reduction, before ending abruptly. MEDICAL AND PATHOLOGICAL INFORMATIONThe Office of the Chief Medical Examiner, Commonwealth of Massachusetts, performed an autopsy on the pilot. The cause of death was described as blunt injury. The autopsy also identified mild, focally moderate, atherosclerosis of the coronary arteries, with approximately 40% stenosis of the left anterior descending coronary artery, less than 10% stenosis of the right coronary artery, and no significant stenosis of the left circumflex coronary artery. The FAA Bioaeronautical Sciences Research Laboratory, Oklahoma City, Oklahoma, performed toxicology testing on specimens from the pilot. The toxicology tests detected no carbon monoxide in blood and no cyanide in blood. The test did detect losartan in the liver and blood. Losartan is approved for use by the FAA and is not considered impairing. The airline transport pilot was departing on a personal local flight in his airplane when the airplane's engine lost total power. Review of airport security video revealed that, after takeoff, the airplane reached an altitude of about 200 ft before turning right and reversing direction. The airplane subsequently stalled, rolled to the right, and descended uncontrolled into trees. It is likely that the pilot reversed direction to return to the airport but failed to maintain adequate airspeed while maneuvering, which resulted in the airplane exceeding its critical angle of attack, an aerodynamic stall, and loss of control. Examination of the engine revealed that the crankshaft had failed due to fatigue cracking between the No. 5 and No. 6 cheeks. The cracking pattern suggested that numerous overstress conditions of relatively short durations acted to initiate the fatigue cracks, but the cause for this overstress could not be determined. 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 engine power section-Failure - C
- F Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Angle of attack-Not attained/maintained - F
- F Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - F
Verbatim from NTSB's published report. Source file
NTSB_2015_ERA16FA023.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, loss of control, 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.
- Semantic Scholar 2016 · Article (Interacción) Trajectory Recovery System: Angle of Attack Guidance for Inflight Loss of Control
This paper describes the design and development of an ecological display to aid pilots in the recovery of an In-Flight Loss of Control event due to a Stall (ILOC-S).
- NTSB Aircraft Accident Reports 2010 · Accident report Loss of Control on Approach — Colgan Air Flight 3407
Colgan Air 3407 / Continental Connection (Q400) Buffalo NY, February 12, 2009 — 50 fatalities. Definitive investigation of the Colgan 3407 stall-stick-pusher crash on approach to Buffalo.
- NTSB Aircraft Accident Reports 2002 · Accident report Loss of Control and Impact with Pacific Ocean — Alaska 261
Alaska Airlines Flight 261 (MD-83) Pacific Ocean, January 31, 2000 — 88 fatalities. Definitive investigation of the Alaska 261 pitch-runaway-and-loss-of-control crash.
- 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 …