Manage fuel, oil, and coolant between sessions
Generated from
content/lms/race-car-engineering-and-operations/01-paddock-logistics/02-fuel-and-fluid-logistics.md; edit the source file, not this page.
Source path: content/lms/race-car-engineering-and-operations/01-paddock-logistics/02-fuel-and-fluid-logistics.md
Course: Run the paddock like a race engineer
Module: Build a paddock that works
Estimated duration: 55 minutes
Lesson aim
You are learning a session-survival skill, not a shelf-storage skill. Fuel, oil, and coolant work is successful when the car leaves for grid with enough fuel to finish the session, the oil and water systems have been checked at the right temperature, the driver knows what the gauges should be doing, and the crew has not created a rushed last-minute problem while trying to fix a simple one. At the intermediate level, you should already know how to open the hood, read the gauges, add fuel or oil when appropriate, and notice obvious leaks. The skill here is turning those actions into a repeatable loop that protects track time.
This lesson deliberately stays narrower than paddock layout and tire staging. The paddock-layout lesson decides where the fuel jugs, funnel, towels, extinguisher, checklist, and logbook live. The tire-staging lesson handles pressures and wheel timing. This lesson starts when the car returns hot from track and ends when it is ready to leave again without guessing.
The operating principle
Your fluid plan has to answer three questions before every session. Will the car have enough fuel to complete the time or distance? Are oil level and oil temperature under control? Is coolant temperature under control, and does the cooling system still have enough water to register correctly? If any one of those answers is uncertain, you do not have a logistics problem later. You have a session problem now.
The reason is simple. A track session compresses consequences. A street car can run errands with vague fuel planning and casual temperature awareness. A track car spends a lot of time at high load, then comes back heat-soaked, then gets sent out again on a schedule that does not care whether you are organized. The MORPCA driver-education guidance treats the post-run car check as preparation for the next outing, not as optional housekeeping. It specifically calls out oil level and temperature, coolant temperature, fuel level, and brake condition as things to inspect or monitor around sessions. That is the mindset: the next session is being won or lost while the current one is cooling.
Fuel, oil, and coolant also affect the driver, not just the mechanic. Fuel load changes weight, and older race-driving guidance points out that a car may handle differently with full tanks than it does with nearly empty tanks. Oil and water temperatures set the boundary for how hard the engine should be treated, especially during warm-up. Coolant temperature and a missing coolant reading are warning signs that can end a session early. The driver who treats the fluid loop as a boring chore is usually the driver who discovers the problem at the worst possible time.
The session loop
Run the same loop every time: return, stabilize, inspect, decide, record, warm, final-check, grid. The order matters because heat and time matter.
Return means you finish the session without cooking the car further than necessary. On the cool-down lap and paddock return, use the brakes as little as possible so you are not pushing more rotor heat into the calipers and brake fluid while you are already done learning for that session. When you park, leave the car in gear and avoid the parking brake. That specific brake practice is outside the fuel-oil-coolant core, but it protects the same turnaround window. A car that returns with one system overheated often turns a simple fluid check into a broader fire drill.
Stabilize means you do not immediately treat a hot car like a cold car. The bonded material does not support detailed coolant-cap handling, expansion-tank technique, or exact waiting times, so do not invent them here. The supported point is more basic and more important: the post-run inspection is preparation for the next outing, and oil and coolant temperatures are part of that inspection. You need a moment to read the car as it is, not as you hope it is. Look at the gauges before shutdown when possible, look under and around the car after shutdown, and let the car tell you whether the next step is normal service or problem diagnosis.
Inspect means you check the same items in the same sequence. Fuel level first if the next session is time-limited and the fuel source is away from your paddock spot. Oil level and oil temperature next, because the guidance says to check oil level every couple of sessions and add oil if needed, while also building the habit of monitoring the oil gauge on track. Coolant temperature next, because a red-zone reading or no reading can mean the session should end and the car should cool. Leak scan last, because a fluid level is not meaningful if the system is actively losing fluid.
Decide means you turn the inspection into an action. If you are not sure the fuel will last the whole session, add fuel. That is not a conservative personality trait; it is the explicit driver-education rule. Running out does not just cost you a lap. It can consume everyone else’s track time while the disabled car is retrieved. For oil, decide whether the level is acceptable according to the car’s normal procedure, then add only if needed. For coolant, decide whether the temperature trend is normal enough to continue or abnormal enough to stop and cool. The lesson is not to top everything off blindly. The lesson is to close each uncertainty before you leave for grid.
Record means you preserve what you learned. Fuel consumption can be worked out, and once it is worked out you can choose the fuel necessary for the distance plus a safety margin. In a race, that margin should be as small as reasonable because excess fuel is excess weight. In HPDE, the safety margin is normally larger because losing a session to a tow is worse than carrying a few extra gallons. Either way, recording matters. If you do not record session length, fuel added, oil added, coolant behavior, and temperature notes, you are relying on memory in a noisy paddock.
Warm means you treat the engine as a system with temperature limits. Van Valkenburgh’s race-car mechanics guidance is blunt on this point: do not rev a race engine, or any engine, before it has had a chance to warm up. The supported procedure is to hold the engine at the minimum smooth running speed until oil and water temperatures reach roughly 140 to 160 degrees. Dry-sump cars can help the process by pre-warming the oil tank for about an hour before start. The lesson for your operation is that warm-up is not a sound check. It is a temperature check.
Final-check means you re-check after the warm engine has changed the state of the car. The mechanics guidance puts oil and water levels, leaks, belt tension, hot valve lash, hot torques, and a last visual inspection after the engine is warm. Your club car may not need all of those race-car checks every session, but the principle transfers cleanly: the last useful check is after the engine has circulated fluid and built temperature, not before the car has shown whether it leaks, pressures up, or behaves normally.
Grid means you leave with no open fluid questions. If the fuel level is a guess, you are not ready. If the oil gauge did something odd on the last session and nobody has looked at it, you are not ready. If the coolant temperature touched the red zone or stopped reading and you are hoping it was a fluke, you are not ready. Intermediate drivers earn pace by making the boring decisions early enough that the exciting decisions happen on track.
Fuel: enough, but not thoughtless
Fuel planning has two different targets depending on whether you are doing HPDE sessions or competition stints.
For HPDE, the fuel rule is simple: if you are not sure, add fuel. The source guidance is practical rather than theoretical. You will be surprised how quickly the car uses gas at track pace, and you do not want to be the reason a session goes yellow or stops for a tow. In a novice group, that advice is usually enough. At the intermediate level, you can keep the conservative behavior while adding a better method underneath it.
Your method is a small fuel log. Before the session, note the starting level in the most reliable unit your operation can support. That might be gallons added, a fuel-cell sight mark, a dashboard range estimate you already know is crude, or a scale number if your program is more developed. After the session, note session duration or laps, then note how much fuel it takes to return to the planned starting level. After several sessions, you will know the car’s normal burn for that track, run group, and driver pace.
Do not pretend one number is universal. The bonded material repeatedly warns that changing conditions change the baseline. Aerodynamic testing guidance makes the broader data point: meaningful results require discipline, one variable at a time where possible, averages rather than single laps, and periodic returns to baseline when conditions change. Although that passage is about aero tests, the method applies directly to fuel logistics. If your fuel burn appears different after the driver got faster, the track cooled, traffic changed, or tire deterioration changed lap pace, you need to record the context instead of treating one session as law.
For competition, the fuel target gets sharper. Frere’s race-driving discussion says that once consumption has been worked out, the tank should carry only the fuel needed for race distance plus a safety margin that is as small as reasonable, because the car should stay as light as possible. That is a different operating point from HPDE. In a race, excess fuel costs acceleration, braking, and possibly handling. In a learning session, excess fuel mostly costs a little performance while buying certainty. Know which game you are playing.
Fuel load also changes how the car feels. The car may handle differently with full tanks and nearly empty tanks, and race setup may need to compromise toward full-tank handling because the start is strategically important. For your lesson, the important driver action is awareness. If the first session after a fuel fill feels heavier, slower to rotate, or different in long corners, do not immediately blame tire pressure, alignment, or yourself. Fuel state is one of the variables. Record it.
Fuel logistics has one more safety habit: pressure and leak awareness. Before starting, the mechanics guidance says water level, oil level, throttle action, and similar checks should already be done, then fuel pumps should be turned on until pressure stabilizes and the fuel system checked for leaks. Do not skip that because the car ran fine last time. A fuel system that leaks only when pressurized may look dry until you prime it. The right time to find that is in the paddock with the car stationary, not at pit-out.
Oil: level, temperature, and warm-up discipline
Oil logistics has two jobs. First, there must be enough oil. Second, the oil must be warm enough and controlled enough to do its job before you ask for track-load rpm.
The driver-education source gives you the session habit: check oil level every couple of sessions and add oil if needed. It also tells you to build the habit of watching the oil gauge on track and monitoring oil temperature, with the back straight named as a good place to do it. That is not a random location. A straight gives you more attention budget than a braking zone, turn-in point, or place where you must solve traffic. Frere makes the same attention principle in the context of pit signals: information should be given where the driver can look without danger, not where the driver is choosing a line or braking. Apply that to your gauges. Decide before the session where the oil glance belongs.
Oil temperature also controls warm-up behavior. Van Valkenburgh’s guidance says to hold the engine at the minimum smooth running speed until oil and water temperatures are in the 140 to 160 degree range. The exact target for your car may come from its builder, but the supported operational rule is not negotiable: do not use throttle blips and free revs as a paddock ritual while the oil is cold. A smooth idle or low-speed warm-up is not wasted time. It is how you keep the engine out of unnecessary stress before the session even begins.
Dry-sump cars add a logistics opportunity. The source notes that dry-sump oil tanks can be helped by wrapping the tank with electrical heating tape and pre-warming the oil for an hour or so before the engine is started. That is not a universal instruction for every street-based HPDE car, and the lesson should not turn it into one. The transferable idea is that some cars need pre-session thermal planning, not just a key turn. If your car has a dry sump or race oil system, warm-up belongs in the schedule, not in the last five minutes before grid.
A good oil routine has three readings. The first is the pre-start level check. The second is the on-track temperature and pressure awareness, placed on a straight where the glance is safe. The third is the post-warm or post-run re-check when the car has circulated oil and revealed leaks. If those three readings agree with the car’s normal pattern, you have confidence. If they do not agree, you have a reason to slow the operation down.
What you should not do is turn oil service into guesswork. Do not add oil because somebody else always adds oil. Do not ignore a gauge because the car sounds fine. Do not wait until grid to discover you need a quart. The intermediate driver’s standard is not mechanical genius. It is repeatable attention.
Coolant: temperature tells you whether the next lap is allowed
Coolant logistics is less about topping up between every session and more about respecting the temperature signal. The driver-education guide says to monitor coolant temperature regularly while on track. It also gives a clear decision rule: if the reading is in the red zone or there is no reading because there may be too little coolant, end the session early and let things cool down.
That rule is intentionally simple. You do not troubleshoot a cooling system at full speed. You reduce the demand and bring the car in. An intermediate driver sometimes wants to finish the lap, finish the session, or see if the gauge comes back. That is the wrong mindset. A coolant gauge that has gone red or stopped giving a trustworthy reading has already changed the objective. The objective is no longer lap time or instruction time. The objective is preserving the car and staying predictable for the group around you.
Coolant belongs in the pre-start and warm-up loop too. The race-car mechanics guidance includes water level among the checks that should already be completed before start, then says the engine should be warmed until oil and water temperatures are in the target range before revving. After warm-up, oil and water levels and leaks are part of the last-minute check. You do not need to turn that into an elaborate ritual. You do need to make coolant part of the same closed loop as oil: level before, temperature during, condition after.
The most important coolant sub-skill is early recognition. If you only look at the gauge when something smells wrong, you are late. Choose a location on the lap where a short glance is safe. The MORPCA guide names the back straight for oil-gauge habits; the same attention logic can include coolant temperature if your display allows it. The glance should not happen where you are braking, turning in, or managing a passing point. A gauge check that steals attention from car placement creates a new risk while trying to avoid an old one.
Leak checks and fire readiness
Fluid logistics is not complete until you know the fluid stayed inside the system. The fuel pump check is the clearest example: turn the pumps on until pressure stabilizes, then check for fuel leaks. It is easy to skip because it feels like a race-car detail, but the logic applies to any pressurized fuel system. Check it when the car is stopped, cool enough to inspect, and not blocking anyone.
The cold-start passage also warns that too much fuel pumping can contribute to a backfire through the inlet and a small fire. The suggested response in that context is a large clean rag or a CO2 extinguisher, with chemical extinguishers noted as messy afterward. Do not stretch that into a full fire-training lesson from this bond. The supported lesson is narrower: fuel work, start-up work, and fire readiness are connected. If your fuel procedure includes priming, pumping, or repeated starting, the extinguisher and a calm helper should not be far away.
Leak scanning is also how you avoid false confidence. A car can show an acceptable level at one moment and still be losing fluid. Look under the car. Look around fittings you can see. Smell for fuel. Notice fresh wetness. If the car just came in hot, do not rush your hands into places the bonded corpus does not instruct you to touch; keep the inspection visual unless your normal shop procedure says otherwise. The skill is catching the obvious leak before it becomes a session-ending leak.
Data discipline without turning the paddock into a lab
The aero-testing chunks are useful here because they teach how not to fool yourself. In the wing-test example, each configuration was run for five laps, only the wing was changed, averages were used, odd laps were discarded, and the baseline was revisited because weather, track conditions, and tire deterioration can move the target. You are not doing aero development in this lesson, but the paddock mistake is the same: you change three things, remember none of them accurately, then make a confident conclusion.
Use that discipline lightly. For a club weekend, your fluid log can be a few lines per session: session number, laps or minutes, fuel added, oil added, oil temperature note, coolant temperature note, any leaks, and driver comment. If you are racing, add starting fuel load and expected stint distance. If you are testing, add one controlled variable and avoid changing other things at the same time.
This record protects you from two traps. The first trap is underfueling because you remember the easiest session, not the hardest one. The second trap is overreacting to a single abnormal session. If lap times, traffic, weather, tire condition, and fuel load all changed, the fluid result needs context. A disciplined log does not make you slower. It keeps you from being busy in the wrong direction.
Sub-skills that make the loop work
The first sub-skill is forecasting. Before the session, you predict fuel need from the last sessions, then add a margin appropriate to HPDE or racing. In HPDE, uncertainty means more fuel. In racing, once consumption is established, the goal is fuel for distance plus the smallest reasonable safety margin.
The second sub-skill is attention placement. You decide where on track you will glance at oil and coolant information. A straight is appropriate because the driver-education source names the back straight as a good place to check the oil gauge, and the racing source warns that information should not be presented where the driver must brake or choose a line. Put the gauge glance where it costs the least attention.
The third sub-skill is warm-up restraint. You keep the engine at the minimum smooth running speed until oil and water are warm enough. This is harder than it sounds in a paddock full of noise, time pressure, and people who judge readiness by sound. You judge readiness by temperature.
The fourth sub-skill is pressure-state leak checking. A fuel system should be checked after pumps run and pressure stabilizes. A warm engine should get a last visual inspection after it has circulated oil and water. The point is to inspect the system in the state that reveals the problem.
The fifth sub-skill is context logging. Fuel burn, temperature trends, and handling feel only mean something when attached to session length, conditions, and fuel load. This is where the data-testing discipline transfers: keep the baseline visible and do not change everything at once.
Calibration cues
You know the skill is improving when the car leaves for grid without last-minute fluid questions. The fuel amount was chosen before the five-minute call, not during it. Oil level was checked on the planned cadence, and oil temperature was watched in the same safe place each session. Coolant temperature was monitored, and any red-zone or missing-reading event changed the plan immediately. The fuel pump and leak check happened before the car was committed to pit-out.
You will also see a calmer paddock rhythm. A good fluid routine is boring. You return, inspect, record, decide, and prepare. There is no debate over whether the car can make it. There is no driver already strapped in while someone is searching for a funnel. There is no fuel run while the group is being called. Those are not personality victories. They are evidence that the loop is early enough.
The data will improve too. After a few sessions, you can say what the car normally burns in a session and what margin you used. You can say whether the oil temperature stabilized, climbed, or changed after a driving change. You can say whether coolant temperature was normal or whether the car needed to cool. If you race, you can connect fuel planning to stint distance and adjust the first refuelling stop conservatively if actual race conditions may burn more than practice suggested.
Failure modes and recovery
The first failure mode is the hopeful fuel call. It sounds like confidence, but it is really missing information. The symptom is a driver saying there is probably enough fuel because the gauge is not empty. The cost is a disabled car and lost track time. The recovery is immediate: if you are not sure, add fuel for HPDE. If you are racing, improve the fuel log so the next call is based on worked-out consumption and a deliberate margin.
The second failure mode is cold-engine noise. The symptom is revving during warm-up because the engine starts and sounds ready. The cost is unnecessary stress before oil and water are at temperature. The recovery is to hold the engine at minimum smooth running speed until the temperatures are up, and to build any dry-sump oil pre-warm into the schedule when the car requires it.
The third failure mode is late gauge attention. The symptom is discovering oil or coolant trouble only after the car feels wrong. The cost is that you have already spent the cheap warning. The recovery is to pick a safe straight and make the gauge glance part of the lap routine. If coolant goes red or gives no reading, end the session early and let the car cool.
The fourth failure mode is blind top-off behavior. The symptom is adding fluid because it feels responsible, without knowing what changed or why. The cost can be extra fuel weight, hidden oil consumption, or failure to notice a leak. The recovery is to inspect, decide, and record. Add fuel when uncertain in HPDE. Add oil if needed. Treat coolant temperature abnormalities as stop-and-cool events rather than casual service moments.
The fifth failure mode is learning from messy data. The symptom is changing fuel load, tire pressure, setup, driver pace, and session timing, then making a strong conclusion from one result. The cost is chasing the wrong cause. The recovery is the same discipline used in track testing: change as little as practical, average observations, discard obvious outliers carefully, and return to a known baseline when conditions move.
The bottom line
Fuel, oil, and coolant logistics is not glamorous, but it is one of the places where intermediate drivers start acting like serious operators. You are not trying to become the most complicated person in the paddock. You are trying to make three answers boring: enough fuel, oil under control, coolant under control. When those answers are settled before grid, the session can be about driving. When they are not, the session is already at risk before the car reaches pit-out.
Worked example: the back-straight gauge habit
You are in a 25-minute HPDE session, and the car has been running normally. The driver-education guidance names the back straight as a good place to check the oil gauge and monitor oil temperature. Use that as a structured habit, not an occasional glance. On the first flying lap, you drive normally and confirm that the car is settled. On the next lap, when the car is straight and your hands are quiet, you take one short look at oil temperature and coolant temperature. You do not do this while braking, turning in, managing traffic, or deciding whether to pass. Frere’s pit-signal guidance supports the same rule in another form: information should be placed where the driver can attend to it without danger.
If oil temperature is normal and coolant temperature is normal, you continue. If coolant temperature is in the red zone or the reading disappears, you stop treating the session as normal. The supported action is to end the session early and let the car cool. If oil temperature is trending higher than your normal pattern but not yet at an emergency threshold, you record that after the session and compare it with fuel load, traffic, weather, and driving pace. You do not make a setup conclusion from one unsupported observation.
The success standard is repeatability. After the session, you should be able to say where you checked the gauges, what you saw, and whether the readings matched the car’s normal behavior. If you cannot remember whether you looked, the sub-skill is not installed yet.
Worked example: first refuelling in a long-distance race
In practice, your team works out fuel consumption. The race-driving source says that in long-distance racing the full tank tells you how many laps the car should run, but the first refuelling stop should be scheduled one or two laps earlier to check whether actual racing consumption is higher than practice consumption. This is the racing version of a conservative first answer.
The workflow is direct. You start with the practice burn number. You plan the first stint from that number, but you do not stretch it to the theoretical edge. You bring the car in one or two laps early, measure what the stint actually used, then update the plan. If race pace, traffic, weather, or fuel burn differs from practice, you learn that while the tank still has margin. After that, your later stops can be planned from race evidence instead of practice assumption.
This also explains why HPDE fuel advice is so blunt. In a learning session, there is rarely a reward for carrying the minimum possible fuel. In a race, excess fuel has a performance cost, so the safety margin should be as small as reasonable once consumption is known. In HPDE, the cost of being wrong is a tow and lost track time, so if you are unsure, add fuel.
Worked example: warm-up on a dry-sump race car
A dry-sump car changes the paddock clock. The mechanics source says the oil tank can be helped with electrical heating tape and pre-warming for an hour or so before starting. That means warm-up is not something you improvise after the grid call. It belongs on the session schedule.
The procedure is calm. Before start, oil level, water level, and throttle action have already been checked. You prime the fuel system until pressure stabilizes and check for leaks. You start the engine without excessive fuel pumping, because the source warns that too much pumping can contribute to inlet backfire and a small fire on a cold race engine. Once running, you hold the engine at the minimum smooth speed until oil and water temperatures reach the 140 to 160 degree range. Only after the engine is warm do you move to final checks such as oil and water levels, leaks, and the last visual inspection.
The wrong version is familiar: the car is started late, revved to prove it is alive, then sent toward grid with no pressure-state leak check. The right version is less dramatic and much more professional. Temperature, pressure, and leaks are confirmed before sound and urgency take over.
Common mistakes
The first common mistake is treating the fuel gauge as a plan. A gauge can be a clue, but the lesson standard is consumption plus margin. In HPDE, if you are not sure you can finish the session, you add fuel. In racing, once consumption has been worked out, you choose fuel for the distance plus a small reasonable safety margin. Good looks like a written or repeated number, not a shrug.
The second common mistake is revving a cold engine. The car may sound ready before the oil and water are ready. Good looks like minimum smooth running speed until the temperature range is reached, followed by final checks after the engine has warmed.
The third common mistake is checking gauges in the wrong place. If the glance happens at turn-in, in a braking zone, or while negotiating traffic, it is badly placed. Good looks like a planned glance on a straight, with enough attention left for car placement and flags.
The fourth common mistake is ignoring a coolant warning because the session is almost over. The supported rule is not ambiguous: red-zone coolant or no reading means end the session early and let things cool. Good looks like sacrificing laps to preserve the car.
The fifth common mistake is changing everything and learning nothing. If fuel load, tires, driver pace, traffic, and weather all change, one session cannot prove a precise conclusion. Good looks like simple logging, controlled changes where practical, and returning to a known baseline when conditions change.
The sixth common mistake is skipping the pressure-state fuel leak check. A dry fuel system at rest may not be dry after the pump stabilizes pressure. Good looks like priming, pressure stabilization, and a leak scan before the car is committed to pit-out.
Drill: three-session fluid loop
Run this drill at your next event for three consecutive sessions. The count is three sessions, not three laps, because the skill lives in the turnaround.
Before session one, record starting fuel state, oil level status, and coolant temperature expectation. During the session, make one planned gauge glance on a straight and note oil and coolant behavior from memory immediately afterward. After the session, record minutes or laps, fuel added to return to your chosen starting level, whether oil was added, whether coolant temperature stayed normal, and whether any leak was seen.
Before session two, predict the fuel you will need before you add it. Then add the margin appropriate to the event. For HPDE, uncertainty means more fuel. During the session, repeat the same safe gauge glance. Afterward, record actual fuel used and compare it with the prediction. Do not adjust the prediction from emotion; adjust it from the log.
Before session three, keep the fluid process the same and avoid adding unrelated changes if you can. If tires, weather, traffic, or driving pace changed, write that down so the fuel and temperature data have context. At the end of the third session, you should know whether your fuel estimate is becoming reliable, whether oil temperature has a normal pattern, whether coolant temperature stayed inside the safe pattern, and whether the inspection sequence caught leaks or uncertainty early.
The success criterion is not a perfect number. Success is leaving for the third grid call with fuel decided, oil and coolant checked, warm-up controlled, and no open question that should have been answered in the paddock.
When this principle breaks down
The loop breaks down when the evidence changes faster than your routine. Weather, track condition, tire deterioration, and fuel burn-off can all move the baseline. In that case, do not force yesterday’s number onto today’s car. Return to a known baseline where possible, record the changed condition, and treat the next session as new evidence.
The loop also changes when the objective changes. HPDE rewards certainty and track time, so extra fuel is usually a reasonable answer to uncertainty. Racing rewards finishing with enough but not much more than enough, so fuel consumption and safety margin need tighter work. Long-distance racing adds another layer: practice consumption may not match race consumption, so the first stop can be scheduled one or two laps early to verify the real burn.
Finally, the loop breaks down when a warning appears. A coolant red-zone reading, no coolant reading, a fuel leak after pump pressure stabilizes, or an engine that has not warmed enough before being revved is not a minor variation. It is a stop-and-fix condition. The session is less valuable than the car.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | MORPCA Drivers Education Guide | bb6aa94244bd7715d445d455e1381217 | 9 | 1 | uio_books_raw_v1 |
| 2 | Race Car Engineering Mechanics Paul Van Valkenburgh | 7dfbac40-f505-5cd5-70c1-cab467cb2972 | 85 | 1 | uio_books_raw_v1 |
| 3 | Sports car and competition driving Fr re Paul | 39e52178-3337-b6c9-7fd6-8b3dd98ed51b | 95 | 1 | uio_books_raw_v1 |
| 4 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 4adf8cb4-89c7-1b45-bd4d-9bb03634ecf3 | 345 | 1 | uio_books_raw_v1 |
| 5 | Competition Car Aerodynamics 3rd Edition McBeath Simon | c0cd0f54-6d9c-7f08-e9af-37c31b3421d3 | 345 | 1 | uio_books_raw_v1 |
| 6 | High-Performance Driver Education HPDE Techniques by Skill Level | 2d881ff1-b9e3-a24d-dde4-59b0bfbd40d2 | 1 | uio_books_raw_v1 | |
| 7 | Race Car Engineering Mechanics Paul Van Valkenburgh | 70ed06bb-1484-1718-5d89-0a43f68d69f3 | 51 | 1 | uio_books_raw_v1 |