The usual suspect of obstacle avoidance doesn't appear to be involved.
And VPS isn't acting up - but that usually caused a failure to descend so it's not really suspected in this case.
I've tracked down something deep in the data regarding RTH that is different from normal but it's not self-explanatory so I'm not sure what it means.
Perhaps
@sar104 could work it out.
Looking at the columns for OSD.goHomeStatus & OSD.goHomeStatus.RAW, in a normal RTH, the steps should be:
Standby 0
Preascend 1
Align 2
Cruise 4
But yours shows:
Standby 0
Cruise 4 - (one line only)
Other 7 - (for the rest of the time it is in RTH but going nowhere)
Not preascending is because the drone was already higher than the set RTH height, that's no problem.
But what is GoHomeStatus Other 7 and why is it happening after only one line of Cruise?
For the second flight those data columns show Other 7 for the whole flight, and not just when RTH is initiated.
Any suggestions
@sar104 ??