The evidence isn’t as compelling as I would like but I’m gonna guess that the P4Pro ran into some tree tops.The main problem is that the Google Earth data and the GPS:heightMsl indicate that the P4Pro was 142 meters AGL when the incident started. If it weren’t for that I’d say this is clearly a case where the P4Pro started running into tree tops.
The incident starts at 558.56 with an abrupt uncommanded drop in the leftFront motor speed.The acceleration data doesn’t show that the P4Pro hit something, at least not very hard
After that there attitude instability.
The Z axis gyro shows the P4Pro doing a very abrupt CW rotation.
All the motors except the leftBack are commanded at one point to 100%. Usually, just one of the motors will be commanded to 100% if there is a propulsion issue. Here it seems the P4Pro got tangled up and then loose several times
Most interesting is that the ultrasonic sensor starts indicating the P4Pro is close to something. I’m thinking the top of the trees.
Were there any physical indications like scratch or scrape marks.