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.
Mansfield, OH
The pilot reported that he attempted to land on the first third of the runway, at an airspeed of 90 knots, while maintaining the runway centerline. During the landing flare, a wind gust turned the airplane approximately 10 degrees to the left. The airplane landed, went off the runway and into the grass, and struck runway lights and signs. Winds were reported as 30 degrees from the right, at 13, gusting to 17 knots
The pilot's inadequate compensation for wind conditions and his failure to maintain directional control during the landing. A factor was the gusty wind conditions.
On June 21, 2003, about 1335 eastern daylight time, a Piper PA-32R-301T, N9298D, was substantially damaged during a landing at Mansfield Lahm Municipal Airport (MFD), Mansfield, Ohio. The certificated private pilot and the two passengers were not injured. No flight plan was filed for the flight that originated at Tri Cities Regional Airport (TRI), Blountville, Tennessee, about 1100. Visual meteorological conditions prevailed for the personal flight conducted under 14 CFR Part 91. According to a witness, an air traffic controller who was working the local control tower, he cleared the airplane to land on runway 32. The controller thought that the airplane was flaring a "little too high," and it landed on the left side of the runway. He thought he saw dust or smoke coming from behind the airplane and called crash, fire, and rescue. The pilot turned off at the next taxiway and the controller asked if everything was okay. The pilot said yes, and the controller directed him to taxi. In a written statement, the pilot said that he attempted to land on the first third of the runway, at an airspeed of 90 knots, while maintaining the runway centerline. During the landing flare, a wind gust turned the airplane approximately 10 degrees to the left. The airplane turned to the left, went off the runway into the grass, struck runway lights and signs, then turned back onto the runway The pilot said the landing was bumpy, but was unaware he had struck anything until he was parked at a hanger. A Federal Aviation Administration (FAA) Inspector examined the airplane on June 23, 2003. According to the inspector, the left main landing was partially separated from the airplane, the left wing was wrinkled, and the left fuel tank was punctured. The pilot reported a total of 327 flight hours, of which, 123 were in make and model. Weather reported at the airport, included winds from 350 degrees at 13 knots gusting to 17 knots, temperature 72 degrees F, dewpoint 51 degrees F, and a barometric pressure setting of 30.04 inches Hg. The visibility was 10 statute miles and clear.