Turn pressure maps into vertical load

Generated from content/lms/race-aerodynamics/02-shape-the-whole-cars-airflow/02-map-pressure-into-vertical-load.md; edit the source file, not this page.

Source path: content/lms/race-aerodynamics/02-shape-the-whole-cars-airflow/02-map-pressure-into-vertical-load.md

Course: Engineer downforce you can actually use

Module: Shape the whole car's airflow

Estimated duration: 55 minutes

Learning goal

You are learning how to read pressure measurements as a vertical-load story. The aim is not to make an attractive pressure plot. The aim is to answer a driving and setup question: is this surface change reducing lift or adding downforce, where on the car is that happening, and does the chassis show the same answer when you look at ride height, suspension compression, sector speed, and high-speed balance?

For an intermediate driver, this skill matters because aero changes are easy to feel incorrectly. A wing angle, undertray change, diffuser strake, or ride-height adjustment may feel better because the car is calmer in one place, worse because it adds drag somewhere else, or invisible because the test was too noisy. Pressure mapping gives you a local explanation. Ride-height or suspension-deflection measurement gives you the accessible vertical-load check. Lap time, sector speed, and driver feedback tell you whether the measured change is usable at speed.

The principle

For lowest lift or maximum downforce, you are trying to create higher pressures on upper panels and lower pressures under the car. That is the simplest pressure-to-load rule in this lesson. If the upper surface pressure rises, that pressure pattern tends to help push the car downward. If the underbody pressure falls, that pressure pattern tends to help pull the car downward relative to the air above it. The exact car force is not proven by one pressure tap, but the sign of the change tells you whether the local pressure field is moving in the right direction.

That rule also explains why a pressure map is not the same thing as a downforce number. A pressure measurement is local. It tells you what is happening at the puck, tap, tube, panel, diffuser area, wing surface, or rear body area you sampled. A vertical-load measurement is global enough to show what the suspension, ride height, or load path is seeing at speed. The useful workflow is to make the pressure map and vertical-load measurement agree with each other. If a diffuser change lowers pressure under the rear of the car, the rear ride-height or rear suspension deflection should move in a direction consistent with more rear download at the same speed. If it does not, you do not yet have a reliable setup conclusion.

Think of the lesson as a three-layer map. The first layer is local pressure: upper body, underbody, diffuser, wing, or rear body panels. The second layer is chassis response: front and rear ride height, damper travel, suspension compression, or load cell reading. The third layer is use on track: handling balance at speeds where aero matters, sector speeds, lap averages, and the driver feedback that says whether the car is actually better.

Why reference pressure matters

A pressure number only becomes useful when you know what it is being compared against. To calculate actual static pressure differences or pressure coefficients, the body-surface readings need a reference static pressure in air that is not disturbed by the car. On a closed car, the reference may be measured inside the car. On an open car, the more reliable reference is a Pitot tube positioned a few feet above or ahead of the car. The same Pitot arrangement can provide total pressure, and the difference between total pressure and reference static pressure gives dynamic pressure. Dynamic pressure is what lets you account for the real speed of the air over the car, including wind.

This is why two runs at the same road speed may not be the same aero test. If the car is travelling into a headwind in one direction and with a tailwind in the other, the speed through the air has changed even if the dashboard speed is identical. A pressure setup that uses a Pitot reference is trying to measure the air the car actually sees, not the speed the driver thinks the car is doing. A practical road or track test should therefore include runs in opposite directions and average the readings. That is not ceremony. It is how you reduce wind bias enough to make the pressure map believable.

The basic field method

A simple pressure test can be done with a pressure puck, hose, gauge, and Pitot reference. Mount the puck on the panel of interest and hold it securely with tape. Run the sensing hose from the puck to the low-pressure port on the gauge. Mount the Pitot tube so it faces directly forward. Connect the other side of the gauge to the static port of the Pitot tube. Drive at the chosen test speed and record the gauge reading. Repeat in the opposite direction. Average the two readings.

