ARCHETYPE: Two Bodies Under Gravity
Legend says Galileo dropped two balls — one heavy, one light — from the Leaning Tower of Pisa and watched them land together. Whether or not he ever climbed that tower, the idea he proved is the engine of an entire family of exam problems: gravity accelerates every free body identically. Drop a stone and throw another straight up past it; juggle two balls a second apart; release a packet from a rising balloon — in every case, each body obeys the same , no matter which way it happens to be moving. That shared acceleration is a gift examiners cannot resist. A ball dropped from a tower and a ball thrown up from the ground must meet — but when, and where? Two balls thrown up with the same speed one second apart cross at a height that looks magical until you see the symmetry. A packet "dropped" from a climbing balloon first rises — the single most reliable trap in kinematics. CBSE and ISC pose the tower meeting as a 3-mark structured question; JEE-Main and NEET compress it into 90-second MCQs; JEE-Advanced stacks conditions ("they meet exactly when the second ball peaks…") that fall apart instantly once you know the master move. And the master move is almost embarrassingly simple: because both bodies share the same , their relative acceleration is zero — so the gap between them closes at constant speed. This article builds that machine: one axis, one clock, one sign convention, position functions for each body, and the relative shortcut that turns four-line solutions into one.
- Two bodies moving vertically under gravity share the same acceleration — regardless of their velocities' directions.
- Master setup: ONE origin, ONE positive direction (up), ONE clock. Each body gets a position function ; they meet when .
- The killer shortcut: relative acceleration is zero, so the gap closes at constant relative speed — meeting time initial gap relative speed.
- Drop from height + simultaneous upward throw at : they meet at , always.
- A body released from a rising platform inherits the platform's upward velocity — it rises before it falls.
- Key idea: shared makes the relative motion of two free bodies uniform — set the position functions equal, or let the gap close at constant speed.
Because every freely moving body near Earth has the same acceleration , two such bodies have zero relative acceleration: write each position as on one shared axis and clock, and their separation changes at the constant rate .
Where this lives today
Equal fall under shared gravity is now a precision industry. Drop towers like ZARM in Bremen give experiments seconds of free fall in an evacuated shaft — everything in the capsule, released together, floats together, exactly the zero-relative-acceleration theorem of Derivation C. The International Space Station is the same physics in permanent flight: every body aboard shares one acceleration, so astronauts float beside their spanners. And the MICROSCOPE satellite mission (2017–2022) confirmed that different materials fall alike to a few parts in . Einstein promoted Galileo's equal fall into the equivalence principle, the cornerstone of general relativity; your tower-meeting problem is the first rung of that ladder.
The setup
Geometry first, because in an archetype the geometry is the physics. Everything happens on one vertical line. Fix the origin at the ground, take up as positive, and start one clock at the first release. Every body in the problem — dropped, thrown up, thrown down, released from a balloon — is then a single function of the same :
where: — where body starts; — its initial velocity with sign (up , down , dropped , released from a platform the platform's velocity); — magnitude of gravitational acceleration, entering with a minus because up is positive. Read it physically: the only thing distinguishing the bodies is their launch data ; the term is identical for all of them — that shared term is the entire secret of this archetype.
Two disciplines make the machine run, and both earn explicit statements in a board answer:
One sign convention, declared once. Choose up as positive and write it down. Then enters every equation as (or ), a dropped body has , a thrown-down body has negative — and you never patch signs mid-solution. Mixing conventions between the two bodies is the number-one mark-killer in this archetype.
One clock. Start at the first event. A body launched later, at , has been flying for , so its position function uses everywhere would appear. Two private clocks — one per ball — is how juggler problems go wrong. The payoff for this discipline is the archetype's superpower. Subtract two copies of equation (1): the terms cancel. The separation changes linearly in time — no quadratic, no square roots. Gravity is invisible to the gap.
The master solution pattern
Route one — positions equal. Write and from equation (1), set , solve for , substitute back for the height. Mechanical, safe, and what CBSE/ISC structured questions expect shown. Route two — the relative shortcut. The gap closes at the constant rate (relative speed at launch), so
where: the initial gap is the launch separation and the relative speed is — with simultaneous launches only; delayed launches need the gap and relative speed evaluated at the second launch. This is a one-line answer to what looks like a quadratic problem, and it is the difference between 90 seconds and 20 seconds on a JEE-Main MCQ.
| situation | governing result | meeting/answer |
|---|---|---|
| drop from + throw up (simultaneous) | gap closes at rate | ; height |
| meet in the air at all? | dropped ball lands at | need |
| two equal throws , delay | symmetry about apexes | meet at from first throw |
| packet from balloon rising at , height | ||
| speed symmetry | up-speed at a height down-speed there | free sanity check |
On a position–time graph the story is one picture: two parabolas of the same curvature, whose vertical gap shrinks along a straight line.
We solve the defining problem of the archetype — ball 1 dropped from height at the same instant ball 2 is thrown up from the ground at speed — for the meeting time and height, first by setting position functions equal (the board-marks route), then by the relative-velocity shortcut (the exam-speed route). Watching both routes land on the same answer is the fastest way to trust the shortcut. Keep up as positive throughout; the dropped ball's initial velocity is zero, not .
Step 1. Position functions on one axis and clock:
Why: both bodies carry the identical term — same , same clock — which is exactly what will cancel.
Step 2. Set :
Why: the quadratic terms cancelled BEFORE any algebra — the meeting condition was secretly linear all along. Gravity delays both balls equally, so it cannot influence when they meet.
Step 3. Meeting height by substituting into either function:
Step 4. The shortcut route: relative to ball 2, ball 1 has zero relative acceleration and closing speed ; the gap is . So — one line, same answer.
Step 5. Reality check — do they meet in the air? The dropped ball lands at ; require , i.e. . Slower throws meet the dropped ball only "below the ground" — meaning never. Verified: , , : , height ; threshold ✓ they meet in the air. Both position functions give .
Go deeper · Derivation B · 1 minThe balloon packet and its inherited velocity
We derive the flight time of a packet released from a balloon that is rising at speed when the packet is let go at height . The physical crux sits in the initial condition: "released" means the packet stops being held, not that it stops moving — it leaves with the balloon's own . So the packet first climbs, decelerating at , then falls past the release height and down to the ground. The algebra is one quadratic; choosing the correct root is part of the derivation.
Step 1. Up positive, origin at the release point, clock starting at release. The packet's displacement:
Why: is positive — the packet inherits the balloon's upward velocity. Writing here is THE classic error; the packet is not "dropped from rest" in any frame fixed to the ground.
Step 2. The ground lies a distance below the origin, so impact is :
Step 3. Solve the quadratic for :
Why: the discriminant is always positive (the packet always lands), and we keep the root because the root is negative — a fictitious impact before release.
Step 4. Impact velocity from : substituting the flight time gives — downward, with a magnitude you could also read directly from (displacement , the appearing because speed at the release height is both going up and coming down). Verified: , , : ; impact speed ; check by ✓.
Go deeper · Derivation C · 1 minWhy the gap between two free bodies closes at constant speed
We prove the archetype's master theorem: for ANY two bodies in free vertical flight — whatever their launch heights, speeds and directions — the separation changes linearly with time. This is the licence behind every "relative velocity" one-liner in this family, so it deserves its own three lines. The strategy is bare subtraction of position functions; the physics is that the -terms are identical.
Step 1. Write both position functions on the shared axis and clock:
Step 2. Subtract:
Why: the terms cancel because is the same for both bodies — Galileo's equal-fall fact doing algebraic work. Nothing quadratic survives.
Step 3. Read the result: the gap is a straight-line function of time with slope . Bodies meet when , i.e. after time (simultaneous launches). If (the juggler's equal throws), the gap never changes while both are in flight — they cross only if a delay built the gap differently. Verified: for the tower problem, , slope , zero at — reproducing Derivation A. For two equal throws apart (both at , ), positions coincide at , matching the worked example below.
The variants examiners actually pose
Drop + throw (the tower meeting). Solved above; the exam dresses it as police towers, wells, cliffs. Watch for the condition add-on: "if they meet at the highest point of ball 2's flight" forces , and then — with the elegant consequence that they meet at , exactly half the tower height, always.
The juggler (equal throws, delayed). Both balls thrown up at , the second later. By time symmetry the crossing sits halfway between the apexes: , the balls passing at equal and opposite speeds .
The balloon packet. Inherited ; solved above. NEET's favourite twist: "how much higher does the packet rise after release?" — answer , from .
Ball past a window / nth-second distances. One body, same machinery: displacement in the -th second is , and window-transit times pin down launch speeds.
Limiting cases
| case | result | meaning |
|---|---|---|
| (tower problem) | , meet at height | a bullet-fast throw meets the ball where it was dropped |
| meet exactly at the ground | slowest throw that still "meets"; slower never does | |
| balloon | packet reduces to a simple drop — formula self-checks | |
| juggler | balls coincide throughout | zero delay = same launch = same flight |
| equal throws, both in flight | gap constant | kills the closing speed entirely |
Worked examples
1 · Board level — the tower meeting (CBSE/ISC pattern, 3 marks)
A stone is dropped from the top of a tower at the same instant a ball is thrown vertically upward from the ground at , along the same vertical line. Take . Find when and where they meet.
Step 1. Declare the convention (this earns a method mark): up positive, origin at the ground, at release. Stone: . Ball: .
Step 2. Meeting condition : the terms cancel, leaving .
Step 3. Height: above the ground.
Step 4. Sanity: the stone has fallen from — also ✓. And , so an in-air meeting was guaranteed.
2 · Board level — the juggler's two balls (ISC/CBSE pattern)
A juggler throws a ball vertically upward at . Exactly later he throws a second ball upward at the same speed from the same point. Take . When and where do the balls cross?
Step 1. One clock, started at the first throw. Ball A: . Ball B (aloft for ): , valid for .
Step 2. Set equal: . Expand the right side: . The and cancel from both sides, leaving .
Step 3. Height: .
Step 4. Read the symmetry: A peaks at , B peaks at — the crossing sits exactly halfway between the apexes, at . A is falling at while B rises at : equal and opposite, as the time symmetry demands.
3 · Competitive level — NEET/JEE-Main pattern: the balloon packet (~3 minutes)
A balloon rises steadily at . When it is above the ground, a packet slips from it. Take . (a) How long does the packet take to reach the ground? (b) With what speed does it land? (c) What maximum height above the ground does it reach?
Step 1. Initial velocity is the balloon's: (up positive, origin at release). Displacement to the ground: .
Step 2. (discard ).
Step 3. Landing velocity: speed downward. (Check: ✓.)
Step 4. Extra climb: , so maximum height , reached at . Timing note: ~3 min, and almost all of it is part (a)'s quadratic — which factorizes if you divide through by first. The mark-scheme trap is : that gives and , both sitting in the options waiting. The word "slips" does not mean "starts from rest".
4 · Competitive level — JEE-Advanced stretch: meet at the apex (~4 minutes)
A ball is dropped from the top of a tower of height at the instant a second ball is thrown up from its base at . They collide exactly when the second ball is at the top of its flight. Take . Find , the time of collision, and the height at which they collide — and show the collision height is regardless of .
Step 1. "At the top of its flight" pins the time: the thrown ball peaks at . So .
Step 2. The tower meeting always satisfies (Derivation A). Hence — equivalently .
Step 3. Collision height = the thrown ball's apex: .
Step 4. Generality: — the apex-meeting always happens at half the tower height, whatever is. Cross-check: the dropped ball falls from ✓. Timing note: ~4 min if you derive; ~90 s if you carry the pattern " apex meeting , collide at " as a known result. JEE-Advanced loves asking for the ratio precisely because the -dependence cancels — an option like "depends on u" is the examiner testing whether you did the algebra.
Exam traps
Inherited velocity ignored. Anything released from a moving platform — balloon, lift, rising drone — starts with the platform's velocity. "Dropped" describes the release, not the initial velocity. This single trap decides more balloon-packet marks than all the algebra combined.
Two private clocks. In delayed-launch problems, write the second body's position with , never a fresh . Expanding carelessly — losing the cross term — is the standard juggler error.
Sign convention drift. One body solved with up positive, the other with down positive, then positions "set equal": guaranteed nonsense. Declare the convention once, at the top, and force every and every through it.
Meeting "below the ground". The algebra happily returns meeting times after one body has already landed. Always check against each body's landing time — in the tower problem, that is the condition.
Distance vs displacement. A ball up-and-back-down has displacement zero but distance (max height). "Distance travelled in the 3rd second" around the apex must be split at the turning point — the naive formula gives displacement, not distance.
"Acceleration is zero at the top." Velocity is zero at the apex; acceleration is throughout, apex included. Any meeting-at-apex analysis that switches off gravity for an instant collapses.
Which ? CBSE/ISC expect unless stated; JEE-Main/Advanced and NEET almost always declare in the question. Use what is stated, and never mix values between the two bodies — they share one by definition.
Calculator habit. Divide quadratics like by common factors first — factorable integers are a deliberate gift, and the quadratic formula under time pressure breeds sign slips.
Origins · 1 minGalileo Galilei and how this was discovered
Galileo turned falling into an exact science. Aristotle had taught that heavy bodies fall faster in proportion to their weight; Galileo — by argument (tie a light ball to a heavy one: must the pair fall faster or slower than the heavy one alone?) and by experiment with inclined planes that "diluted" gravity — established that all bodies share one acceleration. His 1638 Two New Sciences states the odd-number law of distances and the time-squared rule, the DNA of every kinematic equation in this article. The Pisa drop may be legend, but in 1971 Apollo 15 commander David Scott performed it on the Moon with a hammer and a falcon feather: they struck the lunar dust together, on camera. Every "two bodies under gravity" problem is Galileo's equal-fall principle wearing an exam costume.
Going further
Texts. NCERT Physics Class 11, Ch. 3 (motion under gravity) · HC Verma, Concepts of Physics Vol. 1, Ch. 3 · Resnick–Halliday–Walker, Ch. 2.
Provenance. All results are standard kinematics. A verifier should recompute: tower meeting , , : , height , threshold · Example 1 (, , ): , · Example 2 (, , ): , , crossing speeds · Example 3 (, , ): , , max · Example 4 (, ): , collide at · balloon warning-box wrong-route .
Prerequisites. Free Fall & Motion Under Gravity · Kinematic Equations for Uniform Acceleration. Leads to. Relative Velocity & Reference Frames (the shortcut, generalized to 2D) · Chase, Catch & Meet (the same machine laid horizontal).
Why is the relative acceleration of two falling bodies exactly zero?
Because gravity gives every free body the same acceleration , independent of its mass, velocity or direction of motion — Galileo's equal-fall fact. Subtracting the two acceleration vectors: . The gap between the bodies then behaves like a problem with no gravity at all: it just changes at the constant rate set by the launch velocities. That's why meeting times come out of linear equations even though each body separately moves on a parabola in time.
Doesn't the heavier body fall at least a little faster?
In vacuum, no — mass cancels exactly, because the gravitational force on a body is proportional to the same mass that resists acceleration (). In air, drag muddies things: a feather falls slower than a hammer on Earth, but that is air resistance, not gravity playing favourites. Exam problems say "neglect air resistance" precisely to hand you the clean equal- world; the Apollo 15 hammer-and-feather drop shows that world is real.
How do I know whether the two bodies actually meet in the air?
Compute the meeting time, then check both bodies are still airborne then. In the drop-plus-throw problem: must not exceed the dropped ball's landing time , which rearranges to . If the throw is slower than that, the "meeting" the algebra reports happens at negative height — after the stone has already hit the ground. Always translate the algebraic answer back into the physical timeline.
In delayed-launch problems, why (t − t₀) and not a new clock for the second body?
You can run a private clock for each body — but then the meeting condition mixes two different time variables and you must add the offset anyway, usually incorrectly under pressure. One master clock with for the latecomer keeps every position function comparable: setting is legitimate because both are evaluated at the same instant. Just remember the second body's function is only valid for ; before that it hasn't been launched.
Why does the packet from the balloon rise first instead of falling immediately?
Velocity doesn't change instantly — only forces change it, at a finite rate. At release the packet moves upward at the balloon's ; gravity then removes of upward velocity every second, so for half a second the packet is still climbing (another ). Watch videos of skydivers leaving a rising hot-air balloon: they visibly float upward relative to the ground for a moment. "Released" describes the grip, not the motion.
Can I take downward as positive instead?
Absolutely — sign conventions are choices, not laws. Downward-positive is cleaner when everything falls; up-positive is cleaner the moment anything moves upward (like the balloon packet's inherited velocity). The only crime is switching conventions mid-problem or between the two bodies. Declare once, apply it to every , and , and either convention gives identical physical answers.
What's the fastest way to sanity-check a meeting answer in the exam?
Three free checks. First, substitute into BOTH position functions — they must agree (Example 1: both give ). Second, timeline: is before both landing times? Third, symmetry: speeds at a shared height match up/down (Example 2's balls cross at equal and opposite ). Ten seconds of checking catches the sign and clock errors that produce plausible-looking wrong answers.