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.
Indian Trail, NC
The pilot stated that he intended to perform a short field takeoff due to trees at the end of the 2,350-foot-long runway. A pretakeoff engine run up revealed no anomalies, and the pilot initiated the takeoff with the wing flaps extended 10 degrees. "Immediately" after takeoff, the pilot raised the flaps, and felt as though the airplane's nose was "pushed down." The airplane contacted trees at the end of the runway and subsequently impacted the ground, resulting in substantial damage to the fuselage, both wings, and the engine firewall. Postaccident examination of the airplane and engine by a Federal Aviation Administration inspector revealed no anomalies that would have precluded normal operation. According to the airplane owner's handbook, when operating from short runways, "[takeoff] distances can be reduced appreciably by lowering flaps to 25 degrees." The Airplane Flying Handbook (FAA-H-8083-3A) further stated, "On short-field takeoffs, the landing gear and flaps should remain in takeoff position until clear of obstacles and [best rate of climb] has been established. It is usually advisable to raise the flaps in increments to avoid sudden loss of lift."
The pilot's improper flap retraction during a short field takeoff, which resulted in the aircraft experiencing an aerodynamic stall and impact with trees.
The pilot stated that he intended to perform a short field takeoff due to trees at the end of the 2,350-foot-long runway. A pretakeoff engine run up revealed no anomalies, and the pilot initiated the takeoff with the wing flaps extended 10 degrees. "Immediately" after takeoff, the pilot raised the flaps, and felt as though the airplane's nose was "pushed down." The airplane contacted trees at the end of the runway and subsequently impacted the ground, resulting in substantial damage to the fuselage, both wings, and the engine firewall. Postaccident examination of the airplane and engine by a Federal Aviation Administration inspector revealed no anomalies that would have precluded normal operation. According to the airplane owner's handbook, when operating from short runways, "[takeoff] distances can be reduced appreciably by lowering flaps to 25 degrees." The Airplane Flying Handbook (FAA-H-8083-3A further stated, "On short-field takeoffs, the landing gear and flaps should remain in takeoff position until clear of obstacles and [best rate of climb] has been established. It is usually advisable to raise the flaps in increments to avoid sudden loss of lift."