Supernal LLC SUP83-1 accident near California City, California, August 3, 2023
On August 3, 2023 at about 3:03 pm local time, a 2022 Supernal LLC SUP83-1 (powered-lift aircraft), registered N183TD, was substantially damaged in an accident during maneuvering near California City, California. It was a flight test under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A loss of control in flight due to a loss of electrical power to one of the lift-motors.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 3, 2023 · about 3:03 pm local time
- Place
- California City, California · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Supernal LLC SUP83-1, built 2022
- Registration
- N183TD · no longer on the register · serial 001
- Damage
- Substantial damage
- Flight
- Flight test · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
On August 3, 2023, at 0803 Pacific daylight time (PDT), a Supernal, LLC., SUP83-1 unmanned aircraft system, received substantial damage during a developmental test flight at the manufacturer’s test site. There were no injuries. The aircraft was operating with a FAA Certificate of Waiver or Authorization (COA) 2022-WSA-213-SAC-REV1, under Exemption No. 20050 Regulatory Docket No. FAA-2022-1757. According to the operator/manufacturer the accident occurred during the 3rd flight of the day. The test objective was to observe the behavior of the autonomous RTL (Return to Land) function, triggered by a “low” High Voltage (HV) battery warning. Prior to the test, the voltage warning limits were adjusted in the ground control station (GCS) to trigger at a higher voltage than the previous flights. The previous test, i.e., the second flight of the day, had tested similar autonomous flight behavior using a hand-held transmitter (HHTX) lost link test point, and the aircraft turned towards home, and performed a “return to landing (RTL)” flight, as had been planned and expected. On the third flight, at 7:59 AM local time the aircraft lifted off and the pilot translated the vehicle forward from the home position to the west corner of the landing pad and climbed the aircraft to 50 feet. Oscillations were noted, which the pilot said was because of wind, so he lowered aircraft to about 20-30 feet above ground level (AGL) to try and escape the turbulence. Upon reducing the aircraft’s altitude, the oscillations were reduced, but they were not completely gone. With the extra battery power that remained before the low voltage alarm triggered, the pilot maneuvered the aircraft to the east and turned the left wing into the wind to see if it would further reduce the oscillations, but the maneuver had little effect. Then the pilot maneuvered the aircraft on the east side of the pilot’s station and placed it in a hover in front of the GoPro camera that was recording the flight, about 20 feet AGL, to await the reduction in battery voltage. It took less than one minute for the low battery warning to trigger the RTL command, which the Ground Control Station Operator (GCSO) recognized and announced. At this point, the Flight Control Computer (FCC) took over control of the aircraft from the pilot’s HHTX and initiated autonomous flight. A few seconds later, the aircraft yawed left to point its nose towards the landing point with its tail pointing to the GoPro camera. Small oscillations were still noticeable, but the aircraft was in full control of itself, without any issues being noted. After the aircraft turned left, there was a brief hover-hold before the expected aircraft translation was to occur, however at that point the aircraft became inverted at what appeared to be a maximum pitch rate. During the unexpected maneuver the wings stayed fairly level. As the nose pitched up, the aircraft translated backwards and looped over the top of the GoPro. As it was performing the loop it became inverted above the GoPro, and then continued the loop and rapidly descended until it landed directly behind the GoPro. When it landed it bounced and continued another “half-flip” and ended up laying on the ground, inverted. Due to the low altitude and rapid loop/backflip maneuver, the duration of time from problem-initiation and recognition to actual ground-contact was too short for the pilot to react and attempt to recover control. After the aircraft impacted the ground, the pilot immediately activated the controls on the HHTX to disarm and deactivate the aircraft. During the maneuver, the aircraft’s trajectory was not close to any personnel, and no one was injured. Upon impact with the ground the landing gear separated and the fuselage was fractured at multiple points. Most notably the canopy broke, and interior avionics tray dislodged, throwing the avionics battery clear of aircraft, through the opening created by the broken canopy. The right lift motor forward pylon also separated from the fuselage. Postcrash examination and data review revealed that the accident was caused by the failure of a single lift-motor, which led to a loss of control. The motor failure was likely due to a soldering defect that led to the overheating and melting of a wire-solder joint, which led to a subsequent loss of electrical power to the motor. The accident aircraft, a SUP83-1 unmanned aircraft system, serial number 001, manufactured in 2022, registered to TVPX Aircraft Solutions Inc., and operated by Supernal LLC., was a 25% subscale unmanned test aircraft used for the purpose of researching distributed electric propulsion technologies. The aircraft was configured with six propulsors driven by electric motors that are powered by lithium-ion battery packs. The aircraft can perform vertical take-offs and landings and can be reconfigured to horizontal flight with lift being generated by the wings. It is controlled from a handheld transmitter by a remote pilot and monitored by a PC laptop ground station linked to the aircraft via telemetry radios inside a mobile trailer at the test site. At the time of the accident the aircraft had accumulated about 2.6 hours of flight time on the airframe. The pilot was an FAA certified private pilot who reported having 112 hours total flight experience and had no experience with the accident aircraft. The test flight was also supported by a visual observer who was stationed near the pilot and one team member who was located inside the ground control station. The pilot, visual observer, and ground control station operator used hands free headsets to maintain communication during the entire event, and they reported no communication issues among themselves. The test site for this aircraft is a privately owned area near California City, California, within the Hyundai Motor Group’s California Proving Grounds automotive testing facility. Surrounded by unimproved desert, the test area has a large, paved ramp area from which operations are conducted along with the supporting infrastructure appropriate for the operations of the site. Per its COA, SUP 83-1 was permitted to fly within its test area up to 400 feet AGL, remaining clear of both Mojave Air and Space Port/Rutan Field’s (MHV) controlled airspace, and the Edwards Air Force Base (AFB) Restricted Area 2515. Weather was not a factor in the accident. At the time of the accident, there were clear skies, the visibility was about 10 NM, the temperature was 24 degrees C, and the winds were variable at about 8 knots.
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
- Loss of control in flight during maneuvering defining event
The NTSB's findings
- Aircraft › Aircraft propeller/rotor › Propeller system › Propeller/propulsor wiring › Malfunction
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 112 hours in all; 0 in this make and model; 2 in the last 30 days; 70 as pilot in command
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: none
- Injury: no injuries
The aircraft
- Airframe total time: 2.6 hours
- Last inspection: condition inspection, August 3, 2023
- Maximum gross weight: 150 lb
- Seats: 0
- Landing gear: fixed
- Engine 1: T-Motor U13IIKV130 (electric); 2 hours total
- Engine 5: T-Motor U13II KV130 (electric); 1 hours total
- Engine 6: T-Motor U13II KV130 (electric); 2 hours total
- Engine 7: T-Motor U13IIKV130 (electric); 2 hours total
- Engine 8: T-Motor U13IIKV130 (electric); 2 hours total
- Engine 9: T-Motor U13IIKV130 (electric); 2 hours total
- Operator: Supernal, LLC
The flight
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 238° at 8 knots
- Visibility: 11 statute miles
- Sky: clear
- Temperature: 75°F (24°C), dew point 39°F (4°C)
- Altimeter: 30.05 inHg
- Observation at 8:00 am from KMHV, 6 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
2 documents, released by the NTSB on March 21, 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Reports from Parties to the Investigation | PDF, 2 pages | View Download |
| 2 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 11 pages | View Download |
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.
