NTSB CAROL · Event
Event ANC17LA053
Registry · N16GP
FAA Aircraft Registry record.
Make / Model
CESSNA U206G
TCDS
A4CE · CESSNA
Engine
CONT MOTOR IO 520 SERIES (285 hp)
Seats / Engines
6 seats · 1 engine
Last airworthiness date
19780530
ADS-B equipped
Yes — Mode-S A0EFF9
Registrant of record
DECKLOAD AVIATION LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
***This probable cause was modified on November 27, 2018. Please see the docket for this accident to view the original probable cause.*** The pilot's improper decision to takeoff in an area of rough water and ocean swells, which resulted in a failure of the right float struts.
Factual narrative
On September 4, 2017 about 1430 Alaska daylight time, an amphibious float-equipped Cessna U206 airplane, N16GP, sustained substantial damage while attempting to depart the water at Trident Basin Seaplane Base (T44), Kodiak, Alaska. The airplane was registered to and being operated by the pilot as a 14 Code of Federal Regulations Part 91 visual flight rules flight. The airline transport pilot and three passengers were not injured. Marginal visual meteorological conditions existed and no flight plan had been filed. According to the pilot during the takeoff run, the airplane encountered small swells and began to lose speed, while simultaneously pitching forward. In an effort to correct for the forward pitching moment, the pilot applied full aft elevator. Shortly thereafter, he aborted the takeoff, but the airplane continued to pitch forward when it was struck by a larger swell. The right forward float strut fractured and the airplane rolled to the right, which resulted in substantial damage to the right wing's lift strut. An initial examination of the airplane by the pilot revealed that the left nose wheel was partially deployed with the landing gear handle in the up position. A pilot rated witness reported that the accident pilot was talking to several pilots, prior to boarding the airplane, the morning of the accident and specifically asked him "what do you think?" and "which way to go?". He went on to state that one of the options, rather than the typical north departure, was to use "The Cut", which is an easterly departure through a break between the islands. He said this worked as long as the aircraft was airborne before exiting the protected area, as ocean swells were encountered on the other side of the islands. Another pilot rated witness reported that he leaned out his office door and watched as the accident pilot started his water run. He said his initial thought was that the airplane "must be really heavy" because it took a very long time for the airplane to accelerate onto the step. As the airplane disappeared through "The Cut", he saw the wings start rocking up and down, as the airplane, still on step, encountered the ocean swells on the other side. A third pilot rated witness reported that he observed the accident airplane begin its water run. He stated that the airplane was in the plow for an estimated 1,100 ft, prior to accelerating onto the step. The airplane then went through the "The Cut" where it encountered about 8-foot-tall ocean swells, and disappeared. He continued to hear the airplane's engine operating at full power for about 15 seconds before it abruptly stopped. He then jumped in his skiff and motored through "The Cut" to the accident site to assist with the rescue of the airplane and its occupants. A fourth pilot rated witness who aided in the recovery of the airplane the day of the accident reported wind from the east at 15 to 20 knots, 1 to 1 ½ ft seas, with 6 to 8-inch swells. He also stated that there was no evidence of a hydraulic oil leak on the water as the airplane was towed back to the docks at T44. Neither the pilot, nor any of the multiple witnesses reported the airplane yawing about its vertical axis during the takeoff run. Photos of the accident airplane taken during the rescue indicate rough water near the accident site with large ocean swells. The coastal waters forecast for Chiniak Bay on September 4, called for seas of 9 ft, with wind out of the southeast at 25 knots and rain, and a Small Craft Advisory had been issued. The closest weather reporting facility was Kodiak Airport (PADQ), Kodiak, Alaska, about 4.5 miles southwest of the accident site. At 1428, a METAR from PADQ was reporting, in part: wind 100° at 15 knots; visibility, 4 statute miles, mist; clouds and ceiling, scattered clouds at 1,000 ft, overcast clouds at 3,100 ft; temperature, 54° F; dew point 54° F; altimeter, 29.59 inches of Mercury. The airplane was equipped with EDO 696-3500 amphibious floats. The hydraulic lines that service the landing gear are routed through the hollow float struts to their attach points on the deck of the floats. The mechanic who removed the airplane from the water the day after the accident reported that all three of the right float struts were separated completely from their attach points and the hydraulic lines servicing the landing wheels were severed. A postaccident examination of the airplane revealed that the left and right mechanical portion of the landing gear retraction system was not rigged correctly, and the amphibious float cable loops were set to about a 17-pound tension load. No evidence of a hydraulic leak was present inside the amphibious floats or the fuselage. The EDO Model 696-3500 Service and Maintenance Manual states in part: "Rig the cable loop to a 75 – 125-pound tension load." The book, How To Fly Floats, published by EDO Corporation, Rough Water Take-offs states in-part: "When possible, take-offs in rough water should be avoided. Before attempting a rough water take-off, do some reconnaissance of the area first. You may happen to find more favorable surface conditions nearby. Pay special attention to any severe swell conditions that may exist and keep an eye out for swells produced by moving boat traffic. There is a very good possibility that severe damage can be done to either the floats, the attachment gear or the aircraft in big swell conditions." The airline transport pilot reported that, while attempting to takeoff in an amphibious, float-equipped airplane in choppy ocean waters, the airplane began to lose speed while simultaneously pitching forward. He subsequently aborted the takeoff, and the airplane struck a large swell, the right forward float strut fractured, the airplane rolled to the right, and the right wing's lift strut was substantially damaged. The pilot's initial examination of the airplane revealed that the left nosewheel was partially deployed even though the landing gear handle was in the "up" position. Multiple witnesses observed the airplane depart to the east toward an area of unprotected water. One witness reported about 8-ft ocean swells in the unprotected area of the takeoff run, and another witness reported a strong wind from the east. Photos of the accident airplane taken during the rescue indicate rough water near the accident site with large ocean swells. Further, the forecast that day called for 9-ft seas and 25 knot winds. Guidance for takeoffs in float-equipped airplanes states that severe damage can occur when taking off in sea conditions with large swells. Although the pilot was aware of the ocean conditions he still attempted to takeoff in a protected area; however, the airplane did not lift off before reaching the ocean and encountered the large swells. A postaccident examination of the airplane revealed that the left and right mechanical portion of the landing gear retraction system was improperly rigged, and the amphibious float cable loops were set to an inappropriately low tension load. No evidence of a hydraulic leak was present inside the amphibious floats or the fuselage. Due to the improperly rigged landing gear, it is likely that the landing gear up-locks disengaged during the impact with the ocean swells. However, neither the pilot nor any of the witnesses reported the airplane yawing about its vertical axis during the takeoff run; thus, it is unlikely that the left nosewheel deployed during the accident airplane's water run. Furthermore, it is likely that the hydraulic lines were breached when the rear float struts were impact damaged, which then released hydraulic pressure and allowed the previously unlocked nosewheel to partially deploy after the accident. 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-Action/decision-Info processing/decision-Decision making/judgment-Pilot - C
- C Environmental issues-Physical environment-Runway/land/takeoff/taxi surface-Choppy surface-Decision related to condition - C
Verbatim from NTSB's published report. Source file
NTSB_2017_ANC17LA053.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 (icing, 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 · Faculty research project
Reconfigurable Guidance and Control Systems for Emerging On-Orbit Servicing, Assembly, and Manufacturing (OSAM) Space Vehicles
Dynamic response to emergent situations is a necessity in the on-orbit servicing, assembly, and manufacturing (OSAM) field, because traditional on-orbit guidance and control (G&C) cannot respond effic…
- Embry-Riddle Scholarly Commons 2019 · Journal article (IJAAA)
Satellite Maintenance: An Opportunity to Minimize the Kessler Effect
Recently, there has been an emphasis on the growing problem of orbital debris. While the advantages of placing satellites into space are numerous, advances in satellite technology combined with the gr…
- Embry-Riddle Scholarly Commons 2015 · Conference paper
The Implementation of Safety Management Systems in Maintenance Operations
Literature for Safety Management Systems (SMS) that apply to flight operations is abundant, but there is a limited supply of SMS-related literature for maintenance operations.
- 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 · Contractor Report (CR)
Icing Physics Studies Using the 3D SIDRM Test Article: 2023 Icing Tests Analysis
In-flight icing is an important safety issue and is a factor that affects aircraft design and performance. Newer regulations are driving a need for improvements in airframe and engine icing simulation…
- arXiv 2025 · arXiv preprint
Multi-Agent Deep Reinforcement Learning for UAV-Assisted 5G Network Slicing: A Comparative Study of MAPPO, MADDPG, and MADQN
The growing demand for robust, scalable wireless networks in the 5G-and-beyond era has led to the deployment of Unmanned Aerial Vehicles (UAVs) as mobile base stations to enhance coverage in dense urb…
Browse the full corpus — academia portal ↗