Intuition What this page is for
The parent derivation gave us two formulas:
a = m 1 + m 2 ( m 1 − m 2 ) g , T = m 1 + m 2 2 m 1 m 2 g .
Here we stress-test them. We march through every kind of case these formulas can face — heavy-left, heavy-right, equal, one mass zero, one mass huge, a real experiment, and an exam twist that adds an external pull. If you can do all of these, no Atwood problem can surprise you.
Before anything, two reminders in plain words:
a (acceleration) means "how fast the speed changes each second", measured in m/s 2 .
T (tension) means "how hard the rope pulls", measured in newtons (N = kg ⋅ m/s 2 ).
g is the strength of gravity near Earth, g ≈ 10 m/s 2 (we use 10 for clean numbers unless told otherwise).
Every Atwood problem falls into one of these case classes . The examples below fill every row.
#
Case class
What is special
Example
A
Heavy on left (m 1 > m 2 )
a > 0 , motion as assumed
Ex 1
B
Heavy on right (m 1 < m 2 )
a < 0 — sign tells you it moves the other way
Ex 2
C
Equal masses (m 1 = m 2 )
Degenerate: a = 0 , static
Ex 3
D
One mass zero (m 2 = 0 )
Degenerate: free fall, T = 0
Ex 4
E
One mass huge (m 1 ≫ m 2 )
Limiting value: a → g , T → 2 m 2 g
Ex 5
F
Real-world / measure g
Nearly equal masses, timing experiment
Ex 6
G
Kinematics follow-up
Use a in s , v , t equations
Ex 7
H
Exam twist: extra applied force
Formula must be re-derived, not memorised
Ex 8
Worked example Example 1 (Cell A)
m 1 = 6 kg (left), m 2 = 2 kg (right), g = 10 m/s 2 . Find a and T .
Forecast: Left is heavier, so left falls. Guess: is a closer to g or closer to 0 ? (The mass ratio is 3 : 1 , fairly lopsided — expect a well above zero, but not full g .)
Step 1 — Identify the driving force. The net pull is the weight difference ( m 1 − m 2 ) g = ( 6 − 2 ) ( 10 ) = 40 N .
Why this step? From the parent note, gravity on the two sides fights across the pulley; only the difference drives the system.
Step 2 — Identify the inertia. Total mass being moved = m 1 + m 2 = 8 kg .
Why this step? Both masses must accelerate together, so the rope has to shove 8 kg of stuff.
Step 3 — Divide.
a = 8 40 = 5 m/s 2 .
Why this step? a = total mass driving force is just F = ma for the whole system.
Step 4 — Tension.
T = m 1 + m 2 2 m 1 m 2 g = 8 2 ( 6 ) ( 2 ) ( 10 ) = 8 24 ( 10 ) = 30 N .
Why this step? Direct substitution into the boxed formula.
Verify: Check on the light mass m 2 (moving up): net up force = T − m 2 g = 30 − 20 = 10 N , and m 2 a = 2 ( 5 ) = 10 N ✓. Note 30 N lies between m 2 g = 20 and m 1 g = 60 — as tension always must. Units: N ✓, m/s 2 ✓.
Worked example Example 2 (Cell B)
Same setup but now m 1 = 2 kg (left), m 2 = 6 kg (right). We stubbornly keep the parent's convention: left (m 1 ) assumed to go down , positive.
Forecast: We assumed wrong — the heavy side is on the right now. What sign should a come out?
Step 1 — Plug into the formula unchanged.
a = m 1 + m 2 ( m 1 − m 2 ) g = 8 ( 2 − 6 ) ( 10 ) = 8 − 40 = − 5 m/s 2 .
Why this step? We do not re-guess the direction. We trust the algebra to correct us.
Step 2 — Read the sign. a = − 5 m/s 2 . The minus means "m 1 actually accelerates up , not down" — exactly opposite to our assumption.
Why this step? A negative answer under a chosen positive direction always means "reality points the other way." This is the whole reason we're allowed to guess the direction freely.
Step 3 — Tension is unaffected by the sign.
T = 8 2 ( 2 ) ( 6 ) ( 10 ) = 30 N .
Why this step? Tension depends on 2 m 1 m 2 and m 1 + m 2 , both symmetric — swapping the masses can't change T . Same 30 N as Example 1.
Verify: Magnitude of a is 5 m/s 2 , same as Example 1 — because it's the same two masses , just mirrored. Physics can't care which side you labelled "1". ✓
Common mistake "A negative
a means I made an error."
Why it feels wrong: Accelerations "should" be positive, right?
Why it's fine: a < 0 only means opposite to your chosen positive direction . It is the formula politely correcting your guess. Keep it; don't flip signs mid-solution.
Worked example Example 3 (Cell C)
m 1 = m 2 = 4 kg , g = 10 m/s 2 .
Forecast: Balanced buckets. Guess a before reading on.
Step 1 — Acceleration.
a = 8 ( 4 − 4 ) ( 10 ) = 8 0 = 0 m/s 2 .
Why this step? Zero weight difference → zero driving force → no acceleration. The system is in equilibrium .
Step 2 — Tension.
T = 8 2 ( 4 ) ( 4 ) ( 10 ) = 8 32 ( 10 ) = 40 N .
Why this step? With a = 0 , each side is simply held up: T = m g = 4 ( 10 ) = 40 N ✓ — consistent.
Verify: For either mass: T − m g = 40 − 40 = 0 = m ⋅ 0 ✓. Static: the rope pulls exactly as hard as the weight, nothing accelerates.
Worked example Example 4 (Cell D)
m 1 = 3 kg , m 2 = 0 kg (nothing on the right). g = 10 .
Forecast: With nothing to hold it back, what should m 1 do?
Step 1 — Acceleration.
a = 3 + 0 ( 3 − 0 ) ( 10 ) = 3 30 = 10 m/s 2 = g .
Why this step? No opposing mass → the only inertia is m 1 's own, and the only force is its own weight → it's just free fall .
Step 2 — Tension.
T = 3 2 ( 3 ) ( 0 ) ( 10 ) = 0 N .
Why this step? A rope tied to nothing pulls with nothing. There's no second mass to react against, so it can't build any tension.
Verify: m 1 g − T = 30 − 0 = 30 = m 1 a = 3 ( 10 ) ✓. This is the sanity check the parent note forecast — and here we've worked the numbers .
Worked example Example 5 (Cell E)
m 1 = 1000 kg , m 2 = 1 kg , g = 10 . What does a approach, and what does T approach?
Forecast: The huge mass basically falls freely and yanks the tiny one up. Predict a and the upward acceleration the small mass feels.
Step 1 — Acceleration.
a = 1001 ( 1000 − 1 ) ( 10 ) = 1001 9990 ≈ 9.98 m/s 2 .
Why this step? As m 1 dwarfs m 2 , the fraction m 1 + m 2 m 1 − m 2 → 1 , so a → g . The heavy mass is nearly in free fall.
Step 2 — Tension.
T = 1001 2 ( 1000 ) ( 1 ) ( 10 ) = 1001 20000 ≈ 19.98 N .
Why this step? As m 1 → ∞ , m 1 + m 2 2 m 1 m 2 → m 1 2 m 1 m 2 = 2 m 2 , so T → 2 m 2 g = 2 ( 1 ) ( 10 ) = 20 N .
Step 3 — Interpret the small mass. Net up force on m 2 : T − m 2 g ≈ 19.98 − 10 = 9.98 N , giving it ≈ 9.98 m/s 2 upward — nearly g upward. It feels a "2 g " world: gravity g down plus tension pulling it up at nearly 2 g .
Why this step? This makes the limit tangible: an infinitely heavy driver accelerates the tiny mass at essentially g against gravity.
Verify: a = 9990/1001 ≈ 9.980 , T = 20000/1001 ≈ 19.980 ; both approach the predicted limits g and 2 m 2 g ✓.
Worked example Example 6 (Cell F)
Atwood's original trick: make masses nearly equal so acceleration is small and easy to time. Take m 1 = 0.520 kg , m 2 = 0.480 kg . In an experiment the system falls h = 0.500 m from rest in t = 1.010 s . Estimate g .
Forecast: Will measured g come out near 9.8 ? What tiny acceleration do we expect?
Step 1 — Get a from the timing (kinematics). From rest, h = 2 1 a t 2 , so
a = t 2 2 h = ( 1.010 ) 2 2 ( 0.500 ) = 1.0201 1.000 ≈ 0.9803 m/s 2 .
Why this step? We can measure distance and time directly; acceleration is inferred from them.
Step 2 — Relate a to g via the Atwood formula. Solving a = m 1 + m 2 ( m 1 − m 2 ) g for g :
g = a ⋅ m 1 − m 2 m 1 + m 2 = 0.9803 ⋅ 0.040 1.000 .
Why this step? The machine amplifies g into a measurable a ; we invert that amplification to recover g .
Step 3 — Compute.
g ≈ 0.9803 × 25 = 24.5 m/s 2 .
Hmm — that's far too big! The point: with m 1 − m 2 m 1 + m 2 = 25 , any small timing error is multiplied by 25 . Real experiments use much finer timing. With the ideal g = 9.8 , the true acceleration would be a = 9.8/25 = 0.392 m/s 2 , giving t = 2 h / a = 1.000/0.392 ≈ 1.597 s .
Why this step? This shows the real design trade-off: nearly-equal masses give a slow, timeable fall, but demand precise timing because the amplification factor is huge.
Verify: With ideal values: a = 0.392 m/s 2 from g = 9.8 ; then t 2 = 2 h / a = 1.000/0.392 = 2.551 , t ≈ 1.597 s ✓. See Hinglish note for the same idea narrated.
Worked example Example 7 (Cell G)
Back to Example 1 (a = 5 m/s 2 ). Starting from rest, find (i) the speed after 2 s and (ii) the distance fallen in that time.
Forecast: Constant acceleration 5 m/s 2 for 2 s — roughly how fast, roughly how far?
Step 1 — Speed. With u = 0 , v = u + a t = 0 + ( 5 ) ( 2 ) = 10 m/s .
Why this step? Once a is known and constant (masses don't change), ordinary kinematics applies — the machine's job was just to hand us a .
Step 2 — Distance. s = u t + 2 1 a t 2 = 0 + 2 1 ( 5 ) ( 2 2 ) = 2 1 ( 5 ) ( 4 ) = 10 m .
Why this step? Same constant-a kinematics; area under the velocity line.
Verify: Cross-check with v 2 = u 2 + 2 a s : 1 0 2 = 0 + 2 ( 5 ) ( 10 ) = 100 ✓. Units: m/s and m ✓.
Worked example Example 8 (Cell H)
An examiner adds a downward force F = 10 N pulling on the left mass in addition to gravity. Masses m 1 = 4 kg (left), m 2 = 2 kg (right), g = 10 . Find a .
Forecast: The plain formula no longer applies — why not? You must re-derive . Will a be bigger or smaller than the no-F case?
Step 1 — Write Newton's law for each mass (left assumed down = +).
Left: m 1 g + F − T = m 1 a .
Right: T − m 2 g = m 2 a .
Why this step? The extra F is a new term the boxed formula never accounted for, so we go back to Newton's Second Law and Free Body Diagrams and rebuild the equations from scratch.
Step 2 — Add to cancel T .
m 1 g + F − m 2 g = ( m 1 + m 2 ) a .
Why this step? Same trick as the parent derivation: + T and − T cancel on adding.
Step 3 — Solve.
a = m 1 + m 2 ( m 1 − m 2 ) g + F = 6 ( 4 − 2 ) ( 10 ) + 10 = 6 20 + 10 = 6 30 = 5 m/s 2 .
Why this step? The driving force now includes F ; the inertia m 1 + m 2 is unchanged. Bigger than the F = 0 case (a = 20/6 ≈ 3.33 ), as expected — you added a helping pull.
Step 4 — Tension. From the right equation, T = m 2 ( g + a ) = 2 ( 10 + 5 ) = 30 N .
Why this step? With a known, plug into either single-mass equation; the simplest is m 2 's.
Verify: Left equation: m 1 g + F − T = 40 + 10 − 30 = 20 = m 1 a = 4 ( 5 ) ✓. The lesson: memorised formulas break the moment a new force appears — always be ready to re-derive.
Recall The one habit that beats every scenario
Guess a positive direction, write F n e t = ma for each mass, add to kill tension. That single procedure solved cells A–H, including the ones where the boxed formula didn't apply. See Constraint Relations for why "same a " is legitimate every time.