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.
Waukesha, WI
The airplane was 6 miles from the airport when 'something broke on the throttle. The airplane's engine would only develop idle power.' The pilot 'trimmed the airplane for 120 miles per hour and tried to make the runway.' When he noticed that his visual glide path was too low, the pilot elected to land the airplane on a highway between moving automobiles. During the landing, the airplane stuck a curb, an automobile and a truck before coming to a stop on the highway. Examination revealed that the throttle linkage cable to the throttle arm spring had broken leaving the throttle arm in the idle power position.
On July 24, 1996, at 1720 central daylight time (cdt), a Long Eze, N303Y, operated by a private pilot, sustained substantial damage when on approach to landing, the airplane lost partial power. The airplane subsequently struck two vehicles and impacted on a road. Visual meterorological conditions prevailed at the time of the accident. The personal flight was being conducted under 14 CFR Part 91. A flight plan was not on file and the pilot reported no injuries. The local flight originated at Grand Haven, Michigan, at 1707 eastern daylight time. In his written statement, the pilot said that he was six miles from the airport when "something broke on the throttle. The airplane's engine would only develop idle power." The pilot "trimmed the airplane for 120 miles per hour and tried to make the runway." When he noticed that the Visual Approach Slope Indicator (VASI) lights on the airport indicated that his visual glide path was too low, the pilot elected to land the airplane on a highway between moving automobiles. During the landing, the airplane stuck a curb, an automobile and a truck before coming to a stop on the highway. The Federal Aviation Administration (FAA) inspector who examined the wreckage at the scene found the airplane resting on a curb at the intersection of two highways. Both wings were crushed along the leading edges. Both wing spars were broken and pushed aft. The forward fuselage and from the nose, aft to the cockpit was crushed up from underneath. The forward bulkhead was broken. The nose gear had broken off. Both main landing gear had broken off. Flight control continuity was confirmed. Examination of the engine controls revealed the throttle linkage cable to the throttle arm spring had broken inside the housing, leaving the throttle arm in the idle power position. No other anomalies were found.