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

Piper PA-32 accident near Osage Beach, Missouri, May 25, 1996

On May 25, 1996 at about 5:45 pm local time, a Piper PA-32, registered N40933, was substantially damaged in an accident near Osage Beach, Missouri. 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

a partial loss of power for undetermined reasons.

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

What the record shows

Date
May 25, 1996 · about 5:45 pm local time
Place
Osage Beach, Missouri · map
Type
Accident
Injuries
No one was hurt; 4 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-32 · all PA-32s on the register
Registration
N40933 · no longer on the register · serial 32-74-00025
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot reported that within minutes of departure the engine started to lose power but did not quit completely. He reported that the engine was barely above idle. Passengers flying with the pilot also reported that the engine did not sputter but continued to run smoothly at partial power. The pilot reported that he was unable to restore power to the engine and executed a forced landing at a nearby golf course. Due to golfers on the fairways, the pilot was unable to land on the golf course's fairway. The aircraft landed in rough terrain and went through a ravine which produced substantial damage to the aircraft. The examination of the aircraft revealed that fuel was available in all four fuel tanks prior to impact damage. The fuel lines to the engine driven fuel pump were inspected and were intact with no leakage. The electric boost pump was operated and it indicated normal fuel pressure. The engine driven fuel pump was bench tested and operated normally. The engine was test run and operated within specifications.

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
  • Flight time: 374 hours in all; 2 in this make and model; 12 in the last 90 days; 5 in the last 30 days; 120 as pilot in command
  • Medical certificate: Class 2 (valid medical--no waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 3,675 hours
  • Last inspection: annual inspection, October 2, 1995; 25 hours since
  • Maximum gross weight: 3,400 lb
  • Seats: 6
  • Landing gear: fixed
  • Engine: Lycoming O-540-E4B5 (piston); 0 hours total

The flight

  • Departed from: K15 at 7:45 pm
  • Flight plan: none
  • Runway 0

Weather at the time

  • Light: daylight
  • Wind: from 150° at 3 knots
  • Visibility: 7 statute miles
  • Sky: broken clouds at 25,000 ft; scat at 3,500 ft
  • Temperature: 30°F (-1°C), dew point 19°F (-7°C)
  • Altimeter: 30.00 inHg
  • Observation at 4:55 pm from TBN, 40 miles away

Injuries

FatalSeriousMinorNone
Crew1
Passengers3

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.