FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA18FA005 · Bryant C Crosby BC ULTRA PUP

5 Oct 2017 · Bardstown, KY, United States

Bryant C Crosby BC ULTRA PUP · Accident: aerodynamic stall/spin on approach

From Samuels Field (BRY) to Samuels Field (BRY)

Report a problem

Event

NTSB case
ERA18FA005
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
1 · 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

Bryant C Crosby BC ULTRA PUP

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
N484HC
Operator
Unknown
Onboard fatalities
Unknown
Route
From Samuels Field (BRY), Bardstown, KYTo Samuels Field (BRY), Bardstown, KY
Aircraft age
About 4 years (built 2013)
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 go-around
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
Aerodynamic stall/spin
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
  • Personnel issues › Action/decision
  • Personnel issues › Experience/knowledge
  • Personnel issues › Task performance

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

NTSB narrative

A pilot-rated witness saw the airplane in the traffic pattern conducting what seemed to be a normal approach to landing. The witness stated that, during the landing flare, the pilot appeared to be "over controlling the plane" and that he subsequently performed a go-around without touching down. The airplane remained in the traffic pattern for the second approach. The witness then saw the airplane about two-thirds of the way down the runway, and it was not climbing at the same rate as it had during the previous two departures. As the airplane passed the departure end of the runway, the right wing dropped, and the airplane descended straight down below a stand of trees and then reappeared with the nose slightly up and pointing generally to the left of the runway centerline. It then disappeared behind the trees again and crashed. The witness reported that the engine sounded normal during the entire flight. This evidence indicates that the pilot lost airplane control and that the airplane likely entered an aerodynamic stall during the attempted go-around.

Examination of the wreckage revealed no evidence of any preaccident mechanical malfunctions or anomalies that would have precluded normal operation.

The pilot purchased the airplane about 5 months before the accident, and the accident flight was his first flight in the airplane. He had not recorded a flight review in about 25 years.

About 3 years before the accident, the pilot applied for a Federal Aviation Administration medical certificate, which was denied for multiple physical and mental health reasons, and the pilot did not appeal the denial. Thus, the pilot was ineligible to fly any aircraft. According to personal medical records, the pilot had obsessive compulsive disorder, depression/anxiety (not further specified), paroxysmal atrial fibrillation/supraventricular tachycardia, and chronic obstructive pulmonary disease. He had also had a hernia and had undergone back surgery. Although individually controlled, the pilot's numerous physical health issues in the year preceding the accident likely exacerbated his underlying psychiatric illnesses.

Postaccident toxicology testing identified sertraline, which is used to treat depression, and its metabolite desmethylsertraline in blood and liver; however, this medication does not generally affect judgment or decision-making, thus it is unlikely that the effects from the pilot's medications contributed to the accident. However, it is likely that his depression and anxiety affected his judgment and contributed to his improper decision to initiate the flight in an airplane he had never flown, especially given he had not flown for several years and was not eligible to fly any aircraft; this poor decision-making ultimately led to the accident.

Probable cause

The pilot's improper decision to initiate a flight in an airplane he had never flown and with no currency in any airplane nor a medical certificate, which resulted in his loss of airplane control. Contributing to the accident was the pilot's psychiatric disease, which likely affected his decision-making and judgment.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA18FA005
Event ID
20171005X94549
Case number
ERA18FA005
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: e9709e4285f1e5e468e1dea5806275c1364c723ad21fb6398b1e80b08c6f0123; retrieved 2026-09-15T06:19:52.990Z.