FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC03FA075 · Cessna 206

11 Jul 2003 · English Bay, AK, United States

Cessna 206 · Accident: loss of control in flight during landing

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

Report a problem

Event

NTSB case
ANC03FA075
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
1 · 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 206

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
N505SD
Operator
Unknown
Onboard fatalities
Unknown
Route
From Homer Airport (HOM), Homer, AKTo Nanwalek Airport (KEB), English Bay, 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
Landing · aborted
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
Loss of control in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall
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

  • Pilot in command › Airspeed, not maintained

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

NTSB narrative

The solo certificated commercial pilot of the Title 14, CFR 135, cargo flight was attempting to land the airplane on a 1,850 foot long by 50 foot wide gravel-covered airstrip. Several witnesses reported gusty east-southeast winds, ranging between 25 and 40 knots, blowing directly across the runway. They reported that as the airplane proceeded on its final approach to runway 19, which required a correction for a left crosswind, the airplane "floated down the runway" after passing over the runway threshold, and eventually touched down about mid-field. As it touched down, the airplane bounced twice, which was immediately followed by the sound of full engine power. As it began to climb, the airplane made a sharp right turn to the west, to avoid terrain at the end of the runway. As the westerly turn continued, the airplane climbed to about 150 feet, over the ocean waters to the south of the airport. The witnesses said that the nose of the airplane then pitched up, and the left wing suddenly dropped. The airplane subsequently descended, struck the surface of the ocean, and sank in 30 feet of water about 200 yards from shore. Examination of the airplane revealed no evidence of any preimpact mechanical anomalies. Pilots who regularly use the accident airport stated that they routinely encounter substantial downdrafts on final approach to runway 19 when the prevailing strong east-southeast winds are present. The pilots added that when the east-southeasterly winds are blowing, the approach requires a significant correction for a left crosswind. A pilot who had recently departed from the accident airport, talked with the accident pilot via radio about 45 minutes before the accident. The pilot told the accident pilot, in part: "Be careful. You've got the typical strong southeast winds blowing right across the runway."

Probable cause

The pilot's failure to maintain adequate airspeed during an aborted landing, resulting in an inadvertent stall and subsequent collision with water. Factors were the high velocity crosswind conditions, the pilot's inadequate compensation for the wind conditions, and his delay in aborting the landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC03FA075
Event ID
20030718X01149
Case number
ANC03FA075
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, coordinates. 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: 767667af56d0e481e996337384526a70b8c1d52a9b5b861debceafc7ab8f3cc6; retrieved 2026-09-18T13:02:25.678Z.