a–t Graphs & Graph Interconversion

Bolted behind the dashboard of every modern car is a chip that reads an acceleration–time graph for a living. It samples the car's acceleration thousands of times a second, and the moment a crash begins it starts measuring the area under that violently spiking curve. When the area — which is a change in velocity, a Δv — crosses a threshold in a few milliseconds, the airbag fires. The chip never sees your position and never sees your speed directly; it reconstructs everything that matters from the a–t record alone. That is the skill of this module. You have already learned to read the other two graphs of motion: on an x–t graph the slope is velocity, and on a v–t graph the slope is acceleration while the area is displacement. The a–t graph completes the family, and it comes with the same two-part deal — its height tells you the acceleration now, and its area tells you how much the velocity has changed. But this module does something bigger than add a third graph. It assembles all three into a single ladder, x–t ↔ v–t ↔ a–t, with slopes carrying you down and areas carrying you up. Exam setters love this ladder: "here is a v–t graph, pick the matching a–t"; "here is an a–t profile, find the displacement". Those questions are gifts once the translation table is in your head — and near-guaranteed lost marks if it is not.

Key takeaways
  • The height of an a–t graph is the acceleration at that instant; a flat line means constant acceleration — which is why the a–t graphs of suvat problems look boringly rectangular, and why that is exactly the point.
  • Area under an a–t graph = change in velocity Δv over that interval — not velocity itself, and never displacement. Area below the time axis counts as negative Δv.
  • The a–t graph only remembers changes: to get the actual velocity you must be told the starting velocity uu, then v=u+area so farv = u + \text{area so far}.
  • The three graphs form a ladder — x at the top, v in the middle, a at the bottom. Going down the ladder you take slopes; going up you take areas plus a starting value.
  • To get displacement from an a–t graph you must climb twice: a–t → build the v–t graph → take its area. There is no one-step shortcut.
  • Key idea: slope reads downward (x→v→a) and area reads upward (a→v→x, plus starting values) — one translation table decodes every kinematics graph an exam can throw at you.
The core insight

An acceleration–time graph's height is the current acceleration and its signed area over an interval is the change in velocity Δv; combined with the x–t and v–t readings this completes a two-way ladder — slopes go down from position to velocity to acceleration, areas plus starting values go back up — so any one motion graph can be translated into the other two.

Where this lives today

Your phone contains the full ladder in silicon. A MEMS accelerometer streams an a–t record; software accumulates its area to track velocity and accumulates again for displacement — dead reckoning. It drifts (tiny errors in aa pile up through the double climb, and the unknown starting values must come from GPS or a known standstill), which is exactly the "graph only remembers changes" lesson wearing engineering clothes. Fitness watches counting strides, drones holding position indoors, and submarine and rocket inertial navigation all live on this double integration. The crash chip closes the loop with this module's first sentence: airbag controllers monitor the area under the deceleration spike and fire when Δv accrues too fast, while insurers' black boxes score braking harshness from the same record. And seismology runs the ladder at continental scale — an earthquake accelerogram is an a–t graph of the shaking ground, integrated once for ground velocity and twice for the permanent displacement of the fault.

The physical picture

Ride a lift from the ground floor and feel the journey: a push in your feet for the first couple of seconds, then a long stretch of feeling perfectly normal, then a floaty moment as it eases to a stop. That three-act sensation is an acceleration–time graph experienced from inside. Here is one honest lift ride — accelerate upward at 1 m/s21\ \text{m/s}^2 for 2 s, cruise for 4 s, brake at −1 m/s2-1\ \text{m/s}^2 for 2 s — drawn as all three graphs on the same clock:

Figure
One lift ride told three ways — x–t, v–t and a–t stacked on the same time axis
x (m) curve steepens, runs straight, then flattens 12 m v (m/s) 2 m/s cruise rises falls a (m/s²) area +2 m/s a = 0 (cruise) area −2 m/s 0 2 s 6 s 8 s same instants, three languages: slope of x–t = height of v–t; slope of v–t = height of a–t

