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.
Cedar City, UT
According to both pilots, approximately 500 feet agl, the engine lost power and the safety pilot continued flying the airplane. The safety pilot reported that he attempted to restore power, by adjusting mixture and power but nothing worked to restore power. The airplane touched down to the west of the runway, at a 45 degree angle to the paved surface, sank in the dirt, flipped upside down, and skidded to a stop on the runway. The airplane was substantially damaged. An examination revealed no anomalies that would have precluded the engine from producing power prior to the accident. An examination of the remaining systems revealed no anomalies.
the loss of engine power for reasons undetermined. Contributing factors include the lack of suitable terrain for a forced landing, and the soft dirt.
On August 17, 2005, approximately 1315 mountain daylight time, a Cessna 172N, N9892J, operated by a private pilot, was substantially damaged when it nosed over during a forced landing at Cedar City Regional Airport (CDC), Cedar City, Utah. Visual meteorological conditions prevailed. The training flight was being conducted on an instrument flight rules flight plan under the provisions of Title 14 CFR Part 91. The private pilot and private certificated safety pilot were not injured. The cross-country flight was originating at the time of the accident, and was en route to Provo, Utah. According to a telephone interview with both pilots, they were departing on a cross-country flight so the private pilot could build instrument hood time. According to the private pilot, he had established a positive climb rate and transferred the flight controls to the safety pilot so he could put on his hood. Approximately 500 feet agl, the engine lost power and the safety pilot continued flying the airplane. According to a report submitted by the safety pilot, he tried adjusting mixture and power but nothing worked to restore power. The airplane touched down to the west of runway 02, at a 45 degree angle to the paved runway surface. According to the private pilot, the airplane touched down in the dirt short of the runway, bounced, then touched the dirt again. When the nose wheel touched down, it sank in the dirt and the airplane flipped upside down and skidded to a stop on the runway. The nose landing gear assembly separated, the firewall was wrinkled, and both the left and right wings were wrinkled. The airplane was recovered and relocated to a hangar in Phoenix, Arizona, for further examination. The engine was examined by the NTSB IIC on October 5, 2005. No anomalies were noted that would have precluded the engine from producing power prior to the accident.