ARCHETYPE: Two Blocks & a Spring
Every elastic collision you have ever solved is secretly a spring problem played too fast to watch. When two steel balls "bounce," they really compress like stiff springs for a few microseconds, store the collision's energy as deformation, and then pay every joule back as they un-squash. This archetype slows that movie down until you can see every frame: put an actual spring on the front of one block, slide another block into it, and the whole hidden anatomy of a collision — the compression, the moment of maximum squeeze, the rebound — stretches out over visible fractions of a second. The setup earns its place in JEE papers because it forces the one question students dodge: what exactly is conserved, and when? Momentum: always — the spring's pushes are internal to the two-block system. Kinetic energy: only at the ends of the story, when the spring is relaxed; in between, some of it hides in the spring as elastic potential energy. And the star moment — maximum compression — happens at the exact instant the blocks move with a common velocity, because the spring stops compressing only when the blocks stop approaching each other. Master this and you get three archetypes for one: run it forward, it is an elastic collision in slow motion; latch the spring at full squeeze, it becomes a perfectly inelastic collision with the "lost" energy visibly stored; run it backward from a compressed start, it is an explosion. One spring, the whole momentum chapter.
- Block (speed ) slides into a light spring (constant ) mounted on block at rest, on a smooth floor. Momentum is conserved throughout — the spring is internal.
- Maximum compression happens when both blocks move with the common velocity — the instant the approach stops.
- Energy hidden in the spring at that moment: , so with .
- The spring then pays everything back: the blocks separate with exactly the elastic-collision velocities.
- Latch the spring at full squeeze → perfectly inelastic outcome, with the "lost" KE stored, not destroyed.
- Released compressed spring between blocks → explosion: speeds inverse to masses.
- Key idea: the spring makes a collision's interior visible — momentum holds at every instant, kinetic energy dips into the spring and returns, and maximum compression coincides with common velocity.
Momentum conservation holds at every instant (); maximum compression occurs when relative velocity vanishes (both blocks at ), storing ( = reduced mass) — and if the spring relaxes again, the encounter finishes as a perfectly elastic collision.
Where this lives today
Railway shunting yards run Example 1 all day: buffer springs between wagons are sized by exactly — the relative-motion energy they must swallow so that couplings survive; the COM of the wagon pair sails on regardless, just as equation (2) says. Spacecraft docking systems are the gentle version: soft-capture rings on the ISS ports are sprung so that an approaching craft compresses, reaches common velocity with the station (frame 2 of the hero figure), and is latched — Example 4's "latch" is literal flight hardware. Vehicle safety engineering splits the same budget the other way: bumpers act as springs (payback, elastic, no damage) for parking-speed hits, while crumple zones deliberately refuse to pay back — converting the relative-motion energy into deformation, an inelastic outcome by design. And at the smallest scale, chemists model molecular collisions as atoms on spring-like potentials: "elastic" bounces and "reactive capture" (a latch made of chemistry) are frames 3 and 2 of this article, run at picosecond speed.
The setup
On a frictionless floor, block (spring of stiffness fixed to its face) rests; block arrives at speed . Find: the common velocity, the maximum compression, and the final velocities after separation. Variants: spring latched at full squeeze; compressed spring released between two blocks; spring backed by a wall.
The heart of the archetype is one sentence about frame 2: the spring keeps compressing as long as the blocks keep approaching. Compression grows whenever moves faster than ; it shrinks whenever outruns . Maximum squeeze is therefore the turning point where the relative velocity is exactly zero — both blocks momentarily gliding at the same speed. Not " stops" (it never does here), not " hasn't started" (it started the instant the spring touched it): common velocity. From that one insight, momentum hands you and energy hands you , and the problem is over.
The master solution pattern
Momentum, valid at every instant. The spring's forces are internal to the pair, the floor is smooth, so at any moment:
where: — the instantaneous velocities. This is a running conservation law, not just a before/after statement — you may deploy it at maximum compression, at half compression, anywhere.
The common velocity at maximum squeeze. Setting in (1):
where: is also the velocity of the centre of mass — it must be, since at that instant the system moves as one piece. The blocks never both stop (momentum forbids it); they sail together at while the spring holds its maximum charge.
Energy at maximum squeeze. Kinetic energy is conserved plus spring energy: comparing the start with the moment of max compression,
where: the combination (the reduced mass) does the bookkeeping in one stroke: the storable energy is exactly the energy of relative motion, — the centre-of-mass share is untouchable, protected by momentum conservation. Hence
The payback. The compressed spring now accelerates and decelerates until it returns to natural length — at which point it has repaid every joule (light spring, no friction). Momentum (1) plus full kinetic-energy recovery is precisely the definition of an elastic collision, so the exit velocities are the standard elastic results:
where: for , is negative — the light block bounces back. Equal masses swap: , , the collision chapter's exchange rule, now visible in slow motion.
| variant | what changes | result |
|---|---|---|
| standard (spring on 's face) | — | eqs. (2)–(5) |
| spring latched at max squeeze | energy stays stored | inelastic outcome: both at ; spring holds |
| latch released later | stored energy repaid | final velocities still (5) — timing irrelevant |
| compressed spring released from rest | explosion | ; energies inverse to masses |
| spring backed by a wall | momentum NOT conserved | energy alone: |
| spring attached to BOTH blocks | they never separate | oscillation about the COM; velocities trade periodically |
We prove the two pillars — that maximum compression coincides with common velocity, and that the storable energy is — because both are asserted-by-habit in solutions and JEE tests whether you know why. Strategy: track the compression through the relative velocity, then split the kinetic energy into a centre-of-mass part and a relative part and watch momentum conservation freeze the first. Keep an eye on what the spring can and cannot touch.
Step 1. Compression grows with approach. The spring's length shortens at the rate at which the blocks close in: the compression increases while , decreases while . At the maximum, the rate of change is zero:
Why this is airtight: is a running total of (approach speed × time); a running total peaks exactly when the thing being totalled crosses zero. No forces, no calculus formalities — just the definition of compression.
Step 2. Momentum fixes . Equation (1) with both velocities equal: — which is the centre-of-mass velocity, constant from the first touch to the last. The blocks momentarily ride along with their own COM.
Step 3. Split the kinetic energy. Quite generally, the pair's kinetic energy separates into a COM part plus a relative part:
(Substituting and and expanding reproduces — a two-line algebra check worth doing once in your life.)
Step 4. Watch what the spring can touch. Momentum conservation keeps constant, so the COM share is locked — no internal force can raise or spend it. The spring trades only with the relative share, initially (since at the start). At maximum compression : the relative share sits entirely in the spring:
Step 5. The payback and the elastic ending. As the spring re-extends it returns the stored energy to the relative motion; at natural length has recovered its full magnitude but reversed in direction (the blocks now separate as fast as they once approached — the signature). Momentum plus reversed relative velocity is exactly the elastic-collision system, giving (5). Verified: numbers — , kg, m/s, N/m: m/s; COM share J; relative share J ✓; m ✓. Limits: : , , wall formula recovered; : , the invisible-spring (instant collision) limit.
Limiting cases
| case | result | meaning |
|---|---|---|
| (wall) | , | all KE storable — the wall version's licence |
| ; half the KE stored at max squeeze | then full exchange: , | |
| very stiff | tiny , brief contact | the hidden spring of "instant" elastic collisions |
| very soft | large, slow squeeze | same energies, gentler forces, longer contact |
| latched at | both blocks at for good | perfectly inelastic, with the loss visibly banked |
| spring attached to both | no separation, SHM about COM | velocities oscillate between and |
Worked examples
1 · Board level — common velocity and maximum compression (full method)
A block moving at on a smooth floor runs into a light spring () mounted on a stationary block. Find (a) the velocity of each block at maximum compression, (b) the maximum compression.
Step 1. At maximum compression the blocks share a common velocity (approach has paused). Momentum: — both blocks.
Step 2. Energy audit at that instant. Initial KE: J. KE at common velocity: J. Stored in the spring: J.
Step 3. Compression: , so (about 24.5 cm).
Step 4. Shortcut check via reduced mass: kg; J ✓ — one line instead of three.
2 · Board level — the spring as an explosion (release from rest)
A spring compressed by () is held between blocks of and on a smooth floor, everything at rest. The system is released. Find each block's final speed.
Step 1. Stored energy: J. Momentum from rest: (opposite directions), so .
Step 2. Energy: . Substitute : , so .
Step 3. , , opposite ways. Audit: energies J and J — inverse to the masses, the explosion module's split, with the spring as the "charge."
3 · Competitive level — the final velocities (JEE-Main pattern, ~3 minutes)
In the setup of Example 1 ( kg at m/s, kg at rest), the spring re-extends and the blocks separate. Find the final velocity of each block.
Step 1. Recognize the ending: light spring returns all its energy ⇒ momentum conserved and kinetic energy fully recovered ⇒ elastic collision in slow motion. Use the standard results.
Step 2. — the light block rebounds.
Step 3. .
Step 4. Audits: momentum ✓; energy J ✓; separation speed = approach speed ✓ (). Timing note: ~2 min if you spot "elastic in disguise" and quote (5); ~6 min if you re-derive from scratch. The tell is always "light spring" + "smooth floor" + "after the blocks separate." Don't re-solve what the collisions module already solved.
4 · Competitive level — JEE-Advanced stretch: the latch (~4 minutes)
Same collision again, but at the instant of maximum compression a latch locks the spring. (a) Describe the motion now. (b) The latch is released much later. Find the final velocities and comment on the timing.
Step 1. Locked at max squeeze: the pair moves as one body at m/s, carrying KE J, with J banked in the latched spring. This is a perfectly inelastic collision whose "lost" energy is stored instead of burned — the latch is what looks like when nothing is allowed to become heat.
Step 2. On release (wherever, whenever): the spring pushes the blocks apart, spending its 24 J on their relative motion while momentum stays . These are the same two conservation statements as the unlatched story.
Step 3. Same equations, same answers: , .
Step 4. The moral, which is the actual JEE-Advanced content: the final state depends only on the conserved totals (momentum , energy J), not on the schedule of storage and release. Latch it for a second or a year — physics does not bill by the hour. Timing note: ~3 min once you see that release restores the elastic budget. The distractor answer treats the latched phase as "energy lost" and applies inelastic formulas to the ending — but the latch stores, it does not burn.
Exam traps
Wall formula on a free block. is legal only when the spring is backed by a wall/infinite mass. For a free , subtract the untouchable COM energy first — or jump straight to .
"Maximum compression = block 1 stops." It never stops mid-encounter (unless after separation, which is a different moment). Max squeeze = common velocity = COM velocity. Write as the working line.
Forgetting the encounter ends elastic. After the spring relaxes, don't invent new physics: quote the elastic-collision results (5). Equal masses exchange; light block off heavy block rebounds; heavy block barely notices — all inherited intact.
Reduced-mass slips. — the product over the sum, always smaller than either mass. Writing the sum over the product (or using ) inflates the stored energy. Sanity: for equal masses .
Signs after separation. is negative when . Carry the sign; "speed" answers then need the magnitude, and momentum audits need the sign. The rebound direction itself is a favourite one-mark MCQ.
Attached versus resting. A spring merely resting against (or the incoming block) pushes but cannot pull: the story ends at natural length with the elastic outcome. A spring attached to both blocks pulls back past natural length — the blocks never separate and oscillate about their COM forever. Read the mounting before predicting the ending.
Impulsive-force reflex. There is nothing "sudden" here — forces are finite (), contact lasts visible time. Do not import collision-time approximations; conversely, this is why the floor must be stated smooth: over a long contact, friction would have time to act (unlike in the bullet-block impact).
Origins · 1 minRobert Hooke and how this was discovered
Hooke published his spring law in 1676 as an anagram — ceiiinosssttuv — staking priority while he kept experimenting; unscrambled two years later, it read ut tensio, sic vis: as the stretch, so the force. That linear law, , is why this archetype is exactly solvable: linear force means quadratic energy , and the whole encounter reduces to two conservation lines. Hooke was the great mechanic of the early Royal Society — city surveyor after the Great Fire, microscopist who coined the word "cell," Newton's most bitter rival — and his law turned out to be the small-deformation truth of all solids: the steel balls, railway buffers and colliding atoms that "bounce elastically" are all running Hooke's law in miniature, storing and returning energy exactly as the visible spring does here.
Going further
Texts. HC Verma, Concepts of Physics Vol. 1, Ch. 9 (the two-blocks-and-spring family in worked examples and exercises) · NCERT Physics Class 11, Ch. 6 · Kleppner & Kolenkow, Ch. 4 (collisions and the centre-of-mass frame). For the frame-based view of this archetype: Centre-of-Mass Frame Collisions (UG deep dive).
Provenance. All results are standard. A verifier should recompute: Example 1's chain ( m/s, stored 24 J, m) and the kg shortcut; Example 2's explosion split ( and m/s, energies 2:1); Example 3's elastic exit (, m/s) with all three audits; the KE decomposition identity of Derivation A Step 3 by direct expansion.
Prerequisites. Elastic Collisions in 1D · Spring Force & Hooke's Law · Conservation of Linear Momentum. Leads to. Which Conservation Law? (technique) · Centre-of-Mass Frame Collisions (UG deep dive).
Why exactly does maximum compression happen at common velocity?
Because compression is accumulated approach. The spring shortens at the rate (how fast the blocks close in); its length is the running total of that rate. A running total peaks when the rate crosses zero — that is, when . After that instant the rear block is slower than the front block, the gap grows, and the spring re-extends. No dynamics needed: it is the same logic as "your bank balance peaks when deposits stop exceeding withdrawals."
Is momentum really conserved even while the spring is pushing?
Yes — at every instant. The spring pushes backward and forward with equal magnitudes (Newton's third law through a massless spring), so the pair's total momentum never budges: from first touch to final separation. This is stronger than the usual "before and after" statement, and exam questions exploit it: "find when the spring holds 10 J" is solvable precisely because momentum holds mid-encounter too.
What is the reduced mass really doing here?
It converts a two-body problem into a one-body summary. The pair's kinetic energy always splits as (COM part) + (relative part), and the relative part is with — as if the relative motion belonged to a single fictitious particle of mass . Since internal forces can only touch relative motion, tells you instantly how much energy is up for grabs: storable in springs, losable in inelastic collisions (), transferable in encounters. It is the momentum chapter's best shortcut and the rotation chapter will hand you its twin.
What changes if the spring is attached to both blocks?
The ending. Everything up to natural length is identical — but an attached spring can pull, so as the blocks try to separate the spring stretches and hauls them back. Result: no separation, ever; the blocks oscillate about their common centre of mass (which drifts at ), trading velocities periodically between and . In the COM frame it is pure SHM with effective mass , angular frequency — a preview of the oscillations chapter riding on this module's algebra.
Does the stiffness k affect the final velocities?
No — and that is worth internalizing. sets the choreography: stiff spring, small , quick encounter; soft spring, deep slow squeeze. But the final velocities come from momentum + full energy return, and both are -blind. This is exactly why "instantaneous" elastic collisions can be solved without knowing anything about the contact forces: the invisible atomic springs have some enormous , and it cancels out of the answers just as it does here.
Real springs have mass. How bad is the "light spring" idealization?
For exam setups, excellent. A spring of mass carries some kinetic energy of its own (roughly a third of moves with the contact end), so a real encounter returns slightly less than 100% to the blocks and the outcome is very slightly inelastic. With a few percent of the block masses, corrections are below the precision of any answer you'd give. The idealization to actually watch is the floor: any friction acts throughout the long contact and genuinely breaks the momentum bookkeeping — which is why the problem always says "smooth."