Ksp Gravity Assist Calculator

Estimate flyby turning angle, post-encounter heliocentric speed, and velocity change leverage for Kerbal Space Program missions. This tool uses a patched-conic style gravity assist approximation based on selected body, hyperbolic excess speed, periapsis altitude, and incoming approach geometry.

Calculator Inputs

How a KSP Gravity Assist Calculator Helps You Build Better Interplanetary Missions

A KSP gravity assist calculator is one of the most useful planning tools for players who want to move beyond simple transfer windows and start flying efficient, elegant interplanetary trajectories. In Kerbal Space Program, a gravity assist lets you pass close to a moon or planet and leave with your trajectory rotated by that body’s gravity well. The spacecraft does not gain energy from nowhere. Instead, it exchanges momentum with the flyby body and changes its heliocentric path in a way that can either increase speed, reduce speed, or dramatically alter inclination and encounter timing.

For many players, gravity assists feel mysterious because the in-game map can make them look simple while the underlying orbital mechanics are anything but simple. A calculator closes that gap. It estimates how much your incoming hyperbolic excess velocity can be bent, how strong the turn angle becomes at different periapsis altitudes, and how that bend translates into a faster or slower post-encounter trajectory around Kerbol. That is exactly what this page is designed to do. It does not replace full numerical mission design software, but it gives a highly practical patched-conics estimate that is extremely useful for gameplay planning.

The basic idea is straightforward. When you enter a sphere of influence, your ship has an incoming excess speed relative to the target body, commonly written as v∞. The body’s gravity bends that path into a hyperbola. The closer your periapsis, the more severe the bending. Once the ship leaves the sphere of influence, it still has roughly the same v∞ magnitude relative to that body, but its direction has changed. Since the planet itself is moving around Kerbol, rotating that relative vector can produce a large difference in your solar orbit. This is why Jool or Eve flybys can be so powerful in KSP mission design.

What the Calculator Actually Computes

This calculator uses a standard hyperbolic flyby approximation. For a selected body, it looks up gravitational parameter, equatorial radius, and orbital speed around Kerbol. From your chosen periapsis altitude, it computes periapsis radius. From periapsis radius and incoming excess speed, it estimates the hyperbolic eccentricity with the relation:

e = 1 + (r_p × v∞²) / μ

turn angle = 2 × asin(1 / e)

That turn angle is then applied to your incoming angle relative to the planet’s orbital motion. If you choose a prograde-boosting bend, the code rotates the vector to maximize heliocentric speed gain. If you choose a retrograde bend, it rotates it to reduce your heliocentric speed. This lets you quickly compare whether a body is useful for speeding outward, diving inward, or reshaping a future encounter chain.

In practical gameplay terms, the most important variables are:

• Flyby body: Bodies with higher μ and higher orbital speeds are usually better assist candidates.
• Incoming v∞: Lower relative speed is easier to bend sharply, but faster arrivals can still deliver huge results if the geometry is favorable.
• Periapsis altitude: Lower altitude increases bending. Atmospheric worlds need extra care.
• Approach angle: The same planet can either add energy or remove it depending on which side you pass.
• Bend direction: A prograde side pass tends to increase heliocentric speed. A retrograde side pass tends to reduce it.

KSP Body Statistics That Matter for Gravity Assists

The following table summarizes several commonly used KSP gravity assist bodies and the numbers players care about most. These values are standard stock-system figures used in patched-conic planning. Orbital speed is approximated from Kerbol-centered circular velocity and is sufficient for mission estimation.

Body	Radius (km)	Gravitational Parameter μ (m³/s²)	Approx. Orbital Speed Around Kerbol (m/s)	Atmosphere	Gravity Assist Use Case
Moho	250	1.6861 × 10^11	9287	No	Hard target, but useful for deep-solar energy shaping and inward mission chains.
Eve	700	8.1717 × 10^12	8547	Yes	One of the strongest inner-system assists for major energy changes.
Kerbin	600	3.5316 × 10^12	9284	Yes	Common departure and return assist body; useful for resonance chains and Mun-Minmus setup.
Duna	320	3.0136 × 10^11	7263	Yes	Moderate assist strength, often more valuable for timing and plane changes than brute energy gain.
Dres	138	2.1484 × 10^10	6031	No	Limited assist strength; niche option for route shaping.
Jool	6000	2.8253 × 10^14	4126	Yes	The premier outer-system slingshot body for deep missions, moon tours, and dramatic capture reduction.
Eeloo	210	7.4411 × 10^10	2414	No	Weak as an assist source, but important as a destination where pre-arrival shaping matters.

Why Jool and Eve Are So Popular

If you ask veteran players which gravity assist bodies matter most, Jool and Eve appear near the top every time. Jool has an enormous μ, so it can bend high-speed arrivals very effectively. Even though its orbital speed around Kerbol is lower than Kerbin’s or Eve’s, the combination of massive gravity and access to multiple moons creates incredible route flexibility. You can use Jool itself to reshape a solar orbit, then chain moon assists with Tylo, Laythe, Vall, or Bop to reduce capture cost or set up a moon tour.

