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.
Fort Worth, TX
The airplane had just taken off and was climbing out when the engine started to lose rpm. The airplane continued to climb straight for a couple of hundred feet, then the pilot turned the airplane crosswind hoping to make it around the pattern and land. When the aircraft turned downwind it wasn't climbing, prompting the pilot to make a forced landing in a field. The airplane touched down, impacted a berm, bounced, then impacted the terrain a second time before coming to rest in an upright position. An examination by an FAA inspector revealed the mixture control rod was separated from the carburetor.
the partial loss of engine power due to the mixture control rod separating from the carburetor. A contributing factor was the lack of suitable terrain for the forced landing.
On June 7, 2002, approximately 1740 central daylight time, a Cessna 150 single-engine airplane, N6249R, was substantially damaged when it impacted terrain during a forced landing following a partial loss of engine power near Forth Worth, Texas. The airplane was registered to and operated by the pilot. The private pilot and his passenger were not injured. Visual meteorological conditions prevailed, and a flight plan was not filed for the 14 Code of Federal Regulations Part 91personal flight. The flight originated from Hicks Airfield Airport, Fort Worth, at 1735. According to the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1/2), the pilot had just taken off and was climbing out "when the engine started to lose some rpm." The engine continued to make 2,300 to 2,400 rpm and the airplane was climbing. The pilot stated the airplane climbed straight for a couple of hundred feet, then he turned crosswind. He was hoping to "make it around the pattern and land." He then reported "I turned downwind and was not climbing anymore, and there was a pretty good looking field and the rpm was dropping, so I opted to put down in that field." The airplane touched down, impacted a "hidden berm," bounced, then impacted the terrain a second time before coming to rest in an upright position. According to an FAA inspector, who responded to the accident site, the nose gear was folded aft, the engine mount was damaged, and the firewall sustained structural damage. The inspector also reported that the mixture control rod was found separated from the carburetor.