Prep the car the driver can trust
Generated from
content/lms/race-car-mechanic-reference/01-prioritize-the-race-car/04-build-driver-trust-through-prep.md; edit the source file, not this page.
Source path: content/lms/race-car-mechanic-reference/01-prioritize-the-race-car/04-build-driver-trust-through-prep.md
Course: Service the race car that has to finish
Module: Prioritize the work before you wrench
Estimated duration: 55 minutes
Building driver trust through prep is not a pep talk. It is the practical job of making the car, the setup state, and the work process believable enough that the driver can spend attention on driving instead of wondering what will fail next. The strongest support in the corpus is simple: when the driver is sure the owner, engineer, and mechanics know their business, care about the driver's health, and care about finishing, the driver can concentrate on the business at hand. That is the mechanic's performance contribution before the car ever leaves pit lane. You are not just preparing metal. You are preparing the driver's mind to use the metal.
The rule for this lesson is: prepare in a way that turns uncertainty into usable confidence. A driver should not trust the car because you sound confident. A driver should trust the car because the preparation has a known baseline, the changes are controlled, the session has a plan, the feedback loop is honest, and the car's finishing ability has been treated as the first performance requirement. In club racing and HPDE, this matters even more because the same person may be owner, mechanic, driver, data analyst, and crew chief. You may be earning your own trust. If you skip the trust-building work in the paddock, you will pay for it on track with divided attention, vague feedback, wasted sessions, and sometimes with the driver making a large correction for a problem that should have been prevented or at least named before the green flag.
Start with the finish-first premise. The race car has many possible areas for improvement, but the first priority in the tuning and development material is that the car must finish the race. That is not a slogan about being conservative. It is the root of trust. A driver cannot use speed work if the car is not prepared to complete the session. A mechanic who chases an impressive adjustment while leaving the basic state of the car uncertain is asking the driver to do two jobs at once: drive near the limit and carry doubt about whether the machine will stay together. This lesson does not replace the separate lessons on ranking safety and performance work. Here the point is narrower: whatever your priority list says, the driver has to see and feel that the car has been prepared with finishing as the first operating assumption.
Trust has a mechanism. The driver has a limited attention budget. If the driver is spending mental bandwidth wondering whether the work was actually done, whether the adjustment was actually recorded, whether the loose feeling is a setup change or a missed preparation item, or whether the team is guessing from lap to lap, that attention is not available for braking markers, traffic, turn-in timing, throttle pickup, mirrors, flags, or the session plan. Van Valkenburgh's point about mental comfort is therefore not soft psychology. It is operational. When the driver has faith in the car and team, concentration returns to the business only the driver can handle. When the driver lacks that faith, the car may still be mechanically capable, but the driver's use of it becomes guarded and noisy.
Your preparation should produce five things the driver can trust. First, the driver can trust that the car has a known starting condition. Second, the driver can trust that any change from that condition was intentional, recorded, and reversible. Third, the driver can trust that the session objective is known before the car rolls. Fourth, the driver can trust that feedback will be heard as information rather than as blame. Fifth, the driver can trust that the crew is trying to finish sessions and races, not just to look clever with adjustments. These five outputs are more important than whether the paddock looks professional. A neat canopy and a confident voice do not help if the baseline is unknown and every debrief turns into guessing.
The first sub-skill is baseline discipline. A baseline is the fixed reference condition that lets you interpret what happened after a change. Without it, a faster lap after a suspension adjustment might be the adjustment, or it might be the driver improving with practice. A worse lap might be the change, or it might be traffic, temperature, driver inconsistency, or the driver learning a new line badly. Van Valkenburgh is explicit that tests should be baselined because there is no way to judge whether a change is positive or negative without a known reference. For the mechanic, baseline discipline means you can tell the driver what state the car is in before the session, what changed since the last session, and what you can return to if the change is bad.
In practice, a trust-building baseline is not complicated. It is the car's starting setup state, the work completed since the last run, the adjustments made, and the known unknowns. The key is not the particular notebook format. The key is that the driver is never asked to compare a current feel against a mystery. If the driver says the car is less stable than before, you need to know whether before means last session, last event, last controlled setup state, or the ideal memory of a perfect lap. A baseline gives the debrief a place to stand.
The second sub-skill is change control. A change that cannot be evaluated does not build trust. It creates noise. If you change several things at once and the driver reports improvement, you may have made one useful change, one harmful change hidden by the useful one, and one irrelevant change. If the driver reports a problem, you may not know which change created it. This is why reversible preparation matters. The test material stresses the ability to go back to the original setting, especially when a change has negative effects. For a driver, knowing that the crew can return to a known condition lowers the perceived cost of honest experimentation. The driver can push the test because the session is not a one-way trip into confusion.
The third sub-skill is track-time conservation. Carroll Smith's testing discussion is blunt that time is in short supply at a race track and that testing without a plan wastes time, effort, and money. This is a trust issue because the driver can tell when the crew is using the session as a controlled experiment and when everyone is simply burning laps. A planned session tells the driver what to pay attention to. An unplanned session asks the driver to come back with a general impression, and general impressions are where vague complaints and paddock arguments begin. Trust grows when the driver knows each lap has a job.
The plan does not have to be elaborate. Before the car leaves, name the session type. Is this a reliability check after work? Is it seat time for a driver who simply needs miles? Is it a baseline run? Is it one setup evaluation? Is it a controlled comparison against the previous condition? Smith makes room for early-career seat time as a valid need, but he separates that from aimless motoring once the package can be improved. That distinction helps the driver. If the mission is seat time, do not pretend you are doing a development test. If the mission is development, do not let the driver motor around without a specific observation task.
The fourth sub-skill is driver mental preparation. Bentley's preparation material expands the idea beyond the car. Winners prepare everything around the driving task. For this lesson, the mechanic's part is to help the driver convert preparation into a session plan. Before each session, the driver should know what will change in technique or car state and should mentally drive the track with that change in mind. The mechanic can support this by giving a short, factual brief: what was touched, what was not touched, what the driver should feel for, what would count as a stop-now symptom, and what feedback you need after the run. This is not a long meeting. It is a way to make valuable laps count.
A good pre-session brief has a calm rhythm. Start with the car state. Then name the session objective. Then name the driver cue. Then name the debrief question. For example: the car is back on the previous baseline except for one controlled adjustment; the session is three build laps and two push laps; pay attention to what happens just after brake release; after the run, report whether the front of the car accepts the release or washes wide. This kind of brief comes straight from the development-driver material: the driver must objectively describe how the car behaves on the way to the limit, at the limit, and on the way back.
The fifth sub-skill is feedback translation. Many driver-and-crew relationships become weak because the driver reports fixes instead of sensations, or the mechanic hears sensations as commands. Bentley is clear that the driver's job, unless the driver is also the engineer, is to report what the car feels like. The driver who jumps straight to a shock adjustment deprives the engineer or mechanic of the actual evidence. The trust-building mechanic asks for the felt condition, the phase of the corner, the control input, and the repeatability. What happened? Where did it happen? Was the driver on brake release, steady maintenance throttle, throttle pickup, or curb exit? Did it happen every lap or once? What did the driver do in response? That is the information that lets the mechanic work.
This is especially important for an intermediate audience because you may know enough setup language to be dangerous. Technical knowledge helps driver communication when it makes language more accurate. It hurts when it becomes a shortcut around observation. The best driver report is not a demand for a part change. It is a condition-based description. The car understeers after brake release. The front feels like it unloads too quickly. The driver thinks controlling that unload rate might reduce the understeer. That style of report gives the mechanic a usable symptom, a timing cue, and a possible direction without erasing the mechanic's diagnostic role.
The sixth sub-skill is honest driver evaluation. The car could have a problem, but the driver could also be the variable. Lopez emphasizes looking inward for speed and even suggests using a more experienced driver in the same class on a test day to help decide whether the issue is the car or the driver. For the mechanic, this matters because trust is not built by agreeing that every complaint is mechanical. Trust is built by building a system where mechanical diagnosis and driver diagnosis can both be considered without ego. A driver who knows you will not mock a mistake is more likely to report accurately. A mechanic who knows the driver will not blame the car by reflex is more likely to take the feedback seriously.
The seventh sub-skill is consistency. Both Van Valkenburgh and Smith warn against reading too much into scattered lap times or inconsistent driving. One fast lap out of ten does not prove a change. If the driver's performance is not constant enough, the day turns into confusion. This is not an insult to the driver. It is a testing constraint. If the driver cannot repeat the braking point, entry speed, release timing, and throttle pickup closely enough, setup conclusions become weak. In that case, the trust-building move is to stabilize the car, gather miles, and focus on driver consistency before chasing mechanical conclusions.
Consistency also affects the mechanic's credibility. If you claim the car is better because one lap was faster, while the rest of the run is scattered, you train the driver to doubt your interpretation. If you say the data is too noisy to call the change yet, you may sound less decisive, but you become more trustworthy. The stopwatch and recordings are there to protect both sides from wishful thinking. Smith's reminder that the development driver must believe the stopwatch rather than seat feel is a warning against paddock storytelling. Feel matters, but it has to survive comparison with time, repeatability, and the known baseline.
The eighth sub-skill is familiarity. Van Valkenburgh notes that drivers control the car better and are less likely to make mistakes when they have more familiarity with the particular race car and setup. This is not a license to practice race driving on public roads. The same passage warns that racing practice on streets and highways is insane and useless because the conditions are too different. The useful lesson is that trust grows when the driver has enough miles in the car to know what normal feels like. A driver who has never felt the baseline cannot reliably detect a small abnormality. A mechanic who keeps changing the car before the driver has a stable reference makes the driver less useful as a sensor.
In a converted production sports car or sedan, the corpus even notes that ordinary highway miles may be possible if street equipment is added, but the purpose is familiarity, not race practice. In the club environment, you can translate that into legal, safe familiarity work: seating position, belt routine, pit-lane checks, gentle systems checks where permitted, and stable early-session miles. The driver should know the car's normal control weights, visibility, sounds, and braking response at non-hero speeds. Then, when something changes under load, the driver has a reference.
The ninth sub-skill is mechanical accessibility. Smith's testing chapter opens near a practical point: adjustable items should be easily and quickly adjustable. This affects trust because the driver learns whether the crew can actually execute the test plan inside the time available. If the crew needs a long disassembly to reach a routine adjustment, the plan may collapse under paddock time pressure. If the car is built and prepared so normal adjustments are accessible, the driver sees that the team can conserve track time and return to the planned baseline when necessary. Preparation includes making the car serviceable enough for the plan you intend to run.
Do not confuse driver trust with driver comfort in the lazy sense. Trust does not mean hiding risk. Bentley's preparation material recommends thinking through what could happen when you attempt to go faster: the car may not turn in at a slightly higher entry speed, or it may oversteer during a transition because of excess speed and imbalance. The useful version of this is calm consequence planning. You do not feed the driver negative imagery. You name the likely consequence of the plan and the cue that tells the driver to back out. That makes confidence more real because surprises are reduced.
For example, if the driver plans to enter a corner a little faster, the pre-session trust brief might say that the first thing to watch is whether the car accepts turn-in or begins to wash. If the driver plans to release the brake differently, the cue might be whether the front support disappears too abruptly. If the crew changed the car, the cue might be whether the same symptom appears at the same phase of the corner. You are not predicting doom. You are giving the driver a mental model so a change in behavior does not arrive as a mystery.
A useful debrief is short, specific, and sequenced. Ask for the driver's first clean impression, then anchor it to corner phase, then anchor it to lap repeatability, then compare against the baseline, then compare against timing or recordings if available. Do not start with your theory. If you tell the driver what you think before hearing the report, you contaminate the evidence. Driver sensitivity and communication can be developed, but only if the driver practices reporting what the car did rather than what adjustment should be made. The mechanic's listening discipline is part of the training system.
A strong debrief also allows the answer that the car was not the problem. This is where intermediate teams often lose trust. The mechanic is afraid to challenge the driver, or the driver is afraid to admit inconsistency, so the team invents a setup chase. The better pattern is factual: the symptom appeared only on laps where the entry speed rose without a matching release change; the car looked stable when the driver repeated the earlier marker; or the more experienced comparison driver did not reproduce the complaint. That does not shame the driver. It protects the team from solving the wrong problem.
Data and recordings are useful because they make smoothness, consistency, and improvement visible. Van Valkenburgh notes that recordings can show how smooth a driver is and where improvement is possible. This supports trust in both directions. The driver can trust that the mechanic is not guessing from a facial expression. The mechanic can trust that the driver feedback can be compared against something beyond memory. Even simple lap timing and notes are better than a paddock debate where everyone remembers the run differently.
Technical knowledge sits in the middle of this loop. Bentley and the Speed Secrets reading list both support the idea that drivers benefit from understanding vehicle dynamics and race car preparation, even if they never touch a wrench. For the mechanic lesson, the point is that shared vocabulary reduces friction. A driver who understands basic chassis language can report more accurately. A mechanic who understands driver language can ask better questions. But vocabulary is only useful when it points back to what happened in the car. The goal is not to sound like an engineer. The goal is to make the next preparation decision less blind.
Here is the complete trust-building loop. Prepare the car to a known baseline. Record what changed. Brief the driver on the car state, the session objective, and the observation cue. Send the driver out with one main job. Debrief before the memory blurs. Translate sensations into conditions, not commands. Compare the report with timing, recordings, and baseline notes. Decide whether to keep the change, revert it, or gather more controlled laps. Then tell the driver exactly what the car will be when it goes out again. Each loop lowers uncertainty. Each sloppy loop raises it.
The most important tone in this process is honesty. Smith's development-driver standard requires objectivity and complete honesty with self and crew. That standard applies to the mechanic as well. Do not say a change worked because you want it to have worked. Do not say the car is perfect because you ran out of time. Do not say the driver caused it because you feel accused. Do not say the driver should trust you because you have experience. Trust is the result of visible discipline repeated under pressure.
You should also protect the driver from unnecessary paddock noise. If three people give three theories after every session, the driver will begin to filter, defend, or shut down. Use one debrief path. If the driver is also the mechanic, write the debrief before touching the car. The moment you put a wrench in your hand, you will be tempted to turn a vague feeling into a change. Separate the report from the repair. The driver brain and mechanic brain both work better when they do not interrupt each other.
Good trust-building prep is humble about what it can and cannot know. It can know the baseline, the completed work, the change history, the session plan, the driver's report, the timing, and whether a symptom repeated. It cannot know from one messy lap that a setup direction is correct. It cannot know from a confident driver complaint that the car is wrong. It cannot know from a clean paddock appearance that the driver feels mentally free. You earn trust by making the knowable things known and by refusing to pretend the unknowns are solved.
When you do this well, the driver leaves the paddock with a narrower job. The driver does not have to wonder whether the team cares about finishing. The driver does not have to guess what changed. The driver does not have to translate a full session into a vague complaint. The driver can concentrate, report, and build speed with more freedom. That is the mechanic's quiet lap-time contribution: not a magic adjustment, but a car and process the driver can believe enough to drive.
Cross-reference this lesson with the priority and rules lessons in this module. Use the risk-priority lessons to decide what must be serviced before performance work. Use the rules-as-service-input lesson to keep the car eligible and safe for the event. Then use this lesson to make that work visible and usable to the driver. A perfectly correct repair that the driver does not understand may still leave attention on the table. A clear trust loop turns correct preparation into driver confidence, better feedback, and more productive track time.
Worked example: the brake-release understeer report
The driver comes in and says the car pushed after brake release. A weak trust process turns that into an argument or an instant adjustment. The driver says the front needs a rebound change. The mechanic either follows the order blindly or rejects it defensively. Nobody knows whether the car changed, the driver changed, or the corner entry changed.
A stronger process starts with the baseline. You confirm what state the car was in for the run and whether anything changed from the previous session. Then you ask for the phase. The symptom was not general understeer everywhere. It appeared just after the driver released the brakes. That is already more useful than a broad complaint because it names a load-transfer moment rather than a whole-corner personality.
Next you ask for repeatability. Did it happen on every clean lap? Did it happen only after the driver tried a later brake release or higher entry speed? Did it happen in one corner or several similar corners? Then you ask for the driver's corrective action. Did the driver add steering, wait, reapply brake, or delay throttle? This keeps the report in sensation and action, which is the driver's proper contribution.
Only after that do you discuss the mechanic side. The report may suggest that the front support is changing too quickly when the brake is released. Bentley's example supports language that reports understeer after brake release and describes the front unloading too quickly, while leaving the engineer or mechanic to decide the actual remedy. Whether the answer is a damping direction, a driving change, or more baseline laps is not decided by the driver's first sentence. Trust comes from showing the driver that a precise report will be converted into a precise test rather than a paddock guess.
The next session brief is short. The car state is named. The observation is named. The driver is told to repeat the same entry and release for a few laps before changing the technique. If the symptom repeats in the same phase, you have a stronger case. If it disappears when the driver returns to the earlier entry speed, the first diagnosis may be driver approach rather than car setup. Either way, the driver trusts the process because the process did not waste the report.
Worked example: the short SCCA weekend with too little time
Smith calls out SCCA Regional and National events as places where time is especially short. That is the exact environment where trust-building preparation matters. The driver may get limited practice or qualifying time, and every lost lap is gone. If the car rolls out with an unclear setup state, if the crew debates the plan while the session clock runs, or if the driver is sent out just to see how it feels, the team has spent its scarcest resource without a question to answer.
The trust-building version begins before the event. You decide what the baseline is. You decide what is too risky to change during the weekend. You make routine adjustments accessible enough that they can actually be done between sessions. You write down the first-session objective. If the driver is new and needs seat time, call it seat time and keep the car stable. If the driver and car are ready for development, choose one thing to evaluate and keep the rest of the car known.
On the grid, the driver gets a brief that fits the pressure of the moment. The car is in the known baseline. The goal is to build two laps, then repeat the braking and release pattern. Report only the primary symptom and whether it repeated. That is enough. A long technical lecture in pre-grid does not build trust; it consumes attention. The driver needs to know the car is prepared, the plan is controlled, and the debrief will not become blame.
After the session, resist the urge to over-read the fastest lap. One scattered quick lap does not prove the car. If the driver reports a symptom and the times are inconsistent, the trustworthy answer may be to gather another controlled run rather than change the car. That answer can feel slow, but it protects the weekend. The driver learns that the crew values finishing, track time, and evidence more than appearing decisive.
Worked example: the converted production car that needs familiarity
Van Valkenburgh gives a useful club-racing situation: a race car that began as a production sports car or sedan may be capable of ordinary highway miles if street equipment is fitted, but public roads are not a place to practice race driving. The mechanic lesson is about familiarity, not speed practice. A driver who barely knows the car's normal behavior will struggle to separate a real fault from unfamiliarity.
For a converted production car, trust-building prep can include a legal familiarity plan. The driver learns the seating position, belts, control feel, visibility, normal sounds, and pit-lane routine. If legal and appropriate, ordinary miles can build comfort with the machine as a machine. None of this replaces track driving. It simply gives the driver a reference for normal.
At the event, that familiarity pays off in feedback quality. The driver can say that the brake response felt different than the usual baseline, or that a vibration is new, or that the car's response after release changed from prior sessions. Without familiarity, the same driver might only say the car feels weird. Trust is partly the absence of surprise. The more normal the normal feels, the faster an abnormal report becomes useful.
This example also shows why constant untracked changes are costly. If every event begins with a different seating position, different controls, different setup state, and different unexplained noises, the driver never settles into the car. The mechanic may be working hard, but the driver experiences the car as unstable information. Familiarity is not laziness. It is a foundation for accurate sensing.
Drill: the three-session trust loop
Run this drill at the next event when the car is safe to operate and the event format allows normal HPDE or test-session work. The drill uses three sessions. Its purpose is not to find the perfect setup. Its purpose is to train the driver and mechanic to create trust through baseline, plan, report, and controlled response.
Session one is the baseline run. Before the session, spend five minutes writing the car state and the session objective. Make no performance change immediately before the run unless the goal is specifically to verify that change. The driver runs a conservative build sequence and reports only three things afterward: whether the car felt normal, which phase of the lap produced the strongest concern, and whether the concern repeated. Success means the driver can describe the car without requesting an adjustment.
Session two is the observation run. Choose one symptom or one confidence question from session one. Do not chase everything. Brief the driver on one cue. For example, watch what happens just after brake release, or watch whether the car feels more settled after the first two warm laps. The driver runs enough consistent laps to test the cue. Success means the debrief names the phase, the repeatability, and the driver's response, not just a general verdict.
Session three is the controlled response. If the first two sessions justify a change and you can reverse it, make one change. If they do not justify a change, keep the car stable and gather another controlled run. Before the car rolls, tell the driver exactly what changed or that nothing changed. Afterward, compare the report against the baseline and the previous observation. Success means you can decide one of three things: keep the change, revert the change, or collect more data because the evidence is still too noisy.
The drill passes when the driver leaves all three sessions knowing what state the car was in, what the session was trying to learn, and why the next decision was made. It fails if the driver cannot remember what changed, if the crew changes multiple things without a way back, if the debrief turns into a guessed adjustment, or if one fast lap is treated as proof while the rest of the run is scattered.
Common mistakes
The first mistake is the confidence performance. The mechanic speaks with certainty but cannot name the baseline, what changed, or what evidence will decide the next step. Good looks different: calm, specific, and traceable. You do not need to oversell the work. You need to make the car's state knowable.
The second mistake is the magic adjustment. The driver reports a handling problem, and the crew immediately changes a part or setting without anchoring the symptom to phase, repeatability, and baseline. Good looks like translation before action. The driver reports what the car did. The mechanic asks when, where, under what input, and how often. Then the team decides whether a change is justified.
The third mistake is accepting the driver's fix instead of the driver's feel. This is common when the driver has enough technical vocabulary to sound precise. The problem is that a requested adjustment can hide the actual sensation. Good looks like respectful redirection. Ask the driver to describe the feel first. If the driver has a theory, capture it as a theory, not as the evidence itself.
The fourth mistake is the hero-lap conclusion. One fast lap gets treated as proof that the car improved. Good looks like consistency. If the rest of the laps are scattered, say so. A development decision needs repeatability, not one number that flatters the change.
The fifth mistake is the test-day tourist pattern. The car goes out because the session is available, but nobody named a plan. Good looks like a session objective that fits the driver and car. If the driver needs seat time, say that. If the car needs a baseline run, say that. If you are evaluating one change, say that and protect the rest of the car from noise.
The sixth mistake is the blame reflex. Every problem is either the car's fault or the driver's fault before the evidence is heard. Good looks like a shared diagnostic posture. The car could have a problem, and the driver could be the changing variable. Trust grows when both possibilities are allowed without ego.
Calibration cues
You are improving this skill when the driver's questions change. Early on, the driver may ask whether the car is okay, what was changed, or whether a symptom is safe to push through. Later, the driver asks sharper questions: whether the car is still on the same baseline, whether the change should affect brake release or throttle pickup, or what feedback you need after the session. The questions become more useful because the preparation is more transparent.
You are improving when debriefs get shorter and more precise. The driver stops giving whole-car adjectives and starts naming corner phase, control input, repeatability, and correction. The mechanic stops defending theories and starts sorting evidence. This matches Bentley's point that sensitivity and communication can be developed and that better technical knowledge improves language.
You are improving when setup decisions become reversible instead of emotional. A change that helps can be kept for a reason. A change that hurts can be rolled back without embarrassment. A noisy result can be marked inconclusive. The ability to return to baseline is a confidence cue for the driver and a quality cue for the mechanic.
You are improving when lap time interpretation becomes more disciplined. The team no longer treats one isolated lap as a development victory. It looks for consistent driving, useful recordings or timing, and a report that fits the data. The driver trusts the mechanic more when the mechanic is willing to say that the evidence is not strong enough yet.
You are improving when track time feels calmer. The session has a job. The driver knows what to observe. The crew knows what question the session is answering. Even if the answer is not the one you wanted, the day produces learning instead of paddock noise.
When this principle changes shape
There are times when the best trust-building prep is not development testing. Smith notes that early in a driver's career, seat time can be the greatest need. If that is the case, the trustworthy choice may be to leave the car stable and let the driver build familiarity. Do not disguise a learning-mileage day as a setup-development day. The driver will give better feedback later if the baseline is allowed to become familiar now.
There are also times when the driver is not consistent enough to evaluate the car. That does not mean the driver is bad. It means the test question is premature. If braking points, release timing, and throttle pickup are changing widely, the car's behavior is mixed with driver variation. The trust-building response is to narrow the driver task, not to keep changing the car.
Finally, there are times when safety and finishing override the trust loop. If a symptom suggests the car may not stay together or the driver cannot identify what changed, the right answer is to stop and inspect rather than gather more impressions. The corpus supports finishing as the first priority and driver health as central to mental comfort. Trust is never built by asking the driver to ignore an unresolved concern so the team can complete a plan.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | Race Car Engineering Mechanics Paul Van Valkenburgh | 706b6084-0052-a3ba-4f63-34d81ab8ff4c | 112 | 1 | uio_books_raw_v1 |
| 2 | Tune To Win Carroll Smith | 661f2c93-57bd-f041-90d0-fc9ff0cb634b | 160 | 1 | uio_books_raw_v1 |
| 3 | Race Car Engineering Mechanics Paul Van Valkenburgh | 4a0085b1-a5b6-20ef-c288-ff092fa3e4d9 | 116 | 1 | uio_books_raw_v1 |
| 4 | Tune To Win Carroll Smith | ec18ed09-3d26-b226-4218-b8d1aafd0116 | 161 | 1 | uio_books_raw_v1 |
| 5 | Ultimate Speed Secrets - Ross Bentley | 32569ef6-9e67-12c5-e001-2ae0feacb49d | 531 | 1 | uio_books_raw_v1 |
| 6 | Ultimate Speed Secrets - Ross Bentley | 9b1034df-2d61-9fa7-4e7c-66a7adefb25d | 397 | 1 | uio_books_raw_v1 |
| 7 | Going Faster Mastering the Art of Race Driving - Carl Lopez | ef9ea5d6-92b2-e60a-d6d0-5adac150482c | 234 | 1 | uio_books_raw_v1 |
| 8 | Speed Secrets Professional Race Driving Techniques Ross Bentley | 169eda80-83ce-6bc4-70a8-65edfcef5eed | 81 | 1 | uio_books_raw_v1 |