FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Rusts Flying Service Cessna U206G accident

29 Jun 2010 · Iliamna, AK, United States

Cessna U206G · Accident: loss of engine power (total) en route

From King Salmon Airport (AKN) to Lake Hood Seaplane Base (PALH)

Report a problem

Event

NTSB case
ANC10LA056
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
Charter & commuter
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 U206G

Aircraft type
Cessna 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
N4596U
Onboard fatalities
Unknown
Route
From King Salmon Airport (AKN), King Salmon, AKTo Lake Hood Seaplane Base (PALH), Anchorage, AK
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 135: Air Taxi & Commuter
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
Defining eventThe 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
Loss of engine power (total)
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

  • Aircraft › Aircraft power plant

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The float-equipped airplane was in cruise flight on a sightseeing flight when there was a total loss of engine power. After several unsuccessful attempts to restart the engine, the pilot made a forced landing on tundra-covered terrain, and the airplane nosed over. Postaccident disassembly of the engine found that the crankshaft had fractured at the No. 2 journal. Laboratory examination of the crankshaft found "ladder cracking" associated with the journal fracture, which is consistent with a reduced oil flow and overheating of the surface area. At the time of the accident, the engine had 441 hours of operation since major overhaul, which was performed on October 21, 2008.

Probable cause

The total loss of engine power during cruise flight due to a fractured crankshaft.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC10LA056
Event ID
20100630X12540
Case number
ANC10LA056
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2010-06-30.
  • API snapshot SHA-256: eef244f83e76d47fd2a6bed61fc362c5ce90a9f023e534cc253bbff4e9d70082; retrieved 2026-09-15T14:33:42.435Z.