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

August 13, 2021 · Piper PA-28-140 · N1651J

Panguitch, UT

Overview

Report Status
Probable Cause
Event Type
Accident
Date
August 13, 2021
Injury Outcomes
No injuries (3 uninjured)
Location
Panguitch, UT
Aircraft
Piper PA-28-140 (1968)
Tail Number
N1651J
Injuries
None
Aircraft Damage
Substantial
NTSB Number
WPR21LA319

The pilot reported that, he conducted a maximum performance takeoff by adding full power and holding the brakes until engine RPM stabilized. The pilot released the brakes, and upon reaching rotation speed, the airplane drifted left. He maneuvered the airplane toward the runway centerline, and it touched down onto the runway briefly before it became airborne again. The airplane ascended to about 100 ft above ground level, before it began descending. The pilot stated that, there was no available runway remaining, so he initiated a forced landing to the uneven terrain ahead. During the landing roll, the airplane struck a fence and vegetation substantially damaging the fuselage. The pilot reported that prior to takeoff, he calculated the airplane’s weight with passengers and fuel, and determined it to be about 20 pounds under the maximum gross weight of the airplane. However, the pilot did not conduct preflight performance calculations prior to takeoff. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation and that if he took more time in preflight preparations, he would have noticed that the density altitude was too high to takeoff. The pilot operating handbook take-off distance vs. density altitude chart states “extrapolation of chart above 7,000 ft. [density altitude] is invalid. The calculated density altitude at the time of the accident was 9,000 ft mean sea level (msl).

NTSB Probable Cause

The airplane’s inability to maintain altitude during the initial climb due to a degradation in the airplane’s performance due to high-density altitude conditions. Contributing to the accident was the pilot’s failure to conduct preflight performance planning calculations.

Full Narrative

The pilot reported that, he conducted a maximum performance takeoff by adding full power and holding the brakes until engine RPM stabilized. The pilot released the brakes, and upon reaching rotation speed, the airplane drifted left. He maneuvered the airplane toward the runway centerline, and it touched down onto the runway briefly before it became airborne again. The airplane ascended to about 100 ft above ground level, before it began descending. The pilot stated that, there was no available runway remaining, so he initiated a forced landing to the uneven terrain ahead. During the landing roll, the airplane struck a fence and vegetation substantially damaging the fuselage. The pilot reported that prior to takeoff, he calculated the airplane’s weight with passengers and fuel, and determined it to be about 20 pounds under the maximum gross weight of the airplane. However, the pilot did not conduct preflight performance calculations prior to takeoff. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation and that if he took more time in preflight preparations, he would have noticed that the density altitude was too high to takeoff. The pilot operating handbook take-off distance vs. density altitude chart states “extrapolation of chart above 7,000 ft. [density altitude] is invalid. The calculated density altitude at the time of the accident was 9,000 ft mean sea level (msl).

Flight

Event TypeAccident
Event Time19:00 MDT
Nearest AirportPanguitch Muni (1nm E)
Runway36
Runway Length5700 ft
Runway Width75 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-140
Tail NumberN1651J
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 · Reciprocating · 140
Seats4

People & Injuries

Injury SummaryNo injuries (3 uninjured)
Fatal0
Serious0
Minor0
Uninjured3
Total3
Crew 1Age 38 · First Class · None

Conditions

ConditionsVMC
LightDaylight
Wind200° @ 5 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point43 F
Altimeter30.31 inHg
Observation Time18:53
Weather SourceWFAC

Appendix: Source Data