Contact Patch · how a car actually handles

Everything your car does happens on four patches of rubber the size of your hand.

Front-wheel drive or rear? Is 50:50 weight distribution real engineering or a marketing number? Is mid-engine actually better, and better at what? I built a car out of a measured tire file (a real one, from a test rig), pointed a minimum-time solver at it, and asked. Most of the famous answers came back smaller than the arguments about them. Then I replaced the perfect driver with one that could be surprised, and the numbers moved. Everything below runs live in your browser, on the same tire the results use.

scroll
This page's tire model failed its check against the Python it was ported from. The curves below may be wrong. Treat them as broken until this message goes away.
Start with one tire

A tire makes its biggest grip while it is already sliding.

The intuitive model is that a tire holds on until it doesn't, treating grip as a threshold you cross. That model is wrong in the direction that makes fast driving impossible to explain.

To make sideways force, a wheel has to point slightly away from where it is actually traveling. That angle is called slip angle, and the rubber in the contact patch bends as it passes through. Bent rubber pushes back. Slip is the mechanism by which grip exists.

Drag the slider. One tire, one load, nothing changing but the angle.

one tire · 3,600 N on it, about one front corner at restlive
sideways force — of its maximum —

Grip has a top, and the top is flat. By 5° the tire is already making about 91% of everything it will ever make; the last 9% costs another 5° of slip. That flatness is what makes driving at the limit hard. Near the peak, the feedback telling you where you are goes quiet. If you have pushed a car on a wet road and felt more steering stop producing more turning, no drama, only diminishing returns, you have felt the top of this curve.

Push past it and force falls, but gradually. Nothing lets go all at once, and you can be past the peak while still making most of your grip.

Why cornering costs you

Press a tire twice as hard and you do not get twice the grip.

This is the one property of rubber that the rest of chassis engineering is bookkeeping on top of. Load a tire more heavily and it grips harder in absolute terms, but less per newton pressing it down.

This matters because a car corners by moving weight. Lean on the outside wheels and the pair carries the same total as before, shared unevenly. Drag the split and watch what the pair can do.

two tires · 6,000 N between them, total never changeseven
inner 3000 N outer 3000 N pair can make — lost 0.0%
Even sharing always wins. The tire you press harder gains less than the tire you unload gives up, because the loaded one is now further down that falling curve. The penalty grows with the square of the transfer, so the first 500 N is nearly nothing and the last 500 N is most of the bill.

Here is the connection that makes this more than arithmetic. Cornering moves a car's weight onto the outside wheels and off the inside. Braking moves it forward. Accelerating moves it back. Every one of those is the slider you just dragged, happening to a real car in real time.

So a car has less total grip while it is doing something than it has sitting still. Nothing wore out. The weight got shared unevenly, and unevenly shared weight makes less grip. That single fact is why cars built to corner are low and wide, and why anti-roll bars exist at all.

One budget

Turning and stopping come out of the same account.

A tire does not get a separate allowance for cornering and for braking. It has one, and every newton spent one way is unavailable the other. Drawn as a shape, the limit comes out roughly elliptical, which is where the name friction ellipse comes from.

Drag the arrow. It can point anywhere; what it cannot do is leave the ring.

the force budget · drag itat the limit
braking 0% cornering 100%
Spend 70% of the budget braking and about 71% is left to corner with. That is why "brake, then turn" is a statement about an account. It is also why trail braking works. Carry the brakes past turn-in and the weight moving forward buys the front tires grip exactly when you are asking them to bite.
Now a whole car

Watch the four tires through one corner.

Four wheels take a 90° left-hander of 40 m radius, about 63 m of curve, with 70 m of approach before it and 260 m of straight after. A minimum-time solver drives the car. It gets the tire model, the width of the road and a stopwatch, and is not told what a racing line is.

Here is the road from above, and the line it chose. The dashed line is the middle of the road, the obvious way round. The solid one is what came back.

—
jump to

Nobody told it to do that. It runs to the far edge before the corner even starts, steering away from a left-hander in order to take it. Widening the corner is worth more than the distance it costs, and the solver found that on its own.

Watch the arrows rather than the car, and step through in order. For the first 25 m it is still accelerating (the arrows point forward) while already steering away from the corner. Then it brakes hard, 11,000 N at the 32 m mark, and the weight piles onto the front tires, which go from carrying 48% of the car to 70%. Through the corner the arrows swing sideways, and the outside two grow while the inside two shrink to almost nothing. The car is leaning on two tires. Past the apex they rotate forward again.

