Force vectors and resultants
Push on a door near the hinge and it barely moves; push the same force at the handle and it swings wide open. Even before you touch on where a force acts (that is next chapter's territory — moments), the very first skill every mechanics problem demands is representing a force honestly, as a vector with both size and direction, and combining several such forces into one equivalent push or pull. A force is not a bare number; means nothing on its own until you fix an angle too. This article builds the algebraic toolkit — resolving a force into rectangular components, adding forces by the parallelogram law or, far more reliably, by summing components, and expressing a force along a known line of action using a unit vector. Every later topic in this course — moments, couples, equivalent force systems, equilibrium of particles and rigid bodies — leans on this vector arithmetic, so getting it fluent now pays off for the rest of the semester.
Any force can be written as with and , and the resultant of several concurrent forces is found reliably by summing their components, , rather than by imprecise graphical addition.
The core idea
A force in a plane, of magnitude acting at angle from the positive -axis, resolves into rectangular components as
where: are unit vectors along the - and -axes, is measured counter-clockwise positive from the reference axis, and the magnitude recovers as . In three dimensions the same idea extends to . When a force is known only to act along a line from point to point , rather than by an angle, its direction comes from a unit vector along that line:
where: is the position vector from to and is the known magnitude of the force along that line — this is the standard way cable and strut forces are entered into a problem. Two forces can be combined graphically by the parallelogram law (draw both from a common tail, complete the parallelogram, the diagonal from that tail is the resultant) or equivalently the triangle law (place the tail of one at the head of the other; the closing side is the resultant). Both are useful for visualising direction but too imprecise for real computation. The reliable method is component addition: resolve every force into - and -components, add the components algebraically (respecting sign), then recombine.
where: the direction of follows from , with the quadrant fixed by checking the individual signs of and separately, since the inverse tangent alone only returns an angle between and . For a concurrent force system — every force passing through one common point — this component sum is the complete resultant; there is only one line of action the combined push can have. For a non-concurrent system the same sum still gives the correct resultant force, but a single force no longer fully replaces the system: a resultant moment about a chosen point is also needed to capture the turning effect, a topic that follows once moments are introduced. A convenient shortcut for exactly two forces of known magnitude and included angle comes straight from the law of cosines,
where: is the angle between and when both are drawn tail-to-tail; the law of sines then gives the resultant's direction relative to either force, useful as a fast check on a component calculation.
The goal is to show, without relying on drawing an accurate scaled diagram, that the resultant of any number of concurrent forces is obtained purely algebraically by summing each force's - and -components separately, and that this sum is exact regardless of how many forces are involved or how they are oriented, which is why component addition replaces the parallelogram law as the everyday computational tool.
Step 1. Write each force in component form. For concurrent forces , each acting at its own angle from the positive -axis, the unit-vector definition of resolution gives for every from to . This step rests only on the definition of rectangular components introduced above; no new assumption is added.
Step 2. Add the vectors using vector addition rules. Vector addition is defined component-by-component, so . Each bracket is exactly and , the algebraic sum of all the individual -components and all the individual -components.
Step 3. Recover magnitude and direction from the summed components. Since with and , the Pythagorean relation for a vector's magnitude gives , and the direction follows from , i.e. with the quadrant fixed by the individual signs of and .
Step 4. Note why concurrency matters here. Because every force passes through the same point, there is no ambiguity about where acts — it acts through that same common point, and alone is a fully equivalent replacement for the whole force system. If the forces were not concurrent, this same would still be the correct resultant force, but replacing the system entirely would additionally require a resultant moment, since a non-concurrent set of forces can also produce a net turning effect that a single force positioned arbitrarily cannot represent.
Worked example
Two forces act on a hook: at above the horizontal, and at below the horizontal (both measured from the positive -axis, so is at ). Find the resultant force, and also confirm the magnitude using the law-of-cosines shortcut.
Step 1. Resolve each force into components. , ; , .
Step 2. Sum the components separately. , and . Both sums are positive, so the resultant will land in the first quadrant.
Step 3. Compute magnitude and direction. , and above the horizontal. Answer: at above the horizontal.
Competitive stretch
Check with the law-of-cosines shortcut instead. The angle between (at ) and (at ) is . Then , matching Step 3 to within rounding — a fast independent check on any two-force resultant.
Common traps
- Mixing degrees and radians on a calculator when evaluating or — always check the angle mode before resolving.
- Trusting alone for direction; it only returns an angle in , so the signs of and must be checked separately to place the resultant in the correct quadrant.
- Treating a non-concurrent system's vector sum as the complete answer — the resultant force is correct, but a general system also needs a resultant moment, covered once moments are introduced.
- Sign errors when an angle is given as "below the horizontal" or "west of south" — always convert to a single consistent reference (standard position from the -axis, counter-clockwise positive) before writing any component.
Ask the tutor: if resolving an angle given in an unusual reference (like "20 degrees below the horizontal" or a bearing) into signed components is tripping you up, ask the AI tutor to work through a few more force-triangle examples with you step by step.
Why bother with components at all if the parallelogram law already gives the resultant graphically?
The parallelogram law is exact in principle, but drawing it accurately by hand or scale is slow and error-prone, especially with more than two forces or forces in three dimensions. Component addition turns the same physics into arithmetic: resolve each force once, add columns of numbers, and recombine. It scales effortlessly to many forces and to 3-D, and it is what every later topic in the course — equilibrium equations, moment calculations, structural analysis — actually uses. The parallelogram law remains valuable for building physical intuition and for a quick sanity check on your answer's rough direction.
How do I know whether a force system is concurrent or not, and why does it matter so much?
A system is concurrent if the lines of action of all the forces, extended if necessary, pass through one common point — check this from the geometry of the problem, not from the numbers alone. It matters because a concurrent system's net effect is completely described by the single resultant force found by summing components; there is no separate turning effect to worry about, since every force already passes through the same point. A non-concurrent system can still produce a net turning effect even after the forces are summed to zero force, so replacing it fully requires both a resultant force and a resultant moment, which is why the distinction is flagged early and revisited once moments are covered.
When should I use the law-of-cosines shortcut instead of resolving into components?
The law-of-cosines route, , is fastest when you have exactly two forces and already know the angle between them, and you only need the magnitude (with the law of sines for direction if needed). It becomes clumsy for three or more forces, where tracking separate included angles is far more error-prone than simply summing components. Many students use it as a quick independent check on a component calculation, exactly as in the competitive stretch above — if the two methods disagree, a sign or angle error is somewhere in the component work.