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.
Baltimore, MD
The student pilot initiated a short field takeoff from a 2,200 foot runway, after obtaining full power and then releasing the brakes. The flight instructor stated that he checked the engine RPM before the brakes were released. During the takeoff roll, the airplane rotated beyond the midfield position. The instructor stated that the airplane was not climbing so more elevator back pressure was applied, during which the stall warning horn sounded. As the airplane climbed out of ground effect, the stall warning horn sounded again. The airplane then impacted trees at the departure end of the runway, but continued flying. The flight continued to a nearby airport, where a low approach was made (for ground personnel to check for landing gear damage), followed by a full stop landing.
the student pilot's premature rotation and inadequate supervision by the flight instructor (CFI), which resulted in failure of the flight crew to obtain adequate airspeed during takeoff for a proper rate of climb. Trees at the departure end of the runway were a related factor.
On December 15, 1996, about 1030 eastern standard time, a Cessna 152, N714YW, operated by Free Flight Aviation Inc., was substantially damaged when it impacted trees during the initial takeoff climb from the Baltimore Airpark (1W2), Baltimore, Maryland. The certificated flight instructor and student pilot were not injured. Visual meteorological conditions prevailed for the flight destined for Martin State Airport (MTN), Baltimore, Maryland. No flight plan was filed for the flight conducted under 14 CFR Part 91. In a statement submitted by the flight instructor, he stated that the flight originated earlier that morning at the Martin State Airport (MTN), Baltimore, Maryland. Prior to landing at 1W2, the flight involved a series of maneuvers during which no problems were encountered. He then intended to depart runway 27, a 2,200 foot long, 49 foot wide, runway from 1W2. A short field takeoff was performed with the use of 10 degrees of flaps and brake application while applying full power. The instructor stated, "We did pre-takeoff check, set 10 degrees flap, taxied out to position [and] held the brakes. Applied full power, checked for RPM and released brakes. . . .We lifted out past midfield down runway, the plane did not want to climb out and more back pressure caused a stall chirp. When we got out of ground effect, we got another stall chirp. . . ." The airplane impacted trees at the departure end of the runway. The pilot stated that he then elected to continue to MTN, located about 5 miles south. When the flight arrived at MTN, a low approach was performed for ground personnel to check for landing gear damage, followed by a full stop landing. The Federal Aviation Administration Inspector conducted an engine test run. During the engine run, a static run-up was performed satisfactorily.