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

Piper PA-32-300 accident near Kotzebue, Alaska, April 16, 2003

On April 16, 2003 at about 6:05 pm local time, a Piper PA-32-300, registered N2863T, was substantially damaged in an accident near Kotzebue, Alaska (Kotzebue airport). It was flown under charter and air-taxi rules (Part 135). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain adequate altitude/clearance, which resulted in an in-flight collision with terrain during cruise flight. Factors associated with the accident were flat light conditions, and snow-covered terrain.

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

What the record shows

Date
April 16, 2003 · about 6:05 pm local time
Place
Kotzebue, Alaska · Kotzebue · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-32-300 · all PA-32-300s on the register
Registration
N2863T · no longer on the register · serial 32-7240095
Damage
Substantial damage
Flight
Flight · charter and air-taxi rules (Part 135)

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

The solo commercial pilot reported he was transporting cargo on a cross-country flight in VFR conditions. The flight progressed over a large, featureless, snow-covered lagoon, and according to the pilot, flat light conditions made it difficult to discern any topographical features of the terrain. The pilot didn't realize that the airplane had entered a descent. The airplane descended and ultimately struck the snow-covered lagoon, sustaining substantial damage to the wings and fuselage. The pilot reported that there were no preaccident mechanical anomalies with the airplane. The reported weather conditions included a 1,200 foot overcast ceiling and visibility of 9 statute miles.

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

Pilot

  • Certificate: commercial pilot
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 1,900 hours in all; 400 in this make and model; 300 in the last 90 days; 80 in the last 30 days; 1,860 as pilot in command
  • Last flight review: November 21, 2002
  • Medical certificate: Class 2 (valid medical--no waivers/lim.)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 7,610.3 hours
  • Last inspection: 100-hour inspection, April 1, 2003; 48.3 hours since
  • Maximum gross weight: 3,400 lb
  • Seats: 6
  • Landing gear: fixed
  • Engine: Lycoming IO-540K-1A5 (piston); 0 hours total

The flight

  • Departed from: OTZ Kotzebue AK at 12:59 pm
  • Destination: ORV Noorvik AK
  • Flight plan: VFR

Weather at the time

  • Light: daylight
  • Wind: from 080° at 5 knots
  • Visibility: 9 statute miles
  • Sky: overcast at 1,200 ft
  • Temperature: 32°F (0°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Crew1

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

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.