Lesson 12: Speed, Distance, Time

Speed, distance, and time form Singapore's most travelled mathematical triangle — every MRT journey, every school run, every delivery rider's route is a calculation in these three quantities. The relationship (distance = speed × time) is simple; the unit conversions and multi-stage journeys are where examinations bite. This lesson builds fluency with the formula triangle, average speed, and the distinctive Singaporean art of the journey problem.

The Formula Triangle

Three quantities, one relationship: distance = speed × time. The formula triangle organizes all three forms: cover "distance" and read speed × time; cover "speed" and read distance ÷ time; cover "time" and read distance ÷ speed. Singaporean pupils draw this triangle until it is reflex — because every journey problem is one of these three questions.

Units must be consistent: speed in km/h pairs with distance in km and time in hours; speed in m/s pairs with metres and seconds. Mixing units is the number-one error: computing with distance in km and time in minutes without converting. The discipline — convert first, compute second — is worth more than the formula.

Conversions: 1 km/h = 1000 m / 3600 s = 5/18 m/s (approximately 0.278 m/s). So 72 km/h = 72 × 5/18 = 20 m/s — a conversion worth memorizing. And 1 m/s = 3.6 km/h. The MRT's top speed (~90 km/h = 25 m/s) becomes tangible in either unit.

Straightforward Journeys

Problem: "The MRT travels from Jurong East to Bukit Batok (4 km) in 6 minutes. What is its average speed?" Convert 6 minutes to 0.1 hours (6/60). Speed = 4 ÷ 0.1 = 40 km/h. Or in m/s: 4000 m ÷ 360 s = 11.1 m/s. Both are correct; the units answer different curiosities.

Problem: "A delivery rider cycles at 18 km/h. How long to cover 27 km?" Time = 27 ÷ 18 = 1.5 hours = 1 hour 30 minutes. The decimal-to-minutes conversion (0.5 h = 30 min) trips students — always translate the decimal remainder into minutes explicitly.

Estimation guards: Singapore to Kuala Lumpur is ~350 km; at 90 km/h that is about 4 hours (350 ÷ 90 ≈ 3.9). If a computation says 40 hours or 0.4 hours, the estimate exposes it. Journey problems should always begin with "roughly how long?"

Average Speed — The Harmonic Trap

Average speed is total distance divided by total time — not the average of speeds. The classic trap: "A car goes from A to B at 60 km/h and returns at 40 km/h. What is the average speed for the whole trip?" The naive answer, 50 km/h, is wrong. Suppose the distance is 120 km each way: time out = 2 h, time back = 3 h, total 240 km in 5 h = 48 km/h.

The bar-model or timeline picture shows why: more time is spent at the slower speed, so the average weights toward 40. The general formula for equal distances is the harmonic mean: 2 ÷ (1/60 + 1/40) = 48. But Singaporean pupils need not memorize this — the "assume a convenient distance" method (pick 120 km, or any common multiple) solves every such problem.

This is a favourite PSLE/O-level discriminator because it punishes formula-plugging and rewards understanding. The pupil who draws the journey timeline sees the unequal times; the pupil who averages 60 and 40 does not.

Multi-Stage Journeys

Real journeys have stages: "Mei walks to the MRT (10 min), rides 25 min, then walks 5 min to school. The walk covers 800 m total and the ride 12 km. What is her average speed for the whole journey?" Total distance = 12.8 km; total time = 40 min = 2/3 h; average speed = 12.8 ÷ (2/3) = 19.2 km/h. The stages collapse into one total — average speed erases the details.

Meeting problems: "Two friends cycle toward each other from towns 30 km apart, at 12 km/h and 18 km/h. When do they meet?" Their closing speed is 12 + 18 = 30 km/h; time = 30 ÷ 30 = 1 hour. The timeline picture — two bars growing toward each other — makes "closing speed" intuitive.

Overtaking problems: "A bus leaves at 60 km/h; 30 minutes later a car follows at 90 km/h. When does the car catch the bus?" The bus's head start: 60 × 0.5 = 30 km. Closing speed: 90 − 60 = 30 km/h. Catch-up time: 30 ÷ 30 = 1 hour after the car leaves. Relative speed is the master idea — and the timeline bars show it.

Speed in Science and Daily Life

Speeds span scales: a pedestrian ~5 km/h, the MRT ~40 km/h average (90 max), an airliner ~900 km/h, light 1,080,000,000 km/h. Singapore's speed limit (50 km/h on roads) is a social choice encoded in a number; the 10 km/h school-zone limit near schools is mathematics protecting children.

Science extends the idea: current speed (m/s of electrons), sound speed (343 m/s — why thunder lags lightning), and the speed of data (fibre broadband in Gbps). The distance-speed-time relationship is physics' first formula and mathematics' most applied division.

The Grab driver's app, the MRT arrival display ("3 mins"), the food-delivery ETA — all are live speed-distance-time computations. Fluency here is not exam preparation but citizenship in a city that runs on schedules.

Conclusion — Why This Matters

