PoinT GOResearch
how to·how to

Lacrosse Shot Speed Radar Measurement: Correcting Release-Angle Error

Radar angle error can swing lacrosse shot speed readings by 15-20%. Get the crease-position setup, bearing tolerances, and checks that fix it.

PoinT GO Research Team··10 min read
Lacrosse Shot Speed Radar Measurement: Correcting Release-Angle Error

Why One Radar Spot Reads Two Different Speeds From the Same Drill

A Division II assistant coach ran into this two falls ago during a crease-finishing session. One radar unit sat dead-center behind the cage for the entire practice. Shots from X, behind the goal line, working a quick roll, logged in the mid-50s mph. Bounce shots from the top of the box on the next rep, same shooters, same rotation, logged in the high 70s and low 80s. The staff's first instinct was to flag the inside finishers for a strength deficiency and add more medicine-ball work. That diagnosis was wrong before the new program's first rep.

Nothing about the shooters' mechanics changed between reps. What changed was the angle between each shot's true flight path and the radar's fixed line of sight. Doppler radar reports only the velocity component traveling directly along its own beam, so a shot crossing the goal mouth at a sharp bearing loses a chunk of its reading to simple trigonometry, not effort.

Akiyama and Yamamoto ran into this constraint directly when they studied physical predictors of shot velocity in 20 lacrosse athletes. Using a microwave Doppler unit to log ball speed, they found moderate-to-strong correlations between shot velocity and medicine-ball throw distance (r = 0.58-0.66), countermovement vertical jump height (r = 0.44-0.46), grip strength (r = 0.33-0.46), and isokinetic knee extension strength (r = 0.20-0.45) (Akiyama & Yamamoto, 2019). The detail that matters for testing protocol: their radar was realigned to each athlete's fixed shooting position for every trial, not left in one spot to cover every release point on the field. The study's own limitation, a single-institution sample of 20, means those correlations need replication, but the alignment discipline behind the data collection is the part any coach can copy immediately.

The Cosine Effect Doesn't Ask Whether You're Shooting From X or Up Top

Doppler radar measures speed by comparing the frequency shift of the signal it gets back to the frequency it sent out. That shift only equals true ball speed when the ball is moving directly along the radar's beam. Any angle between the beam and the actual flight path, call it θ, knocks the reading down by a factor of cos(θ), regardless of how fast the ball is really moving.

The scale of the loss surprises most people the first time they see it laid out. A 15-degree offset, easy to end up with when a radar is aimed at the goal in general rather than one release point, already discards about 3.4% of the true reading. Widen that to 30 degrees, roughly what separates a shot from X off one pipe versus the other, and the loss passes 13%. A shooter capable of a genuine 90 mph release can watch the display read anywhere from 90 down to 78 mph depending purely on where they stood.

Angle From True Flight PathCosine FactorReading for a True 90 mph Shot
1.00090.0 mph
0.99689.6 mph
10°0.98588.7 mph
15°0.96686.9 mph
20°0.94084.6 mph
30°0.86677.9 mph
45°0.70763.6 mph

Every value in that table is pure trigonometry. No radar model fixes it, and no shooter's technique changes it. It only ever tracks where the unit was pointed relative to where the ball actually went.

Crease Position Changes the True Angle Faster Than Most Setups Adjust For

Lacrosse compounds the angle problem in a way tennis or baseball radar setups rarely face, because shots legitimately originate from all around the box in one session: X and GLE behind the cage, both wings, up top near the restraining line, a crease roll from point-blank range, and a bounce shot that changes direction mid-flight. A radar bolted to one tripod spot might sit within 5 degrees of true for a top-of-box shot and 35 degrees off for a shot from X on the far pipe, in the same ten-minute block, tripod never touched.

Bounce shots add a second wrinkle. The ball's velocity vector changes at the bounce point, so a reading taken after the bounce measures a different trajectory than the one that left the stick. If the goal is release velocity, the unit needs to be gated to catch the ball in the short window before the bounce, not averaged across the whole flight.

