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.
Chandler, AZ
The student pilot related that she was on her second solo flight and had planned to perform some touch and go landings then depart the airport to the south for some air work. Upon completion of the planned air work, she attempted to find the airport and stated that she had difficulties finding the airport and possibly overflew it. When she found the airport, she said that she became concerned with the aircraft's fuel status and about traffic around the airport. She stated that she got 'low' on her approach and then noticed that the engine '...did not sound right.' The pilot stated: 'I know that I was too low because both VASI lights were red. That is when I must have pulled back on the controls and stalled the plane.' An airworthiness inspector from the Scottsdale (Arizona) Flight Standards District Office (FAA) inspected the aircraft after the accident and could find no reason for the engine to have lost power.
THE STUDENT PILOT INADVERTENTLY STALLING THE AIRCRAFT AND AN INADEQUATE ALTITUDE TO PERFORM A STALL RECOVERY. FACTORS IN THIS ACCIDENT WERE: LACK OF TOTAL EXPERIENCE AND STUDENT'S ANXIETY.
THE STUDENT PILOT RELATED THAT SHE WAS ON HER SECOND SOLO FLIGHT AND HAD PLANNED TO PERFORM SOME TOUCH AND GO LANDINGS THEN DEPART THE AIRPORT TO THE SOUTH FOR SOME AIR WORK. UPON COMPLETION OF THE PLANNED AIR WORK, SHE ATTEMPTED TO FIND THE AIRPORT AND STATED THAT SHE HAD DIFFICULTIES FINDING THE AIRPORT AND POSSIBLY OVERFLEW IT. WHEN SHE FOUND THE AIRPORT, SHE SAID THAT SHE BECAME CONCERNED WITH THE AIRCRAFT'S FUEL STATUS AND ABOUT TRAFFIC AROUND THE AIRPORT. SHE STATED THAT SHE GOT 'LOW' ON HER APPROACH AND THEN NOTICED THAT THE ENGINE '...DID NOT SOUND RIGHT.' THE PILOT STATED: 'I KNOW THAT I WAS TOO LOW BECAUSE BOTH VASI LIGHTS WERE RED. THAT IS WHEN I MUST HAVE PULLED BACK ON THE CONTROLS AND STALLED THE PLANE. AN AIR WORTHINESS INSPECTOR FROM THE SCOTTSDALE (ARIZONA) FLIGHT STANDARDS DISTRICT OFFICE (FAA) INSPECTED THE AIRCRAFT AFTER THE ACCIDENT AND COULD FIND NO REASON FOR THE ENGINE TO HAVE LOST POWER.