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

December 26, 2022 · Cessna 177 B · N177D

Franklin, VA

Overview

Report Status
Probable Cause
Event Type
Accident
Date
December 26, 2022
Injury Outcomes
1 injury (1 minor injury)
Location
Franklin, VA
Aircraft
Cessna 177 B (1973)
Tail Number
N177D
Operator
Barger Randall G
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
ERA23LA094

The private pilot departed with full fuel tanks for the cross-country flight with a planned fuel stop en route. As the pilot neared the fuel stop airport, the fuel gauges indicated 3/4 capacity remaining, so he elected to continue to his destination airport. When the flight was 38 miles from the destination, with the fuel selector on the right tank position, the engine “started sputtering.” He then moved the fuel selector to the left tank position and turned the airplane towards a diversion airport. He checked the weather and NOTAMs for the diversion airport and noted nothing that concerned him. As he approached the diversion airport, he keyed the airplane’s radio transmitter 5 times and then 7 times on the common traffic advisory frequency to turn on the runway lights, but they did not turn on (the end of civil twilight had occurred about an hour prior). Concerned about the airplane’s fuel level, he landed but did not know how far down the runway he had landed. He described that the approach was “too fast” and the airplane bounced. After touching down, he applied the brakes but realized he would be unable to stop the airplane on the remaining portion of the runway. He added full power, started to climb, and thinking that the airplane had climbed higher than it actually had, he then banked left. The airplane’s left wing then collided with trees substantially damaging it and bringing the airplane to a stop. The pilot stated that there were no mechanical malfunctions or failures of the airplane that would have precluded normal operation. He also stated that had he known the runway lights were inoperative, he would have diverted to a different airport. Postaccident examination of the airplane revealed the airplane’s radios were tuned to the correct frequency to activate the runway lights. According to the airport manager, the pilot-controlled lighting system at the airport was normally checked on the 1st day of every month and had been last checked 25 days before the accident. Following the accident, he discovered that they were inoperative. Given this information, it is possible that the pilot could have performed a successful landing had the runway lights been operational.

NTSB Probable Cause

The pilot’s failure to maintain clearance from trees during the initial climb following an aborted precautionary landing. Contributing to the outcome were the inoperative runway lights, which reduced the likelihood that the pilot could successfully land the airplane on the runway at night.

Full Narrative

The private pilot departed with full fuel tanks for the cross-country flight with a planned fuel stop en route. As the pilot neared the fuel stop airport, the fuel gauges indicated 3/4 capacity remaining, so he elected to continue to his destination airport. When the flight was 38 miles from the destination, with the fuel selector on the right tank position, the engine “started sputtering.” He then moved the fuel selector to the left tank position and turned the airplane towards a diversion airport. He checked the weather and NOTAMs for the diversion airport and noted nothing that concerned him. As he approached the diversion airport, he keyed the airplane’s radio transmitter 5 times and then 7 times on the common traffic advisory frequency to turn on the runway lights, but they did not turn on (the end of civil twilight had occurred about an hour prior). Concerned about the airplane’s fuel level, he landed but did not know how far down the runway he had landed. He described that the approach was “too fast” and the airplane bounced. After touching down, he applied the brakes but realized he would be unable to stop the airplane on the remaining portion of the runway. He added full power, started to climb, and thinking that the airplane had climbed higher than it actually had, he then banked left. The airplane’s left wing then collided with trees substantially damaging it and bringing the airplane to a stop. The pilot stated that there were no mechanical malfunctions or failures of the airplane that would have precluded normal operation. He also stated that had he known the runway lights were inoperative, he would have diverted to a different airport. Postaccident examination of the airplane revealed the airplane’s radios were tuned to the correct frequency to activate the runway lights. According to the airport manager the, pilot-controlled lighting system at the airport was normally checked on the 1st day of every month and had been last checked 25 days before the accident. Following the accident, he discovered that they were inoperative. Given this information, it is possible that the pilot could have performed a successful landing had the runway lights been operational.

Flight

Event TypeAccident
Event Time15:35 EST
Nearest AirportFranklin Regional Airport (1nm)
Runway9
Runway Length4977 ft
Runway Width100 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 177 B
Tail NumberN177D
Aircraft CategoryAir
DamageSubstantial
OperatorBarger Randall G
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-360-A1F6D · Reciprocating · 180
Seats4

People & Injuries

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

Conditions

ConditionsVMC
LightNight
WindCalm
CeilingNone
Temperature / Dew Point38 C / 2 C
Altimeter30.27 inHg
Observation Time20:35
Weather SourceWFAC

Appendix: Source Data