Miles per hour to Feet per second Converter — Convert units with exact factors and live results

This miles per hour to feet per second converter changes any mph value into ft/s using the exact factor 22/15. Enter a whole, fractional, zero, or negative value to receive a live result. The supporting calculation shows why 1 mph equals exactly 22/15 ft/s rather than treating the commonly displayed rounded factor 1.4667 as exact.

How to use

Enter the value you want to convert in the field labeled “Speed in miles per hour.” The field accepts whole numbers such as 60, fractional values such as 12.5, zero, and negative values. A negative number is appropriate only when you are using the sign to represent direction; ordinary scalar speed is normally entered as a nonnegative value.

Read the primary result as feet per second. The shared calculator multiplies the entered mph value by 5,280 to obtain feet per hour, then divides that intermediate value by 3,600 seconds per hour. This is algebraically identical to multiplying by the exact fraction 22/15. The displayed result is rounded to six decimal places, while the defining fraction is not prematurely shortened to 1.467.

Check the scale before using the answer. The numerical value in ft/s should be about 1.4667 times the numerical value in mph. For example, entering 60 produces 88.000000 ft/s. If you expected a smaller number, you may have applied the inverse conversion. The reverse calculation from ft/s to mph uses 15/22 instead.

Use the reset behavior provided by the shared interface to restore the explicit default of 60 mph. Keyboard users can move to the numeric field, replace its value, and read the refreshed output without requiring a pointer. If an entered decimal came from a physical measurement, round the final value to an appropriate number of significant figures rather than assuming that all six displayed decimal places are measured precision.

For an independent audit, write the units alongside the numbers: multiply mph by 5,280 ft/mi and divide by 3,600 s/hr. Miles and hours cancel, leaving ft/s. This method is especially useful in homework, technical documentation, or any calculation where a unit-label error would be costly.

Formula

$$v_{\mathrm{ft/s}}=v_{\mathrm{mph}}\times\frac{5280\ \mathrm{ft/mi}}{3600\ \mathrm{s/hr}}=v_{\mathrm{mph}}\times\frac{22}{15}$$

Step by step

Worked audit for 60 mph:

  1. Begin with the entered rate: $60\ \mathrm{mi/hr}$.
  2. Replace miles with feet: $60\ \mathrm{mi/hr}\times 5280\ \mathrm{ft/mi}=316{,}800\ \mathrm{ft/hr}$.
  3. Replace one hour with 3,600 seconds: $316{,}800\ \mathrm{ft/hr}\div 3600\ \mathrm{s/hr}=88\ \mathrm{ft/s}$.
  4. Check with the reduced exact factor: $60\times\frac{22}{15}=4\times22=88$.
  5. Confirm the units: miles cancel with miles, and hours cancel with hours, leaving feet per second.
  6. Apply the configured display precision: $88.000000\ \mathrm{ft/s}$.

The exact mathematical result is 88 ft/s. The trailing zeros indicate display formatting, not additional measurement accuracy.

Detailed calculation guide

To convert miles per hour to feet per second, multiply the mph value by the exact fraction 22/15. This follows from one statute mile containing exactly 5,280 international feet and one hour containing exactly 3,600 seconds. For example, 60 mph becomes 60 × 22/15 = 88 ft/s. Retaining the fraction until the final display avoids avoidable rounding error.

Miles per hour and feet per second are units of speed or velocity magnitude. Miles per hour describes the number of statute miles traveled during one hour, while feet per second describes the number of international feet traveled during one second. The conversion changes only the unit and numerical scale; it does not change the physical motion represented.

The conversion is exact under the stated unit definitions. Start with a value measured in miles per hour. Replace each mile with 5,280 feet, then replace the hour in the denominator with 3,600 seconds. The intermediate ratio is 5,280/3,600, which reduces by a common divisor of 240 to 22/15. Consequently, the exact multiplier is a rational number whose decimal expansion, 1.466666…, repeats indefinitely.

