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.
Sidney, OH
The pilot reported that the airplane was in cruise flight at 3000 feet MSL, when the engine began to sputter, then lost power. The pilot stated that he applied carburetor heat, switched fuel tanks, and turned on the fuel boost pumps, but all restart attempts were unsuccessful. He made a forced landing in a rough field, and the airplane was damaged during the landing roll. Postaccident examination revealed evidence of fuel contamination. A brown colored substance was found in the fuel sump drain. The engine was test run using auxiliary fuel and auxiliary electrical power. During the test run, the engine ran smoothly with no indication of a malfunction.
fuel contamination, and the pilot's inadequate preflight inspection, which resulted in subsequent loss of engine power during cruise flight. A factor relating to the accident was: rough terrain in the emergency landing area.
On February 16, 1996, at about 1912 eastern standard time (EST), a Cessna 177A, N30422, lost engine power during cruise flight, and made a forced landing near Sidney, Ohio. The airplane sustained substantial damage during the forced landing. The certificated private pilot and one passenger were not injured. Visual meteorological conditions prevailed and a flight plan was not filed. The repositioning flight was operated under 14 CFR Part 91. The flight originated from Lima, Ohio, at 1900 EST. The intended destination was Sidney, Ohio. The pilot reported that the flight was cruising at 3000 feet Mean Sea Level (MSL), when the engine started to sputter. He stated that he applied carburetor heat and switched fuel tanks, but the engine continued to lose power. The pilot stated that he switched on the fuel boost pumps, but all attempts to restore power were unsuccessful. The pilot made a forced landing in a rough field, and the left main landing gear separated during the landing roll. According to the Ohio State Police, the pilot said that he was repositioning his airplane when the engine lost power about six miles north of Sidney. The pilot told the police officer that the airplane had been in Lima, Ohio, for maintenance since October, 1995. The officer reported that there was about 15 to 20 gallons of fuel onboard the airplane after the accident. The airplane was examined by a Federal Aviation Administration (FAA) Inspector after the accident. The Inspector stated that the examination included checking the fuel in the carburetor and fuel sump drain. The Inspector stated that when they examined the fuel system, a brown colored substance was found in the fuel sump drain. A postaccident engine test run was conducted with the engine still installed on the airframe. Auxiliary fuel and auxiliary electrical power were supplied for the test run. According to the FAA Inspector, the engine started normally, and "...ran smoothly. There was no indication of any malfunction during the run... ."