ERA23LA159
2022-10-27 · Tuskegee, Alabama, United States · Minor · 1 aircraft · Status: Completed
Airport 06A
Current FAA registration · N858AU
- Make / Model
- CESSNA 172S
- Year of manufacture
- 2018 · 4 years old at event
- Engine
- LYCOMING IO-360-L2A (180 hp)
- Seats / Engines
- 4 seats · 1 engine
- Last airworthiness date
- 20180425
- ADS-B equipped
- Yes — Mode-S ABC523
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The flight instructor’s improper flare, which resulted in a hard landing and subsequent runway excursion.
Factual narrative
On October 27, 2022, about 1509 central daylight time, a Textron Aviation Inc. 172S, N858AU, was substantially damaged when it was involved in an accident near Tuskegee, Alabama. The flight instructor sustained minor injuries, and the pilot undergoing instruction was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. The flight instructor reported that he was assessing the abilities of the pilot undergoing instruction. They were practicing short-field landings, and the first landing was uneventful. During the second landing attempt, when the airplane was about 10 to 40 ft above ground level, the airplane’s airspeed decreased, and the sink rate increased. The flight instructor applied full throttle for a go-around, but the engine did not respond. The flight instructor further described that, “Immediately after the rapid application of the throttle to full whilst maintaining all necessary flight control inputs, our sink rate greatly increased, rather than being arrested whatsoever by the addition of full power. We sank as though the power setting had not only remained entirely unchanged but had decreased greatly. I did not have time to reference the engine instruments or the tachometer due to our rapid sink rate and distance from the runway surface, as I pitched to avoid an unrecoverable loss in airspeed.” The airplane subsequently landed hard on the runway and veered left before departing the runway surface. The flight instructor described that after touching down he, “…did not have an opportunity to reach for and pull the throttle to idle from its setting of full power, as my hand had been dislodged from the throttle upon impact. The engine was not producing any sound to indicate it was even running, nonetheless running at the appropriate rate given that the throttle was still set to maximum, with no change made to the aircraft by either occupants. The propeller had almost entirely stopped spinning prior to entering the grass, only striking the grass four times with no prior propeller strike at any point.” The hard landing resulted in a collapse of the left main landing gear and the nose landing gear. Examination of the wreckage also revealed substantial damage to the engine mount and lower fuselage. The flight instructor stated that, after the accident, another flight instructor informed him that the same engine issue happened to her during a go-around the day before and that she reported the issue to the head of the operator’s maintenance department. According to the Federal Aviation Administration principal operations inspector (POI) assigned to the operator, this engine power issue was a fouled spark plug, which the operator corrected before the accident flight. The POI stated the pilot undergoing instruction performed the first short-field landing, and the flight instructor was demonstrating and performing the second landing. Following the accident, POI downloaded data from the airplane’s primary flight display for the accident landing. According to the data, during the final 500 feet of descent toward the landing, the airplane’s indicated airspeed decreased from about 60 knots to about 50 knots as the airplane reached about 50 feet above the ground. During this time the engine rpms varied between about 1,600 to 1,000. In the final 5 seconds before the airplane touched down, the airspeed decreased below 50 knots reaching a low of 25 knots, while the engine rpm remained around 900. As the airplane touched down, the engine rpms rapidly increased to 1,700 rpm, reaching a maximum of nearly 1,900 rpm 2 seconds later, before decreasing again over the next 7 seconds to 0 rpm, while the airplane remained on the ground. The flight instructor was demonstrating a short-field landing to the pilot receiving instruction. The flight instructor reported that, during the landing attempt when the airplane was about 10 to 40 ft above ground level, the airplane’s airspeed decreased, and the sink rate increased. The flight instructor stated that he applied full throttle for a go-around; however, the engine did not respond and may have even further decreased before the airplane landed hard on the runway, resulting in substantial damage to the fuselage. Review of data downloaded from the airplane’s primary flight display revealed that the airplane’s airspeed had decayed from around 50 knots to 25 knots during the landing flare and touchdown, while remaining relatively consistent at around 900 rpm. After touching down the engine power suddenly increased and reached a maximum of 1,800 rpm before then stopping completely about 7 seconds later. The data were not consistent with the flight instructor’s description that the engine power was lost or that the engine did not respond to the throttle inputs during the approach. Rather, the data suggested that the throttle application did not occur until after the airplane had contacted the runway. Following the hard landing, and subsequent runway excursion during which the nose landing gear collapsed, the engine did stop completely, and in his statement the flight instructor expressed surprise that, “…the engine was not producing any sound to indicate it was even running, nonetheless running at the appropriate rate given that the throttle was still set to maximum…” It is possible that this perception may have contributed to the instructor’s recollection of the engine not performing correctly during the accident sequence. Given this information, it is likely that the flight instructor’s improper flare resulted in a hard landing and subsequent runway excursion. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- — Personnel issues-Task performance-Use of equip/info-Aircraft control-Instructor/check pilot
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Not attained/maintained
Verbatim from NTSB's published report. Source file
NTSB_2022_ERA23LA159.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (icing, runway excursion, go-around, maintenance). All research papers
- SKYbrary (Eurocontrol) 2024 · SKYbrary article Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- Embry-Riddle Scholarly Commons 2023 · Faculty research project Reconfigurable Guidance and Control Systems for Emerging On-Orbit Servicing, Assembly, and Manufacturing (OSAM) Space Vehicles
Dynamic response to emergent situations is a necessity in the on-orbit servicing, assembly, and manufacturing (OSAM) field, because traditional on-orbit guidance and control (G&C) cannot respond effic…
- Embry-Riddle Scholarly Commons 2019 · Journal article (IJAAA) Satellite Maintenance: An Opportunity to Minimize the Kessler Effect
Recently, there has been an emphasis on the growing problem of orbital debris. While the advantages of placing satellites into space are numerous, advances in satellite technology combined with the gr…
- Embry-Riddle Scholarly Commons 2015 · Conference paper The Implementation of Safety Management Systems in Maintenance Operations
Literature for Safety Management Systems (SMS) that apply to flight operations is abundant, but there is a limited supply of SMS-related literature for maintenance operations.
- arXiv 2026 · arXiv preprint Enabling Beyond-Visual-Line-of-Sight Drones Operation over Open RAN 5G Networks with Slicing
Among the foretold claims of the transition from 5G to 6G, Beyond-Visual-Line-of-Sight (BVLoS) drone operation has emerged as a prominent Internet-of-Robots enabler.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA) From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…