I have had successful landings with the landing guidance, however, this landing I have screencapped and the landing immediately prior to it, the AI is getting stuck trying to course correct. Right now, it shows an error in the hundreds of meters or so, though it varies wildly (100-400m) but the problem is that it was too busy course correcting to bother to slow down. This landing is still in progress, as of writing, but the previous landing with this issue, the target difference was measured in millimeters much of the time, and no more than 5m, but the AI was still attempting to course correct by 0.0m/s when it smacked into Mun at full speed.

Suggestions to fix: Lower tolerances for course, allow higher errors in landing prediction, and/or input an override onto the course, such that when it's time for the deceleration burn, any course corrections necessary are forgotten about. Missing by 100 meters is better than smacking into the moon full speed, this should be obvious, but the AI does not think so.

As a temporary way to get around this problem, it's possible to switch between "land at target" and "land somewhere" often enough that when you've got the place you want to land targeted closely enough, "landing somewhere" will get you to touch down slowly instead of a high speed rendezvous.

Had this problem too, but I use the landing prediction and land my crafts manually

Another dup of #1052

this is mainly cause by off COM RCS or off COM SAS. as it trient to move the craft in the correct direction to burn it changes it direction due to having more weight at one end or the RCS is pushing it around in space not just changing its orientation. simple rule is keep the orientation controls close to the COM and turn RCS off