Put aero forces into the car's axes

Generated from content/lms/vehicle-dynamics-ii-theory/06-aerodynamic-force-and-moment-balance/01-aero-forces-in-body-axes.md; edit the source file, not this page.

Source path: content/lms/vehicle-dynamics-ii-theory/06-aerodynamic-force-and-moment-balance/01-aero-forces-in-body-axes.md

Course: Read the forces that steer the car

Module: Add downforce and drag to the force budget

Estimated duration: 55 minutes

Principle: the car does not respond to labels on a wind-tunnel sheet. It responds to forces and moments in its own axes.

Your job in this lesson is to take aerodynamic data that may arrive as drag, lift, side force, axle loads, yaw angle, and moments, then turn it into the force and moment bookkeeping the vehicle can actually use. That means you choose a vehicle-fixed coordinate system, choose the point about which moments are reported, resolve the total aerodynamic force into the car axes, and keep the six results together: longitudinal force, side force, normal force, roll moment, pitch moment, and yaw moment.

The first rule is simple: treat the aerodynamic load as one total force first. The air does not know whether your spreadsheet wants drag, lift, side force, Cx, Cy, Cz, MX, MY, or MZ. The air applies a resultant load to the vehicle. For analysis, you resolve that one resultant into rectangular force components at a given point, then add moments about the axes. That is why a complete aero-load statement has three forces and three moments. A table that gives only downforce and drag is not yet a handling model. It is a partial description of a load system.

The second rule is just as important: a force component is only meaningful after you name the axes. Drag is tied to the relative airflow. Longitudinal force is tied to the vehicle body. Lift or downforce may be reported using a wind-tunnel convention, a ride-height convention, or a sign convention where negative lift means downforce. Normal force in the body axes is the vertical or body-normal component in the coordinate system you have chosen. At zero yaw on level ground these categories may appear to line up neatly. As soon as there is yaw angle, side wind, vehicle asymmetry, pitch, roll, or a different reporting convention, the casual language breaks down.

That is the skill: stop reading aero data as names, and start reading it as vectors and moments.

Start with the car axes. A useful handling convention is the vehicle-fixed x, y, z system. In that convention the aerodynamic force coefficients are longitudinal force Cx, side force Cy, and normal force Cz. The moment coefficients are roll moment CMx, pitch moment CMy, and yaw moment CMz. You do not have to love those exact names, but you must pick a system and keep it unchanged through the whole calculation. The source texts use the same basic split: force along the car, force across the car, force normal to the car, plus moments about the longitudinal, transverse, and vertical axes.

Now choose the reference point. For handling analysis, the center of gravity is usually the point that matters, because stability is a question of how the vehicle mass moves and rotates. A resultant aerodynamic force applied at the center of pressure produces no moment about the center of pressure itself. Move the same force to the center of gravity and it creates moments because the force now has lever arms. That is not an optional refinement. If the center of pressure and center of gravity are not the same point, the vehicle sees a moment about the center of gravity.

This is where many aero balance mistakes begin. A driver or engineer says the car has more rear downforce, or more side force, or more drag, but does not say where the resultant acts. The car cannot respond to the magnitude alone. It responds to the magnitude and the line of action. A normal force behind the center of gravity produces a pitch effect. A side force acting away from the center of gravity produces yaw and roll effects depending on the horizontal and vertical offsets. Drag acting above or below the center of gravity can contribute to pitch. The same total force can be stabilizing, destabilizing, or mostly irrelevant to the behavior you are studying depending on its lever arm.

The body-axis workflow starts with a clean free-body habit. Draw or list every external force acting on the vehicle. The vehicle response comes from the net forces and the total moment about the mass center. In simplified handling work you often reduce the full rigid-body problem to the parts you need, because the complete rotational equations are complex and the principal axes of inertia do not necessarily coincide with the body-fixed axes. That simplification is acceptable only if you stay honest about what you kept and what you neglected. If you are analyzing straight-line aero drag and downforce, you may not need the full yaw and roll equations. If you are analyzing a gust, a yawed aero map, or a high-speed corner where roll and side force are coupled, you cannot quietly throw away the lateral and rotational terms.

Use this four-question gate before touching the numbers.