If the gauge needle moves the unexpected way, or a digital gauge shows positive pressure when you expected suction, swap the hoses. Most of the useful readings in this work are small pressure differences, and a reversed connection can make you think a surface is helping when it is hurting. Do not treat the first number as truth. Treat it as a measurement that has to survive correct hose routing, repeated speed, opposite-direction averaging, and a return to baseline.

For more detailed surface pressure mapping, the traditional method is to drill small holes through the surface and fit tubes flush with the outer surface. Those tubes can connect to U-tube manometers, pressure scanners, or surface-mounted transducers. The principle is the same: each location reports the local static pressure. With enough locations, you can compile a distribution over a wing, diffuser, underbody, upper panel, or even the whole body.

The catch is that a whole-body pressure map takes many sample locations and many runs. Even with a multi-port scanner, the mapping process can be affected by weather, wind, track conditions, and other environmental changes while you collect the data. For a club or HPDE driver, the smarter use is usually a focused pressure profile. Pick the surface that answers the setup question. If you changed a diffuser strake, measure the diffuser or underbody area affected by that strake. If you changed a rear wing, measure the wing environment, rear ride height, and the pressures that show whether the rear body is seeing a useful change. Local pressure profiles are much more practical than pretending you can map the whole car accurately in one casual session.

Choosing the question before you test

Before you tape on a puck or drill a tap, write down the question in one sentence. Good questions are local and directional. Did the diffuser strake reduce pressure in the area it was meant to energize or seal? Did the rear wing angle create more rear download without obvious stall behavior? Did the undertray change reduce underbody pressure? Did the front ride-height change reduce lift at the front or merely change balance in a way the driver liked for unrelated reasons?

Bad questions are too broad. Did the car get more aero? Did the wing work? Is the car faster? Those are not pressure-map questions. A pressure map can help explain those outcomes, but it cannot answer them alone. When the question is too broad, you end up changing several things, collecting a few scattered readings, and then inventing a story afterward. The disciplined version is narrower: one configuration change, one set of pressure locations, one speed or speed band, one front-rear ride-height check, and one baseline return.

The front-rear balance question

Vertical load is not only about total downforce. It is also about where the load is added. For stability, you typically want less rear lift than front lift, or more rear downforce than front downforce. But this is not a universal command to add rear wing until the rear feels planted. The rest of the car matters. An understeering front-wheel-drive car may benefit substantially from increased front downforce because the limiting axle is already the front. The right pressure-to-load map therefore separates front and rear.

At minimum, track front and rear ride height or suspension compression at the same test speed. If your pressure change is under the front, the front ride-height behavior should be part of the answer. If your change is at the rear wing or diffuser, rear ride height is essential, but the front cannot be ignored. A rear-only improvement can shift the balance toward understeer. A front-only improvement can make the car point better but reduce high-speed stability if the rear is left lifting too much. The lesson is to map load distribution, not just celebrate a lower pressure number under one panel.

Turning pressure into a chassis reading

The most common accessible way to quantify downforce is to measure suspension deflection at speed. Linear potentiometers can be rigged to measure damper travel. The car is run at a constant, fairly high speed, and the aero-induced compression at front and rear is logged. Back in the garage, that travel is calibrated against known mass on each axle. If wheel rates are non-linear, the calibration has to cover the relevant range of travel rather than relying on one point.

This calibration is what turns a ride-height or damper-travel change into a usable vertical-load estimate. Without it, you only know that the car moved. With it, you can estimate how much download passed through the suspension. You still need to filter out track-surface noise, because bumps and ripples can move the suspension far more sharply than the aerodynamic load trend you are trying to measure. A clean constant-speed section on a long, flat, smooth straight is valuable because it gives the suspension trace a chance to show the aero effect instead of just the road.