Distance compounds it at the close end of the box. Crease finishes from inside 3 meters put the radar close enough that stick-check and follow-through motion can register before or alongside the ball itself, contaminating the peak reading the same way racket-head speed contaminates a badly placed tennis radar. Indoor box lacrosse adds multipath reflection off boards and low ceilings, which some consumer units average into the display rather than reject.

A Setup Standardized by Crease Zone, Not Bolted to One Spot

The fix isn't a better radar. It's treating each crease zone as its own measurement problem with its own bearing correction, built around one fixed base position:

Shot OriginRadar Bearing Adjustment From CenterWhy
Top of box / point0-5° (base position)Nearly in line with a radar centered behind the goal
Wing10-15° pivot toward that wingKeeps beam within tolerance of the actual release line
X / GLE, near pipe20-25° pivot toward that sideShot crosses at a sharp bearing to a centered unit
X / GLE, far pipe30-35° pivot toward that sideWidest angle offset in a standard set; highest error risk if ignored
Crease roll / insideMove unit back to 5-6 m minimumAvoids stick and follow-through contamination at close range

Pair the zone table with a fixed base protocol: mount height at 1.0-1.3 m to match stick-head release height, a locked tripod rather than a handheld unit, peak-speed hold mode, one unit of measurement logged on the sheet. Mark each zone's bearing with tape or a cone on the turf so the angle reproduces session to session instead of getting eyeballed fresh every practice.

One detail catches most testing programs off guard: dominant- and non-dominant-side shots from the identical spot release at a different point relative to the body. Vincent and colleagues documented this when they compared shooting mechanics across high school, collegiate, and professional men's players; trunk lean, shoulder rotation, and crosse angular velocity all differed measurably between dominant and non-dominant releases in the same athletes (Vincent et al., 2016). A bearing tuned for a right-handed release from the wing needs re-checking, not just re-aiming, for a left-handed shooter working the same spot.

A Two-Minute Angle Check Before Any Zone Goes Live

Run this before trusting a single number out of a new crease rotation, new field, or new radar position:

  • Have one shooter hit two shots at matched, moderate effort: one from the zone closest to dead-center, one from the widest-angle zone in the rotation. A wide-angle reading more than 8-10% below the centered reading, with no obvious effort difference, means the bearing needs correcting before real data gets logged.
  • Sight down the radar barrel yourself toward the release point for that zone. If you can't trace a reasonably straight line from the radar head through the ball's actual release point, the bearing is off before the first real shot is taken.
  • Run a stationary drop check between zone changes. A ball dropped from shoulder height should read near zero at rest with one clean spike on the drop; a unit returning noise on this basic check needs a battery or firmware check before it goes near a live drill.

This adds barely any time to a warmup but catches most bearing errors before they get logged as real performance differences between zones.

What Realistic Shot-Speed Numbers Look Like Once Angle Is Controlled

Once bearing error is controlled, shot-speed numbers become genuinely comparable across zones, sessions, and, cautiously, players. Field benchmarks for men's outdoor lacrosse cluster roughly like this by position:

Position / LevelTypical Shot Speed (mph)Typical Shot Speed (km/h)
Youth / recreational35-5556-89
High school attack / midfield55-7589-121
Collegiate defense (long pole)60-8097-129
Collegiate attack / midfield75-95121-153
Elite / recorded top shots100-115+161-185+

The gap between collegiate and elite levels isn't purely a strength gap. Vincent and colleagues found professional players producing crosse angular velocities roughly 21% faster than high school or collegiate players in the same shooting motion analysis (Vincent et al., 2016), a mechanical efficiency difference layered on top of raw output. Treat a 5-8% swing between sessions under matched conditions as normal noise, and watch the gap between an athlete's average and peak shot across ten reps more closely than any single best number.