First, what axes are the forces reported in? A wind-tunnel printout may list drag, side force, and lift. Those are commonly understood in relation to airflow and the measurement setup. A vehicle-dynamics model usually needs longitudinal, side, and normal force in the vehicle axes. If the airflow is aligned with the car and the car is level, the mapping is straightforward. If the car is at yaw, the wind direction and car direction are not the same direction. Resolve the airflow-related forces into the car-fixed axes before you call them Cx, Cy, or Cz.

Second, what sign convention is being used? In one useful printout convention, lift is negative when the load is downforce. That can be perfectly valid, but it must be carried consistently. Do not mentally flip signs because the word downforce feels positive. If a table says negative lift, and that table defines negative lift as downforce, the negative sign is part of the data. Your calculation can convert it later, but the conversion must be explicit.

Third, where are the moments taken? Moments about the center of gravity are not the same as moments about the center of pressure, the ground plane, an axle centerline, or a tunnel balance reference point. If the report already gives MX, MY, and MZ about the center of gravity, you can use them directly after checking convention. If it gives the location of the center of pressure instead, you must move the force to the center of gravity. If it gives axle reactions, you can infer useful splits, but those are reactions at the tire contacts, not a substitute for naming the resultant and reference point.

Fourth, what length and area created the coefficients? Force coefficients are reduced with dynamic pressure and reference area. Moment coefficients need one more length. For vehicle handling work, wheelbase is commonly used for pitch and yaw moment coefficient scaling because the wheels react those moments over the wheelbase. That choice is practical, but it also means two cars with different wheelbases can have moment coefficients that are affected by a length that is not itself an aerodynamic shape feature. When you compare vehicles or configurations, make sure the coefficient denominator did not quietly change the story.

Once those four questions are settled, the actual technique is mechanical.

Step one: write the total aerodynamic force as a vector in whatever axes the data gives you. If your data sheet gives drag, side force, and lift, do not immediately assign them to x, y, and z unless the sheet says those are already vehicle-fixed axes. Treat them as components in the measurement basis. At yaw angle, the relative airstream is at an angle to the car axis, so the longitudinal and lateral parts of the wind velocity are distinct. The same must be true of the force components built from that flow. Resolve by projection: express the unit directions for drag, side force, and lift in the car body axes, multiply each force by its unit direction, then sum the components. The result is one body-axis force vector.

Step two: convert the body-axis force vector into force coefficients only after the resolution is complete. Cx is the body-axis longitudinal force divided by dynamic pressure and reference area. Cy is the body-axis side force divided by the same force scale. Cz is the body-axis normal force divided by the same force scale. If you calculate coefficients first in wind axes, then rename them as body-axis coefficients, you have mixed coordinate systems. That mistake can be hidden at zero yaw and exposed at yaw.

Step three: move the resultant to the reference point used by the vehicle model. For stability and handling, use the center of gravity unless the model explicitly says otherwise. If the center of pressure location is known relative to the center of gravity, compute the moment from the force and the lever arm. In practical terms, a force acting through the center of pressure has no moment about that point, but the same force generally has pitch, yaw, and roll moments about the center of gravity. The pitch moment comes from the fore-aft and vertical offsets of the force line. The yaw moment comes from the side-force line of action relative to the center of gravity. The roll moment depends not only on the side force and height, but also on the rolling axis used in the suspension model.

Step four: keep axle loads as reactions. Load cells under the wheels can report horizontal, vertical, and lateral forces at the tire contacts. That is extremely useful because it shows how the aero system is being reacted by the car. Front and rear vertical loads show the split of downforce. Front and rear lateral loads show the split of side force. The sums must close: front plus rear side force equals total side force, and front plus rear lift equals total lift in the convention of that report. Use those sums as sanity checks. But do not confuse the reaction split with the original free-body statement. The vehicle still needs a total force and a moment system.

Step five: interpret moments as consequences of distribution, not as mysterious extra loads. If a wind-tunnel sheet shows a large pitch moment about the y-axis, that moment arises from the way the aero forces are distributed around the center of gravity. A rear-biased downforce distribution creates a pitch moment even if total downforce looks attractive. The number is not separate from downforce; it is the rotational bookkeeping of where that downforce acts.

