Keep lateral stability in the aero brief
Generated from
content/lms/race-aerodynamics/02-shape-the-whole-cars-airflow/05-keep-lateral-stability-in-the-brief.md; edit the source file, not this page.
Source path: content/lms/race-aerodynamics/02-shape-the-whole-cars-airflow/05-keep-lateral-stability-in-the-brief.md
Course: Engineer downforce you can actually use
Module: Shape the whole car's airflow
Estimated duration: 65 minutes
The skill: brief the car for stability, not just load
This lesson is about a habit that separates useful aerodynamic development from parts that only look fast. You are not trying to write a brief that asks for the largest possible wing, the lowest possible lift number, or the most impressive straight-ahead pressure map. You are trying to brief a car that stays laterally trustworthy when it is doing the work that matters: braking from speed, turning with yaw on the body, living through pitch and ride-height change, accelerating off the corner, and sometimes doing all of that in disturbed air behind another car.
The practical rule is simple. Any aerodynamic change that adds load must also be judged by what it does to front-to-rear balance while the car is cornering. If the load arrives mostly at one end of the car, or disappears from one end during yaw, pitch, ride-height change, wing stall, or traffic wake, the driver does not receive stability. The driver receives a speed-sensitive handling problem. At intermediate level, that is the important shift in thinking: you stop asking whether the part makes downforce in isolation and start asking whether the whole car remains predictable as the airflow and vehicle attitude change.
Aerodynamics matter most once speed is high enough for the air loads to be felt. Ross Bentley places the meaningful driver threshold around the higher-speed range, with only very sensitive drivers feeling aero strongly below roughly 60 mph. That does not mean aero is irrelevant below that speed in every car. It means your first useful driver evidence usually appears in the faster parts of the track: high-speed entry, apex, and exit speeds, and the way the car changes character as speed rises. A car that pushes in slow corners because of mechanical setup can become loose in fast corners if the front gains proportionally more aero grip than the rear. The same car can become lazy and push at speed if the rear gains proportionally more load than the front. Your brief has to protect against both errors.
The lesson sits inside whole-car aero. Other lessons in this module handle treating the body as one aero system, mapping pressure into vertical load, protecting the air before it reaches a device, and respecting wheel and ground interference. Here the narrower job is lateral stability. You are learning how to specify, test, and interpret aerodynamic behavior so the car does not surprise you when the body is at yaw, when the platform moves, or when another car changes the air you drive through.
Principle: the stable aero car keeps balance as attitude changes
Aerodynamic stability is not the same thing as total downforce. Total downforce tells you something about how much vertical load the air can add. Lateral stability tells you whether that load arrives in a way that keeps the front and rear tires working in proportion while the car is turning. Carl Lopez makes the driver-feedback version of this very direct: too much front relative to rear creates high-speed oversteer, while too much rear relative to front creates high-speed understeer. That is the core mechanism behind the brief. You want the aerodynamic loading to support the tires in proportion to the job they are doing, not load one axle so heavily that the other axle becomes the limiting end.
For stability, a common starting preference is less rear lift than front lift, or stated another way, more rear downforce than front downforce. Julian Edgar gives that as a typical stability target while also warning that the rest of the car matters. An understeering front-wheel-drive car may need more front downforce to bring the balance back toward usefulness. That caveat matters. Stability is not a one-size number. It is a balance target tied to the car, tires, speed range, and corner type. The default preference for rear security is a starting point, not permission to make the front ineffective.
The reason straight-line aero numbers are not enough is that the car is rarely in the straight-ahead test condition when the driver needs confidence. Simon McBeath describes how high-level teams test cars at yaw angles representative of cornering because straight-ahead and cornering conditions produce significant aerodynamic differences. Straight-ahead work is still useful. It helps with drag, basic mapping, and the braking phase from high speed. But a race car spends a large share of lap time in corners, so the brief has to include cornering attitudes. If your brief only asks what the part does in zero-yaw flow, it has already missed the main stability question.
The second reason is that the car is not a static model on track. McBeath emphasizes that downforce and balance can be strongly affected by yaw, pitch, rake change, and ride height, and that those attitudes are transient in the real car. Airflow around the car is also unsteady. Every transition from straight running to braking to cornering to acceleration can move the aerodynamic balance. This is why a part that feels fine on one phase of the corner can be a problem in another. The brief has to name the phase where stability matters, because entry stability, mid-corner support, and exit confidence are not automatically the same result.
A useful stability brief therefore has three parts. First, it names the speed range where aero should be judged. Second, it names the corner phases where balance must be protected. Third, it defines the evidence you will use to accept or reject the change. That evidence can be basic: lap times, sector times, high-speed corner entry speed, apex speed, exit speed, straight-line speed, and disciplined driver feedback. You do not need a professional wind tunnel to start doing better work. You do need to stop making vague changes and then calling the result better because the last lap happened to be quicker.
Mechanism: how instability gets built into an aero package
Most lateral instability from aero comes from a mismatch between where the load is made and when the load is available. If a front device adds load strongly as speed rises, but the rear of the car does not gain matching support, the front tires can become more secure than the rear tires in the fastest corners. The driver feels this as a car that is acceptable or even understeery in slow corners, then starts to rotate more than expected as speed rises. That is not the same problem as ordinary low-speed rotation from brake release or mechanical balance. The speed sensitivity is the clue.
The opposite mismatch is also common. If a rear wing or rear body change adds too much rear security without enough front authority, the car becomes stable in the comforting but slow sense: it refuses to point in the fast stuff. The driver turns the wheel, waits, adds more steering, and bleeds speed while the front tires run out of authority. This can look safe because the rear is calm, but it still fails the stability brief if the car cannot place itself accurately at speed. A car that will not respond predictably is not a stable tool. It is merely reluctant.
A wing can add another failure path: stall. Lopez explains that a wing cannot take unlimited angle of attack. At a certain angle, the airflow becomes turbulent, the wing loses some downforce, and drag rises heavily. For the driver, the dangerous part is not only the extra drag. It is the possibility that the load you were counting on is no longer there in the phase of the corner where you need it. If the rear wing is being used to calm high-speed entry, a stalled wing may give you a slower straight and a less secure rear. That is the worst trade: drag without dependable lateral stability.
Ride height and rake create a different kind of mismatch. Edgar points out that you can measure front and rear ride height and experiment with ride-height changes while looking for reduced lift or increased downforce. McBeath goes further and warns that aerodynamic balance changes with ride height and pitch, and that the real car is constantly changing those attitudes. A part that makes good static load can still behave poorly if it is too sensitive to platform movement. If the balance moves suddenly when the nose dives under braking or the rear squats on exit, the driver will call it a handling problem. The aero brief should have predicted that risk.
Yaw adds the cornering version of the same issue. At small yaw angles, the airflow does not meet the car the same way it does straight ahead. Devices see changed inflow. Underbody flow changes. Side surfaces and openings become more important. McBeath notes that straight-ahead testing is good for basic mapping and braking knowledge, but cornering attitudes deserve proportional attention because that is where lap time is spent. The brief must therefore ask whether the part keeps balance during representative yaw, not merely whether it adds load in a clean straight line.
Traffic makes the stability problem relational. When cars run close together, McBeath states that aerodynamic interactions are unavoidable. The following car can lose downforce and grip in the wake of the car ahead, and the mitigation in one tested configuration was to offset laterally, specifically to the left for a left-hand-drive following driver in that case. Do not turn that into a universal law. The lesson is broader: if you race or run in groups, lateral stability is not only a solo-car property. Your car must be understandable when the air is not clean, and your driver tools include line placement as well as hardware.
Technique: write the stability brief before you test parts
A weak brief says to add front downforce, add rear wing, reduce lift, or improve aero balance. Those phrases are too broad to protect the driver. A useful brief tells the fabricator, engineer, crew chief, or your own notebook what the car must do in speed-sensitive handling terms. It should connect the desired aero result to a corner phase and a measurement.
Start with the car you have. Note whether the baseline car understeers or oversteers in low-speed corners, fast entries, fast apexes, and fast exits. The reason for separating low and high speed is that suspension-induced balance and aero-induced balance can point in different directions. Bentley gives the example pattern: a car can understeer at lower speeds because of suspension design, then oversteer at higher speeds because bodywork or wing effects change the loading. If you collapse all of that into one handling word, you will brief the wrong fix.
Next, identify the corners where aero can be judged. McBeath lists practical track evidence such as lap times, sector times, high-speed corner entry, apex and exit speeds, and straight-line speeds. Use those categories. Your stability brief should say which fast corners count as the acceptance test. If the part is meant to improve a fast sweeper, do not judge it mainly by a slow hairpin. If the part is meant to add rear security on high-speed entry, do not declare success just because the car puts power down better in a medium-speed exit.
Then name the phase. Entry stability asks whether the car remains calm as speed is high and the platform may be pitching forward under braking or initial turn-in. Mid-corner stability asks whether the car holds a consistent attitude with yaw on the body. Exit stability asks whether balance remains manageable as speed changes, steering unwinds, and the platform moves again. McBeath's point that balance changes from straight running to braking to cornering to acceleration is exactly why the phase belongs in the brief. If you do not name it, you cannot know whether the test result matches the original need.
After that, set the balance guardrails. You are not writing a setup sheet for every car in the paddock. You are writing the minimum behavior your car must keep. A rear-wing change might have a guardrail that the car must not gain high-speed understeer at the fast apex beyond what the driver can trim with normal steering. A front splitter change might have a guardrail that the car must not become nervous in high-speed entry as speed rises. A diffuser or underbody change might have a guardrail that the car must not become platform-sensitive when ride height changes. Each of those guardrails traces to the same mechanism: front and rear load must remain useful and proportional in the phase being tested.
Finally, define the evidence. For an amateur or club-level program, good evidence can be disciplined and still simple. Use a baseline run, make only the aero change, run the same number of laps, capture lap and sector times, look at fast-corner entry, apex, and exit speed if you have logging, and write driver feedback immediately after the run. McBeath cites Carroll Smith's practical method of comparing two wings over five-lap runs, changing only the wing configuration, averaging lap times, and discarding abnormal highs and lows. The discipline matters more than the sophistication. If you change the wing, tire pressure, brake bias, and driving line at the same time, you do not have an aero test. You have a story you will be tempted to believe.
Sub-skill 1: separate mechanical balance from aerodynamic balance
The first sub-skill is diagnostic. You need to tell whether the balance problem is mainly mechanical, mainly aerodynamic, or a combination. You do this by comparing low-speed and high-speed behavior, then checking whether the handling change grows with speed. Bentley's distinction is the anchor: low-speed balance can come from suspension design, while higher-speed balance can be changed by bodywork and wings.
In practice, write four observations after a session. What does the car do in the slowest corners? What does it do in medium corners? What does it do in the fastest corner entries? What does it do at fast apex and exit? If the answer is the same everywhere, you may be looking at a general balance issue. If the answer changes with speed, aero becomes more suspect. If the car pushes at 45 mph and rotates too freely at 95 mph, do not ask for a generic understeer fix. You need to protect rear aero support or reduce excessive front aero authority at the speed where the problem appears.
This sub-skill protects you from using aero to hide a mechanical problem and from using suspension to chase an aero problem. McBeath notes that useful aero testing works best with an optimized mechanical setup, because then aero configuration changes can be interpreted more cleanly. That does not mean your car has to be perfect before you learn anything. It means you should not pretend the data is cleaner than it is. If the mechanical platform is changing at the same time as the aero package, write that uncertainty down and reduce the size of your conclusion.
Sub-skill 2: think in proportional load, not favorite axle
The second sub-skill is resisting axle bias. Drivers often ask for more front because the car will not turn, or more rear because the car feels nervous. Those requests may be correct, but they are incomplete. Lopez's balance rule is that front and rear tires need to gain load proportionately. Too much front relative to rear creates high-speed oversteer. Too much rear relative to front creates high-speed understeer. So the brief should not worship one axle. It should define the relationship you need.
A useful sentence in your notebook is: what end of the car becomes limiting as speed rises? If the rear becomes limiting, more front load may make the problem worse even if it helps turn-in. If the front becomes limiting, more rear wing may make the problem worse even if it makes the driver feel safer on entry. Stability is the controlled relationship between the ends, not the maximum number at either end.
This is where the rear-stability default needs judgment. Edgar's general guidance that stability typically wants less rear lift or more rear downforce than front downforce is helpful, especially for keeping the rear planted. But he also notes that an understeering front-wheel-drive car can benefit from increased front downforce. The correct intermediate habit is to treat rear security as the default concern at high speed, then check it against the actual car's balance. A front-heavy understeering car may need front authority. A nervous rear-drive car may need rear support. The brief should say which problem you are solving.
Sub-skill 3: include yaw without turning the test into theory theater
The third sub-skill is bringing yaw into the brief in a practical way. You do not need to calculate every side-slip angle to think correctly. You need to stop assuming that straight-ahead data answers the cornering question. McBeath explains that Formula 1 teams test at yaw angles that represent cornering because performance differs significantly from straight running. The intermediate lesson is not that you need a Formula 1 tunnel. It is that your track test must include the fast corners where the body is actually yawed.
A simple yaw-aware brief names the corners that matter and says what must remain stable through them. For example, a front device might be accepted only if the car gains fast-apex speed without adding entry oversteer. A rear device might be accepted only if it calms entry without creating fast-midcorner understeer. A body-side or underbody change might be accepted only if the driver feedback remains consistent from turn-in through steady-state cornering. The point is to judge the part while the car is not straight.
Do not overreach the evidence. If all you have is lap time and feel, you can still learn, but you should keep the conclusion modest. If you have sector times and speed traces, you can separate where the gain or loss happens. If you have ride-height or pressure data, you can go deeper. The key is that yaw becomes part of the acceptance condition, not an afterthought once the part is already built.
Sub-skill 4: protect the platform window
The fourth sub-skill is platform awareness. Aero devices do not work on an imaginary rigid car. The real car pitches, rolls, changes ride height, and changes rake. McBeath warns that aero balance can change with pitch, rake, and ride height, and that real track attitude is transient. Edgar recommends measuring front and rear ride height and experimenting with front and rear ride heights while looking for reduced lift or increased downforce. Put those ideas together and you get a practical rule: a stability brief should include the platform range where the part has to behave.
For a club car, that might be as basic as measuring static ride heights before and after the test, noting whether the car rubs, scrapes, or changes attitude under braking, and paying attention to whether the handling problem appears only in transitions. For a more developed car, it might include ride-height sensors, damper position, or pressure measurement. Either way, the driver language stays the same. If the car is stable only when perfectly settled but nervous during brake release, the brief has not been met. If the car is secure only at one ride height but loses balance when fuel load or bumps change the platform, the brief needs to be tightened.
This sub-skill also keeps you honest about underbody and diffuser work. Edgar's example of testing diffuser strakes shows that real hardware can work but be impractical if it is too deep and scrapes, while shorter replacements may be more usable but less effective. Stability is not only what the part does in clean conditions. It includes whether the part can keep working in the real ride-height envelope of the car.
Sub-skill 5: avoid stalled-wing confidence
The fifth sub-skill is knowing when a wing is no longer giving the kind of stability you think it is. Lopez's stall explanation matters because a stalled wing can cost downforce while adding heavy drag. Edgar's testing advice gives you practical tools: use pitot testing to find freestream airflow above the car, optimize wing angle by measuring rear ride height, and consider throttle-stop drag testing or tufting the wing to see whether the drag and downforce trade is sensible.
In the brief, do not simply say to increase wing angle until the driver likes the rear. Say the wing must add rear support without evidence of stall, without an unacceptable straight-line speed loss, and without turning fast mid-corner balance into understeer. If you have only driver feedback, the warning signs are a car that feels safer but is slower everywhere, loses straight speed heavily, or needs more steering in fast corners. If you have data, compare straight-line speed, fast-corner speed, and sector times. Drag that buys real corner stability may be worth it at one circuit. Drag that only hides nervousness while slowing the straights and front-limiting the fast corners is not.
Sub-skill 6: include traffic if you race in traffic
The sixth sub-skill is remembering that lateral stability can change behind another car. McBeath's close-running case studies show that competition cars interact aerodynamically when they run close together. For the following car, downforce and grip can be reduced, and the tested mitigation was a lateral offset to the left in cars with the relevant configuration. The specific left-side result depended on the tested cars, including their asymmetries and left-hand-drive visibility. Do not copy it blindly. Use it as proof that traffic belongs in the brief.
If your car is only used for solo time trial runs, traffic wake may be a secondary requirement. If you race, instruct, or run dense HPDE groups, it is part of the job. The brief should ask whether the car remains readable when following, especially in fast braking and turn-in zones where wake can take away load. The driver technique side is to experiment with lateral offset when safe and legal, because a small change in placement can change both the air hitting the car and the sight picture. The engineering side is to avoid a package that only feels good in clean air and becomes vague whenever the nose is in another car's wake.
Feedback: say where and how, not just understeer or oversteer
Lopez warns that vague feedback is not useful when a crew is trying to fix the car. The intermediate driver needs to describe where and how the behavior occurs. A stability brief lives or dies on feedback quality. Do not report that the car has understeer unless you also say whether it is entry, mid-corner, or exit; whether it grows with speed; whether it happens in clean air or traffic; and whether it arrives with platform movement.
Good feedback sounds like a diagnosis in time order. On fast entry, the rear is calmer with the new wing, but from apex to exit the front is lazier and I need more steering. Or: the splitter helps initial response in the fast corner, but the rear feels lighter as speed rises and I am delaying throttle. Or: solo laps are stable, but when following another car into the high-speed braking zone the front washes and the car no longer gives the same turn-in. Those statements give the brief something to act on.
The best feedback also separates confidence from speed. A car can feel calmer and be slower. A car can feel more alive and be faster but less forgiving. Use the data categories McBeath lists to keep yourself honest: lap times, sector times, high-speed corner entry, apex and exit speed, and straight-line speed. Then add immediate driver notes. Data without driver context may miss confidence and recoverability. Driver feeling without data may reward whatever setup happened to come last.
Testing method: make one change, then make yourself prove it
A disciplined stability test is simple to describe and hard to execute because drivers are competitive. Lopez points out that a driver left alone for laps will naturally try to go faster, which can skew results toward later changes. That is why the test procedure matters. You are not doing open practice. You are doing a comparison.
Use a baseline setup first. Run enough laps to bring the driver and tires into the same working range you expect for the comparison. Record the conditions, including wind if it is noticeable, because McBeath notes that outside testing is vulnerable to environmental fluctuations. If you can choose conditions, still or near-still air is better for drag and aero comparison, and opposite-direction runs can help smooth some road-test variation where that kind of test is possible. On a racetrack, you may not have that option, so you write the condition down and return to baseline during the session.
Then change only the aero configuration being tested. Carroll Smith's wing-comparison method, as reported by McBeath, used five-lap runs, changed only the wing configuration, averaged times, and discarded abnormal laps. That is a strong model for club-level aero work. Five laps is long enough to get repeated evidence but short enough that tires and driver adaptation do not completely bury the comparison. Returning to baseline periodically is crucial because weather, track state, and tire deterioration can move the target while you are testing.
After each run, write driver feedback before looking for a story in the data. Use the same format every time: entry, apex, exit, straight speed, traffic or clean air, and confidence. Then compare the data. A good aero stability change should show its benefit where the brief said it would. If the part was meant to improve fast entry stability, look for improved or more repeatable entry speed and driver confidence without a penalty that overwhelms the lap elsewhere. If the part was meant to reduce high-speed understeer, look for better fast-apex speed or reduced steering demand without making the rear nervous. If the gain only appears in slow corners, the test did not prove the aero claim.
Decision rules: accept, revise, or revert
The hardest discipline in aero development is reverting a part that almost works. McBeath's research-and-development section encourages experimentation but also warns against being too proud to return to the old setup. For this lesson, that becomes a decision rule. If a change makes the car faster but less recoverable in the fast phase named by the brief, revise it. If it makes the car calmer but slower everywhere that matters, revise it. If it improves the target corner but creates a larger problem in another high-speed phase, revise it. If the evidence is confused because conditions changed, go back to baseline and repeat before drawing a conclusion.
Accept the change only when the evidence and feedback agree with the brief. You do not need every metric to improve. Aero is always a compromise between downforce and drag, and Bentley emphasizes that increased downforce usually brings increased drag, with a compromise between cornering speed and straight-line speed. A stability change can be correct even if it costs a little straight speed, provided the cornering gain and driver confidence produce the better lap or race outcome. But do not accept drag just because the car feels planted. The stability brief is not a comfort request. It is a performance and control request.
Revise the change when the direction is right but the balance is wrong. A rear wing that helps entry but adds too much fast understeer may need less angle, better airflow, a different height, or a matching front change. A front device that helps response but makes the rear light may need rear support or a smaller front step. A diffuser change that works only at one ride height may need platform work or a less sensitive geometry. The exact hardware answer belongs to the rest of the aero system. Your job here is to keep the stability requirement visible so the solution does not become a single-number chase.
Revert when the part creates a problem you cannot explain or control. McBeath's reminder that there are many blind alleys in motorsport is practical, not pessimistic. A part that gives inconsistent balance in yaw, changes too sharply with pitch, appears to stall, or only works in clean air when you need it in traffic should not be defended because it took effort to build. The old setup is a valid control, and going back to it is part of serious testing.
What improvement feels like
When you are improving lateral aero stability, the car does not necessarily feel dramatic. Often it feels quieter in the specific place where it used to ask for a correction. On high-speed entry, you release the brake or start steering and the rear stays in the conversation instead of stepping outside it. At fast apex, the car holds the chosen attitude without asking for extra steering or a lift. On exit, the balance remains legible as speed and platform attitude change. In traffic, the car may still lose grip, but the loss is more predictable and you know whether a lateral offset helps.
The data version is also specific. The gain should appear in fast-corner entry, apex, or exit speed, in sector time that contains the target corner, or in repeatability across laps. Straight-line speed should be checked because drag can consume power at high speed and limit acceleration. Lap time alone is not enough because a part can gain a fast corner and lose a straight, or feel stable while being slower. Use lap time as the outcome, not the whole diagnosis.
The instructor version of the cue is this: the car lets you place it with fewer emergency corrections at the speed where aero matters. That does not mean fewer steering inputs everywhere. It means fewer surprise inputs caused by the aero balance moving underneath you. If the car is still busy because you are driving harder but the balance is consistent and the data supports it, the brief may be working. If the car is calmer because it refuses to rotate or because drag has slowed the entire lap, the brief has not been proven.
Cross-references inside this module
Use the pressure-map lesson when you need to understand how a pressure change becomes vertical load at one end of the car. Use the whole-body lesson when a local device changes flow somewhere else and the balance result surprises you. Use the protect-the-air lesson when a wing or diffuser is not seeing clean enough inflow to produce stable load. Use the wheel-and-ground-interference lesson when the problem changes with ride height, yaw, or wheel wake. This lesson depends on all of those ideas, but its acceptance question is narrower: does the package keep the car laterally stable while the car is actually being driven.
The brief template
Before your next aero change, write the brief in this order. First, state the current behavior by speed and phase. Second, state the target behavior by speed and phase. Third, state the guardrail that must not be violated. Fourth, state the test evidence. Fifth, state the revert condition.
For example, a useful brief for a rear-wing change might say that the current car is nervous on fast entry but acceptable at low speed, the target is more rear confidence above roughly 60 mph on entry and fast apex, the guardrail is no new fast-midcorner understeer or major straight-speed loss, the evidence is five-lap baseline and test runs with fast-corner entry and apex speed plus driver notes, and the revert condition is any sign that the wing adds drag without repeatable target-corner gain. A useful brief for a front device might say that the current car is lazy at high-speed apex, the target is more front authority there, the guardrail is no speed-sensitive rear instability on entry, the evidence is sector and fast-apex speed, and the revert condition is rear nervousness that grows with speed.
That is the skill. You are not promising that one brief will find the perfect setup. You are making sure every aero experiment has to answer the lateral-stability question before it earns a place on the car.
Worked example: sports-prototype yaw versus straight-ahead confidence
Imagine a sports prototype that looks excellent in straight-ahead mapping. Drag is acceptable, total downforce is improved, and the braking phase from high speed looks promising. If the brief stops there, it is incomplete. McBeath describes why high-level teams test at yaw angles representative of cornering: performance differs significantly between straight-ahead and cornering conditions, and much of the lap is spent in corners.
The stability version of the brief would add a yaw requirement. The part is accepted only if the car keeps predictable balance in the fast corners where the body is at small yaw. The driver should compare fast-corner entry, apex, and exit speed against the baseline, then describe whether the balance changes as the car turns. If the car gains straight-line or braking performance but becomes nervous at fast apex, the package is not laterally stable enough for the stated job. If it gains fast-apex speed without creating entry oversteer or exit vagueness, the yaw-aware part of the brief is being met.
This example also shows why the straight-ahead result is still useful. McBeath notes that straight-ahead testing supports basic mapping, drag optimization, and high-speed braking knowledge. The error is not using straight-ahead data. The error is treating it as the whole answer when the car's most important stability work happens while cornering.
Worked example: the Carroll Smith wing comparison as a stability test
McBeath summarizes a practical wing-comparison test from Carroll Smith: two wing configurations, five laps each, only the wing changed, average lap times recorded, and abnormal highs or lows discarded. Turn that into a lateral-stability test by adding phase-specific driver feedback and fast-corner speed review.
Run the baseline wing for five laps and record the target fast corner's entry, apex, and exit behavior. Then run the alternate wing for five laps with no other setup changes. Do not chase lap time by changing your braking point every lap. Hold the procedure steady enough that the wing has to prove itself. After each run, write whether the car changed on entry, at apex, on exit, and on the straight. Then compare sectors and straight-line speed.
A wing that adds rear confidence on entry but costs a large amount of straight speed and makes the car push at fast apex may not pass the brief. A wing that slightly costs straight speed but gives repeatable fast-corner speed and a calmer rear in the target phase may be worth keeping. A result that changes every run because tires or track conditions moved is not a conclusion. McBeath's advice to return to baseline periodically is the protection against fooling yourself.
Worked example: following another car in disturbed air
McBeath's close-running case studies show that competition cars interact aerodynamically when they run near each other. For the following driver, that means downforce and grip can change because the car ahead changes the air. In one tested configuration, the practical mitigation was a lateral offset to the left, which also helped the view from a left-hand-drive position. The specific direction depended on the cars tested, including asymmetry such as an open driver's window and underbody component layout, so do not turn the left offset into a universal rule.
The lesson for the brief is that a race car should not be judged only in clean air if it must race in traffic. Add a traffic condition to the stability requirement. The car should remain readable when following into a fast braking or turn-in zone, and the driver should know whether a safe lateral offset improves both air and sightline. If the car is excellent alone but vague whenever it follows, the aero package may still be fast for qualifying and poor for racing. That distinction belongs in the brief.
Worked example: rear wing height, angle, and stall on a track car
Edgar's testing advice gives a practical rear-wing workflow. Use pitot-tube testing to determine how high the wing must be to reach freestream airflow, optimize wing angle by measuring rear ride height, and consider tufting or throttle-stop drag testing to understand whether the wing is creating useful downforce or acting like an inefficient spoiler. Lopez's wing-stall explanation tells you why this matters: at too much angle of attack, the flow becomes turbulent, the wing loses some downforce, and drag rises heavily.
For lateral stability, the brief should not say to add wing angle until the rear feels safe. It should say the rear wing must add rear support in the target fast phase without evidence that the angle has pushed it into stall and without creating high-speed understeer that costs the fast corner. If the driver reports more rear calm but the data shows slower straights and no fast-corner gain, the angle may be buying comfort with drag rather than stability with performance. If tufts show poor flow or ride-height evidence stops improving, the next step is not automatically more angle. It may be better airflow, different height, less angle, or a broader whole-car change.
Drill: the five-lap lateral-stability brief test
At your next test day or HPDE session where safe solo laps are available, run this drill around one aero change or one simulated aero balance setting. The count is three five-lap runs: baseline, change, baseline return. The duration is one session if the event format allows it, or two sessions if you need a cooldown and a careful adjustment period. The success criterion is not a personal best. The success criterion is a written conclusion that names the target phase, the fast-corner evidence, the straight-speed effect, and whether the car should keep, revise, or revert the change.
Before the session, choose one high-speed corner where aero should matter and one lower-speed corner that helps you separate mechanical balance. Write the baseline behavior before touching the car. Then run five laps on the baseline configuration. Drive consistently rather than heroically. Record lap time, sector time if available, fast-corner entry, apex and exit speed if logged, straight-line speed if available, and immediate feedback for entry, apex, exit, and confidence.
Make only the planned aero change. Run the same five-lap structure. If a lap is clearly abnormal because of traffic, a mistake, or a flag, mark it instead of letting it dominate the average. Then return to the baseline and run five more laps. This last step is what protects you from tire deterioration, changing wind, changing track condition, or driver adaptation. McBeath emphasizes that returning to baseline is crucial when conditions may change.
After the drill, write one decision sentence. Keep the change if it improves or stabilizes the target high-speed phase without violating the guardrail. Revise it if the direction is useful but the balance or drag cost is wrong. Revert it if the car becomes less predictable, stalls the device, loses too much straight speed for the corner gain, or produces evidence you cannot explain. The discipline is the lesson.
Common mistakes
The first mistake is the straight-line-only brief. The part looks good in clean, straight flow, so the team assumes it will help the driver. What good looks like is a brief that includes the fast cornering attitude where the car is actually yawed and asks whether the balance remains predictable there.
The second mistake is peak-downforce chasing. The driver asks for the biggest load number or the most wing angle without asking where the load arrives. What good looks like is proportional front-to-rear loading that supports the target phase. Too much front relative to rear risks high-speed oversteer. Too much rear relative to front risks high-speed understeer.
The third mistake is stalled-wing confidence. The car feels more planted because the wing angle is aggressive, but the wing may be adding drag, losing clean downforce, or making the car front-limited at speed. What good looks like is checking wing height, angle, rear ride-height response, straight speed, tufts or drag testing where available, and fast-corner speed.
The fourth mistake is using one handling word. Saying only understeer or oversteer does not tell anyone where the problem happens. What good looks like is phase-specific feedback: entry, apex, exit, speed range, clean air or traffic, and whether the problem grows with speed.
The fifth mistake is changing too much at once. If you change wing angle, tire pressure, ride height, and driving approach together, you cannot credit or blame the aero change. What good looks like is one change, repeated laps, abnormal laps marked, and a baseline return.
The sixth mistake is ignoring platform sensitivity. A part may work at one static ride height but behave differently when the car pitches, changes rake, or moves through bumps. What good looks like is measuring ride height where possible and treating transition behavior as part of the acceptance test.
The seventh mistake is pretending traffic is separate from aero. In racing, the following car lives in disturbed air, and McBeath's case studies show that close-running interactions are unavoidable. What good looks like is testing or at least deliberately evaluating the car in traffic conditions and teaching the driver safe lateral placement options when wake reduces grip.
When this principle breaks down
The lateral-stability brief does not replace ordinary mechanical setup. Below the speed where aero is meaningful for your car, suspension, tires, alignment, differential behavior, and driving technique may dominate. Bentley's threshold guidance is a reminder to avoid blaming aero for every slow-corner balance problem. If the issue exists at parking-lot speed, the aero brief is probably not the first tool.
The principle also becomes harder to prove when conditions are moving. Wind, tire deterioration, track evolution, traffic, and driver adaptation can all distort the comparison. McBeath's testing sections do not promise perfect certainty; they recommend disciplined methods, baseline returns, and careful statistics because outdoor testing is noisy. When the evidence is noisy, do not force a confident conclusion. Repeat the baseline, narrow the variable list, and make the next test cleaner.
Finally, the rear-stability default is not universal. Edgar notes that many cars want less rear lift or more rear downforce for stability, but an understeering front-wheel-drive car can benefit from increased front downforce. The correct expert habit is to brief the balance the car needs, not the balance a different car needed.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | Competition Car Aerodynamics 3rd Edition McBeath Simon | da0eb061-4403-af2d-783d-5b7d9ae16326 | 476 | 1 | uio_books_raw_v1 |
| 2 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 4adf8cb4-89c7-1b45-bd4d-9bb03634ecf3 | 345 | 1 | uio_books_raw_v1 |
| 3 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 90b5a640-d9b2-b0ef-2f6e-f9a0dadce5aa | 411 | 1 | uio_books_raw_v1 |
| 4 | Ultimate Speed Secrets - Ross Bentley | c53beeb6-27b1-14da-5fe6-a41c50b97409 | 98 | 1 | uio_books_raw_v1 |
| 5 | Going Faster Mastering the Art of Race Driving - Carl Lopez | 7b783695-ad11-951e-1d53-ddf6d5b78dc4 | 233 | 1 | uio_books_raw_v1 |
| 6 | uio julian edgar car aero testing | 237ab1cc-b3cd-b239-83e4-b9ffcef75fdf | 91 | 1 | uio_books_raw_v1 |
| 7 | Competition Car Aerodynamics 3rd Edition McBeath Simon | b7c4490f-404e-a401-7f30-3294b7c2e23d | 347 | 1 | uio_books_raw_v1 |
| 8 | Competition Car Aerodynamics 3rd Edition McBeath Simon | be7ad522-b2e9-c7cf-5200-28fd517a750e | 411 | 1 | uio_books_raw_v1 |