Feet per second to Miles per hour Converter — Convert units with exact factors and live results
Use this feet per second to miles per hour converter to translate a speed in ft/s into mph with the exact factor 15/22. Enter zero, a positive decimal, or a signed value representing velocity in a chosen direction. The result appears with practical rounding, while the formula and worked audit show how seconds, hours, feet, and miles cancel.
How to use
Enter the value you want to convert in the field labeled “Speed in feet per second.” The accepted unit is ft/s. You may enter a whole number such as 88, a decimal such as 12.5, zero, or a negative value such as −44 when the sign represents direction along a chosen axis. If your source is a written fraction, convert it to a decimal before entering it because the field accepts numeric values rather than expressions such as 1/3.
Read the primary result as speed in miles per hour, or mph. The calculator first multiplies the entered ft/s value by 3,600 seconds per hour, then divides by 5,280 feet per mile. This is exactly equivalent to multiplying by 15/22. The displayed answer uses six decimal places so that fractional and low-speed results remain useful.
Check the direction of the conversion before using the answer. This page converts ft/s to mph. If you start with mph and need ft/s, use the reverse relationship: multiply mph by 22/15. A quick magnitude check is also helpful: the mph number should be about 0.682 times the ft/s number. Thus 88 ft/s should produce 60 mph, while 10 ft/s should produce about 6.818182 mph.
For a report, round the result according to the accuracy of the original measurement or the rules governing your work. The extra displayed digits are useful for auditing but do not add certainty to an approximate input. Keep the unit beside the value, preserve a negative sign when it carries directional meaning, and avoid using “FPS” without context because readers may interpret it as frames per second.
Formula
Step by step
Worked audit for 88 ft/s:
- Start with the measured rate: 88 ft/s.
- Convert the time denominator from seconds to hours: 88 × 3,600 = 316,800 ft/h.
- Convert feet to miles: 316,800 ÷ 5,280 = 60 mi/h.
- Verify with the reduced exact factor: 88 × 15/22 = 1,320/22 = 60 mph.
- Apply the output format: 60.000000 mph.
The units cancel as (ft/s) × (s/h) × (mi/ft), leaving mi/h. No rounded conversion constant is used. An independent reverse check gives 60 × 22/15 = 88 ft/s, returning exactly to the input.
Detailed calculation guide
To convert feet per second to miles per hour, multiply the ft/s value by the exact fraction 15/22. This factor follows from 3,600 seconds per hour and 5,280 feet per international mile. For example, 88 ft/s becomes exactly 60 mph. A negative input keeps its sign and can represent velocity in the opposite direction along a selected axis.
A foot per second is a rate of one international foot traveled each second. A mile per hour is a rate of one international mile traveled each hour. Conversion changes the numerical value and unit label, not the underlying motion. Under the stated definitions, 1 ft/s equals exactly 15/22 mph, approximately 0.681818 mph.
The conversion is a ratio-of-units calculation. Begin with a value expressed in feet for every second. Multiplying by 3,600 seconds per hour changes the time basis from seconds to hours, producing feet per hour. Dividing that result by 5,280 feet per mile changes the distance basis from feet to miles. The unwanted feet and seconds units cancel, leaving miles per hour.
The factor should be kept as 3,600/5,280 or its reduced form, 15/22, throughout the calculation. Both forms are exact. The decimal 0.681818 is only a shortened display of a repeating decimal, so repeatedly using that rounded decimal can introduce a small error. The calculator evaluates the ratio from the integer unit counts and rounds only the displayed result to six decimal places.
The international foot is exactly 0.3048 metre. Using 5,280 feet per statute mile means the mile is exactly 1,609.344 metres. These definitions make the ft/s-to-mph ratio exact rather than experimental. The conversion therefore has no measurement uncertainty of its own. Any uncertainty in the answer comes from the entered measurement, not from the unit factor.
Common mistakes usually arise from changing only one part of the compound unit.
- Multiplying by 60 accounts for seconds in a minute but stops before converting minutes to hours. The required time multiplier is 60 × 60, or 3,600.
- Dividing an ft/s value directly by 5,280 changes feet to miles but leaves the denominator in seconds. That result is miles per second, not miles per hour.
- Treating 0.681818 as exact discards the repeating digits of 15/22. Use the fraction for calculation and the decimal only for presentation.
- Confusing ft/s with m/s produces a substantial mismatch because one foot is not one metre. Check the unit printed beside the source value.
- Removing a negative sign changes directional information. When the number represents signed velocity, conversion must preserve its sign.
- Rounding the input before conversion can matter more than rounding the factor. Retain the measured digits until the final reporting step.
Several assumptions define what this result means. The input uses the international foot, not a historical or survey-foot convention. The output uses the statute mile and a conventional hour of 3,600 seconds. The input and output describe the same constant or instantaneous rate; no acceleration is inferred. A signed input is treated algebraically, so a negative result denotes the opposite selected direction rather than a physically negative magnitude of speed.
The calculator accepts ordinary decimal numbers. A fractional quantity must be entered as its decimal equivalent because the numeric field does not parse text such as “1/3.” For example, enter 0.3333333333 for approximately one-third ft/s. Precision in the result cannot recover precision absent from the input. If a sensor reports 27 ft/s to two significant figures, a six-decimal display does not make the underlying observation accurate to six decimal places.
The tool also has clear limitations. It performs a unit conversion, not a motion model. It does not calculate distance from elapsed time, average a varying speed, account for acceleration, resolve velocity vectors, or correct instrument error. It does not infer whether a reading is ground speed, airspeed, wheel speed, projectile velocity, fluid velocity, or another physical quantity. Those interpretations require context supplied by the user.
Very large values can be entered only within the practical numeric limits of the shared calculation engine and the device displaying the result. At extreme magnitudes, floating-point representation may limit the last displayed digits even though the mathematical factor remains exact. For measurements demanding traceable laboratory uncertainty, retain the source data, calibration information, significant figures, and uncertainty budget rather than relying on a rounded screen value alone.
Practical applications include comparing data produced by systems that use different customary speed units. A sports analyst may receive ball or sprint velocity in ft/s while a broadcast graphic uses mph. An engineer may convert a simulation output before comparing it with a specification. A student can use the cancellation steps to check dimensional analysis. A technician may translate conveyor, airflow, or component velocity for a report whose audience expects mph.
The conversion can also support quick reasonableness checks. Since the mph value is about 68.18% of the ft/s value, the numerical result should be smaller in magnitude. A value of 100 ft/s is therefore about 68 mph, not 147 mph. The reverse relationship behaves differently: an mph value is multiplied by 22/15, approximately 1.4667, to obtain ft/s.
Useful tips improve both accuracy and communication.
- Confirm that the source really is feet per second. The abbreviations fps and FPS can be ambiguous because FPS also commonly refers to frames per second.
- Keep 15/22 as the conversion factor in spreadsheets, scripts, and hand calculations whenever possible.
- Enter the full available measurement rather than a prematurely rounded version.
- Match reported precision to the quality of the original measurement, even if the calculator displays additional digits.
- Include ft/s or mph beside every recorded number so that a bare value cannot be misread later.
- Preserve a minus sign when direction matters, but use a nonnegative magnitude when discussing speed in the strict scalar sense.
Interpreting the answer requires separating display precision from physical accuracy. Six digits after the decimal point make small conversions visible and allow results to be audited, but they do not certify six-place measurement accuracy. For an approximate input such as 23.4 ft/s, reporting 15.954545 mph may be useful during calculation, while 16.0 mph may better reflect three significant figures in a final narrative.
Zero is a valid boundary case: 0 ft/s equals 0 mph. A negative value is mathematically valid for a one-dimensional velocity and remains negative after conversion. A small positive value remains positive even if a coarse display would round it to zero. This calculator uses six decimal places to reduce that risk for everyday inputs, although values smaller than half of one millionth mph can still display as 0.000000.
Related formulas help place this conversion within a broader speed toolkit. Reverse the operation with ft/s = mph × 22/15. Convert ft/s to metres per second with m/s = ft/s × 0.3048. Convert mph to metres per second with m/s = mph × 0.44704. If constant speed and elapsed time are known, distance equals speed multiplied by time, provided compatible units are used.
A useful identity check connects the routes. Converting 88 ft/s directly gives 60 mph. Converting 88 ft/s to metres per second gives 26.8224 m/s; dividing by the exact 0.44704 metres-per-second value of 1 mph also gives 60 mph. Agreement between independent unit paths is a strong way to detect a reversed factor or an omitted time conversion.
Best practice is to write the value and units at every line of a manual calculation. Arrange conversion factors so unwanted units appear once above and once below the fraction bar. Do not erase units until they cancel. Retain exact integers or fractions during intermediate work, then round once at the end. For software or spreadsheet use, document the factor as 3600/5280 or 15/22 so reviewers can recognize its origin.
When comparing a converted result with a threshold, avoid rounding before making the comparison. Suppose a limit is exactly 60 mph. The exact corresponding threshold is 88 ft/s. An observed value slightly above 88 ft/s is above the limit even if a low-precision display still reads 60 mph. Regulations, contracts, and engineering acceptance criteria may prescribe their own rounding or tolerance rules, which take priority over a general-purpose display convention.
Do not use this calculator when the source unit is metres per second, kilometres per hour, knots, feet per minute, or frames per second. Do not use it to derive vehicle speed from engine revolutions without tire and gearing data. It is also unsuitable for calculating an average from multiple intervals unless an appropriate distance-weighted or time-weighted method has already produced a single ft/s rate.
For relativistic motion, fluid flows requiring compressibility analysis, navigation involving vectors, or trajectories with changing velocity, the arithmetic conversion may remain valid for an individual component or instantaneous magnitude, but it does not solve the governing physical problem. Use a model suited to that problem and apply this unit factor only at a clearly identified input or output boundary.
Real-world examples illustrate the scale. A person moving at 10 ft/s travels at about 6.818182 mph. A vehicle or projectile moving at 88 ft/s is at exactly 60 mph. A conveyor moving at 2.5 ft/s is about 1.704545 mph. A signed simulation component of −44 ft/s converts to −30 mph, preserving the selected directional convention. A 120 ft/s measurement converts to about 81.818182 mph.
Fractional inputs work without any change to the formula. For 12.5 ft/s, multiplication by 15 gives 187.5 and division by 22 gives approximately 8.522727 mph. For 0.001 ft/s, the exact result is 0.000681818 repeating mph, displayed as 0.000682 mph. These cases show why both decimal acceptance and delayed rounding are important.
Educationally, the converter is more than a lookup factor. It demonstrates dimensional analysis for a compound unit: distance and time must both be converted. A reference chart is convenient for a few fixed values, but it cannot cover arbitrary decimals or preserve signed velocity. A hand calculation reveals the unit cancellation, while the calculator provides fast, consistent evaluation and an auditable result. Using both approaches makes errors easier to spot.
The essential conclusion is straightforward: to convert feet per second to miles per hour, multiply by the exact ratio 15/22 and round only for the intended presentation. The relationship applies equally to zero, decimals, and signed one-dimensional velocities under international-foot and statute-mile definitions. Keep the original measurement precision in mind, label the result in mph, and use a fuller motion model whenever the task involves more than unit conversion.
Beginner: 10 ft/s walking or running comparison
6.818182
Multiply 10 by the exact factor 15/22. The result is 75/11 mph, displayed as 6.818182 mph.
Intermediate: exact 60 mph equivalence
60.000000
The calculation 88 × 15/22 cancels 22 into 88 and gives exactly 60 mph without approximation.
Advanced: fractional conveyor speed
8.522727
A fractional input uses the same factor: 12.5 × 15/22 = 8.522727 repeating mph.
Edge case: signed reverse-direction velocity
-30.000000
The conversion preserves the sign: −44 × 15/22 equals exactly −30 mph along the selected axis.
Real-world: 120 ft/s equipment or projectile reading
81.818182
Multiplying 120 ft/s by 15/22 produces 900/11 mph, displayed as 81.818182 mph.
Frequently asked questions
How do you convert feet per second to miles per hour?
Multiply the feet-per-second value by the exact fraction 15/22. Equivalently, multiply by 3,600 seconds per hour and divide by 5,280 feet per mile. Round only the final result.
What is 1 foot per second in miles per hour?
One foot per second equals exactly 15/22 mile per hour. Its decimal expansion repeats, so it is approximately 0.681818 mph when rounded to six decimal places.
How fast is 10 feet per second in mph?
Multiply 10 by 15/22. The exact result is 75/11 mph, whose repeating decimal is approximately 6.818182 mph when displayed to six decimal places.
How many feet per second is 60 mph?
Use the reverse conversion and multiply 60 mph by 22/15. The result is exactly 88 ft/s, providing a convenient check of the forward conversion.
Is the ft/s to mph conversion factor exact?
Yes. There are exactly 3,600 seconds in an hour and 5,280 international feet in a statute mile, so 3,600/5,280 reduces exactly to 15/22.
Why is 1 ft/s not exactly 0.681818 mph?
The exact value is 15/22 mph, which has a repeating decimal expansion. The written value 0.681818 stops after six decimal places and is therefore a rounded approximation.
Can feet per second be negative?
Speed as a scalar magnitude is normally nonnegative, but a signed ft/s value can represent one-dimensional velocity. A negative sign indicates motion opposite the chosen positive direction and remains negative in mph.
Does converting ft/s to mph change the actual speed?
No. Unit conversion changes the numerical representation, not the physical motion. The ft/s and mph values describe the same rate using different distance and time units.
Why do you multiply by 3,600 when converting ft/s to mph?
The denominator must change from seconds to hours. Since one hour contains 3,600 seconds, multiplying by 3,600 converts feet per second into feet per hour before feet are converted to miles.
What is the reverse formula for mph to ft/s?
Multiply miles per hour by 22/15, approximately 1.4666667. This is the reciprocal of the exact forward factor 15/22, so applying both conversions returns the starting value apart from display rounding.
Are fps and ft/s always the same thing?
Not necessarily. In motion calculations, fps may mean feet per second, but in video and graphics it commonly means frames per second. Write ft/s when you need to remove that ambiguity.
How many decimal places should I use for an mph result?
Use enough digits for the purpose without implying more measurement accuracy than the input supports. The calculator shows six decimal places for auditability, but a measured input may justify fewer significant figures.
Does this converter use the international foot?
Yes. It assumes the international foot, defined as exactly 0.3048 metre, and the statute mile of 5,280 international feet. Historical or specialized foot definitions are outside its scope.
Can I enter a fraction such as 1/3 ft/s?
Enter its decimal equivalent because the numeric input does not evaluate written arithmetic expressions. For one-third ft/s, enter an appropriately precise decimal such as 0.3333333333.
Related calculators
Browse all calculators in this category
Editorial review
Author: JD
Sources
Enable JavaScript to use interactive calculators.