Step six: decide whether roll belongs in the calculation. Some vehicle aero treatments neglect roll angle because experiments on normal vehicles have shown roll angle to have a small effect on the aerodynamic forces. That is a reasonable simplification for many coefficient reductions. It is not permission to ignore roll in every handling problem. When the sprung mass rolls, the relation between aerodynamic side force, rolling axis, center of gravity, and center of pressure can change the equilibrium of forces and moments. If you are studying wheel-load distribution changes or the coupling between roll and yaw, you have to account for the rolling axis and left-right wheel behavior.

For an intermediate driver, the most useful mental model is this: drag and downforce tell you how much air load exists, but the car axes tell you what the load does to the car. The body-axis reduction is the bridge between aero testing and handling behavior.

Consider a straight-line case first. You have a configuration run at zero yaw. The printout gives drag, side force, and lift, with lift negative when it is downforce. Side force is very small. In that case, most of your attention goes to longitudinal force, normal force, pitch moment, and front-rear vertical-load split. You still write Cy down, but you may ignore it for the handling question if it is truly small compared with drag and downforce. The word truly matters. You ignore it because the data says it is small in that condition, not because side force is always unimportant.

Now change only the condition: add yaw angle or a wind gust. The airflow is no longer aligned with the car trajectory. The wind velocity can be resolved into one component along the direction of motion and one component at right angles to it. The aero force system now includes a lateral component that can change yaw response and trajectory. If the center of pressure is downstream of the center of gravity, the side-force impulse can be more effective in increasing the initial yaw rate, while also introducing a damping element as the aerodynamic side force decreases. That is already a different handling problem from the zero-yaw downforce case, even if total downforce has not changed much.

This is why body axes are not bookkeeping for bookkeeping's sake. They keep you from diagnosing the wrong problem. If the car feels nervous in a fast crosswind zone, a downforce-only discussion is too narrow. If the yaw moment is coming from side force acting at a lever arm, adding vertical load may not address the yaw response. If the printout reports a large pitch moment because the rear downforce is high, a total-downforce gain may still move balance in a direction the driver dislikes. If roll motion changes wheel-load distribution while side force acts above the rolling axis, a body-axis model that ignores roll may look cleaner than the car feels.

Good body-axis work has several calibration cues.

The first cue is closure. Your front and rear load sums match the total loads in the report. The side-force split adds to total side force. The lift or downforce split adds to total lift in the report's sign convention. If those sums do not close, stop. You either have a sign error, a unit error, a copied-column error, or a misunderstanding of what the columns mean.

The second cue is stable naming. You never use drag as a synonym for Cx unless you have already confirmed the drag direction and x-axis are aligned or have performed the rotation. You never use lift as a synonym for Cz unless the sign and axis convention match. You never discuss MX, MY, or MZ without naming the reference point. If you can read your own worksheet a week later and know exactly what each component means, you are improving.

The third cue is a believable trend. Coefficients are mathematical treatments of forces, and their value is that they help you spot trends and quantify gains or losses. If a configuration change increases total downforce, shifts front percentage, and changes pitch moment in a consistent direction, the data is telling one story. If the coefficients suggest a gain while the raw forces and axle reactions do not support it, you have a reduction problem before you have an aero insight.

The fourth cue is a matching driver problem. In a straight high-speed section, longitudinal and normal components dominate the usual feel: acceleration cost from drag, platform support from downforce, and balance from front-rear vertical load split. In yawed flow or gust exposure, side force and yaw moment enter the feel: the car may require a correction, change trajectory, or feel more directionally sensitive. In a high-speed bend with roll, side force can couple into roll and yaw while left-right wheel loads diverge. Your axis choice should make the driver complaint easier to state, not harder.

The fifth cue is an honest simplification statement. A good worksheet says which effects were kept and which were neglected. You might state that roll angle effects on the aero coefficients were neglected for a normal-vehicle, small-roll calculation. You might also state that roll equilibrium and wheel-load redistribution were retained because the problem involves high-speed cornering side force. Those two statements can coexist. What you cannot do is silently borrow a simplification from one problem and apply it to another problem with different physics.

There are three sub-skills inside the headline skill.

Sub-skill one is axis translation. You take force names from the measurement source and translate them into the vehicle-fixed x, y, z components. This is where you handle yaw angle, sign convention, and the difference between airflow-related labels and body-related labels. You are successful when every force component has a direction, a sign, a unit, and an axis basis.

