Time, Distance and Speed

Almost every quantitative problem you will face in a judiciary preliminary paper or the CLAT-PG aptitude segment reduces to a single, deceptively simple relationship: distance = speed × time. The challenge is never the formula; it is recognising which of its many costumes — a train crossing a platform, two cars closing on a highway, a boat fighting a current, an average over an unequal journey — is on the page in front of you. This chapter builds the topic from that one equation outward, layering relative speed, conversions, average-speed traps, trains, boats and streams, circular motion and races, with fully worked sums calibrated to the difficulty of ratio-driven questions that examiners actually set. Because this is a law site, we also do something most aptitude guides cannot: we show where speed and stopping distance stop being arithmetic and become evidence, tracing the Supreme Court's treatment of "high speed" in rash-and-negligent-driving prosecutions. Return to the aptitude and reasoning hub at any point to see how this slots into the wider syllabus.

The Core Relationship and Why It Is Enough

Speed is the rate at which distance is covered, so the master equation is Distance = Speed × Time. Rearranged, Speed = Distance ÷ Time and Time = Distance ÷ Speed. Many candidates memorise a triangle with D on top and S and T below; cover the quantity you want and the remaining two show whether to multiply or divide. That mnemonic is fine, but the deeper habit to build is dimensional thinking: if distance is in kilometres and time in hours, speed is in km/hr; if you are handed metres and seconds, speed comes out in m/s. Mismatched units are the single largest source of avoidable error in this topic.

The relationship is linear in each variable when the third is held constant, and this gives rise to two proportionality rules that solve a surprising fraction of questions without any equation at all. At constant speed, distance is directly proportional to time. Over a fixed distance, speed is inversely proportional to time — double the speed and you halve the time. The inverse rule is exactly the same machinery you used in inverse proportion, which is why mastering ratios pays compound dividends here. If a car covers a route in 6 hours at 60 km/hr and you are asked the time at 90 km/hr, you need no formula: speeds are in ratio 60:90 = 2:3, so times are in the inverse ratio 3:2, giving 6 × (2/3) = 4 hours.

Unit Conversion: km/hr to m/s and Back

The two units you will toggle between are kilometres per hour and metres per second. One kilometre is 1000 metres and one hour is 3600 seconds, so to convert km/hr into m/s you multiply by 1000/3600, which simplifies to 5/18. To go from m/s back to km/hr you multiply by the reciprocal, 18/5. Commit these two fractions to memory; they appear in nearly every train and platform problem.

For example, 72 km/hr in m/s is 72 × 5/18 = 20 m/s. Conversely, 25 m/s in km/hr is 25 × 18/5 = 90 km/hr. A quick sanity check: m/s figures are always smaller than the same speed expressed in km/hr (because a metre is far shorter than a kilometre while a second is far shorter than an hour, and the kilometre factor dominates), so 20 m/s being less than 72 km/hr is exactly what you expect. The fluency to convert in one step, without writing out 1000 and 3600, separates candidates who finish the quantitative section from those who run out of clock.

Average Speed: The Harmonic-Mean Trap

Average speed is total distance divided by total time — never, under any circumstances, the simple arithmetic mean of the speeds. This is the most heavily examined misconception in the entire topic, and examiners bait it relentlessly. If a traveller covers equal distances at two different speeds, the arithmetic average overstates the true average, because the body spends more time at the slower speed and that slower leg should weigh more.

The clean result for two equal-distance legs at speeds x and y is the harmonic mean: Average speed = 2xy ÷ (x + y). Suppose a lawyer drives to court at 40 km/hr and returns over the identical route at 60 km/hr. The naive answer of 50 km/hr is wrong; the correct figure is 2 × 40 × 60 ÷ (40 + 60) = 4800/100 = 48 km/hr. The average always tilts toward the slower speed. By contrast, if the two legs take equal time rather than cover equal distance, then the arithmetic mean (x + y)/2 is correct, because each speed now governs the same slice of time. Reading the question to identify whether distances or times are equal is therefore the whole game. The underlying idea — weighting by the right base — is the same logic that powers weighted averages in data interpretation.

Relative Speed: Two Bodies in Motion

When two bodies move, the speed that matters for the gap between them is not their individual speed but their relative speed. The rule is short and absolute. If they move in the same direction, relative speed is the difference of their speeds. If they move toward or away from each other (opposite directions), relative speed is the sum. Once you have the relative speed, every two-body problem collapses back into the single-body equation, with the relevant distance being the gap to be closed or opened.

