Mechanics 1

Condensed sheet

Everything, on one sheet

Every method, every named trap, and every reference card in Mechanics 1 — pulled straight from the lessons, so it can never drift out of sync with them.

9 lessons · 445 min, condensed

Read this once, then stop reading it. Re-reading a summary raises how familiar the material feels without changing how much of it you can produce, which is why it feels like studying and mostly isn’t. Use lookup mode when you need a specific fact. Use self-test mode — where the answers stay covered until you’ve tried to say them — for everything else.

Spec 1.1

1 lesson

Modelling Assumptions in Mechanics, and "Hence Show That" Discipline

A "critique the model" question is not testing whether you remember the vocabulary — it's testing whether you reread the paragraph the model is actually printed in. And a "hence show that" question is not asking you for the right number — the number is already sitting on the page. Both come down to the same discipline: stay tied to what's actually given, never to what you assume this kind of question "usually" wants. One real examiner report names the first failure directly; examiner reports across at least five separate series name some form of the second. Thin as a standalone topic on its own — but two of the quietest ways to lose marks in this whole unit, because a wrong answer to either one can look, right up until the mark scheme explains why, exactly like a right one.

The card

Particle = point mass, no rotation to consider. Rigid body/lamina/rod keep their shape. Light = no weight of its own.
Inextensible string ⇒ same |a| for both connected particles. Light smooth pulley ⇒ same T on both sides, no extra inertia term.
Smooth ⇒ no friction at all. Rough ⇒ F ≤ μR (equilibrium) or F = μR (moving). Wire can push AND pull; string can only pull.
"Critique the model" parts: reread the exact paragraph the model is stated in. Only a modification tied to what's actually named earns credit.
"Hence show that" parts: full explanation, reusing a previous part's value, arriving at EXACTLY the printed value/expression — the argument is marked, not just the final number.
cso = correct solution only, no errors anywhere in that part. DM = a method mark that depends on an earlier method mark already being earned.

Why it works — Why a "critique the model" answer has to be tied to the stem's own words, not to modelling in general

Every model in a Mechanics question is a stated list of simplifications, not an open invitation to list simplifications in general. A question that models a falling object under gravity alone, ignoring air resistance, has made exactly one named trade: real air resistance for zero air resistance, in exchange for equations simple enough to solve by hand. "Critique the model" is asking you to identify that specific trade and reason about undoing it — not to produce any true statement about the real world that happens to sound like physics. This is why a technically-correct observation (real objects experience air resistance; a rod has some width; a string has some mass) can still earn nothing: if the question's own stated model never claimed the opposite of that observation, there's no named simplification for the observation to be relaxing, and the answer is disconnected from what was actually asked. A real examiner report on exactly this question type is direct about the consequence: candidates need to appreciate that a late modelling part refers to "the model," and the model is the one "clearly described" in the question's own paragraph — so only a modification to THAT model, the one actually printed in front of you, receives credit. The discipline is small and mechanical: find the sentence that states the simplification, name what it gave up, and say what changes if that trade is undone — in that order, every time.

Traps — 3

critique-the-model-answer-not-connected-to-the-stated-model
Confirmed verbatim, and the only real past-paper anchor spec 1.1 has as a standalone question type: "Candidates need to appreciate that the question refers to 'the model' and the model is clearly described in the second paragraph of the question. Hence only modifications to that model received credit" (Oct 2019, Q6). A true-sounding statement about the real world — however scientifically accurate — earns nothing if it isn't a relaxation of a simplification the question's own stated model actually named. Find the sentence that states the trade-off before answering, not after.
show-that-final-value-stated-without-the-full-explanation
Examiner reports across at least five series (Jan 2020, Jan 2023, Oct 2022, Jun 2024, Oct 2023) each repeat some form of the same standing instruction: "when a question asks candidates to 'hence show that', ... a full explanation, including all steps, is required to earn full marks, where the explanation must use one or more of the previous parts of the question." On an ag part, the printed target being reached is not, by itself, evidence of anything — a candidate could read it straight off the page. The marks are for the shown argument that arrives there, using a previous part's own value, not for the number matching.
modelling-term-treated-as-decorative-rather-than-load-bearing
A related trap confirmed on a rod-modelling question: "There was general appreciation that modelling the beam as a rod meant that it did not bend, [but] some candidates failed to achieve the mark for including wrong or irrelevant extra statements. The most common incorrect answers related to the mass (or centre of mass) of the rod and comments such as 'clockwise moments equal anticlockwise moments'" (Jan 2020, Q2(b)). "Clockwise moments equal anticlockwise moments" is the EQUILIBRIUM CONDITION, not a consequence of the rod-modelling term — it would be true whatever object the beam had been modelled as. Every term in spec 1.1's vocabulary list licenses a specific, nameable consequence (see the teach block above); a question asking what a modelling term assumes wants THAT consequence, not the technique used to solve the rest of the question.

Say it out loud

Out loud, from memory, no notes: explain why a "critique the model" answer has to be tied to the stem's own words, not to modelling in general to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 2.1

1 lesson

