FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN17FA164 · Bellanca 17 31ATC

24 Apr 2017 · Boonville, MO, United States

Bellanca 17 31ATC · Accident on approach

From Jesse Viertel Memorial Airport (VER) to Jesse Viertel Memorial Airport (VER)

Report a problem

Event

NTSB case
CEN17FA164
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Bellanca 17 31ATC

Aircraft type
Bellanca 17
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N787TV
Operator
Unknown
Onboard fatalities
Unknown
Route
From Jesse Viertel Memorial Airport (VER), Boonville, MOTo Jesse Viertel Memorial Airport (VER), Boonville, MO
Aircraft age
About 44 years (built 1973)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR pattern final
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Miscellaneous/other
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Physical environment
  • Personnel issues › Physical

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The commercial rated pilot was landing the airplane at the end of a personal local flight. The airport manager saw the airplane very low on final approach for runway 18. As the airplane continued toward the airport, it collided with power lines about 0.5 mile north of the runway's approach end. Weather conditions at the time of the accident included a clear sky with no obstructions to visibility. Examination of the airframe and engine did not reveal any anomalies that would have contributed to the accident. The pilot was familiar with the airport and was likely aware of the location of the power lines, which were well below a normal glideslope to the runway.

The pilot did not hold a medical certificate. An autopsy of the pilot revealed coronary artery disease and significant brain pathology. It is unlikely that the pilot's coronary artery disease contributed to the accident as it would not have impaired the pilot's judgment, vision, or decision-making. The pilot had scarring from a previous brain injury and severe damage to his left optic nerve to the extent that he was nearly blind in that eye. Given that the pilot failed to maintain proper altitude while operating in visual conditions and struck a potentially visible hazard, it is likely that his vision deficiency contributed to the accident.

Toxicology test results indicated that the pilot had used multiple psychoactive drugs before the accident, including cocaine, methamphetamine, clonazepam, and diphenhydramine. In addition to their psychoactive effects, these drugs are potent vasoconstrictors and can cause small arteries to spasm, cutting off blood flow to portions of vital organs. Although the neuropathologist who examined the pilot's brain believed the degree of cerebral hypoxic/ischemic damage he identified would take several hours to develop, the pilot was deceased by the time first responders arrived about 10 minutes after the witnessed crash. Therefore, this hypoxic/ischemic damage had to have begun before the accident and was likely caused by the pilot's misuse of cocaine and methamphetamine. This evolving brain ischemia may have played a role in the circumstances of the accident, but without specific information regarding the pilot's symptoms, its exact role cannot be determined. Although the pilot's stage of intoxication with methamphetamine or cocaine at the time of the accident is unknown, it is very likely that he was impaired by the combined effects of these drugs.

Probable cause

The pilot's impairment, due to his use of a combination of psychoactive drugs and a vision deficiency in his left eye, which resulted in a failure to maintain adequate altitude during final approach to landing and subsequent collision with power lines.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN17FA164
Event ID
20170424X60355
Case number
CEN17FA164
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 6fab1b65311368db08a44a5b071f2718d1bd4304b46b27ac27fd937a4b24828b; retrieved 2026-09-15T06:01:32.490Z.