Cessna 172 accident near Arlington, Texas, October 2, 2023
On October 2, 2023 at about 7:00 pm local time, a 1997 Cessna 172, registered N397ES, was substantially damaged in an accident during approach (VFR pattern final) near Arlington, Texas. It was a personal flight under general aviation rules (Part 91). 2 people had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 2, 2023 · about 7:00 pm local time
- Place
- Arlington, Texas · map
- Type
- Accident
- Injuries
- 2 people had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172 R, built 1997 · all 172s on the register
- Registration
- N397ES · registry record · serial 17280164
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Unknown or undetermined during approach (VFR pattern final) defining event
- Off-field or emergency landing during landing
The NTSB's findings
- Aircraft › Aircraft power plant › Engine (reciprocating) › (general) › Unknown/Not determined
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 96.7 hours in all; 26.8 in this make and model; 21.7 in the last 90 days; 4.4 in the last 30 days; 71 as pilot in command
- Last flight review: May 11, 2023
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 5,365.1 hours
- Last inspection: 100-hour inspection, September 26, 2023; 14.3 hours since
- Maximum gross weight: 2,450 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming IO-360-L2A (piston); 3,418 hours total
The flight
- Departed from: KGPM Grand Prairie TX at 6:39 pm
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 170° at 3 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 90°F (32°C), dew point 59°F (15°C)
- Altimeter: 30.05 inHg
- Observation at 1:57 pm from KGPM, 1 miles away
Weather report (METAR): KGPM 021857Z 17003KT 10SM SKC 32/15 A3005
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
4 documents, released by the NTSB on January 2, 2025. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 11 pages | View Download |
| 2 | Photo | PDF, 2 pages | View Download |
| 3 | Engine Run Summary | PDF, 4 pages | View Download |
| 4 | Engine Log | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.