Read the stack from the bottom up. The a–t graph is two rectangles and a gap: +1 m/s2+1\ \text{m/s}^2 for 2 s, zero for 4 s, −1 m/s2-1\ \text{m/s}^2 for 2 s. Its first rectangle has area 1×2=+21 \times 2 = +2 m/s — exactly the velocity gained, which is why the v–t graph climbs from 0 to 2 m/s over those seconds. The middle gap (zero acceleration) is the cruise: the v–t graph runs flat at 2 m/s, not at zero — this is the single most-tested distinction in the whole topic. The final rectangle sits below the axis with area −2-2 m/s, and the v–t line duly falls back to zero. One level higher, the x–t curve steepens while v grows, runs straight during the cruise, and flattens during braking. Same journey, three dialects. Notice what the a–t graph cannot tell you on its own: the lift's actual speed. The two rectangles say "gained 2, lost 2" — true whether the lift started at rest or was already plunging at 10 m/s. The a–t record keeps only changes. Every reconstruction upward needs a starting value handed to you separately.

Area under a–t: the Δv machine

The height of the graph answers "how hard is the velocity being pushed right now?". The area answers the accumulated question — "how much velocity has been gained or lost since we started watching?". For any interval,

Δv=signed area under the a–t graph(1)\Delta v = \text{signed area under the } a\text{–}t \text{ graph} \qquad (1)

where: Δv=vfinal−vinitial\Delta v = v_{\text{final}} - v_{\text{initial}} — the change in velocity over the interval, in m/s; area above the time axis counts positive, area below counts negative. The units confirm the reading: height in m/s² times width in s gives m/s — a velocity, not a distance. In the lift ride, the two rectangles contribute +2+2 and −2-2 m/s, so the net area over the full 8 s is zero: the lift ends as fast as it began (at rest), even though it is now 12 m higher.

Figure
The area machine — one rectangle of a–t turns height times width into a velocity change
t (s) a (m/s²) a = 3 1 4 area = 3 × 3 = 9 m/s = Δv height 3 m/s² width 3 s units decide the meaning: (m/s²) × s = m/s — a change in velocity, never a distance

To convert a Δv into an actual velocity, attach the starting value:

v=u+area under a–t from 0 to t(2)v = u + \text{area under } a\text{–}t \text{ from } 0 \text{ to } t \qquad (2)

where: uu — the initial velocity, supplied by the problem, never by the graph. Equation (2) is v=u+atv = u + at wearing graph clothing: for a constant-acceleration rectangle the area is just a×ta \times t. That is no coincidence — the suvat equations of the next module are this graph family with the areas worked out once and for all. It also explains why the a–t graph of a standard school problem is so visually dull: "uniform acceleration" draws a single flat rectangle. The flatness is the entire suvat world in one picture; the moment an exam draws you a non-flat a–t graph, it is telling you suvat is dead and areas are the only legal tool. One more reading, strictly one line of it: the slope of an a–t graph is called jerk — the rate of change of acceleration, felt as the snap when a driver stamps the brake rather than squeezing it. JEE-Advanced has name-checked it; nothing more is needed at this level.

The ladder: one table, every graph question

Everything from the last three modules compresses into a single two-way machine. Put position at the top, velocity in the middle, acceleration at the bottom:

graphheight (value) meansslope meansarea under it means
x–tposition xxvelocity vvnothing physical — never compute it
v–tvelocity vvacceleration aadisplacement Δx\Delta x
a–tacceleration aajerk (one-line JEE fact)change in velocity Δv\Delta v

Going down the ladder (x→v→ax \to v \to a) you take slopes. Going up (a→v→xa \to v \to x) you take areas — and you must add the starting value at each rung, because areas only deliver changes. The table is symmetric on purpose: each graph's slope is the height of the graph below it, and each graph's area is the change in the height of the graph above it. The ladder also dictates strategy for the question students freeze on: given an a–t graph, find the displacement. There is no one-step route — nothing on an a–t graph means displacement. You climb twice: use areas (plus uu) to build the v–t graph, then take the area of that. The ladder's other daily use is graph matching — and it defeats the trap examiners set most often, the option that merely copies the given graph's shape:

Figure
Matching drill — a rising-then-flat v–t graph and two candidate a–t graphs; translate slopes, never silhouettes
given: v–t slope +, then slope 0 option A: a–t ✓ flat positive, then drops to zero option B: a–t ✗ (shape copy) mimics the v–t silhouette — the bait the translation rising straight v–t segment: constant + slope → flat + a–t flat v–t segment: zero slope → a–t on the axis a straight segment NEVER maps to a slope
Derivation AWhy the area under an acceleration–time graph equals the change in velocity

