FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC15FA071 · de Havilland DHC 3T

15 Sept 2015 · Iliamna, AK, United States

Rainbow King Lodge de Havilland DHC 3T · Accident: loss of control in flight during initial climb

From Iliamna, AK to Kodiak, AK

Report a problem

Event

NTSB case
ANC15FA071
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
3 · 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

de Havilland DHC 3T

Aircraft type
de Havilland DHC-3
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
N928RK
Onboard fatalities
Unknown
Route
From Iliamna, AKTo Kodiak, AK
Aircraft age
About 61 years (built 1954)
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
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
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • 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 airline transport pilot and nine passengers departed in a float-equipped airplane in dark night, visual meteorological conditions on a 14 Code of Federal Regulations Part 91 other work use flight from a fishing lodge to a remote fishing location. The pilot reported that, before the flight departed, the front and center fuel tanks were filled, and the aft fuel tank had "residual" fuel. He did not weigh the cargo nor did he document any weight and balance calculations. When asked how he calculated the airplane's weight and balance before departure, the pilot said he "guesstimated" it.

According to a witness, after liftoff, the airplane began to climb and then descended, and the floats subsequently struck the water's surface. The airplane then became airborne again and veered right, but he lost sight of it behind an area of rising terrain. The pilot reported that he heard a noise from the left side of the airplane shortly after liftoff, which was likely the floats impacting the water. According to the automatic dependent surveillance-broadcast data, the airplane then began a gradual right turn before reaching a maximum altitude of 175 ft above the water. The airplane then descended toward the water's surface, flew low over the water and terrain, and then climbed briefly again before it impacted terrain. The pilot stated that he did not know that the airplane touched the water's surface after the initial liftoff or that the airplane then turned right.

Impact signatures were consistent with a right-wing-low attitude at impact. The entire airplane was accounted for at the wreckage site. Disassembly and examination of the engine and propeller revealed that both were operating during impact. Examination of the airframe and flight control systems found no preimpact malfunctions or failures that would have precluded normal operation.

A postaccident weight and balance study using the passenger weights, weighed cargo, and fuel load showed that the airplane exceeded its maximum gross weight of 8,367 lbs by about 508.6 lbs and that the center of gravity (CG) was 4.08 inches aft of the aft CG limit. Data from the airplane's automatic dependent surveillance-broadcast (ADS-B) showed that the airplane was at or below the stall speeds listed in the airplane flight manual during both the initial and second climbs. The ADS-B data show that, because the pilot failed to determine the airplane's actual preflight weight and CG and loaded and operated outside of the weight and CG limits, the airplane did not attain a proper airspeed to climb, and it experienced an aerodynamic stall.

The pilot departed during dark night conditions over water and was relying on external visual cues and not the airplane's instrumentation to control the airplane. There were insufficient external cues available to the pilot to reliably control the airplane, and he was likely experiencing spatial disorientation after takeoff and the subsequent maneuvering.

Probable cause

The pilot's decision to depart in dark night, visual meteorological conditions over water, which resulted in his subsequent spatial disorientation and loss of airplane control. Contributing to the accident was the pilot's failure to determine the airplane's actual preflight weight and balance and center of gravity (CG), which led to the airplane being loaded and operated outside of the weight and CG limits and to a subsequent aerodynamic stall.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC15FA071
Event ID
20150915X52520
Case number
ANC15FA071
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: 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: 0d3d64abebac9683593a4242c70151f5e636b5811b47c8456bf6a0a95e4f81ae; retrieved 2026-09-14T21:31:03.388Z.