Verify the car before you trust the story
Generated from
content/lms/platform-specific-spec-miata/01-identify-the-car-before-you-plan-it/02-verify-vin-and-visual-cues.md; edit the source file, not this page.
Source path: content/lms/platform-specific-spec-miata/01-identify-the-car-before-you-plan-it/02-verify-vin-and-visual-cues.md
Course: Race a Spec Miata by the rulebook
Module: Identify the car before you plan it
Estimated duration: 55 minutes
The skill: build an identity chain before you build a plan
A Spec Miata can come with a convincing story. It may have a cage, numbers, a logbook, race tires, a seller who knows the right vocabulary, and a paddock history that sounds plausible. None of that is enough. The skill in this lesson is learning to verify the car itself before you trust the story around it.
For this module, do not treat identification as trivia. Identification controls the rest of the plan. The car's VIN, model year, class identity, rule set, event registration, tech form, logbook information, and physical condition must point to the same answer. When they do, you can plan the car. When they do not, you have not found a small paperwork annoyance. You have found an unresolved contradiction.
Spec Miata makes this stricter than an ordinary track-day garage check because the class is production-based and modification-limited. The SCCA Spec Miata language ties the original OEM VIN on the firewall to the model year automobile classified, says VIN plates or stampings remain in place, and gives the firewall VIN precedence. The same rule section says classified cars and weights are listed on the Spec Miata table, and that the factory manual for the specific make, model, and year is required so scrutineers can identify parts and configuration. It also ties engines and internal parts to the correct year and VIN of the car unless the rules say otherwise. That is the core principle: in Spec Miata, the car's legal identity is not whatever the seller, driver, or registration nickname says. It is anchored to the physical car and then checked against the rule set.
The HPDE side teaches the same habit from a different direction. Event instructions warn that the vehicle you bring must match the vehicle indicated on your MotorsportReg registration, and that the car you bring must match the tech form. NASA tech-form instructions put the responsibility on you to inspect the car before bringing it to the track or tech station, to consult an inspector if there are questions, and to have the top of the form filled out before inspection. These are not ceremonial details. They are the event version of the same identity chain: the car, the paperwork, and the person responsible for it must agree before the car belongs on track.
Your working rule is simple: the story is not trusted until the channels agree. Channel one is the physical car. Channel two is the rule and class paperwork. Channel three is the event paperwork and inspection record. If any one channel disagrees with the others, stop planning performance improvements and resolve the identity problem first.
What you are actually verifying
You are not trying to become a concours judge. You are not trying to memorize every NA and NB detail in this lesson. That belongs to the sibling lesson on mapping the NA and NB family. You are not fully separating a legal Spec Miata from every look-alike here either. That belongs to the sibling lesson on separating the Spec Miata from the look-alike. You are doing the first practical pass that makes those later decisions possible: you are proving that the car in front of you is the car the paperwork describes.
Start with four questions.
First, what does the physical car say it is? The strongest starting point in the bonded material is the firewall VIN, because the Spec Miata rule gives it precedence. Then look at visible identity fields that inspection paperwork expects to record: year, make, model, VIN, color, class, GCR weight, track width, wheelbase, displacement, logbook number, restrictor size, car number, class decals, required rule set, and shop manual. These are not all things you will personally measure in a paddock walk-around, but they tell you what a serious inspection process treats as identity-bearing information.
Second, what does the rule set say that identity allows? The Spec Miata rule says the class is for low-cost, production-based cars with limited modifications. It says authorized modifications and safety items are the only permitted or required items unless another section requires safety equipment. It also says updating or backdating is not allowed except where specifically authorized. That means the car's model year and VIN are not just labels. They narrow the parts and configurations that can honestly belong on the car.
Third, what does the event paperwork say you are bringing? The BMW CCA preparation instructions have students verify that the vehicle is in the MSR profile and that it matches the vehicle on the MSR registration. They also tell the student to fix the registration if it shows the wrong vehicle. The same packet says a vehicle mismatch against the registration or the tech form means the car will not be permitted on track. That is a hard operating lesson: your car's identity is only useful if the event systems reflect it correctly.
Fourth, what does the inspection record say about readiness? The annual technical safety form asks for identity fields and then checks drivetrain, interior, suspension, steering, exterior, electrical system, fuel-cell compartment, and logbook items. BMW CCA guidance adds that tech inspection can reveal service issues that take time to resolve, so you schedule it early, resolve failed items, and get a new signed form if a re-check is required. Readiness is not the same thing as identity, but the two touch. A wrong car on a correct-looking form is not ready. A correct car with failed inspection items is not ready. A correct car with vague or incomplete inspection paperwork is not ready enough to trust.
The three-channel identity method
Use the three-channel method every time you inspect a Spec Miata candidate, refresh a car file, or prepare for an event.
Channel one is the physical car. Put your eyes and hands on the car. Confirm the firewall VIN first because the rule gives it priority. Then make a slow pass around the car and note the visible identity cues: color, number and class decals, body panels secured, fender coverage, lights, towing eyes, required decals if applicable, and general neatness. Move from identity cues to inspection cues: wheels and tires, brakes, steering wheel and freeplay, wheel bearing freeplay, suspension and tie-rod freeplay, fluid leaks, lines, battery mounting, positive terminal protection, fire system labels, restraint dates, ballast mounting, and logbook-related details. You are not doing a full annual inspection by yourself unless you are qualified and assigned to do that. You are learning what contradictions look like.
Channel two is the class and rule paper. For Spec Miata, the high-value paper is the current GCR Spec Miata category specification and the factory manual for the specific make, model, and year. The bonded GCR chunk says the manual is required to help scrutineers identify parts and configuration. That tells you how to think: if you cannot explain which manual and which rule set apply to the car, you are not done identifying it. If the seller's story requires a mix of model years, an update, a backdate, or an engine-part story that is not clearly allowed by rule, treat that as an open issue, not a clever shortcut.
Channel three is the event and inspection paper. This includes the MSR profile vehicle, MSR event registration vehicle, tech form, logbook, annual inspection if relevant, and any class-specific event requirements. The HPDE forms and BMW CCA packet are blunt about this. Fill out the top of the tech form before going to the inspector. Verify the form is accurate and complete. Bring the tech sheet. If the car does not match the registration or tech form, it does not get on track under those instructions. The event may not care how good the story sounds in the paddock.
Once you have all three channels, compare them the way a data coach would compare traces. Look for incongruencies. Dig for details. Use other channels if they are available. Ask why. Compare if you can. Those phrases come from a driver-data process chunk, but the thinking transfers cleanly to car identification. A car identity problem is usually not solved by staring at one clue harder. It is solved by comparing independent channels until the contradiction disappears or becomes a clear stop sign.
How to read the firewall VIN without over-reading it
The firewall VIN is your anchor, not your whole answer. The GCR language makes it decisive for the model-year automobile classified, and it says VIN plates or stampings remain in place. If the firewall VIN does not correspond to the claimed model year or the classified car being discussed, the planning process stops. You do not buy parts. You do not choose class weight. You do not assume an engine specification. You do not register the car as the story. You resolve the VIN problem.
But the firewall VIN does not prove every part on the car is correct. The same rule section that anchors identity also says engines and internal components used in rebuilding or refurbishment must have been offered by Mazda in the United States for the correct year and VIN of car unless otherwise provided. It also says assembly, rebuild, refurbishment procedures, dimensions, and specified components must follow factory procedures unless the rules say otherwise. So the VIN tells you the starting identity. It does not absolve you from checking whether the car's components and paperwork match that identity.
This is where intermediate drivers often get sloppy. They use the VIN to win an argument, then stop looking. Good verification does the opposite. The VIN tells you what questions to ask next. Does the class line match? Does the logbook match? Does the tech form match? Does the shop manual match? Do the engine and internal-component claims match the correct year and VIN? Does the event registration match the car you will actually bring? If the answer is yes across the chain, you have a car you can plan. If the answer is mixed, you have an investigation.
Visual cues that matter, and visual cues that do not
A race-looking Miata can be a legal Spec Miata, a non-compliant project, an HPDE car, a retired race car, or a parts mixture. Visual cues help, but they need discipline.
The cues that matter are the cues that connect to a rule, inspection field, or event requirement. The technical safety form expects the car's year, make, model, VIN, color, class, GCR weight, track width, wheelbase, displacement, logbook number, and restrictor size. It also calls out car number and class decals, required decals, minimum weight and restrictor size, wheels and tires, brakes, steering, suspension, ballast mounting, body panels, lights, towing eyes, fire system labels, battery mounting, and shop manual or required rule set. That form is a map of what experienced inspectors care about. Use it as a viewing guide.
The cues that do not matter by themselves are the ones that only make the car look serious. A drilled rotor, a loud exhaust, a big radiator opening, a seat with race-car visual drama, or a sticker package may tell you something about prior use or owner taste, but those cues are not proof of class identity. The SuperMiata guide is useful here because it is skeptical of showy track-car choices. It warns against drilled rotors for track duty and points out that cooling choices depend on the whole system, not one visible opening. The lesson is not to copy that guide into Spec Miata legality. The lesson is to resist being impressed by isolated visible upgrades before you have checked the identity chain.
On a walk-around, say to yourself: visible does not mean verified. Numbers are visible. Class decals are visible. A logbook number is recorded. A firewall VIN is stamped. A tech form has a vehicle line. The job is to make those things agree.
A practical inspection sequence
Use this sequence when you are standing in front of the car.
Begin with the claimed identity. Before touching the car, write one plain sentence: this car is being represented as a specific Spec Miata-class car under a specific rule context for a specific use. Do not make it fancy. If you cannot write that sentence clearly, the story is already too vague.
Next, find the firewall VIN and record it exactly. Do not rely on a dashboard glance, a social-media listing, a memory, or a previous owner's label. The Spec Miata rule gives the firewall VIN precedence. If the firewall VIN cannot be found, cannot be read, or does not match the claimed model-year classification, stop and get knowledgeable help before continuing.
Then compare the VIN to the documents available in the car file. The bonded packet does not give you a title-check procedure, so do not invent one here. Use the channels it does give: the class rule, the shop manual requirement, the logbook or annual inspection fields, the MSR vehicle profile or event registration, and the tech form. Your goal is not to perform legal title research inside this lesson. Your goal is to avoid building an HPDE or Spec Miata plan on a car that the event, tech inspector, or rules do not recognize as the car being claimed.
After that, use the annual inspection form categories as a visual walk path. Start at the front left corner and look for wheel and tire condition, brake hardware, suspension and steering looseness, wheel bearing freeplay, obvious leaks, and secure bodywork. Go corner by corner. Carl Lopez gives the race-prep version of the same habit: look at the suspension on each corner for loose jam nuts, disconnected sway-bar links, missing safety wire, and similar small things that can go wrong. His point is timing as much as thoroughness: do this early, before false grid, so there is time to handle the rare suspect item before it becomes crunch time.
Then open the inspection-paper channel. Is the top of the tech form filled out before inspection? Is the vehicle line correct? Does the car you are looking at match the vehicle listed on the registration? Was a failed item resolved? If a re-check was required, is there a new signed tech form? BMW CCA's preparation packet even reminds drivers that failing paperwork means not driving on track. Treat that as a teaching cue. Your verification skill includes paperwork precision, because the track event does.
Finally, decide. If all channels agree, you move from identification to planning. If one channel is incomplete, label the missing item and get it before making decisions that depend on it. If channels disagree, stop. Do not choose parts. Do not register under the questionable identity. Do not go on track to see whether the car behaves as expected. The BMW CCA malfunction guidance is direct: if you think the car may have a malfunction, get knowledgeable assistance and do not go on track to test your perception. The same conservative rule belongs in identity verification. Track sessions are for driving and learning, not for proving that an unresolved car story is harmless.
The difference between identification and inspection
Identification asks what the car is. Inspection asks whether the car is safe and compliant enough for the intended use. They are different skills, but they overlap.
If you inspect without identifying, you can pass a car-like object through a checklist while missing that the wrong vehicle is on the registration, the wrong year is being used for parts planning, or the wrong class line is being assumed. If you identify without inspecting, you may correctly name the car and still miss obvious readiness issues that keep it off track. Good paddock work keeps both in view.
The BMW CCA manual explains why this matters. During a school, the car is under far more stress than a typical supermarket run or even spirited canyon driving. A well-maintained car performs better and makes the experience more enjoyable because you can focus on driving instead of worrying about the car. The same manual's technical inspection appendix says most items can be checked visually, but the inspection should be thorough. It calls this inexpensive insurance for safety, and it directs questionable findings to a mechanic or club member. That is the correct tone for this lesson: you are not hunting for drama, but you are not waving away doubt either.
The technical safety form reinforces the breadth of the overlap. It records identity fields at the top, then moves into driver equipment, drivetrain, interior, suspension and steering, exterior, fuel-cell area, electrical system, and logbook. A serious car file therefore carries both identity and condition. When you plan a Spec Miata, you want both columns to be clean enough that your next decision is a driving or setup decision, not a hidden car-history problem.
How class variants can create identity traps
The bonded packet includes regional Spec Miata language that mentions SM, SMT, SMSE-T, and SMSE. This lesson is not the place to memorize those classes. The sibling lesson on using the spec line before you spend owns that work. But you need to understand why the class line is an identity cue, not a decoration.
The regional rules say SM must comply with the SCCA GCR and category specifications for Spec Miata. They also say SMT and SMSE-T run under specified rule contexts with a tire-rule exception using Toyo Proxes RR tires in size 205x50x15, with Toyo RA1 also allowed and recommended only for wet conditions. The same regional packet says SMSE was created for owners of the 1.6 Mazda Miata as a low-cost class in SEDiv series, and that it must comply with current GCR and category specifications for listed 1.6 cars. Again, do not turn this lesson into a class-eligibility chart. Take the practical lesson: a class name changes what you must verify.
If a seller says the car is a Spec Miata, ask which rule context they mean. If an event entry says SM but the car was discussed as a regional variant, ask why. If a tech form class field, decals, tires, and owner story point in different directions, do not smooth over the conflict. Put it in the discrepancy list. Resolve it before spending money or towing to an event.
How to handle discrepancies
A discrepancy is not automatically a deal-breaker. It is automatically a stop-and-verify point.
Use a neutral first pass. You are not accusing anyone. You are comparing channels. The data-process chunk gives the right sequence: look for incongruencies, dig for details, use other channels if available, ask why, compare if you can, calibrate to your driving, imagine the ideal, and set objectives for the next session. For car identity, translate that into a paddock process. What exactly disagrees? Which independent channel can confirm it? Who is qualified to answer? What decision depends on the answer? What will you do next only after the answer is clear?
If the firewall VIN and claimed model-year identity disagree, stop at the identity level. If the event registration and car disagree, fix the registration before the event. If the tech form and car disagree, correct the form or re-tech the car as required. If a physical cue raises a safety or mechanical concern, get knowledgeable assistance. If the car has a possible malfunction, do not take it on track to test whether you were right. If a class or rule question remains open, treat the current plan as provisional.
Alan Johnson's old advice on getting involved with race organization is still useful here. He tells aspiring racers to go to tech inspection with someone and learn what happens there, because inspection crews vary and learning to deal with that part of club organization eases the strain when you go racing yourself. That is not just social advice. It is a calibration method. The more real inspections you observe, the better you become at separating paperwork friction from a genuine car-identity problem.
Calibration cues: what improving feels like
You are improving when your inspection conversation gets shorter and more precise. Early on, you may say the car seems like a Spec Miata because it has a cage and numbers. That is weak. A better version is that the firewall VIN, logbook, tech form, MSR registration, class line, and visible inspection fields all point to the same car and rule context, with one named item still waiting for a mechanic or inspector. The best version is that you can explain what each channel proved and what it did not prove.
You are improving when you stop being pulled around by cosmetics. A race seat, decals, tire choice, rotor style, or loud exhaust no longer carries the argument by itself. You treat those as prompts to inspect, not proof. You can admire a tidy car and still ask for the VIN, logbook, tech form, and rule context.
You are improving when your event mornings become boring in the right way. The car in MSR is the car on the trailer. The car on the tech form is the car at the tech station. The top of the form is filled out accurately. The pages are together. The vehicle passed or has a documented re-check. There is no last-minute argument about whether the wrong car was registered. That boring rhythm is a sign of skill.
You are improving when you know when to stop. The manual's malfunction guidance warns against going out to see whether your perception was accurate. In identity work, the equivalent is refusing to let a session, purchase, or build plan become the test of an unresolved contradiction. A mature driver pauses earlier and asks better questions.
Cross-references inside this module
Use this lesson before the sibling lessons. Map the NA and NB family before you plan the car will give you broader platform context. Separate the Spec Miata from the look-alike will sharpen the distinction between race-car appearance and class reality. Use the spec line before you spend will take the rule-specific buying decision deeper. This lesson is the gate before those gates: prove which car and which paperwork you are dealing with before the rest of the plan becomes expensive.
If you already know the NA and NB family well, do not skip this. Familiarity can make you faster, but it can also make you assume. The bonded material keeps pulling you back to recorded facts: firewall VIN, classified model year, required manual, correct year and VIN for engine components, event registration match, tech form match, complete paperwork, and knowledgeable assistance when something seems questionable. That is the posture you want.
Worked example: the BMW CCA registration mismatch
You are loading for a school and the car in the trailer is not the vehicle currently listed in the MSR registration. Maybe you planned to bring one car, changed plans, and forgot to update the event dashboard. Maybe the profile contains both cars but the wrong one is attached to the event. Maybe the tech form was filled out for the other vehicle.
The bonded BMW CCA preparation packet makes the decision for you. The vehicle in the profile, the vehicle on the event registration, and the vehicle on the tech form must match the car you bring. If the registration shows the wrong vehicle, fix it. If the car does not match the registration or the tech form, that vehicle will not be permitted on track under those instructions.
The lesson is not that MSR paperwork is more important than driving. The lesson is that the event uses paperwork to bind one physical car to one driver, one inspection, and one permission to enter the track. Your job is to close that loop before you leave home. The success state is simple: you can point to the car, the MSR entry, and the tech form and they all identify the same vehicle. If they do not, you are not in a driving problem yet. You are in an identity problem.
Worked example: the Spec Miata firewall VIN versus the story
A car is represented as a Spec Miata with a confident history. It has a cage, class decals, a number, and a pile of receipts. The first serious identification question is not whether the story is confident. It is whether the original OEM VIN stamped on the firewall corresponds with the model-year automobile being classified.
The GCR Spec Miata language gives the firewall VIN precedence and says VIN plates or stampings remain in place. It also ties engines and internal components to the correct year and VIN of car unless the rules specifically allow otherwise. That means the firewall VIN does two jobs. It anchors the model-year identity, and it tells you which follow-up questions matter.
If the firewall VIN, logbook, class line, factory manual, and event paperwork agree, the story has started to earn trust. If the firewall VIN points one way and the story points another, do not split the difference. Do not keep planning as if the story is probably right. Stop and resolve the identity. In Spec Miata, the attractive explanation is not the anchor. The stamped car is.
Worked example: regional class language as an identity fork
A Miata is described casually as a Spec Miata, but the regional paperwork around it mentions SM, SMT, SMSE-T, or SMSE. This is not a reason to panic, and it is not a reason to guess. It is a reason to identify the exact rule context before making a plan.
The regional class chunk says SM must comply with the SCCA GCR and category specifications. It says SMT and SMSE-T run under specified rule contexts with a tire-rule exception, including Toyo Proxes RR tires in size 205x50x15 and RA1 allowed with a wet-condition recommendation. It also says SMSE was created for owners of the 1.6 Mazda Miata as a low-cost class in SEDiv series and must comply with GCR and category specifications for listed 1.6 cars.
The practical move is to ask which class line the car is actually being prepared for and then compare the physical car, decals, tires, event entry, tech form, and rule paper. This lesson does not ask you to decide every legality question from memory. It asks you not to let a generic label hide a fork in the rules.
Drill: the three-channel identity audit
Do this drill before your next event or before you seriously plan a Spec Miata purchase. Total time is 30 minutes. You need the car, the current rule or class reference you are using, the event registration or MSR vehicle entry if there is an event, the tech form or annual inspection record if available, and a blank note page.
For the first 8 minutes, audit the paper channel. Write the claimed car identity in one sentence. Then record the event registration vehicle, tech-form vehicle line, class line, logbook number if present, and rule set or shop manual reference if present. Do not fix anything yet. Just record what each paper source says.
For the next 12 minutes, audit the physical channel. Record the firewall VIN exactly. Then walk the car using inspection-form categories as your path: visible number and class markings, color, wheels and tires, brakes, steering, suspension, obvious leaks, body panels, lights, towing eyes, battery mounting, fire-system labels, ballast mounting, and any logbook-related markings. You are not trying to perform a full tech inspection. You are looking for agreement or disagreement with the paper channel.
For the next 7 minutes, compare the channels. Circle every item that disagrees, every item you could not verify, and every item that requires a qualified person. Use the data-process habit: look for incongruencies, dig for details, use other channels, ask why, and compare if you can.
For the final 3 minutes, write the decision. Use one of three outcomes. Outcome one: channels agree, proceed to planning. Outcome two: one or more items are missing, get the missing item before planning depends on it. Outcome three: channels conflict, stop and resolve before purchase, registration, or track use. The success criterion is not finding a perfect car. The success criterion is producing a clear, written identity decision with no vague maybe.
Common mistakes
Mistake one is trusting the race-car costume. Numbers, decals, a cage, a loud exhaust, and track wheels can all be real and still not prove the car's identity or readiness. Good looks like using those cues as prompts, then checking firewall VIN, class line, registration, tech form, logbook, and rule context.
Mistake two is treating the VIN as the end instead of the start. The firewall VIN is the anchor because the Spec Miata rule gives it precedence, but the same rule set also cares about correct year and VIN for engine components and factory procedures. Good looks like using the VIN to choose the next questions, not to stop asking.
Mistake three is assuming the event will accept the explanation. The BMW CCA packet is clear that a vehicle mismatch against MSR registration or tech form keeps the car off track. Good looks like correcting the registration and paperwork before the event, not asking grid or tech to absorb a preventable mismatch.
Mistake four is doing tech too late. BMW CCA warns that technical inspection may reveal service issues that take time to resolve. Carl Lopez gives the same timing lesson from race prep: visual once-over early, before false grid, so a suspect item can be handled before crunch time. Good looks like scheduling inspection early and leaving time for a re-check if repairs are needed.
Mistake five is using the track as the test bench. The malfunction guidance says to get knowledgeable assistance and not go out to see whether your perception was accurate. Good looks like stopping when an identity, mechanical, or safety question is unresolved and asking an instructor, safety chief, inspector, mechanic, or experienced club member.
Mistake six is letting class shorthand hide details. SM, SMT, SMSE-T, and SMSE can sound similar in casual paddock talk, but the regional language shows that class context can affect requirements. Good looks like naming the actual rule context before spending money or registering.
When to stop and ask for help
Stop when the firewall VIN is unreadable, missing, inconsistent with the model-year claim, or not aligned with the paperwork you have. Stop when the tech form identifies one car and the physical car is another. Stop when the MSR event registration lists the wrong vehicle. Stop when a class line is used casually but the decals, tires, paperwork, and rule set point in different directions. Stop when a physical inspection cue suggests a possible malfunction or unsafe condition.
The bonded sources give you several acceptable helpers. NASA instructions say to consult a tech inspector if there are questions. BMW CCA malfunction guidance points to an instructor or chief of safety. The BMW technical inspection appendix says questionable items should go to a mechanic or club member. Johnson's advice points you toward learning from tech inspection crews and club operations. Use those people before the car is on track, before the budget is committed, and before a vague story turns into your problem.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | GCR_SM | 8aaac52cf61cfb33dae2abb73f7a7a52 | 1 | 1 | uio_books_raw_v1 |
| 2 | BMW CCA RMC How to Prepare for the Event | c249264f-c2e3-dc3b-4f4d-ef6649341522 | 2 | 1 | uio_books_raw_v1 |
| 3 | BMW CCA RMC How to Prepare for the Event | e105dec2-abb9-255e-227d-3367f8514e2e | 1 | 1 | uio_books_raw_v1 |
| 4 | NASA HPDE Tech Form 2026.1 | f2c978a8-8d09-8ef2-cdcd-c9b3d4b1b961 | 1 | 1 | uio_books_raw_v1 |
| 5 | 2020 Tech Safety Annual InspectionH 8 11 2020 | 38330aec70b94b664ed9b3b47b8865d1 | 1 | 1 | uio_books_raw_v1 |
| 6 | 2023 Regional Class Rules | 63384ad5199ffa8ecc8abca763c50e09 | 4 | 1 | uio_books_raw_v1 |
| 7 | BMW CCA RMC Driving School Manual 2023-06 | 2cb8166a-44a6-adef-7d05-a5d503f12a1e | 11 | 1 | uio_books_raw_v1 |
| 8 | BMW CCA RMC Driving School Manual 2023-06 | 760e9068-e1c0-19af-2e2e-d41d762fdb07 | 11 | 1 | uio_books_raw_v1 |
| 9 | BMW CCA RMC Driving School Manual 2023-06 | 1098bd14-c393-29ec-1883-8d3c98d21b2b | 27 | 1 | uio_books_raw_v1 |
| 10 | Going Faster Mastering the Art of Race Driving - Carl Lopez | 7d859725-67d6-1174-ad9b-a13d5896d445 | 175 | 1 | uio_books_raw_v1 |
| 11 | Data-for-Drivers-PRINT | bbb02386-778f-20ec-ad16-b9c016921743 | 16 | 1 | uio_books_raw_v1 |
| 12 | Driving in competition None Johnson Alan 1935- None | d2681f34-2d1f-6fe7-1362-aa9c3308cef9 | 19 | 1 | uio_books_raw_v1 |
| 13 | HPDE Verbatim Master Compilation | 881e3857-c9c0-95a8-fbcc-f32d8dcc8cea | 1 | 1 | uio_books_raw_v1 |
| 14 | HPDE Verbatim Master Compilation | 7c91ac8b-38e1-52ca-0496-14a34a79008f | 121 | 1 | uio_books_raw_v1 |
| 15 | Unofficial SuperMiata Guide (2018) | b0f4d9f57c34f92c14f2cd770c2f7c7e | 12 | 1 | uio_books_raw_v1 |
| 16 | Unofficial SuperMiata Guide (2018) | 1c0d87bece37025c69faea960a403a39 | 10 | 1 | uio_books_raw_v1 |