We want to show that the area trapped between an a–t curve and the time axis equals Δv\Delta v, first for constant acceleration and then for any curve an examiner can draw. The strategy is the same one that gave "area under v–t = displacement" in the last module: start from the definition of acceleration, rearrange it into a statement about a rectangle, then chop a general curve into thin rectangular slices. Watch the signs — a rectangle hanging below the axis must come out as a velocity loss.

Step 1. For a constant acceleration aa acting over an interval Δt\Delta t, the definition a=Δv/Δta = \Delta v / \Delta t rearranges to Δv=a Δt\Delta v = a \, \Delta t.

Step 2. Read the right-hand side geometrically. On the a–t graph this stretch of motion is a horizontal line at height aa spanning a width Δt\Delta t: the product a×Δta \times \Delta t is exactly the rectangle's height times its width — its area. So for constant acceleration, area = Δv, with a negative height (aa below the axis) automatically producing a negative Δv. Why the sign takes care of itself: "height" on a graph is a signed coordinate, not a length. A braking phase drawn at −4 m/s2-4\ \text{m/s}^2 for 2 s has area (−4)(2)=−8(-4)(2) = -8 m/s — eight metres per second removed.

Step 3. Now let the acceleration vary. Slice the interval into strips so thin that within each strip aa barely changes; each strip is then an honest rectangle contributing its own small Δv=a Δt\Delta v = a\,\Delta t. The total change in velocity is the sum of all the strip areas.

Step 4. As the strips are made thinner, the staircase of rectangles hugs the true curve ever more closely, and the sum of strip areas becomes the exact area under the curve. So for any a–t graph, signed area = total Δv. (Making this slicing limit precise is exactly what an integral does — the calculus bridge module turns this picture into notation.) Verified: lift ride, first phase — rectangle of height 1 m/s² and width 2 s has area +2 m/s, matching the v–t graph's climb from 0 to 2 m/s; braking rectangle (−1)(2)=−2(-1)(2) = -2 m/s returns it to rest, and the net area +2+0−2=0+2 + 0 - 2 = 0 agrees with the lift starting and ending stationary.

Go deeper · Derivation B · 1 minRebuilding the full motion from an a–t record — the two-phase climb
Derivation BRebuilding the full motion from an a–t record — the two-phase climb

We are given only an a–t profile and a starting velocity, and we want the whole story: the v–t graph and the total displacement. Profile: u=5u = 5 m/s, then a=+2 m/s2a = +2\ \text{m/s}^2 for the first 3 s, then a=−1 m/s2a = -1\ \text{m/s}^2 for the next 4 s. The strategy is the ladder climbed rung by rung — areas of the a–t graph build the v–t graph (equation 2), then areas of the v–t graph deliver the displacement. This stepping procedure is exactly how a flight computer turns accelerometer readings into velocity and position, so the method matters more than the numbers.

Step 1. First rung, phase 1. Area under a–t from 0 to 3 s: (+2)(3)=+6(+2)(3) = +6 m/s. So v(3)=u+6=5+6=11v(3) = u + 6 = 5 + 6 = 11 m/s. Between those endpoints the velocity climbs along a straight line (constant slope +2+2).

Step 2. First rung, phase 2. Area from 3 s to 7 s: (−1)(4)=−4(-1)(4) = -4 m/s. So v(7)=11−4=7v(7) = 11 - 4 = 7 m/s. The v–t graph is now fully drawn: straight up from (0,5)(0, 5) to (3,11)(3, 11), then straight down to (7,7)(7, 7). Why we needed uu: the two areas +6+6 and −4-4 would be identical for a body launched at 5 m/s or at 500 m/s. The a–t graph fixes the shape of the v–t graph; the starting value pins its height.

Step 3. Second rung. Displacement is the area under the v–t graph just built. Phase 1 is a trapezium with parallel sides 5 and 11 over width 3: 12(5+11)(3)=24\tfrac{1}{2}(5 + 11)(3) = 24 m. Phase 2 is a trapezium with sides 11 and 7 over width 4: 12(11+7)(4)=36\tfrac{1}{2}(11 + 7)(4) = 36 m.

Step 4. Total displacement =24+36=60= 24 + 36 = 60 m. Notice the whole solution used nothing but rectangle and trapezium areas — no formula sheet, and it would have worked just as well had the a–t profile carried five phases. Verified against suvat, phase by phase: s1=ut+12at2=5(3)+12(2)(9)=15+9=24s_1 = ut + \tfrac{1}{2}at^2 = 5(3) + \tfrac{1}{2}(2)(9) = 15 + 9 = 24 m ✓; s2=11(4)+12(−1)(16)=44−8=36s_2 = 11(4) + \tfrac{1}{2}(-1)(16) = 44 - 8 = 36 m ✓; and v(7)=5+2(3)−1(4)=7v(7) = 5 + 2(3) - 1(4) = 7 m/s ✓.

