So if we first start to look at the AC movements when thing's start to go haywire ...
At 19,76sec the AC rapidly pitches down (Light blue), this together with a roll going all over in negative direction (Blue) & a yaw that turns CW. This leads to a spiraling rapid descent from 3,89m height to ground. All this indicate as I said earlier, a lost thrust from the left front ... either a motor failure or a lost prop.
As a side note to this we also see that even though the barometric sensor reports a height over HP to 3,89m (Red) the ultra sonic sensor says 0,1m (Black) witch indeed indicates that the sensors were covered or disturbed by the silicon cover ... but even so, that alone can't bring down the AC in this way.
(Click on the charts below to bring them up full screen)
View attachment 105136
Looking further into the motor RPM's show us that something happens with the left front (Magenta) ... at 19,86sec the RPM suddenly drops to only 691rpm's while the others rev between 7700-10300rpm's.
View attachment 105138
Then looking into how the motors was commanded by the flight controller ... As seen below the FC wanted the left front motor to spin 100% (Purple) from 19,75sec. But that only resulted in 691rpm eventually as per chart above.
View attachment 105139
The last check is regarding the motor current draw when all above happens ... at 19,87sec we see that the left front spikes up (blue), indicating it's been jammed.
View attachment 105140
So from above it looks like the reason for this incident was a sudden stop of the left front motor ... either some debris was blown up at take off & into the motor or something internal in that motor came loose & blocked it. Even though something is going on with the downward height sensors (according to the first chart) it can't make a motor stop at height.