DroneFlying
Second Officer
Flight distance : 10774613 ft
United States
Offline
|
After looking at the log I'm going to have to agree with DJI's analysis on this one. Your flight was pretty uneventful until you flew behind the mountain, and the image below shows a line between where you launched from (and presumably were located) and your Mavic at the time of last contact. That image is a little misleading because the log shows you didn't fly in a straight line but initially flew around the mountain and only eventually wound up behind it.
How can a mountain cut the signal so abruptly?
It's pretty easy for a solid obstacle like that to interfere with the signal, especially since the Mavic was almost a mile away from you when it flew behind the mountain.
And why did the drone not return to home?
It's very likely that it tried to, but your RTH height was only set to 30 meters / 100 feet, which wouldn't have been enough to clear the mountain on the return trip.
I was also getting a "battery overcharge" error shortly before the disconnection, but eased off the throttle immediately. Could it be possible that it was a battery issue?
I doubt it. The winds at that time were roughly 22 MPH near the ground and you correctly chose to fly upwind on the outbound portion of the flight. But as a result, the Mavic was having to fight the wind, which I'm guessing was why you were in Sport mode, and the large amount of power the Mavic needed to fight the wind was very likely the reason for the battery overcharge message.
Anyway, I'm sorry for your loss, but it does appear that DJI made the right call on this one.
|
-
|