Casualties unknown

Engine Crankshaft Failure Leads to Forced Landing in Swamp (N8189T)

Minneapolis, MN, US

On June 8, 2000, a Piper PA-28-161 (registration N8189T) was involved in an aviation accident near Minneapolis, MN. Investigators recorded the probable cause as: Fatigue cracking of the engine crankshaft, originating at the aft radius of the third main journal, leading to crankshaft failure and subsequent engine failure. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive; 4 related events involving the same aircraft type or operator are linked below.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 2026-07-04Data APIEditorial standards

During initial climb, an engine crankshaft failed, causing an engine failure. The flight instructor executed a forced landing into a swamp. Investigation revealed fatigue cracking as the cause.

Introduction

An accident occurred during the initial climb phase of a flight when the engine experienced a complete failure due to a crankshaft fracture. The flight instructor, who was at the controls, managed the emergency by performing a forced landing into a swamp.

Accident Details

The flight was in the initial climb after takeoff when the engine lost power. The flight instructor took control and executed a forced landing, which ended in a swampy area. The aircraft sustained damage from the landing.

Investigation Findings

Post-accident examination of the engine revealed that the crankshaft had fractured between the number three bearing journal and the number three connecting rod journal. The National Transportation Safety Board Materials Laboratory Factual Report provided a detailed analysis of the fracture surface. The report described the forward piece of the crankshaft as having a "relatively smooth" surface with "curving crack arrest lines," which are characteristic of fatigue. The fatigue cracking originated at the surface of the aft radius of the third main journal and propagated through more than 80 percent of the crankshaft cross-section before final separation occurred.

Further examination of the bearings showed that the inner and outer diameter surfaces of the number three main bearing halves were circumferentially rubbed. One edge of each of these bearing halves was worn in the approximate shape of the journal radius, and the antirotation tabs were worn away from the outside diameter surface. The number four main bearing halves were deformed, with gouging on the inner diameter surface. Slight circumferential rubbing marks were observed on the inner diameter surfaces of the number one and two main bearing halves. No evidence of heat tinting was noted on any of the bearing halves.

Probable Cause

Fatigue cracking of the engine crankshaft, originating at the aft radius of the third main journal, leading to crankshaft failure and subsequent engine failure.

All Piper PA-28 Cherokee accidents →

Frequently asked questions

What happened in the 8 Jun 2000 Piper PA-28-161 accident near Minneapolis, MN?

During initial climb, an engine crankshaft failed, causing an engine failure. The flight instructor executed a forced landing into a swamp. Investigation revealed fatigue cracking as the cause.

What aircraft was involved and where did it happen?

The accident on 8 Jun 2000 involved a Piper PA-28-161, registration N8189T, at Minneapolis, MN.

What was the probable cause of the accident?

Fatigue cracking of the engine crankshaft, originating at the aft radius of the third main journal, leading to crankshaft failure and subsequent engine failure.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20001212X21174. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.