Overall Trends
Total, fatal, and serious accidents in the selected range.
Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.
Fast key and full-text search with live filters, watches, and precise metadata.
Use quotes for exact phrase matches (for example "fuel selector valve").
Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.
Major cases, deep-report coverage, and investigation media across decades of NTSB history.
Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.
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.
Phillipi, WV
The pilot said he entered the traffic pattern, performed his base and final turns, and configured the airplane for landing. The pilot said that on short final, he began his level off and flare prematurely. He said, 'I just ballooned high and had a hard landing. That's all there is to it.'
The pilot's improper flare that resulted in a hard landing.
On November 21, 1999, at 1430 eastern standard time, a Cessna 172XP, N758LR, was substantially damaged during a hard landing to the Phillipi/Barbour County Airport (79D), Phillipi, West Virginia. The certificated private was not injured. Visual meteorological conditions prevailed for the personal flight that originated at Morgantown, West Virginia (MGW), approximately 1400. No flight plan was filed for the flight conducted under 14 CFR Part 91. In a telephone interview, the pilot stated he flew to MGW, serviced the airplane with fuel, and returned to his home airport at Phillipi/Barbour County. He said he entered the traffic pattern for runway 26, performed his base and final turns, and configured the airplane for landing. The pilot said that on short final, he began his level off and flare prematurely. He said: "I just ballooned high and had a hard landing. That's all there is to it." In a telephone interview, a Federal Aviation Administration (FAA) Aviation Safety Inspector said the airplane sustained damage to the propeller, nose gear, and firewall. He said the flight control tunnels aft of the firewall were crushed and prevented the movement of the flight controls. When questioned about the performance of the airplane, the pilot said, "It was performing very well. No problems." The pilot purchased the airplane November 6, 1999. An annual inspection was performed on the airplane prior to its purchase on October 5, 1999. The pilot reported 143 hours of flight experience, of which 7 hours were in the Cessna 172. Winds reported at Clarksburg, West Virginia, 10 miles northwest of 79D, were from 240 degrees at 7 knots.