FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Alaska Skyways Cessna U206G accident

15 Sept 2011 · Beluga, AK, United States Possible conflict

Cessna U206G · Accident: loss of engine power (total) during initial climb

From Beluga, AK to Lake Hood Seaplane Base (PALH)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ANC11LA103
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
N1779R
Onboard fatalities
Unknown
Route
From Beluga, 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
Initial climb
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

Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.

NTSB narrative

The pilot of the on-demand passenger flight was taking off from a lake in a float-equipped, single-engine airplane. During takeoff/initial climb, the engine lost all power. There was no suitable place to land, and the pilot concentrated on landing the airplane straight ahead, as slow as possible. During the subsequent emergency landing, the airplane collided with terrain in a boggy area, sustaining substantial damage to the fuselage and right wing. The pilot said that, prior to takeoff, the airplane had been in a left step turn and that the left fuel tank had been selected for the takeoff. After the airplane was recovered, with the engine still attached to the fuselage, a new propeller installed, and a clean fuel supply provided, the engine was test run. The engine was run at varying rpms, and a magneto check was completed. No engine anomalies were found.

Probable cause

The total loss of engine power for an undetermined reason.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC11LA103
Event ID
20110915X73207
Case number
ANC11LA103
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: 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: 3723578007a52389fdb89c68855f44218ac68038a65c7956c9786c43325e3bea; retrieved 2026-09-15T16:44:32.252Z.