Unlock $500M in Quoting Opportunity with Automation!
Trending
Categories
Crankshaft Fatigue Causes Emergency Landing

Crankshaft Fatigue Forces Emergency Landing Near Bellevue
A Cirrus SR22T aircraft was compelled to execute an emergency landing near Bellevue, Washington, following a total engine failure caused by crankshaft fatigue, according to a preliminary report from the National Transportation Safety Board (NTSB).
Incident Overview
The event took place shortly after the aircraft departed from Runway 34 at Renton Municipal Airport (KRNT). The flight instructor and the pilot under instruction reported that the plane had stabilized at approximately 2,500 feet mean sea level when the engine’s revolutions per minute (RPM) surged erratically. This was immediately followed by a loud bang and a complete loss of engine power. Unable to restart the engine, the crew deployed the Cirrus Airframe Parachute System (CAPS), enabling a controlled descent into a wooded wetland area near a residential neighborhood.
The aircraft came to rest upright, about four miles northeast of the airport, in a nose-low position. Both pilots survived without injury, and there were no immediate reports of damage or casualties on the ground.
Investigation and Findings
Initial site examination revealed damage to the airplane’s nose landing gear fairing, with both wings and flaps removed during recovery operations. The engine, a Continental Motors TSIO-550-K1B, remained attached to the fuselage, with all cylinders and accessories intact. Investigators confirmed control continuity from the cockpit to the fuel servo and found no external mechanical damage to the engine crankcase.
Subsequent detailed analysis conducted at Continental Motors facilities and the NTSB Materials Laboratory uncovered significant internal damage. The crankshaft was fractured near the No. 2 main bearing and No. 3 connecting rod journal. Further examination revealed fatigue cracks had developed at multiple points along the crankshaft, culminating in its failure. Maintenance records showed the engine had undergone an overhaul in November 2019 and was installed in April 2020, accumulating approximately 680 flight hours since the overhaul. No recent maintenance had been performed on the crankshaft prior to the incident.
The NTSB identified the probable cause as a total loss of engine power resulting from a fatigue fracture of the crankshaft.
Broader Implications
Beyond the technical aspects, the emergency landing highlights operational challenges within the aviation industry. The incident likely caused immediate disruptions, including flight rerouting, passenger accommodations, and temporary airport closures. Financial repercussions for the operator may encompass costs related to fuel, landing fees, and passenger compensation. Moreover, the event has the potential to influence consumer confidence, as travelers may raise concerns regarding aircraft maintenance and safety protocols.
Competitors within the aviation sector are expected to observe the situation closely, potentially adjusting pricing strategies or market positioning should the incident indicate broader maintenance issues. The airline’s response, particularly its transparency and management of customer concerns, will be pivotal in preserving passenger trust and loyalty.
NTSB Identification: 193887

IBM and Adobe Collaborate on AI Solutions for Airlines and Healthcare

LEAP Engine Deliveries Rise 63% to 520 in First Quarter 2026

AerFin Introduces V2500 Engine Support at MRO Americas

AAR links airlines to 5,000 suppliers with new AI parts-buying tool

Ethiopian Airlines Expands 787 Fleet to 46 with New Order

Drake Air Expands Thermal MRO Services for A220 Aircraft

Can SAF Technology Reduce Aviation Emissions?

Divya Manchanda Discusses ePlane’s Vision for Air Taxis and Drones

Pem-Air Expands V2500 Maintenance Capabilities
