Everything, on one sheet

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. When a part asks for a stated number of ways (e.g. "state two ways"), name exactly that many and stop — on real mark schemes for this list format (verified: Oct 2019, Notes for qu 6, part (e)), each correct named way earns a mark up to that count, and each further WRONG way offered beyond it costs -1.
"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. A second, narrower category of valid answer sits alongside an explicitly-named simplification: an implicit assumption about how the model's own given boundary or measurement data were obtained, even though the stem never states it in so many words. This lesson's own anchor question's real credited list (Oct 2019 Q6(e): do not have an instantaneous change from acceleration to constant speed / do not have constant velocity / do not have constant acceleration / reaction time at start / stop watch error at end) includes two answers — reaction time at start, stop watch error at end — that relax no simplification the stem states outright; they relax an assumption baked into treating the model's own start time and recorded duration as exact. The boundary stays narrow even so: the same mark scheme explicitly rejects air resistance (already excluded by the question), friction at the ground, and the height or size of the athlete as extra answers beyond the credited two — so a valid answer ties to either (a) the model's own stated kinematic structure, or (b) how the model's own given boundary or timing data were obtained, never to any generically-true real-world detail, however plausible it sounds on its own. The discipline is small and mechanical: find the sentence that states the simplification (or, for the reaction-time/timing category, identify what the model treated as instant or exact without saying so), name what it gave up, and answer exactly what the sub-part's own wording asks next — sometimes that's just naming the refinement, sometimes it's naming it and stating what changes. This lesson's own sole real verified anchor, Oct 2019 Q6(e) ("state two ways... in which the model could be made to be more realistic"), is marked B1 B1 purely for naming two valid refinements — no accuracy/direction-of-effect mark exists in that question's scheme at all, and the real mark scheme penalises incorrect extras (-1 each), so padding a naming-only answer with unsolicited effect commentary in place of a genuine second refinement is a real way to drop a mark, not a safe default.

Traps — 4

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.

naming-more-modifications-than-the-question-asked-for

A real, verified penalty rule, confirmed in this lesson's own anchor mark scheme's "Notes for qu 6," 6(e): "+1 for each correct answer (max of 2), -1 for each incorrect extra answer after two answer[s]." When a part asks for a stated number of ways, naming a third, wrong one costs a mark even if the first two named are both correct — so name exactly the number asked for and stop. This is a different habit from the "name it, then explain its effect" pattern used elsewhere in this lesson: explaining a correctly-named modification's effect isn't an extra "way" and isn't what this penalty targets. The risk is specifically in listing additional candidate modifications beyond the number the question asks for, in case any of them turn out wrong.

The card

1 hour 30 minutes, 75 marks. Students answer all questions — no choice of question, no optional section.
7 or 8 compulsory questions — not fixed by the spec, varies by series (Jan 2019, Oct 2023: 7; most other series: 8). No sections, no MCQ — one flat sequence of structured, multi-part written questions.
About 1.2 minutes (72 seconds) per mark on average — real question tariffs range from about 6 to 14 marks each, so budget against each question's own printed marks, not the flat average.
Marked in M/A/B/DM lines, not AO bands. An M mark needs the right mechanical principle AND a dimensionally correct equation (sin/cos actually applied, mass/length terms actually present) — a correct final number with the equation missing a required term still scores M0.
Formula booklet gives M1 nothing beyond Pure Mathematics 1/2 — suvat, momentum (mv), and impulse (mv - mu) must be memorised, not looked up.
Ordinary scientific calculator only, like every IAL Maths unit — no CAS/symbolic algebra. There is no calculator-free paper anywhere in this qualification.

Why it works — What an M Mark Actually Requires in Mechanics, and Why a Numerically Correct Answer Can Still Score Zero

