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

Piper PA-22-108 accident near Forsyth, Missouri, January 4, 2014

On January 4, 2014 at about 1:49 am local time, a 1960 Piper PA-22-108, registered N4505Z, was substantially damaged in an accident during enroute (cruise) near Forsyth, Missouri. 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

The pilot's improper flight planning, which resulted in a total 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
January 4, 2014 · about 1:49 am local time
Place
Forsyth, Missouri · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-22-108, built 1960 · all PA-22-108s on the register
Registration
N4505Z · no longer on the register · serial 22-8006
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, while in cruise flight, the airplane experienced a total loss of engine power about 8 miles from the intended destination. The pilot was unable to restart the engine, and he subsequently ditched the airplane in a lake. A postaccident examination of the engine did not reveal any mechanical anomalies that would have prevented normal operation. No fuel was found in the fuel system during the postaccident examination; however, the airplane had been submerged for nearly 1 week before it was recovered from the lake. Postaccident performance calculations indicated that it is likely that the engine lost power due to fuel exhaustion during the accident flight. Although the pilot reported that he had completed preflight planning calculations (the actual paperwork was lost during the accident), the investigation determined that the wind aloft values that the pilot likely used in his preflight planning calculations were significantly different from the actual wind aloft values. As a result, the airplane's actual ground speed was significantly less than what the pilot would have anticipated. The pilot also reported that he completed the accident flight at less than 65-percent engine power, which would have increased the length of the flight and the amount of fuel used during it when compared to higher engine power settings; the available cruise performance charts lacked true airspeed and engine speed data for operating below 65-percent engine power. Therefore, the pilot could not have estimated the total flight time and fuel required for the accident flight with a high level of accuracy. Additionally, the pilot reported that the mixture control cable had fractured during a previous flight and, to continue his cross-country trip, he safety-wired the carburetor mixture control arm in the full-rich position. As a result, the pilot was unable to properly lean the fuel mixture during the accident flight; however, it is unknown to what extent the pilot planned for this condition. Further, the pilot made an unplanned stop at an airport located along his planned route of flight. The additional fuel consumed during this unplanned stop (taxi, engine run-up, takeoff, and climb to cruise altitude) would have further reduced the amount of fuel available to complete the accident flight.

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 enroute (cruise)
  2. Loss of engine power (total) during enroute (cruise) defining event
  3. Off-field or emergency landing during landing
  4. Ditching during landing

The NTSB's findings

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

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 160 hours in all; 18 in this make and model; 30 in the last 90 days; 20 in the last 30 days; 100 as pilot in command; 0 on instruments
  • Last flight review: March 26, 2013
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 2,531 hours
  • Last inspection: annual inspection, May 11, 2013; 24 hours since
  • Maximum gross weight: 1,650 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming O-235-C1B (piston); 2,531 hours total

The flight

  • Departed from: UUV Sullivan MO at 11:00 pm
  • Destination: PLK Branson MO
  • Flight plan: none

Weather at the time

  • Light: night
  • Wind: from 150° at 12 knots, gusting 18
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 28°F (-2°C), dew point 12°F (-11°C)
  • Altimeter: 30.05 inHg
  • Observation at 1:45 am from BBG, 10 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

12 documents, released by the NTSB on January 31, 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.