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

Piper PA 25-235 accident near Yankton, South Dakota, October 1, 2014

On October 1, 2014 at about 5:30 pm local time, a 1963 Piper PA 25-235, registered N6659Z, was substantially damaged in an accident during maneuvering (low-alt flying) near Yankton, South Dakota (Chan Gurney Muni airport). 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 improper fuel management, which resulted in a loss of engine power due to fuel exhaustion.

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

What the record shows

Date
October 1, 2014 · about 5:30 pm local time
Place
Yankton, South Dakota · Chan Gurney Muni · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA 25-235, built 1963 · all PA 25-235s on the register
Registration
N6659Z · registry record · serial 25-2258
Damage
Substantial damage
Flight
Aerial application (crop spraying) flight · agricultural flying rules (Part 137)

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

After conducting an aerial application flight and attempting to return to the airport, the pilot noticed that the fuel float gauge displayed a low quantity. The airplane's engine experienced a total loss of power. The pilot performed a forced landing in a cornfield about 3 miles west of the airport. The airplane sustained substantial damage to the left wing. The pilot reported in a postaccident statement that he ran out of fuel.

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. Fuel exhaustion during maneuvering (low-alt flying) defining event

The NTSB's findings

  • cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid level
  • cause Personnel issues › Task performance › Planning/preparation › Fuel planning › Pilot
  • cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid management

Pilot

  • Certificate: commercial pilot
  • Ratings: single-engine land
  • Flight time: 1,320 hours in all; 800 in this make and model; 360 in the last 90 days
  • Last flight review: March 1, 2013
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: ctr
  • Injury: no injuries

The aircraft

  • Airframe total time: 3,355 hours
  • Last inspection: annual inspection, April 4, 2014
  • Maximum gross weight: 2,900 lb
  • Seats: 1
  • Landing gear: fixed
  • Engine: Lycoming O-540 B2C5 (piston); 4,870 hours total

The flight

  • Departed from: Meckling SD at 3:45 pm
  • Destination: Tabor SD
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 250° at 11 knots
  • Visibility: 10 statute miles
  • Sky: scat at 3,100 ft
  • Temperature: 72°F (22°C), dew point 59°F (15°C)
  • Altimeter: 29.72 inHg
  • Observation at 5:35 pm from KYKN, 5 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

2 documents, released by the NTSB on October 14, 2014. 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.