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

Piper PA-12 accident near Fairbanks, Alaska, September 23, 2012

On September 23, 2012 at about 10:00 pm local time, a Piper PA-12, registered N4483M, was substantially damaged in an accident during enroute (cruise) near Fairbanks, Alaska (Gold King airport). It was a personal flight under general aviation rules (Part 91). 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 improper fuel management, which resulted in a loss of engine power due to fuel starvation.

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

What the record shows

Date
September 23, 2012 · about 10:00 pm local time
Place
Fairbanks, Alaska · Gold King · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-12 · all PA-12s on the register
Registration
N4483M · registry record · serial 12-3436
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The airplane was in level cruise flight when the engine lost power, resulting in an off-airport emergency landing. During the emergency landing, the airplane nosed over and sustained substantial damage to the rudder. The pilot stated that he had exhausted all the fuel from the right tank. When the engine lost power, he switched to the left fuel tank but could not restart the engine.

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 engine power (total) during enroute (cruise) defining event
  2. Fuel starvation during enroute (cruise)
  3. Loss of engine power (total) during emergency descent
  4. Nose over/nose down during landing (landing roll)

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
  • cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid level

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; single-engine sea; instrument: airplane
  • Flight time: 16,000 hours in all; 2,000 in this make and model; 400 in the last 90 days; 140 in the last 30 days
  • Last flight review: May 1, 2012
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: frt
  • Injury: no injuries

The aircraft

  • Airframe total time: 2,914 hours
  • Last inspection: annual inspection, May 20, 2012
  • Maximum gross weight: 1,750 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming O-235 SERIES (piston); 0 hours total

The flight

  • Departed from: Fairbanks AK
  • Destination: AK7 Fairbanks AK
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Visibility: 50 statute miles
  • Sky: clear
  • Temperature: 61°F (16°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Flight crew1

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

1 document, released by the NTSB on October 27, 2012. 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.