# Incident 20201002021159I: Deland, FL, October 2, 2020

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 2, 2020, 12:32 local time
- Place: Deland, FL
- Damage: Substantial damage
- Phase of flight: Hover/Holding
- Location: 29.0227° N, 81.2865° W: Placed by OpenAirDocs: center of DeLand, FL, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=29.0227&lon=-81.2865&mi=10
- Aircraft: NONE (not matched to a registry record)
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20201002021159I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

UAS MAKE/MODEL: PARROT ANAFI THERMIL

SERIAL NUMBER: PS728120AB9G002089

FREQUENCY: 2.4 GHZ

REGISTRATION NUMBER: ^PRIVACY DATA OMITTED^

ISSUED: 03/22/2020

OCTOBER 02, 2020, ESTIMATED TIME OF CRASH 12:31PM LOCATION ^PRIVACY DATA OMITTED^ (CFA) ^PRIVACY DATA OMITTED^. THE PURPOSE OF THE FLIGHT WAS A TRAFFIC STUDY FOR ^PRIVACY DATA OMITTED^, CAPTURE NO LESS THAN 44 MINUTES OF TRAFFIC FLOW STARTING AT 12:00 AND BEFORE 13:00. USE OF 2 OR 3 BATTERIES. PERFORMED UPDATES ON OCTOBER 01 FROM DRONE, CONTROLLER AND 3 BATTERIES. PERFORMED PREFLIGHT AND TEST ON DAY OF ACCIDENT. PERFORMED PREFLIGHT AND TEST FLIGHT OCTOBER 02, 2020 AT 11:11AM TO MARK LOCATION, ALTITUDE AND SYSTEMS CHECK. FLIGHT LASTED 7 MIN 8 S. ONCE BATTERY COOLED IT WAS PLACED ON CHARGED.

1ST BATTERY AND BEGINNING OF MISSION FLIGHT. TAKE OFF AT 11:59. FLIGHT DURATION 18 MIN 11S. FIRST 15 S HOVER TO CHECK SYSTEM, CLIMBED TO 350 AGL. THE 2ND BATTERY TAKEOFF AND SIM CARD REPLACED. THE PREFLIGHT WAS PERFORMED BETWEEN 12:18 TO 12:21PM. AFTER LIFTOFF HOVERED FOR 15 S BEFORE CARING OUT MISSION AND CLIMBING TO 350 AGL TO DESTINATION SAME AS 1ST BATTERY FLIGHT. AROUND THE 15-MINUTE MARK ON BATTERY THE PERCENTAGE SEEMED TO START DROPPING AND WAS BETWEEN 20 TO 25%. AT THIS TIME, IT STARTED A SLOW DECENT OVER THE RESTAURANT BUILDING. OPERATOR HAD EYE CONTACT WITH UAV AND GLANCED DOWN TO CONTROLLER. PILOT NOTICED THAT SCREEN WAS BLACK WITH RED WARNING.WHEN PILOT LOOKED BACK UP HE HAS LOST VISUAL CONTACT WITH DRONE. ESTIMATED ALTITUDE AT THIS POINT 325 AGL OR GREATER. ONCE THE PILOT DETERMINED THE UAV WAS LOST HE SECURED ITEMS ON GROUND AT LOCATION (LAUNCH SITE WAS NORTH OF UAV FLIGHT PLAN). PILOT CHECK AROUND RESTAURANT PREMISES AND SURROUNDING AREAS FOR MISSING DRONE. A RESTAURANT EMPLOYEE ASKED THE PILOT IF HE HAD CRASHED A DRONE IN WHICH HE REPLIED THAT HE DID. HE INQUIRED IF ANYONE WAS HURT OR IF IT HIT ANY OBJECTS IN WHICH THE EMPLOYEE REPLIED THAT IT HIT A BLACK CAR. THE EMPLOYEE POINTED TO THE LOCATION OF THE VEHICLE AND MET WITH THE CAR OWNER. THE PILOT IDENTIFIED HIMSELF AND EXCHANGED INSURANCE INFORMATION. NO CLAIM OF INJURY WAS CONFIRMED AND NO POLICE REPORT SUBMITTED. THE DAMAGE TO THE VEHICLE WAS APPROXIMATELY AROUND $417.00

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.