Measuring aero on track: coast-down, constant-velocity & logged-data estimates
Drag from coast-downs, downforce and balance from constant-speed runs with suspension loads, and both from normal laps with the right corrections. Includes a fully worked GT3 straight-line test.
Measuring aero on track: coast-down, constant-velocity & logged-data estimates: L1 Foundation explanation
Wind tunnels and CFD give the aero map, but the engineer needs to know what the car actually does on track, and to check whether a new part works. Two classic straight-line tests do this with the normal data system (Segers §13.6–13.8):
Coast-down test → drag. Accelerate to high speed on a straight, select neutral, coast with the steering still. With no engine force, Newton's second law says the deceleration is caused by the resistive forces:
(rolling resistance + driveline friction) is measured separately by a low-speed coast-down where drag is small (but not zero: correct for it, or fit over the whole speed curve). Then .
Constant-velocity test → downforce. Hold a steady speed so there is no longitudinal acceleration. The suspension compresses under the downforce; from the spring deflections (or pushrod load cells) and the known spring rates you get the extra load on each axle. A low-speed run (50–60 km/h) gives the reference. It is a low- reference, not a zero-downforce one: it still carries of the downforce (9 % for 60 vs 200 km/h), so divide the measured load increment by . Then and the aero balance is .
Rules for usable results:
- Run in both directions and average — this cancels wind and track gradient to first order.
- Log the weather (density!) and keep tyre pressures, fuel and temperatures consistent.
- Start coast-downs as fast as possible: drag grows with while rolling resistance is nearly constant, so the signal-to-noise ratio is best at high speed.
- Keep the car straight: steering and yaw add tyre drag.
Typical result quality: good teams get repeatability of ~1–2 % and of ~2–4 % — enough to see a two-click wing change, not enough to see a small bodywork detail. That is why these tests are usually done on airstrips or long straights with many repeats.
Misconception: "a faster speed trap proves less drag." Trap speed depends on engine power, gear ratios, exit speed of the previous corner, wind and density. Use a coast-down or a calculated drag channel instead.
Measuring aero on track: coast-down, constant-velocity & logged-data estimates: L2 Practitioner explanation
Worked example — GT3 straight-line test. Weather: 18 °C, 1009 hPa, 60 % RH → Pa, Pa, kg/m³. Car mass with driver and fuel 1310 kg; rotating inertia (wheels, brakes, gearbox output) adds ~3 %: kg.
Step 1 – rolling resistance. Coasting in neutral from 60 to 20 km/h, mean deceleration 0.028 g: total resistance N. Drag is not negligible here: with a roughly linear speed decay the mean is m²/s², so Pa and drag ≈ 80 N for . Hence N. At high speed the tyres carry ~3500 N of extra aero load; with a rolling-resistance coefficient ~0.015 add ~50 N. (Better still: fit to both coasts together, see L4.)
Step 2 – coast-down. Speed falls from 211.8 to 199.2 km/h in 2.0 s: m/s². Total resistance N. Drag N. Mean speed 205.5 km/h = 57.1 m/s → Pa. m².
Error check: using the static mass in both steps gives ~1.00 (−3 %); treating the 60→20 km/h coast as drag-free overstates by 80 N and costs another ~4 %; a 0.3 % downhill grade (0.029 m/s²) would bias by ~2 % — hence the two directions.
Step 3 – constant velocity at 200 km/h (zeroed at 60 km/h). Front springs 300 N/mm, motion ratio (spring/wheel) 0.60; rear springs 220 N/mm, MR 0.80. Average spring compression: front 3.5 mm, rear 5.0 mm. Wheel force per corner :
- Front: N per wheel → N
- Rear: N per wheel → N
- Zeroed at 60 km/h, these deflections measure , so divide by Pa → m², AB ≈ 41.7 %. Dividing by alone would understate by (1.63 m²); the balance is unaffected to first order because both axles scale alike.
Run the opposite direction and average. If run 1 gives and run 2 gives 1.65, the car had a headwind on run 1; the average 1.79 is the estimate, and the wind can be back-calculated from the difference between the runs (Segers §13.8).
Setup for the tests (constant velocity): soft springs (more deflection = better resolution), no packers or bump rubbers in contact, ARBs disconnected or at least not loaded, static heights chosen so that the target dynamic heights are reached at the test speed. Record dynamic ride heights with every point — the result is a point on the aero map, not "the" .
Calibrations to check before the day: potentiometer zeros (a 0.3 mm zero error at the front is ~110 N per axle in this example — about 9 % of the measured front load increment), spring rates measured on a spring tester, load-cell calibration, ride-height laser offsets.
Measuring aero on track: coast-down, constant-velocity & logged-data estimates: L3 Advanced explanation
Drag from normal laps (full-throttle acceleration). Without a dedicated test, use every full-throttle straight:
(Segers Eq. 13.17 form). Error budget: at 250 km/h a GT3 drive force is ~5000 N while drag is ~3000 N. A 4 % engine-torque error (torque map vs. actual, BoP restrictor, ambient) is 200 N → ~7 % drag error. A 1 % error in or gear ratio does the same. So logged-lap drag estimates are good for trends within a session (same engine, same day) but poor for absolute values. The coast-down avoids the torque term entirely, which is why it's preferred.
Downforce from damper/pushrod data on laps. For straight-line points with g:
with under acceleration. Acceleration transfers load rearward and unloads the front springs, so the transfer is added back at the front and removed at the rear (Segers Eq. 13.18–13.19). , are the fractions of the transfer carried by the suspension links through anti-geometry (anti-squat at the driven rear on power, anti-dive/anti-lift under braking). That part never shows in the springs. Use if unknown (it is zero at an undriven front on power), and check the signs on a braking zone where aero is small. Example: GT3 at g, 1380 kg, m, WB 2.7 m → 139 N per axle; with the wrong sign the front error is ~280 N, several points of aero balance. Include heave/third springs and bump rubbers in the sum if engaged; they often carry most of the aero load. Pushrod load cells remove the spring-rate and friction uncertainty.
Drag-moment convention. At constant speed the drag acts at a height of roughly 0.4–0.6 m while the tractive force acts at the ground. This couple transfers ~ from front to rear — about 300–400 N for the GT3 above. It is part of what the tyres "see", and tunnels quoting loads at the contact patch include it; tunnels restraining at the wheel centres may not. Make sure your track and tunnel balances use the same convention before claiming a correlation error of several percent.
g–g envelope method (whole lap). For a constant-μ tyre the maximum combined acceleration rises linearly with dynamic pressure: . Plot the outer envelope of combined g vs from many laps; slope/intercept gives roughly: . This is crude (load sensitivity bends the line, driver may not use the limit everywhere) but needs no suspension instrumentation and is excellent for comparing aero configurations over a test day.
Wind correction properly. With headwind , run speeds give . Averaging the two forces leaves a bias of — for 10 km/h at 200 km/h that's 0.25 %, negligible. Averaging the two coefficients computed with ground speed has the same small bias. Gusts within a run, however, are not cancelled; a pitot (or multi-hole probe) measuring real dynamic pressure (Segers §13.3) is the cure.
Measuring aero on track: coast-down, constant-velocity & logged-data estimates: L4 Expert explanation
Identifying an aero map from track data. Treat the problem as regression: unknowns are map coefficients (e.g. a quadratic surface in , for front and rear load), measurements are axle loads from load cells at many time samples. Model per sample:
If you regress the loads directly with roughly constant load noise (load cells), ordinary least squares is already correct: the high- points dominate naturally. If you regress the coefficients , whose noise variance is , weight each sample by . Either way, exclude transients (high , kerbs, g unless you include roll as a regressor). Check identifiability: if and always move together (no pitch variation), the separate gradients are unobservable — you need runs at different static rakes, which is exactly what Segers' advice to run at several static ride heights to populate the aero maps achieves (§13.7–13.8).
Uncertainty propagation. For : . A 1 % speed error is a 2 % error — GPS speed is better than wheel speed for this because wheel speed is corrupted by tyre growth and load-dependent rolling radius (several mm at 250 km/h on a slick). For coast-downs, differentiate speed carefully: fit a model to the whole speed-time curve (closed-form solution ) instead of differentiating noisy data. comes out with confidence bounds.
Systematic traps. Tyre temperature and pressure change rolling resistance during a run; downforce raises rolling resistance; driveline drag in neutral differs from that in gear (oil churning depends on speed). Gearbox oil temperature can change "rolling resistance" by 50–100 N. Ride height varies with speed, so from a coast-down is an average over a range of platforms — report it with the ride-height window.
Correlation philosophy. The goal is rarely the absolute number; it's the delta between configurations measured under the same conditions, plus a check that tunnel/CFD gradients match reality. Plan the test as an A-B-A-B sequence to remove drift (fuel burn, wind changes, track temperature), and decide beforehand what effect size you need to detect and how many repeats that requires given your measured repeatability.
Key formulas
- mass incl. rotating inertia (kg)
- a
- measured deceleration (m/s²)
- rolling + driveline resistance (N)
- track gradient (rad)
- MR
- motion ratio = spring travel / wheel travel
- spring rate (N/mm)
- spring (damper) compression (mm)
- absolute front aero load (N); if loads are zeroed at a low-speed run, use ΔL/(q − q_low) instead of L/q
- absolute rear aero load (N)
- AB
- aero balance (front share)
- engine torque (Nm)
- overall gear ratio
- driveline efficiency
- dynamic rolling radius (m)
Trackside takeaways
Coast-down for drag, constant velocity for downforce and balance; always both directions.
Measure rolling resistance with a low-speed coast-down (correct for the drag still present, or fit A + BV²); include rotating inertia (~3 %).
A 60 km/h reference still carries ~9 % of the 200 km/h downforce: divide load increments by Δq, not q.
F_wheel = MR·k·x with MR = spring/wheel travel; heave springs and bump rubbers must be included.
A 0.3 mm potentiometer zero error can be ~10 % of front downforce: zero at low constant speed every run.
Logged-lap drag estimates depend on engine torque accuracy: fine for trends, poor for absolutes.
Every result is a point on the aero map: report it with the dynamic ride heights.
On your car
GT3 teams rarely get airstrip time; most aero checks are done from logged laps and occasional straight-line runs at tests. Damper-pot-based downforce estimates are workable because GT3 springs are relatively soft (deflections of several mm).
Check yourself
In a coast-down a 1300 kg car (effective mass incl. rotating inertia 1340 kg) decelerates at 1.8 m/s² at a mean speed of 57 m/s. Rolling resistance + driveline drag = 400 N, ρ = 1.20 kg/m³. What is C_D·A?
- Segers – Analysis Techniques for Racecar Data Acquisition — §13.5 Estimating Drag and Downforce from Logged Data
- Segers – Analysis Techniques for Racecar Data Acquisition — §13.6 The Coast-down Test
- Segers – Analysis Techniques for Racecar Data Acquisition — §13.7 The Constant Velocity Test
- Segers – Analysis Techniques for Racecar Data Acquisition — §13.8 A Worked out Example of a Straight-Line Test
- Milliken & Milliken – Race Car Vehicle Dynamics — Ch. 15 Applied Aerodynamics
- Other — SAE J1263 Road Load Measurement and Dynamometer Simulation Using Coastdown Techniques