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.
Chesterfield, VA
The pilot said the purpose of the flight was to get current with night landings. On final approach to the 5,500 foot long paved runway in calm wind, the pilot said the airplane was high so he increased the angle of descent. Upon touchdown, the airplane landed hard and porpoised several times. The pilot reported that there were no mechanical deficiencies.
pilot's improper flare, which resulted in a hard landing at night.
On June 17, 2002, at 2100 eastern daylight time, a Cessna 177B, N2182C, was substantially damaged during landing on runway 33 at Chesterfield County Airport (FCI), Chesterfield, Virginia. The certificated private pilot/owner sustained minor injuries. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight conducted under 14 CFR Part 91. In a written statement, the pilot said that the purpose of the flight was to get current with night landings. He departed the airport and proceeded direct to the PUBBS non-directional beacon (NDB), where he then entered the instrument landing system (ILS) approach for runway 33. The pilot said that he was flying by visual reference and used the ILS for guidance. He said: "There were no other aircraft in the pattern so I proceeded to land on 33. I was a little high so I increased my angle of descent. I touched down pretty hard and the plane porpoised several times. On one of these the damage was done. I wasn't aware of the damage, but my back hurt so I taxied to my hangar. The weather was clear and the wind was calm" A Federal Aviation Administration (FAA) inspector performed an examination of the airplane. According to the inspector, the firewall was wrinkled. Runway 33 was a 5,500 foot long and 100 foot wide asphalt runway with pilot controlled lighting. The pilot reported a total of 634 flight hours, of which 488 hours were in make and model. He also reported that there were no mechanical deficiencies. Weather at Richmond International Airport, Richmond, Virginia, about 11 nautical miles northeast, at 2054, included wind from 100 degrees at 4 knots, visibility 10 statute miles, and few clouds at 5,500 feet.