FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Smokey Bay Air Cessna U206G accident

15 Dec 2011 · Nanwalek, AK, United States

Cessna U206G · Accident: loss of control in flight during initial climb

From Nanwalek Airport (KEB) to Homer Airport (PAHO)

Report a problem

Event

NTSB case
ANC12FA014
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
N252AL
Onboard fatalities
Unknown
Route
From Nanwalek Airport (KEB), Nanwalek, AKTo Homer Airport (PAHO), Homer, 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 control in flight
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 oper/perf/capability
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The commercial pilot was taking off on the third leg of a scheduled flight returning to the airplane’s base of operation. Earlier in the day, the weather in the area was not suitable for flight operations, but the pilot, along with another company pilot, performed the company risk assessment and decided that, under the current conditions, flights could depart. The pilot reported that the first two legs were uneventful. However, he noted that, upon landing at the end of the second leg, about 3 inches of slush covered the runway, with as much as 6 inches in some areas, and that the wind was from the east at 12 to 15 knots.

After loading passengers, the pilot decided to taxi from the north parking ramp to the opposite end of the runway for a northerly departure. The pilot and witnesses stated that the airplane’s takeoff performance was degraded due to the runway contamination, but the airplane was still able to lift off just past the midfield point. The pilot stated that after the airplane lifted off in a nose-high attitude, he immediately started a shallow left turn to avoid the rising terrain at the north end of the runway. He said that after the airplane cleared a retaining wall on the west side of the runway, it encountered a downdraft, and the pilot was unable to maintain a climb. The airplane impacted the ocean about 100 yards offshore.

There is no official weather reporting at the airport. About 35 minutes before the accident, the nearest official weather reporting station, located 9 nautical miles northeast of the airport, reported wind from 170 degrees at 3 knots. About 10 minutes after the accident, it reported wind from 170 degrees at 10 knots, gusting to 15 knots. The airport is tightly constrained on both sides by terrain and water, and the runway condition is difficult to maintain due to sea erosion and lack of suitable maintenance equipment. According to the airport manager, there is a contract maintenance provider in the village, and, on the morning of the accident, it was determined that runway conditions did not require maintenance. The contractor stated that the weather was very dynamic that day; he asked the pilot of the first airplane that landed if any maintenance was required on the runway and was told that the runway was fine. However, given the contamination on the runway, the accident pilot likely lifted off farther down the runway than normal. The airplane’s attitude and slow airspeed, combined with the unfavorable wind conditions he encountered after he executed the shallow turn, likely resulted in an aerodynamic stall.

A review of the operator’s flight risk assessment form showed that, for the conditions during the accident flight, the pilot and another company pilot should have assigned three of the five risk areas a value that requires additional management approval before flights could be released. Instead, they agreed that conditions were appropriate for flight and were allowed to exercise operational control to release the flights for departure, which placed the flight at risk for an accident.

Probable cause

The pilot’s decision to takeoff from a contaminated runway with unfavorable wind conditions, and his failure to maintain airspeed during the initial climb, which resulted in an aerodynamic stall. Contributing to the accident was the operator’s inadequate procedures for operational control and dispatch.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC12FA014
Event ID
20111216X94904
Case number
ANC12FA014
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: 8263231438b8b4027a07dd3e1515924c896bd408feee85f5618f67bd36b216d1; retrieved 2026-09-15T17:00:42.096Z.