Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

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.

FAQs

NTSB Report

April 19, 2017 · Beech C23 NO Series · N786KS

Fallon, NV

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
April 19, 2017
Injury Outcomes
No injuries (2 uninjured)
Location
Fallon, NV
Aircraft
Beech C23 NO Series (1975)
Tail Number
N786KS
Injuries
None
Aircraft Damage
Substantial
NTSB Number
GAA17CA239

The pilot reported that two private airports were near each other, and he mistakenly landed at the wrong airport. He added that, once he realized his mistake, he referenced the Federal Aviation Administration (FAA) chart supplement and visual flight rules sectional chart and observed a published runway length of 2,600 ft for departure. The pilot reported that he referenced the Pilot's Operating Handbook (POH) and noted that the calculated takeoff distance was 1,350 ft. The pilot reported that, during the takeoff roll, he decided to abort the takeoff with about half of the runway remaining because the airplane had not reached the speed he expected. During the aborted takeoff, the airplane pulled to the left of the runway centerline "slightly" when the brakes were applied, and the left wing struck two fence posts along the runway. The collision with the fence posts pulled the airplane off the runway surface to the left and into a ditch and a barbed wire fence. The left wing sustained substantial damage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The FAA Aeronautical Information Services Office was asked by the National Transportation Safety Board investigator-in-charge to evaluate the published runway dimensions at the accident airport. Upon review, the FAA determined that the runway dimensions provided for the airport should have been 2,483 ft by 25 ft rather than 2,600 ft by 25 ft. The FAA submitted the revised dimensions to the National Flight Data Center for publication. According to takeoff performance calculations with the FAA Koch Chart, the airplane would have likely experienced a 60% increase to the normal takeoff distance. When factoring in this increase with the airplane's POH takeoff distance chart, the ground roll required was about 1,808 ft, and the total distance to clear a 50-ft obstacle was 3,128 ft. Numerous trees were located at the end of the runway. The distance to clear the 50-ft obstacle exceeded the published runway length and revised runway length.

NTSB Probable Cause

The pilot's inaccurate takeoff performance calculations and failure to maintain directional control during an aborted takeoff.

Full Narrative

The pilot reported that two private airports were in close proximity to one another, and he mistakenly landed at the wrong airport. He added that once he realized his mistake, he referenced the Federal Aviation Administration (FAA) chart supplement and visual flight rules (VFR) sectional chart and observed a published runway length of 2,600 ft. for departure. The pilot reported that he referenced the pilot's operating handbook (POH) and noted that the calculated takeoff distance was 1,350 ft. The pilot reported that during the takeoff roll, he decided to abort the takeoff with about half of the runway remaining, because the airplane had not reached the speed he expected. During the aborted takeoff, the airplane pulled to the left of the runway centerline "slightly" when the brakes were applied, and the left wing struck two fence posts along the runway. The collision with the fence posts pulled the airplane off the runway surface to the left and into a ditch and a barbed wire fence. The left wing sustained substantial damage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The FAA Aeronautical Information Services Office was asked by the National Transportation Safety Board investigator-in-charge to evaluate the published runway dimensions at the accident airport. Upon review, the FAA determined the runway dimensions provided for the airport should have been 2,483 ft. x 25 ft., rather than 2,600 ft. x 25 ft. The FAA submitted the revised dimensions to the National Flight Data Center for publication. According to takeoff performance calculations with the FAA Koch Chart, the airplane would have likely experienced a 60% increase to the normal takeoff distance. When factoring in this increase with the airplane's POH takeoff distance chart, the ground roll required was about 1,808 ft. and the total distance to clear a 50 ft. obstacle was 3,128 ft. Numerous trees were located at the end of the runway. The distance to clear the 50 ft. obstacle exceeded the published runway length and revised runway length.

Flight

Event TypeAccident
Event Time11:30 PDT
Nearest AirportDarrow Field (0nm SSW)
Runway16
Runway Length2483 ft
Runway Width25 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftBeech C23 NO Series
Tail NumberN786KS
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-360-A4K · Reciprocating · 180
Seats4

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 58 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind150° @ 9 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point59 / 37 C
Altimeter30.15 inHg
Observation Time18:56
Weather SourceWFAC

Appendix: Source Data