Cessna 172 accident near Fulton, Missouri, August 14, 2016
On August 14, 2016 at about 4:00 pm local time, a 1968 Cessna 172, registered N78242, was substantially damaged in an accident during landing near Fulton, Missouri (Elton Hensley Memorial airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s improper landing flare and subsequent improper recovery from a bounced landing, which resulted in the airplane porpoising.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 14, 2016 · about 4:00 pm local time
- Place
- Fulton, Missouri · Elton Hensley Memorial · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172 K, built 1968 · all 172s on the register
- Registration
- N78242 · registry record · serial 17257543
- 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 during the initial touchdown he "got a bad bounce." On the third bounce the nose wheel "gave way and the propeller impacted the ground." The airplane sustained substantial damage to the firewall. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The Federal Aviation Administration has published the Airplane Flying Handbook FAA-H-8083-3B (2016). This handbook discusses porpoising and states in part: In a bounced landing that is improperly recovered, the airplane comes in nose first initiating a series of motions that imitate the jumps and dives of a porpoise. The problem is improper airplane attitude at touchdown, sometimes caused by inattention, not knowing where the ground is, miss-trimming or forcing the airplane onto the runway. Ground effect decreases elevator control effectiveness and increases the effort required to raise the nose. Not enough elevator or stabilator trim can result in a nose low contact with the runway and a porpoise develops. Porpoising can also be caused by improper airspeed control. Usually, if an approach is too fast, the airplane floats and the pilot tries to force it on the runway when the airplane still wants to fly. A gust of wind, a bump in the runway, or even a slight tug on the control wheel will send the air plane aloft again.
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 defining event
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 413 hours in all; 77 in this make and model; 413 as pilot in command
- Last flight review: April 16, 2015
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 3,698 hours
- Last inspection: annual inspection, May 1, 2016
- Maximum gross weight: 2,300 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320-E2D (piston); 1,746 hours total
The flight
- Departed from: VER Boonville MO at 3:25 pm
- Destination: FTT Fulton MO
- Flight plan: none
- Runway 18, 4,001 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 150° at 8 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 81°F (27°C), dew point 68°F (20°C)
- Altimeter: 30.10 inHg
- Observation at 3:54 pm from KCOU, 10 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
2 documents, released by the NTSB on December 7, 2016. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Accident Photos (Courtesy of FAA) | PDF, 2 pages | View Download |
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.
