7 Famous Disasters Caused by Unit Conversion Errors

Units are not just labels. They are the language that turns a number into a physical fact. When that language breaks down — when one team speaks metric and another speaks imperial, or when the word “mile” means two different things to two different people — the consequences can be catastrophic. The following disasters are not historical curiosities. They are case studies in what happens when measurement errors go undetected, and they remain required reading in engineering programs around the world.

1. Mars Climate Orbiter (1999) — $327.6 Million Lost in Translation

On September 23, 1999, NASA lost the Mars Climate Orbiter as it attempted to enter orbit around Mars. The spacecraft had traveled 669 million kilometers over 10 months, but it arrived at the wrong approach angle and was destroyed by the Martian atmosphere. The cause: a unit mismatch.

Lockheed Martin's navigation software output thruster performance data in pound-force seconds (an imperial unit). NASA's navigation system expected those values in newton-seconds (the SI metric equivalent). One pound-force second equals approximately 4.45 newton-seconds, so the spacecraft was effectively being steered with a systematic error baked into every single course correction for the entire 10-month journey.

The error was invisible because both numbers were plausible-looking. No alarm sounded. No sanity check caught it. The full mission cost $327.6 million. NASA's accident review board later noted that the failure to mandate SI units across all project contractors was a systemic process failure, not merely a software bug.

2. The Gimli Glider — Air Canada Flight 143 (1983)

On July 23, 1983, a Boeing 767 departed Montreal with 69 people aboard. Partway through the flight at 41,000 feet over Gimli, Manitoba, both engines flamed out. The aircraft had run completely out of fuel.

Canada had recently converted to metric. The ground crew calculated the required fuel load using the fuel density in pounds per liter (a hybrid of imperial and metric) instead of the correct kilograms per liter. A kilogram is approximately 2.2 times heavier than a pound, so the aircraft departed with roughly half the fuel it needed.

Captain Bob Pearson, who had glider experience, executed an emergency glide and used a technique called a forward slip — an aggressive cross-control maneuver rarely used on large jets — to control the descent rate without power. He landed the 767 on a closed airstrip at Gimli Industrial Park that happened to be hosting a drag racing event at the time. There were minor injuries on the ground; all 69 passengers and crew survived. The aircraft, dubbed the “Gimli Glider,” was repaired and flew commercially until 2008.

3. The Vasa Warship (1628) — Two Different Feet, One Doomed Ship

The Swedish warship Vasa was the most powerful warship in the Baltic when it set sail from Stockholm on August 10, 1628. It sank 1,300 meters later, in full view of the watching crowds, taking 30 or more sailors with it.

When the wreck was raised in 1961 and studied by archaeologists, they made a remarkable discovery: the measuring rulers found aboard showed that the two construction teams had used different units. The port side was built using Swedish feet (12 inches per foot), while the starboard side used Amsterdam feet (11 inches per foot). The two sides of the hull were physically different sizes. This asymmetry made the ship dangerously top-heavy and unstable — a fatal flaw that no amount of ballast could correct.

The Vasa remains one of the best-preserved 17th-century warships in the world and is on permanent display in Stockholm. It is a 400-year-old demonstration of what happens when two teams building the same structure use different definitions of the same word.

4. The Laufenburg Bridge (2003) — 54 cm Off, by Design

The Laufenburg Bridge was built simultaneously from both banks of the Rhine River, connecting Germany and Switzerland. When the two halves met in the middle, they were 54 centimeters off.

Both countries use sea level as their elevation reference datum — but they use different sea levels. Germany references the North Sea; Switzerland references the Mediterranean. These two sea levels differ by exactly 27 cm, a well-known discrepancy. The error was doubled to 54 cm because the survey teams on each side independently applied the offset, and they applied it in opposite directions — each correcting for the known difference, but correcting the wrong way relative to the other team.

The bridge was completed, but one side had to be built slightly higher than originally designed to accommodate the mismatch. The error cost an estimated €25,000 in additional construction work. Unlike most entries on this list, the Laufenburg case was not a simple conversion error but a reference frame failure — both teams were technically correct within their own system and wrong in a shared context.

5. Columbus and the Wrong-Sized Earth (1492)

Christopher Columbus was not a fool, and he was not sailing to prove the Earth was round — educated Europeans had known that for centuries. What he got badly wrong was the size of the Earth, and the error was fundamentally a unit conversion mistake.

Columbus based his calculations on the work of Arab geographer al-Farghani, who estimated Earth's circumference using Arabic miles of approximately 1,830 meters each. Columbus read those figures but calculated distances using Roman miles of approximately 1,480 meters. He used al-Farghani's larger-Earth number but the smaller Roman mile for scale — making Asia appear roughly 25% closer than it actually was.

Columbus estimated Earth's circumference at approximately 30,000 km. The actual value is 40,075 km — he was off by more than a third. He died in 1506 still believing he had reached the outskirts of Asia, never acknowledging that he had found an entirely unknown pair of continents. The Americas exist on European maps because Columbus got his unit conversion wrong.

For accurate distance conversions, see our meters to feet converter.

6. Korean Air Cargo Flight 6316 (1999) — Meters vs. Feet at Altitude

On April 15, 1999, a Boeing 747 cargo aircraft operated by Korean Air crashed on approach to Bishkek, Kyrgyzstan, killing all three crew members. The investigation found that air traffic control had issued altitude instructions in meters, while the crew was monitoring their altitude using an altimeter set to read in feet.

The crew flew approximately 900 meters (2,950 feet) lower than the intended approach altitude. At that reduced altitude, the aircraft struck a hill near the airport during the descent. The post-accident investigation noted that the mixed-unit environment of post-Soviet airspace — where controllers used meters and many international aircraft used feet — created a persistent ambiguity that contributed to multiple incidents in the region during that period.

The conversion between meters and feet is one of the most common in aviation and engineering. Use our meters to feet converter or our weight converter for cross-system calculations.

Summary Table

The Pattern: Why These Errors Happen

Every disaster on this list shares a structural cause: two systems — two teams, two software modules, two construction crews, two air traffic environments — exchanged a number without agreeing on what that number meant. In every case, the number itself looked reasonable. No alarm fired. No human noticed the discrepancy in time.

Unit conversion errors are especially dangerous because they produce outputs that are wrong in a systematic, consistent way. A random error might trigger a sanity check; a systematic one blends in. The Mars Climate Orbiter's trajectory was off by a small, plausible-looking amount on any given day. It only became fatal at arrival.

The fix is not complicated — it is disciplined. Define units at the interface. Label every value. Check your conversions with a trusted tool. Use our meters to feet converter, weight converter, or temperature converter whenever the stakes are higher than a rough estimate.