Pilot Debrief

RAYTHEON AIRCRAFT COMPANY A36 near Fallon, NV — 2013-07-10

Final reportWPR13LA321
Sign in to save
Date
2013-07-10
Location
Fallon, NV, USA
Airport
FLX
Aircraft
RAYTHEON AIRCRAFT COMPANY A36
Registration
N517DJ
Category
Airplane
Highest injury
Minor
Fatalities
0
Phase of flight
Initial climb

Probable cause

A fatigue failure of the No. 5 connecting rod, which resulted in a catastrophic engine failure during the initial climb and a subsequent forced landing.

NTSB narrative

The pilot reported that, during climbout, when the airplane was about 1,000 ft above ground level, the engine lost power. The pilot subsequently maneuvered the airplane to attempt to land on the departure runway. The airplane touched down short of the runway in rough, desert terrain, which resulted in substantial damage to the wings, fuselage, and empennage. A postaccident engine examination revealed that the No. 5 connecting rod cap and one of its two bolts had fractured midlength; the opposite bolt was intact with the nut still fastened. Metallurgical examination revealed that the No. 5 connecting rod had failed due to a fatigue crack that had initiated on the outer surface of the nut-facing boss. The crack propagated inward until the final cross-section of the connecting rod yoke failed in overstress, which then catastrophically breeched the left side of the engine case. The fatigue crack did not show any material imperfections; however, the surface finish of the boss where the fatigue crack initiated was consistent with it having been shot peened. Although shot peening is performed to impart compressive stresses to prevent fatigue crack initiation, excessive peening times may sufficiently alter the surface to create stress concentrators. However, the configuration of the fractured rod yoke precluded any accurate surface roughness measurements and, therefore, it could not be determined if improper surface modification had occurred.

Analysis

Primary failure mode
Engine power loss
First missed decision gate
Pilot could have aborted takeoff after engine issues were detected.

NTSB coding

Evidence available

  • FDR / data
  • Photos
  • 10 docket documents
View NTSB final reportView NTSB docket

Docket documents10

Related mishaps