There are multiple inconsistencies about this flight. Can you retrieve the .DAT from the controller. The instructions for retrieving the .DAT can be found here
Mavic Flight Log Retrieval and Analysis Guide
section 3. Log File Retrieval ->
Mobile device DAT files (DJI GO 4 & DJI Fly)
I didn't see any evidence of a collision at 375.8 secs (6 mins, 15.8 secs). It does appear that the AC began to tumble (spinning on all 3 axes). We would need the .DAT to determine if it was tumbling.
With regards to the horizontal speed dilemma there is another indication that the
Mini2 was moving faster than the specs would allow.
View attachment 157888
The the green plot shows the horizontal speed logged in the .txt that
@msinger and
@Meta4 noted isn't physically plausible. The red plot is horizontal speed computed as sqrt(xSpeed * xSpeed + ySpeed * ySpeed). xSpeed and ySpeed are believed to be derived from the doppler shift in the received GPS signals.
The foregoing indicates some problem with the GPS data.
@Fdp718x does the trajectory indicated by the green arrows show the final moments of the flight?
View attachment 157890
In the above chart the black plot is the
Mini 2 tilt. It indicates that tilt was constant even though the horizontal speed was increasing. A stuck or broken gyro could have caused this. And, there is this from the eventLog
376.4 : Gyroscope initialization failed. Restart aircraft (Code: 30045).
Can you retrieve the .DAT?