Users have reported that during significant network processing lag planes will respond to inputs far in excess from what they are seeing on their screens. This appears to be an issue from the control system, where the press-release button presses aren't making it to the server as fast as the clients are seeing the vehicles move. This is due to the client taking longer to process the tick due to chewing on packets.

Ideal fix would be to find some way to timestamp the packets, or re-do packets to not allow this to happen in the first place by doing a tick-based movement rather than a on-off movement. This would cause a significant increase in network traffic, but would be easier to resolve than trying to back out the extra movement on the server-side.

Cancelling this, as even though it will make inputs go crazy, it will also cause vehicles that are already in motion to continue that motion. So even if you're nearly going to hit a mountain, and pull up, you'll either pull up and stall from input lag, or fail to pull up due to your inputs not making it to the server. The root cause is low TPS, and that's something the server owners should be handling and taking care of, not something MTS should be trying to put hacks in to smooth over.