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.
Atwater, CA
The pilot said that the flight departed runway 30 and at about 900 feet during the initial climb the engine power level smoothly reduced to about 2,000 RPM. The pilot noted that there was no roughness associated with the power loss. The pilot said she was concerned about the nature of the terrain ahead and elected to perform a 180 degree turn and land down wind on runway 12. The aircraft touched down about two thirds of the way down the runway and the pilot thought the aircraft could not be stopped prior to colliding with a fence at the runway end. She said she added all available power and the aircraft lifted off and over the fence. The aircraft then settled back to the ground and collided with two coral fences about one quarter of a mile beyond the end of the runway. The pilot said the winds at the time were from about 310 degrees at about 10 knots. The engine and airframe were examined by FAA airworthiness inspectors who did not find evidence to explain the reported loss of power.
THE PARTIAL LOSS OF ENGINE POWER FOR UNDETERMINED REASONS AND THE PILOTS FAILURE TO ATTAIN THE PROPER TOUCHDOWN POINT DURING THE SUBSEQUENT FORCED LANDING ATTEMPT BACK ON THE RUNWAY. FACTORS IN THE ACCIDENT WERE THE TAIL WIND CONDITION ENCOUNTERED DURING THE LANDING ATTEMPT AND THE SHORT NATURE OF THE RUNWAY.
THE PILOT SAID THAT THE FLIGHT DEPARTED RUNWAY 30 AND AT ABOUT 900 FEET DURING THE INITIAL CLIMB THE ENGINE POWER LEVEL SMOOTHLY REDUCED TO ABOUT 2,000 RPM. THE PILOT NOTED THAT THERE WAS NO ROUGHNESS ASSOCIATED WITH THE POWER LOSS. THE PILOT SAID SHE WAS CONCERNED ABOUT THE NATURE OF THE TERRAIN AHEAD AND ELECTED TO PERFORM A 180 DEGREE TURN AND LAND DOWN WIND ON RUNWAY 12. THE AIRCRAFT TOUCHED DOWN ABOUT TWO THIRDS OF THE WAY DOWN THE RUNWAY AND THE PILOT THOUGHT THE AIRCRAFT COULD NOT BE STOPPED PRIOR TO COLLIDING WITH A FENCE AT THE RUNWAY END. SHE SAID SHE ADDED ALL AVAILABLE POWER AND THE AIRCRAFT LIFTED OFF AND OVER THE FENCE. THE AIRCRAFT THEN SETTLED BACK TO THE GROUND AND COLLIDED WITH TWO CORAL FENCES ABOUT ONE QUARTER OF A MILE BEYOND THE END OF THE RUNWAY. THE PILOT SAID THE WINDS AT THE TIME WERE FROM ABOUT 310 DEGREES AT ABOUT 10 KNOTS. THE ENGINE AND AIRFRAME WERE EXAMINED BY FAA AIRWORTHINESS INSPECTORS WHO DID NOT FIND EVIDENCE TO EXPLAIN THE REPORTED LOSS OF POWER.