Piper PA-32-260 accident near Vermillion, South Dakota, April 18, 2008
On April 18, 2008 at about 4:30 pm local time, a Piper PA-32-260, registered N32394, was substantially damaged in an accident during landing (landing roll) near Vermillion, South Dakota. It was a personal flight under general aviation rules (Part 91). No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to adequately compensate for the crosswind condition. Contributing to the accident were the crosswind and the soft terrain.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 18, 2008 · about 4:30 pm local time
- Place
- Vermillion, South Dakota · map
- Type
- Accident
- Injuries
- No one was hurt; 4 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-32-260 · all PA-32-260s on the register
- Registration
- N32394 · registry record · serial 32-7500005
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported the local winds were from 020 degrees at 14 knots when he landed. He stated that after touching down, the wind pushed the airplane off the left side of the runway. The nose gear collapsed and the airplane came to rest when it contacted an area of grass and soft sand. The pilot reported that he did not use enough rudder to compensate for the wind.
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
- Loss of control on ground during landing (landing roll) defining event
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
- Landing gear collapse during landing (landing roll)
The NTSB's findings
- factor Environmental issues › Conditions/weather/phenomena › Wind › Crosswind › Not specified
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Crosswind correction › Not attained/maintained
- factor Environmental issues › Physical environment › Runway/land/takeoff/taxi surfa › Soft › Not specified
- Aircraft › Aircraft systems › Landing gear system › Nose/tail landing gear › Capability exceeded
Pilot
- Certificate: private
- Ratings: instrument: airplane
- Flight time: 202 hours in all; 38 in this make and model; 64 in the last 90 days; 3 in the last 30 days; 175 as pilot in command
- Medical certificate: Class 3
- Injury: no injuries
The aircraft
- Landing gear: fixed
- Engine: Lycoming O-540-E4B5 (piston); 0 hours total
The flight
- Departed from: RAP Rapid City SD
- Destination: Vermillion SD
- Flight plan: VFR
Weather at the time
- Light: daylight
- Wind: from 020° at 14 knots
- Visibility: 10 statute miles
- Sky: overcast at 12,000 ft
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 3 |
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.