That distinction between an exact fraction and a displayed decimal matters. A screen may show a result rounded to six decimal places, but the calculation does not need to use a six-place approximation internally. If 1.466667 is substituted for 22/15, every nonzero answer carries a small factor-rounding error. The discrepancy may appear harmless for ordinary road speeds, yet it grows with large inputs and can contaminate later computations when the converted value is reused.

  • Common Mistakes
  • Multiplying by 1.467 and describing that rounded decimal as exact. It is adequate for some estimates but is not the defined conversion factor.
  • Dividing by 22/15 when converting from mph to ft/s. Multiplication is required because one mph corresponds to more than one foot per second.
  • Converting one hour as though it contained only 60 seconds. An hour contains 60 minutes and each minute contains 60 seconds, giving 3,600 seconds.
  • Using 5,280 without accounting for the time denominator. That produces feet per hour, which is an intermediate unit rather than feet per second.
  • Confusing ft/s with m/s. Feet and meters have different defined lengths, so their numerical results are not interchangeable.
  • Applying a nautical-mile definition. Miles per hour in ordinary U.S. road and customary-unit contexts means statute miles per hour, not nautical miles per hour.
  • Reporting many decimals without considering the precision of the original measurement. Exact conversion does not make an approximate speed measurement more accurate.
  • Assumptions

This calculator interprets mph as statute miles per hour and ft/s as international feet per second. It uses 5,280 feet per statute mile and 3,600 seconds per hour. Both relationships are treated as exact for this conversion. The calculation assumes that the input is already a valid numerical speed or signed velocity component and that no separate uncertainty interval is required.

A positive value indicates motion in the chosen positive direction when the number represents velocity. Zero indicates no change in position per unit time. A negative value can represent motion in the opposite direction along a defined axis. In everyday language, speed is a scalar magnitude and is normally nonnegative; the calculator nevertheless accepts negative numbers because signed velocity values are useful in physics, engineering, data processing, and coordinate-based models.

The displayed answer is rounded to six decimal places. Trailing zeros make the configured output precision visible. This presentation choice is not a claim that the source observation was measured to the nearest millionth of a foot per second. Users should round the result further when measurement uncertainty, instrument resolution, or reporting conventions require fewer significant digits.

  • Limitations

This is a unit converter, not a motion simulator. It does not calculate distance from elapsed time, acceleration, braking distance, reaction distance, energy, aerodynamic effects, or a vehicle's legal speed. It also does not determine whether a recorded speed is reliable. Those questions need additional inputs and, in many cases, domain-specific models.

The converter transforms one numerical value at a time. It does not average changing speeds or reconstruct a trip from multiple observations. Converting an average speed produces the equivalent average expressed in ft/s, but it does not reveal the instantaneous speed at any moment. Similarly, converting a peak measurement does not describe how long that peak was sustained.

Very large decimal values remain subject to the numerical limits of the shared calculation engine and the device displaying the result. Ordinary scientific, educational, athletic, and transportation values are well within practical range. For safety-critical engineering, preserve units explicitly, carry appropriate uncertainty, verify software requirements, and use controlled calculation procedures rather than relying on a general-purpose web display alone.

  • Practical Applications

Feet per second is useful when distances are naturally expressed in feet and events occur over seconds. A driver traveling at 60 mph covers 88 feet during each second if that speed remains constant. That equivalence can help explain why even a short reaction interval represents substantial travel distance, although a stopping-distance assessment must separately include reaction behavior, braking performance, road conditions, slope, tires, and other factors.

Coaches and athletes may convert running or projectile speeds when field dimensions are stated in feet. Teachers can use the conversion to demonstrate dimensional analysis and cancellation of units. Engineers may need ft/s when combining a speed with other U.S. customary quantities, provided every term in the larger calculation uses compatible definitions and units. Video analysts can compare frame-to-frame displacement in feet with a speed originally reported in mph.

  • Tips

Keep the fraction 22/15 through intermediate work, especially when the answer feeds another formula. Round only the final reported number. For mental estimates, multiply by roughly 1.5 and then reduce the estimate slightly. For example, 40 × 1.5 suggests 60 ft/s, while the exact result is about 58.667 ft/s.

Use scale checks to catch reversed operations. The numerical ft/s value should be approximately 46.7% greater than the numerical mph value for the same motion. Thus, 10 mph should become about 14.7 ft/s, not about 6.8 ft/s. The inverse conversion behaves oppositely: multiply ft/s by 15/22 to obtain mph.

