Pilot Debrief

AIR VEV INC AIR ZERO2 near Indiantown, FL — 2025-10-23

Final reportDCA26FA019
Sign in to save
Date
2025-10-23
Location
Indiantown, FL, USA
Airport
X58
Aircraft
AIR VEV INC AIR ZERO2
Registration
N514AX
Category
PLFT
Highest injury
None
Fatalities
0

Probable cause

A cascading shutoff of multiple aft motors due to a sudden increase in motor loads during maneuvering, resulting in a loss of control.

NTSB narrative

On October 23, 2025, about 1211 Eastern Daylight Time (EDT), an experimental Air VEV, Inc. Zero 2 advanced air mobility (AAM) electric vertical takeoff and landing (eVTOL) aircraft, N514AX, lost control while maneuvering to land at Indiantown Airport (X58), Indiantown, Florida. At the time of the accident, the aircraft was operated by a remote pilot as an unmanned aircraft system (UAS) under the provisions of Title 14 Code of Federal Regulations Part 91 and a Federal Aviation Administration (FAA) Certificate of Authorization (COA). The aircraft was destroyed by impact forces and a post-crash fire. There were no injuries. The Air VEV Zero 2 is equipped with 8 coaxial pairs of electric engines, each with 4 fixed-pitch propeller blades (figure 1). The airframe has a fixed quad-cycle landing gear. Figure 1. Air VEV Zero 2. (Source: Air VEV) The aircraft is flown visual line of sight (VLOS) by a remote pilot. A ground control station operator monitors telemetry, aircraft system status, and signal status. The remote pilot and ground control station operator are in communication with each other. According to the remote pilot and ground control station operator, the aircraft was flying a circuit pattern with no anomalies for the first completed circuit. During the second circuit, the motor temperatures began to increase. As a result, the remote pilot stated he began a descent and slowed the aircraft to prepare for landing. A ground witness video, which captured the last 8 seconds of the accident flight, showed the aircraft was flying level when it suddenly pitched up, near vertically, and then rapidly descended sideways (left wing down) to the ground until impact. The airframe manufacturer conducted postaccident analysis and testing of exemplar motors electronic speed controllers. Testing showed that high electrical current rate spikes could result in a shutdown of the motor as a hardware protection feature. Sudden increases in motor loads, such as during maneuvering, could result in these current rate spikes. During the accident flight, one of the aft motors likely shut down due to an irregular current spike caused by a sudden increase of load due to maneuvers. The shutdown of an aft motor resulted in a sudden increased load on adjacent aft motors that also led them to shut down. As the forward motors and propellers continued to produce thrust, the aircraft pitched up abruptly once thrust from the aft motors were lost.

NTSB coding

Evidence available

  • 3 docket documents
View NTSB final reportView NTSB docket

Docket documents3

Related mishaps