Sub-skill two is reference-point discipline. You decide whether the moment is about the center of gravity, center of pressure, tire contact plane, or another balance reference. Then you move the force or use the reported moment accordingly. You are successful when another person can tell exactly why your pitch, roll, or yaw moment exists.

Sub-skill three is reaction interpretation. You use axle and wheel load data as a check on the force system and as a way to understand balance, but you do not mistake reactions for the original external force. You are successful when LF plus LR equals total lift in the report convention, CYF plus CYR equals total side force, and your moment interpretation agrees with the load split.

The sibling lessons in this module take the next steps. Center-of-pressure migration is about how the line of action moves and what that movement says about aero balance. Pitch-induced downforce variation is about how attitude changes the aero loads themselves. This lesson comes before both. Here you are not yet diagnosing a moving center of pressure or modeling a pitch-sensitive aero platform. You are making sure the forces and moments are expressed in the car's language before you diagnose anything.

A compact body-axis reduction checklist looks like this. Name the vehicle axes. Name the sign convention. Name the moment reference point. Copy raw drag, side force, lift, speed, yaw angle, and axle loads exactly as reported. Resolve airflow-related components into body-axis components when yaw or convention requires it. Sum front and rear reactions and confirm they match the totals. Convert to Cx, Cy, Cz with dynamic pressure and reference area. Convert moments to moment coefficients with dynamic pressure, reference area, and the chosen length, commonly wheelbase for handling work. Only then describe balance, stability, or driver feel.

If you skip the order, you can get a result that looks sophisticated and is still wrong. If you follow the order, even a simple aero table becomes useful. You can see whether side force is small enough to ignore in that condition. You can see whether a large pitch moment is simply the rotational expression of rear-biased downforce. You can see why a gust problem belongs in yaw and side force, not in total downforce alone. Most importantly, you can keep the math connected to the car the driver actually feels.

Worked example: reducing a coefficient printout from a straight-ahead aero run

Imagine you are handed the kind of printout described in the competition-car aero source: run number, wind speed, yaw angle, total drag, side force, lift, moments MX, MY, MZ, front and rear side-force reactions, front and rear vertical-load reactions, drag power, lift-to-drag ratio, and reference area. The run is straight-ahead or near straight-ahead, and the reported side force is very small compared with drag and downforce.

Your first move is not to talk about balance. Your first move is to identify the basis of the data. The printout reports drag, side force, and lift. It also reports yaw angle. At zero yaw, drag will mostly map to the vehicle longitudinal axis, side force to the vehicle lateral axis, and lift to the normal or vertical axis according to the report's sign convention. Because the run has small side force, you can keep Cy in the worksheet but decide it is not the main handling driver for this condition.

Next, inspect the moments. The source example states that the moments arise from the distribution of aerodynamic forces around the center of gravity, with a large pitch moment about the y-axis arising from more downforce at the rear. That is the key interpretation. You do not need a new mysterious force to explain the pitch moment. The rear-biased vertical load creates a rotational effect about the center of gravity. You can check that interpretation by looking at the front and rear vertical-load columns. LF plus LR must equal total lift in the report convention, and the front percentage of total lift is a useful aero-balance measure.

Now convert only after the checks close. Use dynamic pressure and frontal reference area for the force coefficients. Use the same dynamic pressure and area plus the selected length for the moment coefficients. If the report allows frontal area to be amended for a configuration change, record that change, because a coefficient comparison is only meaningful when the denominator is known.

The lesson from this example is that a straight-ahead aero run can still be a six-component load statement. The side-force part may be small enough to ignore for the specific question, but the pitch moment and front-rear load split are central. You are not just asking how much downforce the car made. You are asking where the car had to react it.

Worked example: a transient wind gust as a body-axis problem

Now work the problem the other way around. The car is exposed to a wind gust. The aerodynamic source describes the proper experimental ideal as a controllable and measurable external wind gust acting on a full-sized car, because scale-model work struggles to reproduce suspension elasticity and mass inertia characteristics. That tells you how serious the axis problem is. A gust is not just extra drag. It is a time-varying external aerodynamic force acting on a moving, rotating vehicle.

