Build a pre-registration checklist that can say no
Generated from
content/lms/race-class-rules-and-categories/07-build-your-class-decision-matrix/04-build-the-pre-registration-checklist.md; edit the source file, not this page.
Source path: content/lms/race-class-rules-and-categories/07-build-your-class-decision-matrix/04-build-the-pre-registration-checklist.md
Course: Choose the race class that fits your car and goals
Module: Build your class decision matrix
Estimated duration: 55 minutes
The pre-registration checklist is not a packing list. A packing list helps you remember your helmet, paperwork, tools, and fuel. This checklist decides whether you should enter the event at all, whether you should enter this class, whether you should change the plan before paying, and whether the weekend has a clear learning purpose. At the intermediate level, you are no longer just asking whether you are excited to race. You are asking whether the class, car, driver, track, budget, and preparation loop line up well enough to make the entry intelligent.
That word matters. Johnson's closing advice is not that you simply get a car and throw yourself at racing. His point is that racing becomes rewarding when you approach it intelligently, stay within the limits you meet on track, and stay within the limits your bank balance tells you about. That is the spirit of this lesson. A good pre-registration checklist gives you permission to say yes with focus, yes with conditions, not this class, not this event, or not yet.
This lesson does not repeat the sibling lessons about listing your real constraints, choosing a class with people to race, or deciding whether to change car or class. Those decisions feed this checklist. Here, you turn those earlier decisions into a practical gate you can run before every registration. The skill is not making a prettier form. The skill is refusing to let excitement, ego, or deadline pressure hide a weak decision.
Principle: registration is a readiness decision
The rule is simple: do not register until the entry has evidence behind it. Evidence means you can point to something specific: the class you selected, the reason that class fits your car and budget, the preparation work still open, the track demands you expect, the practice goal for the weekend, and the information you will bring home afterward. If one of those is missing, you may still register, but you are no longer making a clean decision. You are accepting a known risk, and the checklist should make that visible.
The mechanism is preparation. Bentley frames racing improvement as a combination of hands-on experience, study, theory, and the ability to analyze how to go faster at all times. Johnson frames competition as step-by-step development: the car, its preparation, the crew, driver equipment, track analysis, licensing, first races, testing, and eventually winning. Neither author treats racing as a single heroic act. The successful driver stacks small prepared decisions before the car ever rolls to grid.
The pre-registration checklist should therefore be built around gates, not wishes. A wish sounds like this: the car should be okay, I think this class will work, I will figure out the track when I get there, and I can deal with the budget later. A gate sounds like this: the car preparation question has a named owner, the class question is resolved or still yellow, the track plan is written, the budget has a ceiling, and the post-event note process is ready. The checklist does not need to know everything. It needs to separate what is known, what is unknown but controllable, and what is unknown enough to stop the entry.
There are seven gates. They are class and event fit, car and equipment readiness, driver readiness, track readiness, session strategy, budget and recovery margin, and the information loop. You can add event-specific items, but do not delete these seven. Each one comes from a real racing failure mode. A driver can choose a class that is too serious for their current preparation. A car can be entered before the driver has analyzed the machine well enough to operate it cleanly. A driver can arrive without concentration, without a track plan, or without a method for capturing what happened after the race. The failure is not always a crash or a disqualification. Sometimes the failure is a wasted weekend where nothing improves because the driver never defined what good would look like.
Gate 1: class and event fit
Start with the class. Do not re-argue the entire class decision here. The earlier lesson work should already have identified your real constraints and your likely class. In this checklist, you ask whether that class still fits this event. The answer may change because an event is not abstract. It has a track, a field, a format, a schedule, a preparation burden, and a level of seriousness.
Johnson's discussion of professional racing gives a useful warning even if you are not registering for a professional event. As the level of competition rises, the preparation level rises, the driving skill rises, and a driver who cannot keep up will not last. The pre-registration version of that idea is blunt: do not enter a class because it flatters you. Enter because the event gives you a race you can prepare for honestly. If the class demands a level of car prep or driver execution that you cannot support this month, the checklist should say so before the entry fee is paid.
Use three answers for class fit. Green means the class, car, driver, and budget still match the plan. Yellow means the class can work if a specific action happens before a specific date. Red means the class choice is no longer honest for this event. A yellow without an owner is really red. A red does not mean you failed as a driver. It means the checklist worked. It protected you from confusing ambition with readiness.
For class fit, your checklist should record the chosen class, the reason it fits your car, the reason it fits your current skill, the reason it fits your budget, and the one thing that could still make the entry wrong. That last item matters because every race plan has a weak point. You are not trying to create a perfect plan. You are trying to know where the plan can break.
Gate 2: car and equipment readiness
Johnson's early framework puts car preparation, crew, and driver equipment before going out on track. That ordering is important. It means the car and equipment are not an afterthought once the exciting decision has been made. They are part of the decision itself.
The checklist should not try to replace the event rulebook or the technical inspection form. Instead, it should force you to prove that you have a current answer for each required preparation area. Do you know which car items must be legal for the class. Do you know which driver equipment items must be current for the event. Do you know what still needs inspection, replacement, adjustment, or confirmation. Do you know who is responsible for each unresolved item. If the answer is vague, the item is not green.
The more serious the competition, the less room you have to overlook small operational details. Johnson describes the need to analyze everything about the machine that affects your operation of it, to know where the needles should be, and to remember information well enough to tell the crew when you return. That belongs in the registration checklist because car readiness is not only legality. It is also operability. Can you read the car quickly. Can you notice a change. Can you describe that change accurately. If not, the car may be mechanically present but operationally underprepared.
Build this gate with four columns: requirement, evidence, remaining action, and decision. Requirement is the item or question. Evidence is how you know the answer. Remaining action is the next concrete step. Decision is green, yellow, or red. Do not allow evidence like probably fine. Evidence is a current inspection, a completed preparation task, a rule confirmation, a prior note, or a named conversation with the person responsible. If the item is safety-critical or legality-critical and you do not have evidence, it stops the entry.
Gate 3: driver readiness
Driver readiness is easy to fake because an intermediate driver has already survived enough events to feel competent. That can be useful confidence, but it can also hide drift. Johnson names open-mindedness and concentration as keys to driver preparation. He also describes practicing basic driving skills constantly, even away from the track: paying attention, being critical of your own driving, placing the car exactly, and stopping smoothly. Bentley adds that study helps you learn faster once you are behind the wheel because you can picture the theory before you drive.
Your checklist should ask whether you are ready to learn at this event, not merely whether you want to attend. What is the driving skill you are working on. What is the evidence from your last event that this is the right skill. What will you do in the first session to make that skill visible. What would an instructor or coach notice if you are improving. If the checklist cannot answer those questions, the event may still be fun, but it is not yet a well-authored learning entry.
For an intermediate driver, the readiness question often comes down to attention. Can you keep concentration when traffic is close. Can you stay open-minded when the car or class exposes a weakness. Can you avoid turning every session into a proof of identity. The checklist should include a mental no-go. If you are registering while tired, angry, rushed, or trying to rescue your ego after a bad result, mark that condition. You may still enter, but you should not pretend the driver is neutral.
A strong driver-readiness gate has three parts. First, write the event purpose in one sentence. Second, write the behavior you will practice. Third, write the cue that will tell you whether the behavior improved. For example, the purpose might be to stop wasting practice by chasing other cars. The behavior might be to run the first session at controlled pace while identifying track priorities. The cue might be that your notes after the session describe specific surfaces, radii, camber changes, elevation changes, and straight lengths rather than vague feelings. That cue is grounded in track-reading, not self-congratulation.
Gate 4: track readiness
Track readiness is one of the easiest gates to skip because registration usually happens before the driver is thinking deeply about the circuit. That is backwards. Bentley is explicit that before you can consistently drive at the limit, you need to know the track well, and that knowing the track means more than knowing which way each corner goes. Surface, bumps, curbs, radius, camber, elevation, and straightaway length all shape the work you are signing up to do.
Before registration, your track gate should answer two questions. First, what does this track reward. Second, what does this track punish. You do not need expert notes yet. You do need enough of a track model to know whether the event matches your goal and whether the class choice exposes a weakness you are willing to work on.
Bentley and Johnson both support prioritizing corners by reward. The basic logic is that corners leading onto meaningful straights matter because they determine straightaway speed, and you spend a lot of time accelerating on most road courses. The checklist version is practical: before you register, sit down with a track map and identify the corners that deserve your first attention. Then identify the corners that are likely to tempt you into wasting attention because they feel dramatic but do not lead to much time gain.
Do not confuse track readiness with memorization. A driver can memorize the map and still have no plan. Track readiness means you have a first hypothesis. Which corners must protect exit speed. Which braking zones are likely to demand patience. Which sections are rhythm sections where overdriving one corner ruins the next. Which surface or camber changes could affect your confidence. If the checklist cannot name these, it should require a pre-event study action before registration becomes green.
This gate also protects safety. Bentley's practice advice is clear: practice is for learning the track and finding setup, and it is foolish to waste it by crashing. A pre-registration checklist should therefore include a first-session risk plan. If you are entering a track you barely know, your first session is not a qualifying simulation. It is a data-gathering session. If you cannot accept that, the driver-readiness gate should turn yellow or red.
Gate 5: session strategy
Registration is easier when you imagine only the race. Real weekends are built from sessions: practice, qualifying, and racing, or HPDE sessions that build one after another. Your checklist should include a session strategy because the way you use the first session shapes the rest of the weekend.
For practice, the goal is learning and setup, not winning practice. Bentley's warning against crashing in practice belongs directly in the checklist. Before entering, decide what practice is for. Is it learning the track. Is it confirming the car. Is it checking a setup change. Is it reestablishing rhythm after time away. The answer changes how you drive the out-lap, how much traffic you tolerate, and how quickly you increase pace.
For qualifying or timed sessions, the strategy changes. Bentley notes that qualifying rewards one extremely quick lap and that it is often better to wait for a clear gap rather than drive in a group that slows you down and steals concentration. Johnson gives a related timing-station example: after an acceptable time, verify that officials recorded it and then save the car for the race. The checklist version is to enter with a plan for traffic, timing, and restraint. If your only qualifying plan is go hard, the checklist should mark strategy as incomplete.
For the race or primary run group, write the first-lap intention and the learning intention separately. The first-lap intention is about surviving the opening phase and getting to work. The learning intention is about the skill you came to practice. Mixing them creates confusion. In traffic, your job may be to protect concentration. On a clear lap, your job may be to execute the track priority plan. In either case, the registration checklist should make the job visible before the event begins.
Gate 6: budget and recovery margin
Budget is not a moral issue. It is a performance and safety issue because a driver under financial strain makes different decisions. Johnson directly links intelligent racing with staying within the limits your bank balance gives you. The checklist should take that seriously. If the entry fee consumes the money you needed for preparation, repair margin, or the next event, the entry is not really green. It is a disguised compromise.
A useful budget gate is not just total cost. It asks what must be true after the event. Can you afford the preparation needed before the weekend. Can you afford to absorb normal wear. Can you afford to skip a session if the car needs to be saved. Can you afford to say no to a class that demands more than the car or budget can support. The most dangerous budget answer is not red. It is yellow treated as green.
This gate connects back to class selection. A class with faster cars, deeper preparation, or more serious competitors may be attractive, but the cost of keeping up can change the character of the season. Johnson's professional-racing discussion is an extreme example: the seriousness, preparation level, and skill level increase. You do not need to be chasing professional racing to learn from that. Every class jump has a cost. The checklist forces you to see it before you register.
Gate 7: the information loop
The last gate looks past the event. Johnson emphasizes recording and analyzing the pertinent information from the race soon after it ends, well ahead of the next event. That turns one weekend into material for the next. If you skip this loop, every registration starts from memory, mood, and scattered impressions.
Your pre-registration checklist should begin with the last post-event notes and end with the next note template. Start by reading what you learned last time. What problem did you say you would fix. What did the car need. What did the driver need. What did the track expose. Then create the capture points for the upcoming event. What will you record after each session. What will you tell the crew. What will you compare after qualifying or timed runs. What decision will you make before entering the next event.
This is where Johnson's advice about reading gauges and remembering information for the crew becomes a checklist habit. Do not depend on paddock memory. Decide before registration what information matters enough to capture. If the car has an issue, you need to describe it. If the driver has a recurring error, you need to name it. If the class choice feels wrong after the event, you need enough notes to know whether the problem was car, class, driver, track, or preparation.
Technique: build the matrix
Open a one-page matrix with seven rows, one for each gate. Add five columns: evidence, unresolved question, action, owner, and decision. Evidence keeps you honest. Unresolved question prevents vague anxiety from disappearing. Action turns yellow into work. Owner prevents assumed responsibility. Decision forces the final gate color.
Use green, yellow, and red, but define them tightly. Green means the item is ready enough to register. Yellow means the item can become green before a deadline and has an owner. Red means the item blocks registration or requires changing the class, event, car, or goal. A yellow item without an owner is red. A yellow item without a deadline is red. A red item that you plan to ignore is no longer a checklist item. It is a decision to accept risk, and you should write it that way.
The matrix works best when it is specific enough to make excuses uncomfortable. Do not write car ready. Write the preparation item, the evidence, and the open action. Do not write learn track. Write the track priority hypothesis and the study action. Do not write budget okay. Write the cost ceiling and the recovery margin. Do not write driver focused. Write the first-session behavior that proves focus.
The final decision line should have only four possible outcomes. Register as planned. Register with named constraints. Change class or event. Do not register yet. That last option is important. If the checklist cannot say no, it is not a decision tool. It is decoration.
Calibration cues: how you know the checklist is working
A working checklist changes the feel of the week before the event. You should have fewer surprise decisions in the paddock. Your first session should have a clear job. Your track notes should be more concrete. Your car feedback should be easier to explain. Your budget should not require denial. Your post-event notes should contain the facts needed for the next entry.
On track, the calibration cue is not automatically lap time. In early practice, a better cue may be restraint: you learn the track and car without turning practice into a crash risk. In qualifying, a better cue may be concentration: you seek a clear gap rather than being pulled into a group that ruins the lap. In race preparation, a better cue may be discipline: once an acceptable objective is achieved, you save the car instead of spending it for ego.
In your own behavior, the cue is language. If you find yourself saying probably, should be, or I will figure it out there, the checklist is not complete. If you can state the gate, evidence, action, owner, deadline, and decision without drama, the checklist is working. The point is not to eliminate uncertainty. The point is to stop pretending uncertainty is readiness.
Failure modes and recovery
The first failure mode is entry-form momentum. The registration page is open, the deadline is close, and you start treating payment as progress. Recovery is to pause before payment and fill the seven gates. If two or more gates are yellow, do not register until each yellow has an owner and a deadline. If any red gate is legality-critical, safety-critical, or budget-critical, stop.
The second failure mode is class vanity. You choose the class that sounds like the driver you want to be instead of the event you can prepare for. Recovery is to compare class demands against current car preparation, current driver execution, and available budget. If the answer depends on heroic driving or last-minute fixes, the class is not green.
The third failure mode is track blindness. You enter because the class seems right but you have not studied what the track rewards. Recovery is to build a first track priority map before registration. Identify the corners that feed important straights, the corners that are low-reward distractions, and the surface or elevation features you must learn early.
The fourth failure mode is practice-as-qualifying. You register with no session strategy, then use practice to prove pace. Recovery is to write the first-session job in advance. Practice should gather information and build programming. If the weekend has qualifying, write the traffic plan and the lap plan separately.
The fifth failure mode is paddock memory. You assume you will remember what happened, what the gauges did, what the car felt like, and what you told yourself after the race. Recovery is to create the post-event note template before the event. The pre-registration checklist starts the information loop; it does not wait until you are tired after the race.
The sixth failure mode is fine-point obsession. Johnson warns that fine points come after basics. In checklist terms, this means you should not spend energy on clever little advantages while the basic gates are yellow. If class fit, car readiness, driver focus, track plan, and budget are not clean, the sophisticated details can wait.
How to use this lesson at your next event
Seven to ten days before registration closes, run the checklist once without trying to solve anything. Mark green, yellow, and red honestly. Then solve only the red and yellow items that determine whether the event is still worth entering. Do not turn the checklist into a giant project plan. Its job is to make the entry decision clean.
Three to five days before registration closes, run it again with evidence. Every green should have proof. Every yellow should have an owner and deadline. Every red should change the entry decision. If you cannot resolve a red without hoping, do not enter that class as planned.
After the event, complete the loop. Record the information while it is still fresh. What did the class demand. What did the car need. What did the driver need. What did the track reward. What should be changed before the next registration. That final note becomes the first evidence column in the next checklist. This is how a season becomes development instead of a chain of isolated weekends.
Worked example: Laguna Seca corner priorities before registration
Suppose you are considering an event at Laguna Seca. The class decision has already been made in principle, so the checklist is not asking whether Laguna Seca is exciting. It is asking whether this entry has a track plan. Bentley's track-priority example points to a practical mistake: the corner that leads onto the longest straight is not automatically the most important if another corner is faster and also leads onto a long straight. In the example, Turn 4 becomes more important than Turn 7, while Turns 2 and 3 are lower priority because they do not lead onto much of a straight.
In the checklist, that becomes evidence. Under track readiness, you write that Turn 4 is a high-priority exit corner, Turn 7 is important but not automatically the top priority, and Turns 2 and 3 are not where the first study pass should be spent. Under session strategy, you write that first practice will test whether your braking, turn-in, and throttle timing protect the exits that feed meaningful acceleration. Under driver readiness, you write that the first session is not for proving pace; it is for confirming the track model.
The entry becomes green only if the track model is specific enough to guide behavior. If the checklist simply says learn Laguna Seca, it is yellow. If it says use Turn 4 as a primary exit-speed reference, watch whether traffic steals concentration in the early sessions, and record which surface or camber details changed the plan, then the event has a purpose. That is the difference between a registration and a prepared entry.
Worked example: Turn 8 and the backstretch as a priority test
Johnson's Turn 8 example is useful because it shows what a mature driver does with an unimportant section. Bruce and Denny did not treat most of Turn 8 like the whole lap depended on it. They gave it the priority it deserved and then launched onto the backstretch with serious exit speed. The pre-registration lesson is that your checklist should reveal whether you know which parts of the event deserve attention and which parts should be handled without drama.
Before registering, put one line in the track gate for the section most likely to tempt you. On many tracks, that temptation is a corner that feels brave, looks dramatic, or creates a story in the paddock. Then ask whether it actually feeds lap time, passing opportunity, or class execution. If it does not, the checklist should keep it from becoming the weekend's obsession.
A green answer sounds like this in substance: I know where the backstretch speed is made, I know which part of the preceding corner can be driven without over-investment, and I will judge the session by how well I position the car for the important exit. A yellow answer is emotional: I want to be fast through Turn 8. The checklist's job is to convert that emotion into priority. If you cannot, the track readiness gate remains yellow.
Worked example: stepping into a more serious class
Imagine you have been comfortable in a club-racing environment and are considering a more serious class or event. The earlier sibling lessons help you decide whether the class has people to race and whether the car or class should change. This checklist asks whether the step is ready now. Johnson's professional-racing discussion gives the warning in concentrated form: when the competition level rises, the car preparation level and driving skill level rise too, and a driver who cannot keep up will have a short career.
The pre-registration matrix should make that visible without drama. In class fit, write the preparation gap between your current car and the expected class standard. In driver readiness, write the skill gap between your current execution and the class pace. In budget, write the cost of closing the gap and the recovery margin after the event. In session strategy, write how you will use practice if you are not immediately on pace.
If the class is yellow because one preparation item remains, and that item has an owner and deadline, registration may be reasonable. If the class is yellow because the whole plan depends on you suddenly driving beyond your current skill, treat it as red. The checklist protects development by separating a useful stretch from an ego entry.
Common mistakes
Mistake 1: treating registration as commitment before readiness. The bad version is paying first and solving later. The good version is running the seven gates before payment, then registering only when red items are resolved and yellow items have owners.
Mistake 2: writing feelings instead of evidence. The bad version is car should be fine, class should work, and I know the track well enough. The good version names the preparation item, the class reason, the track priority, and the session plan.
Mistake 3: letting class identity override limits. The bad version is entering a class because it sounds like the next level. The good version compares the class to car preparation, driver skill, budget, and the event's actual demands.
Mistake 4: arriving track-blind. The bad version is studying only the direction of the corners. The good version identifies surface, radius, camber, elevation, straight length, and corner priority before the event.
Mistake 5: using practice to prove speed. The bad version is treating practice like qualifying and risking the car while still learning the track. The good version gives practice a job: learn, confirm, and build the weekend.
Mistake 6: skipping the post-event loop. The bad version is leaving the event with memories that fade. The good version records the important information soon after the race so the next pre-registration checklist starts with evidence.
Drill: the three-pass registration gate
Run this drill before your next event. It takes about 45 minutes the first time and about 20 minutes once it becomes familiar. Use the same event you are actually considering, not an imaginary perfect weekend.
Pass 1 is the decision pass. Set a timer for 10 minutes. Fill the seven gates quickly: class and event fit, car and equipment readiness, driver readiness, track readiness, session strategy, budget and recovery margin, and information loop. Mark each green, yellow, or red. Do not fix anything during this pass. The success criterion is honesty: at least one gate should contain a real unresolved question unless the event is already very well prepared.
Pass 2 is the evidence pass. Set a timer for 20 minutes. For every green, write why it is green. For every yellow, write the owner and deadline. For every red, write the entry consequence: change class, change event, delay registration, or do not enter. The success criterion is that no yellow remains ownerless and no red remains hidden.
Pass 3 is the track and session pass. Set a timer for 15 minutes. Write the first track-priority hypothesis and the first-session job. If the event includes qualifying or timed runs, write the traffic and timing plan. The success criterion is that your first session has a purpose other than going fast.
After the event, spend 15 minutes completing the information loop. Record what the class demanded, what the car needed, what the driver learned, what the track rewarded, and what should change before the next registration. That note becomes the first evidence source for the next drill.
When the checklist should stop you
The checklist should stop you when a red item affects legality, safety, budget, or the basic honesty of the class decision. It should also stop you when the plan depends on becoming a different driver by the first session. Improvement is the reason you enter. Fantasy is not.
It should slow you when the issue is real but controllable. A yellow item is not failure. It is a task with a deadline. If the car needs one preparation confirmation, the driver needs one focused study session, or the track plan needs one map review, the checklist gives you a way to move forward cleanly.
It should let you go when the entry has purpose. Green does not mean perfect. It means ready enough, with known risks, a learning plan, and a way to carry information into the next decision. That is the standard. Not certainty. Preparedness.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | Driving in competition None Johnson Alan 1935- None | 17d31ba3-7629-8532-3e20-7b2a0bd7d80f | 2 | 1 | uio_books_raw_v1 |
| 2 | Driving in competition None Johnson Alan 1935- None | 9b6fb8b6-10bd-03c5-45b0-97cc40cab004 | 157 | 1 | uio_books_raw_v1 |
| 3 | Driving in competition None Johnson Alan 1935- None | 2b9ce0bd-6f1b-b810-a9c2-3ebe6a0cd348 | 150 | 1 | uio_books_raw_v1 |
| 4 | Ultimate Speed Secrets - Ross Bentley | 0237a5bd-e2d4-724e-bc2e-ba13db924f66 | 11 | 1 | uio_books_raw_v1 |
| 5 | Ultimate Speed Secrets - Ross Bentley | a8d5edf3-33e8-42aa-eae2-72f9bd238948 | 184 | 1 | uio_books_raw_v1 |
| 6 | Ultimate Speed Secrets - Ross Bentley | 48ba6002-83bf-7d1d-35d6-8d8a03dd28d8 | 185 | 1 | uio_books_raw_v1 |
| 7 | Ultimate Speed Secrets - Ross Bentley | d64f3ac3-8ef8-0bfd-1ea5-ca5dc9d308c0 | 197 | 1 | uio_books_raw_v1 |
| 8 | Ultimate Speed Secrets - Ross Bentley | 88f4e6ce-94d6-96b6-34c2-f83da10bcb40 | 508 | 1 | uio_books_raw_v1 |
| 9 | Driving in competition None Johnson Alan 1935- None | affec95e-99b0-690c-9949-baa3a4351721 | 155 | 1 | uio_books_raw_v1 |
| 10 | Driving in competition None Johnson Alan 1935- None | 1b06f8d5-7b12-60b7-2bc8-4b205ce91b6b | 147 | 1 | uio_books_raw_v1 |
| 11 | Driving in competition None Johnson Alan 1935- None | 9d60560d-4219-ded4-d22b-1ae96b9b2982 | 65 | 1 | uio_books_raw_v1 |
| 12 | Driving in competition None Johnson Alan 1935- None | 1cf8ccc5-ed81-7e18-9129-2492609f97d9 | 53 | 1 | uio_books_raw_v1 |
| 13 | Driving in competition None Johnson Alan 1935- None | 579297db-e375-4af6-25e9-0d5d31739cd4 | 81 | 1 | uio_books_raw_v1 |
| 14 | Driving in competition None Johnson Alan 1935- None | 6a03cb53-d625-3dca-3e9d-26d427cca31b | 154 | 1 | uio_books_raw_v1 |
| 15 | Speed Secrets Professional Race Driving Techniques Ross Bentley | 8b546b81-602a-e872-facb-d67640333134 | 6 | 1 | uio_books_raw_v1 |
| 16 | Ultimate Speed Secrets - Ross Bentley | 47f6de8d-9d56-5b6d-547a-f1e7bb92faaf | 152 | 1 | uio_books_raw_v1 |