Generated from content/lms/race-aerodynamics/07-turn-findings-into-a-tuning-plan/05-decide-what-is-not-an-aero-problem.md; edit the source file, not this page.

Source path: content/lms/race-aerodynamics/07-turn-findings-into-a-tuning-plan/05-decide-what-is-not-an-aero-problem.md

Course: Engineer downforce you can actually use

Module: Turn findings into a tuning plan

Estimated duration: 55 minutes

Rule out non-aero causes before tuning

The skill in this lesson is not making the first aero change. It is deciding when not to make one. Aero symptoms do not arrive wearing labels. A driver says the car pushed in the fast corner. The speed trace says the car lost top speed. The lap time fell away over a run. A new wing angle was fitted before the session, so the paddock answer is tempting: the aero change caused it. Sometimes that is true. Sometimes the tires faded, the wind shifted, the driver changed the entry, the track evolved, the car was never mechanically balanced, or the measurement method cannot support the conclusion.

Your job before a tuning plan is to protect the team from a false cause. You are not trying to prove that aero never matters. You are trying to make the aero question clean enough that the next change teaches you something. McBeath makes the starting condition clear: useful aero configuration testing on track assumes a race car with an optimized mechanical setup, then changes aerodynamic configuration while recording lap, sector, high-speed corner, and straight-line evidence, supplemented by driver feedback. If the mechanical setup is not under control, if the run structure is sloppy, or if the observed behavior lives outside the speed and phase where aerodynamics is likely to dominate, you do not yet have an aero problem. You have an investigation problem.

The practical rule is simple: call a symptom aerodynamic only after it passes four gates. First, it must occur in a speed range and car phase where aero load, balance, or drag can plausibly move the result. Second, it must repeat when the baseline is stable enough to trust. Third, it must respond to aerodynamic configuration while other important variables are held still. Fourth, its pattern must fit the type of aero effect you are claiming: balance in faster corners, load versus straight-speed tradeoff, drag on long straights, or transient balance shift from pitch, yaw, ride height, and speed. If any gate fails, the honest label is not an aero problem yet.

Principle: aero diagnosis is controlled comparison

Aerodynamics is attractive because the visible parts are adjustable. Wing angle, splitter height, spoiler trim, vent opening, duct shape, and diffuser rake all invite action. A tire losing grip does not look as adjustable in the moment. A headwind does not sit there with a wrench flat on it. A driver who turned in earlier may not feel like a configuration change. That is why uncontrolled aero tuning wastes time. The most adjustable part on the car is not always the cause.

The bonded corpus gives a disciplined pattern. McBeath describes track testing where two wing configurations were compared over five-lap runs, with only wing configuration changes made. Average lap times were recorded, unusual outlying lap times were discarded, sector and handling information were interpreted, and the baseline setup was revisited periodically because weather, track, and tire deterioration can move the reference underneath you. That method is not complicated, but its strength is exactly what most paddock conversations lack: it keeps the cause narrow.

The weak conclusion is: the car had understeer after we changed aero. The stronger conclusion is: in the same speed range, over comparable laps, after returning to baseline often enough to catch drift, with no mechanical or tire changes, this aerodynamic configuration produced a repeatable high-speed balance shift and a measurable sector effect. You may not always reach the strongest version at a club event, but that is the standard you are aiming toward. Until you can say something close to it, do not let the tuning plan harden around the aero explanation.

Gate 1: speed and phase

Start with where the symptom lives. McBeath frames traditional racetrack aero evidence around lap times, sector times, straight-line speeds, and higher-speed corner entry, apex, and exit speeds. The text gives a practical threshold around corners above roughly 60 mph or 100 km/h, while noting that the exact point depends on the downforce level of the car. That does not mean nothing aerodynamic happens below that speed. It means an intermediate driver or club-racing engineer should be suspicious of blaming aero for a symptom that appears only in slow corners, pit exit, hairpins, or low-speed rotation unless there is other strong evidence.

