Decide aero changes with lift-to-drag
Generated from
content/lms/race-aerodynamics/05-trade-downforce-against-drag/02-use-lift-to-drag-as-the-decision-lens.md; edit the source file, not this page.
Source path: content/lms/race-aerodynamics/05-trade-downforce-against-drag/02-use-lift-to-drag-as-the-decision-lens.md
Course: Engineer downforce you can actually use
Module: Trade downforce against drag
Estimated duration: 50 minutes
The decision you are really making
When you change aero, you are not trying to win a downforce contest. You are deciding whether a configuration gives you enough useful load to justify the drag it brings with it. Lift-to-drag is the cleanest lens for that decision because it forces you to ask two questions at the same time: what did the car gain in grip, stability, or confidence, and what did it pay in speed, acceleration, and sector time?
For an intermediate driver or club racer, this lesson is not about designing a wing profile from scratch. It is about making disciplined setup decisions with the car you have. You may be changing rear-wing angle, adding or removing a Gurney, blocking or opening cooling exits, changing splitter height, trimming dive planes, or choosing between bodywork options. The shape of the decision is the same. A change that adds downforce and adds drag is not automatically good. A change that reduces drag and loses downforce is not automatically good. You judge the package by the useful aerodynamic force it gives you per unit of drag cost, then you verify that judgement against sector time, speed traces, and the way the car behaves in the parts of the lap where aero is actually important.
The important word is useful. The MIRA wind-tunnel data described in the corpus are arranged by increasing peak downforce, beginning with cars that generated positive lift. That is a useful way to organize data, but it is not the same thing as ranking cars by lap time. Peak downforce is one axis. Drag is another. Track layout, speed range, yaw, tire condition, and mechanical grip decide whether the extra downforce becomes a lap-time gain or just a tax on the straights.
The practical rule
Use lift-to-drag as a filter before you fall in love with any aero change. If a change gives more downforce for a modest drag increase, it deserves testing. If it gives more downforce only by dragging the car down the straights, it has to prove itself in the fast sectors. If it reduces drag with little loss of high-speed grip, it may be the better race setup even if it looks less aggressive in the paddock. If the data are ambiguous, go back to the baseline and test again before you declare a winner.
This is not a replacement for lap time. It is a way to make lap-time testing less sloppy. A full lap is a blend of braking, corner entry, minimum speed, throttle application, gearing, traffic, tire state, driver confidence, and wind. Lift-to-drag gives you a way to separate the aero question from the noise. It says: for this configuration, in this speed range, on this sector mix, did the aerodynamic load earn its drag?
Why CD.A and CL.A matter more than bare coefficients
The MIRA data chunk makes a practical point that matters in the paddock. The useful wind-tunnel numbers were given as coefficient multiplied by frontal area, such as CD.A and CL.A, because those products are directly proportional to the actual forces at a chosen speed. That matters because the force is what the car feels. A bare coefficient can mislead when the frontal area estimate is approximate or when you are comparing bodywork packages that change the effective area. CD.A and CL.A let you work closer to the thing that matters: actual drag force and actual lift or downforce force.
For your decision process, that means you should write the test question in force language, not appearance language. Do not ask whether the wing angle looks serious. Ask whether the added CL.A, treated as downforce in your sign convention, is worth the added CD.A. Do not ask whether a bodywork part is tidy. Ask whether the drag change shows up in speed, coastdown, or simulation, and whether the downforce change shows up where the tires can use it.
Be careful with signs. Aero data can include positive lift and downforce. Some tables treat downforce as negative lift; some reports describe the magnitude of downforce. Before you compare two packages, make sure you know whether the larger useful number is more negative CL.A or a larger downforce magnitude. This is basic, but it prevents a very expensive kind of confusion: thinking you added grip when the data actually say you reduced lift less, or thinking one package is efficient because the sign convention was read backward.
The mechanism: drag taxes every speed-dependent gain
The corpus does not give a full equation lesson, and you do not need one for the setup choice. The practical mechanism is enough. At a chosen speed, CD.A and CL.A are directly proportional to the actual forces. More useful downforce can help the tires carry more load in fast corners, but more drag resists the car anywhere speed is high. That is why a downforce package can feel excellent in one corner and still lose the sector if the following straight is long enough. It is also why a trimmed package can feel a little lighter but win the lap if it preserves enough grip while improving speed where the car spends time under power.
The tire and suspension chunk adds the second half of the mechanism. The tire contact patches transmit the accelerations, braking, thrust, steering, and sensory information. Aero download is additive to mechanical grip, but mechanical grip remains the basis of the car. The same chunk warns against assuming the suspension is unimportant just because aero grip exists, and it gives a useful anchor: the apex speed of the average racing corner is less than 80 mph, where aero download is secondary to mechanical grip. For this lesson, that means you should not use lift-to-drag as a reason to ignore tires, balance, or chassis. It is a lens for aero tradeoffs, not a magic override for the rest of the car.
On a fast corner, extra downforce may let you carry more minimum speed or apply throttle with less correction. On a medium or slow corner, the same change may barely help because mechanical grip dominates. On the straight after either corner, the drag still has to be paid. Good lift-to-drag decisions start by identifying where the lap is actually aero-limited.
What counts as useful downforce
Useful downforce is downforce that changes what you can do with the car. It lets you brake later in a genuinely high-speed braking zone, turn in with less waiting, hold a tighter or faster arc, reduce steering correction, or open the throttle earlier because the car is more planted. A wind-tunnel value by itself is not yet useful downforce. It becomes useful when it appears in the part of the lap where the car is fast enough and the tires can convert the added load into speed.
The test is not whether the driver likes the feel. Feel matters, but feel is not the verdict. A high-drag package often feels reassuring because the car is calmer in fast places. That may be exactly what you need. It may also be a comfort blanket that costs speed. You should treat driver confidence as one data channel and compare it with sector times, end-of-straight speeds, and the specific corners you targeted.
For example, if you add rear wing and the car becomes calmer in a fast sweeper, the first question is whether that calmness lets you carry more speed or use the throttle sooner. The second question is whether the following straight loses more time than the sweeper gains. The third question is whether the balance change made other corners worse. Lift-to-drag keeps those questions connected.
Build a baseline before you test anything
The measuring-drag chunk gives one of the most important testing rules: return to the baseline setup periodically during the session, because conditions can drift and tire deterioration can change the baseline. That is not just a professional nicety. It is the difference between learning and fooling yourself.
Aero testing is vulnerable to false wins. Tires heat, age, and wear. Fuel burns off. Wind changes. The driver learns the corner. Traffic interrupts laps. A setup tested late in the session may look worse because the tires are gone, or better because you finally drove the corner correctly. If you only run baseline first and new package second, you cannot tell whether the aero changed the car or the session changed around you.
The minimum discipline is an A-B-A pattern. Run the baseline. Run the change. Return to baseline. If the baseline does not come back to roughly the same behavior and performance window, the comparison is contaminated. For a club racer with limited test time, this is sometimes frustrating. Do it anyway when the decision matters. A single clean repeat is worth more than many laps of unanchored guessing.
What to record in the baseline
Record the configuration, not just the lap time. Note wing angle, splitter setting, ride height if available, tire set, tire pressures, fuel state, ambient conditions, and any cooling or bodywork state that could affect drag. Then record the outcome channels: lap time, relevant sector times, terminal speed on the longest straight, speed at the end of key acceleration zones, minimum speed in the target fast corner, and the driver note in plain language.
The data logging chunk supports the practical value of systems that are installed, calibrated, and used to extract useful information for mechanics, engineers, and drivers. The key word for you is useful. A basic logger can be enough if it gives repeatable speed and sector information. A more elaborate system is only better if it is calibrated and if you know what question you are asking. Lift-to-drag testing does not require you to drown in channels. It requires you to connect the channels you have to the aero trade.
Start each test with a sentence. This package should be faster because it gives enough extra high-speed grip in these corners to overcome the drag on these straights. Or this package should be faster because it removes drag without losing meaningful grip in the fast corners. If you cannot say that sentence before the test, you are not testing. You are shopping.
Use sectors before whole laps
The measuring-drag chunk says indirect measurements of configuration changes on sector or lap times and speeds are very valuable and often all you really need to know. That is the right order for this lesson: sectors and speeds first, full lap second. Whole laps are important, but they smear the evidence. Sectors let you see where the trade happened.
Separate the lap into at least three buckets. The first bucket is the aero-gain zone: fast corners, fast braking entries, and places where the car is speed-sensitive and loaded. The second bucket is the drag-cost zone: long straights and high-speed acceleration zones. The third bucket is the neutral or mechanical zone: slower corners where mechanical grip, balance, and driver technique dominate. A good aero change should show its gain in the first bucket, show its cost in the second, and avoid creating confusion in the third.
If a higher-downforce package gains time only in slow corners, be suspicious. The gain may be driver confidence, tire state, or balance, not aero load. If it loses terminal speed but does not improve fast-corner speed, be even more suspicious. That is drag without evidence of useful downforce. If a trimmed package gains straight speed and loses only a tiny amount in the fast sector, it may be the better race choice even if it feels less planted.
Measure drag directly when the decision is close
Sometimes sector and lap data are enough. Sometimes they are not. The corpus describes several direct or semi-direct ways to measure drag. It notes that drag is the easier aerodynamic force to measure with surprisingly little investment, provided you have a long, straight, flat, smooth piece of road. It also describes more sophisticated methods using horizontal suspension loads or driveshaft strain, and a maximum-speed method when space, gearing, at-the-wheels horsepower, and frontal area figures are reliable. The most widely used practical method described is the coastdown technique.
The coastdown idea is simple in use even if the analysis can become technical. You run the car in a controlled state and observe how it decelerates when power is removed. More total resistance means the car slows more quickly. Used carefully, this gives you a way to compare configurations without needing a full wind tunnel. For lift-to-drag decisions, coastdown is especially useful when two packages have similar lap times but different straight speeds, or when you suspect a change added drag without showing enough corner gain.
There is a catch, and the corpus states it clearly: total drag force includes mechanical resistance as well as aerodynamic resistance. That means a sloppy coastdown test can lie. Tire pressure, tire temperature, wheel bearing condition, brake drag, driveline state, road slope, wind, and run direction can all contaminate the result. You cannot treat a single coastdown number as pure aero truth. You use it as one disciplined comparison, with the car and conditions held as constant as you can make them.
For a driver, the practical use is this: if a wing change produces a measurable increase in coastdown resistance, the fast-corner data must earn that cost. If it does not, trim it out. If a drag-reduction change improves coastdown and terminal speed while leaving fast-corner sector performance intact, it deserves attention. If coastdown improves but the car becomes unstable or slower in the high-speed sector, the saved drag was not free.
Look at the air, not just the part
The flow-visualization chunk makes a useful point for amateur aerodynamicists: being able to see what the air is doing around wings, spoilers, diffusers, cooling intakes, outlets, and other crucial areas can help you understand the car and point toward improvements. It also gives an example of wing twist being altered so flow remains attached across the span for longer, allowing more downforce before large-scale separation and stall.
This matters because lift-to-drag is not only a number you calculate after the fact. It is also a way of diagnosing why a change worked or failed. A wing or diffuser that is operating cleanly may add useful downforce for a reasonable drag cost. A part that is separated, stalled, or interfering with another flow path may add drag without adding proportional load. In the car, those two failures can feel similar at first because both may slow the straight. The difference is whether the fast-corner data show a real grip gain.
Do not assume that adding angle always improves the ratio. The wing-twist example points to a deeper idea: sometimes the efficient change is not simply more angle, more area, or more device. It is making the existing device work over more of its span or speed range before separation. For the driver making setup calls, that means a smaller, cleaner change can beat a larger, messier one. If more angle produces a big straight-speed loss and only a small fast-corner gain, the part may be past the useful point for that car and track.
Remember yaw
One bonded chunk is only a figure caption, but it is still a warning worth carrying: it refers to drag versus yaw angle for two configurations. Race cars do not spend the whole lap in perfect straight-ahead flow. In corners, crosswinds, traffic, and transient states, the car sees yaw. A package that looks efficient in straight-line thinking may carry a larger drag penalty when yawed, and a package that is stable in yaw may be worth more than its straight-line number suggests.
Do not overbuild a lesson from a caption. The corpus here does not give a full yaw-testing method. The practical takeaway is modest: if your data show a package with good straight speed but nervous or slow behavior in fast cornering, do not call it efficient too early. If you have access to yaw-aware data, use it. If you do not, use driver comments and fast-corner traces as warnings, not as proof.
Use simulation as a question generator, not a verdict machine
The performance-simulation chunks describe downforce and drag values versus lap time predicted by a simulation, then close with a warning that applies across simple and complex tools: whatever your budget, use the tools carefully and with common sense to improve understanding and performance. That is exactly how you should use simulation in lift-to-drag decisions.
A simulator is useful because it can ask what-if questions faster than you can test at the track. If the model says a high-downforce package should gain in one sector and lose on the straight, that helps you design the track test. If it says the drag cost overwhelms the downforce gain on a particular layout, that may save you from wasting a session. But the model is not the car. It depends on assumptions about speed range, grip, drag, downforce, power, and track segmentation. Use it to choose which configurations deserve real testing, then let the car prove or disprove the prediction.
The best simulator output for this lesson is not just a predicted lap time. It is a predicted pattern. Where should the gain happen? Where should the loss happen? How large must the fast-corner improvement be to overcome the straight loss? If your real data do not show that pattern, ask why before you accept the headline lap time.
Worked example: the MIRA-style data table
Imagine you have data for several configurations in the same style as the MIRA appendix: CD.A and CL.A values rather than bare coefficients, arranged from positive lift toward increasing peak downforce. You are tempted to choose the package with the largest peak downforce. Do not start there.
First, identify the configurations that are realistic for your car and rules. Then compare the change in useful lift or downforce product against the change in drag product. You are looking for packages that add meaningful downforce without a disproportionate drag increase. If two packages are close in downforce but one carries less CD.A, the lower-drag package is a serious candidate. If one package has much more downforce and much more drag, it is not rejected automatically, but it must match a track with enough fast-corner value to pay for the straight-line cost.
Second, map the candidates to your track. A layout with long straights and only moderate-speed corners will punish drag. A layout with sustained high-speed corners may reward load. A layout with many slow apexes may not let the extra downforce matter enough because mechanical grip dominates more of the lap. This is where the tire and suspension principle matters: aero download is additive, but it is not the foundation by itself.
Third, test in a way that can prove the pattern. If the high-downforce package is the right choice, you should see gains in the fast sectors that plausibly pay for any terminal-speed loss. If the lower-drag package is the right choice, you should see straight speed or acceleration improvement without a meaningful fast-sector penalty. If neither pattern appears, the table did not answer the track question. Go back to baseline and test again.
Worked example: the coastdown straight
Now imagine you are deciding whether to add rear-wing angle for a race weekend. The car feels better in a fast corner, but your end-of-straight speed is down. You do not know whether the lap time changed because of aero, driver adaptation, traffic, or tires. A coastdown comparison can help.
Choose a long, straight, flat, smooth road or a suitable test straight. Keep the car state as consistent as possible. Run the baseline configuration, then the added-angle configuration, then return to baseline. Because the coastdown result includes mechanical resistance as well as aero resistance, you keep tire pressures, temperatures, brakes, and driveline condition as consistent as the real world allows. If you can run in both directions to reduce wind or slope effects, do so. The exact analysis method can vary, but the decision logic stays simple.
If the added-angle setup slows more quickly in coastdown and also loses terminal speed, it has clearly increased resistance. That does not make it wrong. It means the fast-corner sector has to show a gain. If that sector does not improve, you have bought drag without earning downforce. If the sector improves but the full lap does not, you have learned that the track does not reward that amount of load. If the sector improves enough to overcome the straight loss, the higher-downforce setup is justified for that layout.
If the return-to-baseline run does not resemble the first baseline run, stop treating the comparison as clean. Tire deterioration and changing conditions can move the baseline. That is why the A-B-A structure matters more than the number of laps you managed to collect.
Worked example: simulation before a test day
Before the next event, you have three candidate packages: baseline, trimmed, and higher downforce. You do not have wind-tunnel time, but you have approximate drag and downforce deltas from previous testing or manufacturer data. A performance simulation can tell you what pattern to expect.
Run the model as a planning tool. For the trimmed package, the model should predict where speed increases and where cornering suffers, if it suffers. For the higher-downforce package, it should predict which fast corners improve and how much straight speed is sacrificed. You then take those predictions to the track as hypotheses, not conclusions.
At the event, you compare the actual sector traces to the predicted pattern. If the model expected the high-downforce setup to gain mostly in the fast sector but the real car gains in a slow sector instead, suspect driver adaptation, balance, tire state, or bad assumptions. If the model expected straight-speed loss and the data show it, the question is whether the fast-sector gain is large enough. Simulation earns its keep when it sharpens your test, not when it lets you skip the test.
Sub-skill: separating aero gain from driver confidence
A driver often feels a higher-downforce car as calmer. Calm can be valuable. It can also hide the fact that the car is slower. Your job is to separate confidence from speed. After each run, write the driver note in action language. Could you turn in earlier? Could you reduce steering correction? Could you reach full throttle sooner? Could you hold the same line with less lift? Then check whether the trace supports the note.
If the note says the car was planted but the minimum speed, throttle timing, and sector time did not improve, the feeling has not yet become performance. If the note says the car was nervous but the trimmed setup wins speed and gives away little in the fast sector, the driver may need adaptation rather than more wing. If the note and data agree, trust the pattern.
Sub-skill: recognizing drag that is masking a gain
Sometimes a downforce package really does improve the target corner, but the full lap does not show it because the drag cost appears somewhere else. This is why sibling lessons on sector trimming and masked gains matter. In this lesson, the key is to avoid throwing away the configuration before you know where it worked.
Look for a package that gains in a fast corner but loses later on the straight. That is not a failed test. It is a clear trade. Now the question is strategic. On this track, in this race format, with this traffic pattern, is the corner gain worth the speed loss? If the answer is no, trim it. If the answer is yes because the corner leads onto another important section or because stability lets you race wheel-to-wheel more safely, keep it with open eyes. Lift-to-drag does not make the decision for you. It makes the cost visible.
Sub-skill: knowing when the ratio is not enough
Lift-to-drag is a decision lens, not the only lens. A package can have a better ratio and still be wrong if it overheats the car, disrupts balance, stalls unpredictably, creates yaw sensitivity, violates the rules, or makes the car impossible to drive consistently. The bonded corpus supports several of those warnings indirectly: cooling intakes and outlets are crucial flow areas, flow attachment and stall matter, yaw affects drag, and tools must be used carefully.
For a driver, the operating rule is simple. Use L/D to screen candidates. Use sector and speed data to verify the trade. Use feel and repeatability to decide whether you can race it. Do not keep a package merely because it has a pretty ratio if the car becomes inconsistent or if the data only work in one clean lap and disappear when conditions change.
Calibration cues
You are improving at this skill when your aero notes become specific before they become emotional. Instead of saying the car had more grip, you can say the added wing was meant to help the fast right and the data showed a small minimum-speed gain there but a terminal-speed loss on the following straight. Instead of saying the trimmed setup was faster, you can say it gained speed in the drag-cost zone and did not give away enough in the aero-gain zone to matter.
Your data traces should start to show repeatable patterns. A good higher-downforce change shows up as better speed, throttle timing, or stability in the targeted fast sections, with a drag cost you can see and accept. A good lower-drag change shows up as improved straight speed or acceleration, with no major loss in the fast sections. A bad change shows cost without targeted gain, or gain that vanishes when you return to baseline.
Your testing habits should also change. You should stop making one-way comparisons. You should return to baseline during the session. You should stop judging aero parts by peak downforce alone. You should ask whether the data are from the same tire state and whether the result survived a repeat. Those habits matter more than owning expensive tools.
Common mistakes
The first mistake is downforce shopping. This is choosing the configuration with the most peak downforce because the number looks impressive. Good looks like choosing the package that gives the best useful load for the track, even if it is not the maximum-downforce package.
The second mistake is comparing bare coefficients without respecting area. The MIRA appendix used CD.A and CL.A because those products are directly proportional to the actual forces at a chosen speed and avoid relying on approximate frontal-area estimates. Good looks like comparing force-relevant products when you have them, or at least being honest about the limits of bare coefficient comparisons.
The third mistake is the one-way test. You run baseline, make a change, improve, and declare victory. Good looks like returning to baseline because tire deterioration and changing conditions can move the target while you are testing.
The fourth mistake is judging by full lap only. Full lap matters, but it hides where the trade occurred. Good looks like separating aero-gain sectors from drag-cost sectors, then deciding whether the trade fits the track.
The fifth mistake is treating coastdown as pure aero. The coastdown technique measures total drag force, and total drag includes mechanical resistance. Good looks like controlling the car state, repeating the baseline, and using coastdown as one piece of evidence rather than a magic number.
The sixth mistake is ignoring mechanical grip. Aero download is additive, but the tire and suspension still form the foundation of cornering power and balance. Good looks like asking whether the corner is fast enough for aero to dominate the decision, especially when many average corner apexes are below the range where aero is the primary grip source.
The seventh mistake is adding angle past the useful flow state. The flow-visualization chunk describes keeping flow attached longer to generate more downforce before separation and stall. Good looks like recognizing that an aero device can stop paying its way when the extra setting adds drag faster than it adds useful load.
The drill: the lift-to-drag decision card
At your next test day, run one focused lift-to-drag drill. Pick one aero variable only: rear-wing angle, splitter setting, a cooling exit state, or one bodywork option. Do not combine changes. Your goal is not to find the perfect setup in one day. Your goal is to prove that you can see the trade clearly.
Use a three-configuration plan if time allows: baseline, added-downforce direction, and trimmed direction. Warm up normally. Run three representative baseline laps. Run three laps in the added-downforce configuration. Return to baseline for two laps. Run three laps in the trimmed configuration. If time or tires are limited, drop the third configuration before you drop the return-to-baseline step.
For each run, fill out the same card. Record the configuration. Record the best clean sector in the aero-gain zone. Record end-of-straight speed or the closest speed channel you have. Record the target fast-corner minimum speed or throttle application point. Record one driver sentence about what the car allowed you to do. After the session, mark each configuration as earned, unearned, or contaminated.
Earned means the intended gain appeared in the target zone and the drag cost was acceptable. Unearned means the cost appeared without the targeted gain. Contaminated means the baseline moved, traffic interrupted the evidence, the tires changed too much, or the driver did not produce comparable laps. The success criterion is not picking the fastest setup. The success criterion is being able to explain why a setup won, lost, or needs another test.
When the principle breaks down
The lift-to-drag lens becomes weak when the corpus-supported evidence channels are missing or contaminated. If you do not have reliable speed, sector, or repeatable baseline data, you can still make a judgement, but you should label it as provisional. If tire deterioration is severe, if wind changes run to run, or if traffic ruins the relevant sectors, the comparison may not be worth much. If the car has a cooling or stability problem, the best L/D package may still be the wrong race package.
It also becomes weak when the track does not ask much of aero. If the important corners are slow and the straights are long, the lower-drag package may win even if the higher-downforce package feels better. If the track has sustained high-speed load and short straights, the opposite may be true. The ratio does not replace track context. It helps you ask the context question precisely.
Cross-references inside this module
Use the induced-drag lesson when the added load comes from wing angle or another device likely to increase induced drag. Use the visible-drag audit when the drag source is bodywork, openings, or exposed hardware you can inspect. Use the fastest-sector-mix lesson when the decision depends on whether one part of the lap is worth sacrificing for another. Use the masked-gain lesson when the car improves in the target corner but the full lap hides it with a loss elsewhere.
The lesson here is narrower. Before you argue about which part to add, ask whether the part improves the useful lift-to-drag trade. Before you trust a lap time, ask whether the sector pattern proves the trade. Before you keep a setup because it feels secure, ask whether the load earned its drag.
Worked example: the MIRA-style data table
Use CD.A and CL.A as the force-relevant comparison, not just the shape of the part or the peak downforce rank. A package with the largest peak downforce still has to justify its drag on the actual track. A lower-drag package with slightly less load may be the better choice if the track has long drag-cost zones or if the fast corners do not reward the extra load.
Worked example: the coastdown straight
Use a long, straight, flat, smooth road or test straight to compare resistance between baseline and changed configurations. Run baseline, change, then baseline again. Because coastdown measures total resistance, not pure aero alone, keep tire, brake, driveline, wind, and road conditions as consistent as possible. The added-downforce setup must show enough fast-sector gain to justify any measured resistance increase.
Worked example: simulation before a test day
Use performance simulation to predict the pattern of the trade before you spend track time. The useful output is not just predicted lap time; it is where the model says the gain and loss should occur. At the track, compare the real speed and sector traces to that pattern and treat mismatches as questions to investigate rather than as automatic proof.
Common mistakes
Common errors are choosing maximum peak downforce, comparing bare coefficients while ignoring area, making one-way tests without returning to baseline, judging by full lap instead of sector pattern, treating coastdown as pure aero, ignoring mechanical grip in slower corners, and adding angle past the point where attached flow and useful load are improving together. Good practice is to make the trade visible, repeat the baseline, and keep only changes that earn their drag.
Drill: the lift-to-drag decision card
At the next test day, choose one aero variable and run baseline, added-downforce direction, return-to-baseline, and trimmed direction if time allows. Use three representative laps for each main configuration and two laps for the baseline return. Record configuration, target fast-sector result, end-of-straight speed, target fast-corner speed or throttle cue, and one driver action note. Success means you can classify each setup as earned, unearned, or contaminated with evidence.
When this principle breaks down
Lift-to-drag is not enough when the evidence is contaminated, when tire deterioration moves the baseline, when cooling or stability overrides the ratio, or when the track does not contain enough aero-sensitive speed to reward the added load. In those cases, keep the judgement provisional and use the ratio as a screening tool rather than a verdict.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | Competition Car Aerodynamics 3rd Edition McBeath Simon | c87c89fe-58c4-8968-6248-4a307e39f9e2 | 346 | 1 | uio_books_raw_v1 |
| 2 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 4bbf9579-1422-c928-32d2-88746f790746 | 478 | 1 | uio_books_raw_v1 |
| 3 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 9f0edfc1-9e8c-3a96-a48d-b0d658513db3 | 385 | 1 | uio_books_raw_v1 |
| 4 | Racing Chassis and Suspension Design Carroll Smith | 148524fa-62af-201e-6dff-3b729c84477a | 8 | 1 | uio_books_raw_v1 |
| 5 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 576d96a1-00b7-66dd-f5b1-e33666cc457f | 334 | 1 | uio_books_raw_v1 |
| 6 | Competition Car Aerodynamics 3rd Edition McBeath Simon | cd94958f-1042-ceff-8d99-06fa06ac633b | 504 | 1 | uio_books_raw_v1 |
| 7 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 5f8f0fe1-ae71-b849-97d2-d63df40bb83b | 423 | 1 | uio_books_raw_v1 |