This list explains how an 85 mph pitch from a 50-foot mound translates to an equivalent speed from a regulation 60-foot-6-inch mound. It is for players, coaches, and fans comparing youth and adult pitching speeds; the comparison is an estimate, not a direct radar-gun conversion.
The Core Estimate
- About 102 mph equivalent. Using equal travel time, 85 × 60.5 ÷ 50 = 102.85 mph, a simple distance-based estimate.
- About 103 mph, rounded. This is the commonly useful rounded figure, not a claim that the pitcher actually threw 103.
- 85 mph measured speed. The pitch remains 85 mph at the measurement point; the longer-distance number is an equivalence.
- 50 feet is the assumed release distance. If “50-foot mound” means the rubber is 50 feet from home, the ball is released in front of the rubber, changing the calculation.
- 60 feet 6 inches is the comparison distance. That is the official distance from the pitcher’s plate to home plate in Major League Baseball.
- Use 60.5, not 60. The extra six inches slightly raises the equal-time estimate.
- State the method with the result. Saying “about 103 mph equivalent by equal-time scaling” prevents confusion with a radar reading.
- Do not call it an official conversion. Baseball has no universally binding formula for converting speeds across mound distances.
- Keep the original reading visible. Reporting “85 mph from 50 feet” preserves the measured fact alongside any comparison.
- Think of it as a quick estimate. It helps orient a comparison, but does not capture every factor affecting a pitch.
How the Distance Calculation Works
- Start with speed times distance ratio. The basic estimate is 85 × (60.5 ÷ 50).
- Calculate the ratio first. The regulation distance is 1.21 times 50 feet, so the estimated equivalent is 1.21 times 85.
- Multiply to get 102.85. Rounding to the nearest whole number gives about 103 mph.
- Use consistent units. Both distances are in feet, so no unit conversion is needed in the ratio.
- Understand the equal-time assumption. The method asks what speed would cover 60.5 feet in the time 85 mph covers 50 feet.
- It is not a physics model of the pitch. The simple equation ignores air resistance, release mechanics, and changes in ball speed.
- Check the input before calculating. A mistaken reading, distance, or unit produces a misleading result.
- Use a calculator for precision. 60.5 divided by 50 is 1.21; multiplying by 85 gives 102.85.
- Round sensibly. “About 103” is clearer than suggesting hundredths of a mile per hour are meaningful here.
- Label it an equivalent speed. That wording distinguishes the calculation from the pitch’s observed velocity.
What the Numbers Do and Don’t Mean
- Radar readings depend on placement. A gun may capture speed near release or closer to the plate, and those readings can differ.
- Pitches slow in flight. Air resistance reduces velocity, so the location and device matter when comparing readings.
- Release point changes the flight distance. Pitchers release the ball in front of the rubber, so rubber-to-plate distance is not actual ball travel.
- Arm slot does not alter the arithmetic. It can affect the pitch’s movement and path, but not the stated distance ratio.
- Spin affects movement, not this formula. A breaking ball and fastball can read differently in flight even at similar initial speed.
- Pitch type matters to interpretation. Comparing a fastball with a curveball reading may not be apples to apples.
- Radar systems are not identical. Device calibration, angle, and tracking method can influence the displayed number.
- Do not infer effort or safety from equivalence. A converted number alone does not show how hard a pitcher is working.
- Do not compare without context. Include age, distance, measurement method, and whether the number is measured or estimated.
- Use the estimate as a conversation aid. It can make distances easier to compare, but it cannot replace measured data.
Comparisons and Quick Reference
- At 50 feet, 80 mph scales to about 97 mph. The equal-time estimate is 80 × 1.21 = 96.8.
- At 50 feet, 85 mph scales to about 103 mph. This is the calculation at the center of this list.
- At 50 feet, 90 mph scales to about 109 mph. The result is 108.9 before rounding.
- At 50 feet, 75 mph scales to about 91 mph. The calculation gives 90.75.
- At 50 feet, 70 mph scales to about 85 mph. The estimate is 84.7.
- At 55 feet, use a smaller multiplier. 60.5 ÷ 55 is about 1.10, not 1.21.
- At 46 feet, the multiplier is larger. The same equal-time approach gives 60.5 ÷ 46, roughly 1.315.
- Do not reuse the 50-foot factor elsewhere. Calculate the ratio from the actual distance each time.
- Write the distance beside the speed. “85 mph at 50 feet” makes the starting conditions explicit.
- Compare similar measurement points. That is more informative than applying a conversion to mismatched radar readings.
Using the Estimate in Baseball Conversations
- For a player profile, show both figures. List the observed 85 mph and the approximate 103 mph equal-time comparison separately.
- For coaching, prioritize repeatable readings. Consistent radar placement makes progress tracking more useful than conversion estimates.
- For scouting, note the source. Record the device, distance, and whether the number was measured or calculated.
- For social posts, explain the math. A short note avoids presenting the equivalent as a verified 103 mph pitch.
- For game comparisons, check the rule distance. Youth leagues use different pitching distances depending on age and organization.
- For training, do not chase the converted number. Use sound mechanics and qualified coaching rather than a headline comparison.
- For historical comparisons, be cautious. Radar technology and measurement conventions have changed over time.
- For a quick answer, say “roughly.” That signals the estimate’s limits without burying the useful number.
- For exact reporting, provide the equation. Readers can verify 85 × 60.5 ÷ 50 themselves.
- For disputed readings, verify the setup. Confirm the actual release-to-plate distance and radar location first.
Common Mistakes to Avoid
- Do not add 18 mph by intuition. The estimate comes from a ratio, not a fixed speed bonus.
- Do not divide by the wrong distance. The comparison uses 60.5 ÷ 50, not 50 ÷ 60.5.
- Do not treat the mound as the release point. The ball leaves the hand ahead of the pitcher’s plate.
- Do not confuse feet with yards. Convert units first if one distance is supplied in yards.
- Do not write “threw 103” without qualification. That wording misstates an estimated equivalent as a measured result.
- Do not imply every 50-foot field is identical. Field setup and league rules can vary.
- Do not compare a phone estimate to calibrated radar as equal evidence. Measurement quality differs substantially.
- Do not assume the pitch travels exactly 50 feet. Release position and trajectory affect its path.
- Do not overstate decimal precision. The inputs and assumptions do not support a precise real-world equivalent.
- Do not use the result to diagnose talent. Velocity is only one part of pitching performance.
Useful Ways to Report the Result
- “85 mph from 50 feet.” This is the clearest way to report the measured reading alone.
- “About 103 mph equivalent by equal-time scaling.” This gives the comparison and its method.
- “85 mph measured; roughly 103 mph equivalent over 60 feet 6 inches.” This keeps fact and estimate distinct.
- Include the league distance. Readers can then understand why a conversion was considered.
- Include the radar location if known. It helps others judge whether readings are comparable.
- Use “approximately,” not “exactly.” The conversion is a simplified estimate.
- Keep the original data in records. Future comparisons may use a different standard or method.
- Show the formula in technical notes. It makes the result transparent and reproducible.
- Separate measured and modeled columns. A score sheet or spreadsheet should not blend the two.
- Ask for clarification when distance is unclear. “50-foot mound” can refer to rubber placement, not ball-flight distance.
Quick Checks Before You Share It
- Confirm the speed is in mph. Kilometers per hour requires conversion before this calculation.
- Confirm the stated distance is 50 feet. Small distance changes shift the result.
- Confirm the target comparison is 60 feet 6 inches. That is the standard MLB plate distance.
- Check the arithmetic: 60.5 ÷ 50 = 1.21. This is the multiplier for the estimate.
- Check the product: 85 × 1.21 = 102.85. The rounded answer is 103 mph.
- State that this is not an official league conversion. It is a mathematical comparison under stated assumptions.
- Keep the caveat near the number. Readers may otherwise repeat the estimate as a measured velocity.
- Avoid presenting it as a guarantee. Actual flight and radar readings vary.
- Use the same convention for comparisons. Consistency matters more than choosing a particular rough method.
- Prefer direct measurement when available. A properly positioned, calibrated radar gun is better evidence.
How to Use This List
For a quick comparison, use the first section’s result: about 103 mph by equal-time scaling. When sharing it, include the original 85 mph reading and the 50-foot distance, and label 103 mph as an estimate. If you know the actual release distance or radar setup, use those details instead of assuming the ball traveled exactly 50 feet.
Frequently Asked Questions
- Is 85 mph from 50 feet really 103 mph? Not as a measured pitch; 103 mph is the rounded equal-time estimate for 60.5 feet.
- What is the calculation? Multiply 85 by 60.5 divided by 50, which equals 102.85.
- Is the conversion official? No, it is a simple comparison, not a universally adopted baseball standard.
- Does a radar gun read the converted speed? No, it reports a reading based on its tracking and measurement setup.
- Why might another calculator give a different result? It may use a different distance, release point, or conversion method.
Final Thoughts
An 85 mph pitch from a stated 50 feet works out to about 103 mph over 60 feet 6 inches under a simple equal-time calculation. Keep the measured speed and estimated equivalent clearly labeled, and use direct, consistent radar readings whenever accuracy matters.