The view stops just past the corner exit; the road runs straight for another 230 m beyond it.

Now the same corner as a diagram, so the numbers are readable. Each wheel shows what it is carrying (the ring, which grows and shrinks as load moves) and what it is spending (the arrow, and how close it comes to the edge).

—
jump to

Through the corner the two cars are indistinguishable. Both are cornering as hard as the tires allow, so both solve the same problem and find the same answer. They pick the same line to within the width of your hand.

Past the exit they differ. The rear-drive car's front wheels go quiet: the corner is done and they are only steering, which costs almost nothing. Its rear wheels do the accelerating.

The front-drive car's front wheels never get to rest. Eighty meters down a straight road, with no cornering left to do, they are still spending well over half of what they have, on acceleration alone. If you drive front-wheel drive you have felt this at every wet junction. Turn and accelerate together and the wheel goes light and tugs at your hands. Ask for the two jobs one at a time and it does both cleanly.

The argument everyone has

Which wheels should drive?

Hold everything else identical (same mass, same weight distribution, same tires, same corner) and change only which axle gets the torque. Real front- and rear-drive cars differ in almost everything, so this is a comparison you cannot run in a parking lot.

The car being modeled makes about 180 hp, a normal sports coupe. At that power the two layouts finish within three hundredths of a second of each other, too close to feel. The interesting part is what moves it, so I solved the same corner again at four engine outputs. Pick one.

same car, same corner · only the driven axle changesfour measured solves

"Rear-wheel drive is faster" is true only at a given power level, and the condition is doing most of the work. With little power the corner exit is limited by the engine, not by grip, so a tire-budget problem has nothing to bite on. Pile on power and the front tires saturate earlier and earlier.

You can check that without any of this. Economy hatchbacks are front-wheel drive and nobody objects, while almost every car built to be fast is rear- or all-wheel drive. That split is usually explained by cost and packaging, and those explanations are true, but the friction budget alone reproduces it, from a tire data file and a stopwatch.

50:50

Weight distribution changes the car far more than it changes the lap time.

Slide the mass along the wheelbase, change nothing else, and measure two things: how the car behaves, and how fast it goes.

The behavior number is the understeer gradient, how much extra steering the car needs as you push harder. Negative means the back gives up first and the car rotates. Positive means the front gives up first and it pushes wide.

slide the mass · everything else held fixed54% front

Across the sweep the car goes from clear oversteer to clear understeer, a swing of about 1.05 deg/g, which is five times the difference a professional test team can reliably tell apart. The lap time moves by around two tenths.

So 50:50 is mostly a marketing number, though not for the reason I expected. Each drivetrain does want its own end of the range (whichever end carries the weight is the end that should drive it), but getting it right is worth a tenth of a second, while the swing in how the car behaves runs from clear oversteer to clear understeer. You are mostly choosing the car's character, and the lap time barely moves.

You have driven a slice of this without meaning to. A full trunk and two rear passengers move you down this table.

Front, mid or rear engine

"Mid-engine is better" is a claim about the wrong number.

Two properties get muddled because you cannot move an engine without changing both. Weight distribution is where along the car the mass sits. Polar moment is how far from the middle it sits, how hard the car is to start and stop rotating.

You can feel the second one in your hands. Swish a broom holding it by the middle, then hold it near the brush and swing the same swing. Same mass, but with the weight far from your grip the broom is slower to start turning and slower to stop.

five layouts on two axes · click onemid engine

Look where the front-engined sedan and the rear-engined 911 land: opposite ends of the balance axis, the same height on the inertia one. Now look at the mid-engine car. At 43% front it is less rearward than the 911. If balance were the story, the 911 would be the extreme one and the mid-engine car unremarkable.

What separates it is the lowest polar moment of the five, mass gathered near the middle. That is the whole difference, and it is argued as a weight-distribution claim because moving an engine changes both at once.

The lap times land inside four hundredths of a second for four of the five. That points at what is wrong with the question.

What was wrong with the question

The driver knew the future.

Everything above was driven by a solver that sees the whole road before it turns the wheel. It knows exactly when the corner arrives, so for a car that takes 356 ms to respond instead of 201 ms, it starts steering earlier. The delay costs almost nothing, because the delay is perfectly predictable.

