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.
Mandan, ND
On September 1, 2024, about 1520 central daylight time, a Diamond DA42 airplane, N705JP, sustained substantial damage when it was involved in an accident near Mandan, North Dakota. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, he departed Bismark Municipal Airport (BIS) and requested vectors for the RNAV 31 approach at Mandan Regional Airport (Y19) from air traffic control. The pilot reported that his approach to Y19 was uneventful and estimated that he touched down about 100 ft past the numbers for runway 31. The pilot attempted to decelerate, keeping constant pressure on the brakes. The pilot stated that the brakes were not working until he approached the end of the runway at which point the brakes “slowly got responsive.” The pilot stated that the pilot-rated passenger asked about conducting a go-around during the landing attempt, but the pilot was focused on stopping. The pilot reported that a go-around could have been possible and that it was a “shock” that he couldn’t stop the airplane. According to the pilot-rated passenger, the landing at Y19 was so smooth that he did not notice the airplane had touched down until the nose wheel shimmied. The passenger stated that the airplane appeared to touchdown within the first third of the 4399 ft runway. He stated that the landing roll seemed normal, but he did not feel as much deceleration as he would have expected. The airplane exited the paved surface of the runway and impacted a runway end identifier light (REIL) resulting in substantial damage to the fuselage. According to the airport manager, who examined the runway surface after the accident, there were visible tire skid marks leading off the end of the runway. A review of Automatic Dependent Surveillance – Broadcast (ADS-B) data revealed that the airplane departed from runway 13 at BIS, climbed to about 4,500 ft mean sea level and made an approach to runway 31 at Y19. The airplane’s ground speed at touchdown was about 118 kts. A review of Automated Weather Observing System (AWOS) data based on the field at Y19 revealed that five minutes before the accident, the wind was from 170° at 7 knots. The airplane was recovered for further examination.
The pilot’s failure to perform a go-around following an unstable approach while landing with a tailwind, which resulted in the airplane touching down long on the runway with insufficient distance to stop. Contributing to the accident was the pilot’s selected flap setting which increased the airplane’s landing roll.
On September 1, 2024, about 1520 central daylight time, a Diamond DA42 airplane, N705JP, sustained substantial damage when it was involved in an accident near Mandan, North Dakota. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, he departed Bismark Municipal Airport (BIS) and requested vectors for the RNAV 31 approach at Mandan Regional Airport (Y19) from air traffic control. The pilot reported that his approach to Y19 was uneventful and estimated that he touched down about 100 ft past the numbers for runway 31. The pilot attempted to decelerate, keeping constant pressure on the brakes. The pilot stated that the brakes were not working until he approached the end of the runway, at which point the brakes “slowly got responsive.” The pilot stated that the pilot-rated passenger asked about conducting a go-around during the landing attempt, but the pilot was focused on stopping. The pilot reported that a go-around could have been possible and that it was a “shock” that he couldn’t stop the airplane. According to the pilot, he used a flap setting of 20°, or APP during the approach and landing. According to the pilot-rated passenger, the landing at Y19 was so smooth that he did not notice the airplane had touched down until the nose wheel shimmied. The passenger stated that the airplane appeared to touchdown within the first third of the 4399-ft runway and the landing roll seemed normal, but he did not feel as much deceleration as he expected. The airplane exited the paved surface of the runway and impacted a runway end identifier light, resulting in substantial damage to the fuselage. According to the airport manager, who examined the runway surface after the accident, there were visible tire skid marks leading off the end of the runway. A postaccident examination of the brake system revealed that the brakes appeared to function normally. There was no evidence of leaks at the hoses, calipers, or at the master cylinders attached to the rudder pedals. Brake application was firm and, with the brakes applied, would have prevented the movement of the airplane. The brake pads appeared to have adequate material left to not impede braking action. The right brake pads were worn more than the left, but not beyond the limit of function. An aircraft performance study using ADS-B and engine ECU data concluded that the airplane touched down at 92 kts calibrated airspeed, 6 kts faster than the 86-kt VREF speed calculated from the Airplane Flight Manual. The airplane’s weight on wheels (WOW) sensors indicated that the airplane was not fully on the ground until 2,136 ft past the runway threshold. The airplane was landed in a 6.3-kt tailwind that would have increased landing distance by 21%. Considering all factors, the study concluded that there was insufficient runway remaining after the touchdown for the airplane to stop. Additionally, the study concluded that had the pilot used the LDG flap setting there would have been sufficient runway remaining. According to the AFM, ground roll distances for flaps LDG are about 73% of the ground roll distances for flaps APP/UP. If that ratio holds for the ground roll estimate above of 2,411 ft with flaps APP, the ground roll estimate for flaps LDG would be 1,760 ft. A ground roll of 1,760 ft would have allowed the airplane to stop on the runway.