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.
Enochville, NC
Witnesses watched the airplane departing the airstrip, and when it did not return, they suspected that something had gone wrong. About 1 or 2 miles from the airport the pilot said, "I had an engine failure." He tried to land in a field but struck the top of a tree and then hit the ground. The FAA examined the wreckage, and found that there was fuel in the tanks, the fuel cap for the right fuel tank was not on the tank and was missing. External inspection indicated the engine had no fuel or oil leaks, the condition and color of the plugs insulation and electrode indicated no fouling, the engine was a little on the lean side, and operated on automotive gasoline. The pilot indicated that he flew a total of 5 hours in the accident airplane in the past 90 days, 3 hours in the past 30 days, and none the 24 hours before the accident.
A loss of engine power for undetermined reasons.
On September 23, 2000, about 1906 eastern daylight time, a Piper PA-22-135, N3483A, owned by a private individual, lost engine power and impacted with a tree during a forced landing near Enochville, North Carolina. Visual meteorological conditions prevailed at the time. No flight plan was filed for the 14 CFR Part 91 personal flight. The airplane was substantially damaged. The private-rated pilot reported serious injuries. The flight had departed from a private airstrip at an unknown time. Witnesses watched the airplane departing the airstrip, and when it did not return, they suspected that something had gone wrong. The airplane was found, and the pilot told his wife that there was an "engine failure." The pilot stated, "...about 1 or 2 miles from [the] airport I had an engine failure. Tried to land in a field but caught top of [a] tree and then hit the ground." When the FAA examined the wreckage, they found that there was fuel in the tanks. The fuel cap for the right fuel tank was not on the tank and was missing. According to the FAA inspector's statement, "...external inspection indicated the engine had no fuel or oil leaks and appeared to be well maintained. Several ignition plugs were removed for examination. The condition and color of the plugs insulation and electrode indicated no fouling. Indications appeared the engine was a little on the lean side...the aircraft was operating on automotive gasoline." It was not determined how long the airplane sat with the fuel in the tanks. However, the pilot indicated on the NTSB form 6120.1/2, that he flew a total of 5 hours in the accident airplane in the past 90 days, 3 hours in the past 30 days, and none the 24 hours before the accident.