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.
Corona, CA
The pilot reported that the day before the accident, the engine experienced a loss of power "from apparent fuel starvation." On the day of the accident, the pilot reported that before the flight he inspected and modified the fuel system. The pilot stated that he "installed fuel hose directly from tank to carb, bypassing gascolator and fuel flow sensor." The pilot then ran the engine at full power for five minutes before takeoff. The pilot successfully took off on runway 25 and at approximately 500 feet above ground level, the engine lost power. The pilot turned the aircraft back towards the departure runway. While turning to line up with the grass alongside the runway, the aircraft "sank out of the turn, collapsed left gear leg and bent left wing - landing in soft grass." The airplane came to a stop in the grass with its nose on the ground and tail in the air. The pilot exited the airplane and pulled the tail back down. The pilot reported that he believed the malfunction was a "fuel flow fault." Approximately 12 gallons of automotive fuel was on board at the time. Federal Aviation Administration airmen records indicated that the pilot does not hold airframe or powerplant mechanic certificates.
A loss of engine power during the initial climb due to a fuel system malfunction. The pilot's incorrect maintenance modification to the fuel system and continued operation with known deficiencies were factors.
The pilot reported that the day before the accident, the engine experienced a loss of power "from apparent fuel starvation." On the day of the accident, the pilot reported that before the flight he inspected and modified the fuel system. The pilot stated that he "installed fuel hose directly from tank to carb, bypassing gascolator and fuel flow sensor." The pilot then ran the engine at full power for five minutes before takeoff. The pilot successfully took off on runway 25 and at approximately 500 feet above ground level, the engine lost power. The pilot turned the aircraft back towards the departure runway. While turning to line up with the grass along side the runway, the aircraft "sank out of the turn, collapsed left gear leg and bent left wing - landing in soft grass." The airplane came to a stop in the grass with it's nose on the ground and tail in the air. The pilot exited the airplane and pulled the tail back down. The pilot reported that he believed the malfunction was a "fuel flow fault." Approximately 12 gallons of automotive fuel was on board at the time. Federal Aviation Administration airmen records indicated that the pilot does not hold airframe or powerplant mechanic certificates.