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.
Brookshire, TX
The unqualified private pilot was practicing visual approaches and landings on a dark night. On his fourth or fifth pattern, the airplane was taking off following a full-flap touch-and-go when it struck a fence and impacted in a field past the departure end of the runway. The pilot stated he landed about one-third down the 4,100 foot runway and the roll out was longer than normal, but elected to attempt another approach. During climb out the pilot saw the orange marker balls on the power lines off the departure end of the runway, realized he could not clear them, and was attempting to dive under the wires when the airplane struck the fence. The pilot also stated the airplane was operating normally at the time of the accident and there were no engine or flight control malfunctions. Examination of the airplane revealed the right wing spar was bent upward. The pilot had not completed a biannual flight review within the past 24 months and did not meet currency requirements for carrying passengers as required by Federal Aviation Regulations.
The pilot's decision to duck under marked transmission lines and his failure to maintain clearance from the fence. Contributing to the accident was the marked transmission lines.
The private pilot was practicing visual approaches and landings on a dark night with one non-rated passenger. On his fourth or fifth pattern, the airplane was taking off following a full-flap touch and go when it struck a fence and impacted in a field past the departure end of the runway. The pilot stated he landed about one-third down the 4,100 foot runway and the roll out was longer than normal, but elected to attempt another approach. During climb out the pilot saw the orange marker balls on the power lines off the departure end of the runway, realized he could not clear them, and was attempting to dive under the wires when the airplane struck the fence. The pilot also stated the airplane was operating normally at the time of the accident and there were no engine or flight control malfunctions. Examination of the airplane revealed the right wing spar was bent upward. Information provided by the pilot on the Pilot/Operator Accident/Incident Report shows the pilot's last flight review was 1 April, 2006. Title 14 Code of Federal Regulations, Part 61.56 states a pilot must accomplish a flight review within 24 months of their last flight review in order to act as pilot in command. According to Federal Aviation Administration officials, the pilot failed to meet the currency requirements for carrying passengers as stated in Title 14 Code of Federal Regulations, Parts 61.57(a)1 and 61.57(b)1.