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.
Marion, IN
The pilot reported that upon landing the airplane 'veered left off the runway. It felt like the left brake was locked up.' The airplane went through a ditch off the edge of the runway and through the field to the crosswind runway. When the airplane's nosewheel contacted the edge of the crosswind runway it collapsed, and the airplane came to a stop on the crosswind runway. Examination of the airplane revealed no mechanical anomalies in the flight controls, engine, engine controls or brakes. An airplane and powerplant mechanic on the airport reported that the airplane's brakes functioned normally while towing the airplane from the accident site.
the pilot's failure to maintain directional control during landing.
On January 31, 1996, at 1530 eastern standard time (est), a Piper PA-32-301, N800TC, piloted by a private pilot, sustained substantial damage when on landing the airplane departed the runway. Visual meteorological conditions prevailed at the time of the accident. The flight was being conducted under 14 CFR Part 91. No flight plan was on file. The pilot reported no injuries to himself or the passenger on board. The flight originated at Waterloo, Iowa, at 1125 central standard time (cst) and was en route to Marion, Indiana. In his written statement, the pilot reported that upon landing on runway 33 (3,596' X 100'), the airplane "veered left off the runway. It felt like the left brake was locked up." The pilot applied full right rudder, but he could not prevent the airplane from departing the runway. The airplane went through a ditch off the edge of the runway, and through the field to the crosswind runway. When the airplane's nosewheel contacted the edge of the crosswind runway, "it collapsed." The airplane came to a stop on the crosswind runway. A Federal Aviation Administration (FAA) inspector examined the airplane in a hangar at Marion Municipal Airport, Marion, Indiana, on February 2, 1996. The examination revealed that the nosewheel had bent rearward under the cowling and was cocked to the right. The firewall and the engine mount had bent down and rearward at the point where the nosewheel strut attaches to the mount. Both propeller blades were also bent. Flight control continuity was confirmed. No anomalies were found in the engine or engine controls. The brakes were tested and functioned normally. In a telephone interview conducted on February 27, 1996, an airplane and powerplant mechanic for Air Marion, Incorporated, Marion, Indiana, reported that the airplane's brakes functioned normally while towing the airplane from the accident site to the hangar.