1 & 2: First of all so had you disconnects between AC & RC in the end ... so if you commanded or not during that period will not show in the logs. But when the connection just in the end reestablish you only had speed straight down & the raw GPS data shows a position just in the edge of that forrest ... so what you may or may not do before that, it all ended up there. And as I stated earlier the gimbal pitch wasn't straight down witch may have led you believe that you had passed the trees.
3: No ... as seen from both the TXT & DAT log the same last valid GPS position is the same in both logs, you have got that position so my advice is that you start your search there ... the bogus position out in the sea isn't valid, the navhealth was zero by then. Furthermore pure logic tells us that the
M2Z couldn't have flown that distance of above 10 kilometers away with a battery at 13%, with autolanding in progress & in a time span that needed a speed over 40 m/s.
The basic is that the TXT log is recording from motors on to off & the DAT log from power on to off ... this if the RC/mobile device is in contact with the AC.
The TXT log ends at 1136sec after motor start, at that time your
M2Z was in autolanding with only down speed at 37m above your HP ... then the log ends with a AC/RC disconnect and then the motors probably stopped hitting the trees ... so end of TXT log.
The DAT log though, still were recording as you luckily regained AC/RC connection ... when that log continues it shows the same position as the TXT log, no speed what so ever ... but a height of approx 4m below your HP indicating ground level. The DAT log records 851sec longer then the TXT log, indicating power still is on but nothing happens, all still in the same position (some small stick movements are registered, but AC is on ground with motors off so nothing happens), then that log also stops, probably due to AC/RC disconnection.