Match rounding to the task. Classroom exercises may request an exact fraction or a fixed number of decimal places. Field measurements should usually reflect the significant figures of the input. Software integrations should retain more internal precision than the user-facing display whenever subsequent calculations depend on the result.

  • Interpretation

The output answers a specific question: how many feet would be traversed in one second at the entered constant rate? An answer of 88 ft/s means that maintaining the represented motion for one second corresponds to 88 feet of displacement magnitude. It does not mean that the original speed was measured over exactly one second, only that the two rates are equivalent.

For signed inputs, the sign survives the conversion because the multiplier is positive. Therefore, −12 mph becomes −17.6 ft/s. The negative sign describes orientation relative to an axis rather than a negative amount of physical path length. If only speed magnitude is relevant, use the nonnegative magnitude instead.

Zero is a valid boundary value and converts exactly to zero. Fractional inputs are also valid: 0.5 mph is exactly 11/15 ft/s, which displays as approximately 0.733333 ft/s. Repeating decimals are normal here and do not imply that the underlying conversion is approximate.

  • Related Formulas

The direct relationship is ft/s = mph × 22/15. The inverse is mph = ft/s × 15/22. Feet traveled at a constant speed over a known duration can be calculated as distance in feet = speed in ft/s × time in seconds. Conversely, constant speed in ft/s equals distance in feet divided by elapsed seconds, provided elapsed time is greater than zero.

A two-stage conversion provides a useful audit: feet per hour = mph × 5,280, followed by feet per second = feet per hour ÷ 3,600. This route produces the same result as multiplying by 22/15. Keeping the units attached to every number exposes mistakes because miles and hours visibly cancel, leaving feet per second.

For comparison with SI units, mph can be converted to meters per second with the appropriate defined length relationship, but that is a separate conversion. Do not insert the mph-to-ft/s factor into a meters-per-second calculation. Likewise, kilometers per hour, knots, pace, and acceleration each describe different units or concepts and require their own formulas.

  • Best Practices

Write the original value and unit before calculating. Apply the exact unit ratio so that unwanted units cancel. Preserve the full factor internally, then choose display precision according to the purpose. Label the final number with ft/s; an unlabeled result is ambiguous and is easy to confuse with mph or m/s.

When reviewing another person's answer, calculate by both the reduced-factor method and the two-stage dimensional method. Agreement helps catch transcription errors without relying on the same expression twice. A reasonableness estimate provides a third check: the ft/s number should be close to one and one-half times the mph number.

Document whether a value is a scalar speed, a signed one-dimensional velocity, an instantaneous observation, or an average. The arithmetic is identical, but its interpretation is not. In technical work, also document the measurement uncertainty and the point at which rounding occurred.

  • When NOT to use this calculator

Do not use this converter when the starting unit is knots, kilometers per hour, meters per second, pace per mile, or another rate that merely resembles mph. Do not use it to infer safe following distance, stopping distance, impact severity, projectile trajectory, travel time, or acceleration without the additional variables and models those tasks require.

It is also inappropriate when a contract, regulation, historical dataset, or surveying workflow explicitly mandates a different foot definition. NIST explains the retirement of the U.S. survey foot, but legacy coordinate data may still require careful treatment. This calculator intentionally uses the international-foot-based relationship appropriate to the stated statute-mile speed conversion.

Do not interpret excessive decimal places as measurement certainty. If a speedometer reports 60 mph to the nearest whole mph, the converted display of 88.000000 ft/s is the exact conversion of the entered number, not proof that the actual motion was exactly 88 ft/s.

  • Real-world examples

At 30 mph, a vehicle's constant-speed rate is 44 ft/s. Over two seconds at that unchanged rate, it would cover 88 feet before considering any change in speed. At 55 mph, the equivalent is approximately 80.666667 ft/s. At 70 mph, the result is approximately 102.666667 ft/s, illustrating why second-by-second travel distance can become substantial at highway speeds.

A slow movement of 0.5 mph converts to approximately 0.733333 ft/s. A signed simulation state of −12 mph converts to −17.6 ft/s without changing direction convention. A large test value of 1,000,000 mph becomes approximately 1,466,666.666667 ft/s; this example is mathematically useful for exposing errors caused by prematurely rounding the factor, not a claim about an ordinary attainable speed.

  • Comparison / educational intent

