here you will see this flight was first time i could tell my controller was not connected to drone and first time i had seen the numbers of flags going off one after the other like on 6/13
I've asked a few questions three times now to get a better idea of your flying experience, but you have completely ignored me.
It's clear that you have no regard for flying rules and frequently fly as high as the drone can go.
Here's the story that the recorded flight data tells ....
(btw .. this data analysis and reporting what it shows, took 2 hours)
A couple of unusual things I noticed in this flight are that although the drone is already at 1640 feet, you keep trying to go higher, pushing the left stick to the limit as you fly.
And when you fly, instead of flying straight forward you commonly have the right stick pushed fully forward and also pushed left to some extent.
You are frequently losing the downlink and sometimes getting weak signal messages.
This shows in the recorded flight data, but you might not be aware of it while flying.
AT 9:20.8 the drone entered RTH and started heading home.
At 10:02 you cancelled RTH and 20 seconds layer started flying further away from home again.
At 13:06.6 you went to RTH again and the drone started towards home from 8677 feet southwest of home.
At 14:45.3 with the drone still more than a mile out, you get an important message:
Critically low power. Aircraft is landing.
Since 9:19 you have ignored four messages that advised you : The remaining battery is only enough for RTH. Return home now.
Instead of returning, you flew further, turned back to fly further again after RTH for a while and flown in Sport Mode, which burns the battery faster.
You left the drone autolanding for almost a minute before resuming forward flight.
From 16:18.1 although you had the right stick fully forward, the drone refused to fly forward and only descended, presumably because the battery level was too low to support forward flight + autolanding.
During the descent you received more downlink lost messages which might have confused you as the drone appeared to be ignoring your control inputs.
AT 17:06.2 with the drone >4000 ft out and having descended from 1640 ft to 300 ft, you tried pushing the left stick up to stop the descent.
This had no effect because the battery level was too low and the drone was trying to descend safely rather than run out of power and fall from the sky.
The descent continued with data ending at 17:03.3 with the drone 233 feet higher than the launch point and >400 ft from home.
It's not clear if data ended because the battery failed and the drone fell, or if it just lost signal through the forest and continued to descend safely, possibly getting hung up in trees.
regardless of what record shows i can tell you what my controller was telling it to do and what it was doing not same for few seconds here and there was in my sight no obstructions here is that flight
I don't see anything remotely looking like losing control or having the drone jammed.
I see a drone that autolanded when battery level was critically low, not a drone that fell like a stone.
Your drone responded exactly as it should to all your joystick inputs.
You may have been confused by losing downlink multiple times.
I do see plenty of signs of a confused and disoriented flyer who didn't know how to fly safely out and bring the drone back again.
If you go to the Airdaya report and click on the Notifications link above the map window, you will see a listing of all the warnings from the flight.
Note the number of times you lost downlink and how long you lost it for.
When this happened, you had no new video data from the drone, but the drone was still connected and receiving your joystick inputs.
That will have been part of the confusion you experienced.