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.
Healdsburg, CA
The pilot said he had completed an uneventful flight earlier in the day. On the accident flight, he performed an engine run-up, which included a magneto check with no mechanical anomalies encountered. He taxied to the active runway (runway 13), and noted the winds were light about 5 knots from the south. The takeoff roll was normal, and they lifted off at 50 mph. After rotation, the airplane started a left bank for no apparent reason. The pilot did not pull back on the control stick; however, he attempted to align the airplane with the runway. He noted that the airplane did not respond to his roll input and continued in the left bank. The pilot also stated that the airplane had started a slight climb just prior to impacting the vineyard. After the initial contact with the vineyard, the airplane became airborne again and then dropped back into the vineyard. The pilot stated that there were no mechanical problems with the airplane and he believes that the winds may have shifted to more of a south wind at the time of the loss of control event. Reported winds at the time were from 140 degrees at 5 knots.
The pilot's inadequate compensation for the crosswind condition and failure to maintain directional/lateral control during the initial climb.
According to the pilot, he had completed an uneventful flight earlier in the day. On the accident flight, he performed an engine run-up, which included a magneto check with no mechanical anomalies encountered. He taxied to the active runway (runway 13), and noted the winds were light, about 5 knots from the south. The takeoff roll was normal, and they lifted off at 50 mph. After rotation, the airplane started a left bank for no apparent reason. The pilot did not pull back on the control stick; however, he attempted to align the airplane with the runway. He noted that the airplane did not respond to his input and continued in the left bank. The pilot also stated that the airplane had started a slight climb just prior to impacting a vineyard. After the initial contact with the vineyard, the airplane became airborne again and then dropped back into the vineyard. The pilot stated that there were no mechanical problems with the airplane and he believes that the winds may have shifted to more of a south wind at the time of the loss of control event. Reported winds at the time were from 140 degrees at 5 knots.