1.3.13 · D5Work, Energy & Power

Question bank — Spring-mass systems — collision problems

2,124 words10 min readBack to topic

Before we start, let's re-anchor every symbol we lean on, so nothing appears unearned. Here is the setup this whole page talks about — two blocks on frictionless ice with a spring between them:

Figure — Spring-mass systems — collision problems
Figure — Spring-mass systems — collision problems

True or false — justify

TF1. During the instant of contact in a spring collision, kinetic energy is conserved.
False as a general claim — the spring force is the contact force, and at the very first instant the spring is barely squished, so that force (with ) and its impulse are tiny; almost no momentum or energy has been exchanged yet. You track the encounter by momentum, and KE is only conserved across the whole encounter because the ideal spring later returns everything it stored.
TF2. The spring is maximally compressed exactly when the incoming block is momentarily at rest.
False — it is maximal when both blocks share the same velocity (), i.e. relative velocity is zero. The incoming block is usually still moving then.
TF3. For two free blocks joined by an ideal spring, the overall outcome is a perfectly elastic collision.
True — an ideal spring stores KE then returns 100% of it, so the before-and-after KE match, which is the definition of elastic (see Elastic and Inelastic Collisions).
TF4. Momentum is conserved when a block hits a spring that is bolted to a wall.
False — the wall supplies an external horizontal force, so momentum is not conserved; only mechanical energy is.
TF5. At maximum compression the system has zero kinetic energy.
False — the whole system still drifts at , so it keeps the drift KE . Only the relative-motion KE, , is stored in the spring.
TF6. If a clip latches the spring at maximum compression, the encounter becomes perfectly inelastic.
True — the blocks are locked together moving at , and the stored is trapped forever, which is exactly the inelastic signature.
TF7. Reversing the roles of and changes the maximum compression.
False — depends on the relative speed and the symmetric (swapping leaves unchanged), so the depth is the same.
TF8. If both blocks start with the same velocity, the spring still compresses a bit before pushing back.
False — with zero relative velocity from the start, the gap never shrinks, so . Nothing compresses.

Spot the error

SE1. "Spring is ideal, so energy is always conserved — so during the collision I'll use ."
The error is timing: you cannot equate initial KE to spring PE at first contact, where and almost nothing has been exchanged. Energy is only clean once you correctly track the stored PE across the full compression and subtract the drift KE.
SE2. "Two free blocks: all the KE goes into the spring, so ."
Wrong — the system still moves at , carrying drift KE that can't be stored. Only the CM-frame part becomes spring PE; you must subtract .
SE3. "Max compression happens when the target block reaches its top speed."
The target's speed peaks after max compression, when the spring is pushing it forward. Compression peaks at equal velocities, before the spring re-expands.
SE4. "The block bounces off a wall-spring with more speed than it came in, because the spring pushes it."
No — an ideal spring returns exactly the energy it stored, so the block leaves at the same speed it arrived (reversed direction). Gaining speed would violate energy conservation.
SE5. "For the wall case (a single block of mass at speed hitting a wall-fixed spring) I should still write to find a common velocity ."
There is no second free body to share momentum with, and the wall makes momentum non-conserved, so that equation is meaningless here. The correct tool is energy: .
SE6. "Since is smaller than either mass, less energy is stored than you'd expect — that means energy is lost."
No energy is lost; is simply the correct effective mass for relative motion. The "missing" KE isn't destroyed — it's the drift KE that was never available to store.
SE7. "A light block () that hits a heavier one can never end up moving backward, so a negative final velocity must be a mistake."
A light block striking a heavier one genuinely rebounds; the elastic result is negative when , and the minus sign just means leftward. Momentum and energy both check out, so the rebound is real.

Why questions

WQ1. Why do we split the problem into a "collision phase" and a "compression phase" at all?
Because different forces dominate at different timescales — the huge, brief contact force needs momentum (impulse view), while the slow, finite spring force needs energy. One law per phase, chosen by which force is negligible.
WQ2. Why does the reduced mass appear in but never in ?
is about the whole system's drift, so it uses total mass; is about the blocks' relative squeezing, and relative motion behaves like a single body of mass . See Reduced Mass and Two-Body Problems.
WQ3. Why can we treat the whole spring encounter as elastic without ever computing a coefficient of restitution?
Because "ideal spring returns all stored energy" is the physical content of restitution ; the spring mechanism guarantees the elastic result by construction.
WQ4. Why is the moment of maximum compression the natural place to apply momentum conservation?
At that instant both blocks share one velocity, turning into a single-unknown equation — the cleanest snapshot the problem offers.
WQ5. Why does energy conservation fail during an ordinary (non-spring) inelastic collision but succeed across a full spring encounter?
Inelastic collisions convert KE into heat/deformation (unrecoverable); an ideal spring only borrows KE as recoverable elastic PE and hands it all back.
WQ6. Why does looking at the problem in the Centre of Mass Frame make the stored energy obvious?
In that frame the total momentum is zero, so at max compression everything is momentarily still and all the frame's KE — exactly — sits in the spring.
WQ7. Why is the max-compression formula the same whether the spring later releases or gets latched?
The compression phase up to the turning point is identical physics either way; latching or releasing only decides what happens after the peak, not how deep the squeeze got.

Edge cases

EC1. What is if (both blocks moving together)?
Zero — the relative approach speed , so ; they simply coast together.
EC2. What happens to as the spring stiffness ?
— an infinitely stiff spring barely compresses, and the encounter looks like an instantaneous elastic bounce.
EC3. What happens if (target immovable, like a wall)?
and , recovering the wall case: with all of block 1's KE stored.
EC4. What if in the two-free-block elastic result?
The blocks swap velocities — the incoming block stops dead and the target moves off at , since .
EC5. Two blocks with a spring attached to block 2's front face (so contact is only made if block 1 catches up): what happens if they start moving apart, ?
Since block 1 is falling behind, its face never presses the free end of the spring, so no compression occurs and the blocks simply drift apart unchanged. (If instead the spring were glued to both blocks, moving apart would stretch it — a different, tension problem outside this note.)
EC6. As (spring vanishingly soft), what does predict, and is it physical?
Mathematically , but that's an idealisation: a real spring has a finite length and coils that eventually touch (or the blocks collide), so the formula only holds while the spring behaves ideally. Practically, a very soft spring means a huge but bounded squeeze and a very gentle, slow interaction.
EC7. What is if the blocks have equal masses and equal-but-opposite velocities ()?
Zero — total momentum cancels, so at max compression both are momentarily at rest and the entire initial KE, , is stored (the Centre of Mass Frame and lab frame coincide here).

Recall One-line survival kit

MEME + Max squish = Same swish. Momentum during the Moment; Energy for the Expansion; and the deepest squeeze is when both blocks swish at the same speed. Everything on this page is a consequence of those two lines.


Connections