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.
Apopka, FL
The pilot reported that, after an uneventful cross-country flight, he observed animals on the runway during the approach, so he chose to perform a go-around. The engine did not produce full power during the go-around, and the airplane would not maintain altitude, so he performed a forced landing short of the runway, during which the airplane collided with trees. An examination of the wreckage and a test run of the engine did not reveal any evidence of a preaccident malfunction or failure that would have precluded normal operation. The recorded systems and engine data showed that there should have been adequate fuel on board to complete the flight. The reason for the loss of engine power could not be determined.
A partial loss of engine power during a go-around for reasons that could not be determined based on the available information, which resulted in a forced landing.
On December 30, 2018, about 2025 eastern standard time, a Cessna LC41-550FG, N78JE, was substantially damaged during a forced landing at Apopka Airport (X04), Apopka, Florida. The private pilot was not injured. The airplane was operated by Hardwood Transport LLC under the provisions of Title 14 Code of Federal Regulations Part 91. Night, visual meteorological conditions prevailed, and no flight plan was filed for the flight to X04. The flight departed Greater Binghamton Airport (BGM), Binghamton, New York about 1523. The pilot reported that he left BGM with full fuel tanks, or 102 usable gallons of fuel on board. Following an uneventful flight, he set up for a visual approach to runway 33 at X04. While on final approach, he observed animals on the runway. He performed a go-around and noted that the engine did not produce full power when the throttle was advanced. While on the downwind leg of the traffic pattern, the airplane would not maintain altitude, so the pilot performed a forced landing. The airplane collided with trees and came to rest in a wooded area off the airport property. The wreckage was recovered to a storage facility and was examined by investigators. Both fuel tanks were breached during the impact sequence and the tanks were dry. The wire bundle connecting the boost pump was observed separated. When reconnected, the wire bundle was tight. Blue, contaminant free fuel was observed in the fuel strainer bowl. The fuel caps were observed installed in the filler necks. The engine was sent to the manufacturer's facility for examination. Due to the minor amount of impact damage to the engine, the investigation team elected to attempt a test run. After some minor repairs to ready the engine for the test cell, the engine experienced a normal start on the first attempt without hesitation or stumbling in observed RPM. Throughout the test phase, the engine accelerated normally without any hesitation, stumbling or interruption in power and demonstrated the ability to produce rated horsepower. The airplane was equipped with a Garmin G1000 integrated flight deck. The G1000 recorded flight and systems data, including fuel quantity and engine performance. The data indicated that the flight began with 51 gallons per tank, or 102 gallons total useable fuel on board. Fuel quantity indications during the final 15 minutes were erratic; however, the total fuel quantity about 15 minutes prior to the accident was about 17 gallons. The average fuel flow during the same time period was about 13.3 gallons/hr.