ThisCalculator

Everyday

MPH to FPS: Speed Conversion Explained

Updated · Standard formula, shown below

Feet per second 88.00 fps
Meters per second
26.82 m/s
Result
Miles per hour
60 mph
You entered

This calculator converts miles per hour (mph) to feet per second (fps) instantly. Enter a speed in miles per hour, and it returns the equivalent speed in feet per second, along with the reverse conversion for reference. The conversion factor is exact: 1 mph = 1.466666… fps.

Formula

The conversion uses the definition of both units:

  • 1 mile = 5,280 feet
  • 1 hour = 3,600 seconds

So the formula is:

fps = mph × 5280 / 3600

Which simplifies to:

fps = mph × 1.466666…

Where:

  • mph = speed in miles per hour (mi/h)
  • fps = speed in feet per second (ft/s)

For metric users, 1 mph = 0.44704 m/s exactly, and 1 m/s = 2.236936 mph.

Worked Example

Using the default value of 60 mph:

  1. Start with 60 mph.
  2. Multiply by 5,280 feet per mile: 60 × 5280 = 316,800 feet per hour.
  3. Divide by 3,600 seconds per hour: 316,800 / 3600 = 88 fps.

So 60 mph = 88 feet per second. The calculator shows 88.00 fps, and also gives 26.82 m/s (60 × 0.44704).

Why Convert mph to fps?

Feet per second is commonly used in physics, engineering, and safety contexts where short distances and short time intervals matter. For example:

  • Stopping distances for vehicles are often quoted in feet per second.
  • Reaction times (like the 1.5-second following rule) are easier to apply in fps.
  • Sports like baseball and tennis measure pitch or serve speeds in mph, but ball travel time over a known distance is easier in fps.
  • Weather reports sometimes give wind gusts in mph, but structural engineers may use fps for load calculations.

Converting to fps lets you multiply by time directly to get distance, or divide distance by time to get speed, without extra unit conversions.

Common Mistakes and How to Avoid Them

The most frequent error is using the wrong conversion factor. Some people multiply by 1.5 instead of 1.4667, which introduces a 2.3% error. For rough mental math, 1.5 is close, but for precise work use the exact factor.

Another mistake is mixing up the direction: to go from fps to mph, you divide by 1.4667 (or multiply by 0.6818). If you accidentally multiply, you get a number that is about 2.15 times too large.

Also, be careful with units when using the metric factor. 0.44704 is exact, but rounding to 0.45 gives a 0.66% error—fine for casual use, not for engineering.

Quick Reference Table

Here are some common speeds converted to fps:

  • 10 mph = 14.67 fps
  • 20 mph = 29.33 fps
  • 30 mph = 44.00 fps
  • 40 mph = 58.67 fps
  • 50 mph = 73.33 fps
  • 60 mph = 88.00 fps
  • 70 mph = 102.67 fps
  • 100 mph = 146.67 fps

Notice the pattern: every 10 mph adds about 14.67 fps. That’s because 10 × 1.4667 = 14.667.

Real-World Examples

Stopping distance: At 60 mph, a car travels 88 feet per second. If the driver’s reaction time is 1.5 seconds, the car covers 132 feet before the brakes are applied. That’s about half a football field.

Baseball pitch: A 90 mph fastball travels at 132 fps. From the pitcher’s mound (60 feet 6 inches from home plate), the ball reaches the batter in about 0.46 seconds.

Wind speed: A 40 mph wind gust is about 58.7 fps. That means in one second, the air moves almost 59 feet—useful for estimating debris travel or cooling effects.

How to Do It Mentally

For a quick estimate, multiply mph by 1.5 and subtract 2%. For example:

  1. Start with 60 mph.
  2. Multiply by 1.5: 90.
  3. Subtract 2% of 90 (1.8): 88.2.
  4. Exact answer is 88.0—close enough for conversation.

If you only need a rough figure, just multiply by 1.5. The error is about 2.3%, which is often acceptable for casual use.

Frequently Asked Questions

How do I convert fps back to mph?

Divide the fps value by 1.4667, or multiply by 0.6818. For example, 88 fps ÷ 1.4667 = 60 mph. The same conversion works in reverse.

Is 1 mph exactly equal to 1.4667 fps?

Yes, the exact factor is 5280/3600 = 22/15 = 1.466666… repeating. The decimal 1.4667 is rounded to four places, which is accurate enough for most purposes.

Why are there 5280 feet in a mile?

The mile originated from the Roman “mille passus” (a thousand paces), but the modern statute mile of 5,280 feet was standardized in England in 1593 by Parliament, partly to align with the furlong (660 feet) and the acre. The number 5,280 is exactly 8 furlongs × 660 feet.

What is the difference between mph and knots?

A knot is one nautical mile per hour, where a nautical mile is 6,076.12 feet (approximately 1.15 statute miles). So 1 knot ≈ 1.1508 mph. To convert mph to knots, divide by 1.1508.

Do I need to convert mph to fps for speed limits?

No, speed limits are always given in mph in the US and UK. FPS is used in physics problems, engineering, and sometimes in sports analytics, but not for road signs.

How accurate is the calculator?

The calculator uses the exact conversion factor 5280/3600, so it is accurate to the number of decimal places shown (2). For most real-world purposes, that is more than sufficient.

Related

Formula used
in mph | Miles per hour | mph | 60 | 0
out fps | Feet per second | fps | mph * 5280 / 3600 | 2
out mps | Meters per second | m/s | mph * 0.44704 | 2

Each line is one input (in, sel, list) or one result (out: label, unit, formula, decimals). How the calculators work

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.