Resultant Forces (Resolving vs. Cosine Rule/Lami's Theorem) and Bearings

Two forces meeting at a point have exactly one resultant, and this whole topic is really two different ways of finding it — resolve into i/j components and use Pythagoras, or draw the triangle the two forces make and hit it with the cosine rule (or Lami's theorem) directly — plus one conversion, bearing to component, that the exam tests far more literally than it looks: get sin and cos the wrong way round and the wrong answer isn't vague, it's a specific number an examiner report has watched real candidates hand in.

The card

Bearing → components (i = east, j = north): i-part = F sinθ, j-part = F cosθ. Sine goes with EAST — the opposite pairing from a standard angle.
Resultant of P, Q at angle θ (from a common point): R² = P² + Q² + 2PQcosθ — same as resolve-then-Pythagoras, always.
Triangle of forces (head-to-tail): the cosine-rule angle at the shared vertex is 180° − θ, the SUPPLEMENT of the angle between the forces at their common point.
Lami's theorem (3 concurrent forces in equilibrium): P/sinα = Q/sinβ = T/sinγ, each angle opposite the OTHER two forces.
Cosine rule is a P1/P2 formula extended to M1 via the booklet's own wording — not printed again in the M1 section. Pythagoras is assumed knowledge, printed nowhere.

Why it works — Why a bearing turns into sin·i + cos·j — and why that feels backwards

A bearing is a direction measured clockwise from north, given as three figures (000° to 360°) — 070° means "start facing north, turn 70° clockwise." This is a genuinely different convention from a standard angle measured anticlockwise from the positive x-axis (east), which is what most trigonometry questions use and what the arithmetic muscle memory from Pure Mathematics is trained on — and the exam relies on that mismatch. Picture the unit circle with north at the top (the j-axis) and east on the right (the i-axis). Starting due north and rotating clockwise through an angle θ, the point traces out east-component sinθ\sin\theta and north-component cosθ\cos\theta — sine pairs with east, cosine pairs with north, which is the OPPOSITE pairing from the standard-angle convention (where cosine pairs with the x-axis and sine with the y-axis). The reason is simply which axis the angle is measured FROM: a standard angle starts at the x-axis, so cosine (adjacent to that starting axis) goes with x; a bearing starts at the y-axis (north), so cosine goes with y instead, and sine — the "how far around" function — ends up paired with x. Nothing about sin and cos themselves has changed; only which axis the angle begins its sweep from has. A real WME01 examiner report on exactly this conversion records the cost of missing it: on a bearing-to-vector question, "a significant number showed a lack of knowledge of bearings and an answer of 12i + 16j was often seen" — the correct conversion required swapping the components (Jun 2024, Q7). The marked-solution block below reconstructs this exact error with real, checkable numbers. The one habit that catches it every time: before resolving anything, sketch the bearing as an arrow on a compass rose and ask whether the arrow leans more toward east or more toward north — the LARGER trig value belongs on whichever axis the arrow leans closer to, and a swapped answer fails that sanity check immediately.

Traps — 3

bearing-sin-cos-pairing-swapped
Confirmed directly on a real bearing-to-vector question: "a significant number showed a lack of knowledge of bearings and an answer of 12i + 16j was often seen" — the report is explicit that "the correct conversion required swapping the components" (Jun 2024, Q7). The mechanism is treating a bearing (measured clockwise from NORTH) like a standard angle (measured anticlockwise from EAST), which swaps which axis sine belongs to. The marked-solution block above reconstructs this exact wrong answer with real, checkable numbers.
triangle-of-forces-supplement-not-taken
Confirmed on a real resultant-of-two-forces question that directly compared the two standard methods: "those candidates who resolved in two perpendicular directions and then used Pythagoras tended to have more success than those who attempted to use the cosine rule on a triangle of forces. A common error with this approach was to use an incorrect angle of 30, 60 or in some cases 330 degrees, even when they had drawn what appeared to be the correct obtuse angled triangle" (Jun 2024, Q2). The triangle itself being right and the angle plugged into the formula being wrong is precisely the failure mode a correct sketch does not, by itself, protect against — the interior angle at the shared vertex is the SUPPLEMENT of the angle between the forces as drawn from their common point, never that angle directly.
incomplete-resolution-missing-a-term
Confirmed on a real equilibrium/resolving question, where a candidate resolved in one direction but dropped a whole force from the equation: "incomplete resolutions e.g. 5 = Fcos30 rather than 5 = Fcos30 + Tcos60" (Jan 2022, Q1, the same series and question that independently confirms Lami's theorem as a credited alternative method — "another direct method involved applying Lami's theorem"). This is a method error, not an accuracy error, under the mark scheme's own general principles for Mechanics marking: an equation produced by resolving is only creditable once every force with a component in that direction has actually been multiplied by its own sin or cos and included — one omitted term breaks the method mark, whatever the rest of the arithmetic does afterwards.

Say it out loud

Out loud, from memory, no notes: explain why a bearing turns into sin·i + cos·j — and why that feels backwards to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 2.2

1 lesson

Resultant Forces (Resolving vs. Cosine Rule/Lami's Theorem) and Bearings

Two forces meeting at a point have exactly one resultant, and this whole topic is really two different ways of finding it — resolve into i/j components and use Pythagoras, or draw the triangle the two forces make and hit it with the cosine rule (or Lami's theorem) directly — plus one conversion, bearing to component, that the exam tests far more literally than it looks: get sin and cos the wrong way round and the wrong answer isn't vague, it's a specific number an examiner report has watched real candidates hand in.

The card

Bearing → components (i = east, j = north): i-part = F sinθ, j-part = F cosθ. Sine goes with EAST — the opposite pairing from a standard angle.
Resultant of P, Q at angle θ (from a common point): R² = P² + Q² + 2PQcosθ — same as resolve-then-Pythagoras, always.
Triangle of forces (head-to-tail): the cosine-rule angle at the shared vertex is 180° − θ, the SUPPLEMENT of the angle between the forces at their common point.
Lami's theorem (3 concurrent forces in equilibrium): P/sinα = Q/sinβ = T/sinγ, each angle opposite the OTHER two forces.
Cosine rule is a P1/P2 formula extended to M1 via the booklet's own wording — not printed again in the M1 section. Pythagoras is assumed knowledge, printed nowhere.

Why it works — Why a bearing turns into sin·i + cos·j — and why that feels backwards

A bearing is a direction measured clockwise from north, given as three figures (000° to 360°) — 070° means "start facing north, turn 70° clockwise." This is a genuinely different convention from a standard angle measured anticlockwise from the positive x-axis (east), which is what most trigonometry questions use and what the arithmetic muscle memory from Pure Mathematics is trained on — and the exam relies on that mismatch. Picture the unit circle with north at the top (the j-axis) and east on the right (the i-axis). Starting due north and rotating clockwise through an angle θ, the point traces out east-component sinθ\sin\theta and north-component cosθ\cos\theta — sine pairs with east, cosine pairs with north, which is the OPPOSITE pairing from the standard-angle convention (where cosine pairs with the x-axis and sine with the y-axis). The reason is simply which axis the angle is measured FROM: a standard angle starts at the x-axis, so cosine (adjacent to that starting axis) goes with x; a bearing starts at the y-axis (north), so cosine goes with y instead, and sine — the "how far around" function — ends up paired with x. Nothing about sin and cos themselves has changed; only which axis the angle begins its sweep from has. A real WME01 examiner report on exactly this conversion records the cost of missing it: on a bearing-to-vector question, "a significant number showed a lack of knowledge of bearings and an answer of 12i + 16j was often seen" — the correct conversion required swapping the components (Jun 2024, Q7). The marked-solution block below reconstructs this exact error with real, checkable numbers. The one habit that catches it every time: before resolving anything, sketch the bearing as an arrow on a compass rose and ask whether the arrow leans more toward east or more toward north — the LARGER trig value belongs on whichever axis the arrow leans closer to, and a swapped answer fails that sanity check immediately.

Traps — 3

bearing-sin-cos-pairing-swapped
Confirmed directly on a real bearing-to-vector question: "a significant number showed a lack of knowledge of bearings and an answer of 12i + 16j was often seen" — the report is explicit that "the correct conversion required swapping the components" (Jun 2024, Q7). The mechanism is treating a bearing (measured clockwise from NORTH) like a standard angle (measured anticlockwise from EAST), which swaps which axis sine belongs to. The marked-solution block above reconstructs this exact wrong answer with real, checkable numbers.
triangle-of-forces-supplement-not-taken
Confirmed on a real resultant-of-two-forces question that directly compared the two standard methods: "those candidates who resolved in two perpendicular directions and then used Pythagoras tended to have more success than those who attempted to use the cosine rule on a triangle of forces. A common error with this approach was to use an incorrect angle of 30, 60 or in some cases 330 degrees, even when they had drawn what appeared to be the correct obtuse angled triangle" (Jun 2024, Q2). The triangle itself being right and the angle plugged into the formula being wrong is precisely the failure mode a correct sketch does not, by itself, protect against — the interior angle at the shared vertex is the SUPPLEMENT of the angle between the forces as drawn from their common point, never that angle directly.
incomplete-resolution-missing-a-term
Confirmed on a real equilibrium/resolving question, where a candidate resolved in one direction but dropped a whole force from the equation: "incomplete resolutions e.g. 5 = Fcos30 rather than 5 = Fcos30 + Tcos60" (Jan 2022, Q1, the same series and question that independently confirms Lami's theorem as a credited alternative method — "another direct method involved applying Lami's theorem"). This is a method error, not an accuracy error, under the mark scheme's own general principles for Mechanics marking: an equation produced by resolving is only creditable once every force with a component in that direction has actually been multiplied by its own sin or cos and included — one omitted term breaks the method mark, whatever the rest of the arithmetic does afterwards.

Say it out loud

Out loud, from memory, no notes: explain why a bearing turns into sin·i + cos·j — and why that feels backwards to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 3.1

1 lesson

Constant-Acceleration Kinematics and Two-Stage Motion

Every one of the five suvat equations assumes exactly one thing: that the acceleration is the same constant value for the whole interval you apply it to. M1's single richest, most consistently examined trap is a journey that quietly breaks that assumption partway through — a force removed, a surface that roughens, a parachute that opens — while the equation on the page looks exactly as innocent as it did a line before. Independently confirmed in at least two separate series, this is the one habit that decides whether a two-stage journey earns full marks or, in the examiners' own words, "no credit" at all.

The card

v=u+at · s=ut+½at² · s=vt−½at² · v²=u²+2as · s=½(u+v)t — none in the M1 booklet. Memorise all five.
Gradient of a velocity–time graph = acceleration. Area under it = displacement.
Acceleration changes anywhere in the journey (force added/removed, new surface, hits the ground)? Two suvat equations, one per constant-a stage — never one across the join.
The handover value (v, s or t at the join) is stage 1's OUTPUT and stage 2's INPUT — carry it across, don't restart stage 2 from rest.
A quadratic root outside the time the model actually describes must be rejected, and the rejection needs a stated reason, not silence.
M mark: correct method (e.g. applying a suvat equation). A mark: needs its M first — but M1 A0 is real. B mark: stands alone.

Why it works — Where the five equations come from — one graph, not five separate facts

Draw a velocity-time graph for constant acceleration: it is a straight line, starting at height uu (the initial velocity) at t=0t=0 and rising or falling steadily to height vv at time tt. Two physical facts about this graph do all the work. First, the gradient of a velocity-time graph is the acceleration — velocity's rate of change is, by definition, acceleration — so a=vuta = \frac{v-u}{t}, rearranged immediately into v=u+atv = u + at: the first equation, read straight off the definition of gradient. Second, the area under a velocity-time graph is the displacement — since velocity is itself the rate of change of displacement, the area swept out between the graph and the time axis is exactly how far the particle has travelled. The region under a straight line from uu to vv over a time tt is a trapezium with parallel sides uu and vv and height tt, so its area is s=12(u+v)ts = \frac{1}{2}(u+v)t — the fifth equation, and arguably the most fundamental of the five, because it's the one that comes directly from 'area under the graph' with no algebra at all. The other three are what happens when you eliminate a variable between these two. Substitute v=u+atv = u+at into s=12(u+v)ts = \frac{1}{2}(u+v)t to remove vv: s=12(u+u+at)t=12(2u+at)t=ut+12at2s = \frac{1}{2}(u + u + at)t = \frac{1}{2}(2u+at)t = ut + \frac{1}{2}at^2 — the second equation. Substitute u=vatu = v-at into the same trapezium area instead, to remove uu: s=12(vat+v)t=12(2vat)t=vt12at2s = \frac{1}{2}(v-at+v)t = \frac{1}{2}(2v-at)t = vt - \frac{1}{2}at^2 — the third. And to eliminate tt rather than a velocity, rearrange v=u+atv=u+at to t=vuat = \frac{v-u}{a} and substitute into s=12(u+v)ts=\frac{1}{2}(u+v)t: s=12(u+v)vua=v2u22as = \frac{1}{2}(u+v)\cdot\frac{v-u}{a} = \frac{v^2-u^2}{2a}, giving v2=u2+2asv^2 = u^2 + 2as — the fourth. All five are one picture, looked at five different ways; memorising them as five unrelated facts is memorising the same idea five times over.

Traps — 4

two-stage-motion-treated-as-a-single-suvat-equation
The dominant trap in this whole topic, independently confirmed in at least two series. Jan 2023 Q5, a vehicle in two distinct phases of acceleration: "many failed to appreciate that they needed to consider two stages of the motion and tried to use t = 14 in a single suvat equation thereby achieving no credit." Jun 2024 Q5, a box falling from a helicopter and then decelerating under a parachute: "a very small number of candidates failed to realise there were two distinct stages of the motion and used an acceleration of 9.8 ms⁻² throughout," and separately, "the most common [error], assuming that the box was accelerating rather than decelerating." Two different series, two different physical scenarios, the same underlying failure: an acceleration valid for only part of a journey, applied as if it held for the whole thing.
halved-the-deceleration-time-instead-of-doubling-it
Verified on the real "acceleration, constant speed, deceleration over unknown time TT" graph question that anchors much of this topic: "a common error was to halve the time taken to decelerate rather than double it" (Jan 2023, Q1). Whatever ratio a question states between two time intervals — one phase taking twice, or three times, as long as another — the arithmetic has to go the direction the stem actually describes; a plausible-looking number produced by inverting that ratio is still wrong.
same-time-variable-reused-across-different-start-times
Verified on a "two particles released at different times" question (Jan 2020, Q3): "some candidates wrote down two correct expressions for the displacements but failed to realise that they referred to different starting times which led to inconsistent values of t." Each individual displacement expression can be entirely correct in isolation and the question can still fail at the moment they're set equal, if one particle's clock and the other's haven't been reconciled first — a later-released particle needs its own time variable, or the earlier one's time variable shifted by the head start, before the two expressions can be honestly compared.
quadratic-root-rejected-without-justification
Verified on a question where solving a suvat-derived quadratic left two roots, only one of them physically valid: "the vast majority found the two roots but some failed to explain clearly why they were rejecting 50" (Oct 2019, Q6), and separately, "candidates need to be reminded to show working when solving quadratics as those who had not derived the correct equation sometimes just wrote down an incorrect answer and received no credit." A kinematics quadratic's two roots are not automatically two valid answers — one can sit outside the time interval the model actually describes (e.g. after the particle has already stopped) — and finding both roots is only half the question; the other half is a stated reason for discarding the one that doesn't fit.

Say it out loud

Out loud, from memory, no notes: explain where the five equations come from — one graph, not five separate facts to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 4.1

1 lesson

Newton's Second Law in Vector Form

F = ma is one equation that is secretly two. Written in vector form, F=ma\mathbf{F}=m\mathbf{a} says a resultant force and the acceleration it produces are always exactly parallel, and finding one from the other is never more than dividing or multiplying each component by the mass separately. This exact spec point has thinner real-exam evidence behind it than any other lesson in this unit — one verified worked example, not three or four — so this lesson says so plainly, builds its practice around the one technique that IS verified, and is honest throughout about where a general Mechanics-marking rule is being applied to this topic rather than documented from it.

The card

F = ma in vector form: F and a are both vectors, m is a scalar — multiply/divide EACH component of a vector by m separately, never combine i and j into one number first.
pi+qj = ri+sj is true only if p=r AND q=s — i and j are independent directions, so equating coefficients isn't a shortcut, it's the only valid method.
More than one force acting? Find the resultant (vector sum) FIRST, then apply F=ma to that resultant — never to a single force alone.
Newton's second law isn't in the M1 formula booklet — the whole M1 section is two sentences confirming nothing extra is given. Know F=ma from memory, vector form included.
Omitting the mass (writing 'resultant force = a' instead of '= ma') is a method error, not a rounding slip — M0, not a small accuracy deduction.

Why it works — Why 'equate coefficients of i and j' isn't a trick — it's the only thing independent directions allow

i\mathbf{i} and j\mathbf{j} are unit vectors pointing in two fixed, perpendicular directions. Because they point in genuinely different directions, no amount of i\mathbf{i} can combine with any amount of j\mathbf{j} to produce a vector that looks like pure i\mathbf{i} or pure j\mathbf{j} again, unless the amount being added is exactly zero — algebraically, c1i+c2j=0c_1\mathbf{i}+c_2\mathbf{j}=\mathbf{0} forces c1=c2=0c_1=c_2=0, with no other solution possible, precisely because the two directions are independent of each other. This single fact is the entire justification for 'equating coefficients': if two vectors pi+qjp\mathbf{i}+q\mathbf{j} and ri+sjr\mathbf{i}+s\mathbf{j} are equal, their difference (pr)i+(qs)j(p-r)\mathbf{i}+(q-s)\mathbf{j} must be the zero vector, which by the fact just stated forces pr=0p-r=0 and qs=0q-s=0 separately — that is, p=rp=r AND q=sq=s, two independent equations produced by one vector equation, never one equation covering both unknowns at once. Applied to Newton's second law: F=ma\mathbf{F}=m\mathbf{a} written out as (Fii+Fjj)=m(aii+ajj)=(mai)i+(maj)j(F_i\mathbf{i}+F_j\mathbf{j}) = m(a_i\mathbf{i}+a_j\mathbf{j}) = (ma_i)\mathbf{i}+(ma_j)\mathbf{j} is genuinely two separate scalar equations in disguise — Fi=maiF_i=ma_i and Fj=majF_j=ma_j — and this is exactly the move the one real verified example for this spec point describes: an examiner report noting that candidates 'equated coefficients of i and j to find the values of p and q' (Jan 2022, Q6) is describing nothing more exotic than applying this fact directly.

Traps — 3

vector-equation-solved-as-if-it-were-one-scalar-equation
WME01-verified-facts.md's one verified real-paper fact for this exact spec point (Jan 2022 Q6) mostly names the CORRECT technique, not a documented wrong one — the record is that candidates 'equated coefficients of i and j to find the values of p and q.' The same examiner-report sentence this is drawn from does go on to name one further error too ('a few neglected to include m or subtracted rather than added the forces'), but Pearson's own examiner describes it as rare, with no numbers and no second series confirming it — thin enough that this lesson still builds its trap-taxonomy mostly around the correct technique's own implication rather than that one rare note (see the closing flag block for the full accounting). But the phrase names the trap by implication: a vector equation like pi+qj=12i+8jp\mathbf{i}+q\mathbf{j}=12\mathbf{i}+8\mathbf{j} is not one equation with two unknowns solved together — it is two entirely independent equations, p=12p=12 and q=8q=8, that happen to be written on one line. Treating it as a single combined equation (adding p+qp+q, or hunting for one 'resultant' unknown that covers both) has no valid method behind it — the mechanism block above shows why i and j being independent directions makes 'equate coefficients separately' the only route in, not one option among several.
mass-omitted-from-the-vector-equation-of-motion
Not specific to this exact spec point in WME01-verified-facts.md's own summary, but a real, verified, general Mechanics-marking principle that applies to it directly: the mark scheme's own general principles for Mechanics marking state plainly, "Omission of mass from a resolution is a method error" (verified, identical wording across MS_Jan2023/MS_Jan2024/MS_Oct2023's general marking guidance). This principle is also independently corroborated as spec-4.1-specific by the real Jan 2022 Q6 examiner report itself — checked directly against the primary Pearson PDF during this lesson's review pass, its full sentence on part (a) reads "a few neglected to include m or subtracted rather than added the forces, but such instances were rare" — real evidence for this exact spec point, just low-frequency rather than a fully worked trap. Newton's second law in vector form is F=ma\mathbf{F}=m\mathbf{a}, not F=a\mathbf{F}=\mathbf{a} — silently dropping the mass, whether because it "looks like" it cancels or because a is mistaken for the resultant force directly, produces an equation that only happens to be correct when m=1m=1. The marked-solution above reconstructs exactly this error and shows the real M0 consequence it carries.
newtons-second-law-applied-to-one-force-instead-of-the-resultant
Also a reasonable extension rather than a documented instance specific to this spec point: spec 4.1's own guidance pairs Newton's second law directly with spec 2.1/2.2's vector-addition content, and the most basic way to misapply F=ma\mathbf{F}=m\mathbf{a} when more than one force acts is to substitute just one of the forces present, as though the other force weren't there. The worked-chain above builds its very first stage entirely around catching this before any arithmetic starts, for exactly this reason.

Say it out loud

Out loud, from memory, no notes: explain why 'equate coefficients of i and j' isn't a trick — it's the only thing independent directions allow to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 4.2

1 lesson

Connected particles — pulleys, pegs, lifts, and cars with trailers

Every connected-particles question is asking the same underlying question four different ways. A car towing a trailer, two masses either side of a pulley, a lift carrying two people, a block sliding down a rough slope on a string — strip away the scenery and each one reduces to the same two facts: every particle joined to the system shares one acceleration, and every particle earns its own equation, F=maF = ma, written for it alone. What actually decides the mark is which forces belong in which equation — and the two traps that live right next to that decision: a system's total mass is not always one particle's own mass, and one string's tension is not automatically every string's tension.

The card

One string, one smooth pulley/peg: same tension both sides, same |a| for every connected particle.
Two separate strings in one system: two different tensions — draw each particle separately.
Incline: resolve along the slope (mg sinθ) and perpendicular (R = mg cosθ); friction = μR, opposing actual motion.
Whole-system equation: driving − resisting = (total mass) × a. Fast for a or D; isolate one particle for an internal force.
Lift with occupants: whole-system mass for the cable tension; each occupant's own equation for their own floor reaction.
g = 9.8; round final numerical answers to 2 or 3 s.f.

Why it works — Why the acceleration is shared but the tension isn't — unless it's the same string

Two physical facts do all the work here, and it matters that they're different facts. Inextensibility is a length constraint: however the system moves, the total length of a taut string (or the fixed geometry of a rigid rod) cannot change, which forces every particle joined by it to move exactly the same distance, in exactly the same time, as every other particle attached to the same connector — so their speeds match at every instant, and therefore so do their accelerations, in magnitude. That argument never mentions force. Masslessness is what produces the shared tension, and it only reaches as far as a single connector's own length: apply Newton's second law to the string (or rod) itself, treating it as a particle of mass zero, and the net force on it must be zero however it's accelerating — F=maF = ma with m=0m = 0 forces F=0F = 0, regardless of aa. For a straight length of string this means the pull at one end must exactly balance the pull at the other, so the tension is the same number everywhere along that one string. A smooth pulley or peg doesn't break this argument, it just bends the string's direction without adding any resisting force along it — spec 1.1's own modelling vocabulary calls this a 'light smooth pulley' for exactly that reason — so the tension on the two sides of a single string over a single smooth pulley is still one number. But the argument was always about ONE connector's own length. A second, physically separate string runs its own independent zero-net-force argument along its own length, with no reason at all to produce the same number as the first string's — the two tensions are related only through whichever particle both strings happen to touch, via that particle's own equation of motion, and nothing shortcuts that. This is precisely the distinction a real examiner report's advice targets when it recommends drawing a separate diagram for each connected particle: one diagram per particle keeps each connector's own tension attached to the string it actually belongs to, instead of letting a single symbol T quietly do service for two different physical quantities.

Traps — 7

car-trailer-weight-components-dropped
Verified on a real car-and-trailer question on an incline: "the most common mistake was omission of the weight components which, if done consistently, fortuitously led to a correct value of D but this received no credit due to the missing terms in the two equations" (Oct 2019, Q3). The word "fortuitously" is doing real work — dropping both weight components in a consistent way can make two errors cancel and still produce a plausible-looking final number, which is exactly why a mark scheme built from M/A/B codes checks that every term that should be in an equation is actually there, independent of whether the final number happens to come out right.
peg-pulley-unfamiliar-two-tension-terms
Verified on a real two-tension peg/pulley question: "many seemed unfamiliar with this type of situation involving two tensions" (Jun 2024, Q3), with the specific error named as "including an extra 3mg term in their system equation of motion or for missing the 3mg term when giving the equation for Q." The fix the same report names directly: "drawing a separate diagram for each of P and Q would have helped some candidates to set up these equations correctly."
peg-pulley-given-tension-substituted-wrong-place
Verified on the same question: "some responses showed confusion between the T value given and the T value to be found, resulting in the substitution of T = 3mg into the wrong place" (Jun 2024, Q3). Two different unknowns sharing the letter T — or a value of T handed to you partway through a multi-part question, then needed again for something new — is a labelling trap as much as a mechanics one: rename a value the moment it stops being unknown, rather than letting one symbol carry two different meanings.
lift-mass-of-lift-alone
Verified: candidates "using the mass of the lift alone... instead of the whole-system" mass when writing the equation of motion for a lift carrying occupants (Jan 2023, Q7).
lift-occupant-reactions-omitted
Verified, the same family of error seen from the other equation: "many candidates attempted an equation of motion for the lift but omitted the reactions from the two occupants" (Oct 2022, Q4). Confirmed as a repeat Pearson question type across two separate series, not a one-off — and, worked through with real numbers, both versions of the mistake collapse onto exactly the same missing terms (see the marked solution above).
incline-friction-direction-reversed
Verified, the single most consistently reported error on this exact rough-incline scenario type: "the most common error was having the frictional force acting down rather than up the plane" (Oct 2022, Q3). Friction opposes actual (or impending) relative motion — never gravity, never "the picture" — so its direction is the one force on an incline diagram that has to be reasoned out LAST, after the direction of motion is already settled, not drawn first out of habit.
incline-changed-acceleration-not-recognised
Verified on a two-part incline question where the force condition changed between parts: "a substantial number did not recognise that the system was subject to a different acceleration" in the second part (Jun 2024, Q6). An acceleration found in an earlier part of a question is not a constant carried forward automatically — any change to a force in the system (a different driving force, friction switching on or off, a changed angle) generally means a genuinely new equation of motion and a genuinely new value of a, exactly the discipline spec 4.2(ii)'s own guidance — a force which changes from one fixed value to another — is testing directly.

Say it out loud

Out loud, from memory, no notes: explain why the acceleration is shared but the tension isn't — unless it's the same string to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 4.4

2 lessons

Connected particles — pulleys, pegs, lifts, and cars with trailers

Every connected-particles question is asking the same underlying question four different ways. A car towing a trailer, two masses either side of a pulley, a lift carrying two people, a block sliding down a rough slope on a string — strip away the scenery and each one reduces to the same two facts: every particle joined to the system shares one acceleration, and every particle earns its own equation, F=maF = ma, written for it alone. What actually decides the mark is which forces belong in which equation — and the two traps that live right next to that decision: a system's total mass is not always one particle's own mass, and one string's tension is not automatically every string's tension.

The card

One string, one smooth pulley/peg: same tension both sides, same |a| for every connected particle.
Two separate strings in one system: two different tensions — draw each particle separately.
Incline: resolve along the slope (mg sinθ) and perpendicular (R = mg cosθ); friction = μR, opposing actual motion.
Whole-system equation: driving − resisting = (total mass) × a. Fast for a or D; isolate one particle for an internal force.
Lift with occupants: whole-system mass for the cable tension; each occupant's own equation for their own floor reaction.
g = 9.8; round final numerical answers to 2 or 3 s.f.

Why it works — Why the acceleration is shared but the tension isn't — unless it's the same string

Two physical facts do all the work here, and it matters that they're different facts. Inextensibility is a length constraint: however the system moves, the total length of a taut string (or the fixed geometry of a rigid rod) cannot change, which forces every particle joined by it to move exactly the same distance, in exactly the same time, as every other particle attached to the same connector — so their speeds match at every instant, and therefore so do their accelerations, in magnitude. That argument never mentions force. Masslessness is what produces the shared tension, and it only reaches as far as a single connector's own length: apply Newton's second law to the string (or rod) itself, treating it as a particle of mass zero, and the net force on it must be zero however it's accelerating — F=maF = ma with m=0m = 0 forces F=0F = 0, regardless of aa. For a straight length of string this means the pull at one end must exactly balance the pull at the other, so the tension is the same number everywhere along that one string. A smooth pulley or peg doesn't break this argument, it just bends the string's direction without adding any resisting force along it — spec 1.1's own modelling vocabulary calls this a 'light smooth pulley' for exactly that reason — so the tension on the two sides of a single string over a single smooth pulley is still one number. But the argument was always about ONE connector's own length. A second, physically separate string runs its own independent zero-net-force argument along its own length, with no reason at all to produce the same number as the first string's — the two tensions are related only through whichever particle both strings happen to touch, via that particle's own equation of motion, and nothing shortcuts that. This is precisely the distinction a real examiner report's advice targets when it recommends drawing a separate diagram for each connected particle: one diagram per particle keeps each connector's own tension attached to the string it actually belongs to, instead of letting a single symbol T quietly do service for two different physical quantities.

Traps — 7

car-trailer-weight-components-dropped
Verified on a real car-and-trailer question on an incline: "the most common mistake was omission of the weight components which, if done consistently, fortuitously led to a correct value of D but this received no credit due to the missing terms in the two equations" (Oct 2019, Q3). The word "fortuitously" is doing real work — dropping both weight components in a consistent way can make two errors cancel and still produce a plausible-looking final number, which is exactly why a mark scheme built from M/A/B codes checks that every term that should be in an equation is actually there, independent of whether the final number happens to come out right.
peg-pulley-unfamiliar-two-tension-terms
Verified on a real two-tension peg/pulley question: "many seemed unfamiliar with this type of situation involving two tensions" (Jun 2024, Q3), with the specific error named as "including an extra 3mg term in their system equation of motion or for missing the 3mg term when giving the equation for Q." The fix the same report names directly: "drawing a separate diagram for each of P and Q would have helped some candidates to set up these equations correctly."
peg-pulley-given-tension-substituted-wrong-place
Verified on the same question: "some responses showed confusion between the T value given and the T value to be found, resulting in the substitution of T = 3mg into the wrong place" (Jun 2024, Q3). Two different unknowns sharing the letter T — or a value of T handed to you partway through a multi-part question, then needed again for something new — is a labelling trap as much as a mechanics one: rename a value the moment it stops being unknown, rather than letting one symbol carry two different meanings.
lift-mass-of-lift-alone
Verified: candidates "using the mass of the lift alone... instead of the whole-system" mass when writing the equation of motion for a lift carrying occupants (Jan 2023, Q7).
lift-occupant-reactions-omitted
Verified, the same family of error seen from the other equation: "many candidates attempted an equation of motion for the lift but omitted the reactions from the two occupants" (Oct 2022, Q4). Confirmed as a repeat Pearson question type across two separate series, not a one-off — and, worked through with real numbers, both versions of the mistake collapse onto exactly the same missing terms (see the marked solution above).
incline-friction-direction-reversed
Verified, the single most consistently reported error on this exact rough-incline scenario type: "the most common error was having the frictional force acting down rather than up the plane" (Oct 2022, Q3). Friction opposes actual (or impending) relative motion — never gravity, never "the picture" — so its direction is the one force on an incline diagram that has to be reasoned out LAST, after the direction of motion is already settled, not drawn first out of habit.
incline-changed-acceleration-not-recognised
Verified on a two-part incline question where the force condition changed between parts: "a substantial number did not recognise that the system was subject to a different acceleration" in the second part (Jun 2024, Q6). An acceleration found in an earlier part of a question is not a constant carried forward automatically — any change to a force in the system (a different driving force, friction switching on or off, a changed angle) generally means a genuinely new equation of motion and a genuinely new value of a, exactly the discipline spec 4.2(ii)'s own guidance — a force which changes from one fixed value to another — is testing directly.

Say it out loud

Out loud, from memory, no notes: explain why the acceleration is shared but the tension isn't — unless it's the same string to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Friction — One Unified Model for Equilibrium and Motion on a Rough Plane

The WME01 spec states friction as two separate guidance lines under two separate sections — "F = μR when a particle is moving" (4.4) and "F ≤ µR in a situation of equilibrium" (5.3) — and it is entirely possible to revise them as two unrelated facts. Pearson's own question-writing doesn't: a particle resting on a rough plane and a particle accelerating down the same plane are the same scenario, split only by whether the resultant force is zero or not, and the single most heavily reported error on this whole topic — getting the friction force's *direction* wrong — costs marks in both versions equally, because neither equation says anything at all about which way F points.

The card

Equilibrium (not accelerating): F ≤ μR. Resolve perpendicular for R, resolve along the plane for F itself. F=0 is the trivial edge of this — not a separate rule.
On the point of sliding, or actually moving: F = μR exactly — the same ceiling, reached or exceeded, not a different equation.
Friction's direction: opposes the ACTUAL motion (moving) or the TENDENCY to slide (equilibrium) — never assumed from an applied force's direction or from habit.
A new or changed force in a later part = a brand-new equation of motion. Never reuse an earlier part's acceleration.
μ = tanθ for a particle on the point of sliding under gravity alone — divide the resolved equations directly; mass and g cancel.

Why it works — Why F ≤ μR becomes F = μR — the same physical boundary, approached from two sides

Picture a particle resting on a rough plane, with friction the only thing stopping it from sliding down under gravity. As long as the plane's incline is shallow, the weight component down the slope (mgsinθmg\sin\theta) is small, and friction only has to supply a small force to balance it — nowhere near the maximum it's capable of (μR\mu R). The particle sits in equilibrium, comfortably inside the inequality FμRF \le \mu R, with plenty of room to spare. Now imagine the incline steepening (or the surface getting smoother, or extra weight being added) — mgsinθmg\sin\theta grows, and the friction actually required to hold the particle still grows with it, while μR\mu R does not grow to keep pace — if anything it shrinks slightly, since R=mgcosθR=mg\cos\theta decreases as the angle steepens. Eventually FF needed for equilibrium reaches exactly μR\mu R — the particle is on the point of sliding, limiting equilibrium, the inequality now an equality — and one more increment of angle (or weight, or a smoother surface) and there is no value of FF left that can hold the particle still: the resultant along the plane is no longer zero, the particle accelerates, and FF stops being an unknown you solve for and becomes a known quantity, μR\mu R, that you substitute directly into F=maF=ma. FμRF \le \mu R and F=μRF=\mu R are not two different rules about two different kinds of situation — they are the same physical ceiling on how much friction is available, looked at from below it (equilibrium, with room to spare or exactly none) and from the moment a particle needs more than that ceiling can supply (motion). Nothing about the surface or the coefficient of friction itself changes at that boundary; only which side of the ceiling the required force sits on does.

Traps — 3

frictional-force-direction-reversed-on-a-rough-plane
Confirmed directly on a real rough-incline question: "the most common error was having the frictional force acting down rather than up the plane" (Oct 2022, Q3). Friction opposes the ACTUAL direction of relative sliding (or, in equilibrium, the direction the particle would tend to slide if friction vanished) — never the direction of an applied force, never "the direction the question feels like it should be," and never assumed from habit built up on simpler questions. This lesson's diagram and worked-chain both build their scenarios specifically so the correct direction is up the plane, deliberately reproducing the exact case this report documents students getting backwards.
changed-force-condition-assumed-not-to-change-the-acceleration
Confirmed on a real two-part incline question where a force condition changed between parts: "a substantial number did not recognise that the system was subject to a different acceleration" (Jun 2024, Q6). A particle continuing to move in the SAME direction across two parts of a question is not evidence that its acceleration is unchanged — if any force in the system has changed (a force added, removed, or altered in size), Newton's second law along the plane has to be rebuilt from scratch for that new part, never inherited from an earlier one. The marked-solution above reproduces this exact failure mode with real, checkable numbers, specifically chosen so the two accelerations really are different (not just relabelled).
equilibrium-and-limiting-motion-treated-as-two-unrelated-topics
Not a quoted student error from a mark scheme — this is the facts bank's OWN inference from the pattern across the archive (WME01-verified-facts.md §4, §7), named here as a trap because treating 4.4 and 5.3 as two disconnected spec items is the single easiest way to miss it: "Pearson's own question-writing treats statics of a particle on a rough plane and dynamics of a particle on a rough plane as the same scenario family split by whether acceleration is zero or not" — and the facts bank is explicit that this claim is "an inference from the pattern across the archive, not a fact stated anywhere in the spec text itself" (§7), not something Pearson has printed as a rule. Revising 4.4 and 5.3 as two separate equations to memorise, rather than as one resolving process with one variable outcome (does the along-plane resultant equal zero, or ma?), is the mechanism-level version of the direction and different-acceleration traps above — all three come from treating a rough-plane scenario as more disconnected from its own physics than it actually is.

Say it out loud

Out loud, from memory, no notes: explain why f ≤ μr becomes f = μr — the same physical boundary, approached from two sides to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 4.3

1 lesson

Momentum, Impulse, and the Sign-Convention Trap

The arithmetic in a momentum question is almost always short — one equation, substituted once. What sinks an otherwise perfect script is a single sign at the very end, and it is not a rare slip: three separate real series (Jan 2020, Oct 2022, Jun 2024) each record the same last mark lost, for the same reason — a candidate reports a velocity's sign where the question asked for a speed, and a speed is never negative.

The card

Momentum p = mv. Impulse I = mv − mu (the impulse-momentum principle). Neither is in the M1 formula booklet — memorise both.
Conservation, two particles colliding directly: m1u1 + m2u2 = m1v1 + m2v2. Every velocity is SIGNED, not a bare speed.
Fix a positive direction ONCE, before writing the equation. Every velocity — given or found — is signed relative to it.
A negative result is not an error. Reporting it as a 'speed' is: speed = |velocity|, never negative.
For an impulse question, start with whichever particle has the simpler known velocities (often the one at rest) — one substitution, no Newton's-third-law flip needed.
Restitution is NOT required at M1 (spec 4.3). Collision problems are confined to one dimension.

Why it works — Why momentum is conserved at all — it falls out of Newton's third law, not a separate law

During a direct collision, particle C exerts a force on particle D, and by Newton's third law, D exerts an equal and opposite force back on C, at every instant of contact — the two forces describe the same physical push, seen from its two sides. Because they act for exactly the same duration, the impulses they produce are also equal and opposite: the impulse D receives from C is the negative of the impulse C receives from D. Write that using the impulse-momentum principle applied separately to each particle: impulse on C =mC(vCuC)= m_C(v_C - u_C), impulse on D =mD(vDuD)= m_D(v_D - u_D), and "equal and opposite" means mC(vCuC)=mD(vDuD)m_C(v_C - u_C) = -m_D(v_D - u_D). Expand both sides and rearrange: mCvCmCuC=mDvD+mDuDm_C v_C - m_C u_C = -m_D v_D + m_D u_D, so mCuC+mDuD=mCvC+mDvDm_C u_C + m_D u_D = m_C v_C + m_D v_D — total momentum before the collision equals total momentum after it. Conservation of momentum is not an extra law bolted onto Newton's three; it is exactly what Newton's third law says once it is written in terms of impulse rather than force, applied to two particles instead of one. This derivation also explains, mechanically rather than as a rule to remember, why one shared sign convention has to cover BOTH particles at once: the identity above only holds if uCu_C, uDu_D, vCv_C and vDv_D are all measured against the same chosen positive direction. Switch which way is "positive" halfway through a working and the two sides of the equation stop describing the same collision.

Traps — 2

velocity-sign-carried-into-speed-answer
The single strongest, most independently confirmed trap anywhere in the WME01 examiner-report record — verified across three separate series, not one. Jan 2020: "the most common error was in not taking account of the direction of the velocity and so not producing a positive answer as required for the 'speed' of P." Oct 2022: "candidates need to be reminded that the final answer needed to be positive as speed was required." Jun 2024: "the final mark was often lost because it had been left as negative." All three describe the same failure: the working is correct up to and including a genuinely negative velocity, and the final mark is lost only by copying that sign into an answer the question specifically called a speed. The fix costs one line: take the magnitude, and state the direction in words if the question wants it too.
harder-particle-chosen-for-impulse
Confirmed on a real WME01 impulse question: "the majority of responses used particle A to find the impulse, rather than using particle B which was much easier since it started at rest" (Jun 2024, Q1). This isn't a correctness error — both routes reach the same right answer — but it is a genuine, examiner-documented efficiency cost: computing the impulse via the harder particle first, then having to invoke Newton's third law to flip the result onto the particle actually asked about, is an extra step with its own extra chance to drop a sign, for no extra credit. Before substituting anything, check which of the two particles in the question has the simpler known velocities (often, but not only, the one that started at rest) and start there.

Say it out loud

Out loud, from memory, no notes: explain why momentum is conserved at all — it falls out of newton's third law, not a separate law to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 5.3

1 lesson

Friction — One Unified Model for Equilibrium and Motion on a Rough Plane

The WME01 spec states friction as two separate guidance lines under two separate sections — "F = μR when a particle is moving" (4.4) and "F ≤ µR in a situation of equilibrium" (5.3) — and it is entirely possible to revise them as two unrelated facts. Pearson's own question-writing doesn't: a particle resting on a rough plane and a particle accelerating down the same plane are the same scenario, split only by whether the resultant force is zero or not, and the single most heavily reported error on this whole topic — getting the friction force's *direction* wrong — costs marks in both versions equally, because neither equation says anything at all about which way F points.

The card

Equilibrium (not accelerating): F ≤ μR. Resolve perpendicular for R, resolve along the plane for F itself. F=0 is the trivial edge of this — not a separate rule.
On the point of sliding, or actually moving: F = μR exactly — the same ceiling, reached or exceeded, not a different equation.
Friction's direction: opposes the ACTUAL motion (moving) or the TENDENCY to slide (equilibrium) — never assumed from an applied force's direction or from habit.
A new or changed force in a later part = a brand-new equation of motion. Never reuse an earlier part's acceleration.
μ = tanθ for a particle on the point of sliding under gravity alone — divide the resolved equations directly; mass and g cancel.

Why it works — Why F ≤ μR becomes F = μR — the same physical boundary, approached from two sides

Picture a particle resting on a rough plane, with friction the only thing stopping it from sliding down under gravity. As long as the plane's incline is shallow, the weight component down the slope (mgsinθmg\sin\theta) is small, and friction only has to supply a small force to balance it — nowhere near the maximum it's capable of (μR\mu R). The particle sits in equilibrium, comfortably inside the inequality FμRF \le \mu R, with plenty of room to spare. Now imagine the incline steepening (or the surface getting smoother, or extra weight being added) — mgsinθmg\sin\theta grows, and the friction actually required to hold the particle still grows with it, while μR\mu R does not grow to keep pace — if anything it shrinks slightly, since R=mgcosθR=mg\cos\theta decreases as the angle steepens. Eventually FF needed for equilibrium reaches exactly μR\mu R — the particle is on the point of sliding, limiting equilibrium, the inequality now an equality — and one more increment of angle (or weight, or a smoother surface) and there is no value of FF left that can hold the particle still: the resultant along the plane is no longer zero, the particle accelerates, and FF stops being an unknown you solve for and becomes a known quantity, μR\mu R, that you substitute directly into F=maF=ma. FμRF \le \mu R and F=μRF=\mu R are not two different rules about two different kinds of situation — they are the same physical ceiling on how much friction is available, looked at from below it (equilibrium, with room to spare or exactly none) and from the moment a particle needs more than that ceiling can supply (motion). Nothing about the surface or the coefficient of friction itself changes at that boundary; only which side of the ceiling the required force sits on does.

Traps — 3

frictional-force-direction-reversed-on-a-rough-plane
Confirmed directly on a real rough-incline question: "the most common error was having the frictional force acting down rather than up the plane" (Oct 2022, Q3). Friction opposes the ACTUAL direction of relative sliding (or, in equilibrium, the direction the particle would tend to slide if friction vanished) — never the direction of an applied force, never "the direction the question feels like it should be," and never assumed from habit built up on simpler questions. This lesson's diagram and worked-chain both build their scenarios specifically so the correct direction is up the plane, deliberately reproducing the exact case this report documents students getting backwards.
changed-force-condition-assumed-not-to-change-the-acceleration
Confirmed on a real two-part incline question where a force condition changed between parts: "a substantial number did not recognise that the system was subject to a different acceleration" (Jun 2024, Q6). A particle continuing to move in the SAME direction across two parts of a question is not evidence that its acceleration is unchanged — if any force in the system has changed (a force added, removed, or altered in size), Newton's second law along the plane has to be rebuilt from scratch for that new part, never inherited from an earlier one. The marked-solution above reproduces this exact failure mode with real, checkable numbers, specifically chosen so the two accelerations really are different (not just relabelled).
equilibrium-and-limiting-motion-treated-as-two-unrelated-topics
Not a quoted student error from a mark scheme — this is the facts bank's OWN inference from the pattern across the archive (WME01-verified-facts.md §4, §7), named here as a trap because treating 4.4 and 5.3 as two disconnected spec items is the single easiest way to miss it: "Pearson's own question-writing treats statics of a particle on a rough plane and dynamics of a particle on a rough plane as the same scenario family split by whether acceleration is zero or not" — and the facts bank is explicit that this claim is "an inference from the pattern across the archive, not a fact stated anywhere in the spec text itself" (§7), not something Pearson has printed as a rule. Revising 4.4 and 5.3 as two separate equations to memorise, rather than as one resolving process with one variable outcome (does the along-plane resultant equal zero, or ma?), is the mechanism-level version of the direction and different-acceleration traps above — all three come from treating a rough-plane scenario as more disconnected from its own physics than it actually is.

Say it out loud

Out loud, from memory, no notes: explain why f ≤ μr becomes f = μr — the same physical boundary, approached from two sides to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 5.2

1 lesson

Equilibrium of a Particle Under Coplanar Forces

A particle in equilibrium is only ever saying one thing: every force acting on it, added together as vectors, comes to exactly zero. Testing that in an exam almost always means resolving into two directions and setting each sum to zero — and the single most concretely documented way to lose marks doing it is not a wrong angle or a slipped decimal, it's a missing TERM. A real WME01 mark scheme records candidates writing 5=Fcos30°5 = F\cos30° where the correct equation was 5=Fcos30°+Tcos60°5 = F\cos30° + T\cos60° — an entire force quietly left out of the sum, on a real question this lesson is built to reconstruct. The same series shows resolving twice isn't the only credited route either: resolving in the direction of one force, or reaching for Lami's theorem, both count as full marks too, and are often faster.

The card

Equilibrium: the vector sum of every force is zero — resolve in any two independent directions and each sum of components must separately equal zero.
A resolution equation needs EVERY force with a component in that direction, each multiplied by its own sin or cos — miss one term and the whole equation is a method error (M0), whatever the arithmetic afterwards does.
Three examiner-credited methods for a coplanar equilibrium problem: resolve horizontally+vertically (always works); resolve along/perpendicular to an unknown force to eliminate the other (only when the two unknowns are mutually perpendicular); Lami's theorem, P/sinα=Q/sinβ=R/sinγ, each angle between the OTHER two forces.
Weight acts vertically down. Normal reaction acts perpendicular to the surface, away from it (push only). Tension pulls along a string, towards the string (pull only). Thrust is the same mechanism along a rigid rod, but pushing.
"Only simple cases of the application of the conditions for equilibrium to uncomplicated systems will be required" — spec 5.2's own scope limit.

Why it works — Why a resolution equation breaks the moment a term goes missing — and when a shortcut is genuinely available

The real general marking guidance for Mechanics defines an M mark itself in these words: "marks given for a correct method or an attempt at a correct method... resolving in a particular direction, taking moments about a point, applying a suvat equation..." — and the same mark schemes' own worked "General Principles for Mechanics Marking" make what that requires concrete for a resolution specifically: every term needing resolving must actually be multiplied by sin or cos, and an equation missing a required term is graded as a method error, not an accuracy slip (this is this course's own synthesis of that general principle, not a second verbatim quotation stitched onto the first — worth being precise about since blurring inference into quotation is exactly the kind of error a course built on citation discipline can't afford). Read together, this says a resolution equation is not partially right when a term is missing — it is a different, incomplete equation, describing a different (and wrong) physical system, one where a force that's actually present has been left out entirely. That is exactly why the real documented trap, 5=Fcos30°5=F\cos30° in place of 5=Fcos30°+Tcos60°5=F\cos30°+T\cos60°, is graded as a METHOD error (M0), not an accuracy error: the arithmetic that follows a correct equation can slip and still earn M1 A0 (method credited, final number wrong) — but an equation with a whole term missing was never the right method to begin with. Now the shortcut. Resolving in a direction PERPENDICULAR to an unknown force eliminates that force from the equation completely, because the cosine of the 90°90° angle between the resolved direction and that force's own line is exactly zero — the force still exists, it simply contributes nothing to THIS particular sum. In this lesson's main scenario, FF is at 30°30° above the horizontal and TT is at 60°60° below it, so the angle between FF's own line and TT's own line is 30°+60°=90°30°+60°=90°FF and TT happen to be mutually perpendicular. That is precisely why resolving ALONG FF's direction simultaneously resolves PERPENDICULAR to TT: the two descriptions coincide only because of this specific 90°90° relationship, and the method-comparison block below uses exactly that coincidence to solve for FF in one line. Change the two angles so they no longer sum to 90°90° (MCQ 2, below, does exactly this) and the two unknown forces are no longer perpendicular to each other — resolving along one no longer makes the other vanish, and the shortcut simply isn't available on that system, however much the equation might resemble one where it was.

Traps — 1

incomplete-resolution-missing-a-term
The one trap this lesson is built around, verified in exactly one series — worth stating that plainly, since three-force equilibrium is a small enough topic in the archive reviewed for this course that inflating "one series" into "commonly" would misrepresent the evidence. A real WME01 mark scheme records: "incomplete resolutions e.g. 5 = Fcos30 rather than 5 = Fcos30 + Tcos60" (Jan 2022, Q1). The mechanism is structural, not a one-off slip: a resolution equation is only a correct description of the system once EVERY force with a component in the resolved direction has contributed its own term, each multiplied by the cosine (or sine) of its own angle to that direction — and the real general marking guidance treats an equation missing a term as a METHOD error (M0), not merely a wrong final number, because the equation itself describes a different, incomplete system. This lesson's diagram, method-comparison and marked-solution blocks all use the SAME scenario specifically so the correct equation (5 = Fcos30° + Tcos60°) and the documented wrong one (5 = Fcos30°) sit side by side, reproducing the real fragment's exact shape rather than a generic warning about "being careful."

Say it out loud

Out loud, from memory, no notes: explain why a resolution equation breaks the moment a term goes missing — and when a shortcut is genuinely available to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 5.1

1 lesson

Equilibrium of a Particle Under Coplanar Forces

A particle in equilibrium is only ever saying one thing: every force acting on it, added together as vectors, comes to exactly zero. Testing that in an exam almost always means resolving into two directions and setting each sum to zero — and the single most concretely documented way to lose marks doing it is not a wrong angle or a slipped decimal, it's a missing TERM. A real WME01 mark scheme records candidates writing 5=Fcos30°5 = F\cos30° where the correct equation was 5=Fcos30°+Tcos60°5 = F\cos30° + T\cos60° — an entire force quietly left out of the sum, on a real question this lesson is built to reconstruct. The same series shows resolving twice isn't the only credited route either: resolving in the direction of one force, or reaching for Lami's theorem, both count as full marks too, and are often faster.

The card

Equilibrium: the vector sum of every force is zero — resolve in any two independent directions and each sum of components must separately equal zero.
A resolution equation needs EVERY force with a component in that direction, each multiplied by its own sin or cos — miss one term and the whole equation is a method error (M0), whatever the arithmetic afterwards does.
Three examiner-credited methods for a coplanar equilibrium problem: resolve horizontally+vertically (always works); resolve along/perpendicular to an unknown force to eliminate the other (only when the two unknowns are mutually perpendicular); Lami's theorem, P/sinα=Q/sinβ=R/sinγ, each angle between the OTHER two forces.
Weight acts vertically down. Normal reaction acts perpendicular to the surface, away from it (push only). Tension pulls along a string, towards the string (pull only). Thrust is the same mechanism along a rigid rod, but pushing.
"Only simple cases of the application of the conditions for equilibrium to uncomplicated systems will be required" — spec 5.2's own scope limit.

Why it works — Why a resolution equation breaks the moment a term goes missing — and when a shortcut is genuinely available

The real general marking guidance for Mechanics defines an M mark itself in these words: "marks given for a correct method or an attempt at a correct method... resolving in a particular direction, taking moments about a point, applying a suvat equation..." — and the same mark schemes' own worked "General Principles for Mechanics Marking" make what that requires concrete for a resolution specifically: every term needing resolving must actually be multiplied by sin or cos, and an equation missing a required term is graded as a method error, not an accuracy slip (this is this course's own synthesis of that general principle, not a second verbatim quotation stitched onto the first — worth being precise about since blurring inference into quotation is exactly the kind of error a course built on citation discipline can't afford). Read together, this says a resolution equation is not partially right when a term is missing — it is a different, incomplete equation, describing a different (and wrong) physical system, one where a force that's actually present has been left out entirely. That is exactly why the real documented trap, 5=Fcos30°5=F\cos30° in place of 5=Fcos30°+Tcos60°5=F\cos30°+T\cos60°, is graded as a METHOD error (M0), not an accuracy error: the arithmetic that follows a correct equation can slip and still earn M1 A0 (method credited, final number wrong) — but an equation with a whole term missing was never the right method to begin with. Now the shortcut. Resolving in a direction PERPENDICULAR to an unknown force eliminates that force from the equation completely, because the cosine of the 90°90° angle between the resolved direction and that force's own line is exactly zero — the force still exists, it simply contributes nothing to THIS particular sum. In this lesson's main scenario, FF is at 30°30° above the horizontal and TT is at 60°60° below it, so the angle between FF's own line and TT's own line is 30°+60°=90°30°+60°=90°FF and TT happen to be mutually perpendicular. That is precisely why resolving ALONG FF's direction simultaneously resolves PERPENDICULAR to TT: the two descriptions coincide only because of this specific 90°90° relationship, and the method-comparison block below uses exactly that coincidence to solve for FF in one line. Change the two angles so they no longer sum to 90°90° (MCQ 2, below, does exactly this) and the two unknown forces are no longer perpendicular to each other — resolving along one no longer makes the other vanish, and the shortcut simply isn't available on that system, however much the equation might resemble one where it was.

Traps — 1

incomplete-resolution-missing-a-term
The one trap this lesson is built around, verified in exactly one series — worth stating that plainly, since three-force equilibrium is a small enough topic in the archive reviewed for this course that inflating "one series" into "commonly" would misrepresent the evidence. A real WME01 mark scheme records: "incomplete resolutions e.g. 5 = Fcos30 rather than 5 = Fcos30 + Tcos60" (Jan 2022, Q1). The mechanism is structural, not a one-off slip: a resolution equation is only a correct description of the system once EVERY force with a component in the resolved direction has contributed its own term, each multiplied by the cosine (or sine) of its own angle to that direction — and the real general marking guidance treats an equation missing a term as a METHOD error (M0), not merely a wrong final number, because the equation itself describes a different, incomplete system. This lesson's diagram, method-comparison and marked-solution blocks all use the SAME scenario specifically so the correct equation (5 = Fcos30° + Tcos60°) and the documented wrong one (5 = Fcos30°) sit side by side, reproducing the real fragment's exact shape rather than a generic warning about "being careful."

Say it out loud

Out loud, from memory, no notes: explain why a resolution equation breaks the moment a term goes missing — and when a shortcut is genuinely available to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 6.1

1 lesson

Moments — Rods and Beams on Two Pivots, "About to Tilt"

Every rod-on-two-supports question is really asking you to pick a point. Take moments about the right one and an unknown reaction force vanishes from the equation before you've even started solving — not because it happens to be zero, but because it's being multiplied by zero. Three separate examiner reports converge on exactly this: pick the wrong point and you're solving two simultaneous equations for a problem that only needed one, and when a beam is "about to tilt," it is disarmingly easy to zero out the reaction at the wrong end.

The card

Moment of a force about a point = force × perpendicular distance from the point to the force's line of action.
A force acting AT the point you take moments about contributes zero, whatever its magnitude — this is why choosing a support as the pivot eliminates that support's own reaction.
Equilibrium of a rigid body: resultant force = 0 (resolve — one direction only, for parallel forces) AND resultant moment about ANY point = 0.
"About to tilt about X" means X is the support staying in contact; the reaction at the OTHER support is zero — not the reaction at X.
One moment equation (about a support) + one resolve equation is usually enough for two unknown reactions. Reaching for a second moments equation is a sign the first didn't use a support point.
Uniform rod: weight acts at the geometric midpoint. Non-uniform rod: weight acts wherever the question states the centre of mass to be — never assume the midpoint.

Why it works — Why the right pivot makes an unknown vanish — it's geometry, not luck

A moment is defined as force × perpendicular distance from the chosen point to the force's line of action. That definition has a consequence worth deriving explicitly rather than taking on faith: if a force acts AT the point you're taking moments about, its perpendicular distance from that point is exactly zero — so its moment about that point is force × 0 = 0, regardless of what the force's actual magnitude is. This is true even for a completely unknown reaction: you don't need to know R_C's value to know that R_C's moment about C is zero, because the multiplication by zero happens on the distance, not on the force. That is the entire mechanism behind "take moments about a support to eliminate its reaction" — it isn't a rule to memorise, it's what the definition of a moment already guarantees the instant you pick a point that force passes through. It is also exactly why the choice of point matters: choosing a point that ISN'T on a force's line of action leaves that force's (nonzero) distance in the equation, and the term survives. A rod resting on two supports has exactly two unknown reactions; taking moments about either support removes one of them from that equation immediately, turning "one equation, two unknowns" (unsolvable on its own) into "one equation, one unknown" (solved by rearranging a single line).

Traps — 5

wrong-reaction-zeroed-at-a-tilting-point
Confirmed verbatim, and the strongest single finding in this spec item's record: "it was necessary to appreciate that 'about to tilt' implied that one of the reactions had to be zero... A number of candidates equated the wrong reaction to zero i.e., in the case where the beam was about to tilt around C they assumed the reaction at C to be zero" (Jan 2023, Q4). The named pivot is the support that STAYS in contact; the reaction that vanishes belongs to the OTHER support. Say out loud which support is losing contact before writing anything as zero.
two-moments-equations-instead-of-moments-plus-resolve
Confirmed independently in two series. Jun 2024 Q4: "those that took moments about a different point required two equations to solve the problem and this inevitably led to more errors being made." Oct 2023 Q1, describing the successful approach by contrast: "Successful candidates then took moments about a number of different points to find the size of x... Where two moments equations were used, there was more opportunity for these errors." One support-point moment equation plus one resolve equation is (almost) always enough for two unknown reactions; reaching for a second moments equation is the sign a support point was not used the first time.
efficient-pivot-choice-explicitly-rewarded
The positive form of the same finding, confirmed in Jun 2024 Q4: "many realised that the smallest value of M would mean that the rod was about to tilt about C and therefore took moments about C. This produced an equation with M as the only unknown." Three series (Jan 2023, Jun 2024, Oct 2023) all reward the identical technique — take moments about the support whose reaction is already known (or about to become) zero, and the target unknown is left standing alone.
misread-relationship-between-two-given-unknowns
A related trap on the same spec item, from a rod held by two tensions rather than resting on two supports (the same technique — two unknown parallel forces along a rod, found by moments — applies either way): "the main errors were in the misinterpretation of the given information about the tensions. The tension at C was 20 N greater than the tension at A. However, pairs of values such as T and 20T, T and 20, or T and T were all seen on occasion" (Jan 2020, Q2). Before setting up any equation, write down in words what the stem's relationship between the two unknowns actually says — "20 more than," not "20 times."
modelling-assumption-confused-with-the-equilibrium-condition
"There was general appreciation that modelling the beam as a rod meant that it did not bend, [but] some candidates failed to achieve the mark for including wrong or irrelevant extra statements. The most common incorrect answers related to the mass (or centre of mass) of the rod and comments such as 'clockwise moments equal anticlockwise moments'" (Jan 2020, Q2(b)). "Clockwise moments equal anticlockwise moments" is the EQUILIBRIUM CONDITION, not a consequence of modelling the beam as a rod — it would be true (or not) whatever object the beam was modelled as. A question asking what the rod-model assumes is asking about rigidity and mass distribution, not restating the technique used to solve the rest of the question.

Say it out loud

Out loud, from memory, no notes: explain why the right pivot makes an unknown vanish — it's geometry, not luck to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Say these out loud before the exam

Every prompt below is answerable from the sheet above. If one stops you, that’s the page to go back to — and the fact that it stopped you is worth more than another read-through of the pages that didn’t.

  1. In one sentence: what do a "critique the model" part and a "hence show that" part have in common, in terms of what they're actually checking that a plain right-looking answer doesn't prove on its own?
  2. What is the "critique-the-model-answer-not-connected-to-the-stated-model" trap, and how do you catch it?
  3. What is the "show-that-final-value-stated-without-the-full-explanation" trap, and how do you catch it?
  4. What is the "modelling-term-treated-as-decorative-rather-than-load-bearing" trap, and how do you catch it?
  5. Without looking: what does this lesson say about the vocabulary spec 1.1 names, and what each term actually licenses in your working?
  6. Without looking: what does this lesson say about "hence show that" — a command word with its own marking discipline, used across the whole unit?
  7. In one sentence: why is the angle used in the triangle-of-forces cosine rule the SUPPLEMENT of the angle between the two forces, rather than that angle itself?
  8. What is the "bearing-sin-cos-pairing-swapped" trap, and how do you catch it?
  9. What is the "triangle-of-forces-supplement-not-taken" trap, and how do you catch it?
  10. What is the "incomplete-resolution-missing-a-term" trap, and how do you catch it?
  11. Without looking: what does this lesson say about forces as vectors: magnitude, direction, and what "resultant" means?
  12. Without looking: what does this lesson say about two routes to the same resultant, and a third worth knowing?
  13. In one sentence: how do you decide, just from a scenario's own wording, whether a kinematics question needs one suvat equation or two?
  14. What is the "two-stage-motion-treated-as-a-single-suvat-equation" trap, and how do you catch it?
  15. What is the "halved-the-deceleration-time-instead-of-doubling-it" trap, and how do you catch it?
  16. What is the "same-time-variable-reused-across-different-start-times" trap, and how do you catch it?
  17. What is the "quadratic-root-rejected-without-justification" trap, and how do you catch it?
  18. Without looking: what does this lesson say about what m1 actually gives you, and what you have to bring yourself?
  19. Without looking: what does this lesson say about the five suvat equations, and the condition they all quietly assume?
  20. In one sentence: why does a single vector equation like F=ma\mathbf{F}=m\mathbf{a} actually give you TWO separate pieces of information to work with, not one?
  21. What is the "vector-equation-solved-as-if-it-were-one-scalar-equation" trap, and how do you catch it?
  22. What is the "mass-omitted-from-the-vector-equation-of-motion" trap, and how do you catch it?
  23. What is the "newtons-second-law-applied-to-one-force-instead-of-the-resultant" trap, and how do you catch it?
  24. Without looking: what does this lesson say about newton's second law, and what changes when a force is written as a vector?
  25. Without looking: what does this lesson say about what's actually verified for this exact spec point — and what isn't?
  26. In one sentence: why does a system with two separate strings over two separate pulleys generally have two different tensions, even though every particle in it shares the same acceleration magnitude?
  27. What is the "car-trailer-weight-components-dropped" trap, and how do you catch it?
  28. What is the "peg-pulley-unfamiliar-two-tension-terms" trap, and how do you catch it?
  29. What is the "peg-pulley-given-tension-substituted-wrong-place" trap, and how do you catch it?
  30. What is the "lift-mass-of-lift-alone" trap, and how do you catch it?
  31. What is the "lift-occupant-reactions-omitted" trap, and how do you catch it?
  32. What is the "incline-friction-direction-reversed" trap, and how do you catch it?
  33. What is the "incline-changed-acceleration-not-recognised" trap, and how do you catch it?
  34. Without looking: what does this lesson say about connected particles: one shared acceleration, one equation per particle?
  35. Without looking: what does this lesson say about car and trailer: a connector that can push as well as pull?
  36. Without looking: what does this lesson say about lift with two occupants: one whole-system equation, one equation per person?
  37. In one sentence: why can a velocity inside a conservation-of-momentum equation come out negative, while an answer the question calls a "speed" never can?
  38. What is the "velocity-sign-carried-into-speed-answer" trap, and how do you catch it?
  39. What is the "harder-particle-chosen-for-impulse" trap, and how do you catch it?
  40. Without looking: what does this lesson say about momentum, impulse, and the one formula spec 4.3 names in words?
  41. In one sentence: what actually decides whether a rough-plane friction question needs the inequality FμRF \le \mu R or the exact equation F=μRF = \mu R — and why doesn't which way the plane is tilted decide it?
  42. What is the "frictional-force-direction-reversed-on-a-rough-plane" trap, and how do you catch it?
  43. What is the "changed-force-condition-assumed-not-to-change-the-acceleration" trap, and how do you catch it?
  44. What is the "equilibrium-and-limiting-motion-treated-as-two-unrelated-topics" trap, and how do you catch it?
  45. Without looking: what does this lesson say about one spec item, written twice — and pearson's own reason to treat it as one model?
  46. Without looking: what does this lesson say about resolving parallel and perpendicular, and the one decision that comes before any arithmetic?
  47. In one sentence: why does 5=Fcos30°5 = F\cos30° (with the Tcos60°T\cos60° term dropped) count as a METHOD error under the mark scheme's own general principles, not just an accuracy error?
  48. What is the "incomplete-resolution-missing-a-term" trap, and how do you catch it?
  49. Without looking: what does this lesson say about what 5.1 and 5.2 actually ask for?
  50. Without looking: what does this lesson say about three routes to the same equilibrium, one of them a genuine shortcut?
  51. In one sentence: why does taking moments about the support a rod is tilting about turn a two-unknown problem into a one-unknown equation?
  52. What is the "wrong-reaction-zeroed-at-a-tilting-point" trap, and how do you catch it?
  53. What is the "two-moments-equations-instead-of-moments-plus-resolve" trap, and how do you catch it?
  54. What is the "efficient-pivot-choice-explicitly-rewarded" trap, and how do you catch it?
  55. What is the "misread-relationship-between-two-given-unknowns" trap, and how do you catch it?
  56. What is the "modelling-assumption-confused-with-the-equilibrium-condition" trap, and how do you catch it?
  57. Without looking: what does this lesson say about rigid body, rod, and the two conditions for equilibrium?

Mechanics 1 · condensed sheet · not affiliated with or endorsed by Pearson Edexcel