The Mistakes That Show Up Most in Crease-Zone Testing

  1. One radar position covering every zone in a rotation drill without re-bearing. Fix: use the zone table above and mark bearings on the turf so recentering takes seconds, not a guess.
  2. Logging a post-bounce reading as release speed on bounce-shot reps. Fix: gate the reading to the release-to-bounce window, or note on the data sheet which reps were bounce shots and treat them as a separate category.
  3. Testing crease rolls from inside 3 meters without accounting for stick-check contamination. Fix: pull the unit back to 5-6 meters for any inside finish, even if that means repositioning between reps.
  4. Mixing dominant- and non-dominant-side shots into one average. Fix: log side separately; the mechanical difference is real and documented, not measurement noise.
  5. Comparing an indoor box lacrosse session to an outdoor field session as if the radar setup were identical. Fix: log the surface and enclosure type; wall and ceiling reflections indoors add variability that has nothing to do with the shooter.

Building a Protocol That Moves With the Drill, Not Just the Radar

A shot-speed number only earns its place in an athlete's file if the next number can be trusted enough to compare against it. That means writing the zone-by-zone setup down like a lab sheet: radar model, bearing per zone, mount height, distance from the shooter, unit of measurement, and which reps were bounce shots or non-dominant side.

Retest on the same cadence used for other power qualities, every 3 to 4 weeks inside a training block works for most programs, and retest with the exact zone sheet from before, not just the same radar in roughly the same spot. A program that rotates fields, tripods, or testers without documenting the setup generates drift that reads exactly like real performance change, with no way to separate the two without the paper trail.

FAQ

Frequently asked questions

01How much does a 25-degree radar angle actually cost a shot from X?
+
About 9.4%. Cos(25°) is roughly 0.906, so a genuine 90 mph release would display closer to 81.5 mph, enough to make a strong finisher look average purely because of where the tripod sits.
02Do I need a separate radar for every crease zone?
+
No. One unit works fine if you re-bear it, or pivot it on a marked base, between zones. What you can't do is leave it aimed at one spot and expect every zone's reading to mean the same thing.
03Why does a bounce shot read differently than a direct shot from the same spot?
+
The ball's velocity vector changes at the bounce. A radar catching the post-bounce trajectory is measuring a different flight path than the one that left the stick, so treat bounce-shot readings as their own category rather than folding them into direct-shot averages.
04Is there a real difference between dominant- and non-dominant-side shot speed, or is that just weaker technique?
+
Vincent and colleagues (2016) documented measurable differences in trunk lean, shoulder rotation, and crosse angular velocity between sides in the same players. It's a real mechanical pattern, not just less practice, and it's worth logging separately rather than averaging away.
05Can PoinT GO replace a radar gun for shot-speed testing?
+
PoinT GO measures crosse-head speed and swing timing from a stick-mounted sensor, a related but distinct signal from ball speed off the head. Most programs get the most value pairing the two: radar for verified ball speed by zone, PoinT GO for the swing data that explains why a reading moved.
Keep reading

Related Articles

how to

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.

guides

Lacrosse Midfield Two-Way Running Conditioning: Reproducing Transition Load Without GPS

Your middie's mile time looks fine but he fades on the third clear of the third quarter. Here's a shuttle-based protocol that reproduces that load without GPS.

how to

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.

how to

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.

how to

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.

how to

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.

how to

Beach Volleyball Jump-Serve Contact Velocity Test: Measuring Toss-to-Contact Timing on Sand

Radar clocks the ball, not why the reading swings 15 km/h between serves. Get the toss-to-contact timing protocol, sand setup, and 2 cited studies.

how to

Bluetooth Dropout Losing VBT Reps Mid-Set: How to Diagnose and Fix It

A set logs 4 of 6 reps and the velocity chart has a gap. Split the cause into interference, distance and buffering, then recover the missing data.

Measure performance with lab-grade accuracy

Get PoinT GO