Skip to main content

Conversion of miles to kilometers (and back) using addition only

Some time ago I came across the trick that allows easy conversion of miles and kilometers (and also mph and km/h) using addition only. The trick uses the fact that the ratio of the Fibonacci numbers is very close to the conversion factor between miles and kilometers.

This is an example of turning multiplication to addition in a similar manner to the use of logarithms in a slide rule.

Firstly, the Fibonacci sequence is pretty easy to remember or regenerate from scratch because it is generated by the rule "the next number is the sum of the preceding two numbers". The sequence starts from 0 and 1 and then proceeds 1, 2, 3, 5, 8, 13, 21, 34, ... Each number is the sum of the previous two numbers.

Secondly, the ratio of consecutive Fibonacci numbers gets closer and closer to 1.62 the larger the numbers get. For example, 3/2 = 1.5, 8/5 = 1.6, 13/8 = 1.63, 21/13 = 1.62, 34/21 = 1.62, ...

Lastly, there are 1.61 kilometers in a mile. If you take the ratio of Fibonacci numbers as 1.62 then the error in using that for miles/kilometers conversions is about 0.5%. For everyday usage that's pretty good.

To go from kilometers (or kph) to miles (or mph) find the number in the list of Fibonacci numbers and look at the preceding number. For example, 34km (or kph) is 21.1 miles (or mph); using Fibonacci you get 21 miles (of mph). 8km is 4.97 miles; using Fibonacci it's 5 miles.

To go the other way (miles to kilometers) simply go the other way along the line. So find the number (in miles) in the Fibonacci sequence and get the kilometers from the next number.

On a recent trip to France I tried this out. The speed limit on a French autoroute is 130 kph which is 80.78 mph. Using the Fibonacci sequence it comes out at 80 mph (you can drop the 0 on both numbers since you're dealing with a ratio and go from 13 to 8 in the Fibonacci sequence).

When it's raining the speed limit drops to 110 kph. Now 11 doesn't appear in the sequence (again I've dropped the zero and will put it back in later). But 11 can be decomposed into 8 and 3 (11 = 8 + 3) and the answer obtained by looking at the mph figures for 11 and 3 in the Fibonacci sequence and adding them together. Thus we get 5 + 2 = 7 and so 110 kph is 70 mph (it's actually 68.35 mph). The error comes about because the early Fibonacci numbers are not quite at the right ratio. You can remove the error by remembering that 3 km is 1.8 (not 2) and then you get 5 + 1.8 = 6.8 (giving 68 mph).

Note that you can also use subtraction. For example, to work out 16 kilometers in miles you could look at 13 and 3 (to get 8 + 1.8 = 9.8) or you could do 21 and 5 (to get 13 - 3 = 10).

You can also play around with other tricks. For example, returning to 110 km you can see that it is 55 * 2 and 55 is a Fibonacci number. So at once you have 110km is 34 miles * 2 = 68 miles.

Comments

deskwarrior said…
And you can create any number of parallel "Fibonacciesque" sequences starting with two numbers not in the normal sequence, e.g.. 3,4,7,11,18,29.. the convergence to that same ratio is still going to occur.
martijn said…
Do people actually use this in practise? I mean, it's a nice trick and all that, but I don't find multiplying by 1.6 (which is equally accurate) too hard. Definitely not harder than splitting a number into smaller ones that happen to occure in the Fibonacci sequence.

(Take the number. Half it. Divide the orignal number by ten. Add these three numbers.)

Popular posts from this blog

Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it: Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name. There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly. What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message: Our system is unable to process last names that contain non-letters, please replace them with spaces. Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your

All the symmetrical watch faces (and code to generate them)

If you ever look at pictures of clocks and watches in advertising they are set to roughly 10:10 which is meant to be the most attractive (smiling!) position for the hands . They are actually set to 10:09.14 if the hands are truly symmetrical. CC BY 2.0 image by Shinji I wanted to know what all the possible symmetrical watch faces are and so I wrote some code using Processing. Here's the output (there's one watch face missing, 00:00 or 12:00, because it's very boring): The key to writing this is to figure out the relationship between the hour and minute hands when the watch face is symmetrical. In an hour the minute hand moves through 360° and the hour hand moves through 30° (12 hours are shown on the watch face and 360/12 = 30). The core loop inside the program is this:   for (int h = 0; h <= 12; h++) {     float m = (360-30*float(h))*2/13;     int s = round(60*(m-floor(m)));     int col = h%6;     int row = floor(h/6);     draw_clock((r+f)*(2*col+1), (r+f)*(row*2+1),

The Elevator Button Problem

User interface design is hard. It's hard because people perceive apparently simple things very differently. For example, take a look at this interface to an elevator: From flickr Now imagine the following situation. You are on the third floor of this building and you wish to go to the tenth. The elevator is on the fifth floor and there's an indicator that tells you where it is. Which button do you press? Most people probably say: "press up" since they want to go up. Not long ago I watched someone do the opposite and questioned them about their behavior. They said: "well the elevator is on the fifth floor and I am on the third, so I want it to come down to me". Much can be learnt about the design of user interfaces by considering this, apparently, simple interface. If you think about the elevator button problem you'll find that something so simple has hidden depths. How do people learn about elevator calling? What's the right amount of