Cessna 172 accident near Batavia, Ohio, July 13, 2018
On July 13, 2018 at about 7:40 pm local time, a 2005 Cessna 172, registered N12064, was substantially damaged in an accident during landing near Batavia, Ohio (Clermont County airport). It was an instructional 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 student pilot’s improper landing flare, which resulted in a hard landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 13, 2018 · about 7:40 pm local time
- Place
- Batavia, Ohio · Clermont County · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172 S, built 2005 · all 172s on the register
- Registration
- N12064 · registry record · serial 172S9839
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The solo student pilot reported that, during the landing flare, he pulled back on the controls too sharply and that the airplane then ballooned and landed hard. Unbeknownst to him, the propeller struck the runway, and he then went around the traffic pattern again. He landed and taxied the airplane back to the ramp without further incident. The airplane sustained substantial damage to the firewall and lower fuselage. The student reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
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
- Miscellaneous/other during landing (flare/touchdown)
- Abnormal runway contact during landing (flare/touchdown)
- Hard landing during landing defining event
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Student/instructed pilot
Dual student
- Certificate: student
- Flight time: 205 hours in all
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: unk
- Injury: no injuries
The aircraft
- Last inspection: inspection type not recorded
- Maximum gross weight: 2,300 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming IO-360-L2A (piston); 0 hours total
The flight
- Departed from: I69 Batavia OH
- Destination: I69 Batavia OH
- Flight plan: not recorded
- Runway 22, 3,566 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 050° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 90°F (32°C), dew point 63°F (17°C)
- Altimeter: 30.11 inHg
- Observation at 7:53 pm from KLUK, 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 October 29, 2018. 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 | Record of Conversation - Student Pilot | PDF, 1 page | View Download |
| 2 | Accident Photos | 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.