The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB ANC09CA095 · Final report

Piper PA-22-160 accident near Talkeetna, Alaska, September 3, 2009

On September 3, 2009 at about 10:30 pm local time, a Piper PA-22-160, registered N9985D, was substantially damaged in an accident during takeoff near Talkeetna, Alaska. It was a personal 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).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

The pilot's selection of an unsuitable landing/takeoff area, resulting in a nose over during takeoff.

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

What the record shows

Date
September 3, 2009 · about 10:30 pm local time
Place
Talkeetna, Alaska · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-22-160 · all PA-22-160s on the register
Registration
N9985D · registry record · serial 22-6777
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The private pilot was taking off from a sand and gravel-covered off-airport site, on a Title 14, CFR Part 91 personal flight. He reported that during the takeoff roll the airplane did not become airborne before reaching the end of the site, and the main wheels struck a pool of water at the departure end. The airplane subsequently nosed over resulting in substantial damage to the wings and fuselage. The pilot said there were no preaccident mechanical problems with the airplane, and noted in his report to the NTSB that it was a poor decision to land at the off-airport site.

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. Collision with terrain or object (not controlled flight into terrain) during takeoff defining event
  2. Nose over/nose down during takeoff

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • Environmental issues › Physical environment › Runway/land/takeoff/taxi surfa › Wet › Contributed to outcome
  • cause Aircraft › Aircraft oper/perf/capability › Aircraft capability › Takeoff distance › Capability exceeded

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 99 hours in all; 99 in this make and model; 49 in the last 90 days; 19 in the last 30 days; 72 as pilot in command
  • Last flight review: July 29, 2009
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 3,141 hours
  • Last inspection: annual inspection, November 20, 2008; 99 hours since
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320 SERIES (piston); 0 hours total

The flight

  • Departed from: Talkeetna AK at 5:30 pm
  • Destination: BCV Chugiak AK
  • Flight plan: none
  • Runway 18
  • A second pilot was aboard

Weather at the time

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

Injuries

FatalSeriousMinorNone
Flig1
Passengers1

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number ANC09CA095.