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.
Phoenix, AZ
During a personal flight, the pilot notified air traffic control that he had a rough-running engine, and the pilot declared an emergency. The controller advised the pilot of two diversion airports; the first was located near the airplane’s position at the time, and the second was located about 12 miles south of the airplane’s position. The pilot elected to divert to the second airport. The pilot advised the controller a few minutes later that the airplane would be unable to reach that airport, and the radar track showed a right turn toward the other airport, which was about 8 miles east from the airplane’s position. No further communication from the pilot was received. A witness located near the accident site reported that the airplane maneuvered to avoid power lines and struck light poles before it impacted the ground. A postimpact fire ensued. Postaccident examination of the wreckage revealed that engine control continuity was established from all the engine controls to their respective engine components. The engine exhibited extensive thermal damage. To prepare the engine for test runs performed by the manufacturer, several components and accessories were replaced due to thermal damage. The engine was successfully run at various power settings. No mechanical anomalies were noted with the recovered parts of the engine and airframe that would have precluded normal operation. As a result, the reason for the partial loss of engine power was not determined.
The partial loss of engine power during cruise flight for reasons that could not be determined with the available evidence.
On June 11, 2019, about 1451 mountain standard time, a Mooney M20V airplane, N576CM, was substantially damaged when it was involved in an accident near Deer Valley Airport (DVT) Deer Valley, Arizona. The private pilot was seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. About 5 months after the accident, the pilot succumbed to his injuries. A statement from the pilot was not obtained during the investigation. Review of air traffic control communications revealed that, about 7 minutes after departing from Scottsdale Airport (SDL), Scottsdale, Arizona, the pilot reported a “rough running engine” and subsequently declared an emergency. The airplane was about 8 miles northwest of DVT at the time of the pilot’s radio call. Radar data showed that the pilot had climbed the airplane to an altitude of 9,100 ft mean sea level. The controller informed the pilot of possible diversion airports, stating that Pleasant Valley Airport (P48), Peoria, Arizona, was near the airplane’s position and that Glendale Municipal Airport (GEU), Glendale, Arizona, was 12 miles south of the airplane’s position. The pilot elected to divert to GEU, and radar data showed that the airplane turned to the south onto a heading that aligned with runway 19. A few minutes later, when the airplane was at an altitude of about 4,700 ft mean sea level, the pilot recognized that the airplane was not going to reach GEU, so he made a turn toward DVT, which was about 8 miles to the east. No other transmissions from the pilot were recorded. Radar data showed that the airplane continued on an easterly heading until the last recorded target; at that time, the airplane was about 2 miles west of DVT. A witness, who was located near the accident site, reported that the airplane appeared to bank left to avoid high-tension power lines before it impacted two light posts and then the ground. A postimpact fire ensued. The airplane came to rest on a street. The postimpact fire consumed most of the airframe. Flight control continuity was established from the cockpit controls to all primary flight control surfaces. Engine control continuity was established from the cockpit controls to their respective engine components. An unmeasured amount of fuel remained in the left-wing fuel tank. Fueling records showed that, on the morning of the accident flight, the airplane tanks were filled with 58 gallons of 100 low-lead fuel. Postaccident examination of the engine revealed extensive thermal damage throughout. The engine was then shipped to the manufacturer for further examination. While preparing the engine for the test runs, several components and accessories were replaced due to thermal damage. The engine was successfully run at various power settings, but it would not run at idle. The metering assembly was removed and tested, and internal components were replaced. Hard deposits of what appeared to be melted plastic on the throttle body internal walls was removed. Afterward, the engine was successfully run. Postaccident examination of the airframe and engine revealed no mechanical anomalies or malfunctions that would have precluded normal operation.