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.
Monticello, IA
The pilot reported that the brakes were not effective during landing rollout. He allowed the airplane to depart the paved runway into the adjacent grass area to slow down. The airplane encountered a shallow ditch which damaged the fuselage immediately aft of the firewall, resulting in substantial damage to the airplane. The firewall and nose landing gear were also damaged. A mechanic completed a postaccident examination and was unable to identify any anomalies with respect to the brake system. The mechanic commented that the brake system can be affected if the parking brake is partially engaged at takeoff; however, the pilot reported that the parking brake was not used during the flight. The mechanic noted the airplane departed the pavement about 800 ft from the end of the 4,400 ft runway and encountered a drainage ditch. The airplane traveled about 600 ft past the ditch before it stopped. Based upon this distance, the pilot likely landed long and with excessive airspeed which resulted in an inability to slow the airplane sufficiently before encountering the end of the runway.
The pilot’s failure to maintain a proper approach airspeed and glidepath which resulted in a long landing and his inability to stop the airplane on available runway and the subsequent runway excursion.
The pilot reported that the brakes were not effective during landing rollout. He allowed the airplane to depart the paved runway into the adjacent grass area to slow down. The airplane encountered a shallow ditch which damaged the fuselage immediately aft of the firewall, resulting in substantial damage to the airplane. The firewall and nose landing gear were also damaged. A mechanic completed a postaccident examination and was unable to identify any anomalies with respect to the brake system. The mechanic commented that the brake system can be affected if the parking brake is partially engaged at takeoff; however, the pilot reported that the parking brake was not used during the flight. The mechanic noted the airplane departed the pavement about 800 ft from the end of the 4,400 ft runway and encountered a drainage ditch. The airplane traveled about 600 ft past the ditch before it stopped. Based upon this distance, the pilot likely landed long and with excessive airspeed which resulted in an inability to slow the airplane sufficiently before encountering the end of the runway.