FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC82DA042 · Cessna U206

27 May 1982 · OUZINKIE, AK, United States

Cessna U206 · Accident: undershoot on approach

From Kodiak /Lilly Lake/ Seaplane Base (9Z3) to Q59 · FREMONOT, CA

Report a problem

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

Event

NTSB case
ANC82DA042
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
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 U206

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
N4877X
Operator
Robert F. Stanford · private individual
Onboard fatalities
Unknown
Route Narrative disagrees
From Kodiak /Lilly Lake/ Seaplane Base (9Z3), Kodiak, AKTo Q59 · FREMONOT, CA
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
Approach · VFR pattern final
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
Undershoot
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, misjudged
  • Pilot in command › Altitude, misjudged
  • Pilot in command › Distance, misjudged

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

NTSB narrative

DURING ARRIVAL, THE PILOT MADE HIS LANDING APPROACH OVER THE VILLAGE SO AS TO LAND THE FLOAT PLANE ON THE BAY AND INTO A 30 KNOT HEAD WIND. WHILE ON FINAL APPROACH, THE AIRCRAFT'S RATE OF DESCENT INCREASED. THE PILOT ADDED FULL POWER AND STARTED TO RAISE THE NOSE, BUT THE PLANE STRUCK THE BEACH IN ABOUT SIX INCHES OF WATER. THE PLANE BOUNCED INTO THE BAY AND REMAINED AFLOAT, BUT BOTH WINGS AND BOTH FLOATS WERE DAMAGED. THE WATER RUDDERS WERE UNUSABLE, BUT THE PLANE WAS TAXIED TO A BEACH BY SAILING AND USING POWER. THE PILOT BELIEVED HE HAD ENCOUNTERED WIND SHEAR DURING THE LANDING APPROACH; HOWEVER, WIND SHEAR WAS NOT VERIFIED. THE AIRCRAFT'S CENTER-OR-GRAVITY WAS NEAR THE FORWARD LIMIT.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record ANC82DA042
Event ID
20020917X02638
Case number
ANC82DA042
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: c73a26966b1378a555e91d1c8cdb06e0a4232200f16ed10a6e11c89845babc97; retrieved 2026-09-18T21:09:38.348Z.