The U.S. aircraft register, updated daily
Accidents · NTSB ANC20LA004 · Final report

Piper PA32R accident near Goodnews Bay, Alaska, November 11, 2019

On November 11, 2019 at about 3:40 am local time, a 1975 Piper PA32R, registered N7721C, was substantially damaged in an accident during initial climb near Goodnews Bay, Alaska. It was a positioning flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s failure to monitor the airplane instruments during a night visual flight rules departure in dark light conditions, which resulted in spatial disorientation and the airplane’s descent into water.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
November 11, 2019 · about 3:40 am local time
Place
Goodnews Bay, Alaska · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA32R 300, built 1975 · all PA32Rs on the register
Registration
N7721C · registry record · serial 32R-7680060
Damage
Substantial damage
Flight
Positioning flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot was conducting the last segment of a scheduled visual flight rules (VFR) route to the company base airport with a pilot-rated observer on board. The weather conditions were night marginal VFR, and the departure airport was in a remote, dark area located on the edge of a large bay. The pilot stated that after takeoff to the east, while turning right to the northwest, he suddenly felt that the airplane was descending; he looked at the vertical speed indicator (VSI) and observed a 500 ft-per-minute descent. The airplane was about 500 ft above ground level at that time. He did not note abnormal engine indications or sounds and attempted to arrest the descent by pulling back on the control yoke, but nothing happened. The airplane impacted the water about 30 to 60 seconds later. He and the observer egressed with no injuries. The observer stated that after takeoff, he was adjusting his headlamp and not looking at the instruments or outside. He then saw what looked like heavy rain out the right window. He recalled that the engine sounded normal, and rpm sounded high just before the airplane “slammed” into the water, right wing first. He did not hear the pilot say anything about engine power or offer any warning to brace for impact. During an interview, the pilot stated that he believed that the airplane wasn’t producing sufficient power because the airplane continued to descend and had a negative VSI indication. He did not attempt to adjust the engine controls, perform any emergency procedures, prepare the airplane for a water landing, make a radio call, or activate the emergency locator transmitter because there was no time. He stated that he concentrated on flying straight ahead with the wings level and told the observer that they were going down. Photographs of the wreckage showed the right wing experienced significant fore-to-aft crush damage, the front fuselage was partially separated from the airframe, and the propeller blades were bent aft with spanwise torsional twists, indicative of engine power at impact. Based on the pilot’s statement that he did not observe abnormal engine indications or sounds, the observer’s recollection that the rpm sounded high before impact, and the propeller impact signatures, it is unlikely that the engine lost power. The pilot did not make sufficient corrections to prevent the impact, such as increasing rpm and throttle to maximum, performing restoring engine power procedures, or obtaining a landing attitude for ditching. Also, he stated that he pulled back on the yoke and the airplane did not respond, which would indicate an elevator control problem and not an engine problem. He made no radio call and did not activate the emergency locator transmitter before impact. Although the pilot indicated he concentrated on flying the airplane straight ahead with wings level, evidence is consistent with the airplane impacting the water in a nose-low, right-wing-down attitude. It is likely that the airplane impacted the water during the initial climbing turn phase, which was consistent with the observer’s recollection. The nearest weather observation about 4 minutes before the accident indicated an overcast cloud layer at 1,600 ft. The accident occurred about 1.5 hours after sunset and, according to the pilot and observer, the moonlight was obstructed by clouds. The pilot stated that it was very dark to the east, which was the direction the airplane was heading during the takeoff, initial climb, and the beginning of the right turn. He also recalled that there were some village lights in the distance to the west and that he did see a horizon. The dark night and lack of visual cues in the area were conducive to the effects of spatial disorientation and would have required an instrument scan to mitigate that hazard; however, based on the pilot’s statement, he was not monitoring the instruments until he felt that the airplane was descending. It is likely that the pilot experienced spatial disorientation during the right turn over dark terrain and water but did not recognize the descent as an indication of such and, therefore, did not correct by referencing the instruments and positively regaining control of the airplane.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of visual reference during initial climb
  2. Collision with terrain or object (not controlled flight into terrain) during initial climb defining event

The NTSB's findings

  • Personnel issues › Psychological › Perception/orientation/illusion › Spatial disorientation › Pilot
  • Environmental issues › Conditions/weather/phenomena › Light condition › Dark › Effect on operation
  • Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Pilot
  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Passenger

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane single-engine; instrument: airplane
  • Flight time: 2,000 hours in all; 1,192 in this make and model; 303 in the last 90 days; 67 in the last 30 days; 1,800 as pilot in command
  • Last flight review: October 15, 2018
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

Pilot-Rated Passenger

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane single-engine; instrument: airplane
  • Flight time: 950 hours in all; 0 in this make and model
  • Medical certificate: Class 2
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 14,114 hours
  • Last inspection: annual inspection, November 3, 2019
  • Maximum gross weight: 3,600 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Lycoming IO-540-KID5 (piston); 6,557 hours total
  • Operator: Paklook Air Inc

The flight

  • Departed from: GNU Goodnews Bay AK
  • Destination: BET Bethel AK

Weather at the time

  • Light: night, dark
  • Wind: from 140° at 12 knots, gusting 20
  • Visibility: 10 statute miles
  • Sky: broken clouds at 1,600 ft
  • Temperature: 48°F (9°C), dew point 45°F (7°C)
  • Altimeter: 29.67 inHg
  • Observation at 3:56 am from PAPM, 9 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

8 documents, released by the NTSB on November 12, 2021. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.