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.
Deland, FL
The pilot stated that during a slow climb after takeoff, a lighted chip light in the airplane's cockpit illuminated. Shortly thereafter, he said he felt the first engine shudder/backfire, and he then made a "Mayday" call, and proceeded to the nearest airport to land. Along the way, the pilot said he increased power in an attempt to ensure he would reach the airport, and initially felt the airplane accelerate, but about 30 seconds later, in addition to the illuminated chip light and vibration associated with the engine, suddenly there was a severe rumble again, followed by the engine operating distinctively rough. He noted little puffs of black smoke, coming out of the stacks around the fuselage, and since there was a heavy forested area ahead, he said he turned the airplane toward a field, to affect a landing. The approach and landing flare/touchdown were uneventful, but during the landing rollout the airplane impacted a ditch, and incurred substantial damage. According to the FAA inspector who responded to the accident, an engine master rod bearing failed.
A loss of engine power due to an engine master rod bearing failure for undetermined reasons, resulting in damage to the airplane during the subsequent forced landing.
On June 20, 2004, about 1050 eastern daylight time, a North American T-28C, N28BZ, registered to and operated by a private individual, as a Title 14 CFR Part 91 personal flight, made a forced landing to a field in the area of Deland, Florida. Visual meteorological conditions prevailed, and a visual flight rules flight plan was filed. The pilot and one passenger were not injured, and the airplane incurred substantial damage. The flight had originated from New Smyrna Beach, Florida, a few minutes before the accident. The pilot stated that he had just departed from New Smyrna Beach Municipal Airport, New Smyrna Beach, Florida, and during a slow climb, at an altitude of about 5,000 feet, the pilot-rated passenger in the back seat alerted him to a flickering chip light. According to the pilot, the passenger said the light flickered dimly for about a second and then illuminated full bright. The pilot said that he then confirmed a lighted chip light on his panel as well, and shortly thereafter felt the first engine shudder/backfire. He then made a "Mayday" call, and proceeded to the nearest airport, Deland Municipal Airport, Deland, Florida, to affect a landing. Along the way, the pilot said he increased power in an attempt to ensure he would reach the airport, and initially felt the airplane accelerate, but about 30 seconds later, in addition to the illuminated chip light and vibration in the engine, suddenly there was a severe rumble again, followed by the engine operating distinctively rough. He noted little puffs of black smoke, coming out of the stacks around the fuselage, and since there was a heavy forested area ahead, turned the airplane toward a field to the east, to affect a landing. As he prepared to land, the pilot said he opened the canopy, secured the fuel flow, placed the propeller control in high pitch setting to minimize drag, secured battery power, and established a glide. He said the approach and landing flare/touchdown were uneventful, but during the landing rollout the airplane impacted a ditch, and incurred substantial damage. According to the FAA inspector who responded to the accident, an engine master rod bearing failed. The inspector further stated that there were metal fragments throughout the oil, and the degree of damage and metal fragments made it difficult to determine what may precipitated the bearing failure.