Limiting cases

casea–t picturemeaning
flat line at zerograph lies on the time axisconstant velocity — the v–t graph is flat but NOT at zero
flat line above axisone rectanglethe entire suvat world; v–t is a rising straight line
flat line below axisrectangle hanging downwardsteady braking or gravity on the way up; v–t falls steadily
tall, narrow spikehuge height, tiny widtha kick or collision: finite Δv delivered almost instantly — the airbag scenario
net area zero over an intervalpositives cancel negativesvelocity returns to its starting value — the body is generally NOT back at its starting place
slope of a–t nonzeroramping accelerationjerk: force is still building; suvat illegal, areas still fine

The zero-net-area row hides a favourite trap. Our lift gained and lost the same 2 m/s, net area zero — yet it moved 12 m. Cancelling velocity changes never cancels displacement, because displacement lives one rung higher, under the v–t graph.

Worked examples

Board level — from an a–t profile to the final velocity (CBSE/ISC pattern)

A particle starts with velocity u=4u = 4 m/s. Its acceleration–time graph shows: a=+2 m/s2a = +2\ \text{m/s}^2 from t=0t = 0 to t=3t = 3 s, a=0a = 0 from t=3t = 3 s to t=5t = 5 s, and a=−4 m/s2a = -4\ \text{m/s}^2 from t=5t = 5 s to t=6t = 6 s. Find the velocity at t=3t = 3 s, at t=5t = 5 s and at t=6t = 6 s, and the net change in velocity over the 6 s.

Step 1. Read areas phase by phase, signs included. Phase 1: (+2)(3)=+6(+2)(3) = +6 m/s. Phase 2: zero area — nothing changes. Phase 3: (−4)(1)=−4(-4)(1) = -4 m/s.

Step 2. Climb from uu using equation (2). v(3)=4+6=10 m/sv(3) = 4 + 6 = \boxed{10\ \text{m/s}}.

Step 3. v(5)=10+0=10 m/sv(5) = 10 + 0 = \boxed{10\ \text{m/s}} — the flat-zero stretch is a cruise at 10 m/s, not a stop.

Step 4. v(6)=10−4=6 m/sv(6) = 10 - 4 = \boxed{6\ \text{m/s}}.

Step 5. Net Δv=+6+0−4=+2 m/s\Delta v = +6 + 0 - 4 = \boxed{+2\ \text{m/s}} — which checks: vfinal−u=6−4=2v_{\text{final}} - u = 6 - 4 = 2 m/s ✓.

Competitive level — a–t given, displacement demanded (JEE-Main pattern)

A body starts from rest. Its acceleration is +3 m/s2+3\ \text{m/s}^2 for the first 4 s, then −6 m/s2-6\ \text{m/s}^2 for the next 2 s. Find the total displacement and the final velocity.

Step 1. Diagnose the route before touching numbers: displacement from an a–t graph = climb the ladder twice. Build v–t first; its area comes second. Anyone hunting for a single formula here donates the mark.

Step 2. Build the v–t graph by areas. Phase 1: Δv=(3)(4)=+12\Delta v = (3)(4) = +12 m/s, so vv climbs straight from 0 to 12 m/s at t=4t = 4 s. Phase 2: Δv=(−6)(2)=−12\Delta v = (-6)(2) = -12 m/s, so vv falls straight from 12 back to 0 m/s\boxed{0\ \text{m/s}} at t=6t = 6 s. The v–t graph is a triangle with apex (4,12)(4, 12).

Step 3. Displacement = area of that triangle, split at the apex: 12(4)(12)+12(2)(12)=24+12=36 m\tfrac{1}{2}(4)(12) + \tfrac{1}{2}(2)(12) = 24 + 12 = \boxed{36\ \text{m}}.

Step 4. Sanity checks. Net a–t area =12−12=0= 12 - 12 = 0 ✓ matches vfinal=vinitial=0v_{\text{final}} = v_{\text{initial}} = 0; and displacement is positive throughout since vv never went negative — the body slowed but never reversed. Timing note: 90 seconds. Thirty for the v–t sketch, thirty for the triangle areas, thirty for the sanity check. The wrong-route penalty is brutal here — students who try to force s=ut+12at2s = ut + \tfrac{1}{2}at^2 across both phases at once (as if one acceleration ruled all 6 s) manufacture nonsense like s=12(3)(36)=54s = \tfrac{1}{2}(3)(36) = 54 m.

