FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC16LA038 · Cessna 206

3 Jul 2016 · Halibut Cove, AK, United States

Cessna 206 · Accident: collision during takeoff/landing

From Homer Airport (HOM) to Halibut Cove, AK

Report a problem

Event

NTSB case
ANC16LA038
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
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
N6251K
Operator
Unknown
Onboard fatalities
Unknown
Route
From Homer Airport (HOM), Homer, AKTo Halibut Cove, AK
Aircraft age
About 8 years (built 2008)
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
Landing · aborted after touchdown
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
Collision during takeoff/landing
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
Tree(s)
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

  • Environmental issues › Physical environment
  • Personnel issues › Task performance

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

NTSB narrative

The private pilot was landing an amphibious airplane in the ocean waters of an inland cove. Photographs of the accident sequence showed the water conditions as relatively calm and glassy. The pilot reported that the airplane touched down faster than anticipated and before her intended touchdown point, which subsequently caused the airplane to bounce back into the air. Instead of continuing the landing, she attempted a go-around. As the airplane climbed in a nose-high attitude, she was unable to see over the nose of the airplane and collided with a stand of tall spruce trees. Witnesses stated that after impact, the airplane descended into the water, resulting in substantial damage to the wings and fuselage. The pilot reported there were no preaccident mechanical malfunctions that would have precluded normal operation.

Probable cause

The pilot's failure to maintain clearance from trees during an attempted go-around.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC16LA038
Event ID
20160705X13929
Case number
ANC16LA038
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2016-07-04.
  • API snapshot SHA-256: 77a594ce15924379a85fe7ac8dae933260efb30d3ea78152db6ba3d213b2ceb6; retrieved 2026-09-16T03:36:22.840Z.