Hazard Reporting

So very frustrated!

Our UAS program is slow to get going as the coordinator of the program is tasked with other duties and the program taking a seat on the backburner in the time being.

I was recently provided access to the County IT Department fleet which includes Mavic 2 Enterprise Advanced.

On Monday (3/27) we had a vehicle pursuit which ended up with the vehicle crashing at a Corp of Engineers area near the river at the edge of city limits. The driver fled on foot from the crash.

Our Sheriff Department assisted with the search for the suspect with their vehicle mounted Flir and a K9 track was attempted. Neither found the suspect.

I was contacted around 0200 in regard to if we had access to a thermal drone. I had access to IT's Mavic 2EA.

I was approved for the deployment and responded to the scene.

I performed my usual pre-flight checks which included weather/airspace and ensured that the equipment was airworthy.

I launched to an altitude of 6ft and performed an input check with the remote control. All inputs were responsive, and no issues were observed.

I climbed to an altitude of 50ft where I held position and adjusted the view of the thermal camera to an oblique angle for maximum view of the area. While I was hovering at 50ft and watching the screen to adjust the view of the thermal camera, the drone fell out of air and struck the ground about 15-20 ft from the landing pad.

The drone sustained damage which rendered it inoperable.

From launch to crashing was within 1 minute.

To make matters worse beyond a failed deployment, one of the younger officers felt the need to be immature and unprofessional and change my unit details in the CAD to "The Drone Destroyer" which quickly spread not only throughout the department but into the Sheriff Department as well.

Later that morning I went into IT with my tail between my legs and broken drone in my hand. While explaining what happened, the IT guy observed a scratch on the top of the Mavic 2EA near the beacon where no other damage was observed.

Review of the flight records shows the drone being deployed to altitude of 6ft and the input check. Then it shows the climb to altitude of 50ft and hovering. The flight record does not show the change in altitude from 50ft to crashing. Minimal flight stick input while hovering at 50ft which was to adjust the view of the area and then adjusting the camera angle.

Tentatively it is being believed that while I was hovering at 50ft an owl attacked the drone. They are going to put the drone and propellers under a black light to see if they can find traces of blood on it.

To add to the unsuccessful deployment, the officer changing my CAD details to "The drone destroyer" is affecting my creditability as a remote pilot. Since being selected for the drone team I have put a lot of effort into gaining knowledge and experience in this program for not only myself but for the department.

It's unfortunate that this incident occurred while we are trying to get the program off the ground. Certainly, does not help get our program off the ground.