ERA24LA099 · Swissdrones Operating AG SDO 50 V2
Phoenix Air Unmanned Swissdrones Operating AG SDO 50 V2 · Accident: fuel related while maneuvering
From Antioch, GA to an unrecorded destination
Event
- NTSB case
- ERA24LA099
- 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
Swissdrones Operating AG SDO 50 V2
- Aircraft type
- Swissdrones Operating SDO-50
- Category
- Helicopter
- 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
- N780PA
- Operator
- Phoenix Air Unmanned
- Onboard fatalities
- Unknown
- Route
- From Antioch, GATo not recorded
- Aircraft age
- About 6 years (built 2018)
- 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
- Maneuvering
- 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
- Aircraft › Aircraft systems
- Organizational issues › Development
- Personnel issues › Experience/knowledge
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During an instructional flight of an intermeshing rotor-equipped unmanned aircraft system (UAS), the remote pilot-in-command (RPIC) received warnings of high fuel pump voltage, followed by warnings of max fuel pump voltage. Recorded data revealed that during these high and max fuel pump voltage spikes, the turbine engine lost power and the collective limiter would engage automatically. While attempting to have the UAS return for landing, the UAS had another partial loss of engine power, and the collective limiter was engaged again and remained engaged for the rest of the flight. The UAS touched down on the ground and then became airborne again; subsequently, the RPIC commanded an engine shutdown. After the engine shutdown, the UAS descended and contacted the ground hard on the skids; subsequently, the rotors contacted two of the vertical stabilizers, which resulted in substantial damage to the vertical stabilizers. According to the airframe manufacturer, it is possible that during a partial loss of engine power, the UAS may become airborne again after contacting the ground, as the autopilot will increase collective when the rotor rpm recovers after contacting the ground. This information was not provided to operators in the Unmanned Flight Manual at the time of the accident, so the RPIC was not aware of the need to engage the auto-land function. A postaccident examination of the airframe and the engine’s fuel system revealed no anomalies that would have precluded normal operation. Fuel samples taken just after the accident revealed no visible signs of fuel contamination or debris. An engine test run was performed using the turboshaft engine, electrically driven fuel pump, and the engine control unit (ECU). The engine operated normally at all tested RPMs and there were no anomalies that would have precluded normal operation. During the test run, a loss of fuel flow was simulated by slowly removing the fuel pickup tube from the fuel tank; the fuel pump voltage would increase to its maximum allowable voltage and the engine would lose power. Given that the main fuel tank was still full at the time of the accident, it is unlikely that the fuel pickup would have become unported during the accident flight. The fuel pump was bench-tested and then inspected. There were no anomalies observed that would have precluded normal operation. Similar cases of high/max fuel pump voltage spikes with accompanying reduction in fuel flow of similar make and model UAS aircraft were reported to the manufacturer and were found to have debris in the fuel system, which degraded the fuel pump’s performance. However, there was no debris found in the accident UAS’s fuel system during the examinations. Based on the available evidence, the partial loss of engine power was likely a result of a reduction of fuel flow to the engine. The reason for the reduction in fuel flow could not be determined.
Probable cause
A partial loss of engine power due to a reduction of fuel flow for undetermined reasons. Contributing to the accident was the UAS manufacturer’s lack of instructions for a partial loss of engine power landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA099
- Event ID
- 20240126193710
- Case number
- ERA24LA099
- 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: c32bca4fa00c5d3911467464c3c6bc0089b94ebf2b79ab49c33dfd5cb445f81e; retrieved 2026-09-16T18:27:55.831Z.