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.
Lansing, KS
While in cruise flight, the pilot became ill and decided he could not safely continue to fly the airplane to the destination airport. The pilot then initiated a forced landing to a field a few miles from the airport. During the forced landing, the airplane impacted a rising embankment and came to rest upright in the field. Examination of the airplane by the inspector revealed the nose gear was separated and the firewall was buckled.
the pilot's inability to maintain aircraft control during the forced landing which resulted in a collision with terrain. A contributing factor was the pilot becoming ill during cruise flight.
On December 4, 2005, at 1500 central standard time, a Cessna 182E single-engine airplane, N123F, was substantially damaged during a forced landing after the pilot in command became ill during cruise flight near Lansing, Kansas. The private pilot and two passengers sustained minor injuries. The airplane was registered to and operated by the pilot. Visual meteorological conditions prevailed, and a flight plan was not filed for the Title 14 Code of Federal Regulations Part 91 personal flight. The local flight departed Highcrest Air Park (SN83), Lansing, Kansas, at an unknown time. According to a Federal Aviation Administration inspector who responded to the accident site, the pilot became ill while in cruise flight and decided he could not safely continue to fly the airplane to SN83. The pilot then initiated a forced landing to a field a few miles from SN83. During the forced landing, the airplane impacted a rising embankment and came to rest upright in the field. Examination of the airplane by the inspector revealed the nose gear was separated and the firewall was buckled.