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

Piper PA-36-285 accident near Clark, South Dakota, June 12, 2009

On June 12, 2009 at about 3:15 pm local time, a Piper PA-36-285, registered N57625, was substantially damaged in an accident during maneuvering near Clark, South Dakota. It was an aerial application (crop spraying) flight under agricultural flying rules (Part 137). 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 inadequate visual lookout and failure to maintain clearance from a levy.

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

What the record shows

Date
June 12, 2009 · about 3:15 pm local time
Place
Clark, South Dakota · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-36-285 · all PA-36-285s on the register
Registration
N57625 · registry record · serial 36-7660022
Damage
Substantial damage
Flight
Aerial application (crop spraying) flight · agricultural flying rules (Part 137)

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

The aerial application pilot reported that he was setting navigational equipment while en route to a field to spray. He stated that he became fixated on the unit. He said, “at the end of the field was a levy with a road on top of it. I noticed this too late and impacted the landing gear of the aircraft at the top of the levy. The airplane continued to fly and I knew I had hit something.” Review of photographs of the airplane showed that structural tubing was torn away from the fuselage tubing and the torn structure remained attached to the separated landing gear.

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. Controlled flight into terrain or object (CFIT) during maneuvering defining event

The NTSB's findings

  • Environmental issues › Physical environment › Terrain › Sloped/uneven › Contributed to outcome
  • cause Personnel issues › Action/decision › Action › Lack of action › Pilot
  • cause Personnel issues › Psychological › Attention/monitoring › Monitoring environment › Pilot

Pilot

  • Certificate: flight instructor, commercial pilot
  • Ratings: single-engine land; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 1,040 hours in all; 7 in this make and model; 10 in the last 90 days; 4 in the last 30 days; 941 as pilot in command; 275 on instruments
  • Last flight review: January 28, 2010
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: ctr
  • Injury: no injuries

The aircraft

  • Seats: 1
  • Landing gear: fixed
  • Engine: Lycoming IO-720 (piston); 0 hours total

The flight

  • Departed from: 8D7 Clark SD
  • Destination: Clark SD
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 59°F (15°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

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.