A travel-ball pitcher throws a bullpen for a scout, and the scout's gun behind the L-screen reads 83. Two weeks later the same kid throws the same effort in front of his own coach, whose tripod is set up on the dugout roof because that is the only clear sightline available, and the number that comes back is 78. Nothing about the arm changed. Nobody accused the coach of using a broken gun, but the conversation that followed - maybe he was tired, maybe the mound is soft - was chasing a physiology explanation for what was actually a geometry problem.
A Doppler radar gun does not measure the speed of the ball. It measures the rate at which the ball is closing the distance directly between itself and the radar antenna. When the gun sits exactly on the ball's flight line, those two numbers are identical. The moment the gun sits off to the side - on a fence, a dugout roof, a courtside chair - the two numbers diverge, and they diverge in exactly one direction: down. This is cosine error, it is entirely predictable from the setup angle, and it is one of the few measurement problems in sports tech you can fix with a tape measure instead of a firmware update.
The Physics: Why Off-Axis Always Reads Low, Never High
Skolnik (2001), in Introduction to Radar Systems, one of the standard references in radar engineering, formalizes what every continuous-wave Doppler radar is actually sensing: the frequency shift in the reflected signal corresponds only to the component of the target's velocity that runs along the straight line between the radar and the target - the radial component. Any velocity the ball has that runs across that line, rather than along it, produces zero Doppler shift and is invisible to the gun. The relationship is exact: measured speed equals true speed multiplied by the cosine of the angle between the gun-to-ball line and the ball's actual direction of travel.
Because cosine of any angle other than zero is less than one, the error only ever runs one way. A misaligned radar gun cannot report a speed higher than the ball's true speed - only equal to it or lower. That asymmetry is itself a useful diagnostic: if a gun is reading inconsistently high on some throws and low on others with no setup change, cosine error is probably not your culprit, since it has no mechanism to inflate a reading.
The size of the error is small at first and then grows fast. At 5 degrees off the flight line you lose under half a percent. At 10 degrees you are still under 2%. Past 15 degrees the curve steepens noticeably, and by 30 degrees - roughly what you get standing at a 45-degree angle to a pitcher from a typical dugout distance - you are underreading by more than 13%.
| Angle Off Flight Line | cos(angle) | Reading Error | 90 mph True Reads As |
|---|---|---|---|
| 0 degrees | 1.000 | 0% | 90.0 mph |
| 5 degrees | 0.996 | 0.4% | 89.6 mph |
| 10 degrees | 0.985 | 1.5% | 88.7 mph |
| 15 degrees | 0.966 | 3.4% | 87.0 mph |
| 20 degrees | 0.940 | 6.0% | 84.6 mph |
| 30 degrees | 0.866 | 13.4% | 77.9 mph |
| 45 degrees | 0.707 | 29.3% | 63.6 mph |
The limitation worth naming here: Skolnik's treatment is general Doppler theory, not a sports-specific finding, and it assumes a single dominant reflector traveling in a straight line. It does not model a spinning or curving ball's changing aspect over flight, which introduces a smaller secondary wobble on top of the geometric error described above - real, but usually below 1% next to the alignment error itself.
Is It Cosine Error, or Is Something Else Going On?
Before you move the tripod, rule out three other common causes of a low reading that get blamed on the gun.
- Release-to-plate deceleration is real and separate. A thrown baseball loses speed to air drag between the pitcher's hand and home plate - commonly somewhere in the 8-10% range for a four-seam fastball over roughly 55 feet of flight, depending on spin and pitch type. A gun set up correctly on-axis behind the plate will read a genuinely slower number than a gun correctly on-axis behind the pitcher, and that is not an error to fix - it is two different, both-accurate measurements of two different points in the pitch. Compare gun placement, not just the number, before assuming misalignment.
- Peak versus average velocity mode. Some radar units default to reporting average velocity across the whole flight rather than the peak value at release or at the plate. If two guns disagree by a fixed few mph on every throw regardless of setup, check the mode setting before checking the angle.
- Weak return signal. A low battery, a target too far out, or a ball with unusually low radar reflectivity can cause a gun to lock onto a weaker or later part of the Doppler return rather than the true peak, producing an inconsistent low reading that has nothing to do with geometry. This shows up as erratic misses rather than a stable, repeatable low number - cosine error, by contrast, produces a low reading that is consistent from throw to throw as long as the setup does not change.
If your low readings are stable and repeatable at a fixed setup, and the gun position was not deliberately placed on the flight line, cosine error is the most likely explanation and the cheapest one to check first.
Getting Pitching Gun Placement Right
The correct position for measuring release velocity is directly behind the pitcher, on the extension of the rubber-to-plate line, gun pointed straight down that line toward the plate. In practice, three setups routinely violate this without anyone noticing:
The L-screen offset. Screens are rarely dead-center on the mound-to-plate line, and a gun mounted on or braced against the screen inherits whatever lateral offset the screen has. A screen set two feet to the glove side at a distance of 40 feet from release already produces a small but nonzero angle - usually still under the 10-degree threshold, but worth checking rather than assuming.
The dugout or fence shot. When there is no clear lane through the screen, the easiest sightline is often from a dugout roof or an outfield-side fence, both of which sit well off the throwing line. This is the setup most likely to produce a double-digit-degree angle and a reading several miles per hour low, exactly like the scout-versus-coach example above.
Behind-the-plate for release speed. A gun correctly on-axis behind the plate measures a real, accurate number - it is just measuring plate velocity, not release velocity, and the two are not interchangeable even when both are correctly aligned. Decide which number you actually want before you decide where to stand.
Getting Serve Gun Placement Right
For serve speed, the flight line runs from the contact point - roughly overhead and slightly forward of the baseline center mark - down through the service box. The gun belongs directly behind that line, typically mounted at or near the baseline center on a tripod, pointed down the center of the court.
The most common real-world violation is a courtside setup: a coach or parent seated in a chair beside the court, off to one side, because that is where seating exists and a baseline tripod would be in the way of play. Depending on how far off-center that chair sits relative to how far it is from the server, the resulting angle is frequently large enough to produce a noticeable, and misleadingly modest-looking, serve speed. A club that reports serve speeds from a fixed courtside camera position across an entire season is comparing every player against the same systematic underread - which keeps rankings internally consistent but makes any cross-venue or cross-broadcast comparison meaningless.
The Alignment Check: A 5-Minute Fix
Run this once per venue or setup, and again any time the gun position changes.
- Identify the true flight line: rubber to plate for pitching, or contact point to the center of the far service box for serving.
- Measure the straight-line distance from the gun to the release point or contact point.
- Measure the lateral (perpendicular) offset from the gun's actual position to that flight line.
- Calculate the angle: angle = arctan(offset / distance). A basic angle-finder or compass app aimed down the barrel of the gun toward the target line gives you this directly without the arithmetic.
- Apply the 10-degree rule: if the angle is under 10 degrees, the error is under 1.5% and generally not worth correcting for most training and scouting purposes. Past 15 degrees, either reposition the gun or plan to apply a correction (see below).
Radar gun manufacturers document this same guidance directly - most sports radar manuals, including Stalker and JUGS units, include a cosine effect note recommending the unit be kept within roughly 10 degrees of the target's line of travel for full-rated accuracy. It is not a hidden defect; it is a stated operating condition that gets skipped when a tripod goes wherever there happens to be room.
Can You Fix Readings You Already Recorded?
If you cannot move the gun - a fixed broadcast camera position, a permanent tripod mount that cannot be relocated mid-season - you can apply a correction after the fact, provided you know the geometry: true velocity equals measured velocity divided by the cosine of the known angle.
This correction is only valid under two conditions. First, you need the actual angle, measured with a tape and a distance, not guessed - a wrong angle estimate can just as easily overcorrect as undercorrect. Second, the target needs to travel in a reasonably straight line relative to the gun for the portion of flight being measured; a pitch with significant late lateral break measured very close to the plate, or a serve with heavy spin curving well before the service box, changes the true angle across the flight window rather than holding it fixed, and a single correction factor will be approximately right at best. For a straight fastball or a flat first serve measured near release, the correction is reliable. For a breaking ball measured deep into its break, treat any corrected number as an estimate rather than a precise figure.
Barris and Button (2008), in their review of motion-analysis methods in sport published in Sports Medicine, flagged this exact category of problem when comparing field-based tools like radar against vision-based systems: non-optical field methods carry setup-dependent error that vision-based systems are structurally immune to, and operator alignment is one of the largest uncontrolled variables in field ball-speed measurement. Their review is qualitative on this specific point rather than reporting a quantified radar effect size, and radar hardware has moved on since 2008 - some current units now include angle-compensation features - so treat it as confirmation of the underlying risk category rather than a number to plug into a spreadsheet.
Worked Example: Two Common Setups, Corrected
Both examples below use measured offsets and distances from real fixed setups, run through the arctan and cosine steps described above.
| Setup | Lateral Offset | Distance to Target | Angle | Reading | True Speed | Error |
|---|---|---|---|---|---|---|
| Dugout-roof tripod, bullpen session | 20 ft | 55 ft | 20.0 degrees | 78.0 mph | 83.0 mph | -6.0% |
| Courtside chair, club serve speed check | 10 ft | 40 ft | 14.0 degrees | 118.0 mph | 121.6 mph | -3.0% |
In the bullpen case, the 5 mph gap between the scout's on-axis reading and the coach's dugout reading is fully explained by an angle just past the 15-degree caution line - no change in the pitcher's actual output is required to account for it. In the tennis case, the underread is smaller in absolute terms but still enough to make a genuinely 120-plus mph serve look like it falls short of that mark on paper, which matters if speed thresholds are being used for scouting, seeding, or program benchmarks. Neither number is a device malfunction. Both are the gun reporting exactly what it was pointed at.
Frequently asked questions
01Can a radar gun ever read too high because of cosine error?+
02How close to dead-on does my radar gun placement need to be?+
03My gun and my friend's gun disagree by 6-8 mph on the exact same pitch. Is one of them broken?+
04Does behind-the-plate placement have cosine error too, or is that setup always correct?+
05Can I just apply a fixed correction number to every reading from a setup I know is angled?+
Related Articles
Tennis Serve Velocity: How to Measure It Accurately with Radar
Angle and distance errors can swing tennis serve radar readings by 10-15%. Get the exact placement, tolerances, and verification checks that fix it.
Why GPS Underreports Sprint Max Speed and How to Fix It
GPS max speed reads low for a reason: sampling rate, smoothing filters, and satellite lock. A control protocol to isolate which one is costing you km/h.
How to Track a Pitcher’s Throwing Velocity with IMU: An 800Hz Sensor Standard Beyond the Radar Gun
Radar guns clock the pitch, not the arm behind it. An 800Hz IMU tracks 5 metrics like MER velocity, where injury risk climbs past 8,500 deg/s.
How to Calibrate a Velocity Sensor: 5-Step VBT Accuracy Protocol
A miscalibrated VBT sensor skews every reading that follows. Follow this 5-step protocol for reference measurement, mounting, baseline, and verification.
Linear Position Transducer Cable-Angle Error Fix: Correcting Off-Vertical Pull
An off-vertical LPT cable inflates displacement and velocity readings. See why, how to test your setup, and the mount fix that corrects it for good.
Ankle Sprain Return-to-Play: Hop Test and Balance Cutoffs Before Cutting Resumes
Pain-free jogging isn't clearance to cut. A hop-and-balance protocol with the LSI and reach cutoffs research actually supports before cutting resumes.
Bands and Chains Wreck Your VBT Velocity Readings: How to Fix It
Add bands or chains and your velocity zones lie. See why accommodating resistance skews VBT readings, and how to test and prescribe around it.
Fixing Barometric Altimeter Drift That Skews Jump Height Readings Indoors
Indoor HVAC and door-driven pressure swings quietly drift a barometric altimeter's baseline, inflating jump height over a session. Here is the re-zero fix.
Measure performance with lab-grade accuracy