Prioritize balance, then load, then drag
Generated from
content/lms/race-aerodynamics/07-turn-findings-into-a-tuning-plan/02-prioritize-balance-load-then-drag.md; edit the source file, not this page.
Source path: content/lms/race-aerodynamics/07-turn-findings-into-a-tuning-plan/02-prioritize-balance-load-then-drag.md
Course: Engineer downforce you can actually use
Module: Turn findings into a tuning plan
Estimated duration: 55 minutes
The priority order
You are not tuning aero to win a top-speed contest. You are tuning the car to be quicker over the whole lap or run. The working order is simple: balance first, total load second, drag third. That order matters because the car only gives you useful aero information when the front and rear downforce aids are working together, and because the fastest setup at the end of the straight is not usually the setup that produces the best lap time.
Balance comes first because an unbalanced aero package hides the answer to every other question. If the car has too much rear aero authority relative to the front, it will tend toward medium- and high-speed understeer. If you respond to that by chasing total downforce or top speed, you are not learning whether the car needs more or less load. You are learning that the front and rear are mismatched. The first job is to make the car aerodynamically neutral enough that a change in total downforce can be judged on lap time, sector time, corner speed, and straight speed instead of being judged through a balance problem.
Load comes second because once the car is balanced at a given front and rear setting, you can build a table of balanced setups from low downforce to high downforce. That table is the useful product of the test. It lets you ask which balanced level is quickest at this venue, and it gives you a starting point for other venues. It can also save practice time when conditions change. If you return to a track where you have already built the table and it is raining, you can choose the maximum practical rear setting and its matching front setting instead of spending the session searching for balance.
Drag comes third because drag is real, measurable, and important, but it is not the first decision. Straight-line speed is one part of the lap. The lap is also made of higher-speed corner entry, apex, and exit speeds, acceleration from corner exit, and braking distance into the next corner. A setup that reduces drag enough to raise top speed may still lose more time in the corners or in the following acceleration and braking sequence. Drag measurement is valuable when it answers a specific question that remains after balance and load have been tested. It is a poor first filter when it tempts you to ignore the whole-lap result.
This lesson is about turning aero findings into a tuning plan. It assumes you have already translated feedback into testable questions, and that you will still validate changes in actual racing air. The focus here is the decision order: how to prevent yourself from solving the easy problem first and the important problem last.
What balance, load, and drag mean in this lesson
Balance is an operational condition, not a vague compliment. In this workflow, balance means the medium- and high-speed handling condition produced by the front and rear downforce aids has been brought out of the intentionally stable understeer you used as a starting point. You begin from a stable condition because it gives you a safer and clearer direction of travel. Then you adjust rear and front downforce until the faster-corner understeer is removed and the car is balanced for that total aero level.
Load means the amount of downforce represented by a matched front and rear setting. You do not treat rear wing angle, spoiler setting, or front downforce setting as isolated trophies. A rear setting becomes useful only when it has a front setting that balances it. A front setting becomes useful only when it belongs to a repeatable row in your table. The row is the setup: rear setting, front setting, lap or run time, segment times, straight-line speeds, high-speed corner speeds, driver balance notes, and conditions.
Drag means the straight-line resistance effect you see indirectly in straight speeds and sector times, or measure directly with methods such as coastdown, suspension-load measurement, driveshaft strain, or a maximum-speed calculation when the required inputs are available. The practical caution is that common direct methods measure total drag force, not pure aerodynamic drag alone. Mechanical resistance is inside the result. That does not make drag measurement useless. It means drag is a tool to use carefully, after you know the setup is balanced enough for the comparison to mean something.
The mechanism: why whole-lap time beats top speed
A lap is a chain of sections, not a single speed trap. One section may reward downforce by letting you carry more speed through a known-radius corner. The next section may reward lower drag by letting the car accelerate better along a straight. Then the next braking zone depends on the speed you reached and the speed you must slow to for corner entry. Even a simple lap model builds the lap by calculating a corner speed, using that as the exit speed for the next straight, calculating acceleration to the end of the straight, calculating braking distance to the next corner entry speed, and repeating that process until the sector times add up to the full lap.
That is why downforce and drag cannot be judged by one number in isolation. More downforce may help the car through a fast corner, help the driver place it better at exit, and improve the next straight by raising the speed at which acceleration begins. The same change may also add drag and reduce speed near the end of the straight. Less wing may make the top-speed number look better, yet cost more time before the speed trap than it gains at the speed trap. The only honest judge is the timed result, supported by segment data and driver feedback about high-speed aero balance.
This is also why the tuning order protects you from a common trap. If you put drag first, you are tempted to choose the setup that looks cleanest down the straight. If you put load first without balancing the car, you are tempted to choose the setup that feels secure but is actually just understeering. If you put balance first, then build a load ladder, then inspect drag as part of the lap-time picture, each decision is made with fewer confounding variables.
The prerequisite: start from a mechanically sorted car
Aerodynamic testing is clearest when the mechanical setup is already optimized enough that medium- and high-speed changes can reasonably be attributed to downforce adjustments. That does not mean the car must be perfect. It means you should avoid using aero changes to mask a basic mechanical balance problem. If the car is poor in low-speed corners and poor in high-speed corners in the same way, you may not yet have an aero question. If the test venue has both low-speed and higher-speed corners, use that contrast to help separate mechanical balance from aerodynamic balance.
Low-speed corners are useful because aero forces are smaller there. Higher-speed corners are useful because downforce effects become visible in entry, apex, and exit speeds, and in the driver feedback about medium- and high-speed balance. The split is not a magic speed line; it depends on the car and its downforce level. The practical point is to avoid treating every handling complaint as an aero problem. The more you can isolate low-speed mechanical behavior from high-speed aero behavior, the cleaner your tuning plan becomes.
Build the first balanced point
A disciplined first run starts from a dynamically stable condition. Set the front downforce aid to its minimum setting. Set the rear downforce aid to a setting you believe will outperform the front. If that means maximum rear downforce, use maximum rear downforce. The purpose is not to be fast on the first run. The purpose is to create a stable medium- and high-speed understeer condition that gives you a clear adjustment direction.
Go out and try the car in the faster corners that are suitable for the test. If the car understeers as expected, reduce rear downforce until the car is balanced. That establishes the minimum-downforce balanced setting for this test sequence. If the car still understeers after the rear wing or spoiler has been reduced to its minimum setting, the answer is not to keep reducing rear. There is no more rear to remove. Increase the front downforce setting until the understeer is removed.
This first balanced point is the anchor of the table. It tells you what front and rear combination produces a balanced car at the low end of the downforce range. Record it as a setup row, not as a memory. Include the front setting, rear setting, lap or run times, driver notes, and any logged data you have. If you are using a data logger, it may capture much of what you need, but you still need notes and times tied to the configuration. The notes matter because aero balance is partly read through the driver, and the driver feedback must be connected to the exact configuration that produced it.
Build the balanced load ladder
After the first balanced point, increase rear downforce. Run the car again and look for the faster-corner understeer that tells you the rear has moved ahead of the front. Then add front downforce until the car is balanced again. That gives you a second balanced point, with more total downforce than the first. Record the same information: settings, times, speeds, segment behavior, and feedback.
Repeat the process until you reach the maximum rear downforce setting you can practically use. Each iteration creates another row in the balanced table. The table should run from minimum practical downforce to maximum practical downforce, with matching front settings for each rear setting. It is time-consuming and it puts use on the car, but it reduces guesswork later. Instead of arriving at the next event with a pile of impressions, you arrive with a reference: at this venue, these front settings balanced these rear settings, and these were the timed consequences.
This table also keeps load decisions honest. Without the table, adding rear wing may feel like adding grip, but the front may be left behind. Adding front may feel like sharpening the car, but the rear may be short of support. With the table, total load is tested through matched pairs. You are comparing balanced low load to balanced medium load to balanced high load. That is the comparison that can answer the lap-time question.
What to record in each setup row
A useful row contains more than a lap time. Record the front setting, rear setting, and any other aero configuration information that changed. Record the lap or run times used in the comparison. Record segment or sector times if available. Record straight-line speeds because drag and acceleration effects often show there. Record higher-speed corner entry, apex, and exit speeds where the data allows. Record the driver feedback about aerodynamic handling balance, especially whether the car is still understeering in the faster corners or whether the adjustment has brought the package back into balance.
Also record the conditions that might move the baseline: weather, track condition, and tire state. You do not need professional-level instrumentation to make this useful. Basic data loggers can capture enough speed and time information for a disciplined comparison. The discipline is the point. The same lap time with no configuration note is trivia. The same lap time attached to a known front and rear setting, a known run order, a known baseline check, and a driver balance note becomes evidence.
Use enough laps to reduce noise. One practical method from the racing-engineering tradition is to run each configuration for five laps, average the lap times, and discard laps that are abnormally high or low. This is not perfect statistics, but it is a practical way to avoid treating one messy lap as the truth. The more important rule is that only the intended configuration changes during the comparison. If you change the wing, tire pressures, driver approach, and run timing all at once, you have made the result hard to trust.
Return to baseline before the baseline moves away from you
The baseline is not fixed just because you wrote it down. Conditions change during a session. Weather and track condition can move. Tires deteriorate. Even if the setup has not changed, the car you are testing may not be identical to the car you tested at the start of the hour. That is why a disciplined aero test returns to the baseline periodically. The baseline return tells you whether the difference you are seeing is still a configuration difference or whether the whole session has drifted.
This is not bureaucracy. It is how you keep from making a confident wrong decision. Suppose your third downforce level looks slower than your first. If you never go back to the first, you do not know whether the third setup is worse or whether the track, weather, or tires have changed. A baseline return will not solve every uncertainty, but it gives you a reference point. If the original baseline has also slowed, you know the session changed under you. If the baseline repeats, the configuration comparison is more credible.
For an intermediate driver, the baseline return has another benefit: it resets your feel. Aero changes can gradually recalibrate your expectations. Returning to a known setting helps you feel what actually changed instead of trusting a memory from twenty minutes ago.
Decide load from the balanced table
Once you have a balanced ladder, load selection becomes a comparison among rows. Look at the lap or run time first. Then look at the sector times and speed traces to understand where the time came from. A high-downforce row might be better through the faster corners and worse on the straight. A low-downforce row might win a straight speed number and lose the lap. A middle row may be the best compromise at that venue. The point is not to predict the answer by opinion. The point is to make the car balanced at each load level and then let timed evidence show which row is quickest.
This is where the top-speed trap usually appears. A higher top speed than your competitors may feel satisfying, but it does not necessarily improve the finishing position. If the setup that produces that speed costs more time in high-speed corners or in the sections that follow them, it is the wrong answer for the lap. You should still record straight speed. You should still care about drag. But straight speed is a clue inside the whole-lap comparison, not the trophy.
Data logging strengthens the decision because it lets you compare cornering and straight-line speeds along with segment and lap times. If the high-load row improves the fast-corner entry, apex, and exit speeds but gives away a small amount at the end of a straight, the sector time tells you whether the trade was worth it. If the low-load row gives a strong straight-line number but the fast corner and following segment suffer, the lap time will usually expose it. The car does not need to tell a dramatic story. It needs to tell a repeatable one.
Use drag as the third filter
After balance and load, drag questions become much clearer. You are no longer asking whether one random configuration is slipperier than another. You are asking whether, among balanced configurations that have been tested for timed performance, a drag reduction is worth pursuing. Sometimes the indirect measurements are enough: sector times, straight speeds, and lap times may already answer the question. If lower drag improves straight speed but loses the lap, you do not need a more elaborate drag test to choose that setup. If two balanced load levels are close on lap time and one is consistently better in the straight sectors, drag may be the deciding topic.
Direct drag measurement is possible with surprisingly modest instrumentation in some cases, but it must be interpreted carefully. Suspension-load measurement in the horizontal plane and driveshaft strain measurement can provide total vehicle drag, but the sensors and logging systems may be beyond many budgets. A maximum-speed calculation can be used only when you have the required space, gearing, reliable at-the-wheels power, and frontal-area information. Coastdown testing is the common practical method: use a long, straight, flat, smooth road and measure deceleration to infer total drag force.
The word total matters. Coastdown and similar methods include mechanical resistance as well as aerodynamic resistance. That means a change in measured total drag is not automatically pure aero. You can still learn useful information, especially when comparing controlled configurations, but you should not pretend the number contains only air. This is another reason drag belongs after balance and load. If the balanced table and timed results already show which setup is faster, direct drag measurement is supporting analysis, not the primary decision-maker.
Sub-skill: isolate the variable you are testing
The first sub-skill is isolation. Aero tests become meaningful when only the intended configuration changes. If you are comparing two wings, run the same basic test structure for each wing and do not mix in other setup changes. If you are building a balanced load ladder, make the front and rear downforce adjustments deliberately and record the result of each pair. If you suspect the track or tires have changed, return to baseline before drawing a conclusion.
Isolation also means choosing the right parts of the track for the question. Medium- and high-speed corners are where aero balance feedback and downforce effects should become more visible. Straight sections reveal acceleration and speed effects. Low-speed corners help you avoid mistaking a mechanical balance issue for an aero issue. The plan should say what each track section is being used to learn. If every section is asked to answer every question, your notes will become muddy.
Sub-skill: translate driver feedback into configuration rows
Driver feedback matters, but it must be attached to the setup that produced it. A note saying the car pushed in the fast corner is useful only if it is tied to the front and rear settings, run order, times, and conditions. A note saying the car felt better is weaker than a note saying the understeer seen in the faster corner on the first run was reduced after a specific front adjustment. The goal is not literary feedback. The goal is feedback that helps you decide the next setup step.
For this lesson, the key feedback word is understeer in medium- and high-speed corners. You deliberately start with a stable understeer bias, then use rear reduction or front increase to remove it. Later, when you increase rear downforce to climb the load ladder, you expect the balance to move again and you use front adjustment to bring it back. The driver is part of the measurement system, but only if the feedback is disciplined and tied to the configuration.
Sub-skill: use simple tools carefully
You do not need a professional simulation suite or full force measurement to make progress. Track testing with lap times, sector times, speed traces, and driver feedback can produce valuable information when the method is disciplined. Flow visualization can help you see what air is doing around wings, spoilers, diffusers, cooling intakes, and outlets, and it can point toward areas worth improving. Simulation can compare basic aerodynamic configurations before you arrive at a circuit, but it relies on assumptions whose validity varies. Simple or affordable tools are useful when you use them carefully and with common sense.
This sub-skill is partly humility. A model can suggest that one downforce-drag combination should be quicker. A flow pattern can suggest a development direction. A coastdown test can show a change in total drag. None of those should override a controlled track comparison that shows the balanced car is faster or slower in the sections that matter. Tools are not the plan. They feed the plan.
Worked example: the wet return to a known test venue
Imagine you previously tested at a venue with both lower-speed and higher-speed corners. During that test, you built a balanced table from minimum practical downforce to maximum practical rear downforce. Each rear setting has a matching front setting, and each row has times and notes. Now you return to the same venue and it is raining.
Without the table, you might spend precious practice time searching for balance. You would add rear downforce for stability, then wonder how much front to add, then use wet practice laps to rediscover something you could already have known. With the table, the first decision is straightforward. Choose the maximum practical rear downforce setting and the front setting that balanced it in your test. That does not guarantee the car is perfect in the wet, but it gives you a known balanced high-load starting point. Now practice time can be used on the wet track itself instead of on a blind balance search.
This example shows why balance comes before load. The useful wet setup is not simply maximum rear. It is maximum rear with the front setting that balances it. It also shows why records matter. The table you made on a dry test day becomes a time-saving tool on a different day. It may not eliminate fine-tuning, but it reduces guesswork.
Worked example: two wing configurations in a controlled comparison
Now imagine you are comparing two wing configurations. The wrong version of the test is to run one wing early in the session, change several things, run the other wing later when the tires and track have changed, and then argue from the best single lap. The disciplined version is to run each configuration in a controlled block, keep the changes limited to the wing configuration, record average lap times, discard abnormal outliers, and use sector and balance information to understand the result.
A practical block is five laps per configuration. After each block, you record the configuration, the laps used in the average, any abnormal laps you removed, driver balance feedback, sector behavior, and straight speeds. If weather, track condition, or tire state may be changing, return to the baseline configuration periodically. That baseline return is the guardrail that keeps you from mistaking session drift for an aero result.
The decision is not which wing has the better story. It is which wing gives the better timed performance while keeping the car balanced in the relevant speed range. One wing might produce more straight speed but worse fast-corner sectors. Another might give a better high-speed corner and a slower terminal speed. You choose from the whole result, not from the number that flatters the setup you wanted to like.
Worked example: simulation as a starting point, not a verdict
Suppose you have access to a simple performance simulation. The model uses a known corner radius and an assumed grip level to calculate a theoretical maximum corner speed. It then carries that speed onto the straight as the exit speed, calculates acceleration to the end of the straight while accounting for aero forces, calculates the braking distance needed for the next corner entry speed, and repeats that process around the lap. Different aerodynamic configurations can then be compared for relative lap time.
This is useful. It can help you arrive with settings that are close enough to make practice efficient. It can show why a downforce change that hurts top speed might still improve the lap, or why a low-drag choice might be attractive at a particular venue. But the model is only as good as its assumptions. Grip level, corner behavior, and the simplifications inside the calculation all affect the answer. Treat the simulation as pre-event triage. It helps you choose the first rows to test. It does not replace the balanced table and the track evidence.
Worked example: deciding whether to run a coastdown drag test
You have completed a balanced load ladder and two rows are close on lap time. The higher-load row is better through a fast sector, but the lower-load row is consistently stronger down the longest straight. The lap times are close enough that you want to understand the drag cost more clearly. This is an appropriate time to consider a drag measurement.
A coastdown test can be practical if you have a long, straight, flat, smooth road and can control the procedure. It gives you a measurement of total drag force. That result includes mechanical resistance as well as aerodynamic drag, so you treat it as a comparison tool rather than a pure aero number. The result may help you decide whether a configuration change is worth pursuing, but it should be interpreted alongside the track data. If the supposedly cleaner setup loses the lap by a repeatable margin, the coastdown number does not rescue it. If the lap result is close and the straight-sector difference is important, the drag test may tell you where to look next.
Common mistakes
Mistake one is chasing top speed first. The symptom is that your notes celebrate the highest speed number while the lap or run time is ignored or explained away. The cost is that you may choose a setup that looks fast in one place and is slower over the whole lap. Good looks like recording straight speeds as part of the evidence, then choosing the balanced row that produces the best timed result.
Mistake two is tuning load on an unbalanced car. The symptom is that you keep adding rear downforce because the car feels secure, while the faster-corner understeer remains. The cost is that you never learn whether the car wants more total downforce or simply needs the front and rear matched. Good looks like starting from stable understeer, reducing rear or increasing front as the method requires, and only comparing load levels after each one has been balanced.
Mistake three is changing too much at once. The symptom is a test sheet full of wing changes, tire changes, unrelated setup changes, and driver approach changes all in the same run. The cost is that the result cannot tell you which change mattered. Good looks like changing the intended aero configuration, running enough laps to average sensibly, and returning to baseline when conditions may have moved.
Mistake four is trusting one lap. The symptom is choosing a setup because it produced the best single lap, even though the other laps in the block do not support it. The cost is that you may be selecting a driver execution lap, a traffic lap, or a condition lap instead of a configuration. Good looks like using a block of laps, averaging the usable laps, and removing abnormal highs or lows from the comparison.
Mistake five is forgetting that the baseline can drift. The symptom is a clean-looking test sequence with no baseline return, even though tires, weather, or track condition changed. The cost is a false conclusion. Good looks like periodically returning to the baseline setup so you can see whether the reference has moved.
Mistake six is treating direct drag as pure aero. The symptom is a coastdown or other total-drag result being discussed as if it contains no mechanical resistance. The cost is overconfidence in the wrong number. Good looks like calling it total drag, controlling the comparison, and using it with lap, sector, and speed evidence.
Mistake seven is overtrusting the model. The symptom is arriving with a simulated answer and treating track testing as a formality. The cost is that assumptions become decisions. Good looks like using the model to choose a sensible starting point, then fine-tuning with real track evidence.
Drill: the balanced ladder test
Run this drill during a test day or practice session where configuration changes are allowed and where you can repeat laps safely and consistently. The purpose is to leave the event with at least three balanced aero rows and enough evidence to choose a load direction without chasing top speed.
Before the first run, make a setup sheet with columns for run number, front setting, rear setting, lap or run times, sector times if available, straight speed, faster-corner feedback, conditions, and action for the next run. Choose the faster corners and straight sections you will use as your evidence points. If the venue also has lower-speed corners, mark them as a cross-check for mechanical behavior rather than as the main aero evidence.
Run one is the stable start. Set the front to minimum downforce and set the rear high enough that you expect the rear to outperform the front. If that requires maximum rear downforce, use it. Drive a controlled block and look for medium- and high-speed understeer. Record the times and feedback. If the car understeers as expected, reduce rear for the next run. If the rear is already at minimum and the understeer remains, increase front for the next run.
Run two is the first balance point. Adjust according to the run-one result and repeat the same evidence sections. Your goal is to remove the faster-corner understeer and establish the low-downforce balanced row. Record the exact front and rear settings and the timed evidence. If you cannot reach balance, stop treating the drill as a load comparison and document the blocker. A load ladder without a balanced first row is not a load ladder.
Run three is the next load step. Increase rear downforce from the first balanced row, then drive the same evidence sections. Expect the balance to move. Add front downforce as needed in the next adjustment to bring the car back to balance. Record the new balanced row when the faster-corner balance returns.
Run four is the high-load step or the baseline return, depending on session length and condition stability. If conditions are stable, continue the ladder by increasing rear again and matching it with front. If conditions have changed, return to the first balanced row and see whether it repeats. The success criterion is not that you find the perfect aero setup in one session. The success criterion is that you finish with at least three recorded rows or two rows plus a baseline return, and that your next aero decision is based on balanced timed evidence rather than the highest straight-line speed.
How to know you are improving
You are improving when your aero notes become predictive. Before a session, you can state which front setting should balance a given rear setting because you have already tested that row. After a run, you can say whether a lap-time change came from the fast-corner sector, the straight, or the baseline moving. When conditions change, you can choose a starting point from the table instead of beginning from guesswork.
You are also improving when your language changes. Instead of saying the car needs more wing, you say which end is short of downforce at the current row, which rear setting you are testing next, and which front setting will be tried to restore balance. Instead of saying the car is slow on the straight, you say whether the straight-speed loss is larger or smaller than the fast-corner and segment-time gain. Instead of saying the model said the setup should work, you say the model suggested a starting configuration and the track test confirmed or rejected it.
Finally, you are improving when top speed becomes just one line in the evidence. You still care about it. You still record it. But you no longer let it outrank lap time, sector time, and balance. That is the practical maturity of aero tuning: you stop asking which setup looks fastest in isolation and start asking which balanced setup makes the car quicker around the whole venue.
When the priority order bends but does not break
There are times when you cannot fully separate mechanical and aerodynamic balance. Practice time may be short. The test venue may not have the clean mix of low- and high-speed corners you would like. Weather may change before you finish the ladder. In those cases, do not pretend the evidence is cleaner than it is. Use the same order, but label the confidence correctly. Balance the car as well as the session allows, compare load levels only where the balance is credible, and treat drag conclusions as provisional unless the straight-speed and timed evidence are repeatable.
There are also times when drag becomes urgent earlier, such as a venue where straight-line performance dominates the lap. Even then, drag should not erase the balance step. A low-drag setup that creates an unresolved high-speed balance problem is not a clean answer. The better adjustment is to build the lowest-load balanced row you can, then compare it against higher-load balanced rows with the straight-sector data included. Drag may carry more weight at that venue, but it still belongs inside a balanced whole-lap comparison.
Cross-references
This lesson sits between question-making and documentation. Use the lesson on translating high-speed feedback into testable aero questions before you choose the variables for a test. Use the lesson on validating in racing air when you need to confirm that a configuration behaves on track rather than only in a model or static observation. Use the speed and ride-height map lesson to preserve the data structure after the test. Use the lesson on deciding what is not an aero problem when low-speed behavior or mechanical setup is polluting the conclusion.
The takeaway
The tuning plan is not more rear wing, more front, less drag, or more top speed. The plan is a sequence. Start from a stable aero condition. Balance the car. Increase total downforce in matched front and rear rows. Record times, sector behavior, straight speeds, and driver feedback. Return to baseline when conditions may have changed. Choose the load level from the timed result. Then use drag analysis to explain or refine the decision, not to replace it. That order keeps the car honest and keeps you from mistaking the most visible number for the most important one.
Worked example: the wet return to a known test venue
Imagine you previously tested at a venue and built a balanced table from minimum practical downforce to maximum practical rear downforce. Each rear setting has a matching front setting, with times and notes. When you return and it is raining, you can choose the maximum practical rear setting and the front setting that balanced it, then spend practice time learning the wet track instead of searching blindly for aero balance.
Worked example: two wing configurations in a controlled comparison
For a two-wing comparison, run each configuration in a controlled block, keep the change limited to the wing configuration, average the usable laps, discard abnormal outliers, and return to baseline if conditions may have changed. The decision comes from timed performance, sector behavior, straight speed, and driver balance feedback, not from the best single lap or the highest top-speed number.
Worked example: simulation as a starting point, not a verdict
A simple performance simulation can compare configurations by building the lap from corner speed, acceleration down the straight, braking distance, and repeated sector calculations. Use that output to arrive with sensible starting settings, but remember that the model depends on assumptions. The track test still has to build balanced rows and confirm the timed result.
Worked example: deciding whether to run a coastdown drag test
After a balanced load ladder, two rows may be close enough that straight-line loss becomes the deciding question. A coastdown test on a long, straight, flat, smooth road can help compare total drag force, but the result includes mechanical resistance as well as aerodynamic resistance. Use it alongside lap, sector, and speed evidence.
Common mistakes
The common errors are chasing top speed first, tuning load on an unbalanced car, changing too many variables at once, trusting one lap, forgetting that the baseline can drift, treating total drag as pure aero, and overtrusting simulation. Good work looks like matched front and rear rows, controlled configuration changes, periodic baseline returns, averaged usable laps, and decisions made from whole-lap evidence.
Drill: the balanced ladder test
At your next suitable test or practice session, prepare a sheet for front setting, rear setting, lap or run times, sector times, straight speed, faster-corner feedback, conditions, and next action. Run a stable-start configuration with minimum front and high rear, establish the first balanced row, increase rear to create the next load step, add front to rebalance, and either continue to a higher-load row or return to baseline. Success means at least three recorded balanced rows, or two rows plus a baseline return, with the next decision based on timed evidence rather than top speed.
When this principle bends but does not break
Short sessions, changing weather, tire deterioration, and imperfect venues can keep you from separating mechanical and aerodynamic effects cleanly. Keep the same priority order, but label confidence honestly. Balance as well as the session allows, compare load only where the balance is credible, and treat drag conclusions as provisional until straight-speed and timed evidence repeat.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 80bde176-e318-b515-e3d5-5de74a7cd507 | 476 | 1 | uio_books_raw_v1 |
| 2 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 9ae791d1-a3da-7f15-55b0-1c14b09569fc | 475 | 1 | uio_books_raw_v1 |
| 3 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 4adf8cb4-89c7-1b45-bd4d-9bb03634ecf3 | 345 | 1 | uio_books_raw_v1 |
| 4 | Competition Car Aerodynamics 3rd Edition McBeath Simon | c0cd0f54-6d9c-7f08-e9af-37c31b3421d3 | 345 | 1 | uio_books_raw_v1 |
| 5 | Competition Car Aerodynamics 3rd Edition McBeath Simon | c87c89fe-58c4-8968-6248-4a307e39f9e2 | 346 | 1 | uio_books_raw_v1 |
| 6 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 90d1fa19-5889-6e05-3847-4f1454f3babb | 384 | 1 | uio_books_raw_v1 |
| 7 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 6edca499-2988-7702-ccc8-3d17b516edff | 385 | 1 | uio_books_raw_v1 |
| 8 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 576d96a1-00b7-66dd-f5b1-e33666cc457f | 334 | 1 | uio_books_raw_v1 |