N397ES accident

NTSB CEN24LA003 · 2023-10-02 · Arlington, TX

Docket — crew, injuries and powerplant

Summary

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.

Full narrative

On October 2, 2023, about 1400 central daylight time, a Cessna 172R airplane, N397ES, was substantially damaged when it was involved in an accident near Arlington, Texas. The pilot and passenger sustained minor injuries. The airplane was operated under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight.

The pilot departed from the Grand Prairie Municipal Airport (GPM), Grand Prairie, Texas, with the intention of conducting a 30-minute flight around the local 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 GPM, 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.

Probable cause

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. The National Transportation Safety Board determined the probable cause of this accident.

Circumstances

Event type
Accident
Highest injury
Minor
Weather conditions
Visual Meteorological Cond
Light condition
Day
Sky condition
NONE
Ceiling (ft)
0
Visibility (sm)
10
Wind direction
170
Wind speed (kt)
3
Temperature (F)
90
Distance from field
0.0

Aircraft

RegistrationMakeModelDamageFAR part
N397ES — — SUBS 091

Sequence of events

#OccurrencePhase
2 Approach-VFR pattern final Unknown or undetermined defining Cruise
3 Landing Off-field or emergency landing Cruise

Findings

Finding
Aircraft-Aircraft power plant-Engine (reciprocating)-(general)-Unknown/Not determined cause