just came across this post and after flicking through all the non post subject junk get to the end.
This is how i see it, the litchi app cant be blamed until everything is seen, we have not seen the mission layout data of the waypoint height settings as it might have just been doing what it was told to do, for one the phantom would not go that high unless the pilot had set that height in the max height settings or it would just use the height setting that the go app set last.
seems to me that the op went into pannic and did all the wrong things going from one to the next and yes I think the motors were shut off by the pilot while still in a tizzy.
(...)
How do you explain the numerous incoherent data in the report of :
Phantom Log Viewer - PhantomHelp.com
...concerning this deadly flight ?
Example :
4m 44s Auto Landing 16satellites 1,376.0ft 7.7mph 28.4ft
4m 44.1s Auto Landing 18satellites 1,378.0ft 8.7mph 33.4ft
4m 44.2s Auto Landing 18satellites 1,379.0ft 9.0mph 34.9ft
4m 44.3s Auto Landing 19satellites 1,380.0ft 8.6mph 37.5ft
4m 44.5s Auto Landing 19satellites 1,380.0ft 8.1mph 41.8ft
(...)
4m 59.2s Auto Landing 19satellites 1,465.0ft 0.9mph 80.5ft
4m 59.6s Auto Landing 19satellites 1,467.0ft 0.9mph 81.0ft
(...)
5m 7.8s Auto Landing 19satellites 1,513.0ft 0.9mph 95.8ft
During 34sec the drone is set in "auto-landing" and its altitude apparently **increases** from 1376ft to 1513ft (about 140ft is significant). The same about the speed of some mph which apparently doesn't move the craft in an other part of the filght record while it is set in "RTH".