On a Pure paper, "a correct method or an attempt at a correct method" is close to the whole story for an M mark. On WME01, the general marking guidance adds a Mechanics-specific clause the Pure papers don't carry — verbatim, identical wording confirmed across MS_Jan2023, MS_Jan2024, and MS_Oct2023: "M" marks "are marks given for a correct method or an attempt at a correct method. In Mechanics they are usually awarded for the application of some mechanical principle to produce an equation, e.g. resolving in a particular direction, taking moments about a point, applying a suvat equation, applying the conservation of momentum principle etc." That extra sentence is doing real work: it means the examiner isn't just asking "did they attempt something," but "does the equation on the page actually correspond to that named principle, applied correctly." Concretely, verified from the same guidance, an equation only earns its M mark if it has the right number of terms and is dimensionally correct — in a resolution, every term that needs resolving has to actually carry a sin or cos factor; in a moments equation, every term has to genuinely be a force×distance or mass×distance quantity (g's may cancel, but the structure still has to be there). This is why the guidance draws three specific lines Pure marking never needs to: "Omission of mass from a resolution is a method error" and "Omission of a length from a moments equation is a method error" — both cost the M mark itself, not just accuracy — while "Omission or extra g in a resolution is an accuracy error not method error," meaning the same M mark survives even though the final number will be wrong. An "A" mark, dependent accuracy — "can only be awarded if the previous M mark has been earned. e.g. M0 A1 is impossible" — and a "B" mark, "independent accuracy... where there is no method (e.g. often given for a comment or for a graph)," complete the same three-code system WMA13's own page documents, but every dependent A mark on THIS paper is only as safe as an M mark that has to survive this Mechanics-specific dimensional check first, not merely "an attempt" in the abstract. A separate, standing g-value convention repeated across nearly every examiner report reviewed for this course completes the picture: use g = 9.8 and round the final answer to 2 or 3 significant figures; "Use of g = 9.81 should be penalised once per (complete) question"; over- or under-accuracy is penalised once per question, but "premature approximation should be penalised every time it occurs" — so a numerically-correct-looking answer can still lose marks it never visibly touched, if an intermediate value was rounded too early on the way there.

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θ. This is the SAME equation as the triangle-of-forces cosine rule below, just with the supplement substituted in: cos(180° − θ) = −cosθ turns R² = P² + Q² − 2PQcos(180° − θ) into this one. Do not take the supplement here — θ is the raw common-point angle, not the triangle's interior angle.
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\theta$ and north-component $\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 — 4

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. Worth knowing for the mark tally specifically: the real Jun 2024 Q7(a) mark scheme explicitly condones this exact sin/cos mix-up at the method-mark level — "Condone sign errors and sin/cos confusion but both components must be resolved" — so in practice this error usually costs only the accuracy mark (1 of the 2 marks), not both; the marked-solution block above shows the M1/A0 split directly.

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.

minimum-distance-t-value-confused-with-minimum-value

Verified in a single series only — not independently repeated elsewhere in the archive reviewed for this lesson, unlike the other traps here. The SAME Jun 2024 Q7 that supplies the bearing-swap trap above continues into a minimum-distance-between-two-moving-particles problem (spec 2.2: application of vectors to displacements and velocities in a plane), where a relative position vector is differentiated to find when the particles are closest. The report records two distinct errors on it: "those using the derivative method often confused the t value, when the minimum occurs (7/12), with the minimum value of d² (80)" — conflating WHEN a minimum occurs with WHAT the minimum value is — and, separately, on the alternative equal-components method, "a significant number of candidates wrote down an incorrect time of 24/10 rather than 10/24." Neither error is built into a full worked example in this lesson: the differentiation step belongs to spec 2.2's wider application-of-vectors content rather than this lesson's resolve/cosine-rule/bearing scope, and the facts bank does not promote this single-series fact to standalone-lesson-worthy status.

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.

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θ. This is the SAME equation as the triangle-of-forces cosine rule below, just with the supplement substituted in: cos(180° − θ) = −cosθ turns R² = P² + Q² − 2PQcos(180° − θ) into this one. Do not take the supplement here — θ is the raw common-point angle, not the triangle's interior angle.
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\theta$ and north-component $\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 — 4

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. Worth knowing for the mark tally specifically: the real Jun 2024 Q7(a) mark scheme explicitly condones this exact sin/cos mix-up at the method-mark level — "Condone sign errors and sin/cos confusion but both components must be resolved" — so in practice this error usually costs only the accuracy mark (1 of the 2 marks), not both; the marked-solution block above shows the M1/A0 split directly.

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.

minimum-distance-t-value-confused-with-minimum-value

Verified in a single series only — not independently repeated elsewhere in the archive reviewed for this lesson, unlike the other traps here. The SAME Jun 2024 Q7 that supplies the bearing-swap trap above continues into a minimum-distance-between-two-moving-particles problem (spec 2.2: application of vectors to displacements and velocities in a plane), where a relative position vector is differentiated to find when the particles are closest. The report records two distinct errors on it: "those using the derivative method often confused the t value, when the minimum occurs (7/12), with the minimum value of d² (80)" — conflating WHEN a minimum occurs with WHAT the minimum value is — and, separately, on the alternative equal-components method, "a significant number of candidates wrote down an incorrect time of 24/10 rather than 10/24." Neither error is built into a full worked example in this lesson: the differentiation step belongs to spec 2.2's wider application-of-vectors content rather than this lesson's resolve/cosine-rule/bearing scope, and the facts bank does not promote this single-series fact to standalone-lesson-worthy status.

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.

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.
Stage 2 doesn't have to end at v=0 — it ends wherever the stem's own boundary is (a stated distance, a time limit, hitting the ground). Read that off the wording; don't assume it by default.
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 $u$ (the initial velocity) at $t=0$ and rising or falling steadily to height $v$ at time $t$. 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 = \frac{v-u}{t}$, rearranged immediately into $v = 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 $u$ to $v$ over a time $t$ is a trapezium with parallel sides $u$ and $v$ and height $t$, so its area is $s = \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+at$ into $s = \frac{1}{2}(u+v)t$ to remove $v$: $s = \frac{1}{2}(u + u + at)t = \frac{1}{2}(2u+at)t = ut + \frac{1}{2}at^2$ — the second equation. Substitute $u = v-at$ into the same trapezium area instead, to remove $u$: $s = \frac{1}{2}(v-at+v)t = \frac{1}{2}(2v-at)t = vt - \frac{1}{2}at^2$ — the third. And to eliminate $t$ rather than a velocity, rearrange $v=u+at$ to $t = \frac{v-u}{a}$ and substitute into $s=\frac{1}{2}(u+v)t$: $s = \frac{1}{2}(u+v)\cdot\frac{v-u}{a} = \frac{v^2-u^2}{2a}$, giving $v^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 — 5

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 $T$" 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.

second-stage-assumed-to-end-at-rest-instead-of-the-stated-boundary

A different failure from the dominant trap that opens this list, and one that only strikes after a student has already done the hard part right: having correctly split the journey into two stages, stage 2 is then assumed to run until $v=0$ by default — when the stem actually cuts it off earlier, at a stated distance, a stated time, or (this lesson's own anchor real paper) the ground itself. Jun 2024 Q5 drops a parachute-and-box system from a helicopter; part (b) asks for "the speed with which P lands on the ground" and scores the A mark for $v=4$ (m s$^{-1}$) — not $0$ — because the box reaches the ground, a positional boundary, before its parachute-deceleration would ever bring it to rest. Part (d)'s own marking notes for the accompanying speed-time graph make the trap explicit: the shape scores B0 "if continuous vertical line at the end or graph ends on the t-axis," and the labelled figures score B0ft "if they just assume it stops as it reaches the ground." A two-stage journey's second stage ends wherever the question's own boundary actually is — read it from the stem, never assume it by default.

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

$\mathbf{i}$ and $\mathbf{j}$ are unit vectors pointing in two fixed, perpendicular directions. Because they point in genuinely different directions, no amount of $\mathbf{i}$ can combine with any amount of $\mathbf{j}$ to produce a vector that looks like pure $\mathbf{i}$ or pure $\mathbf{j}$ again, unless the amount being added is exactly zero — algebraically, $c_1\mathbf{i}+c_2\mathbf{j}=\mathbf{0}$ forces $c_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 $p\mathbf{i}+q\mathbf{j}$ and $r\mathbf{i}+s\mathbf{j}$ are equal, their difference $(p-r)\mathbf{i}+(q-s)\mathbf{j}$ must be the zero vector, which by the fact just stated forces $p-r=0$ and $q-s=0$ separately — that is, $p=r$ AND $q=s$, two independent equations produced by one vector equation, never one equation covering both unknowns at once. Applied to Newton's second law: $\mathbf{F}=m\mathbf{a}$ written out as $(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 — $F_i=ma_i$ and $F_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 $p\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=12$ and $q=8$, that happen to be written on one line. Treating it as a single combined equation (adding $p+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 $\mathbf{F}=m\mathbf{a}$, not $\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=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 $\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.

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 = ma$ with $m = 0$ forces $F = 0$, regardless of $a$. 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.

two-tension-system-unfamiliar-terms

Verified on a real two-tension question (two particles connected in series by separate vertical strings, no pulley — the exact configuration in the marked solution above): "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."

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.

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 = ma$ with $m = 0$ forces $F = 0$, regardless of $a$. 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.

two-tension-system-unfamiliar-terms

Verified on a real two-tension question (two particles connected in series by separate vertical strings, no pulley — the exact configuration in the marked solution above): "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."

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.

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 ($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 ($\mu R$). The particle sits in equilibrium, comfortably inside the inequality $F \le \mu R$, with plenty of room to spare. Now imagine the incline steepening (or the surface getting smoother, or extra weight being added) — $mg\sin\theta$ grows, and the friction actually required to hold the particle still grows with it, while $\mu R$ does not grow to keep pace — if anything it shrinks slightly, since $R=mg\cos\theta$ decreases as the angle steepens. Eventually $F$ needed for equilibrium reaches exactly $\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 $F$ left that can hold the particle still: the resultant along the plane is no longer zero, the particle accelerates, and $F$ stops being an unknown you solve for and becomes a known quantity, $\mu R$, that you substitute directly into $F=ma$. $F \le \mu R$ and $F=\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 question (Jun 2024 Q6, set on a rough horizontal plane, not an incline) 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.

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 $= m_C(v_C - u_C)$, impulse on D $= m_D(v_D - u_D)$, and "equal and opposite" means $m_C(v_C - u_C) = -m_D(v_D - u_D)$. Expand both sides and rearrange: $m_C v_C - m_C u_C = -m_D v_D + m_D u_D$, so $m_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 $u_C$, $u_D$, $v_C$ and $v_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 — 4

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.

sign-as-mass-constraint-not-just-speed-fix

The sign-convention discipline this lesson builds around a final speed extends further than a speed. The same requirement — a velocity must come out with a specific sign — can instead pin down an unknown MASS. A real WME01 mark scheme scores exactly this move: verbatim, "M1 Correct inequality for their v, containing u. N.B. Their first statement must include u and > 0 or < 0 as appropriate," followed by "(4m2 − 3m1) > 0 => 4m2 > 3m1 => m2 > (3/4)m1 * Given answer A1*." The matching examiner report names the mechanism directly: "Successful candidates needed to appreciate whether their expression for velocity found in part (b) was > 0 or < 0 depending on the direction they had chosen as positive. Only the use of the correct inequality could lead to marks being scored in this part." Applied to this lesson's own C/D scenario: suppose only C's rebound is assumed ($v_C < 0$), with the masses left as unknowns $m_C$ and $m_D$. From conservation of momentum, $m_C u_C + m_D u_D = m_C v_C + m_D v_D$, isolate $v_C$, and require it negative — the identical sign-convention discipline this lesson already teaches, pointed at a mass ratio instead of a speed.

hence-show-that-needs-full-working-to-stated-target

"Hence show that" is a general command-word convention, not a momentum-specific one, but it is worth naming here because the anchor question behind this lesson's central sign-convention trap ends on exactly this instruction. Examiner report, General section, naming this same question directly: "when a question asks candidates to 'hence show that', as in question 1(c), 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... it was important that there was sufficient correct working and that the final conclusion was exactly as stated in the question." Two consequences follow for any 'hence show that' part: every step has to be shown, not only the final line, and the working must land on the given target's exact stated form — not an equivalent expression the marker is left to accept on trust.

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 ($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 ($\mu R$). The particle sits in equilibrium, comfortably inside the inequality $F \le \mu R$, with plenty of room to spare. Now imagine the incline steepening (or the surface getting smoother, or extra weight being added) — $mg\sin\theta$ grows, and the friction actually required to hold the particle still grows with it, while $\mu R$ does not grow to keep pace — if anything it shrinks slightly, since $R=mg\cos\theta$ decreases as the angle steepens. Eventually $F$ needed for equilibrium reaches exactly $\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 $F$ left that can hold the particle still: the resultant along the plane is no longer zero, the particle accelerates, and $F$ stops being an unknown you solve for and becomes a known quantity, $\mu R$, that you substitute directly into $F=ma$. $F \le \mu R$ and $F=\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 question (Jun 2024 Q6, set on a rough horizontal plane, not an incline) 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.

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=F\cos30°$ in place of $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°$ 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, $F$ is at $30°$ above the horizontal and $T$ is at $60°$ below it, so the angle between $F$'s own line and $T$'s own line is $30°+60°=90°$ — $F$ and $T$ happen to be mutually perpendicular. That is precisely why resolving ALONG $F$'s direction simultaneously resolves PERPENDICULAR to $T$: the two descriptions coincide only because of this specific $90°$ relationship, and the method-comparison block below uses exactly that coincidence to solve for $F$ in one line. Change the two angles so they no longer sum to $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 — 2

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."

weight-confused-with-mass

A second, distinct trap from this same real examiner report, verified in the same paragraph as the trap above but not previously covered by this lesson despite the lesson's own header claiming to have reviewed this report in full: "It was also not uncommon for weight to be confused with mass resulting in the use of 5g" (WME01_01_pef_20220303.pdf, Jan 2022, Q1) — the general mechanism spec 5.2 already teaches above: weight is $mg$, a FORCE, not a mass, so multiplying a value already given in newtons by g again is a category error, not a rounding slip. (What the real question's 5 N specifically represents — weight or otherwise — is not confirmed by this trap sentence alone; see GROUNDING above and the closing flag block, both of which still flag this as unconfirmed.) Whatever it represents, the PEF confirms it was already correctly given in force units, and that real candidates nonetheless wrote 5g (≈49 N, using g=9.8) in its place — treating an already-force value as if it were still a mass needing conversion. Every subsequent line of working is then wrong by a factor of g, however correctly the resolving technique itself is applied afterwards.

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=F\cos30°$ in place of $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°$ 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, $F$ is at $30°$ above the horizontal and $T$ is at $60°$ below it, so the angle between $F$'s own line and $T$'s own line is $30°+60°=90°$ — $F$ and $T$ happen to be mutually perpendicular. That is precisely why resolving ALONG $F$'s direction simultaneously resolves PERPENDICULAR to $T$: the two descriptions coincide only because of this specific $90°$ relationship, and the method-comparison block below uses exactly that coincidence to solve for $F$ in one line. Change the two angles so they no longer sum to $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 — 2

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."

weight-confused-with-mass

A second, distinct trap from this same real examiner report, verified in the same paragraph as the trap above but not previously covered by this lesson despite the lesson's own header claiming to have reviewed this report in full: "It was also not uncommon for weight to be confused with mass resulting in the use of 5g" (WME01_01_pef_20220303.pdf, Jan 2022, Q1) — the general mechanism spec 5.2 already teaches above: weight is $mg$, a FORCE, not a mass, so multiplying a value already given in newtons by g again is a category error, not a rounding slip. (What the real question's 5 N specifically represents — weight or otherwise — is not confirmed by this trap sentence alone; see GROUNDING above and the closing flag block, both of which still flag this as unconfirmed.) Whatever it represents, the PEF confirms it was already correctly given in force units, and that real candidates nonetheless wrote 5g (≈49 N, using g=9.8) in its place — treating an already-force value as if it were still a mass needing conversion. Every subsequent line of working is then wrong by a factor of g, however correctly the resolving technique itself is applied afterwards.

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 with a known rod weight; if the rod's own weight or centre of mass is unknown, expect one moment equation per given "about to tilt" scenario, solved simultaneously. 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. This is scoped to the common case — rod weight known, two unknown reactions. It does not apply when the rod's own weight and centre-of-mass position are themselves unknown: Jan 2023 Q4 (the source of the trap above) is exactly that case — a non-uniform branch tested via two separate 'on the point of tilting' conditions — and its mark scheme credits two support-point moment equations, one per scenario (M(C) for scenario 1, M(D) for scenario 2), solved simultaneously via a dependent method mark (DM1). That is not the inefficiency described above: with two rod-intrinsic unknowns (W and x) instead of two reactions, each scenario supplies exactly one independent equation, and both are required.

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.