Two trains on parallel tracks, 100 km/hr and 60 km/hr, moving the same way: the faster gains on the slower at 100 − 60 = 40 km/hr, so it closes a 20 km lead in half an hour. The same two trains head-on: they approach at 100 + 60 = 160 km/hr and shut a 320 km gap in 2 hours. Pursuit problems — a thief with a head start, a guard giving chase — are pure same-direction relative-speed sums: divide the head-start distance by the difference of speeds to get the catch-up time. The structural similarity to rate problems in time and work, where combined rates add, is not coincidental; both are applications of additive rates.

Trains: When Length Joins the Distance

Train problems are the flagship application of this chapter because they introduce one twist absent from point-object motion: the moving body has its own length, and that length is part of the distance. The governing question is always, "from the first instant of contact to the last instant of separation, how far has the front of the train travelled?"

The four standard cases follow mechanically. Crossing a pole, signal or stationary man (a point object): distance = length of the train. Crossing a platform, bridge or tunnel (an object with length): distance = length of train + length of platform. Crossing another train moving in the opposite direction: distance = sum of both lengths, speed = sum of both speeds. Crossing or overtaking another train in the same direction: distance = sum of both lengths, speed = difference of speeds. A 200 m train at 20 m/s crossing a 300 m bridge covers 200 + 300 = 500 m at 20 m/s, taking 25 seconds. Master the four cases and convert every speed to m/s first, and train problems become routine.

Boats and Streams: Motion in a Moving Medium

Boats-and-streams problems add a current that helps or hinders the boat. Let the speed of the boat in still water be B and the speed of the stream be S. Downstream, the current aids the boat, so downstream speed = B + S. Upstream, the boat fights the current, so upstream speed = B − S. From these two, the two quantities examiners most often ask for fall straight out: speed in still water = (downstream + upstream) ÷ 2, and speed of stream = (downstream − upstream) ÷ 2.

If a boat goes 30 km downstream in 2 hours and 30 km upstream in 3 hours, downstream speed is 15 km/hr and upstream speed is 10 km/hr; hence the boat in still water does (15 + 10)/2 = 12.5 km/hr and the stream flows at (15 − 10)/2 = 2.5 km/hr. A classic harder variant asks for the average speed of a there-and-back river trip, which is once again the harmonic-mean situation of equal distances at unequal speeds, never the arithmetic mean of upstream and downstream speeds. The same up/down decomposition reappears for an aircraft in a tailwind versus a headwind — the medium changes, the algebra does not.

Circular Tracks and Races

On a circular track the relative-speed rules carry over, but "meeting" now has two flavours. Two runners starting together from the same point and running in the same direction meet again whenever the faster has gained one full lap on the slower; the time is the track length divided by the difference of speeds. Running in opposite directions, they meet whenever their combined distance equals one lap; the time is the track length divided by the sum of speeds. The number of distinct meeting points and the time to meet at the starting point again involve the ratio of the two speeds in lowest terms — pure ratio work.

Races introduce vocabulary worth fixing. "A gives B a start of 20 metres" means B begins 20 m ahead, so A must cover the full track while B covers 20 m less. "A beats B by 10 seconds" means A finishes 10 seconds earlier. "A beats B by 30 metres" means when A finishes, B is still 30 m short. A dead heat means both finish together. Translate each phrase into a precise statement about distances and times, and the race becomes an ordinary distance problem. The trap is treating a head start in distance as though it were a head start in time, or vice versa. A worked illustration fixes the idea: on a 400 m circular track, A runs at 8 m/s and B at 5 m/s in the same direction from the same point. A gains 3 m every second, so A laps B after 400/3 ≈ 133.3 seconds. Send them in opposite directions and they close 13 m every second, meeting after 400/13 ≈ 30.8 seconds. The number of distinct points at which they meet on the track is governed by the difference (same direction) or sum (opposite direction) of the speed ratio's reduced terms — here 8:5 gives 8 − 5 = 3 meeting points going the same way and 8 + 5 = 13 going opposite ways — another reminder that the topic rests on ratios.

Early and Late: The Two-Scenario Equation

A recurring question type gives a person who is late when travelling at one speed and early when travelling at another over the same fixed distance, and asks for that distance or the correct departure time. The reliable method is to write the same distance two ways and equate. Because distance is fixed, the difference in arrival times equals the difference in travel times at the two speeds.