Start with the wind direction. The wind velocity may blow at an angle to the car trajectory. Resolve that wind into a component along the direction of motion and a component at right angles to it. The longitudinal component affects the along-path aero condition. The lateral component creates side-force content. Once that lateral content exists, the center of pressure position relative to the center of gravity matters.

If the center of pressure is downstream of the center of gravity, the side-force impulse can increase the initial yaw angular velocity more effectively, while also adding a damping element as the aerodynamic side force quickly decreases. In driver language, that means the first response and the later settling response can point in different diagnostic directions. The first correction may feel like a yaw kick. The later behavior may feel like the car is finding a new line or damping itself out. You cannot understand that with total downforce alone.

The body-axis reduction is the way to keep the gust honest. Record the side-force component in the car's lateral axis. Record the yaw moment about the center of gravity. Keep the time-varying nature of the terms in mind. Then ask whether the driver complaint is about straight-line load, yaw response, or trajectory change. The gust problem belongs primarily in side force, yaw moment, and transient response, with normal force and pitch included only as supported by the data.

Worked example: roll, side force, and wheel-load distribution in a fast bend

A steady high-speed bend adds a different complication. The vehicle is not just receiving vertical aerodynamic load. The sprung mass can roll, the left and right wheels no longer behave as identical pairs, and aerodynamic side force can couple into roll and yaw through the relative positions of the rolling axis, center of gravity, and center of pressure.

Start by separating two questions. The first question is whether roll angle materially changes the aerodynamic force coefficients. For many normal vehicles, that effect may be small enough to neglect in an aero coefficient model. The second question is whether roll motion matters to the handling equilibrium. In a high-speed bend with side force, it can matter because the rolling moment must be balanced by suspension reaction torque, and the left-right wheel loads change as the sprung mass tilts.

In the body-axis worksheet, you keep the lateral aerodynamic force as Cy or body-axis side force. You locate its line of action relative to the center of gravity and rolling axis. You then carry the resulting roll and yaw effects into the equilibrium you are studying. If you only keep total downforce, you will miss the part of the problem that changes wheel-load distribution. If you only keep roll mechanics and ignore aero side force, you will miss one of the external loads creating the rolling moment.

The practical interpretation is restrained. You do not need to turn every club-racing corner into a full six-degree transient model. But when the driver reports that the car changes attitude or confidence in a fast bend with yawed flow, you should not reduce the aero question to front percentage of downforce only. The side force and its lever arm may be part of the answer.

Common mistakes

Mistake one: renaming wind-axis drag as body-axis Cx without checking yaw. At zero yaw this may do little harm. At yaw it can be wrong because the airflow direction and the car's x-axis are not the same direction. Good work resolves the force into the vehicle axes first, then calculates Cx, Cy, and Cz.

Mistake two: treating lift, downforce, and normal force as interchangeable words. A report may define lift as negative when it is downforce. A vehicle model may define normal force with a different sign. Good work copies the original sign convention, states the conversion, and keeps the converted sign consistent through the worksheet.

Mistake three: discussing aero balance without a reference point. Total force at the center of pressure has no moment about the center of pressure, but the same force usually has a moment about the center of gravity. Good work says where the moment is taken and explains the lever arm.

Mistake four: reading axle-load split as if it were the whole force system. Front and rear vertical loads are extremely useful because they show the downforce split, and front plus rear must equal the total in the report convention. But the axle reactions are not a replacement for the total force and moment statement. Good work uses axle loads as checks and balance indicators while still carrying the six-component load system.

Mistake five: ignoring side force because the first run had small side force. The source printout has a case where side force is small and can be ignored for that run. That does not make side force globally unimportant. At yaw angle, under asymmetry, or in a gust, side force can affect yaw response and trajectory. Good work decides from the condition and data, not from habit.

Mistake six: comparing moment coefficients without checking the scaling length. Moment coefficients require a length in addition to dynamic pressure and reference area. Wheelbase is convenient for handling because the wheels react pitch and yaw over that distance, but it can complicate comparisons between vehicles. Good work records the length used before comparing moment coefficients.

Mistake seven: using a roll simplification in a roll problem. It can be reasonable to neglect roll angle effects on aero coefficients for many normal vehicles. It is not reasonable to neglect roll equilibrium when the question is wheel-load distribution in a rolling vehicle under side force. Good work distinguishes coefficient simplification from handling-equilibrium simplification.