Exam traps

Area under a–t sold as displacement. The most-marked wrong answer on this graph. Its area has units (m/s2)(s)=m/s(\text{m/s}^2)(\text{s}) = \text{m/s} — a velocity change. Displacement needs the second climb. When in doubt, multiply the axis units; the dimensions never lie.

Forgetting the starting velocity. Areas deliver Δv, not v. A "+6 m/s area" question with u=4u = 4 m/s wants 10, and the option grid will offer 6. If the problem hides uu in words ("starts from rest", "moving at 4 m/s when timing begins"), extract it before touching the graph.

Dropping the sign of below-axis area. A rectangle below the time axis subtracts velocity. Treating all areas as positive turns a slow-down into a speed-up and typically doubles the true final speed.

a = 0 read as "at rest". Flat-on-axis a–t means constant velocity. The companion error — reading v=0v = 0 as a=0a = 0 at a turnaround point — is the same confusion mirrored one rung up.

Shape-copying between graphs. The a–t graph of a rising-straight v–t is NOT another rising line — it is a flat one (constant slope ⇒ constant height one rung down). Matching questions bait you with the option that merely looks like the given graph. Translate slopes and heights; never match silhouettes.

Assuming the graphs must join smoothly. An a–t graph may jump vertically (a foot stamping the brake) — that is legal idealization. But the v–t graph it builds can only kink, never jump, and the x–t graph above stays smooth even at the kinks. A matching option showing a v–t graph with a vertical cliff is physically wrong for these problems and can be eliminated on sight.

Origins · 1 minLeonhard Euler and how this was discovered
LE
Leonhard Euler
1707–1783 · Basel, St Petersburg, Berlin

Euler turned Newton's laws into the working machinery this module runs on. His Mechanica (1736) recast dynamics in the language of coordinates and rates — acceleration as the rate of change of velocity, applied point by point along a motion — which is precisely the ladder read downward. More remarkably, he built the ladder's upward direction too: faced with equations too hard to solve exactly, Euler stepped through them — take the current acceleration, hold it for a tiny interval, update the velocity by a Δta\,\Delta t, update the position by v Δtv\,\Delta t, repeat. That "Euler's method" is the thin-slices argument of this module made into an algorithm. Every drone autopilot, phone step-counter and spacecraft navigation computer alive today converts accelerometer records into velocity and position by exactly his stepping recipe, millions of times per second.

History
1687
— Newton's Principia ties force to acceleration, making a(t) the quantity that laws of physics actually specify.
1736
— Euler's Mechanica rewrites Newton in coordinates and rates: the slope-ladder x → v → a becomes standard language.
1768
— Euler publishes his stepping method: rebuild v and x from a by accumulating thin slices — the area-ladder as an algorithm.
1961
— Apollo-era inertial navigation flies: gyroscopes plus accelerometers integrate a–t twice to steer spacecraft with no view outside.
1993
— The ADXL50 MEMS accelerometer puts a crash-sensing a–t reader on a fingernail-sized chip, and the airbag decision becomes an area calculation.

Going further

Texts. NCERT Physics XI Part 1, Ch. 2-3 (motion graphs) — the CBSE/NEET canon · H.C. Verma, Concepts of Physics Vol. 1, Ch. 3 · Halliday, Resnick & Walker Ch. 2 (graphical integration boxes) · AP Physics 1 CED, Unit 1 graphical analysis skills. The calculus that makes the thin-slices argument exact is exactly one module away.

Provenance. All readings follow from a=Δv/Δta = \Delta v/\Delta t and the slicing argument; no result here exceeds NCERT Ch. 3 + standard graphical analysis. A verifier should recompute: lift ride areas (1)(2)=+2(1)(2) = +2, (−1)(2)=−2(-1)(2) = -2 m/s, net 0, displacement 12(2)(2)+(4)(2)+12(2)(2)=2+8+2=12\tfrac{1}{2}(2)(2) + (4)(2) + \tfrac{1}{2}(2)(2) = 2 + 8 + 2 = 12 m; derivation B: v(3)=5+6=11v(3) = 5 + 6 = 11, v(7)=11−4=7v(7) = 11 - 4 = 7 m/s, areas 12(5+11)(3)=24\tfrac{1}{2}(5+11)(3) = 24, 12(11+7)(4)=36\tfrac{1}{2}(11+7)(4) = 36, total 60 m, against suvat 15+9=2415 + 9 = 24 and 44−8=3644 - 8 = 36 ✓; board example v=4+6=10v = 4 + 6 = 10, 10−4=610 - 4 = 6 m/s, net +2+2 ✓; JEE example triangle 12(4)(12)+12(2)(12)=36\tfrac{1}{2}(4)(12) + \tfrac{1}{2}(2)(12) = 36 m ✓.

