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.
Belle Glade, FL
The pilot said he had been airborne for about 20 minutes and looked at the JPI indicator which showed that the oil temperature was 89 degrees and the oil pressure was zero. He said he then entered a turn to go to State Road 84 and execute an emergency landing, and during the turn a loud bang occurred and the engine ceased operating. He then saw a dirt road about 15 miles southwest of State Road 84, and executed a forced landing there instead, but during the landing rollout the left wing tip impacted a pick-up truck that had been parked on the dirt road and it veered into a ditch. The FAA Inspector who responded to the accident scene found clean oil on the bottom of the fuselage, but did not determine the source of the oil leak. The following day when salvage personnel returned to the accident scene to retrieve the airplane wreckage for a detailed examination, they found that the airplane had burned. The engine compartment and aft, to include the cabin and inboard two thirds of both wings had incurred fire damage. Only the wing tips and empennage remained undamaged. Examination of the engine revealed that the rear and right side of the engine had incurred fire damage. In addition, the examination showed that there was an opening in the engine case at the No. 4 cylinder position, and the No. 4 connecting rod was protruding through the opening. Both the No. 4 and No 5 connecting rods had separated from the crankshaft, and both connecting rods as well as all main bearings exhibited signatures consistent with oil starvation.
The loss of engine oil for undetermined reasons that resulted in the engine seizing, a forced landing on a dirt road, and an impact with a vehicle on the dirt road during the landing rollout.
On November 17, 2001, about 1125 eastern standard time, a Beech P35, N9754Y, registered to and operated by a private individual, as a Title 14 CFR Part 91 personal flight, incurred a loss of engine power, while in cruise flight, about 12 miles south of Belle Glade, Florida. Visual meteorological conditions prevailed, and no flight plan was filed. The commercial-rated pilot received serious injuries, and one passenger received minor injuries. The aircraft incurred substantial damage. The flight originated from Pembroke Pines, Florida, the same day, about 1100. The pilot stated that he estimated that he had been airborne for about 20 minutes when he looked at the JPI indicator on the instrument panel and noted that the oil temperature was 89 degrees and the oil pressure was zero. He had been receiving visual flight rules (VFR) flight following, and was talking to Miami Air Traffic Control Center, so he then told them that he was having engine problems and will attempt to make an emergency landing on State Road 84. According to the pilot, as he maneuvered the aircraft into a turn to proceed to State Road 84, there was a loud bang and the engine ceased operating. He said he then saw a dirt road about 15 miles southwest of State Road 84, so he prepared for a forced landing to the dirt road instead. The approach and touchdown on the dirt road were "perfect," but he said he had not seen a pick-up truck that had been parked on the dirt road prior to touchdown, and as the rollout continued the airplane's left wing tip impacted the truck, and the airplane veered off the road into a ditch, incurring damage. On November 17, 2001, an FAA Inspector responded to the accident scene, and stated that he saw clean oil on the bottom of the fuselage, but added that he was unable to determine from where the oil had come. The following day, when salvage personnel returned to the accident scene to retrieve the wreckage for a detailed examination, they found that the aircraft had burned. The airplane engine compartment and aft, to include the cabin and inboard two thirds of the airplane wings had incurred fire damage. Only the wing tips and empennage had not incurred fire damage. On December 5, 2001, the NTSB along with a representative from Teledyne Continental Motors, examined the accident airplane's engine. The examination revealed the existence of fire damage. In addition, the examination showed that there was an opening in the engine case at the No. 4 cylinder position, and the No. 4 connecting rod was protruding through the opening. Both the No. 4 and No 5 connecting rods had separated from the crankshaft , and both connecting rods as well as all main bearings exhibited signatures consistent with oil starvation.