Laser ride-height sensors are another route. They can be more precise depending on the amplitude of suspension travel, but they include tyre deformation. That does not make them useless. It means the ride-height versus vertical-load calibration needs to account for tyre deformation as part of the measured system. Load cells in springs, dampers, pushrods, or pullrods can measure download more directly through those paths. Wheel force transducers can include wheel-generated loads, but they are beyond the accessible level for most club programs.

The important limitation is that suspension deflection and suspension load measurements do not include vertical aerodynamic forces generated by the wheels themselves. This matters especially for open-wheel cars, but it can matter on closed cars too. So the number you get from damper travel or pushrod load is not the whole aerodynamic truth of the car. It is the body, wing, and suspension-path truth you can measure with accessible tools. Use it honestly and correlate it with handling at speed.

Building a credible test run

A credible aero test is boring on purpose. Choose a long, flat, smooth straight. Use a constant high speed that is safe for the venue and high enough for the aero change to matter. Keep the driver task repeatable. Change one configuration at a time. If you are comparing wings, run the same number of laps for each configuration, keep every non-wing setting stable, and use lap or sector averages rather than one hero lap. The Carroll Smith style wing comparison described in the corpus used five laps for each configuration, changed only the wing configuration, and discarded abnormal high or low times before averaging. That is exactly the spirit you want, even if your event structure forces shorter test blocks.

Baseline return is not optional when conditions change. Weather changes, wind shifts, track temperature moves, and tyres deteriorate. If you run baseline first, then configuration A, then configuration B, and never go back to baseline, you may be measuring the tyre or the air rather than the part. Periodically returning to baseline lets you see whether the car itself has drifted underneath the test. If the baseline no longer matches the earlier baseline, your confidence in the configuration comparison has to drop.

Pressure readings need the same discipline. If you measure the roof or underbody at the start of the day and the diffuser at the end of the day, the difference may include changing wind, surface conditions, or tyre state. If you are trying to compare two diffuser strakes, keep the pressure puck or taps in the same locations, repeat the same speed, drive both directions where possible, and return to the original strake or no-strake condition if the session allows.

Reading the signs

A helpful pressure change is not always the largest-looking number. For vertical load, start with sign and location. Higher pressure on an upper panel helps reduce lift. Lower pressure under the car helps reduce lift or increase downforce. A lower underbody pressure near the rear suggests more rear download if the ride-height trace agrees. A higher pressure on rear panels may reduce drag or change separation behavior, but by itself it is not the same as proving more downforce. A wing that makes rear ride height drop may be adding rear download, but if it is stalled it may also be acting like a large spoiler and adding drag out of proportion to useful load.

The rear wing example is a good place to keep your interpretation disciplined. First, use Pitot testing to find how high the wing must sit to be in freestream airflow, meaning air moving as fast as the car. A wing buried in slower, disturbed flow may not respond to angle changes the way you expect. Then optimize wing angle by measuring rear ride height. If rear ride height drops consistently at the same speed, the chassis is seeing more rear download through the measured path. But because many wings are run stalled, add a drag-side check such as throttle-stop testing or tufting when you need to understand the drag/downforce balance. Rear ride height alone says the rear is being loaded. It does not guarantee the load is efficient.

Underbody changes need the same restraint. A full-length undertray can be useful when chasing lower drag, but pressure measurement may not always be the best first test for drag. The corpus points toward going straight to throttle-stop testing for that lower-drag question. If your question is vertical load, pressure under the car and ride-height response belong together. If your question is drag, speed, throttle-stop, or coastdown style testing belongs in the discussion. Do not force a pressure map to answer a drag question it was not designed to answer.

Calibration cues for improvement

You are improving when your readings become repeatable before they become exciting. A good pressure test produces the same sign and similar magnitude when repeated at the same speed in opposite directions after averaging. A good ride-height test shows a consistent front or rear trend at the same speed, after filtering track-surface noise. A good configuration comparison still makes sense after you return to baseline. A good driver report mentions high-speed balance, stability, or grip in the section where the aero change should matter, not a vague whole-lap feeling.