Prerequisites. Velocity–Time Graphs — slope = a and area = Δx, the rungs this module assembles. Leads to. Kinematic Equations for Uniform Acceleration — the flat-rectangle world solved once and for all · TECHNIQUE: Graph Reading at Speed — the ten graph-MCQ patterns drilled against the clock.

If the area under a–t gives Δv, what gives Δx?

Nothing on the a–t graph itself — that is the honest answer and the point of the ladder. Displacement is the area under the v–t graph, one rung up. So from an a–t record you climb twice: areas (plus the starting velocity uu) rebuild v(t); then the area under that rebuilt curve is Δx. There is no legal shortcut, and dimension-checking proves it: a–t area carries units of m/s, and no amount of staring turns a velocity into a distance without another factor of time — which is exactly what the second climb supplies.

Why do I need the initial velocity — isn't the graph supposed to contain the whole motion?

The a–t graph contains the whole story of changes and none of the story of starting points. Two cars, one at rest and one at 100 km/h, both cruising steadily, have identical a–t graphs: flat zero. The graph cannot distinguish them, so the problem must. This is the physics face of what calculus calls a constant of integration, and it is why every reconstruction question hands you a phrase like "starts from rest" or "moving at 5 m/s at t = 0". Train yourself to underline that phrase first — it is data, not decoration.

Can acceleration really jump vertically like the graphs show?

Strictly no — a truly instantaneous jump in acceleration would need a force applied in literally zero time. Real a–t records ramp steeply (the ramp's slope even has a name, jerk). But when a foot hits a brake in 50 milliseconds and the question's clock ticks in seconds, drawing the change as a vertical cliff is an idealization too accurate to matter. The hierarchy worth memorizing: a–t may jump (forces can switch fast), v–t may only kink (velocity cannot teleport — its change is an area, and areas grow continuously), and x–t stays smooth even where v–t kinks.

The net area under my a–t graph came out zero. Does the body end up where it started?

No — it ends up as fast as it started, which is a different thing entirely. Zero net a–t area means Δv = 0, so the final velocity equals the initial one. Our lift gained 2 m/s and lost 2 m/s (net area zero) yet climbed 12 m. To claim the body is back at its starting place you would need the v–t graph's net area to vanish instead — which requires the velocity to actually reverse and spend balancing time negative, like a ball thrown up and caught at the same height.

Why is the a–t graph flat in almost every textbook problem?

Because the school syllabus lives in the constant-acceleration world: gravity near the surface, uniform braking, suvat. A constant acceleration draws a rectangle — visually boring, computationally kind. The a–t graph earns its keep in precisely the questions where it is NOT flat: multi-phase journeys (build v phase by phase), graph-matching items, and JEE questions with triangular or ramping a–t where suvat is illegal but areas still work. A non-flat a–t graph is a flashing sign: "abandon formulas, compute areas".

Is there ever a reason to compute the slope of an a–t graph?

Only for one specific mark: the slope of a–t is jerk — the rate at which acceleration itself changes, felt as the difference between a chauffeur easing onto the brake and a learner stamping it. JEE-Advanced has asked for its value and its units (m/s3\text{m/s}^3); AP and boards do not touch it. Know the one-liner, spend nothing more on it. (Slope of a–t is emphatically NOT velocity — that guess appears in every option grid.)

How do I attack graph-matching questions quickly?

Translate one feature at a time, moving down the ladder. Pick the given graph, mark where its slope is positive, zero, negative — that sign pattern IS the graph one rung down. Then check magnitudes: straight segments have constant slope, so the graph below must be flat there; curved segments mean the graph below is changing height. Kill options that merely copy the given graph's shape (the classic bait), then kill any v–t option with a vertical jump. Two translations usually leave exactly one survivor — total cost under a minute.

Before this

Where this leads