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.
San Carlos, CA
While on an extended downwind for landing the airplane experienced a power failure after throttle was applied. The pilot executed the prelanding and an emergency checklist. Engine power was not restored. According to the same account, the pilot turned the fuel selector to the "off" position before the forced landing was made in the slough west of the airport. The nose wheel was caught in the rough terain and the airplane came to rest inverted. Fuel was added before the flight and post crash examination revealed the tanks carried a supply 1 inch below the tabs. The airplane was successfully started after it was righted and ran roughly.
A loss of engine power for undetermined reasons during an extended downwind leg in the landing pattern.
On December 21, 2000, at 1556 Pacific standard time, a Cessna 177RG, N2102Q, lost power and landed short of the runway while on approach to San Carlos Airport, San Carlos, California. The airplane sustained substantial damage; however, the student pilot, the sole occupant, was not injured. The airplane was being operated as a supervised solo instructional flight by the pilot/owner under 14 CFR Part 91. The return leg of a round-robin flight to the Tracy airport, Tracy, California, originated about 1526. Visual meteorological conditions prevailed at the time and no flight plan was filed. The pilot reported to a Federal Aviation Administration (FAA) inspector that he had flown to the Tracy airport to practice touch-and-go takeoffs and landings. On his return leg, he had reached the traffic pattern at San Carlos, when the tower operator asked him to extend his downwind. He said that he slowed in order to maintain spacing by reducing power; however, when he reapplied the throttle the engine quit. He made a forced landing in the Belmont slough, about 1.5 miles from the end of the runway. After touchdown, the airplane nosed over, coming to rest in shallow water. The FAA inspector reported the throttle, mixture, and propeller was found in the full forward position. The fuel selector was found in the "off" position. There were no anomalies reported with any of the engine controls, cable, or linkages. The pilot stated that the airplane had been filled with aviation fuel prior to his departure from San Carlos en route to Tracy. Recovery personnel reported that although the airplane was inverted and slowly losing fuel when they arrived, the fuel level was found to be within an inch of the tabs in both tanks. After recovery, the airplane was righted and the engine was supplied with fuel and electrical power. The engine was then successfully started and ran roughly after about 45 minutes.