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

Uvify IFO accident near Orlando, Florida, December 21, 2024

On December 21, 2024 at about 11:35 pm local time, a Uvify IFO, registered UNREG, was substantially damaged in an accident during maneuvering near Orlando, Florida. It was flown under rules the NTSB did not record. There were serious injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The remote pilot-in-command’s (RPIC’s) failure to locate the drone show center position over the physical location of the sUA, which resulted in multiple sUA colliding during the initial lift and subsequent loss of control. Contributing to the accident was the RPIC’s inappropriate geofence that was contrary to company procedures and an incorrect show heading which moved the show closer to the spectators. Also contributing to the accident was the operator’s lack of show oversight which allowed for multiple individual errors to go undetected before show start.

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

What the record shows

Date
December 21, 2024 · about 11:35 pm local time
Place
Orlando, Florida · map
Type
Accident · mid-air collision
Injuries
There were serious injuries.
Weather
visual conditions (good weather)
Aircraft
Uvify IFO
Registration
UNREG · no longer on the register · serial 21482IFOD01050100834
Damage
Substantial damage
Flight
Flight · rules the NTSB did not record

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

The accident occurred during the initial phase of a 500 small unmanned aircraft (sUA) drone light show when multiple sUA failed to achieve proper spatial separation, resulting in midair collisions and subsequent loss of control. Several sUA entered the audience which resulted in a serious injury to a spectator. Drone show software (DSS) revealed that the uploaded show center position was incorrect resulting in an approximate 5meter (16.4ft) displacement from the intended location. This error caused the system to assign incorrect aircraft to flight paths. In addition, the show heading had not been entered correctly and was rotated by about 7°. These cumulative errors resulted in crossing paths and collisions during takeoff with flight paths closer to spectators than intended. Furthermore, when the show center location was updated only 498 drones were selected rather than 500, which resulted in 2 drones with different show center positions than the others. Because the system relies on precise spatial alignment for deconfliction, these inconsistencies caused multiple sUA to converge during the initial climb, consistent with video evidence showing non-uniform liftoff followed by collisions. The misalignment of the show heading resulted in the show flight position being off by about 18 meters or 59 ft, which moved the show closer to the audience. The policy for margin between the soft geofence and hard geofence had changed from 5 meters (about 16.4 ft) to 1 meter (3.28 ft)12 days before the accident. According to the operator, it was the responsibility of the remote pilot-in-command (RPIC) to update the command laptops with the new margin default setting as they were being used for shows. The data revealed that the geofence margin had not been updated and was set to 5 meters (16.4 ft). The combined errors resulted in a reduced safety area that was outside the company’s standards. The FAA-issued certificate of waiver assigned responsibility for safe operations to management personnel. However, the operator lacked a formal requirement for independent verification of critical show parameters before launch. The absence of a robust cross-check or supervisory oversight allowed multiple configuration errors—including incorrect show center position, improper heading entry, inconsistent aircraft updates, and nonstandard geofence settings—to go undetected.

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. Miscellaneous/other during maneuvering defining event

The NTSB's findings

  • Personnel issues › Task performance › Planning/preparation › (general) › Pilot
  • Personnel issues › Task performance › Use of equip/info › Use of checklist › Pilot
  • Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
  • Organizational issues › Management › Policy/procedure › Availability of policy/proc › Operator

Pilot

  • Certificate: remote
  • Last flight review: April 3, 2023
  • Medical certificate: None
  • Seat: none
  • Injury: no injuries

The aircraft

  • Last inspection: condition inspection, December 21, 2024
  • Landing gear: fixed
  • Engine 1: Unknown (electric); 0 hours total
  • Engine 2: Unknown (electric); 0 hours total
  • Engine 3: Unknown (electric); 0 hours total
  • Engine 4: Unknown (electric); 0 hours total

The flight

  • Departed from: Orlando FL at 11:30 pm

Weather at the time

  • Light: night
  • Wind: from 030° at 6 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 54°F (12°C), dew point 43°F (6°C)
  • Altimeter: 30.15 inHg
  • Observation at 6:53 pm from KORL, 2 miles away

Weather report (METAR): METAR KORL 212353Z 03006KT 10SM CLR 12/06 A3015 RMK AO2 SLP216 T01220056 10161 20122 53013=

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

7 documents, released by the NTSB on September 15, 2026. 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.

Other NTSB records under UNREG the same tail number, which may have belonged to a different aircraft at the time

2026-07-07CEN26LA246 · accident near Hooker, OK · substantial damage · minor injuries
2026-02-28CEN26LA131 · accident near Van Burensburg, IL · substantial damage · no injuries
2025-10-13ERA26LA017 · accident near Gaffney, SC · substantial damage · serious injuries
2025-09-27CEN25LA397 · accident near Harvard, IL · substantial damage · no injuries
2025-09-12CEN25LA385 · accident near Rossville, IN · substantial damage · serious injuries
2025-07-07CEN25LA242 · incident near Ingram, TX · minor damage · no injuries
2025-06-18DCA25WA305 · accident near N/A · serious injuries
2025-05-01OPS25LA034 · incident near Washington, DC
2025-04-11CEN25LA155 · accident near Brady, TX · substantial damage · serious injuries
2025-01-30DCA25MA108 · accident near Washington, DC · destroyed · fatal

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.