Five unit mix-ups that cost real money

1. The orbiter that was not there

In 1999 NASA lost the Mars Climate Orbiter because one team supplied thrust data in pound-force seconds while the navigation software expected newton seconds. The craft entered the atmosphere far too low. Cost: about 125 million dollars, and a permanent lesson about declaring units in interfaces.

2. The suitcase at the gate

A 23 kg allowance is 50.71 lb. Pack to 50.6 lb thinking you have room and the airport scale — which rounds up — puts you over. Excess baggage charges start around 50 dollars a bag.

3. The tin that changed the bake

Swapping a 9-inch tin (22.86 cm) for a 20 cm one cuts the area by nearly a quarter. The batter sits deeper, the middle stays raw while the edges brown, and the recipe gets the blame.

4. The pipe that weeps

BSP and NPT threads engage well enough to feel correct and seal poorly, because the flank angles differ by five degrees. The joint passes the pressure test and drips a fortnight later, behind the plasterboard.

5. The tyre that broke the speedometer

Fitting a tyre with a five per cent larger overall diameter leaves the speedometer reading low by roughly the same margin, and feeds wrong data to the traction control. It also means the odometer under-records, which affects warranty and resale.

The habit that prevents all five

Write the unit next to every number, every time — in spreadsheets, in drawings, in messages. Almost every error above began with a bare number that both parties interpreted confidently and differently.

Two more worth knowing

The Gimli Glider

In 1983 an Air Canada Boeing 767 ran out of fuel at 41,000 feet. The airline was transitioning to metric units, and the fuel load had been calculated using the pounds-per-litre figure from the older fleet instead of the kilograms-per-litre figure the 767 required. The aircraft left with about half the fuel the crew believed it had, and was glided onto a former air-force runway at Gimli, Manitoba. Nobody died, which says more about the crew than about the arithmetic.

The Space Mountain incident

When a Disney ride was rebuilt using drawings that mixed imperial and metric dimensions, the assembled structure did not match its clearances and the installation had to be reworked. It is a smaller story than a lost spacecraft, and a more common one: most unit errors do not make the news, they just quietly consume a fortnight of somebody's schedule.

Why these errors survive review

A bare number looks complete. "Set the pressure to 30" is a sentence that passes a code review, a drawing check and a handover conversation without anyone noticing that one party means psi and the other bar — a factor-of-fifteen difference. Unit errors are invisible precisely because the value looks plausible in both systems.

Three patterns account for most of them:

• Interfaces between teams. Each side is internally consistent; the boundary is not specified.
• Legacy transitions. Old and new documents coexist and look equally authoritative.
• Spreadsheet columns. Headers say "weight" rather than "weight (kg)", and the file outlives everyone's memory of which it was.

Habits that actually prevent them

1. Put the unit in the label, not in your head. Column headers, variable names, axis titles and field labels.
2. Convert once, at the boundary. Pick one internal unit, convert on the way in and on the way out, and never mix inside the system.
3. Sanity-check the magnitude. A person is not 70 pounds and a suitcase is not 23 pounds. Order-of-magnitude checks catch most swaps instantly.
4. Show the working. If a figure is derived, put the formula next to it so a reviewer can see which factor was used.

A quick reference of exact factors

The takeaway

None of these failures needed better mathematics. They needed the unit written next to the number.