ARCHETYPE: Energy Accounting on Rough Inclines
Kick a block up a rough ramp and clock it as it slides back down to your foot. It returns — but noticeably slower than it left. Nothing mysterious happened up there: gravity took its usual refundable toll, but friction charged the block twice — once fighting the climb, once resisting the descent — and pocketed both payments as heat. That asymmetry between the up leg and the down leg is the entire archetype: one incline, two different decelerations, two different ledgers, and a family of exam questions that all reduce to auditing them. The family is large and worth owning. How far up does it go? — a budget where gravity and friction gang up. Does it come back at all? — a static-friction interrogation at the top. How fast does it return? — the famous ratio that depends only on and , not on mass or launch speed. How much heat was generated? — friction's toll times the odometer, never the altitude. And the workhorse of warehouses: what does it cost to push a crate up at constant speed, and what fraction of that work was "useful"? — the ramp graded like a machine, with an efficiency. Board papers ask the legs separately; JEE chains them — up, interrogate, down, flat run-out, total heat — in one sweep. The master pattern below runs any such chain with two lines per leg.
- Going up a rough incline, gravity and friction both oppose: deceleration ; stopping distance .
- At the top, the block slides back only if gravity beats static friction: . Otherwise it parks on the slope.
- Coming down, friction switches sides: — the asymmetry.
- Return speed ratio (same start and end point): — independent of mass AND of launch speed.
- Heat generated (total path slid) — the odometer bill; it also equals the mechanical energy that went missing.
- Pushing a crate up at constant speed costs ; the ramp's efficiency as a machine is .
- Key idea: on a rough incline the two legs have different books — friction joins gravity on the way up and fights it on the way down — so audit each leg separately and let heat = friction × path close every budget.
Energy accounting on a rough incline splits into legs: ascending, the block pays both and ; at the top static friction decides whether it returns; descending, gravity's refund is taxed by the same friction — so the return is always slower by the factor , and the round trip's missing energy equals exactly times the total distance slid.
Where this lives today
The up-leg budget saves lives on mountain highways: runaway-truck escape ramps are inclines of deep gravel engineered so that — with rolling gravel pushing the effective near 0.25–0.4 — stops a brakeless 40-tonne truck from 130 km/h in under 200 m; the two-bill structure (altitude + "friction") is the design equation, and the parked-forever condition is a feature, not a bug. Ski-run designers run the opposite optimization, grooming snow () and profiling slopes so the descent budget delivers thrilling-but-survivable speeds into engineered flat run-outs. Warehouse ramp specs quote exactly example 3's efficiency, deciding between ramps, lifts and conveyors. And electric trucks on ghat roads now cash the down-leg's refund electrically: regenerative descent recovers the that Rumford's brakes would have boiled away.
The setup
Geometry first. An incline at angle , coefficient of friction (take unless the paper splits them). A block of mass either (a) is projected up the slope at , (b) slides down from rest, or (c) is pushed up at constant speed by a worker. The normal force everywhere on the slope is , so friction's magnitude is fixed at — but its direction flips with the motion: down-slope while the block climbs, up-slope while it descends. That flip is the archetype.
Two readings organize everything. First, each leg is a one-line budget. Up: the launch kinetic energy is spent on two bills, altitude () and heat (). Down: gravity's refund () is taxed by the same heat bill before it becomes speed. Second, the top of the climb is a checkpoint, not a formality: a block at rest on a slope stays at rest unless exceeds static friction's ceiling — the condition , the angle-of-repose test from the friction modules, now embedded mid-problem. Every full-marks solution runs it before computing any descent.
The master solution pattern
Per leg, write the energy (or force) line; at the summit, interrogate; then chain.
Up leg — projected at , stops after slope distance :
where: the two bills share the same , so they simply add in the bracket. Force language says the same thing: , then — use whichever the question's variables invite.
Summit interrogation:
where: the comparison is dimensionless and mass-free. Papers that give on a slope () intend a return; on the same slope intends a park — and "the block stays; find the friction force holding it" (, not ) is its own classic trap.
Down leg — from rest at distance , arriving back at:
where: dividing (3) by (1) cancels , , — the ratio is pure geometry-and-grip. It is always below 1 (friction changed sides but kept charging), equals 1 only when , and hits 0 exactly at : the returning block that barely doesn't return.
The heat line closes every chain:
where: must also equal the mechanical energy missing from the books — computing it both ways is a free audit, used in every worked example below.
We derive the stopping distance (1) and the return condition (2) as one continuous story: energy methods find where the block stops; force methods decide what happens next. The strategy showcases the archetype's division of labour, and the numbers are chosen to be reused by the examples. Watch the friction force switch roles (kinetic while sliding, static at rest) — same surfaces, different laws.
Step 1. Climbing, the block slides, so kinetic friction acts down-slope, alongside gravity's component . Budget from launch to halt over slope distance :
which is (1). Equivalently , constant, so the kinematics route lands identically.
Step 2. At the halt, sliding stops, and the law changes hands: static friction now supplies whatever it can, up to , to hold the block against gravity's .
Step 3. The verdict is the comparison
Park if static wins; return if gravity wins. Mass cancels; launch speed is irrelevant (it only chose ).
Step 4. If parked, the friction actually acting is — the demanded value, below the ceiling. Quoting for a parked block is the friction chapters' cardinal sin, re-armed on a slope. Why the block cannot "park" mid-slide on the way up: while moving it must decelerate through at a definite point; parking is a question only AT that point, decided by statics, not by the energy budget that located it. *Verified: m/s, , , : m/s², m; summit: → returns. These are worked example 1's numbers.*
Go deeper · Derivation B · 1 minThe asymmetric return and the round-trip heat audit
We derive the return-speed ratio (3) and verify the heat line (4) closes the books. Strategy: fresh budget for the down leg (friction now up-slope), divide by the up-leg budget to kill every shared factor, then count heat two independent ways. The watch-out: the ratio compares speeds at the SAME point (the launch point), which is what lets cancel.
Step 1. Down leg from rest at the summit, over the same slope distance : gravity pays , friction (now up-slope) taxes :
Step 2. Divide by the up-leg line :
(the last form after dividing through by — the exam-speed version). Mass, , , and the launch speed have all left the answer.
Step 3. Heat audit, route one — the odometer: total path , so .
Step 4. Heat audit, route two — the missing energy: the block left with and returned with , same height:
The two routes agree identically — the audit every chained problem should end with. Why the ratio's zero at is physical: there the down-slope pull exactly matches kinetic friction, the "descent" is neutral equilibrium in motion — in practice the block parks (statics already held it at the slightly larger ). The formula's fine print: use it only after interrogation (2) says the block moves. *Verified: , : ratio , so ; for m/s: m/s, and J ✓.*
The variants examiners actually pose
The worker's invoice. Pushing a crate up at constant speed: the applied force (along the slope) must fund both bills continuously, , so . Grade the ramp like a machine: useful output , efficiency — worked example 3.
The composite run. Slope, then flat run-out: chain the legs — descend (leg budget), then flat (), then close with the heat audit; the total heat equals the initial when everything ends at rest — worked example 4's punchline.
The double distance. "It stops after distance up; from there it slides down ": the SAME in both legs is what makes the ratio (3) clean. If the problem re-launches from elsewhere, keep the legs' budgets separate and resist ratio shortcuts.
Split coefficients. Papers that give : kinetic runs the budgets, static runs the summit interrogation — never swap their jobs.
Limiting cases
| case | result | meaning |
|---|---|---|
| ratio ; | smooth slope: symmetric legs, gravity-only budget | |
| parks at summit forever | the angle-of-repose knife edge, mid-problem | |
| (kinetic) | ratio (3) → no return | formula out of domain — interrogation (2) already said "parked" |
| , ratio | a vertical wall has no normal force: friction vanishes with | |
| doubled | quadruples, ratio unchanged | budget scales; the asymmetry is geometry's alone |
| large on flat run-out | stop distance shrinks | the braking module's formula, recovered as a leg |
Worked examples
1 · Board level — how far up, and does it come back? (CBSE/ICSE pattern, 3 marks)
A block is projected at m/s up a incline with . ( m/s², , .) Find (a) the distance it travels up the slope, (b) whether it slides back down.
Step 1. (a) Up-leg deceleration: m/s². Distance: .
Step 2. (b) Summit interrogation: — gravity's pull beats static friction's ceiling: . (State the comparison; the bare "yes" drops a mark.)
2 · Board level — the slower homecoming (ICSE/AP-1 pattern)
For the block of example 1 (mass kg), find (a) its speed on returning to the launch point, (b) the total heat generated over the round trip — computed two ways.
Step 1. (a) Ratio route: , so .
Step 2. (b) Odometer route: N over m: .
Step 3. Missing-energy route: J ✓ — the books close, and writing the check earns the reasoning mark.
3 · Competitive level — the worker's invoice and the ramp's grade (JEE-Main/NEET pattern, ~3 minutes)
A worker pushes a kg crate m up a ramp () at constant speed, force parallel to the ramp. ( m/s².) Find (a) the applied force, (b) the work done by the worker, (c) the heat generated, (d) the ramp's efficiency as a lifting machine.
Step 1. (a) Constant speed → force balance along the slope: .
Step 2. (b) .
Step 3. (c) Heat: . Audit: useful J, and ✓.
Step 4. (d) — equivalently , geometry-and-grip again. Timing note: ~3 min. The designed error is N (friction forgotten — "constant speed" does not mean "no friction"). Note the beautiful bookkeeping: worker's 800 J = 600 J banked as height + 200 J burned; the ramp "wastes" exactly its friction share.
4 · Competitive level — the ski-run composite, closed by one audit (JEE-Advanced flavour, ~4 minutes)
A kg skier starts from rest and descends a slope of length m, then runs onto a horizontal stretch, both with . ( m/s².) Find (a) the speed at the bottom of the slope, (b) the distance travelled on the flat before stopping, (c) the total heat generated — and verify it against the altitude budget.
Step 1. (a) Slope leg: , so .
Step 2. (b) Flat leg: .
Step 3. (c) Odometer heat: slope J; flat J; total .
Step 4. Altitude audit: the skier fell m and ended at rest, so ALL the potential energy became heat: J ✓. When a chain starts and ends at rest, total heat = total drop — the one-line sanity check that catches almost every slip in composite problems. Timing note: ~4 min. Chain discipline: one budget per leg, speeds handed across the joints, heat summed over EVERY leg's own path. The mass was never needed until the joule counts — ratios and distances are mass-free, a structure worth noticing under time pressure.
Exam traps
One deceleration for both legs. Up: ; down: . They differ by ; using either for the other leg poisons everything downstream.
Skipping the summit interrogation. Between the legs sits the statics checkpoint vs . Blocks park more often than students expect — and a parked block's friction is , not .
Heat billed by altitude. path, always. The altitude enters heat only through the special audit "starts and ends at rest ⇒ " — and that is a consequence, not the formula.
Slope distance vs height. and both appear; budgets bill gravity by and friction by . One misplaced swaps them.
"Constant speed" read as "no friction". It means zero net force: the worker's force must carry both and . Example 3's designed error.
The ratio used out of domain. presumes a descent happens. If , the answer is "doesn't return", not a negative ratio.
Mass smuggled into mass-free answers. Stopping distances, the return ratio, the park condition: all mass-free. An option with in them is structurally wrong — the same cancellation drill as the flat-curve archetype.
Normal force taken as . On the slope — the in every friction term. Dropping it converts the archetype into a different (wrong) problem.
Origins · 1 minBenjamin Thompson, Count Rumford and how this was discovered
A Massachusetts-born adventurer who fled the American Revolution, reorganized the Bavarian army, and invented the modern kitchen range, Rumford made his great discovery in a Munich cannon factory in 1798. Supervising the boring of gun barrels, he noticed the brass grew hot for as long as the horses turned the drill — seemingly without limit. Caloric theory said heat was a conserved fluid; a bottomless supply from friction was impossible. Rumford boiled water with a deliberately blunt borer to make the point: friction generates heat from motion, endlessly, at a rate set by the work done. Every line in this archetype is his cannon experiment in miniature — the receipt for mechanical energy that leaves the books.
Going further
Texts. NCERT Physics Class 11, Work, Energy and Power chapter (work done against friction) · HC Verma, Concepts of Physics Vol. 1, Chs. 6 & 8 · Halliday–Resnick–Walker Chs. 6 & 8 (friction + energy accounting).
Provenance. All results are standard. A verifier should recompute: example 1 ( m/s², m, returns since ); example 2 (ratio 0.2, m/s, J both routes); example 3 (160 N, 800 J = 600 + 200, 75%); example 4 ( m/s, 8.0 m, 1800 J = exactly).
Prerequisites. ARCHETYPE: The Block-on-Incline Family · Conservation of Mechanical Energy & Efficiency · Kinetic & Rolling Friction. Leads to. TECHNIQUE: Force Method or Energy Method? · ARCHETYPE: Pumps, Motors & Engine Power (ahead in this unit) · Conservation of Mechanical Energy (UG deep dive).
Why does friction "change teams" between the two legs?
Because kinetic friction has one loyalty: it opposes the relative sliding, whichever way that points. Climbing, the block slides up-slope, so friction acts down-slope — gravity's ally. Descending, the block slides down-slope, so friction acts up-slope — gravity's opponent. The magnitude never changes ( throughout, since the normal force is fixed); only the direction flips. That one flip generates the whole archetype: two decelerations, the asymmetric ratio, and the double-billed heat.
Where does the return-speed ratio's independence from mass and launch speed come from?
From shared structure in the two legs' budgets. Both are (force per unit mass) × (the same distance ): up-leg , down-leg . Dividing kills , — and never appeared, because every force in the problem (gravity's component, friction) scales with . What survives is pure slope-versus-grip: . A heavier block or a harder throw goes further up but comes back with the same fraction of its speed — a scaling worth quoting in MCQs before any arithmetic.
Is the heat really generated in equal amounts going up and coming down?
Over the same distance, yes — each way, since both and match. But note what is NOT equal: the fraction of the leg's energy flow that friction takes. On the way up, friction is one of two drains on a big kinetic budget; on the way down it taxes gravity's smaller refund, taking a proportionally larger bite — which is why the return is so dramatically slower even though the joules burned per leg match. When legs have different lengths (composite runs), bill each leg separately: heat follows the odometer, leg by leg.
What if the problem gives different μ_s and μ_k?
Assign each to its jurisdiction. Kinetic runs every sliding budget — both legs' decelerations and every heat line. Static runs exactly one moment: the summit interrogation vs (and any "does it start moving?" question at the bottom). Since typically, a block can be held at the summit by static friction even on a slope it would slide down once moving — the interrogation must use , and using there manufactures returns that never happen.
Why does the "starts and ends at rest" audit give heat = mgΔh regardless of the path?
Because the overall books must balance. Kinetic energy: zero at both ends, no net change. Potential energy: down by . The only other line in the ledger is heat. So — the drop, converted entirely, whatever the route, however many legs. It is the fastest cross-check in this family: example 4's 1800 J had to be before any leg was computed. If your leg-by-leg heat disagrees with the drop, a leg's odometer (or a joint speed) is wrong.
How is this different from the smooth-incline problems I already know?
Structurally, by one term per leg — but that term breaks every symmetry you were allowed to enjoy. Smooth: one acceleration both ways, return speed equals launch speed, energy conservation in pure form, no summit question (it always returns). Rough: two accelerations, a ratio below one, a damaged budget, and a statics checkpoint mid-problem. The exam's favourite hybrid: a smooth incline with a rough flat run-out (or vice versa) — apply the pure law on smooth legs and the damage term on rough ones, and never let one leg's rules leak into the other.