FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA21LA173 · Piper PA-23-250

5 Apr 2021 · Springfield, TN, United States

Highland Rim Aviation Piper PA-23-250 · Accident: fuel related during takeoff

Report a problem

Event

NTSB case
ERA21LA173
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
Event fatalities
Unknown
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

Piper PA-23-250

Aircraft type
Piper PA-23
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
N5018Y
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 58 years (built 1963)
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
Takeoff
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 related
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

  • Personnel issues › Task performance

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

NTSB narrative

The instructor and pilot receiving instruction were conducting multiengine flight training. During takeoff following a simulated engine failure on the runway, the left engine lost power, and the instructor stated that the left propeller would not feather. The airplane descended into terrain past the end of the runway. Witnesses stated that their attention was drawn to the airplane due to its “unusual” sound that was inconsistent with takeoff power. One witness said he could not discern if one engine or both engines were making “continuous sputtering/backfiring” sounds. The airplane climbed to about 100 ft above ground level and the landing gear remained extended until the departure end of the runway. Shortly thereafter, the airplane entered a shallow turn to the left until it disappeared behind a tree line.

Automatic dependent surveillance-broadcast (ADS-B) data revealed that the airplane achieved a groundspeed of 86 knots about midfield and slowed once off the ground. About 200 ft agl, the track depicted a descending, decelerating turn to the left. The radius of the turn tightened until the last target was recorded in the vicinity of the accident site, about ground level, at 59 knots groundspeed. Based on the estimated point at which the takeoff started, the airplane was over 1,400 ft into the takeoff roll when it became airborne. Performance information in the Owner’s Handbook for the airplane indicated a 750-ft takeoff distance. Although ample runway remained on which to safely reject the takeoff, the instructor allowed the pilot to continue the takeoff despite the excessive distance required to become airborne and the loss of left engine power. Pilots who had flown the accident airplane during the week before the accident described the left engine either stopping or running roughly with the fuel selector in the left inboard tank position. When the fuel selector was moved to the left outboard tank position, the engine could be restarted, or smooth, continuous operation would be restored. Each said that these power-loss events were reported to maintenance for correction. Three days before the accident, a flight instructor could not start or sustain power on the left engine with the inboard tank selected but started and ran the engine continuously on the outboard tank. He then demonstrated the discrepancy to company maintenance personnel before he rejected the airplane for his scheduled flight. Examination of the wreckage revealed a 12-inch length of duct tape, employed as a “gasket” to seal the loosely fitted left inboard fuel cap, unsecured inside the fuel tank, where it likely blocked the fuel supply port on the accident flight, as it had intermittently during the days before the accident. Examination and testing of the airframe, engines, and components revealed no evidence of any other preimpact anomaly that would have prevented continuous engine power; however, these examinations and a records review revealed numerous examples of maintenance work that was incomplete, inadequate (including the use of duct tape on the left inboard fuel cap), or not performed; the recommended engine and propeller overhauls were more than a decade overdue.

Probable cause

The flight instructor’s failure to abort the takeoff following a loss of left engine power due to fuel starvation. Also causal was the inadequate maintenance of the left fuel cap by unknown maintenance personnel, which resulted in a blockage of the fuel supply from the left-wing tank. Contributing to the accident was the instructor’s failure to maintain airspeed above the one-engine-inoperative minimum controllable airspeed after deciding to continue the takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA21LA173
Event ID
20210405102871
Case number
ERA21LA173
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, cause areas. 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: d4db82cd3b70f3c9effed5b7a77327a670e82e7cbc2953f9eac769446c2ed4cb; retrieved 2026-09-16T13:55:30.842Z.