Piper J3C-65 accident near South Shore, South Dakota, September 4, 2003
On September 4, 2003 at about 8:30 pm local time, a Piper J3C-65, registered N38435, was substantially damaged in an accident near South Shore, South Dakota. It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A loss of engine power for undetermined reasons. A factor was the soft terrain encountered during the forced landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 4, 2003 · about 8:30 pm local time
- Place
- South Shore, South Dakota · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper J3C-65 · all J3C-65s on the register
- Registration
- N38435 · no longer on the register · serial 7004
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The airplane impacted soft terrain during a forced landing following a loss of engine power. The pilot reported he filled the aircraft with fuel at a private airstrip just prior to takeoff. Approximately 15 minutes after departure the engine lost power. The pilot stated he pumped the throttle, and checked the fuel valve and magnetos, but was unable to get the engine restarted. The pilot stated the airplane impacted soft terrain during the forced landing. The airplane was fueled using above ground fuel tanks at the private airstrip, which is also used by an aerial application operator. There were no reports of problems with other airplanes that had been refueled using the same source. Inspection of the airplane and its engine failed to reveal any failure/malfunction that would have resulted in the loss of engine power. Fuel was added to the header tank. The engine was started and it ran up to 1,500 rpm prior to the mechanic shutting down the engine.
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: commercial pilot
- Ratings: single-engine land
- Flight time: 2,120 hours in all; 12 in this make and model; 200 in the last 90 days; 20 in the last 30 days
- Medical certificate: Class 2 (valid medical--no waivers/lim.)
- Seat: frt
- Injury: no injuries
The aircraft
- Last inspection: inspection type not recorded
- Maximum gross weight: 1,220 lb
- Seats: 2
- Landing gear: fixed
- Engine: Continental A65 (piston); 0 hours total
The flight
- Departed from: PVT Summit SD at 8:15 pm
- Destination: 1D1 Milbank SD
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: at 4 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 75°F (24°C), dew point 45°F (7°C)
- Altimeter: 30.14 inHg
- Observation at 7:53 pm from ATY, 18 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 | |||
| Passengers | 1 |
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.