Hello,
Just wondering ... as my
Mavic 3 went mental and crashed on fence.
Hi there & welcome to the forum ... even though it's due to this unfortunate incident.
Your log reveals 2 thing's mainly ...
1. Your
Mavic 3 was seriously malfunctioning during most of this flight. This affected systems like barometric height, GPS positioning & the connection between your
M3 & controller. You got a lot of warnings about all this on your screen device but you disregarded them & continued the flight anyway.
2. The log also show that you ... most probably in confusion, flew your
M3 into that fence with max Sport mode speed & didn't release the forward speed stick until the
M3 had crashed.
If we start up with all M3 malfunctioning systems ...
The first chart below covers the whole flight.
The green background color to the left = Motorstart & take off
The pink background color = GPS mode with APAS activated
The white background color = loss of connection between RC &
M3
The blue background color to the right = Sport mode
The red graph = Barometric height above the location where you started the motors (there the barometric sensor was reset to 0ft)
As you see ... the barometric height goes way out of showing correct values, the place where you flew was flat ... no way that you could have flown 22 ft below the point where you started the motors.
Further more, look at all the white areas where the red graph doesn't record ... that's connection interruptions. Seems very odd as you flew in an open place close by.
(Click on the chartsbelow to make them larger)
Here below we look at how bad you GPS is functioning ...
All background colors mean the same as earlier ... but with 2 additions.
The second green background color from the left = ATTI mode (no GPS positional hold at all & no auto braking)
The grayish background color = No home point recorded ( it gets recorded 220sec into the flight with your
M3 far out over the go-cart track.
The black graph = GPS level (which is how reliable the flight controller thought the GPS position was on a scale from 1 to 5 ... with 5 as best. The home point doesn't get recorded until 4. As you see your
M3 dropped down to 2 on a regular basis totally unmotivated ... you flew in an open place & your
M3 should have had a clear view of the sky.
Then over to the crash & what you commanded your M3 to do ...
In below chart you see only the very end of the flight.
Background colors same as before ...
Green graph = heading speed in mph.
Blue dashed graph = elevator stick input (the right stick forward/backward ... neutral stick reads value 1024)
Purple dashed graph = throttle stick input (the left stick forward/backward ... neutral stick reads value 1024)
And again, the black graph = GPS level
It's easy to see that you switch to Sport mode (green background color) ... the speed is 0mph (green) & you're hovering just before switching mode. Then you command full speed with the elevator stick (dashed blue) & the heading speed increases (green) & tops out at just over 43mph. You also apply a throttle stick input (dashed purple) to ascend ... then at 916sec into the flight you crash. The gps level went to a 2 there in the end (black) ... but you didn't got ATTI mode so braking when releasing the sticks still worked, which is confirmed when looking in this chart.
So your
M3 didn't fly itself into that fence ... you did.
In the end you shouldn't have flown this
M3 ... it showed to many failures in vital systems. Your
M3 have serious failures that you should be able to pinpoint to DJI ... but that you flew anyway just made thing's worse & your commands made it crash.