Suppose a clerk walking at 5 km/hr reaches the registry 10 minutes late, but at 6 km/hr arrives 5 minutes early. The time gap between the two scenarios is 15 minutes, or 1/4 hour. If the distance is D, the times are D/5 and D/6 hours, and their difference is D/5 − D/6 = D/30. Setting D/30 = 1/4 gives D = 7.5 km. From there the scheduled time follows by plugging back in. This template — same distance, two speeds, a known difference in time — recurs so often that recognising it instantly is worth more than any single formula.

A second common variant fixes the distance and varies only the speed to produce a time saving or loss. If increasing speed from 40 km/hr to 50 km/hr saves a commuter 30 minutes on a fixed route, you can recover the distance from the time difference alone. The times are D/40 and D/50 hours; their difference is D/40 − D/50 = D(50 − 40)/2000 = D/200 hours. Setting D/200 = 1/2 gives D = 100 km. The same algebra answers "by how much must speed rise to arrive on time" questions: once the distance is known, the required time follows, and the required speed is distance divided by that time. Train yourself to treat the time difference as the bridge between two otherwise identical journeys.

When Speed Stops Being Arithmetic: Rash and Negligent Driving

For a law aspirant, the most valuable thing this topic offers is a bridge between computation and doctrine. In motor-accident prosecutions and compensation claims, courts are repeatedly asked to infer rashness or negligence from speed and stopping distance — and the Supreme Court has been emphatic that the arithmetic alone proves nothing. In State of Karnataka v. Satish, (1998) 8 SCC 493, the Court held that merely because a vehicle was being driven at "high speed" does not, by itself, establish negligence or rashness; "high speed" is a relative term, and it is for the prosecution to bring on record material showing what high speed meant in the circumstances of the road, traffic and conditions of that case.

That principle was reinforced in Mohd. Aynuddin alias Miyam v. State of Andhra Pradesh, (2000) 7 SCC 72, where the Court drew the line between a rash act (an over-hasty act, running the risk of a consequence with indifference to it) and a negligent act (a breach of the duty to take care), and observed that no presumption of negligence arises merely from the occurrence of an accident, though the doctrine of res ipsa loquitur can shift the evidential burden onto the person in control of the vehicle. The lesson for the quantitative mind is sharp: a speed figure is a premise, not a conclusion.

Stopping Distance, Following Distance and the Rules of the Road

The physics that underlies your arithmetic also underlies the regulatory standard of care. Stopping distance has two components — the reaction distance covered while the driver perceives the hazard and moves to the brake, and the braking distance once the brakes engage — and the second grows with the square of speed, which is precisely why doubling speed far more than doubles the danger. Indian law translates this into a positive duty through Regulation 23 of the Rules of the Road Regulations, 1989, framed under Section 118 of the Motor Vehicles Act, 1988, which requires a driver following another vehicle to keep a sufficient distance to stop safely if the vehicle in front slows or halts suddenly. The Supreme Court applied exactly this standard in Oriental Insurance Co. Ltd. v. Tata AIG General Insurance Co. Ltd., 2026 INSC 208, holding that failure to maintain the sufficient distance mandated by Regulation 23 amounts to negligent driving.

The same speed-and-distance reasoning resurfaced in Ravi Kapur v. State of Rajasthan, (2012) 9 SCC 284, where the Court explained that the standard of care is that of a reasonable and prudent driver and that res ipsa loquitur may apply where the manner of the accident itself bespeaks negligence. Reading these alongside the formulas in this chapter, you can see that the harmonic mean and the 5/18 conversion are not idle drills — they are the quantitative grammar of the very questions a trial court must answer about how an accident happened.

From Negligence to Culpable Homicide: The Pareira Line

Where speed combines with knowledge of a likely fatal consequence, the offence can climb beyond rash driving into culpable homicide not amounting to murder. In Alister Anthony Pareira v. State of Maharashtra, (2012) 2 SCC 648, the accused drove a car at very high speed and in a drunken condition onto a pavement where labourers were sleeping, killing seven and injuring eight. The Supreme Court upheld conviction under Section 304 Part II of the Penal Code, reasoning that a person who drives rashly with knowledge of the dangerous character and likely effect of the act, resulting in death, may be held guilty not merely of the act but of its result. Speed here was not the offence; it was evidence of the knowledge and indifference that elevated the offence.

This progression — from a bare speed figure that proves nothing (Satish), to a regulatory following-distance duty (Oriental Insurance), to speed as proof of culpable knowledge (Pareira) — is exactly the kind of doctrinal ladder examiners reward you for seeing. It also explains why aptitude and law are not siblings kept in separate rooms on this site: the numerical skill of computing distance covered before braking is the same skill a judge deploys when testing whether a stopping distance was physically achievable.

