FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC89FA100 · Cessna U-206G

21 Jun 1989 · Anchorage, AK, United States

U.S. Air Force Cessna U-206G · Accident: loss of control in flight during initial climb

Report a problem

Event

NTSB case
ANC89FA100
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
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 U-206G

Aircraft type
Cessna U-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
N8773Q
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
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
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

  • Miscellaneous eqpt/furnishings › Not removed
  • Pilot in command › Aircraft preflight, improper
  • Pilot in command › Checklist, not followed
  • Pilot in command › Climb, not attained
  • Pilot in command › Tie down, not corrected

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

NTSB narrative

THE ACCIDENT REPORT SUBMITTED BY THE FLYING CLUB CHIEF INDICATED THAT THE PILOT DID NOT RELEASE THE TAIL TIEDOWN DURING HIS PREFLIGHT INSPECTION. IT WAS ATTACHED TO A 4X4 POST IN A CONCRETE WEIGHT. DURING THE ATTEMPTED TAKEOFF THE AIRPLANE WOULD NOT GET ON STEP. THE TAKEOFF WAS ABORTED. A SECOND TAKEOFF WAS ATTEMPTED FROM THE MIDDLE OF THE LAKE. DURING THE TAKEOFF THE NOSE BEGAN TO PITCH UP APPROACHING A STALL. THE PILOT PUSHED THE YOKE FORWARD & THE AIRPLANE SETTLED BACK ONTO THE WATER JUST PRIOR TO IMPACT WITH THE LAKE'S DEPARTURE END SHORELINE.

Probable cause

THE FAILURE OF THE PILOT TO CONDUCT A PROPER PRE-FLIGHT INSPECTION AND REMOVE THE TAIL MOORING FROM THE FLOAT PLANE. CONTRIBUTING TO THE ACCIDENT WAS THE PILOT'S OVER CONFIDENCE IN HIS PERSONAL ABILITY.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC89FA100
Event ID
20001213X28452
Case number
ANC89FA100
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: 4baa8c8c5ec1ec2af1eded73e2c264e2111b7418938d10b8eb948fb8d456d13b; retrieved 2026-09-23T07:29:16.483Z.