FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX91LA048 · Cessna T-206

2 Dec 1990 · Tonto Basin, AZ, United States

Cessna T-206 · Accident: total loss of engine power (mechanical failure) en route

From Phoenix Sky Harbor International Airport (PHX) to Show Low Regional Airport (SOW)

Report a problem

Event

NTSB case
LAX91LA048
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
0
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

Cessna T-206

Aircraft type
Cessna T-206
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
N8655Z
Operator
Pagani, Ronald · private individual
Onboard fatalities
Unknown
Route
From Phoenix Sky Harbor International Airport (PHX), Phoenix, AZTo Show Low Regional Airport (SOW), Show Low, AZ
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 bolt › Failure, total

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

NTSB narrative

WHILE FLYING A 9,500 FT MSL THE PILOT, ALSO THE REGISTERED OWNER, OBSERVED AN INCREASE IN OIL TEMPERATURE FOLLOWED BY A DECREASE IN OIL PRESSURE. MOMENTS LATER OIL SMOKE EMANATED FROM THE ENGINE COMPARTMENT FOLLOWED BY A TOTAL LOSS OF ENGINE POWER. THE SUN BLINDED THE PILOT WHILE ON APPROACH TO A DIRT STRIP AND WHEN HE WAS ABLE TO SEE THE DIRT STRIP THE AIRPLANE'S ALTITUDE WAS INSUFFICIENT TO NEGOTIATE A LANDING ON THE STRIP. THE PLT ELECTED TO LAND IN AN ADJACENT OPEN AREA. DURING THE LANDING ROLL-OUT THE AIRPLANE'S LEFT WING STRUCK A BARN. ENGINE EXAM DSCLSD THE NO. 3 CONNECTING ROD FAILED AND ITS ASSOCIATED BEARING EXHIBITED EXTREME HIGH TEMP DISTRESS. DURING THE LAST ANNUAL INSP THE OIL ANALYSIS SHOWED HIGH CONCERTRATION OF IRON AND STEEL.

Probable cause

THE FAILURE OF A CONNECTING ROD IN THE ENGINE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX91LA048
Event ID
20001212X24766
Case number
LAX91LA048
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: 7f65f0c3bf7c0f5226f0f85298c5e6089c231a7447e481c6bbed62f5293ae1bf; retrieved 2026-09-23T05:06:26.178Z.