The phase matters as much as speed. Aerodynamic balance is not fixed. McBeath emphasizes that balance can change with yaw, pitch, rake, ride height, and the transient condition of the car, and that the car moves from straight running to braking to cornering to accelerating while both mechanical and aerodynamic loads change. If the driver reports understeer at brake release, mid-corner, and track-out, those may be three different problems. The first may include pitch and platform movement, the second may be loaded aero balance, and the third may be power delivery, tire condition, exit line, or aero shift as the car accelerates and ride height changes.

A useful triage note includes corner or sector, speed band, car phase, steering state, throttle or brake state, and whether the symptom appears in low-speed corners too. You are building a filter. Aero balance changes should show up most clearly where aero load is meaningfully contributing to tire normal load and where speed is high enough for configuration changes to move corner speed or balance. A mechanical issue has no obligation to respect that boundary. A tire issue may worsen with run length. A wind issue may change by direction. The speed-and-phase note gives you the first separation.

Gate 2: baseline stability

A baseline is not just the setup sheet you started the morning with. A baseline is the current reference condition you can return to and trust. McBeath stresses returning periodically to the baseline setup during a session, especially when weather or track conditions change. Tire deterioration is specifically called out as a variable that can be relied upon to change the baseline. That is the core of deciding what is not an aero problem: a moving baseline can impersonate a tuning result.

Imagine a test that begins with fresh tires and cool air. The baseline feels stable. You add rear downforce. Three runs later, the car understeers more and the top speed is lower. If you do not return to baseline, you cannot cleanly separate the configuration from the tires and conditions. The more laps you run, the more the tire and track story matters. The more the wind changes, the more the straight-speed and drag story can be contaminated. The more the driver learns or tires, the more lap time can move without a configuration cause.

The calibration cue is simple: if the baseline gets worse in the same way as the new configuration, the new configuration is probably not the whole cause. If baseline top speed drops in both directions of a straight-road test, wind or mechanical resistance may be in the result. If baseline corner speed falls over the same run length as the changed setup, tire degradation may be the major actor. None of those observations prove aero is irrelevant. They prove the current symptom is not clean enough to spend the next session chasing aero parts.

Gate 3: change isolation

The clean aero finding comes from one aerodynamic change at a time. McBeath's cited wing comparison worked because only the wing configuration changed between defined runs. If you change rear wing, front ride height, tire pressure, and brake bias together, you may still make the car better, but you have not learned which change did the work. When the lesson goal is deciding what is not an aero problem, stacked changes are especially dangerous because they create false confidence.

Isolation is also about the track evidence you choose. McBeath notes that there is not always time to separate mechanical from aerodynamic balance tuning, but the practical hope is to isolate each effect if the venue has low-speed and higher-speed corners. Use the track layout as a filter. A change that alters slow and fast corners in the same direction may be mechanical, tire, driver, or a broad platform effect. A change that leaves slow corners similar but moves faster corners in a repeatable way is a stronger aero candidate.

This filter protects you from the top-speed trap. McBeath warns that the setup producing the highest top speed rarely coincides with the best lap time, and that a higher top speed may not improve finishing position. If a higher-downforce setup lowers top speed but improves high-speed corner speed and segment time, the loss is not automatically an aero problem to fix. It may be the price of a better lap. If top speed drops without corner or segment benefit, then drag or configuration efficiency belongs on the suspect list.

Gate 4: pattern fit

Once a symptom passes speed, baseline, and isolation gates, ask whether the pattern fits the aero problem you are naming. Aero balance, total downforce, drag, and transient platform sensitivity are different questions. They can overlap, but they should not be diagnosed from the same single feeling.

An aero balance problem is about how aerodynamic load is divided front to rear at the speed and attitude in question. McBeath's basic tuning sequence starts from a dynamically stable condition: minimum front downforce and enough rear downforce to create medium and high-speed understeer. Then rear downforce is backed off until the car is balanced, or front downforce is increased if rear is already at minimum. The process is repeated with more rear downforce, adjusting the front until balance returns, building a reference table of balanced settings from minimum to maximum downforce.

