FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC93LA174 · Cessna 206

11 Sept 1993 · SWIKSHAK BAY, AK, United States

Cessna 206 · Accident: in flight collision with terrain/water during initial climb

From an unrecorded airport to PORT ALSWORTH, AK

Report a problem

Event

NTSB case
ANC93LA174
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
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
General aviation
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
N9707Z
Onboard fatalities
Unknown
Route
From not recordedTo PORT ALSWORTH, 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 91: General Aviation
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
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
In flight collision with terrain/water
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/mush
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 › Proper climb rate, not attained
  • Pilot in command › Stall/mush, encountered

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

NTSB narrative

THE PILOT-IN-COMMAND STATED TWO OTHER AIRPLANES TOOK OFF FROM THE SLOUGH JUST BEFORE HIM. HE WAS THE LAST TO DEPART AND MADE HIS TAKEOFF RUN DOWNSTREAM ON THE SLOUGH. HE LIFTED OFF AT 50 TO 55 KNOTS AND THE AIRPLANE BEGAN TO SETTLE JUST AFTER LIFT OFF. THE PILOT STATED HE KNEW THE WATER WAS VERY SHALLOW AND TRIED TO MAINTAIN FLIGHT UNTIL REACHING DEEPER WATER. THE AIRPLANE SETTLED ONTO THE SLOUGH AND THE FLOATS STRUCK A MUD BAR AND THE AIRPLANE NOSED OVER. THE WIND WAS CALM. THE PILOT STATED THERE WERE NO MECHANICAL IRREGULARITIES DURING THE TAKEOFF. THIS WAS A BUSINESS FLIGHT CONDUCTED UNDER 14CFR91 BY A FISHING LODGE.

Probable cause

THE PILOT-IN-COMMAND'S FAILURE TO ATTAIN A PROPER CLIMB RATE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC93LA174
Event ID
20001211X13289
Case number
ANC93LA174
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1993-09-12.
  • API snapshot SHA-256: 5cf258f6a645485d38abe15a143d58eec14503f26c5448e26e50ac5a26699fa0; retrieved 2026-09-21T00:23:24.969Z.