Distance Conversion Explained

Length is the simplest unit conversion and the one people most often get wrong. Here is the math behind every factor, the statute-vs-nautical mile gap, the compound feet-and-inches output, and the reference distances that catch errors instantly.

#conversion#distance#length#metric#imperial#us-customary#units

Why every distance conversion ultimately runs through the metre

Length is the simplest physical quantity to convert and the one most people get wrong anyway. There are too many units (millimetres, centimetres, metres, kilometres, inches, feet, yards, miles, nautical miles, plus the compound forms like feet-and-inches), too many almost- identical definitions of "the same" unit (international foot vs US survey foot, statute mile vs nautical mile vs Roman mile), and far too many tempting mental shortcuts that drift by a few percent each time. The distance converter on Calc Dragon collapses all of this to a single multiplication using exact factors fixed by the 1959 International Yard and Pound Agreement. This article walks through how that one multiplication actually works, where each constant comes from, the corner cases the converter handles silently, and the reference distances that catch a wrong answer before a wrong answer catches you.

The piece covers the metre-bridge formula every length conversion uses, the exact constants for both metric and customary units, the difference between statute and nautical miles, why feet-and-inches is worth its own output mode, the compound-unit decomposition that turns 1.78 m into "1 m 78 cm" without spurious carries, real-world reference distances to anchor a figure, and the cases where a length converter is the wrong tool — geodetic distance on a curved Earth, pre-2023 US survey-foot land records, and astronomical distance where a metre stops being a useful unit at all.

The math behind every length conversion

Every conversion in the distance converter uses a single intermediate unit: the metre. Each unit has a "metres per unit" factor, and the conversion is two multiplications:

result = value × (metres per source unit) ÷ (metres per target unit)

So 5 miles expressed in kilometres is 5 × 1609.344 ÷ 1000 = 8.04672 km. The same metre bridge handles every pair without needing one constant per source-target combination — only one number per unit is stored, and every other conversion follows from it. This is the standard pattern in scientific software, units libraries, and the SI brochure itself. The cost is two multiplications instead of one, and the saving is that adding a new unit only adds a single number to the table rather than a full row and column.

The factors used are exact wherever possible. The metric units are exact by definition: 1 km = 1000 m exactly, 1 cm = 0.01 m exactly, 1 mm = 0.001 m exactly. The imperial and US customary units are exact under the 1959 International Yard and Pound Agreement, which fixed 1 yd = 0.9144 m exactly. From there 1 ft = 0.3048 m exactly, 1 in = 0.0254 m exactly (25.4 mm), and 1 mi = 1609.344 m exactly (5280 ft). The nautical mile is exact by international agreement at 1852 m. NIST SP 811, the US national handbook of unit factors, lists the same numbers. Only when the converter displays the result does any rounding happen; the underlying arithmetic runs in full floating-point precision.

Worked example: 5 miles in seven different units

Take a 5-mile run — about an 8-kilometre Saturday morning — and convert it across the unit table. The distance converter gives:

  • In metres: 5 × 1609.344 ÷ 1 = 8046.72 m. Useful for track work where 8000 m is a standard repeat distance.
  • In kilometres: 5 × 1609.344 ÷ 1000 = 8.04672 km. Round in your head to "8 km plus a touch".
  • In yards: 5 × 1609.344 ÷ 0.9144 = 8800 yd exactly. A mile is exactly 1760 yards by definition, so 5 miles is exactly 8800.
  • In feet: 5 × 1609.344 ÷ 0.3048 = 26 400 ft exactly. A mile is exactly 5280 ft by definition.
  • In inches: 5 × 1609.344 ÷ 0.0254 = 316 800 in exactly.
  • In nautical miles: 5 × 1609.344 ÷ 1852 ≈ 4.345 nmi. A statute mile is about 87% of a nautical mile.
  • In centimetres: 804 672 cm. The kind of figure that only matters in physics homework.

Going the other direction is symmetric: 10 km in miles is 10 × 1000 ÷ 1609.344 ≈ 6.214 mi. The converter handles all eight base units in a single dropdown, plus four compound output formats, so the source and target can be chosen independently and any pair works.

Why the international foot is not the US survey foot

