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

Cessna 172K accident near Xenia, Ohio, October 19, 2014

On October 19, 2014 at about 10:05 pm local time, a 1969 Cessna 172K, registered N79534, was substantially damaged in an accident during takeoff near Xenia, Ohio (Greene County airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The failure of the seat track mechanism, which led the pilot to inadvertently apply aft yoke and lift his feet off the rudder pedals and resulted in a loss of directional control during takeoff.

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

What the record shows

Date
October 19, 2014 · about 10:05 pm local time
Place
Xenia, Ohio · Greene County · map
Type
Accident
Injuries
1 person was seriously injured.
Weather
visual conditions (good weather)
Aircraft
Cessna 172K P, built 1969 · all 172Ks on the register
Registration
N79534 · no longer on the register · serial 17258157
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The private pilot reported that, during takeoff for the local personal flight, his seat unexpectedly moved rearward, and the seat back tipped rearward. As the seat slid rearward, the pilot inadvertently applied aft yoke and his feet came off the rudder pedals, which resulted in a loss of directional control. The airplane went off the left side of the runway and struck a ditch, which resulted in substantial damage to the airplane. A postaccident examination of the pilot seat revealed that the forward outboard metal tang on the seat base that retained the base to the track was deformed. The forward outboard position of the base also contained the locking pin mechanism that adjusted the seat fore and aft and locked the seat into position. The deformation of the metal tang likely allowed the seat to become detached from the track and disengaged the locking pin, which allowed the seat to slide rearward. The seat back structure would not lock in any position after the accident. The reason why the seat back could not lock in position could not be determined. The Federal Aviation Administration had previously issued an airworthiness directive (AD), which required repetitive inspections of the seat mechanism, including inspections of the tangs on the seat base. A review of airplane's maintenance records showed that the inspections had been performed in accordance with the AD. The deformation of the tang was consistent with a lateral deformation due to a sideways force, but it could not be determined if the deformation was present during the most recent inspection. A review of the airplane maintenance discrepancy records showed that, the day before the accident, a different pilot had entered a maintenance discrepancy, which noted that the "left seat slid back three times during flight." The following day, a mechanic repaired the hold-down spring and returned the airplane to service. After that repair and before the accident flight, another pilot entered a maintenance discrepancy, which noted that the "left front seat was in the reclined position and would not lock in the upright position." The records showed that the discrepancy had not been corrected before the accident flight. It could not be determined whether or not the accident pilot was aware of the previous discrepancy reports.

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. Loss of control on ground during takeoff defining event
  2. Runway excursion during takeoff

The NTSB's findings

  • cause Aircraft › Aircraft structures › (general) › (general) › Failure
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Attain/maintain not possible

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 178 hours in all; 17 in this make and model; 6 in the last 90 days; 2 in the last 30 days; 68 as pilot in command; 0 on instruments
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Airframe total time: 5,565 hours
  • Last inspection: 100-hour inspection, July 16, 2014
  • Maximum gross weight: 2,299 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320 SERIES (piston); 0 hours total
  • Operator: Macair Aviation LLC

The flight

  • Departed from: I19 Xenia OH at 10:05 pm
  • Destination: I19 Xenia OH
  • Flight plan: none
  • Runway 25, 4,500 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 220° at 5 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 25,000 ft; a few clouds at 20,000 ft
  • Temperature: 54°F (12°C), dew point 36°F (2°C)
  • Altimeter: 30.11 inHg
  • Observation at 9:58 pm from FFO, 11 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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.