Snowboard Halfpipe Landing Load Testing: Why Trick Height Fades Late in a Run

A rider drops in clean, stomps the first three hits of the run just fine, then somewhere around hit four or five the air starts looking smaller — not because they're gassed the way a sprint would gas them, but because every landing on that wall is quietly loading the same joints the last landing just loaded. Coaches who track air time off a single big hit miss this pattern completely, because the tallest air in a session often happens early, while the legs are still fresh and the run hasn't cost anything yet. By the time it matters — hit five, hit six, the trick that's supposed to close the run — the rider is landing into knees and ankles that have already absorbed four rounds of collision-level force, and a stopwatch reading from one jump won't show you any of that.

This guide sets out a hit-by-hit testing protocol for halfpipe runs: how to measure air time and landing load on every wall of a run rather than just the best one, what a normal versus concerning decline curve looks like, and what to actually do about it once you've found it.

Why a Single Big-Air Reading Misses the Real Pattern

Most halfpipe testing still measures the way judges score: pick the best hit of the run and report that number. Harding, Mackintosh, Martin, and James (2008, Journal of Sports Sciences) built one of the first practical tools for this, mounting a single inertial sensor near an athlete's center of mass and detecting the flight phase as the window where the sensor reads close to free-fall acceleration — no vertical ground reaction, because the athlete isn't touching the ground. Their system tracked air time and rotation well enough to support automated scoring alongside judges' calls, and it proved a simple point that still holds up: you don't need a lab full of cameras to get a usable air-time number off a wearable sensor. What that kind of system usually reports, though, is a single flight-phase duration per jump — exactly the number a coach wants for the highlight hit, and exactly the number that hides a run-long decline if nobody logs every hit in sequence.

Run the same detection logic across all five or six hits instead of just the tallest one, and a different picture shows up: air time tends to fall in a fairly steady line from the first hit to the last, well before the rider would describe themselves as tired.

What 'Landing Load' Actually Measures on Each Hit

Air time tells you how long a rider was off the wall. It tells you nothing about how hard they came back down, and that second number is the one driving the decline. Landing load, for this protocol, is two related readings taken from the same accelerometer signal: peak resultant acceleration at ground contact (reported in g) and landing impulse, the area under that acceleration curve across the contact phase (reported in g·s, or converted to N·s per kilogram of body mass for cross-athlete comparison).

Krüger and Edelmann-Nusser (2010, Sports Technology) measured exactly this in elite freestyle snowboarders using a combined full-body inertial system and bilateral insole pressure system during halfpipe jumps, and reported peak vertical landing forces commonly running in the region of three to five times body weight, with a clear asymmetry between the leading and trailing foot depending on the direction of rotation on the trick. Their sample was small — two athletes — which is typical for this kind of instrumented-athlete work but means the specific force values shouldn't be treated as population norms, only as a demonstration that halfpipe landings sit in genuinely high-force territory even on a well-executed trick.

Equipment and Run Protocol

A single triaxial IMU is enough — you don't need the full insole pressure array from a research lab to run this in-season. Mount it low on the sacrum (close to the body's center of mass, which gives a cleaner flight-phase read) or, if you want foot-specific asymmetry data, on the boot cuff of each leg. Sample at 800 Hz or higher; halfpipe landings load and unload inside roughly 150-220 milliseconds, and anything below about 400 Hz starts missing the true peak.

The baseline single-hit trials matter more than they look. Without a fresh-leg reference for that individual rider on that specific wall height, a hit-six air time of 1.0 seconds is just a number — you can't tell whether it's a 10% dip or a 25% one. Log the baseline the same day, same pipe, same conditions as the full runs; wall height and snow conditions change these numbers enough between venues that a baseline from last month's session isn't a fair comparison.

The Cumulative Load Curve: Watching Height Fall Hit by Hit

Here's what a single run typically looks like once you log every hit instead of just the best one — this is an illustrative session, not a specific rider's data, but the shape of the curve is the pattern that shows up over and over in run-length testing:

Three things move together here, and each one on its own would be easy to explain away. Air time drops about 28% from hit one to hit six. Peak landing acceleration climbs steadily — the rider isn't landing softer as they go, they're landing harder, because the eccentric control that normally absorbs force is degrading. And contact time shortens, which sounds backwards until you realize what it means: a fatigued landing doesn't sink into a longer, more controlled absorption phase, it stiffens up and dumps the force faster into a shorter window. That combination — falling air time, rising peak force, shrinking contact time — is the fingerprint of accumulated landing load, not general tiredness. Nicol, Avela, and Komi's (2006, Sports Medicine) review of stretch-shortening cycle fatigue lays out the likely mechanism: repeated high-force eccentric-to-concentric landings progressively blunt the stretch reflex and reduce elastic energy return, and that effect compounds within a single bout well before an athlete would self-report as fatigued. Their work isn't halfpipe-specific — most of the underlying studies used repeated drop jumps or hopping protocols in a lab — but the mechanism transfers directly to a run where every wall is another high-force landing stacked on the last one.

Interpreting the Drop-Off: Normal Range vs Red Flag

Some decline across a run is normal and not a red flag on its own — riders aren't machines, and a 5-10% air time drop from hit one to the final hit, alongside a modest rise in peak landing g, is the expected cost of six consecutive high-force landings. What separates a normal training effect from something to act on is the combination and the rate.

• Under 10% air-time drop, contact time stable or rising: normal fatigue pattern. No action needed beyond noting it for that rider's baseline.
• 10-20% air-time drop with contact time falling: the stiffening pattern described above is showing up. Flag it, but one session in this range isn't a program change on its own.
• Over 20% air-time drop, contact time falling, peak accel climbing past roughly 6.5-7g on a rider whose baseline sits well below that: the rider is landing later hits with meaningfully less force attenuation than they land early ones. This is where landing-related injury risk on the closing tricks of a run climbs, and it's worth restructuring the run or the session before it shows up as an ankle or knee issue instead of a number on a chart.

Track the pattern across sessions, not just within one run. A rider whose hit-six numbers are creeping worse week over week — even if no single session crosses the red-flag line — is accumulating load faster than they're recovering from it, and that trend is usually a more useful early warning than any single day's data.

Training and Run-Pacing Fixes That Actually Help

Once the curve shows up, three adjustments do most of the work. First, sequence the run around it: if a rider's data consistently shows the steepest drop after hit four, that's a case for putting the hardest, highest-consequence trick earlier in the run rather than saving it for the finale — a run built on the assumption that the legs are equally fresh at hit six as at hit one is fighting the data. Second, build landing-specific eccentric strength off-snow — depth jumps and loaded step-downs that train the leg to absorb force over a longer, more controlled window rather than stiffening up under load, which directly targets the contact-time shortening pattern rather than just building general leg strength. Third, treat run volume like any other high-force training variable and periodize it: stacking full competition-length runs back to back with short rest, session after session, is exactly the exposure that drives the week-over-week creep described above, and cutting full-run volume in favor of isolated single-hit repetition for a few days lets the eccentric system recover without losing trick reps.

None of this replaces landing technique coaching — a rider who lands stiff-legged on every hit will show a worse curve than one with clean absorption mechanics regardless of conditioning. But technique work alone doesn't fix a run-pacing problem, and conditioning work alone doesn't fix a technique problem; the load curve is useful precisely because it tells you which one you're actually looking at on a given day.