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.
Brighton, MI
The pilot stated that, after a local pleasure flight with his children as passengers, he returned to his departure airport and re-entered the traffic pattern for runway 22. He reported that while on final approach he didn't like the way things looked and chose to go-around. He stated that initially the aircraft responded normally and began to climb, but 'immediately after metering off flaps, the engine began to vibrate grossly out-of-balance.' The pilot performed emergency procedures, but the 'loss of power and altitude continued....lake landing was very suspect due to lack of altitude. Reviewed area for alternative - none!' The aircraft struck the top of a large tree and then contacted a smaller tree before it descended into the lake. Pilot and passengers were able to exit the aircraft before it sank. The aircraft was submerged for more than 20 hours before it was recovered from the lake. A subsequent engine run-up was satisfactorily accomplished.
THE UNSUITABLE TERRAIN (TREES AND A LAKE) ENCOUNTERED DURING A FORCED LANDING MADE NECESSARY BY THE PARTIAL FAILURE OF THE AIRCRAFT'S POWERPLANT DURING AND ATTEMPTED GO-AROUND. THE OCCUPANTS WERE ABLE TO EXIT THE AIRCRAFT BEFORE IT SANK; THE AIRCRAFT WAS SUBMERGED FOR OVER 20 HOURS BEFORE IT WAS SALVAGED FROM THE LAKE.
THE PILOT STATED THAT, AFTER A LOCAL PLEASURE FLIGHT WITH HIS CHILDREN AS PASSENGERS, HE RETURNED TO HIS DEPARTURE AIRPORT AND RE-ENTERED THE TRAFFIC PATTERN FOR RUNWAY 22. HE REPORTED THAT WHILE ON FINAL APPROACH HE DIDN'T LIKE THE WAY THINGS LOOKED AND CHOSE TO GO-AROUND. HE STATED THAT INITIALLY THE AIRCRAFT RESPONDED NORMALLY AND BEGAN TO CLIMB, BUT 'IMMEDIATELY AFTER METERING OFF FLAPS, THE ENGINE BEGAN TO VIBRATE GROSSLY OUT-OF-BALANCE.' THE PILOT PERFORMED EMERGENCY PROCEDURES, BUT THE 'LOSS OF POWER AND ALTITUDE CONTINUED....LAKE LANDING WAS VERY SUSPECT DUE TO LACK OF ALTITUDE. REVIEWED AREA FOR ALTERNATIVE - NONE!' THE AIRCRAFT STRUCK THE TOP OF A LARGE TREE AND THEN CONTACTED A SMALLER TREE BEFORE IT DESCENDED INTO THE LAKE. PILOT AND PASSENGERS WERE ABLE TO EXIT THE AIRCRAFT BEFORE IT SANK. THE AIRCRAFT WAS SUBMERGED FOR MORE THAN 20 HOURS BEFORE IT WAS RECOVERED FROM THE LAKE. A SUBSEQUENT ENGINE RUN-UP WAS SATISFACTORILY ACCOMPLISHED.