Free-Body Diagrams & Problem-Solving Strategy
Every bridge you have ever crossed was certified by an act of imagination: an engineer mentally sawed the structure apart — one girder, one cable at a time — lifted each piece onto a clean page, drew every force the rest of the world exerts on it, and demanded that the piece obey Newton's laws all by itself. That ritual has a name, the free-body diagram, and it is the most valuable picture you will learn to draw in physics. Examiners know it: in most mechanics problems the marks are won or lost before any algebra happens, in the two centimetres of page where you drew (or failed to draw) the forces. Every board runs on this skill. CBSE and ISC award explicit method marks for a correct diagram; IGCSE and A-Level ask you to draw and label the forces as a question in its own right; AP Physics 1 has a free-response style where a wrong diagram forfeits the page. JEE and NEET never say "draw a free-body diagram" — they pose two- and three-block systems unsolvable without one, then plant options matching every classic diagram error: the phantom "force of motion", the arrow, the reflex. This module turns the skill into a five-step algorithm you run identically on every problem, plus the strategic choice experts make and beginners miss: where to cut — the whole system, or one body — and why you usually do both. It is the operating manual for everything U3 throws at you next, from the Atwood Machine to the block-on-incline family.
- A free-body diagram (FBD) isolates one body and shows every external force on it — weight, normal, tension, friction, applied pushes — and nothing else.
- The admission test for every arrow: name the agent. "Table pushes book" qualifies. "Motion carries it forward" does not — motion is not a force, and is the result of forces, never an arrow.
- Forces the body exerts on other things go on their diagrams — third-law partners never share a diagram.
- The algorithm: isolate → inventory (touch test + gravity) → label with symbols → axes along the acceleration → per axis.
- System vs component: cut around several bodies for the acceleration (internal forces cancel); cut around one body to expose the internal force the question asks for. Most exam problems need both passes.
- Key idea: cut one body free, draw every force acting on it and nothing else, then read along well-chosen axes — the diagram is the complete interface between the physical situation and the mathematics.
Cut one body free, draw every external force acting on it and nothing else, then project along axes matched to the acceleration — the free-body diagram is the complete interface between a physical situation and Newton's laws, and where you cut (whole system or single body) decides how hard the algebra will be.
Where this lives today
The free-body diagram never retired; it multiplied. Every finite-element simulation — the software that certifies aircraft wings and crash-tests cars before they exist — is millions of free-body diagrams solved at once: the structure is meshed into tiny elements, and each node's equation is for the forces its neighbours exert on it. The engineer's mental saw became an algorithm, but the physics per element is this module's recipe unchanged. Robotics runs the method in real time: a legged robot deciding where to plant a foot solves a contact problem — which normal and friction forces keep the body on its intended motion — hundreds of times per second, and game-physics engines resolve thousands of per-body ledgers every frame. Engineering licensure exams still open the way your next problem set does: draw the free-body diagram first.
The physical picture
Think of a free-body diagram as an interrogation. Grab one object, lift it out of its surroundings, and ask: who is pushing or pulling on you, and which way? Each truthful answer becomes an arrow. Earth pulls the block down — arrow. The table presses up — arrow. The rope pulls — arrow. That is the complete testimony: anything the block does to the table is the table's problem, on the table's diagram, not here. The inventory is mercifully short. Contact forces act only where something touches the body — run a finger around its boundary and you find them all: a normal force from every surface, friction along it, tension from every string, the push of a hand. Add the one long-range force of this course, gravity, from the centre. Trace the boundary, add weight, and you are provably done.
Two illegal arrows account for most wrong diagrams ever drawn. The first is the "force of motion" — the feeling that a moving object must carry a forward push. It died in 1687: uniform motion needs no force, only changes do (the whole of Force, Inertia & Newton's First Law). A coasting puck has exactly two arrows, weight and normal, however fast it slides. The second is drawing as a force: is the verdict the forces produce, the right-hand side of the law — smuggling it onto the diagram double-counts the physics. Slogan: the left side of lives on the diagram; the right side is what the diagram predicts.
The five-step algorithm
Run these five moves, in order, on every problem — they are the marking scheme's checklist.
Step 1 — Isolate. Choose the body and say it aloud: "the block", not "the block and rope, sort of". Treat it as a point at its centre (fine while nothing rotates).
Step 2 — Inventory. The touch test: trace the boundary — every touch contributes a normal force, possibly friction, or a tension. Add gravity. Every candidate arrow must pass the agent test: who is exerting you?
Step 3 — Draw and label. Arrows start on the body, point in the force's direction, and carry symbols (, , , , ) — never numbers yet. Algebra first, arithmetic last: early substitution hides errors and destroys part marks.
Step 4 — Choose axes. Any perpendicular pair works, but the algebra collapses when one axis lies along the acceleration. On an incline, tilt the axes with the slope — the constraint direction then reads .
Step 5 — Project and solve. Each axis gives one scalar equation. Count unknowns; if bodies are connected, add the constraint (same along an inextensible string) and repeat for another body. The law the diagram feeds is Newton's second, written with the subscript that carries the whole philosophy — only forces exerted by other objects on this body enter:
where: — each force drawn on the diagram; — the body's mass; — its acceleration. It is a vector statement, which is exactly why the diagram matters: the bookkeeping that guarantees no force forgotten, none invented, each with the right direction. Axis by axis it becomes
where: the components are signed — a force at angle to an axis contributes its piece there and its piece to the other axis. Each body supplies two scalar equations in 2D — that count tells you in advance how many bodies you must isolate.
The force inventory
| force | direction rule | known or unknown? |
|---|---|---|
| weight | vertically down, from the centre | known |
| normal | perpendicular to the surface, pushing away | unknown — solve the ⊥ equation; |
| tension | along the string, always pulling | unknown — same throughout an ideal string |
| friction | along the surface, opposing sliding or its tendency | static: unknown up to a ceiling · kinetic: |
| applied push/pull | as given | known |
| spring force | along the spring, toward natural length | (Hooke's Law module) |
We solve the hero-figure problem in full: a block of mass on a smooth horizontal table, pulled by a rope with tension at angle above horizontal; find the acceleration and the normal force. It is the cleanest end-to-end run of the five steps, and it carries the exam's favourite subtlety — the tilted pull changes , so anyone who wrote by reflex has already lost the thread. Watch the vertical equation quietly derive the normal force.
Step 1. Isolate the block. Touch test: the table touches it (normal ; smooth, so no friction), the rope touches it (tension at ), gravity acts ( down). Three arrows, each with an agent.
Step 2. Axes: horizontal (the block stays on the table, so is horizontal) and vertical . Only the pull needs decomposing: along , along .
Step 3. Project equation (2) on , where :
Why dropped below : the rope's vertical slice carries part of the weight, so the table supplies less. At , — the verge of lift-off.
Step 4. Project on :
Why only the cosine drives: the vertical slice fights gravity, not inertia — only the horizontal slice accelerates the block.
Step 5. Limits: gives , (flat drag, the reflex case); gives , (a pure lift attempt). Both endpoints are right, so the decomposition is trustworthy. Verified: , , , : , — recomputed in Worked Example 1; NCERT Ch. 5 pattern.
Where to cut — system vs component
Newton's third law (its own module) makes cutting legal. When two bodies interact, a cut through their connection exposes an equal-and-opposite pair — one arrow plunging into each body. Separate diagrams show both arrows, one each. Fuse the bodies into a single system and the pair hides inside, cancelling exactly. Choosing where to cut is choosing which forces you can see:
where: "internal" means both ends of the interaction live inside the cut. The system cut is the fast lane to the acceleration — one equation, no internal unknowns. The component cut is the only way to find a tension or contact force, because a force must cross the cut boundary to appear on a diagram. Skilled solvers run both, in that order.
Go deeper · Derivation B · 1 minTwo blocks in contact — the two-pass method
A hand pushes with force on block 1 (mass ), which pushes block 2 () ahead of it on a smooth floor. We want the contact force between them — invisible on any diagram of the pair, visible only when we cut between them. The strategy is the two-pass method every connected-body problem reuses: system first for the acceleration, then one strategic component cut. The moral is worth memorising — the contact force is exactly the fraction of needed to accelerate the mass downstream of the cut.
Step 1. System cut around both blocks (). The pushes between them are now an internal third-law pair and cancel; the only horizontal external force is :
Why the pair cancels: the two contact forces are equal and opposite and both act inside the cut, so they vanish from the external sum — that cancellation is the entire advantage of the system view.
Step 2. Component cut around block 2 alone. The hand touches only block 1, so the single horizontal force on block 2 is the push from block 1, :
Why block 2 is the smarter cut: isolating block 1 gives — two forces instead of one. Both agree; the cleanest diagram is the body with the fewest arrows.
Step 3. Test by reversing the push: apply to block 2's side and the downstream mass becomes , so the contact force is . Same blocks, same push, different squeeze — the cut feeds whatever mass lies beyond it. Verified: , , : , ; reversed, . Ledger: ✓. Limits: zeroes the contact force; passes the full . HC Verma Ch. 5 pattern.
The same two-pass logic, plus the string constraint (one shared along an inextensible string, one throughout an ideal one — Tension & Ideal Strings), is the entire method behind pulleys. The Atwood Machine & Variants archetype runs it as the worked setup, so we leave pulleys to it.
Limiting cases
| case | result | meaning |
|---|---|---|
| , | statics — Equilibrium of Concurrent Forces is this row grown into a module | |
| system cut | internal pairs cancel | fastest route to ; internal forces invisible |
| component cut | connection forces exposed | the only way to see a tension or contact force |
| coasting body | only and on the page | uniform motion needs no force — first law |
| massless string | one along the string | a massless body obeys even accelerating |
| circular motion | net inward part | centripetal is a role, never an extra arrow |
Worked examples
1 · Board level — the angled pull (CBSE/ISC pattern, 3 marks)
A block rests on a smooth horizontal table. A rope pulls it with at above the horizontal (). Draw the free-body diagram and find the block's acceleration and the normal force.
Step 1. FBD: weight down, normal up, tension at . Decompose the pull: horizontal , vertical .
Step 2. Vertical equation (): — the rope carries a quarter of the weight.
Step 3. Horizontal equation: .
2 · Board level — two blocks in contact (IGCSE-to-CBSE ladder)
A force pushes a block, which pushes a block ahead of it on a frictionless floor. Find and the force between the blocks.
Step 1. System cut (): .
Step 2. Component cut around the block — one horizontal force, the contact push: .
Step 3. Audit with the other block: ✓ — checking the unused equation is five-second insurance.
Step 4. Push the block first instead and the contact force feeds the downstream : — double, for the same applied force.
3 · Competitive level — the three-block train (JEE-Main pattern, ~3 minutes)
Blocks of , and sit touching in a row on a smooth floor. A force pushes the block from the left. Find both contact forces.
Step 1. System cut (all three, ): .
Step 2. Contact between blocks 1 and 2: cut so the downstream mass is . .
Step 3. Contact between blocks 2 and 3: downstream mass . .
Step 4. Audit the middle block (two contacts): ✓. Timing note: ~3 min the first time, ~90 s once "downstream mass × a" is a reflex. The trap options are 12, 10, 6 N shuffled — a contact force matched to the wrong cut. Say it aloud: the force feeds "everything beyond this face".
4 · Competitive level — horizontal force on an incline (JEE-Main pattern, ~2.5 minutes)
A block is held at rest on a smooth incline by a horizontal force (). Find and the normal force.
Step 1. FBD: weight down, normal perpendicular to the incline, horizontal. Tilt the axes; two forces now decompose — weight ( along, into the slope) and ( up-slope, into it).
Step 2. Along-slope equilibrium: , so .
Step 3. Perpendicular equation: .
Step 4. Note what happened: , because the horizontal push presses into the slope. Anyone who wrote from memory lost this question — the diagram, not the formula sheet, decides. (Check: ✓.) Timing note: ~2.5 min. Budget the first 30 s for the diagram and axes; the two projections are then mechanical. The planted wrong answer is always for .
Exam traps
The phantom arrows. Force of motion, , "centripetal force" as an extra agent — all fail the name-the-agent test. When asked to draw an FBD (AP, A-Level, IGCSE), examiners deduct for extra arrows, not just missing ones.
written from memory. The vertical (or perpendicular) equation derives ; any angled pull, push or extra contact changes it — Examples 1 and 4 both punish the reflex, and a wrong poisons friction via next module.
Third-law partners on one diagram. The pair of "table pushes block up" is "block pushes table down" — a force on the table, filed on the table's diagram. Weight and normal on one block are not partners; they merely balance when .
Axes fighting the acceleration. On an incline, horizontal-vertical axes put both unknowns in both equations. Tilt the axes so one equation reads and the algebra halves. Heavy simultaneous equations usually mean wrong axes.
Numbers substituted too early. Label arrows symbolically and solve; substitute in the last line. Boards award method marks for the symbolic line even when arithmetic slips — a numbers-first page loses both.
Sign chaos in multi-body problems. Give each body its own positive direction along its own motion, so the shared stays positive in every equation. Mixing conventions mid-problem is the classic Atwood killer.
Which ? CBSE/ISC ; JEE/NEET as stated (usually ); A-Level ; AP-1 accepts . State it once at the top.
Origins · 1 minLeonhard Euler and how this was discovered
Newton stated the laws; Euler made them an algorithm. His Mechanica (1736) recast the Principia's geometry as equations for a single isolated body, and in 1750 he published a "new principle of mechanics" — per component, valid for any body you choose to cut free from its surroundings, rigid or fluid, whole or part. That cut principle is the license behind every free-body diagram: pick any piece of the world, replace everything you removed with forces, and the second law holds for the piece. The idea that "any body, cut free, obeys " is arguably the most-used single idea in applied mechanics.
Going further
Texts. NCERT Physics Class 11, Ch. 5 · HC Verma, Concepts of Physics Vol. 1, Ch. 5 · Halliday, Resnick & Walker, Ch. 5–6.
Provenance. Standard Newtonian method. A verifier should recompute: the angled pull (, at , : , ); the contact-pair law (, : , reversed ); the two-block example (, : , contact , reversed ); the train (, : , contacts and , audit ); the incline hold (, , : , ).
Prerequisites. Newton's Second Law: F = ma · Newton's Third Law & Interaction Pairs · Weight, Normal Force & Apparent Weight. Leads to. Equilibrium of Concurrent Forces · The Atwood Machine & Variants · The Block-on-Incline Family — and, for the deep dive, the university-tier Free-Body Diagrams (Advanced Mechanics).
Why doesn't the force I exert on the wall appear on my own free-body diagram?
Because your diagram lists only forces exerted on you, and that force acts on the wall — it belongs on the wall's diagram. What appears on yours is its third-law partner: the wall's push back on you. Equal and opposite, but on different bodies — which is why they can never cancel. This one filing rule — every force filed under the body it acts on — is the discipline of the method. Push a wall while standing on ice and your diagram predicts the outcome: the only horizontal force on you is the wall's push, so backward you slide.
Is centripetal force a separate arrow on the diagram?
No — adding one is a classic double-count. "Centripetal" names a role, not an agent: it is whatever net inward component the already-drawn forces provide. A ball whirling on a string has two arrows, tension and weight; the tension is (most of) the centripetal force. Correct procedure: draw the ordinary forces, point one axis at the circle's centre, set the net inward component equal to . An arrow labelled "centripetal" with no nameable agent fails the admission test — delete it.
Where does ma go, if not on the diagram?
On the other side of the equals sign. The diagram supplies the left of — the inputs; is the output those forces produce. Drawing it as a force double-counts the physics and wrecks the signs. Clean habit: write the force sum straight off the diagram, then the equals sign, then — the geography of the equation mirrors the logic. (Non-inertial frames, where a pseudo-force legally joins the diagram, have their own module — note it uses the frame's acceleration, not the body's.)
Weight and normal force on a resting book are equal and opposite — aren't they a third-law pair?
No — the most-tested subtlety in the chapter. Partners are one interaction seen from both ends: "Earth pulls book" pairs with "book pulls Earth". Weight (from the Earth) and normal (from the table) are two different interactions that balance only because the book has . In a lift accelerating downward, instantly, while every true pair stays exactly equal and opposite. Equal-because-of-equilibrium is the second law's doing, not the third's.
How do I decide which way to draw friction?
Ask what the contact surfaces are doing — or trying to do — relative to each other. Kinetic friction opposes actual slipping; static friction opposes the tendency to slip (if friction vanished, which way would the surfaces slide? Static friction points the other way). This produces surprises: friction points forward on a car's driven wheels, and forward on a crate in an accelerating truck — there it is the only force accelerating the crate. The full machinery lives in Static Friction and Kinetic & Rolling Friction; the diagram needs only the direction.
When can I lump bodies into one system, and when must I separate them?
Cut wherever you like, provided everything inside the cut shares one acceleration. Lumping is the fast lane to : internal forces cancel by the third law. The price is blindness — internal forces are invisible from outside the cut. The moment a question asks for a tension or contact force, cut through that connection so it crosses the boundary and appears. Professionals do both in sequence: system for , then one component cut. More unknowns than equations means too few cuts.