On data, the cleanest cue is separation between configurations that is larger than the likely repeatability error. The corpus warns that downforce measurement repeatability may be on the order of plus or minus a few percent, so tiny increments are not worth over-claiming. If the expected change is smaller than the noise, write it down as inconclusive. If the pressure map changes clearly, the ride-height trace moves in the matching direction, and the car balance at high speed changes in the same direction, you have a much stronger conclusion.

On the steering wheel and seat, the cue is not mystical. More rear download should show up as a rear that is calmer and more resistant to high-speed oversteer, with the warning that too much rear bias can make the car understeer. More front download on an understeering car may show up as better high-speed front authority. Lower lift overall may make the car feel more settled as speed rises. These feelings are only useful when tied to the place on track where speed is high enough for aero load to be meaningful. If the driver reports a big difference in a slow corner, be cautious about crediting the pressure change.

How to use sector and lap data

Indirect measurements such as sector times, lap times, and speeds are often enough to decide whether a configuration is useful. They are not less serious just because they are indirect. A disciplined five-lap comparison can reveal handling balance and performance by track sector. The key is to avoid worshipping one lap. Average comparable laps, remove abnormal outliers, and look for the sector where the aero device should help or hurt. A high-downforce setup may gain in a fast section and lose on a straight if drag rises. A lower-drag undertray change may show speed benefit without a large pressure-map story. The pressure map tells you mechanism. The sector data tells you whether the mechanism paid rent.

For a driver, this matters because the fastest setup is not always the one with the lowest underbody pressure at one tap. You need balanced options ranging from low to high downforce levels, and then you need to correlate those settings with handling at speeds where aero matters. That correlation is the real lesson. You are building a map from local pressure to suspension load to driver-usable balance.

What not to duplicate from neighboring skills

This lesson does not try to teach the whole-car aero system from scratch. That belongs with the broader body-as-system lesson. It also does not deeply teach upstream flow protection, wheel and ground interference, or lateral stability. Those lessons sit next to this one. Here, you use those ideas only as boundaries: choose pressure locations that answer the specific device question, remember that wheels can create vertical aero loads that suspension-path measurements miss, and make front-rear balance part of the interpretation.

The practical standard

A useful pressure-to-load test ends with a sentence you can defend. For example: at the same test speed, this diffuser change reduced measured pressure under the rear area, rear ride height moved in the direction of more rear download after calibration, and the driver reported more high-speed rear stability; the change is probably adding useful rear aero load. Or: this rear wing angle lowered rear ride height, but tufting or throttle-stop evidence suggests stall or excess drag, and sector speed does not improve; the load may not be efficient. Or: pressure readings changed, but baseline drift and tyre deterioration make the comparison inconclusive; repeat with a tighter A/B/A plan.

That is what you are training. Not a single magic number. Not a belief that every new aero part worked. A pressure map becomes valuable when it is tied to a vertical-load check, corrected for test conditions, and judged against what the car does at speed.

Worked example: Mazda RX7 upper-body pressure mapping

Start with the named Mazda RX7 example as a pressure-mapping lesson rather than a setup prescription. The corpus describes upper-body pressure measurements on a Mazda RX7 and notes that undercar pressures matter when the goal is reducing lift. The instructional move is to take the same measurement logic and point it at the surface that answers your question.

If you want to understand an upper-panel change, mount the pressure puck on the roof or other panel of interest, route the hose to the gauge, reference the other side of the gauge to the static port of a forward-facing Pitot tube, and run the car at the designated test speed. Repeat the run in the opposite direction and average the two readings. If the sign looks wrong, check the hose routing before you invent an aero explanation.

Now translate the reading. A higher pressure on the upper panel is generally favorable for reducing lift. If you instead find low pressure over an upper surface, that area may be contributing to lift rather than helping download. But do not stop with that local answer. If the goal is vertical load, choose matching front or rear ride-height measurements for the same speed. The RX7 example teaches that pressure can be measured anywhere on or under the car; your job is to place the measurement where it can answer the current setup question.

