FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA19FA155 · Bellanca 1730

22 Apr 2019 · Henderson, KY, United States

Bellanca 1730 · Accident: fuel exhaustion on approach

From Mid-Carolina Regional Airport (RUQ) to an unrecorded destination

Report a problem

Event

NTSB case
ERA19FA155
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
0
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 1730

Aircraft type
Bellanca 1730
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
N9693E
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mid-Carolina Regional Airport (RUQ), Salisbury, NCTo not recorded
Aircraft age
About 43 years (built 1976)
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
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
Fuel exhaustion
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
  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Task performance

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

NTSB narrative

The student pilot and passenger had taken the airplane without permission from the owner on a night cross-country flight with an unknown destination. About 4 hours after departure, the airplane flew an approach to a closed airport but likely did not land. The airplane then climbed and flew about 10 miles away from the airport before returning; the last radar data indicated an altitude of about 700 ft above the ground about 1/2 mile south of the runway consistent with aa left downwind leg in the airport traffic pattern. The airplane impacted terrain in a near vertical nose-down attitude near midfield about 200 ft south of the runway. There were no ground scars leading up to the main wreckage, which was consistent with little or no forward airspeed and a loss of control. About 3-4 gallons of fuel were recovered from the right wing; however, a placard on the filler neck indicated 4 gallons of fuel were unusable. A trace amount of fuel was found in the left wing, and no fuel was found in the fuselage auxiliary tank. A post-accident examination of the airframe and engine revealed no preimpact anomalies that would have precluded normal operation; however, a lack of rotational scoring on the propeller blades was noted. It is likely that the airplane's engine lost power due to fuel exhaustion as the airplane was in the airport traffic pattern the second time, and the pilot failed to maintain sufficient airspeed, which resulted in an aerodynamic stall and impact with terrain.

The student pilot had logged 24 hours of total flight experience, 23 of which was dual instruction. He had logged 3 hours of dual cross-country experience, of which 1.4 hours were in the accident airplane earlier on the day of the accident. He had no other experience in an airplane of the same make/model. He had logged a total of 4 hours at night in a different airplane make/model. Thus, it is likely that the pilot had little experience in fuel planning and management, night operations, and emergency procedures in the accident airplane make/model to help him deal with the loss of engine power on approach to the airport at night.

Toxicology performed on the student pilot was positive for methamphetamine, cocaine, and their metabolites. Although the test results could not be directly correlated to the exact time of use, the amount, or the residual effects at the time of the accident, the results suggest use within hours of the accident. It is likely that impairment from the student pilot's use of cocaine and methamphetamine contributed to his unsafe decision-making to embark on the night cross- county flight in an unfamiliar and complex airplane, with a passenger, on the night of the accident.

Probable cause

The student pilot's failure to maintain proper airspeed, which resulted in the exceedance of the airplane's critical angle of attack at a low altitude, in the airport traffic pattern, following a total loss of engine power due to fuel exhaustion. Contributing to the accident was the student pilot's decision to attempt the night cross-country flight, his lack of overall and specific operational experience, and his likely impairment from use of methamphetamine and cocaine.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA19FA155
Event ID
20190424X95940
Case number
ERA19FA155
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2019-04-23.
  • API snapshot SHA-256: fc4d53523be62108cbd99a21a3ad20cf399c56b21d33291ff77ccb2cdbdad9d6; retrieved 2026-09-15T06:57:00.561Z.