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.
Philadelphia, PA
The aircrews of a United DC-10 (FLT 99 Heavy) and two U.S. Air DC-9's (FLT 25 and FLT 199) taxied for takeoff at about the same time. Due to delays, the No. 2 engine of FLT 199 was shut down in accordance with applicable fuel conservation procedures. After FLT 99 was cleared for takeoff, the aircrew of FLT 199 started their engine, but it torched and emitted flames from the tail cone. The captain of FLT 25 saw the flames and transmitted on tower frequency, "99, you're right engine's on fire." At about that time, United FLT 99 Heavy was lifting off. Thinking he had an engine fire, the captain of United FLT 99 Heavy aborted above V1/VR rather than continuing into a low ceiling with fog and rain. The captain thought he could stop on the hard surface, but was unable. The plane came to rest on muddy terrain. One passenger was injured during evacuation. During this sequence, the tower controller was unable to see the runway due to the low visibility (3/8 mi).
THE AIRCREWS OF A UNITED DC-10 (FLT 99 HEAVY) AND TWO U.S. AIR DC-9'S (FLT 25 AND FLT 199) TAXIED FOR TAKEOFF AT ABOUT THE SAME TIME. DUE TO DELAYS, THE NO. 2 ENGINE OF FLT 199 WAS SHUT DOWN IN ACCORDANCE WITH APPLICABLE FUEL CONSERVATION PROCEDURES. AFTER FLT 99 WAS CLEARED FOR TAKEOFF, THE AIRCREW OF FLT 199 STARTED THEIR ENGINE, BUT IT TORCHED AND EMITTED FLAMES FROM THE TAIL CONE. THE CAPTAIN OF FLT 25 SAW THE FLAMES AND TRANSMITTED ON TOWER FREQUENCY, "99, YOU'RE RIGHT ENGINE'S ON FIRE." AT ABOUT THAT TIME, UNITED FLT 99 HEAVY WAS LIFTING OFF. THINKING HE HAD AN ENGINE FIRE, THE CAPTAIN OF UNITED FLT 99 HEAVY ABORTED ABOVE V1/VR RATHER THAN CONTINUING INTO A LOW CEILING WITH FOG AND RAIN. THE CAPTAIN THOUGHT HE COULD STOP ON THE HARD SURFACE, BUT WAS UNABLE. THE PLANE CAME TO REST ON MUDDY TERRAIN. ONE PASSENGER WAS INJURED DURING EVACUATION. DURING THIS SEQUENCE, THE TOWER CONTROLLER WAS UNABLE TO SEE THE RUNWAY DUETO THE LOW VISIBILITY (3/8 MI).