The direct fraction method is compact and reliable, while the dimensional-cancellation method is more explanatory. Multiplying by 1.4667 may be adequate for a quick informal estimate, but using 22/15 gives the defined result and costs no additional conceptual complexity. The converter combines both approaches: the engine follows the exact unit relationships, and the worked audit makes every cancellation inspectable.

This miles per hour to feet per second converter is most valuable when the reader needs both an immediate answer and a defensible calculation trail. It distinguishes exact definitions from rounded presentation, accepts signed and fractional values, and explains what the resulting rate does and does not establish. For the reverse direction, use 15/22; for broader motion questions, select a calculator that explicitly includes time, distance, acceleration, or the relevant physical model.

Beginner: highway speed

88.000000

Multiply 60 by 22/15. The factors simplify cleanly, producing exactly 88 ft/s.

Intermediate: fractional speed

18.333333

A decimal input is valid: 12.5 × 22/15 equals 55/3, displayed as 18.333333 ft/s.

Advanced: large exact-factor test

1466666.666667

This test demonstrates why the repeating factor should remain exact internally; premature rounding creates a visible discrepancy at large scales.

Edge case: signed velocity

-17.600000

The negative sign is preserved and may describe motion opposite a defined positive axis. Scalar speed itself is ordinarily nonnegative.

Real-world comparison: 55 mph

80.666667

At a constant 55 mph, the equivalent rate is approximately 80.666667 feet during each second.

Frequently asked questions

How do you convert miles per hour to feet per second?

Multiply the miles-per-hour value by the exact fraction 22/15. This comes from multiplying by 5,280 feet per mile and dividing by 3,600 seconds per hour. For example, 60 mph × 22/15 equals exactly 88 ft/s.

How many feet per second is 1 mph?

One mile per hour is exactly 22/15 feet per second, which has the repeating decimal representation 1.466666…. Rounded to four decimal places, 1 mph is 1.4667 ft/s.

How many feet per second is 60 mph?

Sixty miles per hour is exactly 88 feet per second. The calculation is 60 × 22/15; dividing 60 by 15 gives 4, and multiplying 4 by 22 gives 88.

Why is the mph-to-ft/s conversion factor 1.4667?

A statute mile contains 5,280 feet and an hour contains 3,600 seconds. Dividing 5,280 by 3,600 gives 22/15, whose decimal expansion is 1.466666…. The value 1.4667 is only a rounded display of that exact fraction.

Is the conversion from mph to ft/s exact?

Yes, under the stated international-foot and statute-mile definitions, the factor 22/15 is exact. A decimal result may still require rounding because fifteenths often have repeating decimal expansions.

How do you convert feet per second back to mph?

Multiply feet per second by the reciprocal factor 15/22, approximately 0.681818. For example, 88 ft/s × 15/22 equals 60 mph exactly.

Can miles per hour or feet per second be negative?

Scalar speed is conventionally nonnegative. A negative entry can nevertheless represent a signed velocity component moving opposite the chosen positive direction. The unit conversion preserves that sign.

What is 70 mph in feet per second?

Seventy miles per hour equals 70 × 22/15, or 308/3 ft/s. The decimal result is approximately 102.666667 ft/s when rounded to six decimal places.

Should I use 1.467 or 22/15 to convert mph?

Use 22/15 when accuracy matters because it is the exact factor. Multiplying by 1.467 introduces a small rounding error before the final result is calculated, and that error grows with larger values.

Does 88 ft/s mean an object travels 88 feet every second?

Yes, if the object maintains a constant rate of 88 ft/s, it covers 88 feet during each second. Real motion may accelerate or decelerate, so the statement applies only while that rate remains constant.

Are feet per second and meters per second the same?

No. A foot and a meter are different defined lengths, so ft/s and m/s have different numerical scales. Use a dedicated feet-per-second-to-meters-per-second conversion when SI units are required.

Why does the result show more decimal places than my input?

The interface uses six decimal places to display fractional conversions consistently. Those digits describe mathematical rounding, not the accuracy of the original measurement; report fewer digits when the source value is approximate.

Related calculators

Browse all calculators in this category

Editorial review

Author: JD

Sources

Enable JavaScript to use interactive calculators.