Units: Why Mixing Them Up Can Crash a Spacecraft

Imagine a recipe that says: "Add 2 of sugar." Two what? Two spoons? Two cups? Two whole bags? You would never know if the cake will be tasty or a sticky disaster. A number on its own tells you almost nothing. Engineers learned this lesson the hard way — once, a missing word after a number destroyed an entire spacecraft.

The money analogy

Think about money. If a friend says "I'll give you 100," you would immediately ask: "100 what?" 100 rupees, 100 dollars, and 100 yen are wildly different amounts. The number is the same; the meaning is completely different.

And if you owe someone 100 dollars but pay them 100 yen, you haven't paid about 99% of your debt. That's not a small mistake. That's the whole mistake. Measurements work exactly the same way: the number only means something when you say what kind of "100" it is.

What a unit really is

A unit is the agreed-upon "thing" you are counting. When you say a table is 2 metres long, you mean: take a standard stick called a metre, and the table is as long as 2 of those sticks laid end to end. The unit is the stick. The number tells you how many sticks.

To make sure everyone uses the same sticks, the world agreed on a system called SI units (from the French name Système International). It has a few base units you already know: the metre for length, the kilogram for mass, and the second for time. Other units are built from these. For example, the newton, the SI unit of force, is the push needed to speed up 1 kilogram by 1 metre per second, every second. Holding a medium apple in your hand? That's roughly 1 newton pressing down on your palm.

But not everyone uses SI all the time. In the United States, engineers often work in feet, pounds, and a force unit called the pound-force. One pound-force is about 4.45 newtons. Neither system is "wrong" — they are just different sticks. Trouble starts when one person counts in one stick and another person assumes a different stick.

The day the sticks didn't match

In 1999, NASA sent a spacecraft called the Mars Climate Orbiter to study the weather on Mars. It flew for nine months and about 670 million kilometres — almost perfectly.

To stay on course, the spacecraft fired small thrusters from time to time. One team's software calculated how hard those thrusters pushed and wrote the answer in pound-force units. Another team's software read those numbers and assumed they were in newtons. No one converted between them.

Remember: 1 pound-force is about 4.45 newtons. So every push was actually about 4.45 times bigger than the navigation software believed. Each tiny error nudged the predicted path a little off. After months of nudges, the spacecraft arrived at Mars about 170 kilometres lower than planned — and instead of slipping into orbit, it hit the upper atmosphere and was destroyed. A $125 million machine, lost not because a part broke, but because two computer programs disagreed about which stick they were counting with.

A tiny worked example

Let's see how easy this mistake is to make. Suppose a small thruster pushes with a force of 20 pounds-force, and our navigation computer needs the force in newtons.

The conversion factor — the exchange rate between the two units — is 4.45 newtons per pound-force. So we multiply:

20 pounds-force × 4.45 newtons per pound-force = 89 newtons

Now imagine we forget to convert, and the computer reads "20" as 20 newtons. It now believes the push is 89 ÷ 20 = 4.45 times weaker than it really is. One forgotten multiplication, and every prediction the computer makes from then on is built on a wrong number. That is exactly the kind of slip that doomed the Mars Climate Orbiter.

Notice something important in the arithmetic: the words "pounds-force" cancel out, leaving only "newtons." Engineers call this a dimensional check — writing the units into the math and making sure they cancel correctly. If the leftover unit is wrong, the answer is wrong, no matter how good the numbers look.

How engineers stop unit mistakes

Because one missing conversion can be so costly, engineers have built habits and tools that catch unit slips before they cause damage.

The first habit is the simplest: always write the unit next to the number. Not "the beam carries 500" but "the beam carries 500 newtons." On drawings, in emails, in spreadsheets, in computer code — every number gets its unit, every time. A naked number is treated like an unlabelled bottle in a chemistry lab: you don't trust it, no matter how confident you feel.

The second habit is the dimensional check we met earlier. Before trusting an answer, an engineer traces the units through the whole calculation and confirms they cancel down to the expected result. If a stress calculation somehow ends in "metres per second," something multiplied where it should have divided — and the check catches it even when the digits look perfectly reasonable.

The third defence is teamwork and standards. Companies agree in advance which unit system a project will use, write it on the front page of every document, and review each other's work. Modern engineering software helps too: many programs store units alongside values and refuse to add metres to kilograms. After the Mars Climate Orbiter loss, checks like these were tightened across the space industry — proof that the cheapest fix is the one made before launch, not after.

Where you see this in real life

Unit mix-ups aren't just a space problem. They hide everywhere:

• Airplane fuel. In 1983, a passenger jet in Canada ran out of fuel mid-flight because the fuel load was figured in pounds when the aircraft needed kilograms — it had roughly half the fuel everyone thought. The pilots glided it down safely, and the plane became famous as the "Gimli Glider."
• Medicine doses. Milligrams (mg) and micrograms (mcg) differ by 1000 times. Hospitals train constantly so the two are never swapped.
• Tyre pressure. Pumps may read psi, bar, or kilopascals. 32 psi is about 2.2 bar — put "32" of the wrong one in your tyre and you'll know something's off.
• Buying flooring. Square metres and square feet differ by almost 11 times. Order 50 of the wrong one and your room is mostly bare concrete.
• Weather and ovens. 30 degrees Celsius is a hot summer day; 30 degrees Fahrenheit is below freezing. Same number, opposite wardrobe.

Why engineers care so much

Engineers care about units because machines don't ask follow-up questions. A person hearing "add 2 of sugar" will ask "2 what?" A computer, a pump, or a thruster will just use the number it was given. Every bridge load, bolt torque, and fuel calculation passes through dozens of hands and programs, and the units are the shared language that keeps them all talking about the same physical reality. A single silent mismatch can waste millions — the Mars Climate Orbiter cost about $125 million — or, far worse, put lives at risk. That's why good engineers write the unit next to every single number, every single time, and check that units cancel properly in every calculation. It is the cheapest insurance in all of engineering: it costs nothing but a few extra pen strokes.

Want to see unit conversion in action? Try the free pressure unit converter and other calculators at enggtools.in — and explore more beginner-friendly explainers at enggtools.in/articles.