On September 28, 2000, a Cessna 172K (registration N84034) was involved in an aviation accident near Burns, OR. No fatalities were reported. Investigators recorded the probable cause as: Fatigue crack originating from foreign object damage on the leading edge, which propagated through two-thirds of the chord, resulting in blade separation. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive.
During a climb in turbulent conditions, the outboard five inches of a propeller blade separated due to a fatigue crack. The pilot shut down the engine and made an emergency landing. Investigation traced the crack to foreign object damage.
Incident Summary
During a climb in turbulent conditions, the most-outboard five inches of one propeller blade separated from the aircraft. The resulting violent vibration prompted the pilot to shut down the engine and execute an emergency landing in an open field. No further injuries or damage were reported beyond the blade separation itself.
Examination Findings
An examination conducted at the NTSB materials laboratory determined that the blade section had separated due to a fatigue crack that had propagated through two-thirds of the chord of the blade. The origin of the fatigue crack was identified as an area on the leading edge where the blade had been damaged by impact with a foreign object. The fatigue crack likely grew over time until the remaining blade material could no longer withstand the operational loads, leading to the separation.
The aircraft was landed safely without further incident. The investigation did not specify the type of aircraft, engine, or other operational details beyond the conditions described.
Probable cause
Fatigue crack originating from foreign object damage on the leading edge, which propagated through two-thirds of the chord, resulting in blade separation.
What happened in the 28 Sept 2000 Cessna 172K accident near Burns, OR?
During a climb in turbulent conditions, the outboard five inches of a propeller blade separated due to a fatigue crack. The pilot shut down the engine and made an emergency landing. Investigation traced the crack to foreign object damage.
Were there any fatalities in the 28 Sept 2000 Cessna 172K accident?
No fatalities were recorded in this accident.
What aircraft was involved and where did it happen?
The accident on 28 Sept 2000 involved a Cessna 172K, registration N84034, at Burns, OR.
What was the probable cause of the accident?
Fatigue crack originating from foreign object damage on the leading edge, which propagated through two-thirds of the chord, resulting in blade separation.
A SkyWalk Join't 3 paraglider crashed into the ground near Las Vizcachas, Chile, on September 1, 2024. The pilot and passenger sustained serious spinal…
PARAPENTE (ULTRALIVIANO NO MOTORIZADO)·2024-09-01DGAC Chile
A Cessna 172N struck electrical cables while on final approach to land at Aucó Aerodrome in Chile. The pilot was uninjured, but the aircraft sustained damage…
A Bombardier DHC-8-402 suffered a tail strike during landing at Puerto Williams on September 9, 2024. All 76 occupants were unharmed, but the aircraft…
A MYD JS-MD 3 glider veered off the runway and struck a wall at Vitacura Aerodrome on January 6, 2025. The pilot was uninjured, but the aircraft sustained…
A recreational paraglider flight in Puchuncaví, Chile, ended with the pilot sustaining serious injuries after a rapid descent and impact with a hillside on…
PARAPENTE (ULTRALIVIANO NO MOTORIZADO)·2025-03-29DGAC Chile
A Tecnam P2006T landed on its belly at an aerodrome in Poland after the crew failed to confirm landing gear deployment. The incident resulted in no injuries…