Standing Knee Injuries — Throws and Shots

ACL, MCL, and meniscus injury mechanisms specific to standing exchanges — distinct from leg-lock knee trauma.

Adapted from InGrappling, Standing Knee Injuries — Throws and Shots. System Games did not invent this curriculum.

Medical disclaimer. This content is for educational purposes only. It does not constitute medical advice. Consult a qualified medical professional for any injury or health concern.

Injury Prevention & Recovery Two Different Knee Trauma Profiles

The site already covers knee ligament injury and MCL strain in the leg-lock context — heel hooks, kneebars, ashi garami pressure. Standing-context knee trauma is mechanistically different and merits its own page. The injuries look similar on imaging but the prevention strategy is not the same: the leg-lock context is governed by tap timing and partner control of rotation; the standing context is governed by foot fixation, level-change mechanics, and throw-receiver landing posture.

This page covers ACL, MCL, and meniscus mechanisms in standing — throw-receiving, shot-driving, sweep-on-planted-foot, and the specific blast-double loading context. For the leg-lock equivalents, see the dedicated knee-ligament and MCL pages.

The classic non-contact ACL tear in standing happens when the foot is fixed and the body continues to rotate around it. In a no-gi standing exchange, three contexts produce this loading.

Foot sweep on a planted foot. When de-ashi or kosoto strikes a foot that has just become weight-bearing, the sweep direction is across the line of the planted foot. If the receiver’s foot does not release — caught by mat friction, a deep stance, or a sock — the body rotates around a fixed knee. This is the most common standing ACL mechanism in drilling. The fix is technical on both sides: the sweeper aims through the foot, not into it, and the receiver maintains posture that allows the foot to release rather than sticking.

Throw-receiving with a planted leg. Receivers caught mid-throw who post a leg to stop the rotation — instead of going with the throw — load the planted knee with the full angular momentum of a falling body. ACL, MCL, and meniscus all sit in the loading path. The fix is at the receiver: do not post the leg, take the throw.

Pivot-and-cut entries gone wrong. Some judo entries require a quick pivot on a deeply weighted foot. Done correctly, the foot rotates with the hip. Done with a slow foot — wet mat, fatigue, an unaware partner stepping on the toe of the rotating foot — the knee rotates while the foot does not. Most of these injuries are practitioner-driven, not partner-driven, and present in fatigue conditions.

The blast double shoulder-plant injury is well-known (see the dedicated page). What is less commonly noticed is that the same mechanism loads the lead knee. The shooter drives forward, the defender sprawls heavily, the shooter’s lead knee absorbs the combined deceleration of the shooter’s body plus the descending defender’s weight. If the shooter’s lead foot is planted and their hip rotates over it during the failed shot, the loading pattern matches the foot-fixation ACL mechanism above.

The signal for shooters: lead-knee soreness in the days after a heavy sprawl session is not normal training fatigue. It is a load alarm. Repeated exposure without modification is how shooters develop chronic knee issues mid-career.

The MCL is loaded by valgus force — pressure pushing the knee inward while the foot is fixed. In standing, this happens when an opponent’s body weight or sweeping action pushes the lower leg laterally while the upper leg is still loaded. Common contexts: a knee-tap that catches the knee at the wrong angle, an inside-trip that pulls the receiver’s leg outward against a loaded standing leg, a body-lock takedown where the receiver’s legs separate and the inside knee absorbs the lateral spread.

MCL strains heal more reliably than ACL tears, but they accumulate. A practitioner with two or three minor MCL events in a year is on a path to a more significant injury and should look at the specific mechanism that recurs — which throw, which shot defence, which partner type — rather than assume it will resolve itself.