A load problem is different. If more downforce increases faster-corner speed but changes the straight-speed cost, the question is whether elapsed time is better. McBeath points to corner-speed gains from increasing downforce, related straight-line speed loss, and overall elapsed time as the net measure. A lower top speed is not automatically bad if the segment and lap are better.

A drag problem needs straight-line evidence and environmental discipline. McBeath explains that drag is the easier aerodynamic force to begin measuring with modest tools, but outside testing suffers from wind. Practical remedies include still or near-still conditions and running in opposite directions, then smoothing data fluctuation statistically. If your straight-speed comparison was done in one direction on a windy day, do not overstate it.

A transient platform problem is the most nuanced. McBeath emphasizes that aero balance changes as the car changes speed and moves through braking, cornering, and acceleration, with pitch, yaw, ride height, and unsteady flow involved. A symptom that appears only during a narrow transition may not be solved by a static wing angle change. The correct label may be transient aero-platform suspicion, not proven wing-balance problem.

Evidence that keeps aero on the suspect list

Ruling out non-aero causes does not mean being conservative to the point of blindness. McBeath describes the value of seeing what air is doing around wings, spoilers, diffusers, cooling openings, and other crucial areas. Flow visualization can provide understanding and point toward areas for improvement. If you have visual evidence that flow behavior changes around an aero device, that is a legitimate reason to keep an aerodynamic question alive.

But visual evidence still has to be connected to measured behavior. A tuft pattern, witness mark, or observed separation can tell you where to look. It does not automatically tell you that the driver's complaint, sector loss, or straight-speed change came from that feature. Good aero work combines the visual clue with the run evidence instead of letting the clue become the conclusion.

The same is true for a balanced-setting table. If you have already built a reference table of front and rear settings from minimum to maximum downforce, use it. That table is a strong way to avoid guessing because it records how the car was balanced at different downforce levels and what the times showed at the test venue. If a later symptom appears with a known balanced combination, the first question is whether current conditions still match the earlier baseline.

Working protocol

Step one: write the symptom as a phase-specific observation. Avoid broad labels. Do not write fast push. Write that the car adds steering from entry to apex in the faster right-hand corner, or that it loses straight speed after the preceding exit, or that it becomes unstable as brake pressure releases at high speed.

Step two: decide whether the observation belongs inside the likely aero window. If it is only a low-speed cornering problem, leave aero out of the first response unless other evidence is strong. If it is a straight-speed problem, consider drag but ask about wind, exit speed, direction, and mechanical resistance. If it is a high-speed corner balance problem, keep aero on the list but continue the protocol.

Step three: check the baseline. Ask what the car did in the same sector before the change, whether the baseline was repeated after the change, whether tires and weather were comparable, and whether traffic or outlier laps distorted the average. If the baseline was not repeated and the evidence comes from a long evolving session, mark the finding provisional.

Step four: check isolation. List every change made between the compared runs. Include aero parts, ride heights, tire pressures, tire age, fuel, alignment, damper or bar settings, driver instruction, and track condition if known. If more than one meaningful variable moved, the conclusion becomes a test request, not a setup fact.

Step five: compare low-speed and high-speed behavior. If the same balance change appears in both, suspect mechanical, tire, driver, or broad platform change before a purely aerodynamic explanation. If the changed behavior concentrates in faster corners and the slow corners remain comparable, the aero case strengthens.

Step six: compare corner speed, straight speed, segment time, and lap or run time together. A speed trace can show corner and straight speeds, split times, elapsed run time, and braking deceleration trends. Do not tune from one number.

Step seven: name the next best question. Sometimes it is return to baseline. Sometimes it is repeat in opposite directions. Sometimes it is hold mechanical setup fixed and run a five-lap aero comparison. Sometimes it is build the balanced front-rear downforce table. Sometimes it is stop calling it aero and inspect tires, driver inputs, or mechanical balance.

How to rule out common non-aero causes

Tire deterioration is the first non-aero suspect because the source explicitly calls it out as a baseline changer. If the car degrades over the run, if the later baseline no longer matches the early baseline, or if the driver notes a progressive loss rather than a configuration-specific change, tire state can be the main explanation.

