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

July 4, 2022 · Piper PA-32-300 · N1403X

Mount Pleasant, TX

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
July 4, 2022
Injury Outcomes
4 injuries (1 fatality, 3 serious injuries)
Location
Mount Pleasant, TX
Aircraft
Piper PA-32-300 (1975)
Tail Number
N1403X
Injuries
Fatal
Aircraft Damage
Destroyed
NTSB Number
CEN22FA299

The pilot was established on final approach for landing in night visual conditions. The airplane tracked inbound along the approach course until, about 0.40 mile from the runway, it impacted trees and terrain. A witness reported that the airplane seemed to be right overhead when he first heard it, and about one second later he heard it impact trees. He noted that the engine sounded like it was at maximum power. The outboard portion of the right wing was located at the initial tree strike, and the inboard portion of the right wing was located within the debris path. A ground impact path began about 160 ft from the tree strike, and the main wreckage, which consisted of the fuselage, left wing, empennage, and engine, came to rest about 320 ft from the initial tree strike. An examination of the airframe and engine identified no anomalies consistent with a preimpact failure or malfunction. The runway was equipped with precision approach path indicators (PAPI). During the onsite investigation the day after the accident, the PAPI lights were illuminated. A review of airplane position data revealed that the airspeed was about 78 knots while on final approach. The aerodynamic stall speed was 62 knots with the wing flaps retracted and 55 knots with them extended. The descent rate during that period was within the capabilities of the airplane.

NTSB Probable Cause

The pilot’s failure to maintain the proper glidepath while on final approach in night visual conditions, which resulted in a collision with trees.

Full Narrative

HISTORY OF FLIGHTOn July 3, 2022, at 2244 central daylight time, a Piper PA-32-300 airplane, N1403X, was destroyed when it was involved in an accident near Mt. Pleasant, Texas. The pilot and two passengers were seriously injured. The pilot-rated passenger was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Automatic dependent surveillance – broadcast (ADS-B) data revealed that the visual flight rules flight departed from the Memorial Field Airport (HOT), Hot Springs, Arkansas, about 2145, and proceeded direct to the Mt. Pleasant Regional Airport (OSA), Mt. Pleasant, Texas. The pilot climbed to a cruise altitude of about 8,500 feet before beginning a descent about 30 miles from the destination airport. About 4 miles from OSA, the pilot entered the airport traffic pattern on a left base leg for runway 17. About 1.5 miles from the runway 17 threshold the airplane was established on final approach at 700 ft mean sea level (recorded geometric altitude). The recorded altitudes from the time the plane became established on final approach until the last ADS-B data point showed a consistent descent without any major disturbances. The final ADS-B data point was received at 2244:45 when the airplane was about 0.42 miles from the runway arrival threshold. A witness located immediately north of the airport along the extended runway centerline reported hearing the airplane. He noted that it seemed to be right overhead when he first heard it and, approximately one second later he heard the airplane impact the trees on the opposite side of the road. He described the engine as sounding “strong” and at “maximum power,” emphasizing that the airplane seemed to be “at full throttle.” The witness also commented that the weather that night was “clear and nice.” PERSONNEL INFORMATIONThe pilot had logged 9.3 hours of night flight time in the 30 days before the accident. His most recent night flight occurred about 3 weeks before the accident flight. He logged three night landings during that flight. METEOROLOGICAL INFORMATIONOn the day of the accident, the sun set at 2033 and civil twilight ended at 2101. The moon was in a waxing crescent phase with 19% of the visible disk illuminated. Moon transit was at 1707 and set at 2353. WRECKAGE AND IMPACT INFORMATIONThe airplane impacted trees and terrain less than one-half mile from the runway 17 arrival threshold. The right wing separated, and the outboard 4-foot section was suspended in a tree about 50 ft above ground level. The wing tip was resting on the ground near the tree. Tree branches exhibiting fresh breaks were also near the initial tree strike. The remaining inboard section of the right wing was separated at the root and located along the debris path. A ground impact path began about 160 ft from the initial tree strike and extended to the main wreckage, and the main wreckage was located about 320 ft from the initial tree strike. The main wreckage consisted of the fuselage, empennage, left wing, engine, and propeller. The fuselage was inverted and resting on the left wing, which was separated at the root. The main wreckage was at an approximate elevation of 385 ft msl. An examination of the airframe and engine revealed no anomalies consistent with a preimpact failure or malfunction. The altimeter setting was 29.98 in Hg when observed during the airframe examination. TESTS AND RESEARCHA review of position data revealed that, while on final approach, the airplane’s airspeed varied from about 74 knots to 78 knots, and the descent rate was between 280 fpm and 700 fpm. According to the airplane pilot’s operating manual, the aerodynamic stall speed was 62 knots and 55 knots with the wing flaps retracted and fully extended, respectively.

Flight

Event TypeAccident
Event Time22:44 CDT
Nearest AirportMount Pleasant Rgnl (0.8nm N)
Runway17
Runway Length6004 ft
Runway Width100 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-32-300
Tail NumberN1403X
Aircraft CategoryAir
DamageDestroyed
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-540-K1A5 · Reciprocating · 300
Seats6

People & Injuries

Injury Summary4 injuries (1 fatality, 3 serious injuries)
Fatal1
Serious3
Minor0
Uninjured0
Total4
Crew 1Age 49 · Third Class · Serious

Conditions

ConditionsVMC
LightNight
Wind100° @ 4 kt
Visibility10 sm
CeilingNone
Altimeter30.00 inHg
Observation Time22:50
Weather SourceWFAC

Appendix: Source Data