Controls were all in default settings.
Where the video stopped, the data stopped logging also. 8.16m
The 1st thing I noticed was there was no compass calibration. Not that there needed to be, I just have the ability to see if one was performed prior to.
Next I saw a warning you received when reaching the max set height, which was not that high.
At this point I went on to see if the data gave any appearance of hitting a tree limb as mentioned in one of your post. While I found no evidence of that taking place, I did begin getting a very good feeling that your aircraft (a/c) had been attacked by a bird. This was based on what I saw in the Pitch data and Height data at the same point and time. The nose of the a/c went downward while traveling forward, and in the same time frame the a/c also climbed nearly .46 meters.
I then looked over everything that would indicate a motor issue and found nothing.
I then paid attention to the pilots flying characteristics with the r/c during the point in which the a/c began to come down.
It was after I went through the tumbling part of the video frame by frame and sync's what I saw there and with the data from the pilots control with the r/c that lead me to the final call.
The final call is the left rear propeller broke. It either broke off in flight, or broke but not completely until contact with the ground......... So now if none of the following took place, then you can go back to the bird attack. 1) If the mentioned Propeller has never had any contact with any surface, ever. 2) If you have never tightened down the propeller with a tool to assist you.
If your answer is NO to 1 & 2, go with the bird. Btw, nothing electrical stood out anywhere that was abnormal until the last 3 lines of data which would equal milliseconds well after the point which the a/c came down.