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.
Columbus, OH
The pilot had flown a cross country flight on an instrument flight rules flight plan. The pilot reported that while on approach he picked up recorded weather which was "winds from 310 at 9 gusting to 15, 10 miles visibility, a few clouds at 9,500’ and altimeter 29.63" and that he was cleared to land on runway 27L. The pilot asked for a wind check and the tower reported the wind as "from 300 at 20 with no mention of gusts." The pilot used full flaps during the landing and reported an indicated airspeed of 95-100 knots. He reported that during the flare he experienced "normal ground-effect 'turbulence'" and "focused on maintaining the centerline and allowing airspeed to bleed off to land smoothly." He stated that immediately upon touchdown, the airplane began veering about 20 degrees to the left. He said that he tried to correct with right rudder only. The pilot said that he "determined that more aggressive correction was unsafe and instead decided to exit the runway into the grassy area between the runway and the airport ramp area." The airplane's left wing struck a runway light and then the 3,000 feet remaining sign.
The pilot not maintaining directional control during the landing. Contributing to the accident were the gusty crosswinds and the airport sign that was impacted.
The pilot had flown a cross country flight on an instrument flight rules flight plan. The pilot reported that while on approach he picked up recorded weather which was "winds from 310 at 9 gusting to 15, 10 miles visibility, a few clouds at 9,500’ and altimeter 29.63" and that he was cleared to land on runway 27L. The pilot asked for a wind check and the tower reported the wind as "from 300 at 20 with no mention of gusts." The pilot used full flaps during the landing and reported an indicated airspeed of 95-100 knots. He reported that during the flare he experienced "normal ground-effect 'turbulence'" and "focused on maintaining the centerline and allowing airspeed to bleed off to land smoothly." He stated that immediately upon touchdown, the airplane began veering about 20 degrees to the left. He said that he tried to correct with right rudder only. The pilot said that he "determined that more aggressive correction was unsafe and instead decided to exit the runway into the grassy area between the runway and the airport ramp area." The airplane's left wing struck a runway light and then the 3,000 feet remaining sign.