Structural Stress & Part Breakage

Lore & Background

In the early days of the K.A.S.L. program, Kerbal engineers discovered that a rocket's equations of motion were only half the battle. The other half lived in the joints. A part that could accelerate a payload to orbit could still snap in two if the force at its connection point exceeded what its structural rating allowed. The structural stress model formalized this: every joint in a vessel is continuously evaluated against the part's gMax, and the moment the load crosses the threshold, the part is severed, tumbles, and is gone. What was once a theoretical concern in the design office became a very visible, very expensive cloud of spinning debris over the launch pad.

The practical consequence reshaped how Kerbals think about their vehicles. Tanks, which are large, relatively light, and often mounted at the end of a long stack, became the most vulnerable components. Engineers learned to place structural members and engines closer to the center of mass, to avoid cantilevered wings that whip under aerodynamic load, and to sequence staging so that the heaviest loads are shed before the next burn pushes the remaining structure past its limit. Reentry profiles were redesigned to keep peak dynamic pressure within the fairing's and the vessel's structural envelope, and landing approaches were tuned so that touchdown forces stayed below the strut and tank ratings.

Over time, the stress model became a kind of silent mentor. It never lectures; it simply lets your carefully balanced three-stage rocket shed its middle section at 3.8 g, three seconds before apoapsis, and leaves you staring at a cloud of orange and white fragments while your command pod drifts slowly toward reentry on a trajectory you never intended. The Kerbal who respects the joints builds rockets that survive. The one who doesn't gets a very photogenic debris field.

In Their Own Story

The launch window was in ninety seconds and Junior Engineer Vrelka was still arguing with the structural report. "You want to put the oxidizer tank ABOVE the engine cluster? At 4.2 g?" she said, tapping the gMax column on her tablet. The senior Kerbal, a weathered pilot named Dorn, just shrugged and pointed at the timeline. "We don't have time to redesign the stack, Vrelka. Trust the math."

They trusted the math. The math said 4.1 g peak. The structural report said the tank's rating was 4.0 g. A margin of zero. The wind at the pad was gusting.

Liftoff was clean. The first two minutes were textbook. Then the air thickened, the dynamic pressure climbed, and the gust that Dorn had shrug-off shoved the stack two degrees off-axis. The force at the tank's lower joint ticked up. 4.01. 4.03.

There was no sound. One moment the tank was there, a long white cylinder catching the sunlight. The next it was a separate object, spinning slowly, its contents venting in a thin white plume that caught the light like a comet's tail. Dorn's hands were already on the abort handles. Vrelka was already pulling the backup trajectory.

They made it to orbit. Barely. And in the debrief, Dorn said nothing for a long time, then: "Next time, we trust the math AND the wind."

Vrelka wrote that in her notebook. She underlined it twice.

Reader's Guide

The rule is simple to state and brutal to live with: every part in your vessel has a structural rating (gMax), and the moment the force at any joint exceeds what that rating allows, the part breaks free and becomes debris. The force comes from acceleration, aerodynamic drag, collision impulses, and landing loads. In practice, this means your rocket is only as strong as its weakest joint, and the weakest joint is almost always a tank or a wing mounted far from the center of mass.

Why it matters: a part that breaks at 3 g on ascent is a mission-killer. A part that breaks during reentry can puncture your command pod. A part that snaps on landing can take your wheels with it. The failure is not gradual; it is instantaneous, and the debris it creates can strike other parts in a chain reaction.

Common failure modes: tanks separating during a high-G burn (especially the topmost tank in a stack), wings or fins shearing off under aerodynamic load in dense atmosphere, and struts or legs buckling on a hard landing. Long, thin, cantilevered structures are the worst offenders because the lever arm multiplies the force at the root joint.

Pro tips: Keep heavy parts close to the center of mass. Use structural members and engines as internal load-bearing elements rather than bolting a tank to the very tip of a long stack. Fairings are not just for looks; they reduce the aerodynamic load on exposed parts. When designing for reentry, keep peak dynamic pressure below your most vulnerable part's rating. For landings, approach with as little residual velocity as possible and let the struts do their job within their rated load. And always check the gMax column in the VAB before you commit to a configuration. The math is your friend. The wind is not.

Did You Know?

• A part that breaks in flight does not simply vanish; it becomes a dynamic physics object that can tumble, collide with other parts, and even strike the ground and bounce, creating a debris field that persists until the s
• The structural rating (gMax) is a per-part property visible in the VAB and SPH, meaning two identical-looking tanks from different part families can have different break thresholds, and the choice of which tank you use i
• Aerodynamic drag is a major contributor to structural stress, which is why a rocket that flies fine in vacuum can shed parts the moment it enters a thick atmosphere at high speed, even if its thrust-to-weight ratio is pe
• The structural stress model is what makes staging order a structural problem, not just a mass problem: shedding a heavy upper stage before the next burn can be the difference between a 3.5 g load (safe) and a 4.5 g load