Predict when your brake pads will die: a 20-line Python estimator for Dubai traffic

#python #beginners #productivity #diy

Most people find out their brake pads are finished the same way: a metal-on-metal squeal at a red light on Sheikh Zayed Road. By then the pad is gone and the disc is often scored too, so a routine job turns into pads plus discs.

You can see it coming months ahead with two measurements and about 20 lines of Python. This is the small estimator I'd give any developer who drives in Dubai, plus the brake facts you need to read the numbers properly.

Why Dubai eats brake pads

Pad life is quoted all over the place (30,000 to 70,000 km is a common range), but city driving here sits at the short end for a few reasons:

Stop-start traffic. A 25 km commute at peak hour can mean dozens of hard stops from 80 km/h down to zero. Every stop turns speed into heat in the pad.
Heat soak. On a 45°C afternoon the brakes start hot before you touch them, and they shed heat more slowly.
Fine sand. Dust gets between pad and disc and works like a mild abrasive.
Front bias. The front axle does most of the braking work (often quoted at around 70%), so the front pads almost always go first.

So the brochure number won't help you much. Your own wear rate will.

What to measure

You need two readings of the front pad friction material (not the steel backing plate), taken at least 5,000 km apart, with the odometer reading each time.

A new pad usually has about 10 to 12 mm of friction material.
Most workshops replace at about 3 mm. Many pads have a small metal wear tab that starts squealing at roughly that point.
Under 2 mm you're close to the backing plate grinding the disc.

You can often see the outer pad through the wheel spokes with a torch, and a cheap pad thickness gauge makes it repeatable. The easiest option is to ask whoever services the car to write the pad thickness on the job card every time. Most will do it if you ask.

The estimator

from dataclasses import dataclass

@dataclass
class Reading:
    odometer_km: int
    pad_mm: float

def estimate(first: Reading, second: Reading,
             replace_at_mm: float = 3.0,
             km_per_month: float = 1800) -> dict:
    km = second.odometer_km - first.odometer_km
    worn = first.pad_mm - second.pad_mm
    if km <= 0 or worn <= 0:
        raise ValueError("need two readings, later one thinner")
    rate = worn / km * 1000            # mm per 1,000 km
    left_mm = second.pad_mm - replace_at_mm
    left_km = max(left_mm, 0) / rate * 1000
    return {
        "wear_mm_per_1000km": round(rate, 3),
        "km_until_replace": round(left_km, -2),
        "months_until_replace": round(left_km / km_per_month, 1),
    }

print(estimate(Reading(42_000, 8.0), Reading(52_000, 6.2)))

With those sample numbers:

1.8 mm worn over 10,000 km gives a rate of 0.18 mm per 1,000 km
6.2 mm now minus the 3 mm limit leaves 3.2 mm, which is about 17,800 km
At 1,800 km a month (a fairly normal Dubai commute plus weekends), that's about 10 months

Put the date in your calendar a month earlier and you'll never hear the squeal. If you want to go further, keep one reading per service in a CSV and fit a line through all of them instead of using two points. Wear isn't perfectly linear (summer and a new commute route both change it), so more points give a better slope.

Things the script can't tell you

Thickness is only one signal. These ones mean "get it looked at now", whatever the numbers say:

Grinding or scraping. That's usually the backing plate on the disc. Stop driving on it.
Pulsing through the pedal under braking. Typically uneven disc thickness or pad deposits on the disc. Pads alone often won't fix it.
Pedal feels soft or sinks. Could be air or old fluid. Brake fluid absorbs water over time, and that lowers its boiling point: DOT 4 fluid has a minimum dry boiling point of 230°C but only 155°C once it has absorbed moisture (the Wikipedia page on brake fluid has the full table). In Dubai heat, with repeated hard stops, that gap matters. Most makers say to change it every two years.
Car pulls to one side when braking. A sticking caliper or uneven pad wear on one side.
One pad much thinner than the other on the same axle. Same story, usually a caliper slide pin that needs cleaning and greasing.

One more that people mix up: if the car drifts to one side when you're not braking, that's rarely the brakes. It's more often tyre pressure or alignment, and a wheel alignment check after a hard pothole or kerb hit is the cheaper first step.

When it's time

When the estimate says you're a month or two from 3 mm, book the job and ask three questions:

What's the pad thickness on each side, front and rear?
What's the disc thickness compared with the minimum stamped on the disc (usually marked "MIN TH")?
When was the brake fluid last changed?

If the discs are still above minimum and not scored, you only need pads. If you're in Dubai and want a garage to measure everything and tell you straight, BRITFIX's brake pad replacement page lists what they check. They're in Al Quoz Industrial Area 4 and open Monday to Saturday.

Takeaway

Two thickness readings, the odometer at each one, and a ten-line wear-rate calculation turn brake pads from a surprise into a calendar entry. In Dubai traffic, measure the fronts at every service, and change the brake fluid every two years. The heat makes old fluid a real problem.

DEV Community