Your first TXT log ended at around 343sec with 64% battery ... your craft was then up on the max set height (200m) & the connection started to be sketchy (white vertical stripes in the chart=disconnected). All RC commands was nicely obeyed by the craft as shown in the data compiled in the chart.
Dotted graphs is the stick inputs ... Rudder (red) correlates to a yaw movement (blue), Elevator input (purple) correlates nicely to heading speed changes (black) ... and throttle commands (yellow) fits nicely to changes in the vertical Z-speed (light blue).
All was normal ...
View attachment 136291
... and your craft was here when the first log ended ... note at the big red arrow that the mobile device location is included in the data (explain further below...)
View attachment 136294
When the log recording continues (the second .TXT log) the timing is 1188sec & the battery is down at 1% & the craft is lowbattery auto landing. No stick inputs is made what so ever. & the connection is still sketchy (white vertical stripes in the chart=disconnected).
View attachment 136295
... and the craft is now here & are descending, the second log ends at 181,9m height relative the HP. Also note that during this short second log no mobile device position data is included anymore.
View attachment 136296
So what happened in between those 2 logs separated with 845sec & 63% battery ..?
My firm belief is that this was due to a disconnect between your RC & mobile device ... the craft obeyed all inputs it got according to the logs ... it had moved horizontally in between the 2 logs ... & in the first log the mobile device position was included in the data but not in the second.
So why didn't it make a low battery RTH ? I believe it actually did ... but either you canceled it unintentionally by pushing the RTH button on the RC, below from the manual... or it encountered an obstacle blocking it's way & the OD sensors stopped it.
View attachment 136298
The mobile device DAT log you included pretty much confirms my idea about the RC/mobile device disconnect ...
View attachment 136299
In order to know more about what happened in between those 2 log recording occasions the craft DAT log is needed.