FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI04LA181 · Beech BE-N35

9 Jul 2004 · Austin, MN, United States

Beech BE-N35 · Accident: total loss of engine power (mechanical failure) en route

From Ankeny Regional Airport (IKV) to Chetek Municipal Southworth Airport (Y23)

Report a problem

Event

NTSB case
CHI04LA181
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Beech BE-N35

Aircraft type
Beechcraft BE-N35
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N80HL
Operator
Justin Graff
Onboard fatalities
Unknown
Route
From Ankeny Regional Airport (IKV), Ankeny, IATo Chetek Municipal Southworth Airport (Y23), Chetek, WI
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Total loss of engine power (mechanical failure)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Engine assembly, connecting rod › Failure
  • Engine assembly, connecting rod › Overload
  • Engine assembly, crankcase › Fractured
  • Engine assembly, other › Failure
  • Engine assembly, other › Fatigue
  • Lubricating system › Starvation/exhaustion

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The airplane sustained substantial damage during a forced landing following a loss of engine power in cruise flight. The pilot reported the airplane had been operating properly at 5,000 feet mean seal level (msl) until the propeller started to overspeed between 2,950 - 3,025 rpm and the overspeed annunciator light illuminated. He attempted to slow the propeller with the propeller pitch control but without effect. The oil pressure gauge read zero. He reduced the throttle to about 15 inches of manifold pressure to slow the engine to 2,500 rpm. About 30 seconds to 1 minute later, the airplane began to shake and vibrate violently, white smoke filled the cabin, and oil covered the windshield. The pilot reported that he decided to execute a forced landing to one of the flat farm fields. He lowered the gear and established about a 90 knot descent. He shut down the engine by pulling the mixture to idle cutoff. He slipped the airplane to lose altitude prior to landing. The airplane skidded in the mud for about 80 yards, and the landing gear retracted back into the wheel wells during landing roll out. The on-site inspection of the engine revealed a hole in the right side of the engine case. The engine teardown revealed that number 1 cylinder piston pin plug was fractured in two pieces. The smaller of the two pieces was deformed with substantial material loss with the fracture surface being obliterated. The number 4 cylinder piston pin plug rotated within the piston pin. Metal contamination was found in the oil pressure relief valve and valve seat. There was a hole in the engine case next to the number 5 cylinder. The number 5 connecting rod was broken and the end of the rod was "hammered" and blackened. The number 5 rod bearing was scored and blackened. The number 1, 4, and 6 rod bearings exhibited melting and protruding. All main bearings were scored. The oil pump gears turned freely, and the sides of the pump walls were scored. The number 1 and number 4 cylinder piston pins and piston pin plugs were sent to the National Transportation Safety Board's Materials Laboratory for examination. The examination revealed that the number 1 cylinder piston pin plug had a fracture surface with visible crack arrest lines, features consistent with fatigue. Black deposits were observed on the head of the larger piece of the number 1 piston pin plug and on the ends of the number 4 cylinder piston pin plugs, although the deposits were less thick than on the number 1 piston pin plug. An impression was observed on the larger piston pin plug piece in the bevel between the head and the shank. The impression was located on the same side of the piston pin plug as the fatigue origin. The surface of the impression was covered with black deposits. The pilot reported the engine had 1,000 hours of operation since the last overhaul, and 47.7 hours of operation since the last inspection. The engine did not have an oil filter installed on it.

Probable cause

The loss of engine power due to the fatigue fracture of the piston pin plug that lead to engine oil starvation/exhaustion and the subsequent overload fracture of the piston rod and crankcase.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI04LA181
Event ID
20040715X00982
Case number
CHI04LA181
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 05ce511ec9bbda5596d3918042e51c536e1a91e152a27c0d0fcc2cb77a505f94; retrieved 2026-09-22T07:08:04.289Z.