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 26, 2011 · Piper PA-28-161 · N81917

Quinton, VA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
July 26, 2011
Injury Outcomes
1 injury (1 minor injury)
Location
Quinton, VA
Aircraft
Piper PA-28-161
Tail Number
N81917
Operator
Wings of Carolina Flying Club
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
ERA11CA423

Originally the pilot was going to depart earlier on the day of the accident and had planned to stop enroute to his destination for more fuel. After receiving a weather briefing, he decided to delay his departure until later that evening due to the possibility of thunderstorms being present in the vicinity of his destination airport at his planned time of arrival. Prior to departure that evening, he had the fuel tanks filled to capacity. During the flight, and despite his previous flight planning, he did not stop for more fuel. When he was approximately 64 miles from his destination, the pilot noticed that his fuel gauges were indicating that he had less fuel than he anticipated. Upon arrival at his destination, he flew an instrument approach and advised the air traffic controller that he was low on fuel. Due to the visibility, he was unable to see the runway environment and executed a missed approach. He was then instructed by the air traffic controller to climb to 2,000 feet mean sea level (msl). During the climb, the engine lost power and the airplane began to descend, but the pilot was able to restart the engine. He then began climbing back up to 2,000 feet msl; however, the engine lost power again. The airplane once again began to descend, but this time the pilot was unable to restart the engine. The airplane then struck trees and came to rest after falling approximately 20 feet to the ground. Total duration of the flight was approximately 4 hours and 43 minutes. Postaccident examination of the airplane revealed that the firewall and left wing were substantially damaged and both fuel tanks were absent of fuel. There was no evidence of any preimpact mechanical failure or malfunction of the airplane or engine. Correlation of radar and weather data revealed that the pilot would have encountered a headwind for the majority of the flight. When asked by a state trooper how the accident occurred, the pilot advised him that he had run out of fuel.

NTSB Probable Cause

The pilot's inadequate preflight planning and fuel management, which resulted in a total loss of engine power due to fuel exhaustion.

Full Narrative

Originally the pilot was going to depart earlier on the day of the accident and had planned to stop enroute to his destination for more fuel. After receiving a weather briefing he decided instead to delay his departure until later that evening due to the possibility of thunderstorms being present at his time of arrival in the vicinity of his destination airport. Prior to departure that evening he had the fuel tanks filled to capacity. During the flight despite his previous flight planning, he did not stop for more fuel. When he was approximately 64 miles from his destination, he noticed that his fuel gauges were indicating that he had less fuel than he anticipated. Upon arrival at his destination he flew an instrument approach and advised air traffic control that he was fuel critical, as he had exceeded his estimated flight time, his fuel gauges were indicating a low fuel state, and other aircraft were also landing. Due to the visibility, he was unable to see the runway environment and executed a missed approach. He was then instructed by Air Traffic Control to climb to 2,000 feet above mean sea level (msl). During the climb the engine lost power and the airplane began to descend. The pilot executed the engine restart procedure and was able to get the engine to restart. He then began climbing back up to 2,000 feet msl however, the engine lost power again. The airplane once again began to descend but this time; the pilot was unable to get the engine to restart. The airplane then struck trees and came to rest after falling approximately 20 feet to the ground. Total duration of flight was approximately 4 hours and 43 minutes. Post-accident examination of the airplane by a Federal Aviation Administration inspector revealed that the firewall and left wing were substantially damaged and both fuel tanks were absent of fuel. There was no evidence of any preimpact mechanical failure or malfunction of the airplane or engine. Correlation of radar and weather data revealed that the pilot for the majority of the flight would have encountered headwinds. The airplane was also not equipped with wheel fairings which according to the manufacturer would have further reduced its range by up to 7 percent. When asked how the accident occurred by a state trooper, the pilot advised him that he had run out of fuel.

Flight

Event TypeAccident
Event Time04:15 EDT
Nearest AirportRichmond International Airport (6nm)
Runway25
Runway Length5326 ft
Runway Width100 ft
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-161
Tail NumberN81917
Aircraft CategoryAir
DamageSubstantial
OperatorWings of Carolina Flying Club
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · 0-320-D3G · Reciprocating · 180
Seats4

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 29 · Third Class · Minor

Conditions

ConditionsIMC
LightNight
Wind220° @ 4 kt
Visibility6 sm
CeilingOvercast 600 ft
Altimeter29.76 inHg
Observation Time08:45
Weather SourceWFAC

Appendix: Source Data