In the second half of the flight you constantly commanded negative throttle (purple graph) for descent most of the flight & the vertical speed (blue graph positive for descend & negative for ascend) answered nicely with positive values. The green graph shows the height above ground directly beneath the AC measured by the VPS sensors on the belly ... in the end of the flight just where the grey background starts (which indicate a force landing) you are just 0,5m above ground ... and continue to apply negative throttle for descending, which at that height (0,5m) initiate a "vertical low limit force landing".
So ... you can't fly lower over the ground beneath the AC than 0,5m, applying throttle for descend there will start the landing process.
(Click on the charts below to make them larger)
View attachment 132904
It's one spot that stands out though ... it's between 414sec to 420sec approx. where the barometric height (red graph) decreases from 5,2m to 1,3m without any throttle input ... at the time the AC was 3,2m above ground beneath. This could indicate that the barometric sensor isn't fully functional. If you could share the corresponding mobile device DAT log for this flight ... maybe something in there can give a clue. The correct DAT log ends with FLY058.DAT ... it's located in a sub folder
MCDatFlightRecords in the same place where you founds the .TXT log you attached.
View attachment 132908
And just to show off the battery data ... to end the speculation, no problem with that battery.
View attachment 132905
It's perfectly normal that the barometric height (which always is relative to the take off point where the sensor is reset just after take off) ... can differ from the VPS height which measures the height above ground directly beneath the AC.
If you take off from the top of a 50m high hill and fly down in the valley & stopped 1m above ground down there the barometric height will report -49m ... but the VPS heigh would be +1m.
No need to calibrate any IMU's ...