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.
Farmingdale, NY
The pilot reported that she was in an extended traffic pattern for runway 19. During the turn to final, about 10 miles from the airport, the tower controller instructed her to overfly the airport. She added power and climbed to 2000 feet, still heading toward the airport. About 2 miles from the approach end of runway 19, the tower controller then cleared her to land. The pilot reduced the power, applied carburetor heat, and established a descent towards the airport. On short final, about 200 feet above the ground, the tower controller instructed her to go around. She tried to apply power; however, the engine did not respond. She observed the tachometer was indicating about 1000 RPM, and the mixture was rich. The pilot performed a forced landing during which the airplane impacted a tree and slid into a fence. Examination of the aircraft did not disclose evidence of mechanical malfunction. A functional check of the engine revealed satisfactory operation.
loss of engine power for undetermined reasons.
On April 6, at 1645 eastern daylight time, a Cessna 152, N67562, was substantially damaged during a forced landing at the Republic Airport, Farmingdale, New York. Visual meteorological conditions prevailed, and no flight plan had been filed for the local, personal flight which departed at 1530 and was conducted under 14 CFR Part 91. According to the NTSB Form 6120.1/2, the pilot reported that she was in an extended traffic pattern for runway 19. During the turn to final, about 10 miles from the airport, the tower controller instructed her to overfly the airport. She added power and climbed to 2000 feet, still heading toward the airport. About 2 miles from the approach end of runway 19, the tower controller then cleared her to land. The pilot reduced the power, added carburetor heat, and established a descent towards the airport. On short final, about 200 feet above the ground, the tower controller instructed her to go around. She added power; however, the engine did not respond. She observed the tachometer was indicating about 1000 RPM, and the mixture was rich. The pilot performed a forced landing during which the airplane impacted a tree and slid into a fence. Examination of the wreckage by the Federal Aviation Administration (FAA) Inspector did not disclose evidence of mechanical malfunctions with the airframe. A functional test of the engine revealed satisfactory operation.