Air Crash.

[BudWalker]

@gupppy The .DAT continued recording after the MA crashed. You might want to look at the last recorded position in the .DAT which was about 36 meters past the last recorded position in the .txt

 

[gupppy]

Thank you BudWalker this was a problem coming, now I know. Just wish I can find the drone.

 

[BudWalker]

Thank you BudWalker this was a problem coming, now I know. Just wish I can find the drone.

Did you get a chance to look for the MA? It's likely that it came to rest at the location I showed you in post # 21. That's coordinates Longitude 18.812661°, Latitude -34.099026°.

 

[gupppy]

Hi BudWalker, yes we looked in the spot for day`s. Area was a security area back in the day`s. ( they use to test explosives) I was granted permission to search there. The spot is so overgrown that you could be 1 meter away and not see it. The only hope is the the craft had my cell number on an someone (with reward) will find it. I do get some feed back form DJI and I expect to get a result from them soon. I`ll let you know.
Thanks for you concern.

 

[gupppy]

Hi BudWalker, yes we looked in the spot for day`s. Area was a security area back in the day`s. ( they use to test explosives) I was granted permission to search there. The spot is so overgrown that you could be 1 meter away and not see it. The only hope is the the craft had my cell number on an someone (with reward) will find it. I do get some feed back form DJI and I expect to get a result from them soon. I`ll let you know.
Thanks for you concern.

Hi BudWalker,
I thought I`ll let you know that DJI regards this case as a fly away. They are going to replace the drone. I AN SUPER HAPPY!!
Cheers mate

 

[AntDX316]

There are a few possible explanations for this behavior, but the txt log doesn't contain the necessary data to distinguish between them. The problem was a disagreement between the IMU velocity and position data, triggered by a CCW full rotation at 566 seconds:

View attachment 79897

Looking in position rather than velocity space:

View attachment 79898

It might have been a yaw error due to an incorrectly initialized IMU yaw value caused by taking off from a magnetically distorted location, a compass calibration issue, or simply a failure of the IMU inertial sensor package. The lack of any problems for most of the flight generally makes the first two options less likely, but IMU failure is much less common. The answer will likely be in the DAT file (FLY060.DAT) data if you want to retrieve and post that.

Mobile device DAT file: How to retrieve a V3.DAT from the tablet

Nah, I've taken off from 999 compass spots and it works fine.

 

[AntDX316]

DJI Flight Log Viewer | Phantom Help

Upload and view flight logs from your DJI drones

www.phantomhelp.com

 

[Keule]

Nah, I've taken off from 999 compass spots and it works fine.

Are you the OP?

 

[AntDX316]

Are you the OP?

no, are you? I'm on a Mavic 2 Zoom and Pro.. I didn't realize it was for Mavic 1 Air until now..

 

[Keule]

no, are you?

No

 

[Meta4]

Nah, I've taken off from 999 compass spots and it works fine.

What are you trying to say?
What's a "compass spot", what does taking off from 999 of them prove?

 

[sar104]

Nah, I've taken off from 999 compass spots and it works fine.

DJI Flight Log Viewer | Phantom Help

Upload and view flight logs from your DJI drones

www.phantomhelp.com

You are a bit late to the discussion. This one was resolved several days ago and yes - what I posted in #4 was correct. The details, from the DAT file, are discussed in posts #18 and #20.

 

[MPPilot]

Almost seems like we need to start strapping a cell phone to the back of our drones so we can use the "find my phone" app to find the drone. Maybe DJI will come out with a data enabled drone in the future.

 

[msinger]

Almost seems like we need to start strapping a cell phone to the back of our drones so we can use the "find my phone" app to find the drone

Or a tracker?