Piper PA-32-260 accident near Petersburg, Michigan, September 29, 2000
On September 29, 2000 at about 7:04 pm local time, a Piper PA-32-260, registered N33117, was destroyed in an accident near Petersburg, Michigan (Gradolph Field). It was a personal flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
the pilots failure to abort the takeoff and obtain/maintain clearance from the corn crop. Factors were the tall, wet, grass runway, and the corn crop.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 29, 2000 · about 7:04 pm local time
- Place
- Petersburg, Michigan · Gradolph Field · map
- Type
- Accident
- Injuries
- No one was hurt; 3 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-32-260 · all PA-32-260s on the register
- Registration
- N33117 · no longer on the register · serial 32-7500014
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The airplane impacted corn immediately after takeoff from a grass runway and was destroyed by a post impact fire. The pilot said he was departing on runway 27 using a short field takeoff procedure. He said that the wind was 270 degrees at 5-7 knots. He said that, during the takeoff, the airplane "settled back on down. He said that the airplane became airborne again but couldn't clear the corn crop at the end of the runway. The pilot said that the grass on the west end of the runway was about 8 inches high. In his written report, the pilot listed no mechanical malfunction of the aircraft. A postaccident examination of the aircraft failed to reveal any preexisting anomalies. The inspector also noted that the grass on the runway was about 3 inches high and the grass was "very damp but firm." A weather report for a reporting station located about 13 nautical miles and 85 degrees magnetic was reporting winds, about 20 minutes after the accident, as 130 degrees at 3 knots.
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
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 232 hours in all; 172 in this make and model; 10 in the last 90 days; 2 in the last 30 days; 180 as pilot in command
- Medical certificate: Class 3 (valid medical--no waivers/lim.)
- Seat: left
The aircraft
- Last inspection: annual inspection, March 15, 2000
- Maximum gross weight: 3,400 lb
- Seats: 6
- Landing gear: fixed
- Engine: Lycoming O-540 (piston); 0 hours total
- Fire on the ground
The flight
- Departed from: 88G at 7:04 pm
- Destination: Eaton Rapids MI
- Flight plan: none
- Runway 27, 2,380 ft by 110 ft
Weather at the time
- Light: not reported
- Wind: from 130° at 3 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 145°F (63°C), dew point 109°F (43°C)
- Altimeter: 30.00 inHg
- Observation at 7:21 pm from TTF, 13 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 | |||
| Passengers | 2 |
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.