NTSB CAROL · Event
Event CEN20LA214
Aircraft involved
Probable cause & findings
A high velocity descent and impact with terrain for undetermined reasons.
Factual narrative
HISTORY OF FLIGHTOn June 6, 2020, at 1523 eastern daylight time, a Cessna 172 airplane, N13520, was destroyed when it was involved in an accident near New Washington, Indiana. The student pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. According to the pilot’s flight instructor, the pilot was to conduct a solo practice flight in preparation for his private pilot check ride. The flight was to include maneuvers in the northeast practice area, which is near New Washington. The flight instructor stated that he tracked the airplane on his phone and the flight track disappeared about 20 minutes into the flight. The pilot was supposed to return by 1700. The recorded automatic dependent surveillance-broadcast (ADS-B) data revealed that the airplane departed Bowman Field Airport (LOU), Louisville, Kentucky, at 1509, proceeded northeast along the Ohio River, and climbed to about 3,000 ft above ground level (agl). About 2 nautical miles south of New Washington, the airplane completed 3 consecutive left steep turn maneuvers (see figure 1) and remained about 3,000 ft agl. At 1523:09 the airplane descended and proceeded southeast; this flight track continued into a steep dive in excess of 10,000 ft per minute and a calculated groundspeed of about 170 kts. The final ADS-B data point was recorded at 1523:34 and 165 ft agl. Figure 1 – Accident flight path with the initial impact point overlaid on a Google Earth map. PERSONNEL INFORMATIONThe flight instructor stated that he and the student pilot had flown together the day before the accident when they completed a “mock check ride” in preparation for the student's private pilot check ride, which was scheduled for 6 days later. The flight instructor added the student was well prepared to pass the check ride, but that the student had asked permission for another solo flight for additional practice. The flight instructor stated that the student was “one of his best” and that he was “always well prepared.” WRECKAGE AND IMPACT INFORMATIONThe airplane wreckage was located in a field and the initial impact point was identified by a few shallow craters and disturbance of dirt (see Figure 2). The wreckage path was oriented on a 130° heading and extended about 300 yards. All major components of the airplane were located at the accident site and there was no post impact fire. The responding Federal Aviation Administration inspectors completed an initial examination of the wreckage debris, which was scattered across the field. The propeller had separated from the engine and was found about 30 yards from the initial impact. The wings both separated from the fuselage at the wing roots and were about 100 yards from the initial impact point. The engine separated from its mount and was about 220 yards from the initial impact point. The farthest piece of wreckage was a portion of the left fuel tank and filler port. Figure 2 – Aerial view of the accident site and wreckage debris path (Source: Indiana State Police). A postaccident examination revealed that the airframe exhibited significant impact damage and separations. The flight cables remained attached to their respective control surfaces, and control continuity was confirmed through several tensile overload separations in the cockpit area. The engine sustained significant impact damage and most accessories were impact separated. The crankshaft was manually rotated through with binding noted during rotation due to the impact damage. Continuity of the crankshaft to the rear gears and to the valve train was confirmed. When the crankshaft was rotated, compression and suction were obtained for each cylinder. One propeller blade exhibited longitudinal twisting toward the blade face and was impact separated about midspan. The outboard portion of the blade was not observed. The other blade was bent aft about 100° and exhibited longitudinal twisting toward the blade face, leading/trailing edge gouges, and “S” bending. There were no anomalies with the engine or airframe that would have precluded normal operation. MEDICAL AND PATHOLOGICAL INFORMATIONAn autopsy of the pilot was performed by the Scott Funeral Home, Jeffersonville, Indiana, and authorized by the Clark County Chief Deputy Coroner, Clark County, Indiana. The cause of death was multiple blunt force injuries and the manner of death was accident. Toxicology testing performed at the FAA Forensic Sciences Laboratory found no drugs of abuse. The student pilot was to conduct a solo practice flight in preparation for his private pilot check ride. The flight was to include maneuvers in a specific practice area. The pilot’s flight instructor stated that he tracked the airplane on his phone and the flight track disappeared about 20 minutes into the flight. The recorded automatic dependent surveillance-broadcast data revealed that the airplane departed and climbed to about 3,000 ft above ground level. While in the practice area, the airplane completed 3 consecutive left steep turn maneuvers towards the northeast and remained about 3,000 ft agl. Less than 1 minute later the airplane descended and proceeded southeast; this flight track continued into a steep dive in excess of 10,000 ft per minute and a calculated groundspeed of about 170 kts. The airplane wreckage was located in a field; the debris path was oriented southeast and extended about 300 yards. All major components of the airplane were located at the accident site and there was no post impact fire. Postaccident examinations revealed findings indicative of the engine operating at the time of the accident, which were also consistent with the high velocity descent. There were no mechanical malfunctions or anomalies found with the engine or airframe that would have precluded normal operation. No medical findings were identified in the pilot’s autopsy or toxicology. The accident is consistent with a wings-level, high velocity descent and impact with terrain for reasons that could not be determined with the available information. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Altitude-Not attained/maintained
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent rate-Incorrect use/operation
- — Personnel issues-Task performance-Use of equip/info-Aircraft control-Student/instructed pilot
Verbatim from NTSB's published report. Source file
NTSB_2020_CEN20LA214.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type. Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2019 · Conference Paper
Crash Testing and Simulation of a Cessna 172 Aircraft: Pitch Down Impact Onto Soft Soil
During the summer of 2015, NASA Langley Research Center conducted three full-scale crash tests of Cessna 172 (C-172) aircraft at the NASA Langley Landing and Impact Research (LandIR) Facility.
- NASA NTRS 2019 · Technical Memorandum (TM)
Simulating the Impact Response of Three Full-Scale Crash Tests of Cessna 172 Aircraft
During the summer of 2015, a series of three full-scale crash tests were performed at the Landing and Impact Research Facility located at NASA Langley Research Center of Cessna 172 aircraft.
- Embry-Riddle Scholarly Commons 2023 · Conference paper
Validation of Training Satisfaction Survey
The Training Satisfaction Survey (TSS) was developed as part of a larger project to examine the features of Virtual Reality software and supporting devices as a training program on visual illusions an…
- Semantic Scholar 2021 · Article (Data in Brief)
Cockpit voice recorder transcript data: Capturing safety voice and safety listening during historic aviation accidents
Cockpit Voice Recorder (CVR) transcripts capture audio data within cockpit environments. This aids the investigation of causal factors contributing to aviation accidents by revealing communication and…
- Semantic Scholar 2021 · Article (Safety Science)
Safety voice and safety listening during aviation accidents: Cockpit voice recordings reveal that speaking-up to power is not enough
Abstract Safety voice is theorised as an important factor for mitigating accidents, but behavioural research during actual hazards has been scant.
- Embry-Riddle Scholarly Commons 2021 · Journal article (JAAER)
Can Backward-Chained, Ab-Initio Pilot Training Decrease Time to First Solo?
Flight simulation has made progressively significant inroads into pilot training at all levels of a pilot’s career – typically starting with training for the Instrument rating in light aircraft and co…
Browse the full corpus — academia portal ↗