Skip to content

ERA24LA352

2024-07-19 · Danville, Kentucky, United States · None · 1 aircraft · Status: Completed

Airport DVK

Current FAA registration · N9991E

Make / Model
CESSNA 172N
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19790714
ADS-B equipped
Yes — Mode-S ADF692

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot’s failure to maintain control of the airplane while landing and his inadequate communication to the pilot-rated passenger of her role during the flight.

Factual narrative

The private pilot (who was the pilot-in-command for the flight) was flying with two passengers, one of whom was seated in the right front pilot seat, held a commercial pilot certificate, and had more flight experience than the private pilot. The pilot-rated passenger in the right front seat reported that during the approach, she had commented to the pilot twice about the airplane’s airspeed, and that she had nudged the yoke forward with one finger as an indication to the pilot to lower the nose; however, the pilot pulled back on the yoke and added power to cushion the landing, which resulted in several bounces on the runway before the airplane traveled off the left side. She further described that the landing flare occurred while the airplane too high above the runway and at too slow a speed, about 15 ft above the runway and at an airspeed decreasing to less than 50 knots. The pilot reported that during the landing attempt, after the pilot-rated passenger pushed the yoke forward, he pulled back because he did not want the nose of the airplane to strike the runway first, which resulted in a hard landing and subsequent bounce. As the pilot was attempting to regain control of the airplane, the pilot-rated passenger increased the engine power to full in attempt to abort the landing, but the airplane then veered to the left and departed the runway surface. The airplane came to rest upright in a grass area next to the runway. The fuselage was substantially damaged during the accident sequence. The pilot reported that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation. He also stated that, “…we will need to improve the communication between me as the PIC and [any pilot-rated passengers] such as informing me of their concern rather than touching the control, especially during landing.” 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-Pilot
  • — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Not attained/maintained
  • — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained
  • — Personnel issues-Task performance-Communication (personnel)-Lack of communication-Pilot

Verbatim from NTSB's published report. Source file NTSB_2024_ERA24LA352.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

Matched on aircraft type. All research papers