The first flight shows the same problem that happened in the second flight.
It was temporary and the pilot brought the drone down before things got out of control.
This shows the flight data from the 2nd flight better than Airdata:
Upload and view flight logs from your DJI drones
www.phantomhelp.com
There was an issue that caused the flight controller to lose confidence in the GPS data.
It first showed up at 1:44.4 until 2:13.
It came good briefly and started again at 2:16.5.
The drone effectively had no GPS for the rest of the flight (although the flight data contains GPS position data after that point, it is not believable.
A test calculation I did with data later in the flight gave a speed of >100 mph.
The ESC issue Airdata reported was probably due to interpreting bad data rather than a genuine issue.
The pilot had no indication of speed and his distance showing in telemetry was false information.
Height data would have been accurate.
That left the Phantom in atti mode, still controllable but with no horizontal position holding.
It had no brakes and could be blown by the wind.
The pilot left the controls untouched until 2:40.6.
He gave some input with the joysticks throughout the flight until giving up at 9:16.7 with the drone 350 feet up, position unknown.
Because of the problem with GPS data, we have no idea where the drone really was or how fast it was drifting away.
If the Phantom was <1 year old, the data might be sufficient for a warranty claim with DJI.
This incident is quite a difficult one to solve.
I can't be much more help, but it might be a worthy puzzle for
@sar104 to tackle.
He will probably need to see the .dat file from the phone/tablet.
Instructions for finding that are in here:
With the introduction of the Mavic Mini there has been a noticeable uptick in the number of posts requesting help with lost or crashed aircraft. While there is plenty of help and advice available on this forum, and detailed guidance and options on several other websites, I thought that perhaps a...
mavicpilots.com