Flying 10m Sprint Test: Protocol, Setup, and Benchmarks

A team runs its athletes through a standing 10m sprint, records the times, and calls it a speed test. The problem is that a standing 10m time is mostly a strength-and-start-mechanics number, not a top-speed number, and coaches who use it to chase max velocity gains end up training the wrong quality. Krzysztof and Mero (2013) reconstructed the split times of the three fastest 100m races on record and found that Bolt, Powell, and Gay were still gaining velocity in flying 20m segments well past the 60m mark, meaning a standing-start test over any short distance never actually samples the phase where top speed lives. A flying 10m test fixes that by giving the athlete a run-in to reach near-maximal velocity before the clock starts. What follows is the setup, the execution details that most field tests get wrong, and benchmark times to check your numbers against.

What a Flying 10m Test Actually Measures

In a standing sprint test, the clock starts at the gun or the first gate, so the recorded time is a mix of reaction, force production off a static start, and whatever top speed the athlete reaches by the finish. In a flying test, the athlete builds up over a run-in distance and the clock only starts once they cross the first gate at or near their ceiling velocity. The 10m segment between the two gates is then a near-pure measure of maximum running speed, stripped of the acceleration component entirely.

This distinction matters because acceleration ability and maximum velocity are separable qualities that don't always travel together. Cronin and Hansen (2005) tested a flying 10m sprint in a cohort of rugby league players alongside squat jump height, isometric strength, and a standing sprint, and found that flying sprint performance correlated with lower-body power output in a way the standing sprint did not track as cleanly — the two tests were picking up different physical qualities, not redundant versions of the same one. An athlete can have an average start and an excellent top gear, or the reverse, and a single standing-start number hides which one applies.

Course Setup, Run-In Distance, and Equipment

Run-in distance: This is the single most consequential setup decision and the one most field tests get wrong by defaulting to whatever distance happens to fit the space available. Team-sport athletes without a sprint-specific training background typically reach 95% or more of their achievable velocity by 20–25m, so a 20m run-in is usually sufficient. Athletes with a sprinting background, including track athletes and speed-trained field-sport players, continue accelerating past 30m and need a 30–35m run-in or the flying gate will still catch them mid-acceleration and inflate the reported max velocity number downward. When in doubt, run one pilot trial with a radar or laser gun watching the run-in; if velocity is still rising at the point where the first gate would sit, extend the run-in by 5m.

Gate placement: Dual-beam infrared gates at hip height, positioned exactly 10m apart, mark the start and end of the timed zone. Do not use a single-beam system for this test — a single beam is prone to false triggers from an arm swing at high stride frequency, and at maximum velocity the margin for that kind of error matters more than it does during acceleration testing.

Surface and wind: Use the same firm, dry surface for every session an athlete is compared across. Outdoors, note wind direction and rough speed; a tailwind above roughly 2 m/s measurably inflates flying times in the same way it does for official sprint records, and testing into a headwind on one occasion and with a tailwind on another will produce a false training effect or a false decline. If you cannot control for wind, test indoors or accept that outdoor sessions are only comparable to other sessions run in similar conditions.

Alternative to gates: A calibrated radar gun or a GPS/IMU unit sampling at sufficient frequency can substitute for timing gates and has the advantage of showing the full velocity curve rather than just the average over 10m, which makes it easier to confirm the run-in was long enough.

Step-by-Step Testing Protocol

1. Warm up thoroughly. General mobility and light jogging for 8–10 minutes, followed by 3 progressive build-up runs over the full run-in plus flying zone distance at roughly 70%, 85%, and 95% effort, each with 2–3 minutes of rest. Skipping the 95% build-up is the single most common reason a first trial underperforms the rest of the session — the neuromuscular system needs at least one near-maximal exposure before it produces a true peak.
2. Set the run-in. Mark the start point with a cone at the chosen run-in distance behind the first gate (20m for most team-sport athletes, 30m or more for sprint-trained athletes, confirmed by the pilot trial described above).
3. Execute the trial. The athlete accelerates progressively through the entire run-in, reaching top gear before the first gate rather than at it, and holds that effort through the second gate without any visible deceleration before the line. Cue athletes explicitly to keep sprinting 5m past the finish gate — many athletes unconsciously ease off in the final meter before a line they can see, which slows the recorded segment.
4. Record and repeat. Take 3 valid trials with 5 minutes of full rest between each — flying sprints are maximal-effort efforts and under-resting compounds fatigue trial to trial. Discard any trial where the athlete visibly decelerated before the exit gate or stumbled during the run-in.
5. Score. Use the fastest of the three valid trials. Convert time to velocity as 10 divided by the flying 10m time in seconds, expressed in meters per second, for a more intuitive number to track over a training block.

Common Setup and Execution Mistakes

Flying 10m Time and Max Velocity Benchmarks

The ranges below are drawn from published race analysis and sport-specific testing literature (Krzysztof & Mero, 2013; Haugen, Tønnessen, Hisdal, & Seiler, 2014) and should be treated as broad reference points, not pass/fail thresholds — testing methodology, run-in distance, and timing system all shift the absolute numbers.

Elite sprinters reach a meaningfully different velocity ceiling than field-sport athletes, but the gap between an elite soccer player and a recreational one (roughly 1–1.5 m/s) is often smaller than coaches assume — the bigger separation between levels tends to show up in acceleration and repeated-sprint ability rather than in pure top speed.

Turning Flying 10m Data Into Training Decisions

The real value of a flying 10m score shows up when it's paired with a standing-start sprint time from the same athlete. If both are strong relative to peers, the athlete is well-rounded and general sprint work maintains both qualities. If the standing 0–10m is poor but the flying 10m is competitive, the limitation is force production off a static start, and the training priority is resisted starts, hip extensor strength, and start-position mechanics — flying sprints won't move that number much. If the flying 10m is the weak link despite a decent standing start, the athlete has an acceleration engine but no top gear, and the fix is maximum-velocity work: flying sprints at 95–100% effort, very light sled loads (5–10% of bodyweight) that don't compromise stride mechanics, and overspeed methods like slight downhill running or tow-assisted sprints.

Programming flying sprints for max-velocity development works best at low volume and high quality: 4–6 reps of 10–20m flying zones per session, full recovery of 3–5 minutes between reps, and no more than 2 sessions per week layered on top of other speed and strength work. Because these are maximal-effort, high-force efforts, they should sit early in a session after a full warm-up and before any accumulated fatigue, and total weekly max-velocity sprint volume should stay under roughly 150–200m of flying-zone distance to manage hamstring strain risk. Re-test the flying 10m every 4–6 weeks using the same run-in distance and surface — a 0.02–0.03s improvement is a real training effect at this level, while anything smaller can fall within normal session-to-session variability.