What happened
On November 10, 2019, a Piper PA32-300 aircraft, registration N7721C, was involved in an accident near Goodnews Bay, Alaska. The flight was the final segment of a scheduled commuter route from Goodnews Airport (GNU) to Bethel Airport (BET). The crew consisted of the pilot and a pilot-rated observer.
After departing runway 6 at GNU, the pilot climbed to approximately 300 feet above ground level and initiated a right turn to the northwest to avoid mountainous terrain. The pilot reported that while the flight was occurring in dark conditions, a horizon and distant village lights were visible. During the turn, the pilot noticed the vertical speed indicator (VSI) showed a descent of 500 feet per minute. The pilot attempted to arrest the descent by pulling back on the control yoke, but the aircraft continued to descend.
The aircraft impacted the water near the mouth of the Goodnews River approximately 30 to 60 seconds after the descent was first noted. The impact occurred with the right wing first. Both the pilot and the observer were not injured and were able to egress the aircraft and wait for rescue.
The investigation
Due to the remote location, the wreckage was not physically examined, but photographic evidence was reviewed. The investigation found that the wings, fuselage, and right side of the stabilator sustained substantial damage. The engine and front fuselage were partially separated from the airframe at the firewall. The propeller blades exhibited rearward bending with spanwise torsional twist signatures, which is indicative of the engine producing power at the time of impact.
Data from a recovered Garmin 796 GPS unit ended during a taxi sequence at GNU, likely due to a buffering process. Weather observations from Platinum Airport (PTU) four minutes before the accident indicated winds from 140 degrees at 12 knots, 10 miles of visibility, and an overcast cloud layer at 2,000 feet. The accident occurred approximately 1.5 hours after sunset, and the crew reported that moonlight was obscured by clouds.
Findings
- The pilot did not observe abnormal engine indications or sounds, and the observer noted the engine RPM sounded high just before impact.
- The pilot's report that the aircraft did not respond to elevator inputs suggests a potential control issue rather than engine failure.
- The pilot did not perform emergency procedures, make a radio call, or activate the emergency locator transmitter before the impact.
- The dark environment and lack of visual cues were highly conducive to spatial disorientation.
- The pilot was not monitoring the instruments until the descent was already underway.