OK - well that's a great illustration of how to misinterpret the flight data. It never occurred to me to check if you flew it into an obstacle, so I never bothered looking at the velocity data, nor worried about why the yaw response happened before the errors. Very careless.
So yes - that is what the data shows - simultaneous forward motion with descent, followed by an impact. The GPS and sensor errors were a result of that, not the cause, and the high vertical speed after impact was obviously due to the sensor error, and not real.
View attachment 98064
So unfortunately that was not a hardware problem, except in the sense that the hardware lost the battle with the tree, and won't be covered under warranty.