A strange case that happened to me, I was standing high in relation to the destination I wanted to fly to. I advanced towards the destination and slowly descended but then as a result of descending, the Mavic went into landing state. Left stick all the way up canceled the landing But it intrigues me to know why it happened.
In practice in terms of height from the ground I was at least 30 meters when Mavic decided to land.
Note : this is not U[color=var(--ytd-video-primary-info-renderer-title-color, var(--yt-spec-text-primary))]ncontrolled Descent, this is actual landing state.
[color=var(--ytd-video-primary-info-renderer-title-color, var(--yt-spec-text-primary))]

https://app.airdata.com/share/tQsNlS/GENERALOverview

I guess it is related to sonar data. take a look here :




Thanks.

A strange case that happened to me, I was standing high in relation to the destination I wanted to fly to. I advanced towards the destination and slowly descended but then as a result of descending, the Mavic went into landing state. Left stick all the way up canceled the landing But it intrigues me to know why it happened.
This shows your flight data much better than Airdata's summary:
https://www.phantomhelp.com/LogViewer/08IDX1QZVJC3WRBQHGZH/

At 0:59.9 (not the time you indicated above) you pulled the left stick full and held it there.
The downward facing sensors indicate the drone was 0.8 metres above the ground at the time.
That brought the drone down and you continued to hold the left stick down which initiated a forced landing at 1:01.3, which you cancelled at 1:02.9

In practice in terms of height from the ground I was at least 30 meters when Mavic decided to land.
Your VPS sensors were indicating that the ground was no more than 9.5 metres (at 1:47.5) above the ground anywhere during the flight and often much closer.
If this is incorrect you need to clean the downward facing sensors or remove whatever is blocking their view below the drone and recalibrate the downward sensors.

Hi. I am sorry for the trouble this has caused. With regards to this concern. As Labroides advised at post #2, kindly please check if there any scratches or dirt on the downward sensors that might be causing this issue and please try flying in a different location with less interference to isolate he issue. Please keep us posted for further assistance. Thank you.

It was indeed very dusty area.  Since this is the first time it happend, For now, I am sticking with the "dust on sensor" theory.

have you check this? https://app.airdata.com/share/tQsNlS/GENERALNotifications

ZenKaffi Posted at 7-31 07:38
have you check this? https://app.airdata.com/share/tQsNlS/GENERALNotifications

I already gave him something much more detailed than Airdata provides.