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

June 13, 1999 · Cessna 172P · N5494K

Seymour, TN

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
June 13, 1999
Injury Outcomes
2 injuries (2 minor injuries)
Location
Seymour, TN
Aircraft
Cessna 172P
Tail Number
N5494K
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
MIA99LA182

The pilot stated that he had flown into the airstrip a minimum of 15 times and during the first approach, he recognized that he flight was high. He performed a go-around, orbited the airport 1 time to allow for departing traffic, then reentered the traffic pattern to land. While over the approach end of the runway with the flaps fully extended, he recognized that the flight was again 'high' but thought sufficient runway remained after landing to stop the airplane. The airplane was landed 'too far down the runway to be able to stop...', and he retracted the flaps to 10 degrees, applied full power, and began to climb. During the climb the left main landing gear collided with a marked power line. The airplane then collided with trees, a fence, and came to rest upright. The pilot further stated that there was no engine failure or malfunction. Examination of the airplane by an FAA airworthiness inspector revealed control continuity for roll, pitch, and yaw.

NTSB Probable Cause

The failure of the pilot to perform a go-around earlier resulting in a long landing, insufficient runway remaining to stop, and subsequent in flight collision with a marked power line during an aborted landing.

Full Narrative

On June 13, 1999, about 0915 eastern daylight time, a Cessna 172P, N5494K, registered to and operated by Morristown Flying Service, Inc., collided with a power line and trees during takeoff following an aborted landing at Seymour Air Park, Inc., a private airtrip located near Seymour, Tennessee. Visual meteorological conditions prevailed at the time and no flight plan was filed for the 14 CFR Part 91 personal flight. The airplane was substantially damaged and the commercial-rated pilot and pilot-rated passenger sustained minor injuries. The flight originated about 0840, from the Moore-Murrell Airport, Morristown, Tennessee. The pilot stated that after departure, the flight proceeded to Coopers Field then to Seymour Air Park, Inc., where the flight entered the traffic pattern for landing on runway 25. The flight turned onto final approach and recognizing that the flight was too high, the pilot performed a go-around and orbited the airport once to allow for departing traffic. The flight reentered the traffic pattern and while over the approach end of the runway with the flaps fully extended, the pilot noted that the flight was again too high but thought there was sufficient room to land. The airplane was landed "...too far down the runway to stop before going off the end so I applied full power, flaps to 10 degrees, & began to climb." During the climb, the left main landing gear collided with the top marked power line. The airplane then collided with trees about 25 feet agl, 1,200 feet from the power line contact, impacted a fence, and came to rest upright. The pilot further stated that he had flown into that airstrip a minimum of 15 times and there was no engine failure or malfunction. The airplane was determined to have come to rest on a magnetic heading of 010 degrees. Examination of the airplane by an FAA airworthiness inspector revealed that about 5 feet of length of the leading edge of the left wing and the left wingtip were separated. The engine/propeller assembly was displaced up approximately 15 degrees and to the left approximately 90 degrees from the normally installed position with the propeller hub and one of the propeller blades resting against and above the leading edge and the upper wing skin surface, respectively. The nose landing gear was sheared off and continuity of the flight controls for yaw, roll, and pitch was confirmed.

Flight

Event TypeAccident
Event Time09:15 EDT
Nearest AirportSeymour Air Park, Inc. (0nm WSW)
Runway25
Runway Length2300 ft
Runway Width100 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172P
Tail NumberN5494K
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O320-D2J · Reciprocating · 160
Seats4

People & Injuries

Injury Summary2 injuries (2 minor injuries)
Fatal0
Serious0
Minor2
Uninjured0
Total2
Crew 1Age 25 · Second Class

Conditions

ConditionsVMC
LightDaylight
Wind3 kt
Visibility5 sm
CeilingNone
Temperature / Dew Point66 F
Altimeter30.00 inHg
Observation Time12:53
Weather SourceWFAC

Appendix: Source Data