A real driver reacts to what has already happened. For them, 155 ms is 155 ms of the car not doing what they just asked, arriving exactly when they are trying to correct something. Response time is nearly free if you know the future and expensive if you don't, which is why every "which layout is faster" answer above came back smaller than expected. We were asking about driveability using a driver for whom driveability does not exist.

So the numbers above are a floor. A design difference a perfect driver can plan around is one a real driver has to survive, and surviving is a different measurement.

Here are the same five cars, driven by a learner that reacts instead of planning, over a road whose grip is not quite what it expected. Every lap it drove is drawn.

weight on front

With no disturbance every drivable car traces one line. Turn the grip variation on and they fan out, and the quickest of them starts running out of road while the others do not. That is what "the fast setup is the one that bites" comes down to. It is about what happens when you go over the edge. Lose front grip and the car pushes wide, which scrubs speed, which gives the grip back. Lose rear grip and it rotates, which points the tires further from where they need to be, which rotates it more.

Note the 40% car, which fails with nothing going wrong. This driver cannot drive it, which is a different problem with a different fix.

And then software gets involved

A computer can decide which wheel pays.

First, the part your car already has. When you turn, the outside wheel travels further than the inside one, so something has to let the two driven wheels spin at different speeds or the tires would scrub. That something is the differential (a lump of gears between them), and every interesting thing it does comes from one rule: torque flows from the faster-turning wheel to the slower one.

That rule is fixed, the same in every corner. It is why a car with a heavily locked differential binds and pushes wide in a parking lot, and why a cheap hatchback can spin one unloaded wheel uselessly in the air while the other does nothing.

Torque vectoring replaces the rule with a decision. Push harder on the wheels down one side and the car rotates, a genuine steering input that has nothing to do with the steering wheel. So measure how the car is turning, compare it to how the driver asked it to turn, and push harder on whichever wheels close the gap. It works in two layers: one decides how much rotation you want, the other decides which wheels pay for it. Put a motor or a brake at each corner and it can meter all four separately, where the gears could only meter one axle.

Here is what that does to the layouts from two sections ago: same driver, same corner, same demand, with the differential swapped for the controller.

same corner, same demand · which wheel is being pushed, and how hard—
—
jump to

Step through it. The differential is left-right identical at every instant, which is what one fixed rule looks like. The controller is not. At turn-in it brakes the inside wheels and drives the outside ones, which twists the car into the corner. As the steering unwinds it reverses, taking rotation away. Down the straight it stops intervening and the two look the same again.

It is also redistributing under braking. Both cars are slowing at the same rate, but the controller puts more of that through the wheels that have the load to take it.

So what is it worth? It is not "the car stayed on the road," since you could always ask for less. The honest measure is the most cornering each layout can survive, found by turning the demand up until it fails.

With an open differential, four of the five archetypes leave the road at a demand the fifth one meets easily. With the controller on, all five stay on it. Nothing else changed.

Measured as spread in cornering limit across the five layouts, the controller flattens the difference between them by 16× at 181 hp and 47× at twice that. This controller makes where the engine sits, the thing that made a 911 a 911, close to irrelevant to whether the car holds its line.

There is one exception, a mechanism rather than a gap. The front-driven car doesn't flatten. Its limit is a front-tire slip-angle ceiling, and a controller built to move torque around has nothing to move when torque was never what was failing.

This is a model. It has four wheels, load transfer, and a real measured tire, but no roll camber, roll steer, or compliance steer, which together are most of a real car's understeer. This car produces about 5% of a real one's understeer gradient. Read the orderings and the directions; the magnitudes are illustrative.
One corner, one car, one tire file. A 90° left-hander of 40 m radius, with a long straight after it. A hairpin or a sweeper stresses different budgets and can reorder things.
The tire is bigger than the car wears, and the shape of the braking-versus-cornering trade is an assumption standing in for coefficients this tire file doesn't carry. That a tire trades one for the other is certain; that it trades along an ellipse exactly is our choice.
The numbers on this page are exported from the experiments' own artifacts, and the tire curve is recomputed live from the same coefficients with a known-answer check against the Python. An audit of this series found ten of fifteen write-ups had drifted from their own data at least once; this page is built so it can't.

Most of it is one fact about rubber.

Grip falls as load rises. Everything above (why cornering costs you, why the driven axle should carry the weight, why a diagonal arrow runs out first, why a computer metering four wheels beats gears metering one) is that fact with different bookkeeping on top. The rest is knowing which question you asked.

Contact Patch · Orbitope