The U.S. aircraft register, updated daily
Accidents · NTSB ERA24LA099 · Final report

Swissdrones Operating AG SDO 50 V2 accident near Antioch, Georgia, January 18, 2024

On January 18, 2024 at about 4:23 pm local time, a 2018 Swissdrones Operating AG SDO 50 V2 (helicopter), registered N780PA, was substantially damaged in an accident during maneuvering near Antioch, Georgia. It was an instructional flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
January 18, 2024 · about 4:23 pm local time
Place
Antioch, Georgia · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Swissdrones Operating AG SDO 50 V2, built 2018
Registration
N780PA · registry record · serial 551024
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Autorotation Engine shutdown
  2. Autorotation Hard landing
  3. Fuel related during maneuvering defining event

The NTSB's findings

  • Aircraft › Aircraft systems › Fuel system › (general) › Unknown/Not determined
  • Personnel issues › Experience/knowledge › Training › Training with equipment › Student/instructed pilot
  • Organizational issues › Development › Manufacture/production › Document/info production › Manufacturer

Pilot

  • Certificate: private, remote
  • Ratings: multi-engine land; multi-engine sea; single-engine land; rotorcraft: unmanned (suas)
  • Flight time: 221 hours in all; 4 in this make and model; 11 in the last 90 days; 3 in the last 30 days; 221 as pilot in command; 0 on instruments
  • Last flight review: January 6, 2023
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: none
  • Injury: no injuries

Other crew

  • Certificate: commercial pilot, remote
  • Ratings: single-engine land; instrument: airplane; rotorcraft: unmanned (suas)
  • Flight time: 163 hours in all; 11 in this make and model; 3 in the last 90 days; 0 in the last 30 days; 163 as pilot in command; 21 on instruments
  • Last flight review: January 6, 2023
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: none
  • Injury: no injuries

The aircraft

  • Airframe total time: 38.4 hours
  • Last inspection: condition inspection, January 3, 2024; 3.5 hours since
  • Maximum gross weight: 191 lb
  • Seats: 0
  • Landing gear: fixed
  • Engine: Jakadofsky Pro X (turboshaft); 34 hours total
  • Operator: Phoenix Air Unmanned LLC

The flight

  • Departed from: Antioch GA at 4:11 pm
  • Flight plan: none
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 170° at 5 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 37°F (3°C), dew point 12°F (-11°C)
  • Altimeter: 30.20 inHg
  • Observation at 11:15 am from PUJ, 11 miles away

Weather report (METAR): KPUJ 181615Z AUTO 17005KT 10SM CLR 03/M11 A3020 RMK AO2=

Injuries

FatalSeriousMinorNone
Flight crew2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

16 documents, released by the NTSB on July 16, 2025. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.