Imagine a spacecraft that needs to cover 300,000 kilometres. It travels 10 kilometres every second. Dividing 300,000 by 10 gives 30,000. But 30,000 what—seconds, minutes or hours? And could we calculate a flight to Mars in the same way?
If the path length is prescribed and speed is constant and positive, travel time is distance divided by speed: t = d/v. Our example gives 30,000 seconds, or 8 hours 20 minutes. That is an answer for a teaching model. Predicting the arrival of an actual spacecraft also requires its trajectory and how its speed changes. OpenStax: distance, speed and time.
First agree on the journey we are calculating
Our imaginary space contains two markers: departure and destination. They remain fixed relative to each other in our chosen reference frame—a way of specifying positions and time. For this exercise, the frame is not accelerating. Their straight-line separation is exactly 300,000 km. This is an invented number for an exercise, not the current distance to the Moon or any other body.
The craft flies straight between them at a constant 10 km/s, measured relative to the markers. Timing begins when it passes departure already at that speed, and ends when it passes the destination. We omit acceleration before departure and stopping after arrival. Gravity does not bend or change this hypothetical motion.
Distance, speed and elapsed time must belong to one consistent reference frame. Combining a path measured in a Sun-centred frame with the craft’s speed relative to Earth will not give a reliable answer. Positions and motion are always described relative to a chosen frame. OpenStax: reference frames.
Division counts equal portions of the journey
In the first second the craft travels 10 km, and in the next second another 10 km. In 100 seconds it covers 1,000 km. “How long will the journey take?” now means: how many 10 km portions fit into 300,000 km? There are 30,000 portions. Each represents one second, so the travel time is 30,000 seconds.
Let d stand for path length, v for constant speed and t for elapsed travel time. In time t, the craft covers v ⋅ t, so d = v ⋅ t. To find time, divide the path length by the number of kilometres covered per second:
t = (d)/(v).
The formula compresses the same idea of equal portions. Units determine the answer’s unit: kilometres divided by kilometres per second give seconds. If speed is given in kilometres per hour, the answer is in hours.
Branch · With formulasOptional · you can skip this
How seconds become 8 hours 20 minutes
Substitute the numbers, then check their units separately:
t = (300 000 km)/(10 km/s),; t = 30 000 s.
When dividing by a fraction, its denominator moves to the numerator. The units cancel like this:
(km)/(km/s) = (km ⋅ s)/(km) = s.
One minute contains 60 seconds. Thus 30,000 s is 500 minutes: 8 complete hours and another 20 minutes. Check by working backwards:
8 ⋅ 3600 = 28 800,; 20 ⋅ 60 = 1 200,; 28 800 + 1 200 = 30 000.
Alternatively, first convert 10 km/s to 36,000 km/h and divide 300,000 by 36,000. The result is 8(1)/(3) hours. A third of an hour is 20 minutes, not 33 minutes: decimal fractions of an hour must be multiplied by 60 rather than read as minutes.
Faster means fewer seconds; farther means more
At 20 km each second, every second completes twice as much of the same journey. We need half as many seconds: 15,000, or 4 h 10 min. Instead, keep speed at 10 km/s and double the path length. We then need twice as much time: 16 h 40 min.
Compare these cases. Each bar represents time on a shared scale; a longer bar does not mean a faster craft.
One model, three journeys
Predict first: how does time change if only speed or only distance doubles?
Reference example
- Prescribed path length
- 300,000 km
- Constant speed
- 10 km/s
- Calculated time
- 8 h 20 min
Reference time
Twice the speed
- Prescribed path length
- 300,000 km
- Constant speed
- 20 km/s
- Calculated time
- 4 h 10 min
Half the time
Twice the distance
- Prescribed path length
- 600,000 km
- Constant speed
- 10 km/s
- Calculated time
- 16 h 40 min
Twice the time
Shared bar scale: from 0 to 16 h 40 min.
These relationships hold when the other conditions stay the same. Doubling speed does not mean we can halve a real mission’s duration without other changes: we first need to explain how the craft obtains its new speed and which path it follows.
The operation itself also has boundaries. At v = 0, a craft will not cover a positive distance; division by zero gives no arrival time. A negative number is also unsuitable for v here: it represents scalar speed, without direction, rather than a velocity component along an axis. If the path length is zero and v > 0, the formula gives zero time—there is no distance left to cover in the model.
A message and a spacecraft take different times
Substituting the speed of light for the craft’s speed gives the time for a light signal to propagate in vacuum. That answers a different question. Light covers our hypothetical 300,000 km in about one second; a craft at 10 km/s takes 8 h 20 min.
The speed of light in vacuum, c, is exactly 299,792,458 m/s, or 299,792.458 km/s. A signal therefore takes slightly more than one second to cross 300,000 km, not exactly one second. BIPM: the metre definition and exact value of c.
Branch · ScaleOptional · you can skip this
One astronomical unit: minutes or days?
The astronomical unit, symbol au, is a length unit equal to exactly 149,597,870.7 km. It is close to the characteristic Earth–Sun distance, but that does not mean their current separation is always that value. IAU: definition of the au, Resolution 2012 B2.
Take a hypothetical straight path 1 au long, fixed endpoints and a craft travelling at a constant 30 km/s in the same frame. This gives:
t = (149 597 870.7)/(30) s,; t = 4 986 595.69 s.
Divide by the 86,400 seconds in a day to obtain approximately 57.7 days. A light signal crossing the same fixed distance requires:
t = (149 597 870.7)/(299 792.458) s,; t ≈ 499 s.
That is about 8 min 19 s one way. With fixed endpoints and no processing delay, a reply would require another crossing. Neither number calculates a flight to the Sun or another real destination: 1 au specifies only the exercise’s length. Nor are we calculating the craft’s own clock reading in a relativistic flight.
What is missing for a real flight?
A planet does not wait beside a stationary finish marker. It moves along its orbit while the craft travels. The craft also moves in a gravitational field: even with its engine off, its direction and speed can change. An interplanetary trajectory is usually part of an orbit around the Sun; it must meet the target’s future position. NASA: trajectories and planetary encounters.
Thus the planets’ current separation is not a ready-made length for the future path, and a craft’s maximum speed is not its speed throughout the journey. Entering the trajectory, possible manoeuvres and braking for capture at the destination depend on the chosen mission. Dividing one distance value by a speed record is insufficient to predict arrival time.
Branch · DeeperOptional · you can skip this
What if we substitute an average speed?
Average speed over a whole journey is total path length divided by total elapsed time. If both quantities for the same trajectory and reference frame are already known, t = d/v_(avg) is valid even when speed varies. OpenStax: average and instantaneous speed.
But a definition does not supply missing information. If time is unknown, average speed must come from a justified model of motion, rather than a guess based on initial or peak speed. Taking the ordinary mean of the initial and final speeds is not a universal rule.
If a journey is divided into sections with known constant speeds, calculate each section’s time and add the times. Continuously varying speed requires a more detailed description of motion. Our first formula remains useful, but does not replace information about the actual path.
Check your understanding: in our model, both path length and speed double. What happens to time? It stays at 8 h 20 min: the route contains twice as many kilometres, but every second covers twice as many. The two effects cancel. This is a first example of reasoning with proportions.
To calculate a simple travel time, first specify the path, reference frame and positive constant speed, match the units and divide. To calculate an actual mission, we first need to establish how the spacecraft will move. For another exercise, triple only the distance: can you predict the result before dividing, then check its units?