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.
Sac City, IA
The airline transport pilot reported that he changed the engine oil the night before the accident flight. The next day, he performed a normal engine run-up and then departed on the agricultural application flight. The airplane's tail lifted when the airplane reached 60 mph, and the airplane then accelerated to 80 mph. Shortly after getting airborne, the pilot felt that the airplane was not performing as it should be and that the engine power was decreasing. He advanced the engine controls full forward and selected a cornfield for the forced landing. The pilot reported that he thought that the engine's blower/supercharger had failed because the engine did not stop but did seem to lose power. An engine examination was not performed; therefore, the reason for the loss of engine power could not be determined.
The loss of engine power for reasons that could not be determined based on the available information.
On August 12, 2015, about 1600 central daylight time, a Grumman G-164B agricultural airplane, N311AL, lost engine power shortly after take-off near Sac City, Iowa. The pilot was not injured and the airplane was substantially damaged during the forced landing. The airplane was registered to and operated by a private individual under the provisions of 14 Code of Federal Regulations Part 137 as an agricultural flight. Visual meteorological conditions prevailed at the time. According to the pilot, he changed the engine oil the night before and completed a 45 minute engine run. On the accident day, he performed a normal run-up and everything appeared normal. He noted a 50 rpm drop per magneto during the engine run-up. He then departed down the runway and lifted the tail at 60 mph and accelerated to 80 mph. Shortly after getting airborne, he felt the airplane was not preforming as it should. The airplane was able to climb over a set of wires, but the engine power faded. He advanced the engine controls full forward, and then selected a cornfield to perform the forced landing in. During the landing, the airplane nosed over and came to rest inverted. Due to the un-harvested corn field, the airplane remained on site until about November 7, so an engine examination was not performed. The pilot added that he thought the engine's blower/supercharger had failed, since the engine didn't stop, but seemed to lose power. A completed NTSB 6120 form was not returned by the operator.