Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

October 2, 2023 · Cessna 172 R · N397ES

Arlington, TX

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
October 2, 2023
Injury Outcomes
2 injuries (2 minor injuries)
Location
Arlington, TX
Aircraft
Cessna 172 R (1997)
Tail Number
N397ES
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
CEN24LA003

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.

NTSB 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.

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.

Flight

Event TypeAccident
Event Time14:00 CDT
Nearest Airport0nm
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172 R
Tail NumberN397ES
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-360-L2A · Reciprocating · 160
Seats4

People & Injuries

Injury Summary2 injuries (2 minor injuries)
Fatal0
Serious0
Minor2
Uninjured0
Total2
Crew 1Age 26 · First Class · None

Conditions

ConditionsVMC
LightDaylight
Wind170° @ 3 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point59 F
Altimeter30.05 inHg
Observation Time13:57
Weather SourceWFAC

Appendix: Source Data