Cessna 172 N397ES

Summary

On 2 October 2023 at about 19:00 local time, a Cessna 172 registered N397ES was involved in an accident near Arlington, Texas, 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

2 October 2023 at 19:00

Classification

Accident

Location

Arlington, Texas, United States

Coordinates

32.7198, -97.0518

Aircraft

Cessna 172

Registration

N397ES

Category

Airplane

Year built

1997

Engines

1

Operator

Not recorded

Operating rule

Part 91: General Aviation

Purpose of flight

Personal

Phase of flight

Not recorded

Route

Grand Prairie → Unknown

Aircraft damage

Substantial

Weather

VMC

Light

Day

NTSB number

CEN24LA003

2 people had minor injuries.

A reported loss of engine power during the landing approach due to undetermined reasons, which resulted in a forced landing and collision with a fence.

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

Read the full NTSB narrative

The pilot departed on a local flight around the area with a friend. After returning to the airport, he entered the traffic pattern and realized that he had inadvertently extended his downwind leg while explaining the before-landing checklist procedures to the passenger. As the pilot turned the airplane onto the final leg of the traffic pattern, he noticed that the airplane was lower than usual due to the extended downwind and added engine power. The engine did not respond, and he applied full throttle, but the engine still did not respond. After determining that he could not glide the airplane to the airport, the pilot performed a forced landing to a parking lot. After landing, the airplane collided with a fence, resulting in substantial damage to both wings. The pilot secured the engine and egressed the airplane with the passenger. The airplane was recovered to a secure facility for further examination. To prepare the engine for a test run, a repair was performed to one of the engine mounts and a test club replaced the damaged propeller. A fuel can containing 100 low lead fuel was connected to the fuel system to simulate airframe-provided fuel. The firewall fuel strainer was damaged and would leak fuel freely, so the fuel container could not be routed through the header tank. A fuel line was connected directly from the fuel can to the electric fuel pump. The engine was primed and started. The engine parameters were normal, and the engine was able to provide rated horsepower. No anomalies were detected with the engine that would have precluded normal operation. The engine logbook recorded that a mechanic replaced the engine fuel servo before the accident flight. However, the results of the engine run could not be used to determine if the fuel servo contributed to the reported loss of engine power.

Quoted verbatim from the NTSB record.