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.
Malad City, ID
In a written statement the private pilot, who was at the controls during the accident, stated that after a high approach the airplane touched down at a point where it was "too late to execute a missed approach, because we had used so much of the runway. We both slammed on the brakes and started skidding off the end of the runway. We went through a barbed wire fence and hit a ditch. Hitting the ditch launched the aircraft over a road. We went through another fence and hit another ditch, flipping the aircraft upside down." The commercial pilot/certified flight instructor reported that the airplane was too high during the approach and just as he was going to instruct the pilot to go-around "...the wheels touched down and the tires started to lockup."
The private pilot's improper touchdown point during landing and the certified flight instructors delayed remedial action. Ditches and fences were factors in the accident.
On April 22, 2006, at 2145 mountain standard time, a Cessna 172S, N679SP, sustained substantial damage subsequent to a runway overrun during landing at the Malad City Airport (MLD), Malad City, Idaho. The airplane was being operated by Air Center of Salt Lake, West Jordon, Utah, as an instructional cross-county flight under the provisions of Title 14, CFR Part 91. The private pilot receiving instruction (pilot "A") and the commercial pilot/certified flight instructor (pilot "B") were not injured in the accident. Visual meteorological conditions prevailed for the night cross-country flight that originated from Salt Lake City Municipal 2 Airport (U42), Salt Lake City, Utah, at 2035. A flight plan had been filed, however it had not been activated. In a written statement dated April 27, the private pilot, who was at the controls during the accident, stated that after a high approach the airplane touched down at a point where it was "...too late to execute a missed approach, because we had used so much of the runway. We both slammed on the brakes and started skidding off the end of the runway. We went through a barbed wire fence and hit a ditch. Hitting the ditch launched the aircraft over a road. We went through another fence and hit another ditch, flipping the aircraft upside down." In a written statement dated April 29, the commercial pilot/certified flight instructor reported that the airplane was too high during the approach and just as he was going to instruct the pilot to go-around "...the wheels touched down and the tires started to lockup." Both pilot statements are contained in the public docket associated with this report.