Drill: six-row body-axis audit at your next event

Use this as a paddock drill with your own aero map, a team setup sheet, a published tunnel printout, or a prepared worksheet from your instructor. Do not do it while driving. Do it after sessions when the car is parked and you can think clearly.

Count and duration: complete six rows in one event day. Do two rows before the first session, two rows after the middle session, and two rows after the final session. Spend about ten minutes per pair of rows. Each row is one aero condition or one configuration condition: for example zero yaw baseline, nonzero yaw, higher speed, lower speed, configuration A, and configuration B.

For each row, fill these fields in order: source axes, sign convention, reference point for moments, drag or longitudinal force as reported, side force as reported, lift or normal force as reported, yaw angle, MX, MY, MZ, front vertical load, rear vertical load, front side force, rear side force, reference area, coefficient length, and any conversion you made into body axes.

Then perform three checks. Check one: front plus rear vertical load equals total lift or normal force in the report convention. Check two: front plus rear side force equals total side force. Check three: every moment you discuss has a named reference point. If any check fails, mark the row unresolved and do not use it to make a balance claim.

Success criterion: by the end of the day, at least five of six rows close on the force sums, all six rows name the moment reference point, and none of your notes use drag, lift, side force, Cx, Cy, Cz, MX, MY, or MZ without an axis or sign convention. The point is not to create a perfect aero model. The point is to build the habit that prevents false balance conclusions.

When this principle breaks down or needs more model than you have

The body-axis reduction is necessary, but it is not always sufficient. A transient wind gust adds time-varying forces and moments. The full equations include coupling between yawing, rolling, and pitching motion, inertia terms, tire reactions, and aerodynamic terms. The source text notes that the resulting equations can become nonlinear and mathematically difficult, which is why simplified assumptions are introduced.

That matters for your confidence level. If you have a steady-state tunnel run, body-axis reduction and moment bookkeeping may be enough to compare configurations. If you are diagnosing a transient gust response, a yaw kick, or a trajectory change, you should treat the result as a reduced model unless you also have the transient data and vehicle response model. If you are studying a rolling vehicle in a fast bend, you may need left-right wheel loads and a suspension roll model, not just front-rear aero balance.

There is also an experimental limit. The aerodynamic transient source emphasizes that the correct way to simulate transient aerodynamic forces is a controllable, measured external gust on a full-sized car, while scale-model testing struggles with suspension and inertia representation. That does not make simpler data useless. It tells you how far to trust it. Use body-axis reduction to avoid basic coordinate errors, then be explicit about whether your data supports a steady-state, quasi-steady, or transient conclusion.

Author Review

No quiz questions are attached to this lesson.

Sources

#	Document	Chunk	Pages	Score	Collection
1	Tires Suspension and Handling Second Edition Dixon John C	7b56ed13-3403-11c2-3f8d-978526eff3cd	174	1	uio_books_raw_v1
2	Competition Car Aerodynamics 3rd Edition McBeath Simon	b7f8c68b-3c29-88fe-b88b-f9ada3d2e375	373	1	uio_books_raw_v1
3	Road vehicle aerodynamics Scibor-Rylski A. J Sykes D. M	11ece586-3f7e-1c0c-c507-296d9c5b9b14	183	1	uio_books_raw_v1
4	Road vehicle aerodynamics Scibor-Rylski A. J Sykes D. M	27f582f6-76d3-7857-bede-4d209abaa8ff	231	1	uio_books_raw_v1
5	Road vehicle aerodynamics Scibor-Rylski A. J Sykes D. M	4c130cd5-9dec-94d5-4522-a24ed24173f2	237	1	uio_books_raw_v1
6	Road vehicle aerodynamics Scibor-Rylski A. J Sykes D. M	37cf82f6-1b02-5521-8fed-6bfdb78732e2	205	1	uio_books_raw_v1
7	Tires Suspension and Handling Second Edition Dixon John C	2e01a9ec-a6ff-54ef-0bc3-b598ff1233d6	28	1	uio_books_raw_v1
8	Road vehicle aerodynamics Scibor-Rylski A. J Sykes D. M	2be4259e-405d-83c9-c7b9-d16cbde9f182	252	1	uio_books_raw_v1