LAX93LA356

NTSB accident investigation · Cessna 182A · Oracle, AZ · September 17, 1993

Accident · Serious injuriesLimited investigationFinal report
Date
September 17, 1993, 10:05 local (17:05 UTC)
Place
Oracle, AZ
Injuries
1 serious, 2 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N6336BCessna 182A
Weather
Visual (VMC) · Day
Status
Completed · report June 24, 1994
Report
Approved by Office Director
FAA report
19930917034939A
Case key
28478

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

Failure of the crankshaft due to fatigue.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Loss of engine power(total) - mech failure/malfCruise
Engine assembly,crankshaft - fatigueCause
Forced landingDescent - emergency
In flight collision with objectLanding
Object - tree(s)Factor

Analysis

During a local VFR flight, the engine lost power. The pilot tried to land on an asphalt surfaced road, but was unable to reach the roadway. During the forced landing, the airplane collided with trees on uneven desert terrain and was damaged. An examination of the engine revealed that the crankshaft had failed forward of the number one journal. The fractured surfaces displayed beach marks consistent with fatigue. There was no evidence that the engine had sustained any high temperature distress or lack of lubrication. The engine had accrued about 4434 hours since new and about 1110 hours since it was overhauled on 12/10/87.

Factual narrative

On September 17, 1993, at 1005 hours mountain standard time, a Cessna 182A, N6336B, collided with some trees during an emergency landing near Oracle Junction, Arizona. The emergency landing was precipitated by a total loss of engine power during cruise flight. The pilot was conducting a local visual flight rules personal flight. The airplane, operated by D. Genzman, dba Snoopy's Flight School, Tucson, Arizona, sustained substantial damage. The certificated private pilot and one passenger were not injured; one passenger sustained serious injuries and was subsequently hospitalized. Visual meteorological conditions prevailed. The flight originated at Ryan Field, Tucson, Arizona, at 0935.

Mr. Dean Hennies, Aviation Safety Inspector [Airworthiness], Scottsdale [Arizona] Flight Standards District Office, examined the engine on October 6, 1993. The examination revealed that the crankshaft broke forward on the number one (1) connecting rod journal. The fractured surfaces displayed beach marks consistent with fatigue. There was no evidence that the engine sustained any high temperature distress. The engine displayed normal lubrication signatures.

The maintenance records examination revealed that the engine had accrued about 4,434 hours since new and about 1,110 hours since major overhaul. The major overhaul was accomplished on December 10, 1987.

Aircraft

Registration
N6336B
Reported as
Cessna 182A
Category
Airplane
Serial number
34236
Airframe hours
4,433
Engine
Continental O-470, 230 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Registered owner
Dennis W. Genzman
Airworthiness certificate
Standard, Normal
Last inspection
Annual · August 16, 1993 · 8 hours before
Departed
RYN · Ryan Field, AZ
Destination
RYN

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
45
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Valid Medical--w/ waivers/lim
Seat
Left
Flight hours
133 total · 22 in this make and model · 78 as pilot in command · 8 in the last 90 days · 3 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
130° at 12 knots
Visibility
40 statute miles
Lowest ceiling
None
Temperature
90 °F
Altimeter
30.00 inHg

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.