Famous Unit Conversion Failures
Safety · Last updated: July 2025
Unit conversion errors rarely make headlines until something fails visibly—a lost spacecraft, a plane out of fuel, a patient harmed by a tenfold overdose. Behind each incident is a chain of assumptions: that everyone used the same system, that software converted correctly, or that a handwritten note was unambiguous. Studying these failures helps engineers, healthcare workers, and even home cooks build habits that prevent silent mistakes.
Mars Climate Orbiter (1999)
NASA’s Mars Climate Orbiter was lost during orbital insertion in September 1999 because navigation software produced thrust commands in pound-force seconds (lbf·s) while the spacecraft expected newton seconds (N·s). One team used English units; another assumed metric. Over months of trajectory corrections, the discrepancy accumulated until the probe passed too close to Mars and disintegrated in the atmosphere.
The investigation by NASA’s Mishap Investigation Board cited a “failure to use metric units in the ground software” and broader process issues: inadequate communication between contractors, insufficient verification of interface specifications, and missing end-to-end testing of unit consistency. The mission cost roughly $125 million. The lesson is stark: convert once at system boundaries, label every interface, and test with realistic integrated data.
Air Canada Flight 143 — the Gimli Glider (1983)
On July 23, 1983, Air Canada Flight 143, a Boeing 767, ran out of fuel at 41,000 feet over Manitoba because ground crew miscalculated the fuel load. Canada had recently switched to metric; the aircraft’s fuel gauge was inoperative, so crew relied on manual drip-stick measurements and arithmetic.
The drip-stick tables gave fuel volume in liters, but the airline’s procedures still thought in pounds of fuel. A conversion factor of 1.77 lb/L was used—but that applied to kilograms per liter (actually about 0.8 kg/L for jet fuel), not pounds per liter. The plane took off with less than half the fuel required for the trip. The pilots, both experienced glider pilots, dead-sticked the jet to an abandoned airstrip at Gimli, Manitoba; miraculously, no one died. The incident became a textbook case for metric transition training and for never flying without cross-checking fuel totals against independent calculations.
Medical dosing: pounds vs kilograms
Healthcare has repeated tragedies from confusing mass units in drug dosing. Many pediatric and chemotherapy protocols specify dose per kilogram of body weight. If a clinician enters the patient’s weight in pounds but the software assumes kilograms—or vice versa—the effective dose can be wrong by a factor of about 2.2. In pediatrics, a factor-of-2.2 error can be lethal.
Institute for Safe Medication Practices (ISMP) and similar organizations document cases where heparin, morphine, and other high-risk drugs were administered at many times the intended dose because weight units were mislabeled or free-text orders lacked units. Modern electronic health records often force unit selection, but legacy workflows and mental math still cause harm. The rule for medicine: always write the unit next to the number, and have a second person verify high-risk calculations.
Other engineering and construction cases
Unit confusion appears in civil engineering too. The Laufenburg bridge between Germany and Switzerland was built with mismatched elevation references in the 2000s because one side used a North Sea datum and the other a different vertical reference—leading to a 54 cm height mismatch at the abutment. While not strictly a unit conversion error, it illustrates how unlabeled reference systems cause expensive rework.
In software, the Mars Rover Spirit experienced a flash-memory issue partly traced to confusion between metric and English units in early development tools—less dramatic than the Climate Orbiter but a reminder that embedded systems inherit human assumptions. Pharmaceutical manufacturing has seen batch rejections when bulk ingredients were weighed in ounces instead of grams on imported raw-material labels.
Patterns across failures
| Pattern | Example | Prevention |
|---|---|---|
| Silent unit mismatch at interfaces | Mars Climate Orbiter | Contract specs with explicit SI; integration tests |
| Wrong conversion factor | Gimli Glider | Independent fuel calculation; metric training |
| Missing unit on a number | Medical overdoses | Force units in software; read-back protocols |
| Similar names, different quantities | US vs UK gallons in recipes | Write “US gal” or “imp gal” explicitly |
Lessons for everyday users
You do not need to orbit Mars to benefit from these lessons:
- Write units on every number in notes, spreadsheets, and shared documents—“150” is meaningless; “150 lb” or “150 kg” is not.
- Convert at the boundary. Do all math in one system; convert inputs at the start and outputs at the end.
- Sanity-check orders of magnitude. If a converted luggage limit is 500 kg for a carry-on, you misread lb as kg.
- Use tools consistently—the same converter or formula each time—for repeat tasks like recipe scaling or medication tracking (always follow your clinician’s instructions for drugs).
- Question ambiguous labels on imported products: is the wrench size in mm or inches? Is the gallon US or imperial?
Why these stories persist in training
Engineering ethics courses, aviation ground-school briefings, and nursing orientation still cite the Mars Orbiter and Gimli Glider because the root causes are human and organizational, not merely arithmetic. Checklists, peer review, and explicit unit fields in software exist because mental conversion is error-prone under time pressure. The arithmetic itself is trivial; the discipline to apply it uniformly is not.
For general reference conversions—travel, cooking, fitness—a trusted converter reduces typo risk. For safety-critical work, treat conversion as a verified step with a second source, not a mental afterthought.
References
Double-check conversions with the tounits.com converter before they become costly mistakes.