Worked example: rear wing height, angle, and diffuser work on the Honda test car

The Honda sports-car examples in the corpus are useful because they show how quickly pressure, ride height, practicality, and drag become one problem. For a rear wing, first find whether the wing is actually in freestream air. Use Pitot testing above the car to determine how high the wing must sit to see air moving as fast as the car. A low wing in disturbed flow may still make the car feel different, but angle changes will not mean much if the wing is not being fed properly.

Once the wing is positioned, use rear ride height to optimize angle. At the same speed, more rear download should show as rear ride-height reduction or rear suspension compression, assuming the measurement is calibrated and the surface noise is filtered. But a stalled wing can still load the rear while acting like a large spoiler. That is why the corpus pairs wing angle with tufting or throttle-stop drag testing when the drag/downforce balance is in doubt.

The diffuser-strake example adds the practicality check. Longitudinal plywood strakes beside the diffuser reduced pressures, so the pressure result said they worked. But they were impractically deep. Shorter rubber replacements did not scrape on the road, but they also did not reduce pressures as much. That is the real track-day engineering trade: a pressure map can tell you that the aggressive part is aerodynamically stronger, while the car and venue tell you whether it is usable. The lesson is not to worship the lowest pressure. The lesson is to connect reduced pressure, vertical-load evidence, drivability, and physical practicality.

Worked example: Carroll Smith style two-wing comparison

Use the Carroll Smith style wing comparison as the model for configuration discipline. Two wings were compared. Each configuration was run over five laps. Only the wing configuration was changed. Lap-time averages were recorded, and abnormal high or low times were discarded. The value of that example is not that five laps is magical. The value is that the test structure kept the comparison clean.

For your own version, pair that structure with pressure and ride-height data. Run the baseline wing for a five-lap block or the event equivalent. Record rear ride height or rear damper travel at the same high-speed point each lap, along with sector times and driver notes. Switch to the comparison wing and repeat without changing other setup variables. If conditions are shifting, return to the baseline wing before declaring a winner.

The conclusion should include both performance and mechanism. If the new wing adds rear compression at speed, improves high-speed stability, and gains in the fast sector without a major straight-line penalty, you have a coherent case. If it adds rear compression but loses speed or feels lazy, the drag/downforce balance may be poor. If lap time improves but pressure and ride height do not agree, you may have found a driver-confidence effect or a test-noise problem rather than a clean aero gain.

Common mistakes

1. Treating one pressure tap as a downforce number. A pressure tap is local. It can show whether the local static pressure moved in a useful direction, but it does not by itself quantify the whole car load. Good looks like pairing the pressure reading with calibrated front or rear ride-height, suspension-deflection, or load-path data.

2. Forgetting the reference pressure. If you do not compare body readings with a reference static pressure in undisturbed air, you cannot make a clean pressure-coefficient or actual-pressure claim. Good looks like using a Pitot reference when needed and remembering that dynamic pressure reflects true airspeed, including environmental airflow.

3. Testing in one direction and trusting the result. Wind can bias the pressure reading even when road speed is identical. Good looks like running the same test in the opposite direction and averaging the readings.

4. Mapping too much of the car with too little discipline. Whole-body pressure plots require many locations and many runs, so conditions can drift during the test. Good looks like focusing on a wing, underbody, diffuser, or panel profile that answers a specific question.

5. Changing several things at once. If wing angle, ride height, tyre state, and undertray hardware all change, you cannot assign the pressure or load result to one cause. Good looks like one configuration change per comparison, with baseline returns when conditions move.

6. Ignoring tyre deterioration and baseline drift. A later run may be slower or feel worse because the tyres changed, not because the aero part failed. Good looks like periodic baseline checks and cautious conclusions when the baseline no longer repeats.

7. Reading suspension deflection as total aero load. Suspension deflection and suspension load measurements miss vertical aerodynamic forces generated by the wheels themselves. Good looks like calling the result the measured suspension-path or body-generated load, then correlating it with handling.

