Propellant Management (Fuel/Oxidizer)

Lore & Background

In the workshops of the K.A.P. (Kerbal Academy of Propulsion), junior engineers learn that a rocket is only as good as its propellant bookkeeping. The game's designers made a deliberate choice to strip away the bewildering chemistry of real liquid propellants—RP-1, LOX, hypergols—and replace them with two intuitive, colour-coded resources. Fuel is the 'burnable' half; Oxidizer is the 'oxygen' half. Together they let a Kerbal engineer think in simple ratios rather than molecular equations, yet the consequence of a mismatch is just as fatal: an engine that sputters and dies because one tank emptied a few seconds before the other.

This simplification has shaped the culture of Kerbal spaceflight. Veterans speak of 'propellant planning' the way a sailor speaks of tide tables. A well-known informal maxim holds that the first thing a pilot checks after a failed ascent is not the engine, not the guidance, but the propellant readout—because in the vast majority of early career-mode disasters, the answer is 'I ran out of oxidizer at 3,200 metres.' The Monopropellant system, meanwhile, carries its own quiet lore: RCS thrusters are the spacecraft's last line of attitude control, and a pilot who forgets to budget monopropellant for a deorbit burn learns the hard way that a tumbling vessel in low Kerbin orbit is a very expensive lesson in orbital mechanics.

The Xenon and Solid Fuel resources, though less central, add texture to the design space. Xenon's extraordinarily low thrust but high efficiency makes ion drives a long-game tool, while solid fuel's non-throttleable, non-restartable nature demands that boosters be sized and timed with precision. Together, the five resources form a small but expressive toolkit that lets Kerbal engineers build anything from a clunky lander to a graceful interplanetary probe, always mindful that every kilogram of propellant is a kilogram of mass that must be accelerated.

In Their Own Story

The launch window was in eleven minutes. Juno sat cross-legged on the concrete pad, her green fingers tapping the tablet against her knee, recalculating the oxidizer budget for the third time. The Mk II sat in the wind, its fuel tanks gleaming dully under the overcast Kerbin sky, and the whole thing smelled faintly of hot metal and ambition.

'You're over by four percent,' she muttered, scribbling a correction. 'Four percent of oxidizer. That's… that's roughly two seconds of burn at full throttle.' She looked up at the tower, at the little blinking lights that meant the range was green. Somewhere in the hangar, a junior tech was already loading the RCS monopropellant cart, and the ion-drive xenon canister was still in its crate, waiting for a mission that wasn't this one.

She sealed the tablet, stood, and walked to the base of the booster. The wind pushed her hair into her face. She pressed her palm flat against the cold metal of the fuel tank and felt, or imagined she felt, the faint vibration of the turbopumps already spinning up.

'Come on,' she whispered to the rocket. 'Don't let me down at three thousand metres.'

The countdown voice crackled over the open channel. Ten. Nine. The pad shuddered. And the sky, for one long, roaring second, turned white.

Reader's Guide

Here's the rule, stated plainly: every liquid engine in your vessel has a fixed fuel-to-oxidizer consumption ratio. As long as BOTH resources are available in the connected tank network, the engine burns. The instant either one hits zero, the engine cuts—regardless of how much of the other remains. This is the single most common cause of 'my rocket died at apogee' failures in career mode.

Why it matters in practice: you are not just managing total propellant mass; you are managing two separate pools that must stay in sync. A tank that is 60 % fuel and 40 % oxidizer will leave 20 % of the fuel unburned if the engine ratio is 1:1. That dead mass is pure penalty on your delta-v budget.

Most common failure modes: (1) Sizing tanks to total propellant mass without checking the ratio, leaving one resource stranded. (2) Forgetting that RCS thrusters draw monopropellant from the same vessel, so a long attitude-hold can quietly drain the reserve you needed for a deorbit burn. (3) Stacking tanks in a way that the engine draws from the 'wrong' tank first, creating an unexpected imbalance mid-burn.

Pro tips: Before every launch, open the vessel's resource readout and verify that fuel and oxidizer will deplete within a few seconds of each other. Budget monopropellant separately—treat it as a non-renewable attitude-control reserve. For ion drives, remember xenon is consumed over hours, not seconds, so your tank sizing logic is completely different. And when in doubt, add a small buffer tank of the resource that tends to run out first; a few extra kilograms of oxidizer is far cheaper than a mission lost to a dead engine at 4,000 metres.

Did You Know?

• A liquid engine in KSP will shut down the moment either Fuel or Oxidizer reaches zero, even if the other resource still has hundreds of kilograms left—so a perfectly full tank can still leave you stranded if the split is
• Monopropellant is a completely separate resource from Fuel and Oxidizer; RCS thrusters and small monoprop engines will not 'borrow' from your main liquid-propellant tanks, which is why pilots budget RCS propellant as its
• Xenon, used by ion engines, is consumed at a dramatically lower rate than chemical propellants, meaning a small xenon tank can power a drive for an in-game time far longer than the equivalent chemical burn—trading thrust
• Solid Fuel, used by solid rocket boosters, cannot be throttled or shut down once ignited, making its sizing and ignition timing a critical part of early-ascent propellant planning.