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.
Caldwell, NJ
The pilot-in-command (PIC) of the business jet described that at the conclusion of the flight the second-in-command (SIC) would conduct the landing. The SIC briefed the approach and the PIC agreed. The tower cleared the airplane for the visual approach to runway 22 (4,552-ft-long), noting winds were 300° at 18 knots, gusting to 26 knots. The PIC told the SIC that if he did not feel comfortable with the approach to landing, he should voice his concern, and initiate a go-around or transfer control of the airplane to the PIC. The PIC also briefed the procedure for taking control of the airplane should any unsafe conditions be observed. The PIC further described that after turning final, the landing checklist was completed, and the airplane was established on a stabilized approach. The SIC noted that he would fly at a slightly higher speed due to varying winds and gusts. Just before touchdown, the airplane “encountered a gust of wind that resulted in a ground effect float.” The airplane then touched down “at Ref speed” and on what the PIC perceived to be the first third of the runway. Due to the float and wind gust upon touchdown, the PIC called for the controls with the intent to initiate a go-around or to bring the airplane to a stop. The PIC then decided not to commence a go-around due to the limited amount of remaining runway available, low airspeed, and time to initiate takeoff power. The PIC realized that the airplane would not come to a stop on the remaining runway, even with maximum braking applied, and the airplane overran the runway and came to a stop in a brook beyond the departure end. The forward portion of the fuselage was substantially damaged during the runway excursion. The PIC reported that there were no mechanical malfunctions or failures of the airplane that would have precluded normal operation. Review of airport surveillance camera footage showed that the airplane touched down beyond the midpoint of the runway.
The flight crew’s failure to attain a proper touchdown point during landing, which resulted in an overrun of the runway and collision with terrain.
The pilot-in-command (PIC) of the business jet described that at the conclusion of the flight the second-in-command (SIC) would conduct the landing. The SIC briefed the approach and the PIC agreed. The tower cleared the airplane for the visual approach to runway 22 (4,552-ft-long), noting winds were 300° at 18 knots, gusting to 26 knots. The PIC told the SIC that if he did not feel comfortable with the approach to landing, he should voice his concern, and initiate a go-around or transfer control of the airplane to the PIC. The PIC also briefed the procedure for taking control of the airplane should any unsafe conditions be observed. The PIC further described that after turning final, the landing checklist was completed, and the airplane was established on a stabilized approach. The SIC noted that he would fly at a slightly higher speed due to varying winds and gusts. Just before touchdown, the airplane “encountered a gust of wind that resulted in a ground effect float.” The airplane then touched down “at Ref speed” and on what the PIC perceived to be the first third of the runway. Due to the float and wind gust upon touchdown, the PIC called for the controls with the intent to initiate a go-around or to bring the airplane to a stop. The PIC then decided not to commence a go-around due to the limited amount of remaining runway available, low airspeed, and time to initiate takeoff power. The PIC realized that the airplane would not come to a stop on the remaining runway, even with maximum braking applied, and the airplane overran the runway and came to a stop in a brook beyond the departure end. The forward portion of the fuselage was substantially damaged during the runway excursion. The PIC reported that there were no mechanical malfunctions or failures of the airplane that would have precluded normal operation. Review of airport surveillance camera footage showed that the airplane touched down beyond the midpoint of the runway.