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.
Oklahoma City, OK
According to the pilot, he lifted off the 1,800 foot soft sod runway after an 800 foot ground roll and as the airplane passed over the fence, he noticed the climb deteriorating. A scan of the instruments indicated the tachometer indicating 2,100 RPM versus the 2,500 RPM that would have been normal for takeoff. The airplane subsequently crossed a river and impacted the opposite bank. Two of the passengers stated that they thought the pilot had used most of the runway during the takeoff roll. Post-accident investigation revealed no evidence of pre-impact mechanical failure or malfunction. Tear down of the propeller indicated that the blades were at a pitch setting of about 20.5 degrees instead of the 12.5 degrees pitch which was normal for takeoff and climb. No explanation for the higher pitch setting was found during the investigation. A computer simulation of the accident scenario indicated that the blade angle would have been about 18.5 degrees for the conditions and power described by the pilot.
THE PROPELLER HYDRAULIC CONTROL PITCH SETTING BEING INCORRECT FOR UNDETERMINED REASONS. A FACTOR IN THE ACCIDENT WAS THE PILOT'S FAILURE TO IDENTIFY AND CORRECT THE PITCH SETTING AS THE PROPELLER WENT TO A HIGHER SETTING.
ACCORDING TO THE PILOT, HE LIFTED OFF THE 1,800 FOOT SOFT SOD RUNWAY AFTER AN 800 FOOT GROUND ROLL AND AS THE AIRPLANE PASSED OVER THE FENCE, HE NOTICED THE CLIMB DETERIORATING. A SCAN OF THE INSTRUMENTS INDICATED THE TACHOMETER INDICATING 2,100 RPM VERSUS THE 2,500 RPM THAT WOULD HAVE BEEN NORMAL FOR TAKEOFF. THE AIRPLANE SUBSEQUENTLY CROSSED A RIVER AND IMPACTED THE OPPOSITE BANK. TWO OF THE PASSENGERS STATED THAT THEY THOUGHT THE PILOT HAD USED MOST OF THE RUNWAY DURING THE TAKEOFF ROLL. POST-ACCIDENT INVESTIGATION REVEALED NO EVIDENCE OF PRE-IMPACT MECHANICAL FAILURE OR MALFUNCTION. TEAR DOWN OF THE PROPELLER INDICATED THAT THE BLADES WERE AT A PITCH SETTING OF ABOUT 20.5 DEGREES INSTEAD OF THE 12.5 DEGREES PITCH WHICH WAS NORMAL FOR TAKEOFF AND CLIMB. NO EXPLANATION FOR THE HIGHER PITCH SETTING WAS FOUND DURING THE INVESTIGATION. A COMPUTER SIMULATION OF THE ACCIDENT SCENARIO INDICATED THAT THE BLADE ANGLE WOULD HAVE BEEN ABOUT 18.5 DEGREES FOR THE CONDITIONS AND POWER DESCRIBED BY THE PILOT.