Two definitions of the foot were used in the United States until the end of 2022. The "international foot" is exactly 0.3048 m, fixed by the 1959 agreement and used in all modern engineering, sport, aviation, and everyday measurement. The "US survey foot" was retained for federal land surveys and is defined as 1200/3937 m ≈ 0.30480060960 m — about two parts per million longer than the international foot. The difference is microscopic for most purposes (about 3 mm per mile) but it matters for high-precision land surveys and for any document that cross-references coordinates from before and after the changeover.

The National Geodetic Survey deprecated the US survey foot at the end of 2022, and the international foot is now the only legal foot in the United States. Pre-2023 surveying records, US Public Land Survey System monumentation, and some state plane coordinate systems still use the survey foot, and converting them with the international foot introduces a systematic 2 ppm bias. The Calc Dragon converter uses the international definition only — for survey-foot work, multiply the international result by 1 + 2 × 10⁻⁶, which is below display precision for any sub-kilometre distance.

Statute mile vs nautical mile: when each is right

The statute mile (1609.344 m) is the everyday mile — the one on US and UK road signs, marathon distances, and most spoken English. The nautical mile (1852 m) is used in marine and aviation navigation because it has a geometric meaning: one nautical mile is approximately one minute of arc of latitude on the Earth's surface. That definition makes nautical miles enormously convenient for navigation by latitude, since every degree of latitude is 60 nmi by construction. The original definition tied the nautical mile to the Earth's actual size, but the modern definition (1852 m exactly) is a rounded value that no longer depends on which spheroid is used to model the Earth.

A nautical mile is about 15% longer than a statute mile (1.151 statute miles per nautical mile). Speeds in marine and aviation contexts are reported in knots — one knot is one nautical mile per hour. A "30 knot" cruise speed is 30 × 1.852 = 55.56 km/h, or about 34.5 mph. Marathons and road races always use statute miles or kilometres; sailing and aviation always use nautical miles. The two worlds rarely meet, but when they do (an air-sea rescue, an Atlantic crossing recorded in both units, a yacht-race report quoting both nm and km), the 15% gap is large enough to matter.

Compound units: feet-and-inches without spurious carries

Single-number outputs work for engineering and science but feel wrong for human heights and quick-reference building dimensions. A person is "5 ft 10 in", not "5.833 ft". A bookshelf is "1 m 78 cm" or "178 cm", rarely "1.78 m" outside formal documents. The distance converter exposes four compound output modes — feet+inches, yards+feet+inches, metres+ centimetres, and kilometres+metres — and decomposes the result with integer arithmetic so that float drift cannot cause a 12-inch carry to show up where 11.99 was meant.

The decomposition runs on hundredths of the smallest unit, not on the floating-point value directly. To convert 1.7800001 m to ft+in, the converter first computes total inches (70.0787...), rounds to the nearest 0.01 in (7008 hundredths of an inch), then divides by the inches-per-foot ratio (1200 hundredths of an inch per foot) to get 5 ft with 1008 hundredths of an inch left over (10.08 in). The round-then-decompose order matters: rounding the inches first and then asking "is this 12 or more?" gives 5 ft 10.08 in, not the spurious 5 ft 12.00 in that naive rounding can produce when the true answer is just a hair under a whole foot.

Reference distances to anchor a figure

Numbers without context are hard to sanity-check. A few reference distances make it easier to spot when a converted figure is obviously wrong:

  • A4 sheet of paper: 297 mm × 210 mm (about 11.7 in × 8.3 in).
  • Average adult human height: 1.65 to 1.85 m (about 5 ft 5 in to 6 ft 1 in).
  • Door height: 2.04 m (about 6 ft 8 in) is the UK standard internal door height; 6 ft 8 in is the US standard.
  • One storey of a typical building: about 3 m (10 ft) floor-to-floor.
  • Olympic swimming pool length: exactly 50 m (164 ft).
  • Athletics track lap: exactly 400 m on the inside lane (about 437 yards).
  • Football pitch (association): 100 to 110 m long, 64 to 75 m wide. A "100 m pitch" and a "100 yard American football field" differ by 8.6 m.
  • 5K race: 5 km = about 3.107 miles.
  • Marathon: 42.195 km, exactly 26 miles 385 yards by tradition (the distance from Windsor Castle to the White City stadium for the 1908 London Olympics).
  • Channel crossing (Dover to Calais): about 33 km (21 miles, or 18 nautical miles).
  • London to Paris: 344 km (214 miles) by air.
  • Earth's circumference at the equator: 40 075 km (24 901 miles, or 21 600 nautical miles by definition — 360 degrees × 60 nmi/degree).
  • Distance to the Moon: 384 400 km on average (about 239 000 miles).

