NTSB CAROL · Event
Event ANC16LA062
Registry · N91AK
FAA Aircraft Registry record.
Make / Model
VAN'S AIRCRAFT RV-12IS
Year of manufacture
2024
Engine
ROTAX 912 IS (100 hp)
Seats / Engines
2 seats · 1 engine
Last airworthiness date
20240427
ADS-B equipped
Yes — Mode-S AC945C
Registrant of record
REXAIR AIRCRAFT LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's failure to maintain adequate airspeed during the initial climb and turn after takeoff, which resulted in an exceedance of the airplane's critical angle of attack and an aerodynamic stall.
Factual narrative
On September 9, 2016, about 1130 Alaska daylight time, a float-equipped, de Havilland DHC-2 (Beaver) airplane, N91AK, sustained substantial damage during a collision with water, following a loss of control shortly after takeoff from Uganik Lake, about 35 miles west-southwest of Kodiak, Alaska. The airplane was registered to Redemption, Inc., and operated as Flight 43 by Island Air, as a visual flight rules (VFR) scheduled commuter flight under the provisions of 14 Code of Federal Regulations (CFR) Part 135. Of the three occupants onboard, the airline transport pilot and two passengers all sustained serious injuries. Visual meteorological conditions prevailed, and company flight following procedures were in effect. Flight 43 originated in Kodiak about 1100, with a preplanned, intermediate stop at Uganik Lake, before continuing to the flights scheduled stops in Amook Bay and Zachar Bay, Alaska. According to the operator's director of maintenance the purpose for the intermediate stop at Uganik Lake was to drop off a maintenance technician. He added that another company owned a Cessna 185 that had landed at Uganik Lake earlier in the day and damaged a float, and the maintenance technician was called in to inspect the float prior to the airplane returning to Kodiak. He said that after landing, the accident pilot met the crew of the Cessna 185 on the western shore of Uganik Lake, where he dropped off the maintenance technician, and then he departed for Amook Bay. Witnesses reported seeing the accident airplane back-taxi to the east before it eventually turned around to start the takeoff run to the west, and towards an area of rising, tree-covered terrain. The witnesses consistently reported that after the airplane became airborne, it began a left turn to avoid the rising terrain ahead. As the airplane flew closer to the rising terrain, the left turn steepened, and the airplane began a steep nose down descent. The airplane subsequently struck the shallow waters on the western end of Uganik Lake, and it came to rest partially submerged. The airplane sustained substantial damage to the wings and fuselage. The witnesses to the accident reported gusty wind conditions, from the west, estimated to be between 15 to 25 knots. Due to injuries sustained in the accident, the pilot did not recall the accident sequence; however, he did remember back-taxiing the airplane to the east for a westerly departure. He also recalled variable wind conditions, estimated to be 15 knots, with increasing gusts to 25 knots from the west. The pilot stated that to the best of his knowledge there were no preimpact mechanical anomalies with the airplane. One of the two passengers reported that he was seated in the right front seat, and his wife was seated just behind the pilot on the left side of the airplane. He added that water conditions consisted of 8 to 12 inches of chop on the surface of the water as the pilot started his westerly takeoff run. He said that just after takeoff, the airplane climbed slower than what he was accustomed to from previous flights. He added that as the airplane continued to climb, he could see an area of rising terrain ahead of them. As the airplane approached the area of rising terrain, he said that the pilot turned the airplane very steeply to the left, and then the airplane nosed down abruptly and then began a nosed down, uncontrolled descent into the shallow water below.
ADDITIONAL INFORMATION
At the time of the accident, the pilot was using a Garmin GPSMAP 496 portable global positioning system (GPS) receiver, capable of storing route-of-flight data. The GPS data logs for September 9, 2016 supported the pilots, passengers, and witness accounts of the accident. A flight track map overlay, and tabular data corresponding to the accident flight are available in the public docket for this accident. The airline transport pilot was conducting a scheduled commuter flight between remote villages in a float-equipped airplane. After making an intermediate stop to drop off a company maintenance technician at a remote lake, the pilot back-taxied the airplane to the east in preparation for a westerly departure. He estimated the wind at 15 knots with increasing gusts to 25 knots from the west. Ground witnesses and passengers on board the airplane reported that the pilot initiated a takeoff to the west, toward an area of rising, tree-covered terrain. After becoming airborne, the airplane entered a left turn to avoid the terrain. The left turn steepened, and the airplane then entered a steep nose-down descent into the terrain. The pilot reported that he did not recall any preaccident mechanical problems with the airplane. Due to his injuries, he was unable to recall the events of the accident. Postaccident examination revealed no mechanical malfunctions or anomalies of the airplane. Given the witness accounts of the accident, it is likely that the pilot exceeded the airplane's critical angle of attack during the initial climb toward and subsequent turn away from rising terrain, which resulted in an aerodynamic stall and loss of control at an altitude too low for recovery. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Airspeed-Not attained/maintained - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Angle of attack-Not attained/maintained - C
- — Environmental issues-Physical environment-Terrain-Mountainous/hilly terrain-Contributed to outcome
Verbatim from NTSB's published report. Source file
NTSB_2016_ANC16LA062.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall, loss of control, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2023 · Conference paper
The Value of Strong Partnerships to Build a Successful Aviation Maintenance Career Pathway Program for Transitioning Military Service Members
The aerospace industry is competing with other industries for a qualified workforce, and many of those competing industries are investing heavily in creating workforce development pipelines.
- Semantic Scholar 2016 · Article (Interacción)
Trajectory Recovery System: Angle of Attack Guidance for Inflight Loss of Control
This paper describes the design and development of an ecological display to aid pilots in the recovery of an In-Flight Loss of Control event due to a Stall (ILOC-S).
- NTSB Aircraft Accident Reports 2010 · Accident report
Loss of Control on Approach — Colgan Air Flight 3407
Colgan Air 3407 / Continental Connection (Q400) Buffalo NY, February 12, 2009 — 50 fatalities. Definitive investigation of the Colgan 3407 stall-stick-pusher crash on approach to Buffalo.
- NTSB Aircraft Accident Reports 2002 · Accident report
Loss of Control and Impact with Pacific Ocean — Alaska 261
Alaska Airlines Flight 261 (MD-83) Pacific Ocean, January 31, 2000 — 88 fatalities. Definitive investigation of the Alaska 261 pitch-runaway-and-loss-of-control crash.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
Browse the full corpus — academia portal ↗