The U.S. aircraft register, updated daily
Accidents · NTSB GAA17CA239 · Final report

Beech C23 accident near Fallon, Nevada, April 19, 2017

On April 19, 2017 at about 6:30 pm local time, a 1975 Beech C23, registered N786KS, was substantially damaged in an accident during takeoff (rejected takeoff) near Fallon, Nevada (Darrow Field). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
April 19, 2017 · about 6:30 pm local time
Place
Fallon, Nevada · Darrow Field · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Beech C23 NO SERIES, built 1975 · all C23s on the register
Registration
N786KS · no longer on the register · serial M-1676
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Preflight or dispatch event during prior to flight
  2. Loss of control on ground during takeoff (rejected takeoff) defining event
  3. Collision with terrain or object (not controlled flight into terrain) during takeoff (rejected takeoff)
  4. Runway excursion during takeoff (rejected takeoff)

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Personnel issues › Task performance › Planning/preparation › Performance calculations › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
  • Environmental issues › Physical environment › Runway/land/takeoff/taxi surface › (general) › Decision related to condition
  • Environmental issues › Physical environment › Runway/land/takeoff/taxi surface › (general) › Accuracy of related info
  • Environmental issues › Physical environment › Object/animal/substance › Fence/fence post › Contributed to outcome

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 91 hours in all; 91 in this make and model; 19 in the last 90 days; 7 in the last 30 days; 70 as pilot in command
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 6,505 hours
  • Last inspection: 100-hour inspection, July 1, 2016
  • Maximum gross weight: 2,450 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-360-A4K (piston); 6,505 hours total

The flight

  • Departed from: FLX Fallon NV at 5:05 pm
  • Destination: 1NV1 Fallon NV
  • Flight plan: none
  • Runway 16, 2,483 ft by 25 ft

Weather at the time

  • Light: daylight
  • Wind: from 150° at 9 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 8,000 ft
  • Temperature: 59°F (15°C), dew point 37°F (3°C)
  • Altimeter: 30.15 inHg
  • Observation at 6:56 pm from KNFL, 6 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

6 documents, released by the NTSB on June 22, 2017. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.