I've been using alexmoon's KSP Launch Window Planner to plot transfers from the Mun to Minmus, but the trajectories that I get are quite far off, and I feel like I must be doing something wrong.

What I do is:

  • Create a maneuver node somewhere on my spacecraft's starting orbit, and use Precise Node to set its time to the one from the planner.
  • Copy the Δv values (prograde and normal) from the planner to the maneuver. (Precise Node shows the maneuver's ejection angle at this point.)
  • Adjust the maneuver's time value up or down a bit until the ejection angle shown in Precise Node matches the one in the planner. (The planner's time value can't be exactly right because it's assuming a perfectly-circular, perfectly-equatorial orbit, and reality isn't that perfect. As I understand it, the ejection angle is what really matters.)

This gives me a trajectory that goes out well past Minmus in terms of distance from Kerbin, but it doesn't deviate much from the Mun's orbital plane, and it passes well above or below Minmus's inclined orbit — far enough that I don't get an encounter. The ejection inclination shown in Precise Node is much less (around an order of magnitude) than the one shown in the planner.

I can usually "fix" the trajectory by adding another maneuver node somewhere along the path, with a burn in the normal or anti-normal direction to point it toward Minmus's orbit — basically, a mid-course plane change even though I asked for a ballistic trajectory in the planner — but that shouldn't be necessary. I understand that minor adjustments will be needed since my starting orbit isn't the perfect one that the planner assumes, but having to add a major maneuver seems like a bit much.

I've tried setting the planner to produce a transfer with a mid-course plane change, but haven't had much luck with that either. And the in-game Transfer Window Planner mod (which only seems to support ballistic trajectories) produces the same results as the web-based planner.

I feel like I'm missing some crucial step in translating the results from the planner into a maneuver node. In particular, I'm puzzled that the maneuver node's ejection inclination is always so much less than the value shown in the planner — even though (I think) that's determined mainly by the normal Δv, which I copied exactly from the planner, and my starting orbit is very close (0.06°) to equatorial.

Can someone enlighten me?

Here's an example:

Misaligned orbits Misaligned orbits, top view Misaligned orbits, overview

I asked the planner for a ballistic transfer from Mun to Minmus starting on year 1, day 356, with an initial orbit of 104km. The key details of what it gives me are:

  • Departure: year 1, day 356 at 00:00:00 (UT: 7668000)
  • Ejection Δv: 211 (prograde 196.0, normal -78.2)
  • Ejection angle: 222° to prograde
  • Ejection inclination: -6.76°

To turn this into a maneuver, I put the 7668000 time and 196.0 and -78.2 Δv values into Precise Node, then adjusted the time back a little to 7666100 (a difference of about 32 minutes) to get the ejection angle in Precise Node close to 42° to retrograde (equivalent to 222° to prograde).

But the ejection inclination that Precise Node shows for this maneuver is 1.24° north — very different from the -6.76° shown in the planner — and you can see that the trajectory puts me way above Minmus's orbit at the closest approach. It goes out "far enough" to get there, but the plane change is completely wrong.

My spacecraft here is starting in an equatorial orbit (0.05106° inclination) around Mun, with apoapsis at 107km and periapsis at 101km (not perfectly circular, but that shouldn't affect the inclination change much).

  • A picture would help a lot for determining if you're doing something wrong.
    – MBraedley
    Commented Sep 12, 2015 at 20:25
  • @MBraedley, I updated the question with an example and screenshots.
    – Wyzard
    Commented Sep 12, 2015 at 22:31
  • Those are good, but what I was really looking for was the the entire planned trajectory, with some detail on the maneuver node specifically. On the other hand, it does seem that it is getting you close to an encounter. These tools aren't perfect, either, so the fact that it's getting you pretty close is a good thing. My opinion is that you're always going to need a little manual adjustment.
    – MBraedley
    Commented Sep 12, 2015 at 22:38
  • It's just coincidence that this one is close because the trajectory takes me near the AN marker. Usually I don't even get the close-approach markers. I can post more images, but a full screenshot would be unwieldy.
    – Wyzard
    Commented Sep 12, 2015 at 22:41
  • @MBraedley, I added another image that includes the Mun escape portion of the maneuver. If you trace a line leftward from the word "Prograde" (yellow) in the Precise Node window, the spot where you cross the purple path is about where the escape occurs.
    – Wyzard
    Commented Sep 12, 2015 at 22:52

1 Answer 1


The time given in launch window planner is completely orientational - definitely not to be used as the precise departure moment. You need to fine-tune the time for the exact departure angle and inclination.

The window planner has no clue about your initial/current argument of periapsis, therefore it can't suggest the precise moment to start the burn - that moment completely depends on your current position in your current sol's orbit.

Imagine you launch two probes into the same orbit, exactly half an orbit apart. When one flies over the dusk terminator, the other crosses the dawn line. Since the orbits and the destination are identical, the window planner will give both exactly the same departure date and delta-V components. But at the moment of the optimal burn they will be on two opposite sides of the planet, flying in opposite directions - how would you expect both, performing exactly the same burn relative to their current speeds, to end in the same place if they depart in two opposite directions?

What you do instead, you set the burn values, set the time to have roughly the right departure moment, and then adjust the precise burn moment to have the desired ejection angle and ejection inclination values. The departure time will be off relative to the "optimal" but that's a relatively small error which you should fix by a mid-course correction.

(if you desire to avoid mid-course correction, can perform a very precise, high-thrust burn, and want to arrive precisely at the target, you may do the above, note down the time when the burn should occur, convert the seconds back to date, find the new point on the graph, note down the new departure angles, fine tune the time and speed for the new values... repeat as necessary iteratively increasing precision.)

  • I already do adjust the maneuver time to get the correct ejection angle. But AFAIK, the ejection inclination isn't really determined by the maneuver time; it's determined by the maneuver's normal Δv component. That's why I'm confused that using the planner's Δv gives me an ejection inclination that's very different from the planner's, regardless of the time when I do the maneuver.
    – Wyzard
    Commented Sep 23, 2015 at 5:59
  • 1
    I'm not sure why that inclination error happens, but I'm afraid the original problem may come from Mun's high orbital velocity. "(a difference of about 32 minutes)" - with orbital period of 6 days, the 32 minutes of delay would move the intersect just about as far from AN as in the picture.
    – SF.
    Commented Sep 23, 2015 at 6:27

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .