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

Piper PA-22-160 accident near Watertown, South Dakota, November 8, 2010

On November 8, 2010 at about 9:00 pm local time, a Piper PA-22-160, registered N3029Z, was substantially damaged in an accident during landing (landing roll) near Watertown, South Dakota. It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's inadvertent and premature use of the brakes during the landing roll, which resulted in a nose-over.

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

What the record shows

Date
November 8, 2010 · about 9:00 pm local time
Place
Watertown, South Dakota · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Piper PA-22-160 · all PA-22-160s on the register
Registration
N3029Z · registry record · serial 22-6983
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot reported that he circled the farm field to check the condition of the landing area prior to landing. During the landing roll, he inadvertently stepped on the brakes prior to the tailwheel touching down and the airplane nosed over, which resulted in substantial damage to the fuselage and wings.

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. Nose over/nose down during landing (landing roll) defining event

The NTSB's findings

  • cause Aircraft › Aircraft systems › Landing gear system › Brake › Unintentional use/operation
  • cause Personnel issues › Action/decision › Action › (general) › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 138 hours in all; 45 in this make and model; 11 in the last 90 days; 6 in the last 30 days; 45 as pilot in command
  • Last flight review: August 10, 2010
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Airframe total time: 1,976 hours
  • Last inspection: annual inspection, December 20, 2009; 74 hours since
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320 (piston); 0 hours total
  • Operator: Super 20 LLC

The flight

  • Departed from: LYV Laverne SD at 7:30 pm
  • Destination: Watertown SD
  • Flight plan: none
  • Runway 04, 1,800 ft

Weather at the time

  • Light: daylight
  • Wind: from 130° at 8 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 64°F (18°C), dew point 36°F (2°C)
  • Altimeter: 29.84 inHg
  • Observation at 7:45 pm from ATW, 7 miles away

Injuries

FatalSeriousMinorNone
Flight 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.

Other NTSB records under N3029Z the same tail number, which may have belonged to a different aircraft at the time

2005-10-29ATL06CA011 · accident near Bennettsville, SC · substantial damage · no injuries

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.