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.
Okanogan, WA
While maneuvering over an orchard that he was preparing to spray, the pilot flew through a sudden downdraft which pushed him up against his seat belt and shoulder straps. About two seconds later, the engine quit and could not be started. The pilot elected to attempt the forced landing in an alfalfa field that was straight ahead of him. The aircraft initially touched down in the alfalfa, but bounced back into the air and touched down a second time in an area that had been freshly plowed. The main gear sank into the soft dirt and the aircraft nosed over. During the post-accident engine inspection, the engine would not start until the carburetor had been struck a couple of times with a hammer. After the carburetor was jarred by the hammer, the engine started and was able to be test run. Disassembly of the carburetor did not reveal whether the float had stuck, an orifice had been temporarily blocked, or whether there had been some other malfunction.
A malfunctioning carburetor. Factors include a downdraft, and the soft dirt in a newly plowed field.
On May 19, 1999, approximately 1145 Pacific daylight time, a Grumman G-164B, N6861K, nosed over in a freshly-plowed field during a forced landing near Okanogan, Washington. The pilot was not injured, but the aircraft, which was owned and operated by Okanogan Air Service, sustained substantial damage. The local 14 CFR Part 137 aerial application flight, which had been airborne for about 30 minutes, was operating in visual meteorological conditions. No flight plan had been filed, and there was no report of an ELT activation. According to the pilot, while maneuvering over an orchard he was about to spray, the aircraft encountered a "big bump of air" which pulled him up against his seatbelt and shoulder harness. About two seconds later, the engine suddenly lost power, momentarily sputtered, and then quit altogether. The pilot elected to make a forced landing in an Alfalfa field that was straight ahead, so he dumped his remaining chemical and prepared to land. The aircraft initially touched down in the alfalfa, but bounced back into the air and touched down again in a freshly plowed portion of the field. After this second touchdown, the main gear sank into the soft dirt and the aircraft nosed over. During a post-accident engine run, the engine would not start until the carburetor was tapped several times with a hammer. After jarring the carburetor with the hammer, the engine was able to be started and run. Disassembly of the carburetor did not reveal whether the float had stuck, contamination had temporarily blocked an orifice, or whether there was some other malfunction.