Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

October 23, 2025 · Air Vev AIR ZERO2 · N514AX

Indiantown, FL

Overview

Report Status
Probable Cause
Event Type
Accident
Date
October 23, 2025
Injury Outcomes
No injuries (1 uninjured)
Location
Indiantown, FL
Aircraft
Air Vev AIR ZERO2 (2024)
Tail Number
N514AX
Operator
Air Vev
Injuries
None
Aircraft Damage
Destroyed
NTSB Number
DCA26FA019

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 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.

Full 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.

Flight

Event TypeAccident
Event Time12:11 EDT
Nearest AirportIndiantown (0nm SE)
Runway31
Runway Length6300 ft
Runway Width75 ft
Flight Plan FiledNone
Aircraft FireGrd
Aircraft ExplosionNo

Aircraft

AircraftAir Vev AIR ZERO2
Tail NumberN514AX
Aircraft CategoryPlft
DamageDestroyed
OperatorAir Vev
Operating RulePart 91
Engines8
Engine TypeElectric
Engine DetailsMgm Compro · REB 60 · Electric · 96 | Mgm Compro · REB 60 · Electric · 96 | Mgm Compro · REB 60 · Electric · 96
Seats0

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 38 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind320° @ 5 kt
Visibility10 sm
CeilingNone
Altimeter30.02 inHg
Observation Time07:47
Weather SourceWFAC

Appendix: Source Data