I see two problems in this log:
First, your transmitter failsafe is repeatedly being triggered. It looks like a bad connection with your RC transmitter. Each time the RC In channel 3 (throttle) drops is a disconnect. Eventually, it completely loses connection as the drone flies away.
This is a problem that you should fix, but it did not cause the fly-away. I think we saw radio problems with one of your earlier flights. Are you using the same transmitter?
The second problem is what caused the drone to fly too high: vibrations.
This is the first part of your flight, when the drone is ascending to 20 meters (24 meters EKF altitude).
In ArduPilot flight logs, you can see what the drone is trying to do by comparing desired versus measured attitude. For example, in this graph, the drone wants to make the red line (measured altitude) follow the green line (desired altitude). You can see that in the first half of the graph, this is ture - the red line follows the green line upwards until it gets to the correct altitude. However, in the second half, you can see that the red line begins to go upwards, even though the green line stays below it. This means that the drone is climbing upwards, even though the flight controller doesn’t want to. This indicates that the flight controller cannot accurately estimate its climb rate.
Climb rate estimation heavily relies on the accelerometers, which can be confused by excessive vibration. Here are your vibration readings:
In general, you want the vibration measurement to be less than 30. Also, the accelerometer clipping VIBE.Clip should never increase in flight. The very high Z vibrations and clipping are certainly the cause of the uncontrolled ascent by the drone.
Try to mount your flight control board to reduce vibration, and make sure that nothing is touching it that could rattle against it, such as loose wires. If you post a picture of your current mount, we might be able to suggest some improvements.