DJI Mindy Posted at 2017-2-27 03:14
At 00:36, you were flying forward with full throttle and crashed. Please refer to the screenshot.
Sorry for the misunderstanding.[view_image]

No I was at full throttle at 00:35 and cut off at 00:36:02. The drone should have stopped movement but continued on its own forward. I gave commands to drop and strafe right,  Why is that being ignored by support?

hallmark007 Posted at 2017-2-27 04:11
Think if you look again you will see the OP was 18.6 meters high.

Seriously? 18.6 is my distance from initial takeoff, not height.

Impact9 Posted at 2017-2-27 18:32
Seriously? 18.6 is my distance from initial takeoff, not height.

Your height is measured at 0 from your take off so I was assuming once you crossed the bridge you were now in a minus height and was adding that to your height from the water..

Impact9 Posted at 2017-2-27 18:32
No I was at full throttle at 00:35 and cut off at 00:36:02. The drone should have stopped movement but continued on its own forward. I gave commands to drop and strafe right,  Why is that being ignored by support?

Since you are flying with full throttle, it will takes some times to brake.
The drone will not stop immediately after you release the stick.

Note there is a throttle problem as I was only going 15.8MPH at full throttle.  It doesn't take 3 second to come to a stop. Also the drone doesn't slow it continues to move forward. Again, explain why the drone does NOT respond to commands to strafe right or drop. In total I've asked this at least 8 times between here, through email, and on phone calls.
Nobody acknowledges that the drone is doing things on its own (moving left, rising, moving forward) while ignoring dead stick, straffe right, and drop commands.

Can anyone at DJI look into my case at this time? I was able to recover and returned the drone on 2 March, it arrived to the California center on 10 March and sat on the dock till 22 March. It's be under Damage Assessment since 23 March. I'm hoping they are able to see the errors not showing on my flight logs that are on the cloud and can also explain the uncommanded movement left and up which caused this accident.

CAS-485607-Q9Y3D2