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.
Columbia, CA
On January 23, 2025, about 1515 Pacific standard time, a Cessna 172K, N79910 , was substantially damaged when it was involved in an accident near Columbia, California. The pilot and passenger sustained serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot stated that after departure he continued east to Columbia and entered the downwind leg of the traffic pattern at a 45° angle for runway 17. On the final approach, he noted that the airplane was high and maneuvered the airplane in a forward slip in an attempt to descend faster. As the airplane approached the runway, it was still too high, and the pilot determined there was not enough available distance to land safely. The pilot initiated a go-around by pushing the throttle fully forward to increase engine power and turned the carburetor heat off. Shortly thereafter, the engine rpm began to decrease. He verified that the mixture, throttle, and carburetor heat were all fully forward and confirmed that the fuel selector was set to both tanks. When he moved the throttle aft and forward, the engine briefly surged, and the rpm increased. As he searched for a suitable off-airport landing site, he observed that the surrounding terrain was hilly with trees and brush. The engine then lost rpm again. With limited options, he turned left in an attempt to return to the runway. While transmitting a radio call to report the engine failure, he noticed the radios had gone blank. The airplane collided with trees and impacted the ground in a nose-down attitude.
On January 23, 2025, about 1515 Pacific standard time, a Cessna 172K, N79910 , was substantially damaged when it was involved in an accident near Columbia, California. The pilot and passenger sustained serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot stated that after departure he continued east to Columbia and entered the downwind leg of the traffic pattern at a 45° angle for runway 17. On the final approach, he noted that the airplane was high and maneuvered the airplane in a forward slip in an attempt to descend faster. As the airplane approached the runway, it was still too high, and the pilot determined there was not enough available distance to land safely. The pilot initiated a go-around by pushing the throttle fully forward to increase engine power and turned the carburetor heat off. Shortly thereafter, the engine rpm began to decrease. He verified that the mixture, throttle, and carburetor heat were all fully forward and confirmed that the fuel selector was set to both tanks. When he moved the throttle aft and forward, the engine briefly surged, and the rpm increased. As he searched for a suitable off-airport landing site, he observed that the surrounding terrain was hilly with trees and brush. The engine then lost rpm again. With limited options, he turned left in an attempt to return to the runway. While transmitting a radio call to report the engine failure, he noticed the radios had gone blank. The airplane collided with trees and impacted the ground in a nose-down attitude.