WPR24LA281 · Evektor-Aerotechnik A S HARMONY LSA
Evektor-Aerotechnik A S HARMONY LSA · Accident: fuel starvation during initial climb
From an unrecorded airport to Gallup Municipal Airport (GUP)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR24LA281
- 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
Evektor-Aerotechnik A S HARMONY LSA
- Aircraft type
- Evektor HARMONY
- 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
- N272JT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Gallup Municipal Airport (GUP), Gallup, NM
- Aircraft age
- About 1 year (built 2023)
- 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
- Substantial
Cause areas
- Aircraft › Aircraft systems
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Shortly after takeoff, the airplane was about 200-300 ft above ground level, the engine lost power. The pilot landed the airplane back on the runway near the departure end and subsequently overran the end of the runway. Shortly thereafter, the right wing struck a shrub and the left main landing gear struck a large rock and sheared off, resulting in substantial damage. The airplane came to rest upright about 600 ft from the departure end of the runway. Postaccident examination revealed no evidence of failures or malfunctions that would have resulted in the loss of engine power. About 6 gallons of fuel were drained from the right tank and about 2 gallons of fuel were drained from the left tank. According to the airplane Pilot’s Operating Handbook, each fuel tank contained 0.25 gallons of unusable fuel. During the examination, with the left wing slightly lowered, fuel from the left tank was unable to be pumped to the engine, even though the level was above the unusable fuel amount. However, the pilot stated that he had the right fuel tank selected, and fuel continuity to the engine was established with it during postaccident examination; therefore, the low fuel level in the left tank should not have been a factor. According to the airframe manufacturer, the airplane’s unusable fuel was tested in accordance with Light Sport Aircraft (LSA) category and European Union Aviation Safety Agency (EASA) standards. Downloaded engine control unit data revealed that, shortly after takeoff, a rapid decrease in the fuel flow and fuel injection mass for each cylinder preceded the decrease of the other engine parameters until shutdown, consistent with fuel starvation. Furthermore, about 5 minutes after the accident, the pilot restarted the engine and ran it for about 30 seconds. Running the engine successfully after the accident likely compromised evidence of what caused the engine failure.
Probable cause
A total loss of engine power due to fuel starvation for reasons that could not be determined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR24LA281
- Event ID
- 20240820194956
- Case number
- WPR24LA281
- 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, 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: adfaba9abaa37d2cae29e70f7d0da2376faaff36f9f0e22769156f80de99f568; retrieved 2026-09-16T19:11:01.790Z.