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.
West Chicago, IL
The pilot reported that 'nothing was abnormal' during the takeoff on runway 33. At an altitude of 500 feet above ground level, the engine 'began to run roughly and lose power.' He 'turned back toward the field, established best glide, and called the tower.' He checked the engine controls. He reported that he felt heat on his legs and smelled 'something hot'. No smoke or flames were visible. He attempted to land on runway 19L but 'excess altitude, airspeed, and a downwind approach made it impossible... .' He advanced the throttle to full which 'resulted in almost no acceleration.' The pilot reported that he elected to land in a farm field south of the airport. He conducted a soft field landing. The airplane impacted a row of trees and bushes 'at the end of the field.' Examination of the airplane revealed engine controls were intact. Fuel samples exhibited no evidence of contamination. The engine operated normally during a warm up, run up, and a full power test run.
The loss of power for undetermined reasons.
On February 8, 1997, at 1515 central standard time, a Cessna 172, N13611, operated by Shamrock Aviation, Ltd., sustained substantial damage when it impacted trees during a forced landing in West Chicago, Illinois. The private pilot and one passenger reported no injuries. The local, personal flight originated about 1513 and was conducted under 14 CFR Part 91. Visual meteorological conditions prevailed and no flight plan was filed. During a telephone interview, conducted on March 18, 1997, the pilot reported that he performed a "normal" run up and "nothing was abnormal" during the takeoff on runway 33. At an altitude of 500 feet above ground level, the engine "began to run roughly and lose power." He reported that he had to lower the nose to maintain an airspeed of 75 knots. He "turned back toward the field, established best glide, and called the tower." He checked the engine controls. He reported that he felt heat on his legs and smelled "something hot". No smoke or flames were visible. He attempted to land on runway 19L but "excess altitude, airspeed, and a downwind approach made it impossible... ." He advanced the throttle to full which "resulted in almost no acceleration." The pilot reported that he elected to land in a farm field south of the airport. He conducted a soft field landing. The airplane impacted a row of trees and bushes "at the end of the field." Examination of the airplane revealed engine controls were intact. Fuel samples were clear and clean. The engine operated normally during a warm up, run up, and a full power test run.