DJI Mavic, Air and Mini Drones
Friendly, Helpful & Knowledgeable Community
Join Us Now

Mavic Mini flyaway

Here is another one to try. Thanks for your help btw.
It's scrambled as well.

Looking at your flight path and description of the incident in post #1, it has a lot of the signs of a yaw error incident.
Can you describe the surface you launched from and any steel items that might have been within 10 feet of it?
 
It's scrambled as well.

Looking at your flight path and description of the incident in post #1, it has a lot of the signs of a yaw error incident.
Can you describe the surface you launched from and any steel items that might have been within 10 feet of it?
If I remember correctly this was a hand launch on this occasion. The structure I was trying to photograph is a steel structure...but I believe I was approx 50-60ft away.
I flew towards it (drone flew normally - no issues), then flew backwards to get a better shot of the city in the background.
Looking at the screen I noticed that it started to drift slowly to the left - no wind at all.
When I then looked up at the drone to check it position it then just flew in a circle and then off to my right - I thought I had lost it as it wasn't responding to my stick control.
Eventually after a few seconds I managed to regain control, reduce altitude and flew back and landed.

Any reason why the flight data is scrambled?
 
Looks like the data is corrupted somehow.


Have seen this before, @sar104 did one like this not sure if it could be delat with.
I'm sorry ... there's something wrong with the file.
It's giving crazy data that's very, very wrong, and I can't tell anything about the flight from it.

There's a remote chance the @sar104 might be able to untangle it?? (maybe)

Right - another one of those. Yes - it's recoverable - I just need to apply the correction routines. That will take a while.
 
  • Like
Reactions: Prismatic and Meta4
That's the correct file, but the problem appears to be magnetic interference at startup. Can you see if you can find the mobile device DAT file ending FLY043.DAT?
Hi, thanks for the reply...looking through my phone it says that this folder is empty.
 
I have managed to look at the flight data on airdata and according to this the propeller has fallen off several times during the flight.
1587739057315.png
1587739074245.png
 
I have managed to look at the flight data on airdata and according to this the propeller has fallen off several times during the flight.
View attachment 99529
View attachment 99530

No - the txt flight logs from your aircraft are corrupted, and so the AirData parser is simply getting confused. You didn't have any propeller issues, and most of those notifications are artifacts of the corrupt data. I have cleaned up the important data - hence my comment above that this looks like magnetic interference at takeoff.
 
Well if you want access to the DAT files when you need them then yes - it should definitely be turned off.
Thanks for your help. Have you any idea why they would be corrupted? Anything that I need to do?
 
Thanks for your help. Have you any idea why they would be corrupted? Anything that I need to do?
Would the file be corrupt as well if downloaded from AirData? Looks a bit better than what Phantom LogViewer displayed.

Neither of those websites is able to correct the data errors. I've not been able to figure out what causes it - I've only seen three total instances of this problem.
 
It is either magnetic interference at the takeoff location or an IMU problem in flight - the velocity disagreements are quite characteristic:

Delta_V.png

Unfortunately, without the DAT file that contains the raw sensor data, it is difficult to figure out the exact cause.
 
I should think that the recovery of control is a clue, no? An intermittent failure in the IMU could (possibly, maybe) revert to correct performance in flight. In contrast a yaw error caused by a faulty compass initialization is never "autocorrected" because there's no physical fault at play, intermittent or otherwise. (Assuming the Mini can't reset the compass after takeoff; only the Mavic 2 has that capacity.)
 
  • Like
Reactions: MAvic_South_Oz
Considering all the above, I'd think the only thing the OP can now do is contact DJI (chat), tell them you've had this crash and ask what has happened . . . go through the procedure of having them look at the log (and DAT they should have).

It will come down to them doing the right thing unless they can find a definitive pilot error somewhere.

One more thing you COULD try, is when talking to DJI, ask for the copy of the DAT file to be emailed to you.
There was a case just in the past few days here, where the pilot asked for his DAT, and they sent it to him.
It was uploaded there and checked.

Here it is . . . check on from this past by that thread OP . . .

 

DJI Drone Deals

New Threads

Forum statistics

Threads
135,471
Messages
1,606,441
Members
163,916
Latest member
chrusse
Want to Remove this Ad? Simply login or create a free account