8. Calling a stalled wing successful because rear ride height dropped. A stalled wing can still load the rear while costing too much drag. Good looks like combining rear ride-height optimization with tufting or throttle-stop drag checks when wing efficiency is in question.

Drill: pressure-to-load correlation in three test blocks

Do this over three test blocks, each built around five steady laps or the closest equivalent your event allows. The success criterion is not a lap record. The success criterion is a conclusion that survives repeated readings, opposite-direction or baseline correction where possible, and agreement between pressure, ride height, and driver feel.

Block 1 is baseline measurement. Choose one local pressure target, such as an underbody point near a diffuser change or an upper panel you are studying. Mount the pressure puck or use existing taps. Reference the gauge to a forward-facing Pitot static port. Run at the designated speed, record the pressure, and repeat in the opposite direction if the venue permits. Record front and rear ride height or damper travel at the same speed. End with a short driver note focused only on high-speed balance.

Block 2 is one configuration change. Change only the chosen aero item: wing angle, wing height, diffuser strake, undertray detail, or ride height if that is the test. Repeat the same pressure location, same speed, same ride-height capture, and same driver note. If the pressure sign improves but the ride-height response does not agree, mark the result as unresolved rather than forcing a conclusion.

Block 3 is baseline return or second confirmation. Put the car back to baseline if conditions have changed, or repeat the better configuration if the earlier data was clean. Look for three things: the baseline repeats within the noise you can tolerate, the pressure change is larger than random scatter, and the ride-height or suspension-deflection trend matches the pressure story. If the change is tiny relative to repeatability of a few percent, call it inconclusive. That honesty is part of the drill.

When pressure maps are not enough

Pressure maps are strongest when you need mechanism. They tell you where the car is seeing higher or lower local static pressure and how a configuration change altered that pattern. They are weaker when you ask them to stand in for complete vehicle force measurement, drag measurement, or race-lap usefulness.

Use suspension deflection, load cells, or laser ride height when you need vertical-load evidence. Use sector and lap averages when you need performance evidence. Use throttle-stop, coastdown, or related drag methods when the question is drag. Use tufting when you suspect separated or stalled flow and need a visual sanity check. The rear wing example shows why: rear ride height may say the wing loads the car, while tufting or drag testing may reveal that the load is being bought inefficiently.

The deeper rule is to match the tool to the question. Pressure for local cause. Ride height or suspension load for accessible vertical-load response. Sector, speed, and driver feedback for usefulness. Baseline returns for trust.

Author Review

No quiz questions are attached to this lesson.

Sources

#	Document	Chunk	Pages	Score	Collection
1	uio julian edgar car aero testing	237ab1cc-b3cd-b239-83e4-b9ffcef75fdf	91	1	uio_books_raw_v1
2	uio julian edgar car aero testing	561b0517-420a-cee0-a0d0-cbb161f44d01	92	1	uio_books_raw_v1
3	Competition Car Aerodynamics 3rd Edition McBeath Simon	0278f848-5839-0a5b-9776-f3dabc163310	350	1	uio_books_raw_v1
4	Competition Car Aerodynamics 3rd Edition McBeath Simon	c7061e35-15c9-08fb-b0a9-b04116b1715c	348	1	uio_books_raw_v1
5	Competition Car Aerodynamics 3rd Edition McBeath Simon	e69e50b8-72e1-795d-d8ff-b80dec2cc10c	352	1	uio_books_raw_v1
6	Competition Car Aerodynamics 3rd Edition McBeath Simon	c0cd0f54-6d9c-7f08-e9af-37c31b3421d3	345	1	uio_books_raw_v1
7	uio julian edgar car aero testing	89abcae8-3403-71f2-1f72-df5627d4be7a	47	1	uio_books_raw_v1
8	Competition Car Aerodynamics 3rd Edition McBeath Simon	c87c89fe-58c4-8968-6248-4a307e39f9e2	346	1	uio_books_raw_v1