Terminal Velocity

Lore & Background

In the early days of the KSC, junior flight controllers would watch a test rocket tumble back from a failed ascent and marvel at how it simply… stopped falling faster. The numbers on the telemetry board would climb, climb, then flatten into a stubborn plateau. Senior engineers called it 'the air's ceiling,' and it became the first lesson every new pilot learned: you cannot outrun the atmosphere. The more you push your nose into the wind, the harder the wind pushes back, and eventually the two cancel out. From that day on, every mission plan at the KSC had a line item for terminal velocity, because ignoring it meant watching a perfectly good lander turn into a very expensive meteor.

The Kerbals learned the hard way that terminal velocity is not one number. On Kerbin, with its dense, blue-tinged sky, a bulky cargo lander might plateau around a few hundred meters per second. On Duna, where the thin, rust-colored air offers far less resistance, the same lander would keep accelerating well past that mark before the drag finally caught up. On Eeloo, the haze is so thick that even a streamlined probe reaches its ceiling almost immediately after leaving orbit. Pilots who treated terminal velocity as a constant rather than a local condition found their parachutes shredded or their heat shields glowing cherry-red at altitudes where they expected a gentle drift.

Over the years, the KSC developed a whole vocabulary around it: 'the ceiling,' 'the wall of air,' 'the speed the sky won't let you pass.' Engineers began designing craft with intentional drag cones, deployable panels, and staged parachute sequences specifically to manage where and how that ceiling was met. The lesson etched into every flight manual is the same one the first test pilots learned: the atmosphere is not a void you fall through. It is a medium with a speed limit, and that limit is yours to negotiate, not ignore.

In Their Own Story

The telemetry board flickered green, then amber. Jem's fingers hovered over the parachute deploy switch, knuckles white. Outside the cockpit, Kerbin's sky had gone from the black of orbit to a deep, bruised violet, the horizon a smear of orange where the atmosphere thinned into nothing. The speedometer needle was still climbing—380, 410, 440—each tick a small violence against the frame of the lander.

"Ceiling's at about four-six-zero on this mass," muttered the co-pilot, eyes on the drag readout. The orange cone on the belly had done its job, bloating the cross-section, but the craft was still shedding fuel, still getting lighter, still falling faster than the air could hold it.

Jem exhaled. 455. 458. The needle shuddered, fought the glass, and stopped. Held. The vibration in the frame eased from a roar to a growl. "Ceiling," Jem said, and the word felt like a hand on the shoulder, steadying.

Below, the Kerbal surface was a patchwork of green and blue, impossibly close. The parachute switch waited, patient and red. Jem pressed it.

The jolt was gentle. Almost kind. Like the sky had finally said, *enough, you may rest now."

Reader's Guide

The rule: terminal velocity is the speed at which aerodynamic drag force equals the gravitational force on your craft. In KSP's model, drag scales with the square of velocity, air density, drag coefficient, and cross-sectional area. Once those two forces balance, acceleration drops to zero and your speed plateaus. This is not a hard cap you can't exceed—if you add thrust or lose mass (fuel burn), the equilibrium shifts upward—but it is the speed you will naturally settle into during a passive fall.

Why it matters: every atmospheric landing, reentry, and probe descent is governed by where that plateau lands relative to your craft's structural limits and parachute ratings. If your terminal velocity exceeds a parachute's max deployment speed, the chute bursts. If it exceeds your heat shield's tolerance, you ablate or break apart. If it exceeds your structural load limit, the craft simply comes apart in a shower of parts.

Common failure modes: deploying a parachute while still above its rated speed (the single most common new-pilot crash); designing a lander with too little drag for the target atmosphere, so it slams into the ground at 500 m/s; forgetting that as fuel burns off, mass drops and terminal velocity rises mid-descent; and assuming Kerbin numbers apply to Duna or Eeloo, where the ceiling is radically different.

Pro tips: Add drag cones or deployable panels to raise your cross-sectional area before you need to slow down. Stage your descent—use a retrograde burn to trade velocity for altitude, then let the air do the rest. Check your parachute's max deployment speed in the part inspector and build a margin of at least 20-30 m/s below your expected terminal velocity. On thin-atmosphere worlds, plan for a powered descent rather than relying on drag alone. And always monitor your mass: a half-empty fuel tank means a higher ceiling than a full one, so time your parachute deployment for the lighter, faster phase of the fall.

Did You Know?

• On airless bodies like the Mun or Minmus, there is no terminal velocity at all—objects accelerate under gravity indefinitely until they hit the surface, which is why every Mun landing requires a retrograde engine burn.
• The orange 'drag' part in KSP exists specifically to increase a craft's cross-sectional area, lowering its terminal velocity without adding mass or complexity to the design.
• Because drag scales with the square of velocity, doubling your fall speed quadruples the drag force—and the heating rate—which is why the last 100 m/s of a reentry is disproportionately dangerous.
• Terminal velocity in KSP is recalculated every physics tick, so a craft that sheds fuel, deploys a panel, or changes its angle of attack mid-fall will see its ceiling shift in real time.