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.
Wichita, KS
The pilot flying stated that he had recently completed simulator training in the airplane type and that the accident flight was his first flight in an actual airplane of that type. The pilot-in-command had the pilot flying sit in the left seat for the flight and allowed him to perform the approach and landing. During preflight and while airborne, the pilots discussed braking procedures and techniques, which included the need to apply braking evenly and firmly. During landing, the pilot applied brakes, and, a few seconds later, the airplane began swerving left and right. The airplane exited the runway and stopped. The airplane was equipped with a flight data recorder, and no anomalies were noted in the data that would have contributed to the accident. The accident likely occurred as a result of the pilot's improper brake application, which resulted in the loss of directional control.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
On October 15, 2013, about 1900 central daylight time, an Embraer EMB-500, N610AS, was substantially damaged when it departed the runway while landing at Colonel James Jabara Airport (KAAO), Wichita, Kansas. Both of the Airline Transport rated pilots were uninjured. The airplane was registered to and operated by Executive Flight Services, Inc., and doing business as Executive Airshare. The airplane was being operated under the provisions of 14 Code of Federal Regulations Part 91 as a repositioning flight. Visual meteorological conditions prevailed for the flight, which operated on an instrument flight rules flight plan. The flight originated from Charles B. Wheeler Downtown Airport (KMKC), Kansas City, Missouri at 1816. The pilot flying stated he had recently completed training in the Embraer EMB-500, and that the accident flight was his first flight in an actual EMB-500 airplane. The pilot-in-command elected to place the pilot in the left seat for the flight, and allowed him to perform the approach and landing. The pilots discussed braking procedures and techniques during both preflight and while airborne, which included the necessity to apply braking evenly and firmly. The pilot stated the landing was firm, but not a hard landing, and that the first portion of the landing rollout was "fine". The airplane began oscillating left and right a few seconds after applying full braking, and the airplane became uncontrollable and exited the runway. The airplane came to a stop and both pilots exited the airplane. The airplane was equipped with a flight data recorder. The BRAKE FAIL and BRAKE RH CONTROL VALVE FAIL messages were logged 16-17 seconds after the landing transition. The wheel speeds were zero at the time both messages were recorded. The data did not reveal any braking anomalies or maintenance codes while the airplane was in motion.