Kerbal Space Program Codexery

Specific Impulse (Isp)

The one number that decides whether your Kerbal reaches orbit or becomes very expensive space debris.

Specific Impulse (Isp) is the core efficiency metric for every rocket engine in Kerbal Space Program. Expressed in seconds, it quantifies how long one kilogram of propellant can sustain one kilogram of thrust, making it the single most important number a Kerbal engineer must internalize when designing a vehicle. Whether you are lifting a lander off the Kerbin surface or coasting between Jool and Eeloo, Isp determines how much delta-v your propellant budget can actually deliver.

In the KSP universe, Isp sits at the heart of the Tsiolkovsky rocket equation and governs the fundamental trade-off every Kerbal pilot faces: high-thrust, low-efficiency engines that can punch you out of the atmosphere, versus low-thrust, high-efficiency drives that can carry you across the system on a sliver of fuel. Mastering this trade-off is what separates a successful mission from a very expensive piece of orbital litter.

Measures
Propellant efficiency — thrust produced per unit of propellant mass flow
Unit
Seconds (s)
Governing equation
Δv = Isp × g₀ × ln(m₀ / m₁)
Typical KSP range
≈ 300 s (solid boosters) to ≈ 3,000 s (xenon ion drives)
Key constant
g₀ = 9.81 m/s² (Kerbin standard gravity)
Primary trade-off
Higher Isp generally pairs with lower thrust output

Lore & Background

At the Kerbal Space Center, engine design is a sacred discipline. The first-generation solid boosters were brute-force marvels: enormous thrust, modest Isp, and a reliability that earned them a place on every early launch vehicle. The liquid-fuel engines that followed — the Terriers and their siblings — struck a practical middle ground that let Kerbals reach orbit without needing a mountain of propellant tanks strapped to the airframe. Each new engine class pushed the Isp envelope further, and with it came a new philosophy of mission design.

The arrival of nuclear thermal engines changed the conversation entirely. With Isp values roughly double those of the best liquid engines, a nuclear stage could carry a crewed lander to the Mun and back on propellant that a liquid stack would have burned up in the first few minutes of ascent. Engineers at KSC began to speak of "Isp matching" as a core design principle: use the right engine for the right phase of flight, and let the staging sequence peel away dead weight at exactly the moment it stops helping.

Then came the xenon ion drives, and the KSC design culture split into two camps. Purists argued that no Kerbal should ever trust a drive that could be stopped by a stiff breeze. Pragmatists pointed out that, given enough time and a sufficiently thin propellant stream, an ion engine could deliver more total delta-v than any chemical stack the KSC had ever built. Both camps were right, and the resulting hybrid architectures — chemical boosters for the first few minutes, ion drives for the rest of the trip — became the hallmark of every serious interplanetary mission the KSC has attempted since.

In Their Own Story

The xenon drive hummed at a frequency Jaq could feel in her teeth. Outside the small observation port, the pale disc of Duna hung in the black, and the fuel gauge ticked down by fractions of a percent every time she eased the throttle. Three hours. Three hours of that whisper-thin thrust, and the transfer window would close, and she would be orbiting a rust-colored rock with no way home.

She pressed her thumb against the glass. Back on Kerbin, the launch had been a violent, glorious thing — SRBs screaming, the Terrier shaking the whole stack until her coffee bag exploded against the ceiling. That was the low-Isp world: fast, loud, finite. Now, in the quiet of the outer system, the ion drive was doing what no chemical engine could — stretching a few kilograms of xenon into a delta-v that would have required a tank the size of her cabin.

"KSC, Jaq. Burn is at sixty percent. I can see the caldera from here." A pause. "It's… smaller than the maps say."

She eased the throttle another notch. The hum deepened. The fuel gauge ticked. And Duna, patient and red, waited for her to arrive.

Reader's Guide

Rule: Isp is a fixed property of each engine in KSP. It does not change with altitude, atmospheric density, or throttle setting. Your delta-v budget is simply Isp × 9.81 × ln(mass ratio), and that is the whole conversation. If your math says you need 3,200 m/s and your stack delivers 2,800 m/s, you will not make orbit. No amount of piloting skill fixes a fuel deficit.

Why it matters in practice: Isp is the multiplier on everything. A 345 s Terrier and a 3,000 s xenon drive carrying the same propellant mass differ by nearly a factor of ten in delivered delta-v. Choosing the wrong engine for a mission phase is the single most common cause of failed launches and stranded landers.

Common failure modes: (1) Launching a heavy stack on an ion drive — you will never clear the atmosphere. (2) Using a low-Isp chemical engine for a long interplanetary transfer — you will run dry halfway. (3) Forgetting that structural mass and empty tank mass count against your mass ratio, silently eating your delta-v.

Pro tips: Match Isp to the phase. High thrust / low Isp for ascent. Moderate Isp for orbital insertion and interplanetary transfers. Maximum Isp for the final approach and long cruises. Stage aggressively — every kilogram of dead engine and empty tank you jettison at the right moment is pure delta-v gained. And always compute your total delta-v budget before you build, not after you've already welded the tanks on.

Did You Know?

More in Game Mechanics & Physics

Elsewhere in the Kerbal Space Program universe

Spotted an error? Know more?

This is a living reference — every entry is fact-audited, and reader corrections feed straight into our audit queue. Suggest an edit · See this site's audit record

Comments

Loading…
Open in the interactive codex →