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

Bellanca 17-30A accident near Albany, Ohio, April 5, 2014

On April 5, 2014 at about 10:30 pm local time, a 1972 Bellanca 17-30A, registered N8259R, was substantially damaged in an accident during approach (VFR pattern base) near Albany, Ohio (Ohio University Snyder Field). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s loss of airplane control during the approach to landing.

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

What the record shows

Date
April 5, 2014 · about 10:30 pm local time · cases in 2014
Place
Albany, Ohio · Ohio University Snyder Field · cases near this airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Bellanca 17-30A, built 1972 · all 17-30As on the register
Registration
N8259R · no longer on the register · serial 30475
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot was using flight following services from air traffic control during the return leg of the cross-country flight, and, about 12 miles from the destination, the pilot reported to the approach controller that he had the airport in sight. Two witnesses reported seeing the airplane traveling toward the airport and then "nose dive" to a nearby quarry's property. One of the witnesses indicated that the back of the airplane hit a tree and that the airplane subsequently impacted the ground. The other witness said that the airplane engine was making a "buzzing" noise after the airplane crashed but that he did not hear anything before the crash. The main airplane wreckage came to rest inverted near a tree line about 2,300 feet northwest of the runway's displaced threshold. Trees in the tree line exhibited broken and cut branches along about a 300-foot-long path, and the airplane was found fragmented and signs of a ground fire were observed along the path. The crankshaft propeller flange had separated from the crankshaft. A family member who flew with the pilot during an earlier leg of the cross-country flight reported that the airplane's engine seemed harder to start than usual and that, during cruise, a distinct engine vibration occurred when the fuel mixture was leaned. However, examinations revealed no preimpact airframe or engine anomalies that would have precluded normal operation. Further, during an engine test run conducted after engine items that had sustained impact damage were replaced and a centering pilot shaft and the propeller flange were welded to the engine's crankshaft separation point, the engine ran normally, and no preimpact engine anomalies were detected. On the basis of the evidence, it is likely that the pilot lost control of the airplane during the approach to landing.

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. Loss of control in flight during approach (VFR pattern base) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Not attained/maintained

Pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 25,075 hours in all
  • Last flight review: June 11, 2013
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 3,891 hours
  • Last inspection: annual inspection, October 1, 2013; 23 hours since
  • Maximum gross weight: 3,200 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Cont Motor IO 520 DCK (piston); 3,770 hours total
  • Fire on the ground

The flight

  • Departed from: TRI Bristol/Johnson/Kingsport TN at 9:15 pm
  • Destination: UNI Albany OH
  • Flight plan: none
  • Runway 07, 5,600 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 340° at 4 knots
  • Visibility: 10 statute miles
  • Sky: scat at 5,000 ft
  • Temperature: 48°F (9°C), dew point 27°F (-3°C)
  • Altimeter: 30.14 inHg
  • Observation at 10:35 pm from UNI, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

33 documents, released by the NTSB on October 1, 2014. 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.

#DocumentWhat it is
1 Release of Wreckage PDF, 1 page View Download
2 Evidence Control Forms PDF, 2 pages View Download
3 Witness Statements PDF, 4 pages View Download
4 Pilots 72-HOUR History Supplied by Family Member PDF, 2 pages View Download
5 Communication Summary - Fire Chief Waren Keirns PDF, 1 page View Download
6 Communication Summary - Leslie Nicholson PDF, 1 page View Download
7 Communication Summary - Becky Sheets PDF, 1 page View Download
8 Pilot Logbook Excerpt PDF, 3 pages View Download
9 Maintenance Logbook Excerpts PDF, 2 pages View Download
10 GPS Factual Report PDF, 2 pages View Download
11 Party Forms PDF, 2 pages View Download
12 Toxicology Report PDF, 2 pages View Download
13 Photo 1 - Front of Airplane PDF, 1 page View Download
14 Photo 2 - Right Side of Airplane PDF, 1 page View Download
15 Photo 3 - Ground Scar and Path of Broken Branches PDF, 1 page View Download
16 Photo 4 - Aerial View of Accident Location PDF, 1 page View Download
17 Photo 5 - Tree Branch with Dark Paint Transfer PDF, 1 page View Download
18 Photo 6 - Tree Trunk with Charred Bark PDF, 1 page View Download
19 Photo 7 - Separated Tree Branch PDF, 1 page View Download
20 Photo 8 - Tree Branches Not Consistent with Recent Separations PDF, 1 page View Download
21 Photo 9 - Shattered Glass Near Left Wing Tip PDF, 1 page View Download
22 Photo 10 - Auxilliary and Fuselage Fuel Tank Selector PDF, 1 page View Download
23 Photo 11 - Fuel Tank Selector PDF, 1 page View Download
24 Photo 12 - Flap Jack Screw Extension PDF, 1 page View Download
25 Photo 13 - Engine Driven Fuel Pump Drive Gear and Its Shear Shaft PDF, 1 page View Download
26 Photo 14 - Propeller Flange PDF, 1 page View Download
27 Photo 15 - Sparkplugs PDF, 1 page View Download
28 Photo 16 - Fluid Draining from the Fuel Hose Between Firewall and Engine Driven Fuel Pump PDF, 1 page View Download
29 Photo 17 - Fuel Manifold PDF, 1 page View Download
30 Photo 18 - Separated Propeller Flange Welded to Crankshaft PDF, 1 page View Download
31 Photo 19 - Engine on Test Stand with Test Club PDF, 1 page View Download
32 Photo 20 - Swaged Cable Connection on Governor Control Cable PDF, 1 page View Download
33 Photo 21 - Swaged Cable Connections on Mixture and Throttle Control Cables PDF, 1 page View Download

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

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/CEN14FA185.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.