Weather and wind are the second suspect, especially for drag and straight-speed claims. McBeath identifies wind as an evident drawback of outside track testing and recommends still or near-still conditions and opposite-direction runs when needed. On a racetrack you may not be able to run both directions, but you can still be honest about the limit.

Mechanical resistance is the third suspect in straight-line testing. McBeath explains that direct drag measurement may require accounting for rolling resistance, transmission losses, and rotating inertia, and cites coastdown, dynamometer, and towing approaches for separating non-aero forces. For configuration comparisons, incremental changes in total drag can often be treated as aerodynamic in context, but if vertical force changes dramatically enough to affect rolling resistance, measurement is better than assumption.

Mechanical balance is the fourth suspect in cornering diagnosis. Meaningful aero configuration work assumes an optimized mechanical setup. If the car already has unresolved mechanical understeer, poor tire use, or inconsistent low-speed behavior, adding wing may cover or exaggerate the symptom without teaching you the cause.

Driver input is the fifth suspect. The bonded chunks do not teach a detailed driver-coaching protocol here, but the test logic still requires you to acknowledge the driver as a variable. If braking point, entry speed, line, steering rate, or throttle application changes between runs, the car's attitude and speed history into the corner changed.

Measurement error is the sixth suspect. McBeath notes that even simple rpm or speed traces can produce useful information, but the value comes from preserving a record and inspecting it. A basic logger can be enough; a vague memory usually is not.

Calibration cues

You are improving at this skill when your notebook stops saying aero bad and starts saying what evidence would make aero likely. You write high-speed only, baseline repeated, same configuration except rear wing, straight speed down and faster-corner minimum speed up, segment net positive. Or you write low-speed and high-speed both worse after long run, no baseline return, tires older, do not call aero yet.

Your data traces improve in the same way. You begin to look at speed across a sector, not only lap time. You compare corner entry, apex, and exit speeds in faster corners. You look at straight-line speed alongside the exit that created it. You compare split time and overall elapsed time. You watch for braking deceleration changes that might explain a sector without invoking aero.

Your run structure improves. You hold non-aero settings still while testing aero. You use defined run lengths. You average useful laps rather than worshipping the single best or worst lap. You return to baseline often enough to catch drift. You note weather, tire condition, and driver comments. You create a reference table of balanced front and rear settings when the car has adjustable downforce aids, so a future wet session or different venue does not require starting from guesswork.

Recovery when you chased the wrong cause

If you discover that a supposed aero problem was not aerodynamic, do not defend the old story. Return to the last known stable baseline if it is safe and practical. Record what confused the diagnosis: no baseline return, changing tires, wind, stacked changes, low-speed symptom, driver variation, or a data problem. Then write the next test as a controlled comparison.

The most common recovery is a baseline re-run. Put the car back to the known aero setting, hold the mechanical setup, and run enough comparable laps to see whether the original symptom returns. If it does return, the cause is probably still present outside the aero change. If it disappears, repeat the aero change with tighter controls. If both runs are inconsistent, stop treating the day as a tuning day and treat it as a data-quality or conditions day.

The mature action is not to keep adding changes until one feels better. It is to admit that the current evidence does not isolate aero, return to a known setup, and design a cleaner comparison.

Worked example: faster-corner push after adding rear wing

You add rear wing because the driver wanted more security in a fast corner. The next session comes back with a complaint: the car now pushes in that same fast corner and the top speed is down. The rushed answer is to remove the rear wing and declare the change bad. A better answer follows the gates.

First, the symptom passes the speed gate. A faster corner is exactly where aerodynamic balance can become visible, and straight speed is a valid part of the aero tradeoff. Second, check baseline stability. Was the earlier baseline repeated after the change, or are you comparing a cool early run with a warmer later run on older tires? If there was no return to baseline, the correct conclusion is provisional.