Exam Strategy and Common Traps

A disciplined order of operations clears most questions quickly. First, fix the units — convert every speed to a single system (usually m/s for trains, km/hr otherwise) before doing anything else. Second, identify the structure: is it single-body, relative-speed, average-speed, a stream, a circular track, or an early/late two-scenario problem? Third, decide what is the distance — for trains, remember to add lengths; for pursuits, the head start is the distance. Only then compute.

The traps are predictable. The average-speed question almost always tempts the arithmetic mean when the harmonic mean is correct. Relative-speed questions punish adding when you should subtract and vice versa — re-read the direction of travel. Train questions catch candidates who forget the train's own length when crossing a platform, or who mix km/hr and m/s. Boat questions invite you to average upstream and downstream speeds directly when the trip is equal-distance and demands the harmonic mean. Race questions blur a head start in distance with a head start in time. Practise until structure recognition is instant, the way a strong candidate instantly classifies a sum as time and work or ratio and proportion; speed of recognition, not cleverness of method, is what the clock rewards.

A Worked Set to Tie It Together

Consider a consolidated problem of the kind a preliminary paper might pose. A train 150 m long passes a platform 350 m long in 20 seconds. How fast is it, in km/hr, and how long would it take the same train to overtake a 250 m goods train running on a parallel track in the same direction at 36 km/hr?

The total distance to cross the platform is 150 + 350 = 500 m in 20 seconds, so the train's speed is 500/20 = 25 m/s, which in km/hr is 25 × 18/5 = 90 km/hr. For the overtake, both speeds must be in the same unit: the goods train at 36 km/hr is 36 × 5/18 = 10 m/s, and the passenger train is 25 m/s. Same direction means relative speed is the difference, 25 − 10 = 15 m/s. The distance to cover when overtaking is the sum of the lengths, 150 + 250 = 400 m. Time = 400 ÷ 15 = 26.67 seconds, or 80/3 seconds. Notice every tool from this chapter in one sum: length-aware distance, the 5/18 conversion, and same-direction relative speed. That integration — not any single formula — is what consistent scorers carry into the hall. Build the rest of your quantitative base from the aptitude and reasoning hub.

Frequently asked questions

What is the single most important formula for Time, Distance and Speed problems?

Everything flows from Distance = Speed × Time. Rearranged, Speed = Distance/Time and Time = Distance/Speed. The proportionality corollaries matter just as much: at constant speed, distance is proportional to time; over a fixed distance, speed is inversely proportional to time.

Why is average speed not the simple average of two speeds?

Average speed is total distance divided by total time, never the arithmetic mean of the speeds. For two equal-distance legs at speeds x and y, the correct figure is the harmonic mean 2xy/(x+y), because the body spends more time at the slower speed, so that leg must weigh more. The arithmetic mean (x+y)/2 is correct only when the two legs take equal time.

How do I convert km/hr to m/s quickly?

Multiply km/hr by 5/18 to get m/s, and multiply m/s by 18/5 to go back. For example, 72 km/hr = 72 × 5/18 = 20 m/s, and 25 m/s = 25 × 18/5 = 90 km/hr. Always convert to a single unit before computing, especially in train problems.

When a train crosses a platform, what distance does it cover?

The distance equals the length of the train plus the length of the platform, because the train must travel from the first instant its front meets the platform to the last instant its rear leaves. Crossing a pole or a stationary person, the distance is only the train's own length, since those are point objects with negligible length.

Does high speed by itself prove rash or negligent driving in Indian law?

No. In State of Karnataka v. Satish, (1998) 8 SCC 493, the Supreme Court held that high speed alone does not establish rashness or negligence; "high speed" is relative and must be proved with material showing what it meant in the circumstances. Mohd. Aynuddin v. State of A.P., (2000) 7 SCC 72, added that no presumption of negligence arises merely because an accident occurred, though res ipsa loquitur may shift the evidential burden.

Is there a legal duty about following distance, and how does it link to stopping distance?

Yes. Regulation 23 of the Rules of the Road Regulations, 1989, framed under Section 118 of the Motor Vehicles Act, 1988, requires a following driver to keep sufficient distance to stop safely if the vehicle ahead slows or halts. Because braking distance grows with the square of speed, that buffer must widen sharply at higher speeds. In Oriental Insurance Co. Ltd. v. Tata AIG General Insurance Co. Ltd., 2026 INSC 208, the Supreme Court treated breach of Regulation 23 as negligent driving.