Speed problems teach proportional reasoning in motion: doubling speed halves time, tripling distance triples time at constant speed. These are direct and inverse proportions (Lesson 4) wearing a traveller's clothes.

The examination skills — consistent units, the formula triangle, average speed as total-over-total, relative speed for meetings and chases — are a complete toolkit. Draw the timeline, label the stages, and the journey problems solve themselves.

Beyond exams, this is the mathematics of punctuality, planning, and logistics — the quiet arithmetic beneath Singapore's reputation for efficiency.

Journey Graphs — Reading Singapore's Commute

The MRT system map is a graph in the everyday sense — but journey mathematics uses graphs in the technical sense: distance-time plots. Sketch a commute: flat line (waiting at Jurong East), steep rise (express segment), gentle rise (all-stops segment), flat (interchange wait), steep rise again. The picture tells the journey's story more vividly than any timetable.

MyTransport.SG and the LTA's data portals publish real journey statistics: average speeds per line, peak-hour loads, headways. A pupil can compute: the North-South Line is 45 km; end-to-end scheduled time ~70 minutes; average speed ≈ 38.6 km/h — far below the 90 km/h top speed, because stops dominate. Real data makes the formula triangle concrete.

Traffic engineers use the same mathematics at scale: the ERP (Electronic Road Pricing) system models traffic flow as speed-density relationships, raising prices to keep speeds above 45 km/h on expressways. The "fundamental diagram of traffic flow" — speed vs. density — is a graph every Singaporean driver experiences financially.

Project idea: time your own school journey in segments, plot the distance-time graph, compute each segment's speed, and identify where time is lost. You will have done transport engineering — and understood why the MRT engineers obsess over dwell times.

Debate — Is Average Speed Too Tricky for Primary School?

The harmonic-mean trap (Lesson 12's 60/40 round trip averaging 48, not 50) is many pupils' first encounter with a plausible-but-wrong answer. Critics argue it is developmentally inappropriate: it punishes intuition, rewards a formula pupils cannot derive, and sorts by trickery rather than understanding. Save it for secondary school.

Defenders call it the perfect primary problem: it is solvable by concrete methods (assume 120 km, compute times, divide totals) without any formula, and it teaches the priceless lesson that intuition needs checking. The pupil who has been burned by 50-vs-48 never again averages rates blindly — a lifelong immunity.

Singapore's syllabus sides with the defenders but scaffolds carefully: average speed appears first as total÷total in simple journeys, and the trap version only after pupils are fluent. Difficulty is not the enemy — unprepared difficulty is. Sequence it right, and the "trick" becomes a triumph.

Worked Example — The Assumed-Distance Heuristic

Problem: "A delivery van travels from Singapore to Malacca at an average speed of 80 km/h and returns at 60 km/h. Find its average speed for the whole journey." The naive average, (80 + 60) ÷ 2 = 70 km/h, is wrong — the van spends longer at the slower speed. Heuristic — assume a convenient distance: choose 240 km (a common multiple of 80 and 60). Time out = 240 ÷ 80 = 3 h; time back = 240 ÷ 60 = 4 h. Average speed = total distance ÷ total time = 480 ÷ 7 ≈ 68.6 km/h. Formula route: for equal distances, average speed = 2 ÷ (1/80 + 1/60) = 480/7 ≈ 68.6 km/h — the same answer, but the formula is opaque until the assumed-distance method has shown *why* it works.

The assumed number is a heuristic, not a trick: any distance gives the same average, so pick one that makes the arithmetic kind.

Common Mistakes

• Averaging the speeds. Average speed is total distance ÷ total time — never the mean of two speeds unless the *times* are equal.
• Mixing units mid-calculation. Kilometres with minutes, metres with hours: convert everything first (6 minutes = 0.1 h), then compute.
• Leaving 1.5 hours as "1 hour 50 minutes". 0.5 h = 30 minutes. Convert the decimal part by multiplying by 60, every time.

Exam Experience

Question 1 [2 marks]. A car travels 156 km in 2 hours 24 minutes. Calculate its average speed in kilometres per hour.

Question 2 [3 marks]. (a) Express 90 km/h in metres per second. (b) A train travels at this speed for 45 seconds. How far does it travel?

Question 3 [6 marks]. A train leaves Town A at 09 15 and travels at 72 km/h towards Town B. A car leaves Town A at 09 45 and travels at 96 km/h in the same direction. (a) How far has the train travelled by 09 45? (b) At what time does the car catch up with the train?

Marking scheme. Q1: M1 for converting 2 h 24 min to 2.4 h; A1 for 156 ÷ 2.4 = 65 km/h. Q2: (a) M1 for 90 × 5/18 (or 90,000 ÷ 3,600); A1 for 25 m/s. (b) B1 for 25 × 45 = 1,125 m (allow follow-through from (a)). Q3: (a) M1 for 72 × 0.5; A1 for 36 km. (b) M1 for closing speed 96 − 72 = 24 km/h; M1 for time = 36 ÷ 24 = 1.5 h; A1 for 1.5 h; A1 for 11 15.