Drive the fuel number as the car changes
Generated from
content/lms/racecraft-and-strategy/03-tire-fuel-management/02-fuel-strategy.md; edit the source file, not this page.
Source path: content/lms/racecraft-and-strategy/03-tire-fuel-management/02-fuel-strategy.md
Course: Racecraft & Strategy
Module: Tire & Fuel Management
Estimated duration: 55 minutes
The skill
A fuel stint is not one perfect lap repeated until the checkered flag. It is a changing problem. The car starts heavier, burns fuel, becomes lighter, may change balance as the fuel load moves or drops, and still has to hit a strategic fuel-per-lap target. Your job is to drive that number without turning the race into a slow parade lap, without creating random lifts in the wrong places, and without missing the larger race plan.
The fuel number begins with engineering questions, but it becomes a driving skill as soon as the car leaves pit lane. The team needs to know how much fuel is consumed per lap, how many laps the car can complete on a tank, how much fuel must be carried to finish, whether a stop is needed, where the pit window sits, and what lap-time penalty comes from carrying fuel. Those questions are not background trivia. They define the lap you are being asked to drive. If you are told to save fuel, the real instruction is not simply go slower. The real instruction is spend less fuel per lap while losing the smallest useful amount of time, then keep repeating that choice as the car changes.
That is the difference between fuel saving and driving a fuel number. Fuel saving can become emotional. You lift here, coast there, grab a different gear once, brake too early on another lap, then hope the tank tells a good story at the end. Driving the number is measured. You know the baseline. You know the target. You choose the parts of the lap where the fuel cost is high and the lap-time cost is acceptable. You compare the result. You keep asking why the data looks the way it looks. Then, as the fuel load burns off and the balance changes, you adapt without losing the target.
This lesson lives beside tire-management lessons, but it is not the same skill. Tire lessons ask how to manage heat, slip, and wear. This lesson asks how to manage fuel consumption, range, balance, and consistency. The two overlap because the same driver inputs affect both, but do not let that overlap blur the objective. Here the unit of success is fuel per lap plus race time, not tire temperature or tire life.
The principle
The principle is simple: drive the fuel target through a planned input pattern, then keep recalibrating that pattern as the car gets lighter and the balance shifts.
There are four parts inside that sentence. First, the target is per lap. Race fuel economy is normally useful to you as consumption per lap, not as road-car mileage. Second, the pattern must be planned. You do not save fuel by scattering random coasting and lifts across the lap. You save it by deciding where the trade is least painful. Third, the pattern must be repeatable. A single clever lap does not fix a race if the next five laps wander all over the fuel number. Fourth, the car changes. A lighter load can reduce lap times, and fuel burn can lower the center of gravity. If the fuel cell is not centrally located, the longitudinal balance can change as well. The same fuel-save plan may not feel identical in lap five and lap twenty-five.
The mechanism matters because it keeps you from using magic thinking. Fuel burned by the engine can be estimated several ways. A tank-level sensor may give a direct signal, but its usefulness depends on how well the sensor is mounted. Flow can be measured between tank and engine, but supply and return fuel temperature can change density, so temperature compensation matters for accuracy. A modern motorsport ECU can calculate fuel use from injector operation. The ECU works from engine RPM and load, determines injector timing, and the amount of fuel passing through an injector is tied to opening time and flow rate. For you as the driver, that means your throttle shape, engine load, gear and RPM choices, and acceleration demand all matter, but they only matter in the way the measured system proves they matter.
That last phrase is important. Do not assume one trick is always best. The data sources in this bond keep returning to comparison: overlay laps, look for differences, prioritize the biggest delta, use other channels to check, and ask why. Fuel work is not just about a fuel-flow number. You also need speed, throttle, brake pressure, gear, RPM, GPS line, segment time, and sometimes steering or total steer angle. If a lap uses less fuel but loses the race in one bad segment, that is not a good fuel lap. If a lap is fast but consumes too much to finish the stint, that is not a good race lap. The skill is choosing the compromise deliberately.
Translate strategy into a lap you can drive
Before you can drive the number, you need the number translated into driver language. The engineering version might be liters per lap, gallons per lap, laps to empty, or projected fuel remaining at the end. The driver version is a repeatable lap plan. You need to know whether the race requires normal push pace, mild conservation, a hard save to open or close a pit window, or a late correction because the real consumption is worse than expected.
Start with the four strategy questions. How much fuel is being consumed per lap? How many laps can be completed on the tank? How much fuel load penalty is being carried, and what does that do to lap time? How does the car balance change as that load burns away? Those questions define the size of the problem. If the required fuel number is close to the natural number, you may only need to clean up waste. If the required number is far away, the lap plan needs obvious, intentional save zones, and the team needs to accept the lap-time cost.
Then turn the number into zones. A zone is a part of the lap where you will change one thing and then measure it. Good zones are easy to repeat and easy to see in data. A long full-throttle run before a heavy brake zone may be a candidate for a small earlier release if the data proves the time cost is acceptable. A place where you habitually apply throttle too early and then lift is a candidate for cleaning up the application, because the trace already shows waste. A place where you are coasting without a plan may be a candidate for either making the coast intentional or removing it. A fast corner with an unplanned lift is usually a warning sign, because the cost in speed and confidence can be larger than the fuel benefit.
Do not build the lap around six different experiments at once. If you change throttle timing, gear, brake point, and line in every major corner, the data will show differences but will not tell you what caused them. Keep it simple. Pick one or two changes, drive them repeatedly, and compare them against the baseline. That is how you convert a strategic instruction into a usable control plan.
Establish the baseline
A baseline is not just your best lap. For fuel strategy, a baseline is the normal version of the lap with enough channel data to explain where the time and fuel go. You want the lap that represents your sustainable race pace, not a qualifying-style outlier. If you only compare against a single hero lap, you may reject a useful fuel plan because it looks bad against a lap you cannot repeat over a stint.
The minimum baseline is lap time, fuel used per lap, and a few channel traces. Throttle position tells you where you are full, partial, hesitant, coasting, lifting, or applying too early and backing out. Brake pressure tells you whether the brake event is hard and short, light and long, whether there is a long tail, and whether pressure varies lap to lap. GPS speed shows where speed is gained or lost. Gear and RPM show the engine operating pattern. Segment or section reports show where the time loss actually lives. Delta or compare time helps you prioritize the biggest differences instead of chasing noise.
Once you have the baseline, overlay it with a candidate fuel-save lap. Do not stare at the whole trace at once. Find the biggest time differences first. Then identify what changed at those points. Was the speed reduction caused by throttle lift, brake application, steering angle, line, or traffic? The Data for Drivers material is blunt about this: data generates questions, and data does not answer all of them by itself. That is exactly the right mindset. If the red lap is slower at a point, you still have to ask why. If the why is a planned early release that saved enough fuel, the loss may be acceptable. If the why is a fear lift, traffic, a missed shift, or a confused line, it is not a fuel strategy.
A useful baseline also includes your reference-point feel. At intermediate level, you should be able to say where the lift starts, where the brake pressure rises, where the brake release begins, when the car accepts the turn, when the throttle starts, and whether the exit requires a correction. That driver feel is not a substitute for data, but it helps you interpret data. If the trace shows a lift in a fast corner and your memory says you were not confident in the line, the answer is not simply fuel. It may be vision, mental image, traffic, or commitment. The data points you to the question.
Choose fuel-save zones by cost, not habit
The common bad fuel-save habit is saving a little everywhere. It feels responsible, but it often produces a dirty lap: early brake points, vague coasting, lost exits, poor rhythm, and no clear evidence of which change helped. A better approach is to choose zones by cost. You want the parts of the lap where a small reduction in demand produces a measurable fuel benefit and the smallest strategic time loss.
The first candidate is waste cleanup. If the throttle trace shows early application leading to a lift, that is not an elegant fuel-save technique. It is an input that did not match the car or the corner. Clean it up by delaying the application until you can keep it committed, or by making the first application smoother and more certain. You may save fuel because the engine spends less time in unnecessary load, and you may also save time because the car is not being asked, released, and asked again. The key is that the trace must confirm the change.
The second candidate is a planned release before a braking zone. This is not random coasting. It is a precise earlier end to the acceleration phase, followed by the same brake reference discipline and a clean corner entry. If the release is too early, you give up a lot of straight-line speed. If it is too late, you may save almost nothing. The right version is visible in speed and throttle data: the throttle comes off earlier by plan, the brake event remains controlled, the minimum speed and exit do not collapse, and the time loss is concentrated where you intended.
The third candidate is reducing avoidable acceleration events. A sloppy corner exit can force you to breathe the throttle, correct the car, then accelerate again. A missed gear or inconsistent shift can show up as an abnormality in the data and can also disrupt the fuel plan. The race-strategy material treats driver consistency as a major factor over a race distance, and fatigue can show up as gear-shifting mistakes, changes in throttle blipping, earlier braking points, and other abnormalities. In fuel work, those are not just driving-quality problems. They are strategy problems, because they make consumption and lap time less predictable.
The fourth candidate is gear and RPM experimentation, but only if you have data support. Since ECU fuel calculation is tied to RPM, load, injector timing, and injector flow, gear and RPM can matter. But this bond does not support a universal rule such as always use the taller gear or always short shift. The correct instruction is to test the candidate and compare fuel used, lap time, exit speed, and downstream effect. One method may help in one type of corner and hurt in another. That is why you compare not only lap time but also straightaway speeds or RPM at reference points.
Keep braking and corner entry stable
Fuel saving often goes wrong at the brake pedal. You lift early, arrive at the brake zone at a different speed, then brake vaguely because the rhythm has changed. That can produce a long, light brake trace, a rolling entry, a missed apex, and a weak exit. The lap may use less fuel, but the time loss is uncontrolled.
The better method is to separate the fuel-save decision from the brake-quality decision. If your plan is an earlier release, make the release the experiment. Then still brake with a shape you can repeat. The data material suggests looking at brake pressure shape, initial application, trail, long tail, inconsistency, and light-long versus hard-short events. Use those as your checklist. A clean fuel-save lap should not turn every brake zone into a different brake technique unless that is the planned experiment.
Going Faster breaks corner entry into useful blocks. The throttle-brake transition can range from a slow cautious lift to a rapid move from full throttle to heavy brake pressure. Straight-line deceleration uses the tire primarily for braking, and there are cases where you may brake at less than threshold. Brake-turning combines deceleration and direction change. Those blocks help you diagnose a fuel lap. If the fuel-save release changes your arrival speed, you may not need the exact same brake pressure, but you still need a deliberate throttle-brake transition, a controlled straight-line deceleration phase, and a clean brake-turn if the corner requires it.
The mistake is letting conservation erase precision. A fuel number does not excuse lazy braking. It demands more precision, because you are trying to change one part of the lap without contaminating the rest. If the brake trace becomes inconsistent, the data cannot tell whether the fuel-save plan is good. It can only tell that the driver stopped repeating the lap.
Adapt as the fuel burns off
The car is not the same car at the end of a stint. As fuel load drops, the performance potential changes. The car is lighter, lap times may decrease, and center of gravity height can decrease. If the fuel cell is not centrally located, the longitudinal balance can also change. You may feel this as a change in braking stability, rotation, midcorner balance, traction, or the timing of when the car accepts throttle. The exact feel depends on the car and the fuel-cell location, so do not invent a direction before you have evidence.
Your first job is awareness. During the stint, ask whether the car is changing in entry, middle, or exit. Is the understeer or oversteer beginning earlier? Does the car need a different speed at turn-in? Does the brake release need to move? Can you get back to power at the same place, or does the car ask for a different timing? Bentley's adaptation material is useful here because it treats style as variable. You adapt to understeer or oversteer by changing line, turn-in speed, brake release, and power timing, then compare reference-point RPM or straightaway speed and lap time to see what worked.
This matters for fuel because the best conservation method may change with balance. Early in the stint, a heavier car may punish a lazy entry or a long brake tail differently than it does later. Later in the stint, the lighter car may make the planned save zone less costly, or it may make a different zone more attractive. The rule is not to chase the car every lap. The rule is to notice when the same plan stops producing the same result.
Use two layers of evidence. The first is your feel: entry stability, rotation timing, throttle confidence, and whether you are making corrections. The second is data: brake pressure shape, throttle trace, speed, segment time, gear, RPM, GPS line, and reference speed or RPM on a straight. Lap time alone can hide the story. You may gain in one corner because the lighter car rotates better and lose on the next straight because your exit got worse. That is why the source material warns that lap time may not tell the real story and that straightaway speeds should be compared as well.
Protect the race with consistency
Fuel strategy is not won by one clever lap. It is won by a string of laps that hit the number closely enough to preserve the race plan. Driver consistency is treated in the strategy material as the third important factor after fuel and tire behavior. A driver can be faster in a qualifying lap and still lose over a race distance through degradation in lap times. Physical condition and concentration matter, and the data may show fatigue as driving errors.
For fuel work, late-stint errors have two costs. They cost time directly, and they damage the prediction. A missed shift changes the engine pattern. Earlier-than-normal braking changes speed and segment time. A change in throttle blipping or throttle timing changes the trace. If the team is trying to project whether you can make the finish or hit a pit window, inconsistency makes the projection less trustworthy.
Your mental task is to keep the fuel lap boring in the right way. Same planned release. Same brake shape. Same apex discipline. Same return to throttle. Same review of whether traffic forced a deviation. If traffic, a yellow, or a battle changes the lap, label that lap mentally and in the post-session review. Do not let one traffic lap become proof that the fuel plan works or fails.
This is where an intermediate driver can make a big jump. You do not need prototype-level fuel software to improve. You need a clean process: baseline, target, planned zones, repeatable execution, comparison, and adjustment. That is enough to make you useful to the race strategy instead of being a variable the strategy has to survive.
What to look at after the run
After the session or stint, start with the strategy number. What was the measured fuel use per lap? How many laps would that complete on the available tank? Did the number support the pit window or race distance? If your system uses tank level, remember that sensor mounting affects signal quality. If it uses flow measurement, remember that supply and return temperature can affect density. If it uses ECU calculation, remember that injector opening time needs to be scaled correctly to fuel used. As the driver, you may not perform those calculations yourself, but you should know which signal the team trusts.
Then review the lap execution. Overlay the baseline and the fuel laps. Use delta or compare time to find the biggest differences. Identify the difference before judging it. Look at throttle for coasting, hesitation, early application followed by lift, and fast-corner lifts. Look at brake pressure for shape, inconsistency, and long tails. Look at gear and RPM for changed engine patterns. Look at GPS line if the time loss might be from line rather than fuel technique. Look at segment times to see whether the loss is concentrated in the planned zones or scattered across the lap.
Finally, ask why. A slower lap is not automatically a good fuel lap. A lower-fuel lap is not automatically a good race lap. A clean fuel lap is one where the measured consumption moved toward the target, the time loss appeared where you planned it, the rest of the lap stayed stable, and the car's changing balance was handled without emergency corrections. That is the standard.
Worked example: building the race number from practice fuel data
Imagine practice gives the engineer enough data to answer the basic race-strategy questions. The team calculates fuel consumed per lap, estimates how many laps can be completed on a tank, and decides whether the race can be finished without refueling or where the pit window must open. That is the engineering layer. Your job begins when that result turns into a driver instruction.
If the car naturally uses more fuel per lap than the race plan allows, do not ask for a vague instruction. Ask where the first experiment should happen. The clean driver version might be: keep the normal line and brake references, release the throttle slightly earlier before the heaviest braking zone, avoid the known early-throttle-then-lift corner, and repeat that for four laps. After the run, compare those laps against the baseline. If fuel per lap improves and the time loss is concentrated in the planned zones, the plan is becoming usable. If fuel improves but speed collapses in unrelated corners, the lap was not disciplined enough. If fuel does not improve, the chosen zones were not strong enough or the measurement does not support the assumption.
This example also shows why the fuel-measurement method matters. Tank level is simple, but signal quality depends on sensor mounting. Flow measurement can work, but density changes from temperature differences between supply and return fuel must be handled for accuracy. ECU calculation can use injector opening time, RPM, load, and injector flow, but that calculated channel still has to be scaled into fuel used. You do not need to become the engineer, but you do need enough literacy to know whether the number you are chasing is trustworthy.
Worked example: using a Lime Rock Park overlay without inventing the answer
The bonded Data for Drivers example shows a Lime Rock Park overlay with GPS speed, throttle position, front brake pressure, and time lost against distance. The useful lesson is not that the red lap saved fuel. The chunk does not say that. The useful lesson is how to interrogate a lap difference.
Suppose you run a normal lap and a candidate fuel-number lap at Lime Rock. The compare-time trace shows the biggest loss in one section. You do not immediately declare the fuel lap too slow. You identify the difference. Did you lift the throttle? Did you brake? Did you add steering angle? Did traffic change the line? Was the reduction in speed caused by the planned release, or by uncertainty? If the throttle trace shows the planned release before a braking zone and the brake trace stays clean, the time loss may be acceptable. If the trace shows a fast-corner lift that was not in the plan, the fuel number may be hiding a confidence or line problem.
That is the discipline you want from every fuel review. The overlay gives you questions. It does not give you all the answers. Your memory of traffic, vision, mental image, and confidence fills in the human part. Then the next session gets one cleaner objective, not a pile of guesses.
Worked example: the light car that changes balance late in the stint
Now imagine a car whose fuel cell is not centrally located. The race-strategy material warns that as fuel level drops, center of gravity height decreases and longitudinal balance can change. The exact direction is car-specific, so you do not get to assume the car will always become easier or always become nervous. You have to read it.
Early in the stint, your fuel-save plan may be a small earlier release before one major braking zone plus a cleaner throttle pickup in a corner where you used to apply early and lift. Midway through the stint, the lighter car starts reaching the same brake marker differently. You feel that the brake release that worked early now leaves the car rotating at a slightly different time. If you ignore that, you may add steering correction, delay throttle, and lose the exit. If you overreact, you may abandon the fuel plan and chase lap time. The correct response is smaller and more disciplined: keep the planned save zone, adjust the brake release or turn-in speed enough to match the changed balance, then check reference speed or RPM on the next straight.
The point is not to make a setup change from the cockpit. The point is to keep your driving style adaptable. Bentley's adaptation work supports trying different line, turn-in speed, brake-release, and power-timing choices, then comparing data and reference points. In a fuel stint, that adaptability protects both the fuel number and the lap time.
Common mistakes
The first mistake is saving fuel everywhere. It feels safe, but it produces an unmeasurable lap. The good version is saving in named zones with named inputs, then checking whether the time loss appears where expected.
The second mistake is turning the brake zone into mush. A planned early release should not automatically become a long vague brake event. The good version is a clear throttle-brake transition, a brake-pressure shape you can repeat, and a corner entry that still lets you hit the line.
The third mistake is trusting lap time alone. A fuel lap can look acceptable on total time while losing too much speed onto a straight, or it can look poor because one planned segment carries all the loss. The good version is comparing segment time, straight reference speed or RPM, throttle, brake, gear, and GPS line.
The fourth mistake is blaming the car for every change. Fuel burn can change balance, but traffic, fatigue, missed shifts, vision, mental image, and inconsistent braking can also change the data. The good version is to ask why before changing the plan.
The fifth mistake is trusting a weak fuel signal. Tank-level data depends on sensor mounting, flow data needs careful treatment, and ECU fuel use requires correct scaling. The good version is to know which measurement your team trusts and to avoid overreacting to a single questionable lap.
The sixth mistake is ignoring late-stint fatigue. The strategy material lists gear-shifting mistakes, changes in throttle blipping, earlier braking points, and other abnormalities as signs that consistency is degrading. The good version is to keep the fuel lap simple enough that you can still execute it when you are tired.
Drill: three-session fuel-number progression
Run this drill at the next event only when traffic, rules, and coaching context make it appropriate. The count is three sessions, with four measured laps per session after warm-up. The success criterion is three consecutive measured laps where the planned fuel-save zones are visible in the trace, the lap-time loss is concentrated in those zones, and the rest of the lap does not pick up unplanned fast-corner lifts, brake inconsistency, or gear/RPM abnormalities.
Session one is the baseline. Drive four sustainable race-pace laps with no fuel-save experiment. Record fuel used per lap if the car can provide it. Save throttle, brake pressure, speed, gear, RPM, GPS line, and segment times. After the session, pick the two largest candidate zones by comparing where fuel demand and lap-time cost appear to make sense. Do not pick more than two.
Session two is the first fuel-number run. Apply only the two chosen changes. For example, make one planned earlier release before a major braking zone and clean up one corner where the throttle trace showed early application followed by a lift. Do not change every corner. After the session, overlay the baseline and fuel laps. If the biggest time loss is not in the planned zones, the execution was not clean enough. If the loss is planned but the fuel number does not move, the chosen zones are probably not useful enough.
Session three is the changing-car run. Repeat the same plan later in the day or with a meaningfully different fuel load if available. Pay attention to whether the car asks for a different brake release, turn-in speed, or power timing. The goal is not to set a fast lap. The goal is to keep the same fuel strategy alive while adapting to the car's balance. Afterward, compare straight reference speed or RPM as well as lap time, because a change that helps one corner can cost the next straight.
Cross-references
Use the tire-management lessons when the problem is heat, slip, and degradation. Use this lesson when the problem is fuel per lap, tank range, pit window, fuel-load balance, and repeatability. Use Spend the car where it pays when you need to decide which parts of the lap deserve risk, grip, or time loss. The shared habit across all of them is measured compromise: make one deliberate change, compare it, ask why, and carry forward only what the evidence supports.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | Analysis Techniques for Racecar Data Acquisition (Jorge Sergers) | 3c4d0a78b3d803ea85783514e06ce387 | 19 | 1 | uio_books_raw_v1 |
| 2 | Analysis Techniques for Racecar Data Acquisition | 79921028-b3b8-48ea-496d-c91d0bf02af4 | 20 | 1 | uio_books_raw_v1 |
| 3 | Analysis Techniques for Racecar Data Acquisition | 63fef2f3-088c-8d13-939d-10bf5e81e21f | 20 | 1 | uio_books_raw_v1 |
| 4 | Data-for-Drivers-PRINT | c76265b3-e38e-d9dd-45b1-10446beb0a9b | 11 | 1 | uio_books_raw_v1 |
| 5 | Data for Drivers | cabda699642b26311b0a7ef998da2c71 | 15 | 1 | uio_books_raw_v1 |
| 6 | Ultimate Speed Secrets - Ross Bentley | c5789e88-5571-d188-9c4a-ff8f5751f88b | 503 | 1 | uio_books_raw_v1 |
| 7 | Going Faster Mastering the Art of Race Driving - Carl Lopez | 3b70eb1f-e4e3-c70c-1221-c2c8a8e43d83 | 51 | 1 | uio_books_raw_v1 |
| 8 | Data-for-Drivers-PRINT | b80dc634-a0a7-d6de-d470-353aed47e2a6 | 17 | 1 | uio_books_raw_v1 |