Cessna 172S N1254D

Summary

On 26 May 2024 at about 23:47 local time, a Cessna 172S registered N1254D was involved in an accident near Pierson, Florida, United States. 2 people were on board and 2 had minor injuries. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

Date

26 May 2024 at 23:47

Classification

Accident

Location

Pierson, Florida, United States

Nearest airport

Pierson Muni (2J8)

Coordinates

29.0000, -81.0000

Aircraft

Cessna 172S

Registration

N1254D

Category

Airplane

Year built

2006

Engines

1

Operator

Not recorded

Operating rule

Part 91: General Aviation

Purpose of flight

Instructional

Phase of flight

Not recorded

Aircraft damage

Substantial

Weather

VMC

Light

Night

NTSB number

ERA24LA231

2 people had minor injuries.

The flight instructor’s failure to attain a proper touchdown point during a precautionary landing, which resulted in a runway excursion during landing.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

The private pilot and the flight instructor had been practicing emergency engine-out procedures in preparation for the private pilot’s commercial checkride. The pilot stated that he just completed the emergency procedure for a simulated engine fire, which evolved into a simulated loss of engine power. He entered a steep spiral over the airport from 2,500 ft mean sea level (msl) to lose altitude and entered the left downwind leg of the traffic pattern at 1,200 ft msl. The private pilot said that while turning from downwind to base, the flight instructor suddenly took control of the airplane because the engine oil temperature annunciator illuminated. The flight instructor made a sharp turn onto final approach and declared an emergency. The airplane was high, so the flight instructor extended the flaps and performed a maximum forward slip to lose altitude. The airplane touched down more than halfway down the 2,600-ft-long turf runway before contacting a ditch, and then nosed over. The airplane’s vertical stabilizer/rudder and a wing strut were substantially damaged during the accident sequence. The pilot said the engine never lost power and was operating right up until impact. The flight instructor said he had experienced an emergency about three months prior to the accident due to a cracked engine case, during which the engine was loud and would vibrate when he applied full power. He said he did not want to add power to go-around because he was concerned that he was dealing with similar scenario or that the engine would catch fire due to the high oil temperature. A postaccident test-run of the engine was conducted utilizing the airplane’s existing fuel and oil systems. The engine started immediately, and all engine parameters were normal. A separate functional test of the oil temperature probe revealed that it operated within normal range. No mechanical deficiencies were noted with the engine that would have precluded normal operation. According to flight data downloaded from the airplane’s digital avionics, each time the throttle was decreased to idle while performing the engine out simulations, there was a progressive increase in oil temperature. As such, it is most likely that the engine did not have time to cool down in between each engine-out simulation and the oil temperature gradually increased until the annunciator came on.

Quoted verbatim from the NTSB record.