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.
Winston-Salem, NC
Before landing, the pilot was advised by approach control that Boeing 737 training was being conducted on runway 33. The pilot agreed to land on runway 21 and hold short of runway 33. The aircrews conducting 737 training were so advised. The aircraft was on final approach shortly after the tower closed at 2300 EST. The pilot did not see the runway lights, but at first, he thought they were set on low intensity and could not be seen with hangar and ramp lights in the background. At 150 to 200 ft AGL, he saw the runway when it was illuminated by his landing lights and realized the runway lights were not on. Quickly, he decided to land rather than go-around and conflict with the traffic using runway 33. Shortly after reaching for the throttles to reduce power to idle and land, the plane stalled from 20 to 50 ft AGL and landed hard. An investigation revealed that the pilot had inadvertently moved the propeller controls to the reverse pitch position. The pilot had been on duty since his first takeoff at 0600.
BEFORE LANDING, THE PILOT WAS ADVISED BY APPROACH CONTROL THAT BOEING 737 TRAINING WAS BEING CONDUCTED ON RUNWAY 33. THE PILOT AGREED TO LAND ON RUNWAY 21 AND HOLD SHORT OF RUNWAY 33. THE AIRCREWS CONDUCTING 737 TRAINING WERE SO ADVISED. THE AIRCRAFT WAS ON FINAL APPROACH SHORTLY AFTER THE TOWER CLOSED AT 2300 EST. THE PILOT DID NOT SEE THE RUNWAY LIGHTS, BUT AT FIRST, HE THOUGHT THEY WERE SET ON LOW INTENSITY AND COULD NOT BE SEEN WITH HANGAR AND RAMP LIGHTS IN THE BACKGROUND. AT 150 TO 200 FT AGL, HE SAW THE RUNWAY WHEN IT WAS ILLUMINATED BY HIS LANDING LIGHTS AND REALIZED THE RUNWAY LIGHTS WERE NOT ON. QUICKLY, HE DECIDED TO LAND RATHER THAN GO-AROUND AND CONFLICT WITH THE TRAFFIC USING RUNWAY 33. SHORTLY AFTER REACHING FOR THE THROTTLES TO REDUCE POWER TO IDLE AND LAND, THE PLANE STALLED FROM 20 TO 50 FT AGL AND LANDED HARD. AN INVESTIGATION REVEALED THAT THE PILOT HAD INADVERTENTLY MOVED THE PROPELLER CONTROLS TO THE REVERSE PITCH POSITION. THE PILOT HAD BEEN ON DUTY SINCE HIS FIRST TAKEOFF AT 0600.