Turn shop skill into racing-risk control
Generated from
content/lms/race-car-mechanic-reference/01-prioritize-the-race-car/01-apply-shop-skill-to-racing-risk.md; edit the source file, not this page.
Source path: content/lms/race-car-mechanic-reference/01-prioritize-the-race-car/01-apply-shop-skill-to-racing-risk.md
Course: Service the race car that has to finish
Module: Prioritize the work before you wrench
Estimated duration: 55 minutes
Shop skill matters at the track only after you translate it into risk. In a normal shop, you may look at a worn part and ask whether it can make the next service interval, whether the customer approved the repair, or whether the replacement is in stock. In a race paddock, those are still useful questions, but they are not the first questions. The first question is what the finding can do to the driver, the crew, the other cars, and the session if it fails under load.
That is the skill in this lesson: you take an ordinary mechanical observation and convert it into a racing-risk decision before you convert it into a repair plan. A loose fastener, a soft brake pedal, a tire flat spot, a drivetrain vibration, a bent suspension part, a test result that did not repeat, and a driver report that sounds vague do not all deserve the same response. Some findings are immediate safety stops. Some are reliability threats that can end the race or destroy expensive parts. Some are performance or diagnosis problems that can make you chase the wrong change. Your job is to sort the observation by consequence, then choose an action that reduces the actual racing risk.
The clean rule is this: consequence outranks convenience. The easier repair is not automatically the higher priority. The familiar part is not automatically safer. The expensive component is not automatically the most urgent. In the supplied racing-mechanics material, the most severe category is made clear by examples such as axles, hubs, spindles, hub carriers, and steering arms. A failure in that group can cause a serious accident. Other highly stressed engine, transmission, and driveline parts may be expensive and race-ending, but the immediate consequence is often different. That distinction is not permission to ignore the engine or driveline. It is the start of disciplined thinking. You first ask what happens if this item fails at speed, under braking, over a bump, or during corner exit. Then you decide whether the car may run, must be inspected further, must be tested in a controlled way, or must stop.
This is why inspection is not clerical work. A race car is light, highly stressed, and expected to survive loads that are not normal road-service loads. The more the car is built for low weight and structural efficiency, the less margin you should assume is hiding in the parts. In a perfect world you would inspect every inch of every component with unlimited time. In the real paddock you cannot. You therefore need a criticality map: which parts get mandatory attention because their failure mode can hurt people, which parts get service attention because their failure mode can end the event or destroy the car, and which parts get monitored because their main cost is performance, confidence, or diagnosis.
A useful way to say it in the shop is: first protect control, then protect containment, then protect the test. Control means the driver can still steer, stop, support the car, and keep the tire attached and loaded. Containment means the car does not spill fluid, shed parts, or create a hazard for other drivers. The test means the next session produces evidence you can trust. A car that cannot stop predictably is not a setup problem. A car leaking oil or coolant is not merely down on performance. A tire with one flat-spotted section is not proven good because the rest of the tread still looks thick. A setup change that cannot be compared to a baseline is not evidence, even if the lap time looks better.
The mechanism is simple but unforgiving. Racing load turns small shop defects into fast failures. Braking puts large loads through hubs, spindles, uprights, bearings, brake mounts, pedal linkage, fluid, tires, and the driver. Cornering adds lateral load and heat. Acceleration and shifting add driveline shock. Testing adds another layer because the car may change significantly between runs, the driver may be adapting, and the safety staffing may be thinner than at a race. A part that looked acceptable in the paddock can become the part that decides whether the driver has braking, steering, or grip on the next lap.
The first sub-skill is consequence reading. Do not start with the repair operation. Start with the failure story. If the steering arm cracks, the driver may lose directional control. If a hub or spindle fails, the car may lose wheel support. If the brake system cannot be modulated, the driver may lock tires or lengthen the stop at exactly the wrong place. If an engine failure sends oil or coolant onto the rear tires, the driver may spin and the rest of the field may inherit the hazard. If a tire has a flat spot, it may feel acceptable in the paddock and still wear through one local patch to the cord. Consequence reading keeps you from treating all defects as equal.
The second sub-skill is inspection rhythm. The racing-mechanics source makes the economic argument bluntly: the cost of inspection is small compared with normal teardown time and the potential loss from failure. That does not mean you inspect randomly until you run out of daylight. It means you decide ahead of time which parts always receive direct attention, which parts require measurement, and which parts require driver feedback after every session. Safety-critical suspension, steering, wheel, hub, and brake areas should not depend on memory or optimism. They should be part of a repeated walkdown that survives fatigue, time pressure, and a good-looking lap time.
The third sub-skill is controlled proof. Shop confidence is not the same as track proof. A brake repair, pad change, bias change, tire change, or major setup change needs a proof method that exposes the system without turning the first hot lap into the experiment. The brake-testing passage gives a good model. The ideal place is the center of a long straightaway such as a drag strip, with two-way runs possible and plenty of escape road. The car should be tested under high stress, including full fuel when that is relevant, and the brakes should be warmed to representative operating temperature. New pads should be bedded before the measurement phase. Then the driver repeats complete stops from a specific speed, begins braking within a few feet of a fixed marker, and compares stopping distance. The point is not just one heroic stop. The point is smooth, consistent, repeatable braking.
That brake example teaches more than brakes. It teaches the pattern for shop-to-risk translation. First, create a known starting condition. Second, warm the system into the state it will actually see. Third, use a fixed marker or fixed reference. Fourth, repeat enough times to learn whether the result is consistent. Fifth, decide before the run what variation is acceptable. In the brake example, the driver should keep stopping distances within roughly a 5 to 10 percent range. That kind of acceptance window is how you keep a proof run from becoming a story the crew wants to believe.
The fourth sub-skill is baselining. A race car cannot be judged cleanly if every session changes the car, the driver, the track, and the weather at the same time. The testing source is clear that there is no way to know whether a change is positive or negative unless there is a well-known fixed reference. You need to be able to go back to the original condition. This matters when a change looks good, because the gain may be driver improvement or changing conditions. It matters even more when the change looks bad, because you need a known safe place to return to. A shop-skilled mechanic who ignores baselines can still do beautiful work and create useless evidence.
Baselining also protects against ego. One fast lap among scattered lap times does not prove the car improved. It may only prove the driver found one lap. Testing requires consistency above ordinary race pace ambition. The driver has to feel steering forces, motion, vibration, noises, smells, and small changes, and then report them honestly. The mechanic has to record vehicle and environmental conditions so contradictions can be analyzed later. The crew has to resist the trap of searching the car for a problem that was actually driver error. None of that replaces mechanical inspection. It makes mechanical inspection smarter.
The fifth sub-skill is deciding how large a change can safely be. In development work, a change can be made large enough that the result is obvious. That helps bracket an optimum instead of wasting time on endless tiny moves. But the exception is critical: do not make a large change where it may make the car dangerously uncontrollable or liable to critical failure. This is another place where ordinary shop skill must become racing-risk judgment. A spring perch adjustment, brake-balance change, geometry change, wing change, or tire-pressure change is not just a technical action. It changes what the driver will feel when the car reaches the next braking zone or corner. If the likely downside can remove control, shrink the change, move the test to a safer environment, or do not run it.
The sixth sub-skill is driver sensory triage. The driver is part of the inspection system. The tire passage gives a concrete example: a flat-spotted tire may look like it has plenty of tread, yet one small area can wear to the cord and fail. During a race, the driver is often the best person to discover the flat spot. Because front brake bias is common and a sliding tire has less traction, the driver may feel the problem at the steering wheel. That is shop information arriving through the driver. You should train yourself to ask for details that connect sensation to risk: when did the vibration start, is it speed related or brake related, does it change under load, did the steering wheel pulse, did the car pull, did the pedal get longer, did the smell appear after braking or after throttle, did the behavior repeat on the next lap.
Tire evidence deserves special treatment because tires connect almost every system to the ground. The corpus supports several tire-related risk cues. Cold tires do not have peak traction. Tires can cool quickly at high speed with no load or while sitting during a pit stop. Wear rate depends on car, track, ambient temperature, driving technique, and events such as spins. Visual inspection may be enough for an experienced person, but a tread-depth gauge gives a better basis for prediction. Tire temperatures and wear patterns can point toward pressure, camber, chassis roll, bump steer, and balance problems. Some of those problems cost lap time; some can make the car unstable or force the driver to nurse the tires. The point is not to turn this lesson into a tire-engineering course. The point is to stop treating tire observations as casual comments.
Brake evidence deserves the same respect. A driver who cannot hold the brakes near the verge of lockup without full lockup does not have a brake system the crew can blindly trust. The brake proof from the corpus asks for short, instantaneous bits of sliding without full lockup, smooth performance, and consistency throughout repeated applications. If the car wanders, darts, locks one wheel, has a soft or changing pedal, or cannot repeat stops from a marker, you do not solve the problem by telling the driver to be braver. You identify whether the issue is system capability, modulation, bias, tires, suspension behavior, or driver inconsistency. Shop skill becomes useful when it helps the driver approach the limit without turning braking into a gamble.
This matters because many drivers underuse the brakes even when the car has more capacity available. The source notes that few drivers are willing to use brakes to the limit, even if they know what the brakes can do. That is not only a driver problem. It is also a trust problem. If the car has not been inspected, warmed, bedded, tested, and proven repeatable, the driver has rational reasons to hold back. If the mechanic can show that the brakes are consistent, the tires are in a known state, and the car stops repeatably from a marker, the driver can spend attention on driving rather than wondering whether the next pedal application is the one that changes.
The seventh sub-skill is track-testing risk control. A test day can be more dangerous than racing even with no other cars on track. The corpus gives the reasons: many components may be altered, vehicle characteristics can change a great deal between runs, and the team may not have the corner workers and safety personnel that exist during a race. At minimum, the source calls for an ambulance and paramedic. The shop translation is that a test plan is not complete because the wrench work is complete. You must decide whether the venue, staffing, escape road, run sequence, and driver instructions match the risk of what you changed.
The eighth sub-skill is stop-or-nurse judgment. Breakages can occur despite money, care, and engineering. A motor, tire, braking-system part, rod end, upright, or wheel can fail unpredictably. You do not dwell on that fact, but you respect it. If the motor is failing and oil or coolant may be spraying out the back, the driver should get off line to avoid ruining the race for others and to keep the fluid off the driven tires. If a tire vibration suggests a flat spot, the decision may be to pit before it becomes a corded local failure. If the front tires are going away during a race, the driver may need to change line and technique to nurse them. If the brakes are inconsistent, the car may need to stop before the next high-speed commitment. A shop-skilled person who cannot make that call is only half useful in racing.
The ninth sub-skill is communication. The racing-mechanics text ties car condition and mechanic care directly to driver concentration. When the driver knows more about the condition of the car and the care being put into it, the driver can focus on other racing risks. That does not mean the mechanic gives a long technical lecture before grid. It means the mechanic communicates the right things: what was inspected, what was changed, what is still being watched, what the driver must report, and what the pit signal or stop condition is. This is where this lesson touches the sibling lesson on driver trust, but the focus here is narrower. Trust is not a mood. It is the byproduct of correctly translated risk.
Here is the working method. When you find something, do not write only the part name. Write the risk sentence. A basic example is: left-front hub play found after session; possible wheel support and braking stability risk; car does not return to track until inspected and corrected. Another is: front tire shows local vibration report after lockup; possible flat spot despite acceptable average tread; rotate by hand, inspect circumference, measure where possible, and decide before next session. Another is: brake pads changed; system not accepted until warmed, bedded, and repeated from a marker with consistent stopping distance. The risk sentence forces the repair conversation to begin with consequence.
After the risk sentence, choose the action class. Stop means the car does not run until the condition is corrected or proven not to exist. Controlled proof means the car may run only in a specific test condition with fixed markers, escape room, warm systems, and a clear abort. Monitor means the car may run, but the driver and crew know the cue that would escalate it. Record means the finding is not currently a safety or reliability limiter, but it could explain later evidence. The action class keeps you from using the same response for a hub concern, tire-pressure observation, setup-change uncertainty, and engine-response complaint.
Intermediate mechanics often struggle because their hands are better than their ranking. They can replace pads, bleed brakes, check toe, inspect rod ends, set pressures, and look for leaks, but they have not yet built the habit of asking what each finding can do at race load. This lesson is the bridge. You already have shop senses: sight, touch, smell, sound, and feel for loose, cracked, hot, leaking, binding, or worn things. The upgrade is to attach each sense to a racing consequence. Burning smell after a session is not just a smell. It belongs to a system and a risk. Vibration is not just vibration. It belongs to rotating speed, braking load, wheel support, tire damage, or driveline stress. A driver saying the car darts over bumps is not just a complaint. It may point toward bump steer, tire behavior, or suspension damage that changes entry stability.
Carroll Smith's setup-diagnosis material in the supplied bond is valuable here because it shows how shop evidence, tire evidence, and driver feel connect. Too much tire pressure can reduce footprint and traction. Too little can make response soft and mushy and raise tire temperatures. Front tires going off can cause understeer after the car has initially pointed into the corner. Bump steer can make the car dart over bumps, wander under braking, or change balance after turn-in. In the race, the driver's available response may be only to change line and technique to nurse the tires. In the shop, your response is to identify whether the driver is nursing a known limitation or unknowingly driving around a fixable risk.
The same caution applies to brake evaluation. The supplied Smith passage warns that brake performance is hard to compare because there are too many variables and too much ego. Instrumentation helps, but the driver remains the largest variable. Many drivers take too long to get on the brakes hard, leave them hard on too long, or brake too heavily too deep into the corner. If you ignore that, you may tear into a good brake system because the lap trace or driver report looks ugly. If you overuse that, you may blame the driver while a real mechanical problem is developing. Racing-risk control lives between those mistakes. You combine inspection, fixed tests, repeatability, driver honesty, and data when available.
The clearest calibration cue is fewer surprises. You are improving when the car comes back with findings that match your watch list instead of completely new failures. You are improving when the driver reports changes in steering force, vibration, smell, sound, pedal feel, and tire behavior with enough specificity that the crew can inspect the right place. You are improving when a brake proof produces repeated stops within the accepted range instead of one dramatic stop and several scattered ones. You are improving when a baseline return settles arguments about whether a change helped. You are improving when the crew can say why the car is cleared, why it is held, or why it is being sent out only for controlled proof.
Another calibration cue is lap evidence. One superfast lap among scattered times does not prove the car or the mechanic improved. A useful car is repeatable enough for the driver to evaluate. If a change is supposed to improve braking confidence, you should see more consistent brake points, cleaner release, fewer lockups, and better repeated stops in controlled testing. If a tire issue is being managed, you should see the driver alter technique before the tire is destroyed, not after the cord appears. If a setup change is truly better, you should be able to return to the baseline and understand the difference. If the result disappears when the baseline returns, you learned something important.
Do not confuse this with building a bureaucracy. A racing-risk note can be short. The discipline is not length; it is consequence. A useful note might say: right-rear tire outside shoulder hot and wearing; watch exit oversteer and traction loss; pressure and camber review before next session. Another might say: brake stop test varied beyond target; do not clear for threshold-braking session until cause found. Another might say: engine smell plus possible fluid mist; driver instructed to get off line and pit if repeated. These notes are plain because the paddock needs plain language under time pressure.
There are limits to what this lesson supports. The bonded corpus does not give torque values, exact crack-inspection intervals, manufacturer service limits, rulebook compliance thresholds, or part-specific retirement schedules. Do not invent them. Use the relevant service manual, sanctioning-body rules, manufacturer limits, and experienced engineering support for those details. The skill here is upstream of those documents: when you see a shop finding, you know whether it belongs in the safety-critical path, reliability path, performance-test path, or evidence path. Then you know which document, test, or person you need next.
The final habit is to close the loop after the session. Ask what the car told you, what the driver told you, what the measurements told you, and whether those stories agree. If they disagree, do not force agreement. Record the inconsistency. The testing source specifically calls for recording vehicle and environmental conditions so inconsistencies can be analyzed later. That is not paperwork for its own sake. It is how you avoid making tomorrow's decision from today's bad memory. A mechanic who records conditions, baselines changes, listens to driver sensory detail, and prioritizes by consequence is applying shop skill to racing risk.
Worked example: Brake proof before the car needs the brakes
A brake job feels finished when the hardware is bolted, the system is bled, the pedal feels firm, and the wheels are back on. In racing-risk terms, that is only the shop finish. The car is not yet proven for a driver who will arrive at the next braking zone at speed.
Use the long-straight brake proof from the corpus as the model. Choose a place with escape room, ideally a straight section such as a drag strip. Warm the racing brakes to a representative operating temperature and make sure new pads are broken in before the proof starts. If the car will race with a full fuel load, include that load because it stresses the system and can affect balance through fuel location and slosh. Use a fixed marker for brake application and a fixed starting speed. The driver declutches during complete stops so engine drag or stalling does not contaminate the result.
The risk question is not whether the driver can produce one impressive stop. The question is whether the system and driver can repeat the stop. The corpus gives a useful acceptance idea: begin braking within a few feet of the marker and keep stopping distances within a 5 to 10 percent variation. While doing that, evaluate modulation. The car should let the driver hold the brakes near the verge of lockup, with only brief bits of sliding and without full lockup or a flat-spotted tire. If the car locks suddenly, wanders, changes pedal feel, or produces scattered stopping distances, the risk is still open.
The shop translation is straightforward. A brake system that cannot be repeated from a marker is not cleared by a nice pedal in the paddock. A driver who cannot modulate without flat-spotting may need technique work, but the crew still needs to prove the system is consistent enough to practice that technique safely. A pad change or repair is complete only when it passes the proof appropriate to the event risk.
Worked example: The tire with plenty of tread and one dangerous place
A tire can deceive you because average appearance is not the same as local condition. The corpus warns that a tire may appear to have plenty of tread and still wear through to the cord in one small flat-spotted area. That makes this a perfect example of applying shop skill to racing risk.
The driver locks a front wheel in braking, finishes the session, and reports a steering-wheel vibration. In a casual shop mindset, you might glance at the tire, see usable tread, and move on. In a racing-risk mindset, you tell the failure story. A sliding tire has less traction. With common front brake bias, the flat spot may be on the tire that is already being asked to do hard braking work. If the damaged section wears locally to the cord, the next session can turn a minor lockup into a tire failure.
The correct action is not automatically to throw the tire away, because the bonded corpus does not give a universal discard threshold. The correct action is to refuse the average-view shortcut. Rotate the tire through the full circumference, inspect the suspected section, measure tread where possible, connect the driver report to the physical evidence, and decide whether the tire can continue, must be moved to a lower-risk role, or must be retired under the applicable tire and team standard. If the car must run, the driver also needs to know what cue escalates the issue: increased vibration, braking instability, visible cord, or any repeat lockup.
This example also teaches why the driver is part of inspection. During the race, the driver may be the best person to discover the flat spot. The mechanic who respects that report catches risk earlier than the mechanic who waits for the tire to look obviously bad.
Worked example: A setup change that looks faster but is not yet evidence
A mechanic changes suspension geometry and the driver goes faster. The paddock wants to celebrate. The racing-risk method asks one more question before accepting the result: faster compared with what fixed reference.
The testing material says a change cannot be judged positive or negative without a well-known baseline. You need to know the original setting and be able to return to it. That protects you in both directions. If the driver went faster because the driver improved, the new setup may get credit it did not earn. If the car got worse, the baseline gives you a known place to return. If track or environmental conditions changed, the recorded conditions help explain the inconsistency instead of letting the crew invent a story.
The risk side is just as important. The corpus allows larger changes when they make the result obvious, but it draws a boundary where a large change may make the car dangerously uncontrollable or liable to critical failure. That means you do not treat all development changes the same. A safe, obvious bracket may be useful for a low-risk adjustment in a controlled test. A large change in an area that affects braking stability, steering response, tire loading, or structural load path deserves a smaller step, a safer venue, or no run until the risk is understood.
The action class for this example is controlled proof. Define the baseline, record conditions, make the change, run a repeatable sequence, listen to the driver's sensory report, and return to baseline if the result is unclear. A faster lap is only useful if the car remains controllable and the comparison survives a return to reference.
Common mistakes
The first common mistake is ranking by repair difficulty instead of failure consequence. A difficult engine job can be expensive and important, but a small steering, hub, spindle, or brake concern can sit closer to immediate accident risk. Good looks like writing the failure story before the work order: what happens if this part fails under racing load.
The second mistake is clearing a repair because it looks finished in the paddock. Brakes are the clearest example. Good looks like warm, representative, repeated proof from a fixed reference, with the driver able to modulate near lockup and repeat stopping distance within the accepted range.
The third mistake is believing one fast lap. The testing material rejects scattered lap times as proof. Good looks like repeatable laps, recorded conditions, and a return to baseline when the result matters.
The fourth mistake is treating tire evidence as visual only. A tire with one flat-spotted section can be dangerous while the rest of the tread looks acceptable. Good looks like inspecting the full circumference, using measurement when possible, and taking steering-wheel vibration seriously.
The fifth mistake is making a large test change in a critical area just because obvious changes are easier to evaluate. Good looks like separating useful bracketing from dangerous bracketing. If the change can make the car uncontrollable or create critical failure, reduce the step or change the test environment.
The sixth mistake is blaming the car for every driver report, or blaming the driver for every strange result. Good looks like using both truths: the driver is a major variable, and the car can still be failing. Baseline, record, inspect, and require honest sensory feedback.
Drill: The risk translation walkdown
Run this drill at your next event before the first session and again after the first hard session. It takes 25 minutes the first time and 15 minutes after you have practiced it.
Round 1 is a five-minute critical-path walk. Move around the car and name only the systems whose failure can remove control or create immediate hazard: wheels, hubs, spindles, uprights, steering links, brake hardware, brake fluid behavior, visible leaks, tire condition, and anything that can shed or spill onto the track. For each finding, say the risk sentence out loud. Do not say only loose, worn, hot, or leaking. Say what that condition can do at speed.
Round 2 is a ten-minute evidence walk. Check the items that can ruin the test or hide a developing failure: tire wear pattern, suspected flat spots, tread depth where useful, brake pad and pedal condition, fluid smell or mist, drivetrain vibration reports, and anything changed since the last baseline. Classify each item as stop, controlled proof, monitor, or record.
Round 3 is a five-minute driver handoff. Tell the driver what was inspected, what was changed, what is being watched, and what sensation requires a pit-in or off-line response. Ask for reports in sensory language: steering force, vibration, noises, smells, pedal travel, pull under braking, or change after tire warmup.
Success criterion: before the session, every open finding has an action class. After the session, at least three driver comments are tied to specific systems or marked as not repeated. If you cannot classify a finding, the drill has done its job. The car does not need optimism; it needs a clearer inspection or safer proof.
When this principle breaks down
The principle breaks down when you pretend the corpus gives numbers it does not give. It does not provide torque specs, crack-size limits, part retirement intervals, sanctioning-body tech limits, or manufacturer-specific service limits. For those, use the rulebook, manufacturer data, service documentation, and qualified engineering judgment.
It also breaks down when the team lacks a safe test environment. The testing material warns that track testing can be more dangerous than race driving because components are being altered, vehicle characteristics change between runs, and safety staffing may be thinner. If you cannot provide enough escape room, staffing, or control for the test, do not let the first competitive lap become the proof.
Finally, it breaks down when communication is vague. The driver cannot help inspect the car with comments such as weird, sketchy, or not right unless you follow up. Convert those words into timing, load, sound, smell, vibration, pedal, steering, and repeatability. The better the question, the more useful the driver's senses become.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | Race Car Engineering Mechanics Paul Van Valkenburgh | 6761997c-1267-f401-0671-5bfbf75c8c8d | 104 | 1 | uio_books_raw_v1 |
| 2 | Race Car Engineering Mechanics Paul Van Valkenburgh | 55f18e0a-8bd9-aafd-8acd-9a54106ac323 | 127 | 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 | Race Car Engineering Mechanics Paul Van Valkenburgh | 0903a808-e0ea-dc82-7e79-ef31b93d3533 | 116 | 1 | uio_books_raw_v1 |
| 5 | Race Car Engineering Mechanics Paul Van Valkenburgh | 497023f2-2fc5-86df-1857-e91fbf31f847 | 19 | 1 | uio_books_raw_v1 |
| 6 | Tune To Win Carroll Smith | b18ba001-b4b2-85d5-df49-bd67bc0d05af | 137 | 1 | uio_books_raw_v1 |
| 7 | Going Faster Mastering the Art of Race Driving - Carl Lopez | 68849090-ed6a-aba5-b5b6-d9b227026942 | 193 | 1 | uio_books_raw_v1 |
| 8 | Tune To Win Carroll Smith | 4ca87def-91c7-272a-da3a-5ca0b2f239c9 | 107 | 1 | uio_books_raw_v1 |