If a converted figure puts a "100 m sprint" at "100 mi" or a 5K race at "50 km", the conversion has gone wrong by a factor of a thousand, and the unit was almost certainly misread. The distance converter is exact, so a wildly off result almost always means the input unit was wrong.

How to convert distances in your head

For mental estimation, a small set of shortcuts covers most common conversions:

  • km → mi: multiply by 0.6 and add 1%. So 100 km → 60 + 0.6 = 60.6 mi (exact 62.14, error 2.5%). For a tighter shortcut, use the Fibonacci coincidence: consecutive Fibonacci numbers are an excellent km↔mi pair. 8 km ≈ 5 mi, 13 km ≈ 8 mi, 21 km ≈ 13 mi. The error is under 1%.
  • mi → km: multiply by 1.6 (or by the next Fibonacci number). 5 mi → 8 km, 8 mi → 13 km, 13 mi → 21 km.
  • m → ft: multiply by 3.28, or for a quick estimate, multiply by 3 and add 10%. So 100 m → 300 + 30 = 330 ft (exact 328.1).
  • ft → m: divide by 3.28, or divide by 3 and subtract 9%. So 300 ft → 100 − 9 = 91 m (exact 91.4).
  • cm → in: divide by 2.54. For a mental version, multiply by 0.4. 25 cm → 10 in (exact 9.84).
  • in → cm: multiply by 2.54, or multiply by 2.5. 10 in → 25 cm (exact 25.4).
  • nmi → km: multiply by 1.852, or multiply by 1.85. 100 nmi → 185 km.

These are approximations, not replacements for the exact answer. The Fibonacci km↔mi trick is the only one accurate enough to use in place of the converter, and only because the golden ratio (1.618) happens to be very close to the actual conversion factor (1.609).

Common mistakes

Reading "miles" as "nautical miles" (or vice versa)

A "30 mile" range and a "30 nautical mile" range differ by 15% — a gap big enough to matter for fuel planning, ETA estimates, and any navigation involving both surface and air movement. Aviation, marine, and military contexts default to nautical miles; everyone else defaults to statute. When a number comes from one of those contexts and is being used in another, always check which mile is meant before doing the conversion.

Mixing kilometres and miles in the same workflow

The 1.609× factor is small enough to be invisible in a single conversion but accumulates fast in a chained calculation. A jogging log that records distances in km on weekdays and miles on weekends will quietly under- or over-count weekly totals by 60% on the confused days. Pick one unit per workflow and convert at the boundary, never in the middle.

Treating "metres" as "yards" because they are close

A metre and a yard differ by about 9 cm — close enough that the words get used interchangeably in casual American sport commentary, far enough that a "100-yard sprint" is meaningfully shorter than a "100-metre sprint" (the 100 m takes about half a second longer at elite pace). Track and field events are always metric. American football is always in yards. Other sports are mixed.

Forgetting that "klick" means kilometre

Military slang for "kilometre" is "klick", which gets transcribed as "click" in civilian writing and occasionally misread as something else entirely. A "5-klick patrol" is 5 km, not 5 miles. The unit is always metric in military contexts, even in countries that otherwise use miles for road distances.

When the converter is not enough