Eve, by contrast, is valuable because it combines strong gravity with very high orbital speed around Kerbol. In practical terms, that means a well-planned Eve flyby can add or subtract a lot of heliocentric energy. Eve is often used for missions heading inward, for advanced routes toward Moho, or for creative gravity-assist ladders that reduce propellant requirements.

Typical strategic comparison

Scenario	Best Body	Reason	Common Risk
Boosting to outer planets with one major assist	Eve or Kerbin	High orbital speed can add strong outward energy if geometry is favorable.	Wrong-side pass lowers energy instead of raising it.
Large post-encounter trajectory rotation in the outer system	Jool	Huge μ supports significant turn angles even at relatively high arrival speeds.	Atmospheric or moon-interference planning errors.
Reducing solar orbital energy for inner-system missions	Eve	Strong gravity plus high orbital velocity makes inward braking assists effective.	Aerothermal danger if periapsis is set too low.
Fine tuning encounter timing after departure from Kerbin	Kerbin	Accessible resonance maneuvers and repeated returns are easier to test and iterate.	Overcomplicating mission design when a simple burn would suffice.

How to Read the Output Correctly

The most visible number is the turn angle. This tells you how many degrees your incoming excess velocity vector is rotated by the flyby. Bigger is usually better if your goal is dramatic trajectory shaping, but bigger is not automatically optimal. A mission to Moho may need a specific reduction in heliocentric speed, not just the largest possible bend. Likewise, a Jool capture chain might prioritize moon alignment and arrival timing over a single maximum-deflection pass.

The outgoing heliocentric speed tells you what happens after your v∞ vector is recombined with the planet’s own orbital motion around Kerbol. This is the number most players care about when they say a flyby gave them free delta-v. Technically, the spacecraft exchanged momentum with the flyby body, but for planning purposes the result feels like free propulsive leverage.

The approximate speed change compares post-encounter heliocentric speed to pre-encounter heliocentric speed using the selected geometry. It is a compact way to judge whether your flyby gained energy or dumped it. A positive value indicates a prograde-style boost. A negative value indicates a braking effect.

The eccentricity is useful as a sanity check. Values just above 1 mean a very strongly bent hyperbola, especially at low v∞ and low periapsis. Larger eccentricity means a shallower flyby with less turning power.

Best Practices for Planning KSP Gravity Assists

1. Start with mission intent. Decide whether you want more heliocentric speed, less heliocentric speed, a plane change, or only encounter timing adjustment.
2. Estimate v∞ honestly. If your arrival speed is too optimistic in the calculator, your real mission will bend less than expected.
3. Watch atmospheric worlds. Eve, Kerbin, Duna, and Jool all require safe periapsis margins. The mathematically strongest periapsis may be physically impossible.
4. Use charts to compare sensitivity. If small periapsis changes create large turn-angle differences, your mission may need tighter correction planning.
5. Remember moon assists. Around Jool in particular, the giant planet is only part of the story. Moon chains often produce the most efficient tours.
6. Check transfer timing separately. A powerful theoretical flyby is worthless if the planetary alignment is inaccessible at launch.

Common Mistakes Players Make

• Assuming lower periapsis is always better without checking atmosphere or terrain.
• Confusing body-relative speed with heliocentric speed.
• Trying to maximize turn angle when the real goal is only modest energy adjustment.
• Ignoring approach angle and then wondering why the flyby removed speed instead of adding it.
• Using a gravity assist when a small corrective burn would be simpler and safer.

Real-World Gravity Assist References and Why They Matter to KSP Players

Although KSP simplifies the full solar-system problem into patched conics and a smaller set of bodies, the strategic thinking is very similar to real astrodynamics. NASA and university resources are excellent for understanding why a slingshot works, how vector addition changes energy, and why flyby geometry matters more than intuition suggests. If you want to go deeper, these authoritative references are worth reading:

• NASA Basics of Space Flight Primer
• NASA Solar System Exploration: Gravity Assist Overview
• MIT educational gravity assist notes

When to Use a Calculator Instead of Eyeballing the Map

Eyeballing works for basic transfer burns and broad encounter targets, but gravity assists are fundamentally vector problems. Small differences in arrival angle or periapsis can create surprisingly large downstream consequences. A calculator is especially helpful when:

• You are deciding whether Eve or Kerbin is the better first assist.
• You need to know if a Jool arrival can be bent enough to set up a moon tour.
• You are planning an inward mission where reducing solar speed is more important than increasing it.
• You want to compare multiple periapsis options before committing to a dangerous atmospheric pass.

Final Takeaway

A KSP gravity assist calculator turns a complicated orbital mechanics concept into a usable mission-planning workflow. By entering body, approach speed, periapsis altitude, and geometry, you can quickly estimate whether an encounter is likely to help, hurt, or simply reshape your route. The most efficient KSP missions are often not the ones with the biggest engines. They are the ones where the pilot uses planetary motion as part of the propulsion system. Learn the geometry, compare bodies intelligently, and use calculated flybys to turn difficult missions into surprisingly elegant ones.