Present your car so officials can read it
Generated from
content/lms/race-class-rules-and-categories/05-let-rules-shape-the-prep-plan/04-present-the-car-so-officials-can-read-it.md; edit the source file, not this page.
Source path: content/lms/race-class-rules-and-categories/05-let-rules-shape-the-prep-plan/04-present-the-car-so-officials-can-read-it.md
Course: Choose the race class that fits your car and goals
Module: Let rules shape the prep plan
Estimated duration: 55 minutes
The skill in this lesson is not how to pass tech by arguing, hiding, charming, or hoping. The skill is to present the car so the official can understand it quickly, verify the required facts, and decide that the car belongs on track. At the intermediate level, you already know that rules matter. Now you need to make the car, the paperwork, and your paddock behavior tell one consistent story.
That story has three parts. First, the car is the same car the paperwork describes. Second, the safety condition you claimed before the event is still true when the car reaches the grid, tech lane, or impound. Third, if the car has changed because of damage, repair, altered equipment, missing equipment, or post-session contact, you bring that change to the officials instead of making them discover it.
That is why readability is a preparation skill, not a cosmetics skill. A clean, organized, document-backed race car is easier for officials to evaluate. A confusing car makes the official slow down, poke deeper, and wonder what else is unclear. Alan Johnson's old racing advice is blunt on this point: a beginner should expect tech inspectors to notice small omissions, to be suspicious of unfamiliar work, and to be focused on safety before they are impressed by ingenuity. The practical response is not resentment. The practical response is to arrive with a car that can be probed without producing surprises.
The core principle is simple: make compliance visible before speed becomes relevant. The annual inspection, the event inspection form, the tech sticker, the logbook, the VIN or car identity, the driver's gear, and the current physical state of the car all need to agree. If they do not agree, the official is no longer reading a prepared car. The official is now investigating a discrepancy.
This lesson is intentionally narrower than the sibling lessons in this module. It does not decide where minimum preparation ends and wise preparation begins. It does not teach how to preserve a class identity through parts choices. It does not budget legal upgrades, and it does not analyze loophole builds. Here, your job is operational: once the car has been prepared under the applicable rules, you stage it so the people responsible for safety and legality can verify it without guesswork.
Start with the official's job. In NASA race procedures, an annual race car safety inspection happens before the vehicle's first race each calendar year. An authorized tech official or authorized competition vehicle tech shop completes the annual technical form. The driver then presents that form to the regional chief scrutineer at the first event before going on track. When accepted, an annual tech sticker is affixed in the required place. The rules also say that no car may enter a competitive session without the required annual tech sticker, unless the required approval exists. That is not just paperwork trivia. It tells you what officials are reading first: a chain from inspection, to form, to sticker, to the car in front of them.
Safety inspection does not end after the annual sticker appears. NASA also makes the driver responsible for inspecting the car at each event, and officials may inspect cars for safety issues at any time. Random safety checks are common in the cited rule text. That means you cannot treat annual tech as a permanent shield. The annual sticker says the car completed a required inspection. It does not say that a loose part, outdated safety item, damaged harness mount, missing sticker, or altered safety system will be ignored later.
In HPDE-style school rules, the same readability principle appears in a different form. A pre-event technical inspection by a qualified entity may be required. The participant remains solely responsible for the safe condition of the vehicle driven to, at, and from the event. Some procedures require the tech form to represent one vehicle, include the complete VIN, and match the actual car brought to the event. If the participant changes vehicles, a new form is required for the replacement vehicle. Even when the chapter is not allowed to perform an actual inspection at the track, it may verify that the vehicle listed on the form is the same car presented for use at the event. In other words, the official may not be wrenching on your car, but the official is still reading identity, paperwork, and consistency.
SCCA race experience material frames the official role from the event side. Technical and safety inspection exists to certify that competition vehicles and required driver gear comply with the current event rules and supplementary regulations. Tech may issue stickers for compliant cars and helmets, conduct compliance checks at the request of safety or race control leadership, and report nonconforming cars. That tells you another part of the readability skill: your helmet, personal gear, and car are part of one compliance presentation. Do not make the official chase your helmet in the trailer, your logbook in the tow vehicle, and your car identity in a half-filled form.
The first surface officials read is documentation. A readable document packet is not a folder stuffed with every receipt you own. It is the small set of documents the event actually needs, arranged so the official can confirm identity and status quickly. For a race weekend, that usually means the car logbook when required, the annual race car technical form or proof of annual inspection, the relevant event tech form, and any notes that explain changes since the last inspection. For a school or HPDE setting, it may mean the completed pre-event technical inspection report, signed at the inspection, tied to the correct VIN, and presented at registration before driving begins. If the event instructions say to bring a helmet or personal safety gear to tech, that gear is part of the document-and-equipment presentation.
The second surface is the car's identity. Identity means more than make, model, and color. It is the specific vehicle represented on the specific form. The HPDE rules in the bonded corpus are explicit that only one vehicle is represented on each tech form, and that the vehicle used on track must be the same vehicle represented within the tech inspection form submitted for that day's event. That principle matters in racing too, because the logbook, annual tech form, tech sticker, and class paperwork all point to one physical car. If you bring a replacement car, borrow a car, swap a chassis, or change the car after the paperwork was completed, the official should hear that from you before the official finds the mismatch.
The third surface is safety equipment. NASA's annual inspection section includes annual inspection, event inspection, re-inspection after major crash or safety equipment alteration or damage, missing required annual sticker, and an emergency exit time standard. That creates a practical staging checklist. Belts, seat, harness mounts, roll bar or cage elements, fire system or extinguisher where applicable, window net or arm restraints where applicable, driver gear, and exit path should not be buried, blocked, stale, or unexplained. You are not presenting a show car. You are presenting a machine whose safety systems need to be understood quickly.
The fourth surface is current condition. A car can have correct paperwork and still be unreadable if the current condition contradicts the paperwork. Loose bodywork, a missing muffler, damage from contact, altered safety equipment, missing or outdated equipment, and an unresolved logbook note all move the car out of routine presentation and into re-check territory. NASA's impound rule specifically requires cars that lost body panels, had body contact, or lost parts on track to report to impound. The rule also requires body contact report forms to be turned in within the stated time window. The lesson is not that every scuff ends a weekend. The lesson is that after a reportable change, officials need to read the changed car before you treat it as unchanged.
The fifth surface is your behavior. Officials read the driver as much as the car. If you arrive late, leave the logbook elsewhere, get defensive about a visible defect, make adjustments after the checkered flag when the rules say no adjustments are allowed, or cannot provide tools and crew for a requested disassembly, you have made the inspection harder. If you arrive with the car staged, the paperwork ready, the gear present, and a calm explanation of any change since the last inspection, you make the official's job easier. That does not guarantee a pass. It does make the process clean.
A useful mental model is the cold read. Imagine the chief of tech has never seen your car, knows nothing about your history, and has three minutes to decide whether this car belongs in the next session or requires more attention. What can that official learn without asking you to unpack the trailer, move five loose items, remove a cover, find missing paperwork, or explain why the VIN on the form does not match the car? If the answer is not enough, the car is not ready to be read.
Prepare the cold read before you leave home. Begin with the event's actual rules and supplemental regulations. The New Drivers and Minor Drivers Guide notes that before going on track, a driver must visit scrutineers, usually tech, to obtain a tech sticker, and that the car logbook and sometimes helmet or personal safety gear may be required. It also points you toward registration, paddock placement, grid entry, fuel, timing and scoring, medical, meetings, stewards, results, and other event locations. Those details are not busywork. They keep you from using tech time to solve basic event-orientation problems.
Before the event, match the paperwork to the physical car. On an HPDE form, that means the correct car, correct VIN where required, one car per form, current inspection window where required, participant signature, and replacement form if the car changes. On a race car, it means the annual form, logbook, sticker location, notes, and any event forms agree with the car that will actually be presented. If the car had safety equipment altered, safety equipment damaged, a major crash that involved a tow, a missing annual tech sticker, or a logbook indication requiring re-inspection, do not wait for a line worker to discover it. Schedule or request the correct re-inspection.
Then make the car physically legible. Clean enough does not mean polished. It means an inspector can see what needs to be seen. Mounting points should not be hidden by loose gear. Belts should not be buried under bags. A helmet that needs a sticker should be with the car or in your hand, not somewhere in the paddock. The battery, fire bottle or extinguisher, tow hooks, cutoff switch, cage or roll bar areas, seat mounts, harness attachments, window net and latch, and other safety-related items should be accessible according to the car's rule set. The Johnson chunk makes the cultural point well: tech inspection crews are likely to complain about what they can find, and sometimes that nit-picking may catch something important. If the official can easily see the important items, minor confusion has less room to grow.
Staging also means removing noise. Loose tools, spare parts, drink bottles, unmounted cameras, unsecured radios, and random paddock clutter tell the official that the car may not have been checked as a system. The bonded rules do not list every loose-item example, so do not overread this as a source-specific checklist. The grounded point is narrower: officials are checking safe condition, required equipment, and legal preparation. Anything that blocks those checks or makes the current condition ambiguous works against you.
When you arrive at the event, do the process in the order the event expects. Registration commonly comes first to resolve outstanding items and receive credentials. Then the driver finds paddock space and prepares the car for tech. Before track activity, the driver visits scrutineers to obtain the sticker or complete the required check. If the event expects the logbook, helmet, annual paperwork, or safety gear, bring it then. A readable car can still lose a session if the driver loses the paperwork timeline.
At tech, answer the question being asked. If the official asks whether the car on the form is the car presented, the answer is an identity answer, not a story about your build. If the official asks whether the car has had contact, altered safety equipment, or a missing sticker, answer the condition question directly. If the official asks for the logbook, do not offer a photo unless the event permits it. The official is not there to admire how much effort went into the car. The official is there to certify, verify, or escalate based on the current rules.
The strongest intermediate habit is change discipline. Any meaningful change to the car should pass through a simple question: does this change affect what an official would have inspected, documented, or stickered? If yes, bring it forward. A replacement vehicle after a pre-event HPDE inspection requires a new form in the cited rules. A major crash with a tow, safety equipment alteration or damage, logbook note requiring new inspection, or missing annual tech sticker requires re-inspection in the NASA text. A car that lost a body panel, had body contact, or lost parts on track must report to impound under the NASA race procedure. These are not all the possible examples in every organization, but they show the pattern: when the car changes, the reading changes.
Impound is where this skill becomes high-pressure. After a race, NASA's rule sends the top four finishing drivers and cars in each class to impound immediately. It also sends cars with body contact, lost body panels, or lost parts to impound. The driver is responsible for reporting directly to impound with the vehicle and logbook at the proper time. If the driver must stop in pit lane after the checkered flag, no adjustments to the vehicle are allowed, while taking tire temperatures is permitted. That rule creates a precise behavioral standard. Do not cool the brakes by changing duct tape. Do not tidy a dangling panel. Do not top off fluids. Do not change anything that could alter what tech is about to read. Bring the car as it finished, with the logbook.
Disassembly readiness is part of readability for race cars. The NASA text gives tech inspectors broad authority to inspect anything at any time for any reason and says competitors should have crew and tools to disassemble requested items. If the competitor is not prepared to comply, the vehicle or part assemblies may be taken to a shop for compliance checks. That does not mean you need to scatter tools across the paddock. It means your crew plan should include who can remove the requested item, where the right tools are, and how you will comply without drama. A car that can only be verified by a missing specialist or an unavailable tool is not fully readable under post-session pressure.
The official's read also includes the driver gear. SCCA race experience rules identify tech and safety inspection as covering competition vehicles and required driver gear. Tech duties include issuing both tech stickers and helmet stickers to compliant equipment. NASA annual inspection procedures include emergency exit testing with the driver wearing required gear and tightly belted when the clock starts. So when you present the car, think of driver gear as connected to the vehicle's safety system. A helmet out of date, missing from tech, or separated from the car when a sticker is needed can stop the same day just as effectively as a car issue.
The mechanism behind all of this is risk control through verification. Organizations require inspections because wheels, fuel lines, belts, driver gear, and other safety systems affect more than the driver in one car. They affect other drivers, workers, insurance exposure, and whether the event can continue. Johnson's explanation connects race-car preparation to the confidence of tech inspectors: they want a car prepared in a way that convinces them the wheels will not fall off and fuel lines will not come loose. Modern rulebooks put consequences behind the same idea: fines, disqualification, license consequences, removal of annual stickers, impound, re-inspection, and compliance checks.
A readable presentation reduces uncertainty. It does not reduce the standard. If the car is illegal, unsafe, missing equipment, or out of date, presentation will not make it legal. But if the car is properly prepared, readability prevents a good car from looking like a questionable car. That distinction matters at crowded events, when officials have limited time and many cars to process. Your preparation should let them spend their attention on the rule issue itself, not on avoidable confusion.
Use five sub-skills to build the habit.
Sub-skill one is document discipline. Create a compact event packet before loading the car. For race use, include the car logbook when required, annual inspection paperwork, current event tech paperwork, and any note that explains a required re-inspection or repair. For school or HPDE use, include the pre-event tech inspection form completed by the qualified person, with the correct car and VIN when required, and signed where required. Do not rely on memory for which form belongs to which car. The bonded HPDE material is clear that the vehicle represented on the form must be the same car used on track.
Sub-skill two is identity discipline. The car you unload must be the car the paperwork describes. If you change vehicles, you change paperwork. If the car's logbook or annual form has a note requiring attention, you treat that note as part of the car's identity. If the annual sticker is missing, you treat that as an inspection problem, not as decoration. The goal is not to make officials trust your memory. The goal is to let them connect car, form, sticker, and logbook without a gap.
Sub-skill three is access discipline. Put required items where they can be inspected. Clear the cockpit of clutter. Have the helmet and required gear available when the event asks for it. Know how the hood, trunk, cutoff, tow points, window net, belts, seat, fire equipment, and cage or roll bar areas can be shown. Access discipline does not mean taking the car apart before anyone asks. It means the official does not have to fight your paddock mess to see basic safety systems.
Sub-skill four is change discipline. Any contact, lost part, damaged safety equipment, altered safety equipment, major crash, tow, missing sticker, or replacement vehicle should trigger a check against the event rules. Some changes require re-inspection. Some require impound. Some require a new form. Some require a report within a time window. Intermediate drivers often lose ground here because the car seems basically fine. The rules in the bonded corpus care about reportable conditions, not your optimism.
Sub-skill five is interaction discipline. Be calm, direct, and prepared. SCCA's race experience material emphasizes calm, clear, sympathetic correction and discipline from driver coaches. You should make the official side of the conversation easier in the same spirit. Do not bury a simple answer under defensiveness. Do not treat a safety concern as a personal insult. Do not negotiate with the line worker over a rule you did not read. If there is a disagreement, ask what document or official process governs the next step.
You will know you are improving when tech becomes boring in the right way. Registration and tech stop feeling like a hunt for missing items. The official can match the car to the form without asking you to search for numbers. The annual sticker, event sticker, helmet sticker, or logbook status is easy to confirm. If there is a change or repair, you already know whether it requires re-inspection or reporting. If you are sent to impound, your first movement is toward impound with the car and logbook, not toward the toolbox.
Another calibration cue is how few assumptions you ask officials to make. A weak presentation asks the official to assume the replacement car is acceptable on the old form, assume the logbook note was handled, assume the missing sticker fell off after inspection, assume the loose panel is harmless, or assume the driver gear is current somewhere else. A strong presentation asks the official to verify facts that are physically present.
There is also a time signature. A readable car costs time at home and saves time at the track. The pre-event document match, gear staging, cockpit clear-out, and change review may take an hour in the garage. At the event, that hour becomes a quiet tech line, a clean first session, and no scramble to find a qualified inspector after the driver's meeting. In racing, it also protects post-race time. If the car goes to impound and a compliance check requires tools, your crew already knows the plan.
The most important recovery rule is this: if the car becomes unreadable, stop making it more unreadable. After damage, contact, a lost part, or a paperwork mismatch, do not hide the issue under speed, heat, or schedule pressure. Bring the issue to the right official. If the rules require re-inspection, report, new form, impound, or no adjustments, follow that path. The cost of a lost session is smaller than the cost of a penalty, disqualification, safety failure, or credibility loss.
Presenting the car well is not an attempt to make officials less strict. It is a way to let strict inspection work efficiently. A well-prepared race car should be able to stand there quietly while officials read it. The paperwork says what the car is. The stickers show what has been accepted. The logbook records what needs attention. The current condition matches the story. The driver knows what changed. That is the standard you are practicing.
Worked example: first event of the year with annual tech
You are bringing a race car to its first event of the calendar year. The temptation is to think of the annual inspection as something that happened at the shop and is now behind you. That is not the operational skill. The skill is to connect the annual inspection to the first on-site presentation.
Before loading, you confirm that the annual race car technical form was completed by the authorized person or shop. You put that form with the car logbook and the event paperwork. You check where the annual sticker must be placed once accepted, because NASA's cited procedure requires the sticker on the lowest part of the driver's side windshield when applicable, or on top of the roll bar in open cars without separate approval. You also check whether the car has any logbook note, missing sticker problem, safety equipment alteration, safety equipment damage, or major crash history that would require re-inspection.
At the track, you do not let the car drift into the paddock as an undocumented object. Registration is handled, credentials are received, and then the car is staged for the regional chief scrutineer or tech process with the paperwork and logbook in hand. If personal gear must be reviewed because this is the first event of the year, that gear is present. If the helmet needs a sticker, it is not locked in the trailer. The official can read annual inspection, car identity, driver gear, and sticker status in one place.
A weak version of this same morning looks different. The driver says the shop did annual tech but cannot find the form. The logbook is in the tow vehicle. The helmet is back at the hotel. The cockpit is full of loose gear. The annual sticker is missing, or there is an old sticker in a questionable place. None of those facts proves the car is unsafe, but together they force the official to investigate rather than verify. That is what this lesson is trying to prevent.
Worked example: post-race impound after contact or a lost part
You finish a race and either place in a position that requires impound, have body contact, lose a body panel, or lose a part on track. Under the NASA procedure in the bonded corpus, the top four finishing drivers and cars in each class must proceed to impound immediately, and vehicles with body contact, lost body panels, or lost parts must also report to impound. If in doubt about finishing position, the driver and vehicle report to impound. The driver is responsible for reporting directly with the vehicle and logbook.
The readable presentation starts before you reach the impound space. You do not stop in pit lane and adjust the vehicle after the checkered flag. The cited rule allows tire temperatures, but no adjustments. That distinction matters because impound is supposed to read the car as it finished. If you repair, remove, tighten, tape, or alter something before officials see it, you have changed the evidence.
Once in impound, your job is controlled compliance. The logbook is with the car. If body contact occurred, the required report form is turned in within the required window. If the official asks to inspect a part, you do not argue that the car was fine at speed. If a requested disassembly is part of the compliance check, the bonded NASA text expects the competitor to have crew and tools ready. The correct behavior is to make the check possible.
The common failure is the instinctive paddock repair. A driver sees a loose panel, missing muffler bracket, rubbing tire liner, or damaged corner and wants to make it tidy before anyone sees it. That instinct may be normal in the paddock, but it conflicts with impound readability. The official needs the car's post-session condition, not the cleaned-up version. Your skill is to pause the mechanic reflex until the rules allow work.
Worked example: HPDE replacement vehicle after pre-event tech
You registered for a driving school with one car, had that car inspected within the required pre-event window, and signed the pre-event tech inspection report. Two days before the event, that car develops a problem and you decide to bring a different car. The bonded HPDE material is exact about the principle: the vehicle used on track must be the same vehicle represented within the tech inspection form for that day's event, only one vehicle is represented by each form, and a replacement vehicle requires a new form.
The correct intermediate move is not to arrive with the old form and explain at check-in that the replacement car is basically similar. You get the replacement vehicle inspected by a qualified person who is familiar with that make and model, complete the form for that specific car, include the complete VIN if the form requires it, sign the correct statement, and present that form at registration. If the chapter is operating under a hands-off verification model, staff may still verify that the car on the form is the same car you brought.
The reason this matters is not bureaucracy for its own sake. The pre-event inspection is an identity-and-condition claim about a particular vehicle. When you change vehicles, you break the connection between the inspection and the car. A readable presentation repairs that connection before the event staff has to challenge it.
Common mistakes and what good looks like
Mistake one: treating tech as a negotiation. You arrive with a questionable item and plan to talk your way through it. What good looks like: you arrive with the applicable form, sticker, logbook, and current condition aligned. If there is a questionable item, you already know which official process applies and you ask for that process rather than arguing in line.
Mistake two: separating the documents from the car. The car is ready, but the logbook is in another vehicle, the annual form is in an email you cannot quickly find, or the HPDE form is in a bag under the trailer. What good looks like: the required documents travel as part of the car's track-day kit, and the person presenting the car can produce them without leaving the tech interaction.
Mistake three: using the wrong form for the right car, or the right form for the wrong car. This is especially common when two similar cars are in the same household, shop, or team. What good looks like: each form identifies one vehicle, the VIN or required identity fields match the physical car, and replacement vehicles get replacement paperwork.
Mistake four: hiding a changed condition behind schedule pressure. The car had contact, lost a part, damaged safety equipment, or changed safety equipment, but the next session is close. What good looks like: you treat change as a trigger. You check the rule path for re-inspection, report, impound, new form, or official review before the car returns to the normal flow.
Mistake five: presenting a cluttered cockpit. The official may need to see belts, seat, mounts, nets, gear, exit path, or other safety items, but the interior is full of loose paddock items. What good looks like: the cockpit is clear enough for the safety systems to be read, and driver gear that must be checked is available.
Mistake six: making post-checkered adjustments before impound. The driver thinks a quick fix is harmless because the race is over. What good looks like: if the rules send you to impound, you go to impound with the vehicle and logbook, avoid adjustments, and wait until the process permits work.
Mistake seven: no disassembly plan. A compliance check asks for access to a part, but the crew member with the tool is gone, the tool is buried, or nobody knows how to remove the item cleanly. What good looks like: for a race weekend, your crew has a basic impound compliance plan and knows where the relevant tools are.
Mistake eight: mistaking cosmetic cleanliness for readability. A shiny car can still be confusing if the paperwork does not match, the sticker is missing, or a safety system is inaccessible. What good looks like: the car is clean enough to inspect, organized enough to understand, and documented enough to connect to the rules.
Drill: the three-minute tech read
Run this drill before your next event. Do it once at home before loading, once in the paddock before going to tech, and once after the first session if the car had any contact, curb strike, loose part, or repair.
For the home pass, give yourself twenty minutes. Put the car where you can walk around it. Place the required documents, logbook, event form, annual paperwork, helmet, and required driver gear in one staging area. Then ask a helper to perform a three-minute cold read. The helper does not need to be a licensed tech inspector. The helper's job is to answer these questions from visible evidence: what car is this, what form represents it, what sticker or annual status applies, what gear goes with it, and what visible condition would make an official slow down. If the helper cannot connect car, form, sticker, logbook, and gear within three minutes, fix the presentation.
For the paddock pass, give yourself ten minutes before you enter the tech process. Confirm that registration items are complete, the car is the car on the form, the cockpit is clear enough to inspect, gear that may need review is present, and no event-specific instruction has been missed. The success criterion is that you can walk to tech without returning to the trailer for a basic required item.
For the post-session pass, give yourself five minutes before doing ordinary service work if there was any incident or visible change. Ask whether the car had contact, lost a part, lost a body panel, damaged or altered safety equipment, or created a condition that your rules send to impound or re-inspection. The success criterion is not that the car goes back out. The success criterion is that you identify the correct official path before you touch the car in a way that could change what officials need to read.
When this principle changes by organization
Different organizations put different limits on who may inspect, what must be presented, and when a car can be checked. That is why this lesson teaches a presentation principle instead of one universal tech-line script.
In the NASA race material, officials may inspect cars for safety issues at any time, random safety inspections are common, post-race or qualifying legality inspection can inspect anything at any time for any reason, and competitors may need crew and tools for requested disassembly. The driver is responsible for annual and event inspection duties, impound reporting, and the car's logbook.
In the HPDE material from the bonded corpus, the participant is still solely responsible for safe vehicle condition, but the chapter or people acting for the chapter may be prohibited from performing the actual inspection or at-track inspection. Even there, the chapter may verify that the vehicle listed on the pre-event inspection form is the same car presented for the event, and instructors may perform visual and verbal safety verification. The inspection authority is different, but the readability requirement remains.
In SCCA race experience material, the technical and safety inspector's job includes certifying that vehicles and required driver gear comply with current rules and supplementary regulations, issuing stickers, conducting checks when requested by safety or race control leadership, and reporting nonconforming cars. Again, the practical driver skill is the same: know which official is reading the car, know what that official is authorized to check, and present the car so the check can happen without confusion.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | NASA_Club_Codes_and_Regulations_CCR_2025.5 | 0502178197c1e934fc68dd3b824f6cf7 | 69 | 1 | uio_books_raw_v1 |
| 2 | NASARules2023 | 2f9fff55cb864f460d956e1e2a5ac44a | 70 | 1 | uio_books_raw_v1 |
| 3 | Driving in competition None Johnson Alan 1935- None | e4f6a604-3cd4-1272-d619-b770fbca52de | 34 | 1 | uio_books_raw_v1 |
| 4 | HPDE_Verbatim_Master_Compilation | 2950d188808673ddc2bd565a345cbaee | 295 | 1 | uio_books_raw_v1 |
| 5 | RACE EXPERIENCE RULES | c847c14e9bca676ed203ef4dc499e9b2 | 56 | 1 | uio_books_raw_v1 |
| 6 | New Drivers and Minor Drivers Guide v1.0 | 52b5e9e8885b461b1b284e754b2db070 | 1 | 1 | uio_books_raw_v1 |
| 7 | ACNA_Driving_School_Guidelines_2013-03-05 | 236e5078e3334fdfb8ec92b8e541beaa | 11 | 1 | uio_books_raw_v1 |
| 8 | HPDE_Verbatim_Master_Compilation | e1a363b324c40d8818a0dbd812fed1d9 | 70 | 1 | uio_books_raw_v1 |