FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA15FA221 · BR Legend LLC TURBINE LEGEND

23 May 2015 · West Columbia, SC, United States

BR Legend LLC TURBINE LEGEND · Accident: fuel starvation during initial climb

From Columbia Metropolitan Airport (CAE) to Asheville Regional Airport (AVL)

Report a problem

Event

NTSB case
ERA15FA221
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

BR Legend LLC TURBINE LEGEND

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
N42BR
Operator
Unknown
Onboard fatalities
Unknown
Route
From Columbia Metropolitan Airport (CAE), West Columbia, SCTo Asheville Regional Airport (AVL), Asheville, NC
Aircraft age
About 12 years (built 2003)
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
Initial climb
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 starvation
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft propeller/rotor
  • Aircraft › Aircraft systems
  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The commercial pilot departed on a cross-country flight in the experimental, amateur-built, turboprop airplane. About 3 minutes after takeoff, the pilot initiated a return to the departure airport. About 6.8 nautical miles (nm) from the runway, at an altitude of about 6,500 ft mean sea level, the pilot declared an emergency, stating that he had "lost" the engine. Shortly thereafter, he informed air traffic control that the airplane had experienced a loss of fuel pressure. Witnesses saw the airplane collide with a tree and subsequently impact a pond about 1.2 nm from the runway. They reported no engine sound.

Examination of the airplane revealed no evidence of preimpact failures or malfunctions of the flight controls that would have precluded normal operation. The landing gear and flaps were found retracted. There was no evidence of preimpact failure or malfunction of the engine core. The engine-driven fuel pump showed signs of internal cavitation, while the auxiliary fuel pump, which provided fuel under pressure to the engine-driven fuel pump, flowed nearly 48% less than specified by the manufacturer, and had an inconsistent/intermittent laboring sound during testing. Disassembly revealed an improperly-installed fitting, which resulted in the decreased fuel flow rate, a loss of fuel pressure, and a subsequent engine flame-out. Inspection also revealed that a component of the fuel pump had been replaced after manufacture, but there was no record of this maintenance in the airplane's logbooks.

While it was not known if the pilot attempted to perform an air restart of the engine, a worn ignitor box and ignitor plug may have precluded a successful restart of the engine.

Although the pilot descended the airplane at its published best glide airspeed in his attempt to return to the airport, because the airplane was not equipped with an electrically-operated feathering pump, the propeller blade angle remained where it was set when the engine flame-out occurred, which was likely flat pitch. The flat pitch of the propeller blades significantly decreased the airplane's engine-out glide ratio. Had the pilot promptly feathered the propeller blades to reduce drag following engine flame-out, or had the airplane been equipped with a feathering pump, it is likely the airplane would have been able to reach the intended runway and land uneventfully.

Although an enlarged heart was noted during the autopsy and toxicological testing detected quinine, given that the pilot was actively controlling the airplane just before the accident, there is no evidence that a medical condition or use of quinine contributed to the pilot's inability to fly the airplane.

Probable cause

An engine flame-out due to fuel starvation as the result of an improperly-installed auxiliary fuel pump fitting, and the pilot's failure to promptly feather the propeller following the engine-flame out, which resulted in decreased glide capability and impact with terrain. Contributing to the accident was the pilot's operation of the airplane with no emergency electric propeller feathering system.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA15FA221
Event ID
20150523X02458
Case number
ERA15FA221
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, coordinates. 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: 09250f3a0201a8f6bed8ab9ec52c6a4f304c81bac7f0bb3ad7b97c143449d68a; retrieved 2026-09-14T19:08:46.352Z.