When the Deep Space Network antenna at Goldstone pings a spacecraft and measures the round-trip time, the answer comes back as a range in kilometers: 247 million and change, the signal took 1,647 seconds round-trip at the speed of light, that's roughly 247,000,000 km. But the trajectory model doesn't run in kilometers. It runs in AU. The flight dynamics team divides by 149,597,870.7 and feeds 1.65 AU into the n-body integrator. Every tracking pass, every orbit determination, every course correction burn — the conversion runs. Nobody talks about it. It just happens.
This conversion is the hidden step in every interplanetary mission ever flown. Mariner 2 to Venus in 1962: km ranging data converted to AU for the first time by a computer rather than a room full of human calculators. Voyager 2's Grand Tour used this conversion thousands of times between 1977 and 1989, each time a tracking station locked on and measured the range. The Cassini orbiter ran it for 13 years at Saturn. New Horizons still runs it now, at 163 AU and counting, the numbers getting slower to update as the signal delay stretches past 22 hours each way.
Divide kilometers by 149,597,870.7 to get AU. Ten million kilometers — a typical interplanetary cruise distance in a month — is 0.067 AU. A hundred million km is 0.668 AU. A billion km is 6.68 AU, which puts you past Jupiter. The number is small because the AU was chosen to measure planetary distances, and those are large. When you're driving across town, you don't measure the trip in millimeters. Same logic.
The inverse conversion — AU to km — is more common in public-facing material because people want to know "how far is Jupiter in miles?" But inside a mission control room, km to AU is the conversion that actually gets used. The tracking data comes in kilometers. The flight software eats AU. Somewhere in between, a number gets divided by 149,597,870.7. It's the quietest math in the building, and getting it wrong is not an option.
Spacecraft distances in km and AU
| Mission / Object | Distance (km) | Distance (AU) | |
|---|---|---|---|
| Moon (Apollo) | 384,400 | 0.00257 | 3 days transit each way |
| Sun-Earth L1 (JWST) | 1,500,000 | 0.01 | Halo orbit, permanent shade |
| Mars (at opposition) | 78,340,000 | 0.52 | Shortest Earth-Mars distance |
| Mars (at conjunction) | 378,000,000 | 2.52 | Sun between Earth and Mars |
| Jupiter (Galileo) | 628,000,000 | 4.2 | Orbit insertion: Dec 1995 |
| Saturn (Cassini) | 1,500,000,000 | 10.0 | 7-year cruise, 13-year science |
| Pluto (New Horizons) | 5,900,000,000 | 39.5 | Flyby: July 14, 2015 |
| Voyager 1 (now) | 24,400,000,000 | ~163 | Beyond the heliopause |
Frequently Asked Questions
Is there a shortcut for converting km to AU in my head?
Not really. Divide by 150 million and you'll be within half a percent — that's the best estimation shortcut. 300 million km ÷ 150 million = 2 AU (actual: 2.005 AU). For rough mental math, 150 million km per AU is close enough. For anything that matters — navigation, publication, curiosity — use the exact division.
How many km is the diameter of the Solar System in AU?
Depends where you draw the line. Neptune's orbit is 30 AU radius, so 60 AU across — roughly 9 billion km. The Kuiper Belt extends to about 50 AU. The heliopause — where the solar wind stops — sits around 120 AU. The Oort Cloud starts at about 2,000 AU and stretches to maybe 100,000 AU, or about 1.6 light-years. There is no clean edge.
When should I use this conversion instead of the reverse?
Use km→AU when you have a measured distance in kilometers — a ranging measurement, a radar echo, a laser altimeter reading — and need to place it in an orbital dynamics framework. Use AU→km when you've computed a trajectory in AU and need to tell the propulsion engineer how far the spacecraft actually travels. The two conversions are mirror images; which one you reach for depends entirely on whether you're holding a measurement or a prediction.
Engineering Context
The Mars Science Laboratory entry corridor was 10 km wide. The distance from Earth to Mars at EDL was 248 million km. Dividing gives you the angular targeting precision required: a 10 km window at 1.66 AU is an angular error tolerance measured in nanoradians. The navigation team at JPL hit it. The conversion from km to AU ran inside the Monte Carlo simulation 10,000 times, each time with slightly perturbed initial conditions, each time testing whether the spacecraft would enter the atmosphere corridor. The math is simple — just a division. Getting the right answer over and over while the solar wind pushes at the spacecraft and the planets tug at each other is not simple. Length Conversion Guide.
More: AU to km · AU to miles · light-years to km · km to light-years · Guide