Third, check isolation. If only rear wing changed, the result is much cleaner. If rear wing, tire pressure, and driver brake marker changed together, you cannot assign cause. Fourth, check pattern fit. More rear downforce can create a more stable but more understeering high-speed balance. McBeath's safe starting method begins with enough rear downforce to create medium and high-speed understeer, then backs off rear or adds front until the car balances. The symptom may not mean aero is the wrong tool. It may mean the front and rear downforce settings are not matched.

The tuning-plan decision is therefore specific. Do not write remove wing because top speed dropped. Write that the rear-downforce increase produced high-speed understeer and straight-speed loss, then test the balanced-setting sequence. Judge the result by faster-corner speed, straight speed, segment time, and lap or run time together.

Worked example: the aero change blamed for tire drift

You run baseline in the morning, then make an aero change before lunch. The car feels worse in the afternoon. The driver reports less grip everywhere and especially complains that the fast corner is no longer trustworthy. The new part is visible, so the team blames it.

This is exactly where the baseline gate protects you. McBeath says track and weather conditions can change during a session and that tire deterioration can be relied upon to change the baseline. The first question is whether the car was returned to the earlier setup and whether it reproduced the earlier behavior. If the baseline also feels worse and the logged speeds have fallen in both low-speed and high-speed areas, the aero change has not been isolated.

Now use the low-speed and high-speed filter. If the car is worse in the slow corners where aero should be less dominant and worse in the fast corners too, the symptom pattern does not point cleanly at aerodynamic balance. Tires, track state, driver fatigue, traffic, and temperature deserve attention before the wing angle becomes the main answer.

The correct next action is a controlled re-run, not another aero adjustment. Return to the baseline aero setting if safe, run a defined comparison, record the lap or segment times, note tire state and conditions, and only then repeat the aero change if the baseline behaves consistently.

Worked example: a straight-speed drag claim on a windy road

A team tests two configurations on a long straight piece of road. Configuration B is slower by a small amount at the end of the run, so the team calls it a drag increase. That may be true, but the bonded source gives you a warning: outside testing is exposed to wind fluctuation, and the practical remedy is still or near-still conditions plus opposite-direction runs when necessary.

The first filter is environmental. Were the runs made in comparable wind, or did the wind change between passes? Were they run both directions, or only one way? If only one direction was used and the wind was active, the honest conclusion is that the drag claim is contaminated. The next action is to repeat under calmer conditions or in both directions, then average or apply simple statistics to smooth the fluctuation.

The second filter is non-aero resistance. McBeath describes rolling resistance, transmission losses, rotating inertia, and mechanical resistance as part of direct drag measurement work. For incremental configuration changes, you can often treat total drag changes as aerodynamic in this context. But if the configuration also changes vertical load enough to affect rolling resistance, measurement is better than assumption.

The decision is not that straight testing is useless. It is useful when the question is clean. The decision is that a small one-direction speed change in wind is not yet a drag problem. It is a request for a better drag test.

Common mistakes and what good looks like

Mistake one is blaming aero for any fast-corner complaint. Good looks like writing the speed band and phase first, then asking whether the symptom is isolated to faster corners and whether low-speed behavior stayed comparable.

Mistake two is comparing a new setup to a memory instead of a repeated baseline. Good looks like returning to the baseline periodically, especially when weather, track, or tires may have changed, and treating a drifting baseline as its own finding.

Mistake three is changing too many things at once. Good looks like one aerodynamic configuration change inside a defined run, with driver feedback and data notes tied to that run.

Mistake four is worshipping top speed. Good looks like comparing straight speed against faster-corner speed, segment time, and total elapsed time. A lower top speed can be acceptable if the net time improves.

Mistake five is ignoring wind during drag testing. Good looks like still or near-still conditions when possible, opposite-direction runs when needed, and caution when environmental fluctuation is larger than the change you are trying to measure.

Mistake six is treating transient balance as a static wing-angle problem. Good looks like naming the phase: braking, straight running, cornering, or accelerating. If the symptom appears during pitch, yaw, speed, or ride-height change, the next question may be aero platform behavior rather than simple front-rear static balance.

Mistake seven is refusing to revert. Good looks like being willing to return to the old setup when a new idea does not work. Experimenting is useful, but a clean revert is how the next comparison stays meaningful.