For straight-line distance between two points on the Earth's surface, a unit converter is the wrong tool — the relevant calculation is great-circle distance, computed from latitude and longitude using the haversine formula or Vincenty's algorithm. The distance converter handles the unit; the geodesy is a separate problem. For two cities at known coordinates, dedicated geographic tools (Google Maps, the Royal Observatory's calculators, the Movable Type Scripts haversine page) will give the great-circle distance, after which the converter handles km ↔ mi ↔ nmi.

For astronomy, metres and kilometres stop being useful units past a few million km. The standard astronomical units are the astronomical unit (AU, the average Earth–Sun distance, exactly 149 597 870 700 m by IAU definition since 2012), the light-year (the distance light travels in a Julian year, 9.461 × 10¹⁵ m), and the parsec (about 3.086 × 10¹⁶ m, defined by stellar parallax). These are not in the dropdown — they would push the rest of the units off the visual scale — but the conversion is mechanical: 1 light-year is about 63 241 AU, 1 parsec is about 3.262 light-years.

For anything below the millimetre, scientific notation takes over: the micrometre (10⁻⁶ m) for cell biology, the nanometre (10⁻⁹ m) for semiconductor process nodes and visible light wavelengths, the picometre (10⁻¹² m) for atomic radii, the femtometre (10⁻¹⁵ m) for nuclear radii. The metre is the right unit at human scale; both the very large and the very small need their own.

For the day-to-day questions — "how many km in 5 miles", "how tall am I in feet and inches", "how far is a marathon in km" — the Calc Dragon distance convertergives the exact answer using NIST and 1959-Agreement factors. The maths is one multiplication, the constants are exact, and the result is the same number every accurate converter on the internet should return.

Frequently asked questions

See the FAQ on the distance converter page for direct answers on how many kilometres are in a mile, how to convert feet and inches to centimetres, what a nautical mile is, and how accurate the conversion factors are. The combined calculator and FAQ cover both quick-reference and deeper questions on length conversion. For related conversions, the area converter handles square metres, square feet, acres, and hectares; the volume converter handles litres, gallons, and cups; the weight converter handles kilograms, pounds, and stones; and the pressure converter handles bar, psi, and atmospheres.

Frequently asked questions

How many kilometres are in a mile?

Exactly 1.609344 kilometres. This is the international standard value, fixed since the 1959 International Yard and Pound Agreement, which set 1 yd = 0.9144 m exactly. From there, 1 mi = 1760 yd × 0.9144 m = 1609.344 m exactly. NIST SP 811 lists the same value.

What is the difference between a statute mile and a nautical mile?

A statute mile is exactly 1609.344 m, used on roads, in athletics, and in everyday English. A nautical mile is exactly 1852 m, used in marine and aviation navigation because it approximately equals one minute of arc of latitude. A nautical mile is about 15% longer than a statute mile (1.151 statute miles per nautical mile). Speeds in marine and aviation contexts are reported in knots — one knot is one nautical mile per hour.

How do I convert feet and inches to metres or centimetres?

Multiply by exact factors: 1 ft = 0.3048 m, 1 in = 0.0254 m. So 5 ft 10 in is 5 × 0.3048 + 10 × 0.0254 = 1.778 m, or 177.8 cm. The Calc Dragon distance converter accepts feet+inches as a compound output mode, decomposing a metre value back into "5 ft 10 in" form using integer arithmetic so that float drift cannot produce spurious carries like "5 ft 12 in".

Is the US survey foot the same as the international foot?

Almost, but not quite. The international foot (used everywhere now) is exactly 0.3048 m. The US survey foot, retained for federal land surveys until the end of 2022, is 1200/3937 m ≈ 0.30480060960 m — about 2 ppm longer. The difference is microscopic for everyday work (about 3 mm per mile) but matters for high-precision land surveys. The National Geodetic Survey deprecated the US survey foot in 2022, and the international foot is now the only legal foot in the US.

Why use a metre as the conversion bridge?

Storing one factor per unit (metres per unit) instead of one factor per pair makes the converter easier to maintain and adds no precision penalty. Every conversion is two multiplications: result = value × (metres per source unit) ÷ (metres per target unit). The same metre-bridge pattern is used in every modern units library and in the SI brochure itself. Adding a new unit means adding one number to the table, not a row and a column.

How accurate are the conversion factors?

They are exact wherever possible. The metric units (mm, cm, m, km) are exact by definition. The imperial and US customary units (in, ft, yd, mi) are exact under the 1959 International Yard and Pound Agreement, which fixed 1 yd = 0.9144 m. The nautical mile is exact at 1852 m by international agreement. The arithmetic runs in full floating-point precision; only the displayed result is rounded for readability.

Why is a marathon 26 miles 385 yards rather than a round number?

The 1908 London Olympics organised the marathon route from Windsor Castle to the White City stadium, with the finish line moved to be in front of the royal box. That made the distance 26 miles 385 yards (42.195 km), which the IAAF then standardised in 1921. Earlier marathons used a variety of distances close to 25 miles (40 km), reflecting the rough length of the original Marathon-to-Athens run.

What is the Fibonacci trick for kilometre and mile conversion?

The golden ratio (1.618) is very close to the actual mile-to-kilometre factor (1.609), which means consecutive Fibonacci numbers are excellent km↔mi pairs. 5 mi ≈ 8 km, 8 mi ≈ 13 km, 13 mi ≈ 21 km, 21 mi ≈ 34 km. The error is under 1% for each pair — accurate enough to use in place of the exact converter for casual mental arithmetic.

Informational only. Not personalised financial, legal, or tax advice.