ERA24LA163 · Evektor-Aerotechnik A S HARMONY LSA
Jet Access Group Evektor-Aerotechnik A S HARMONY LSA · Accident: system/component malfunction/failure (non-power) en route
From Tampa Executive Airport (VDF) to Page Field (FMY)
Event
- NTSB case
- ERA24LA163
- 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
- 0 · 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
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
- N469JA
- Operator
- Jet Access Group
- Onboard fatalities
- Unknown
- Route
- From Tampa Executive Airport (VDF), Tampa, FLTo Page Field (FMY), Fort Myers, FL
- 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
- En route
- 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
- System/component malfunction/failure (non-power)
- 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
- Organizational issues › Development
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was on the final leg of a flight to reposition it to its home base. This was the fourth flight since the airplane had been reassembled after it was manufactured, disassembled, and shipped. The pilot reported a normal takeoff, and during the initial climb the airplane performed normally. Upon reaching 2,200 ft mean sea level (msl), the airplane lost all engine power. The pilot turned back toward the airport and attempted to restart the engine multiple times without success. At 800 ft msl, the pilot deployed the whole airplane parachute system. The airplane descended under the parachute canopy until it impacted a tree, became inverted, and impacted the ground. The impact resulted in substantial damage to the fuselage, vertical stabilizer, and both wings. A postaccident examination of the airplane revealed that the fuel line going from the electrical fuel pump outlet to the four-way distributor was disconnected at the four-way distributor and was leaking fuel. The factory-installed clamp remained attached to the disconnected fuel line and was observed to be further down the fuel line than the other fuel lines that remained attached to the four-way distributor. If the fuel line was seated properly, the clamp would have only been at the last ridge on the fitting. After examining the fuel line, the line was reinstalled onto the four-way distributor, and a new clamp was installed. An engine test run was performed, and the engine operated normally at all rpm settings except for idle, which was to be expected due to the propeller blades having been shortened to facilitate the test run. Except for the disconnected fuel line, no anomalies or mechanical failures were found with the airframe or engine that would have precluded normal operation of the engine. Given this information, it is likely that during the climb the fuel line slipped off the four-way distributor valve and starved the engine of fuel. This is consistent with, and a likely result of, the fuel line and clamp being installed too low on the four-way distributor valve fitting, which resulted in the line being able to slide off the fitting during engine operation. There were no logbook entries documenting that the fuel line or the four-way distributor valve had been adjusted or reinstalled since the airplane was manufactured; however, there were minor differences between the condition of the fuel system as found after the accident vs. the condition of the system as documented by pre-delivery photographs taken by the airframe manufacturer. Given the lack of maintenance documentation, it could not be determined when any maintenance, modification, or other alterations of the fuel system could have occurred between when the airplane was manufactured and the accident flight.
Probable cause
The improper installation of the fuel line that connected the fuel pump to the four-way distributor, which resulted in fuel starvation when the line became disconnected.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA163
- Event ID
- 20240405194035
- Case number
- ERA24LA163
- 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: c109ca9a55b3ebb00cbdada25c46e11cd30e00d4d6514569486c52e62f811a5b; retrieved 2026-09-16T18:38:33.885Z.