Drill: the three-run aero-or-not filter

At your next test day, choose one aero-relevant symptom and run a three-run filter. The count is three defined runs: baseline, one aero configuration change, and return-to-baseline. The preferred run length is five laps per configuration when the event format allows it, matching the disciplined comparison described in the corpus. If your event gives shorter sessions, keep the structure and reduce the lap count rather than mixing variables.

Before the first run, write one symptom in phase-specific language. Choose one faster corner or one straight-sector question. Also choose one lower-speed corner as a mechanical reference if the track layout gives you one. Record the current aero setting, tire state, weather notes, and any mechanical settings you promise not to change.

Run one is baseline. The driver gives feedback immediately afterward, but the note must include where, when, and how the symptom occurred. Record lap or segment times if available. From a basic logger, collect speed or rpm versus time so you can compare corner speed, straight speed, splits, and braking deceleration trends.

Run two is the single aero change. Make only the chosen aerodynamic change. Do not add tire pressure tuning, bar changes, damper changes, alignment changes, or a new driving assignment. Record the same notes and the same data. Discard laps that were obviously abnormal because of traffic or mistakes before comparing averages.

Run three is return-to-baseline. This is the part most teams skip, and it is the part that tells you whether your reference moved. If the baseline reproduces its earlier behavior, your comparison is much stronger. If the baseline has drifted, you have found a non-aero confounder: tires, weather, track, driver, or measurement.

The success criterion is not making the car faster. The success criterion is a defensible label. At the end of the drill, you must be able to place the symptom in one of four buckets: likely aero balance or load, likely drag or straight-speed tradeoff, not cleanly aero because the baseline moved, or not primarily aero because the symptom appears outside the aero-sensitive pattern.

Cross-references for the tuning plan

Use this lesson before the sibling lesson on translating high-speed feedback into testable aero questions. That lesson should receive only the findings that passed the speed, baseline, isolation, and pattern-fit gates.

Use it before prioritizing balance, load, then drag. If the symptom is not yet proven aerodynamic, prioritizing aero categories is premature. If it is aerodynamic, this lesson helps you name which category you are actually feeding into that priority order.

Use it before validating in racing air. The validation lesson needs a clean question. A dirty question produces a dirty validation even when the car is tested on track.

Use it before building a speed and ride-height map. If the symptom is transient and linked to braking, yaw, acceleration, or ride-height movement, the map may be the next right tool. But this lesson keeps you from using that map as a catch-all explanation for every bad lap.

Author Review

No quiz questions are attached to this lesson.

Sources

#	Document	Chunk	Pages	Score	Collection
1	Competition Car Aerodynamics 3rd Edition McBeath Simon	4adf8cb4-89c7-1b45-bd4d-9bb03634ecf3	345	1	uio_books_raw_v1
2	Competition Car Aerodynamics 3rd Edition McBeath Simon	c0cd0f54-6d9c-7f08-e9af-37c31b3421d3	345	1	uio_books_raw_v1
3	Competition Car Aerodynamics 3rd Edition McBeath Simon	2dcc6067-583b-6042-00b6-d306f5d46cd6	344	1	uio_books_raw_v1
4	Competition Car Aerodynamics 3rd Edition McBeath Simon	76c2bbb8-7ace-d134-aad7-e2b7ba9841e5	475	1	uio_books_raw_v1
5	Competition Car Aerodynamics 3rd Edition McBeath Simon	80bde176-e318-b515-e3d5-5de74a7cd507	476	1	uio_books_raw_v1
6	Competition Car Aerodynamics 3rd Edition McBeath Simon	b7c4490f-404e-a401-7f30-3294b7c2e23d	347	1	uio_books_raw_v1
7	Competition Car Aerodynamics 3rd Edition McBeath Simon	da0eb061-4403-af2d-783d-5b7d9ae16326	476	1	uio_books_raw_v1
8	Competition Car Aerodynamics 3rd Edition McBeath Simon	2abb3a1a-1abc-3549-8f79-9fce704061d6	334	1	uio_books_raw_v1