Drive inside your brain's bandwidth limit
Generated from
content/lms/mental-game-ii-perceptual-science/01-build-your-perceptual-map/01-recognize-the-processing-limit.md; edit the source file, not this page.
Source path: content/lms/mental-game-ii-perceptual-science/01-build-your-perceptual-map/01-recognize-the-processing-limit.md
Course: See sooner and decide faster at speed
Module: Build the map your brain drives from
Estimated duration: 55 minutes
Skill you are building
This lesson is about driving at a pace your brain can actually support. Not the pace your ego wants, not the pace your lap timer dares you to try, and not the pace that worked once when everything lined up. The skill is to keep the car, the track, and your decisions inside your current processing capacity so your inputs stay deliberate, smooth, and useful.
That matters because performance driving is not only a mechanical task. Your hands and feet move because your brain tells them what to do. Your judgment about entry speed, brake release, steering rate, throttle timing, and track use depends on the quality of the information your brain receives and how efficiently it processes that information. When that input is clean and your mental programming is strong, you can drive closer to the limit with less conscious effort. When the input is noisy, late, or overloaded, the same car and same corner suddenly feel like too much.
For an intermediate driver, the trap is subtle. You already know the flags, the line, the basic brake-turn-apex-track-out sequence, and enough car control to survive mild mistakes. That means you can run fast enough to expose the next limiter: mental bandwidth. You may not be spinning or missing every apex, but you may be driving with your brain half a corner behind the car. The result is usually not dramatic. It looks like slightly late turn-in, slightly abrupt brake release, slightly extra steering, slightly early maintenance throttle, and slightly unused track at exit. Add those small delays together and the lap feels busy while the stopwatch says you are giving time away.
The goal is not to think more. The goal is to feed your brain better information, reduce unnecessary task load, and build enough mental programming that more of the lap can run on well-trained automatic responses. You are not trying to become passive. You are trying to become available. When the next important cue appears, you want enough unused attention to recognize it and act.
The principle: quality input, useful processing, clean output
The core rule is simple: your driving output can only be as good as the information and programming feeding it. Bentley's mental-performance material returns to this repeatedly. Better sensory input improves skill. Practice builds programming. Mental imagery strengthens that programming. Focus affects what you get. Physical and emotional state can degrade the information coming in. On a good day, you feel switched on because you are processing quickly and efficiently. On a bad day, it can feel as if the same familiar track is arriving too fast.
In this lesson, brain bandwidth means the practical limit of what you can perceive, interpret, decide, and convert into car control at the speed you are driving. It is not a fixed number. It changes with fatigue, anxiety, confidence, preparation, experience at the track, familiarity with the car, and how many new tasks you are trying to manage at once. It also changes within a session. The first lap after a long break may use more bandwidth than lap four. A corner you know well may cost almost none. A corner with a new pavement patch, traffic, a yellow flag, and a late pass decision may consume all of it.
You control bandwidth with three dials.
The first dial is speed. Speed compresses time. The faster you arrive, the less time you have to sense speed, choose the braking point, release the pedal, set steering, feel rotation, and decide whether the car will use the full exit. This is why corner entry is so demanding. Setting entry speed is harder than squeezing throttle on exit because the entry requires you to judge what the car will need before the corner has fully happened.
The second dial is information quality. A lap is not just a ribbon of asphalt. It is a stream of visual, tactile, and timing information: cracks, curbs, surface changes, steering feedback, brake-pedal vibration, bumps, the way your view rotates as the car slides, where other cars appear around the circuit, and the reference points you have learned to trust. If the stream is sharp, your brain can make better decisions. If the stream is vague, you start guessing.
The third dial is task load. Trying to learn a new track, change your braking technique, work on smoother hands, chase a faster driver, monitor mirrors, and improve exit throttle all in one lap is too much for most intermediate drivers. The car may still be under control, but the quality of your decisions drops. You begin responding to what already happened instead of preparing for what comes next.
Driving inside bandwidth means you set those three dials so you can still produce clean output. Clean output means your brake application and release match the corner, your steering builds progressively, your throttle comes in as steering unwinds, your car uses the available track, and you can remember what happened afterward well enough to learn from it.
How the limit shows up at speed
Bandwidth trouble usually appears first as timing trouble. You do not suddenly forget how to drive. You arrive a little late to each job. You brake at the point you planned, but you are not settled enough to release cleanly. You turn in, but the car needs a bigger steering input than it should. You see the apex, but you are not sure whether you can reach it without pinching. You get to exit, but there is unused pavement outside the car because you either under-committed to speed or over-constrained the car with steering.
A useful way to read this is through steering. Bentley's cornering guidance is blunt: the less steering you need, the faster you can be. He also separates slowing the steering input from slowing the car. If your brain is overloaded, you often do the opposite. You delay the decision, then make the steering input more abrupt. That creates more tire demand right when the car is already using grip for braking or acceleration. Too much steering for the amount of braking or acceleration can push one end of the car past its traction limit. The car may understeer or oversteer, and it is tempting to blame setup, tires, or the track. Sometimes it is the car. Often, at this stage, it is your timing and your bandwidth.
Bandwidth trouble also appears as poor track use. If you are leaving inches of track unused at exit because you are not comfortable letting the car run out, you are giving away speed. But if you are using all the track only because the car is washing wide and you are out of choices, that is not the same thing. Good track use is planned. It comes from setting the entry speed, release, rotation, and throttle so the car naturally finishes where it should. Overloaded track use is accidental. The car arrives at the edge before your brain has caught up.
Another sign is poor recall. After a session, you should be able to mark where you began braking, where you ended braking, where you returned to full throttle, what reference points stood out, and what surface details mattered. If you come in hot and can only say that everything felt busy, you did not gather enough usable data from the session. You may have driven laps, but you did not build the map.
The bandwidth budget
Use a bandwidth budget any time you are learning, rebuilding confidence, or adding speed. Before the session, decide what the lap is allowed to cost you mentally. That sounds abstract, but it becomes concrete when you limit the number of jobs you are asking your brain to run.
Start with one primary job. For example, in a first session at a new track, the job may be to identify reliable visual references and build a mental map. You are not trying to optimize every entry. You are giving your brain high-quality input. You notice cracks, curbs, worker stations, surface changes, signs, bridges, and the shape of each exit. You are paying attention to what is new, not trying to prove speed before the track is loaded.
In a second session, the primary job might be speed sensing. You ask whether the speed you carry into each corner matches what the corner actually needs. Bentley stresses that you must develop an innate sense of how fast you are traveling and how much that speed must change before each corner. That is not only a speedometer task. In most track driving, you sense speed from visual flow, engine and tire feel, brake pressure, steering response, and whether the car arrives at the planned part of the track with margin.
In a third session, the job might be input shape. Now you are watching whether your steering, brake release, and throttle application are progressive enough to keep the tires at the limit rather than shocking them past it. If you are trail braking, the more steering you add, the more brake you release. As you unwind steering at exit, you add throttle. The bandwidth question is whether you can actually manage that exchange, or whether you are reciting the idea while your feet and hands are late.
This budget does not mean you ignore everything else. You still drive safely, give point-bys where required, watch flags, and respect traffic. It means the performance-learning focus is narrow enough that your brain can process it well. You are choosing one improvement job rather than pretending to do six.
The technique: build speed only after the map can carry it
The practical technique has four steps: load the map, stabilize the speed, shape the inputs, then add speed.
First, load the map. Every track has its own personality. Even two circuits with similar layouts can feel different. Before you ask for pace, you need a usable mental model of where the car is going, what references matter, and how the surface talks back. After a session, download the lap onto a track map. Mark the details of what you did and what you noticed: shift points, brake start, brake end, full-throttle return, cracks, curbs, worker stations, signs, bridges, pavement changes, and marks on the surface. This is not paperwork for its own sake. It turns a noisy session into stored structure.
Second, stabilize the speed. You do not need to be slow, but you need to be able to sense and set speed before each corner. If the entry speed is a guess, everything downstream becomes a correction. The entry phase is difficult because you are deciding the car's future while still approaching the corner. When you are inside bandwidth, the entry feels prepared. The brake point is chosen, the release is beginning on purpose, and turn-in is not a surprise.
Third, shape the inputs. Slow down the hands without slowing down the lap. Build steering in a way the tires can accept. If you are braking and turning, trade brake for steering rather than stacking both demands carelessly. If you are exiting, unwind steering as throttle rises. This is the physical expression of a brain that is ahead of the car. The car feels less busy because you are no longer using abrupt inputs to catch late decisions.
Fourth, add speed. Only add speed when the first three steps are stable enough that recall, timing, and input shape remain clean. If you add speed and immediately lose your map, miss your release, or stop using the full exit, you have exceeded your current bandwidth for that task. Back up one click. Your job is not to avoid discomfort forever. Your job is to stretch capacity without driving so far outside it that the session stops teaching.
Sub-skill: sensory input quality
Your brain cannot process information it never receives. One of the most useful intermediate upgrades is to deliberately sharpen your sensory channels. Spend sessions noticing what the car feels like over bumps, how quickly the steering responds, what vibration comes through the wheel, what the brake pedal tells you, and what you can see in the surface. Watch cracks, undulations, curb shape, changes in pavement, the direction your view changes as the car rotates, and where other cars appear on other parts of the track.
This is different from sightseeing. You are not collecting trivia. You are improving the quality of the raw material your brain uses to drive. A driver with cleaner sensory input can sense earlier whether the car is rotating, whether the brake release is too fast, whether the turn-in was late, or whether the exit curb is coming too soon. That earlier sensing buys bandwidth because the correction can be smaller and calmer.
Intermediate drivers often skip this because they want the next technique. But the technique depends on the feed. If the only thing you know about a corner is that it is turn five and you are supposed to apex late, your brain has very little to work with. If you know the approach texture, the brake marker, the pavement seam near release, the curb shape, the way the view opens at exit, and the feel of the car when it rotates correctly, you have a much richer map.
Sub-skill: speed sensing
Speed sensing is the ability to know how fast you are going and how much that speed must be altered for the next corner. This is central to staying inside bandwidth because a poor speed estimate forces your brain to solve the corner too late.
At first, speed sensing may be crude. You brake because you reached a marker. You turn because the cone or curb says to. That is fine as a starting point, but it is not enough. You want to feel whether the car is arriving too quickly before the braking zone is already over. You want to know whether the speed you released into the corner will let the car reach apex and still open the wheel on exit. You want to sense whether the car is at the tire's cornering limit after brake release, not just hope it is.
Practice this by asking one question after each important corner: did my entry speed give me choices, or did it take choices away? If you arrived with choices, you could release the brake deliberately, place the car, and decide throttle timing. If speed took choices away, you probably had to add steering, hold brake longer than planned, delay throttle, or accept poor track use. That is a bandwidth problem as much as a speed problem. The brain was forced into emergency accounting.
Sub-skill: mental programming and automatic control
Practice is not just repetition. It is programming. When you repeat a physical action with attention and accuracy, you strengthen the pathway that lets you perform it later with less conscious load. That is why skilled drivers can drive more of the car on automatic pilot. They are not asleep. They have built better programs.
This is also why sloppy practice is expensive. If you repeatedly turn in late and rescue the corner with extra steering, you are programming that rescue. If you repeatedly add throttle before you have started to unwind the wheel, you are programming that conflict. If you repeatedly drive laps without downloading what happened, you are programming vague driving. Inside-bandwidth practice asks for fewer jobs, done with higher quality.
Mental imagery extends this programming away from the car. After you have driven the track and gathered real information, replay the lap in your mind. The more accurate repetitions you do, the faster you learn the track and the more available your brain becomes in the car. Imagery is not fantasy pace. It is the mental rehearsal of the real references, timing, sensations, and decisions you want to execute.
Sub-skill: state management
Your processing limit is affected by your state. Fatigue, anxiety, emotional stress, alcohol, prescription drugs, and similar impairments can reduce the quality of information going into your brain. In a track-day context, the practical version is simple: do not judge your bandwidth from your best lap on your best morning. Judge it from the state you are actually in during this session.
If you are tired late in the day, your budget should shrink. If you are anxious after a slide, your budget should shrink. If traffic has made the session mentally loud, your budget should shrink. This is not weakness. It is accurate self-management. The fastest sustainable driver is not the one who pretends every lap has the same mental capacity. It is the one who notices capacity, protects input quality, and chooses the correct task load.
Worked example: the unfamiliar-track first session
Imagine your first session at a track you have studied but never driven. You know the map and maybe some video, but the surface, sightlines, curbs, and camber are not yet in your body. The bandwidth mistake is to chase pace immediately because the layout looks familiar on paper.
A better first-session job is to build the perceptual map. You drive at a pace that lets you notice what you have never seen before. You identify where the surface changes. You notice which curbs are flat enough to use and which are only visual boundaries. You learn which worker station appears before the braking zone, which sign is visible in traffic, where a crack points toward the apex, and how the exit opens. You do not need to solve every corner at the limit yet. You need enough input that the next session can be smarter.
After the session, you download immediately. On a track map, you mark brake starts and ends, full-throttle returns, shift points, pavement features, curb shapes, and any reference that helped. Then you run mental imagery using that actual information. In the next session, the track costs less bandwidth because more of it is already loaded. You can now spend attention on speed sensing or input shape rather than basic orientation.
The wrong version is easy to recognize. You come in saying the track is fun but busy. You cannot remember where you ended braking. You cannot describe the exit of the corner that mattered. You know you were faster than the out-lap, but you cannot say why. That session may have been enjoyable, but it did not build enough map to support much more speed.
Worked example: the Trans-Am trail-braking lesson
Bentley describes learning straight-line braking first, then gradually learning trail braking, and later needing to improve it in a Trans-Am car because that was the way to go fast in that car. Use that as a bandwidth example, not just a braking example.
Straight-line braking is mentally simpler. Brake, release, turn. Trail braking asks your brain to manage a moving exchange: as steering increases, brake pressure must decrease. If you keep too much brake while adding too much steering, the tire demand stacks up. If you release too quickly, you may lose the rotation and support you needed on entry. The technique is faster when you can process the exchange. It is messier when your brain is behind it.
So you do not learn trail braking by simply charging deeper and hoping your foot figures it out. You reduce task load. Pick one or two corners where the technique is appropriate and where you have enough runoff, visibility, and comfort under your event rules. Keep the same initial brake point for several laps. Work only on the release shape and steering build. Ask whether the car rotates more naturally, whether steering demand decreases, and whether you can still remember the sequence afterward. If those answers are no, the task is beyond your current bandwidth at that speed.
As the programming improves, the same technique costs less attention. That is the point. You are not trying to consciously calculate brake pressure forever. You are building a program that lets you sense and shape the entry with less mental strain.
Worked example: the high-moment production car
A production-based track car often carries more mass away from the center than an open-wheel car, so it can have a higher moment of inertia and respond more slowly to initial direction change. The bandwidth mistake is to wait for the car to rotate, realize it is late, then add a sharper steering input. Now the driver has created both a timing problem and a tire-demand problem.
The inside-bandwidth solution is to plan for the car you are driving. Begin turn-in slightly earlier and make the steering more progressive. That does not mean turning lazily or parking the car at entry. It means you give the car the time and input shape it needs to respond. Your brain is ahead of the car instead of surprised by its delay.
The calibration is the apex and exit. If the earlier, more progressive turn-in lets the car tuck toward apex without over-slowing, and then release toward track-out with less steering, you are processing the car correctly. If you still arrive late and need extra wheel near apex, you probably waited for proof before acting. In a slower-responding car, waiting for proof can consume the entire corner.
Drill: the three-session bandwidth ladder
Run this over one event day or over three consecutive sessions when conditions are stable. The count is three sessions, with one primary job per session. Do not combine the jobs until the third session is complete.
Session one is the visual-input session. Your pace target is comfortable enough that you can see details. For every major corner, identify at least one approach reference, one surface or curb detail, and one exit-opening cue. The success criterion is not lap time. It is whether you can draw or annotate those cues after the session without guessing.
Session two is the tactile-input session. Keep pace similar. Focus on what the car tells you through steering response, brake pedal feel, vibration, bumps, and how the car rotates. Your success criterion is whether you can name where the car felt settled, where it felt late, and where your input shape changed the response.
Session three is the output-quality session. Now choose two corners and improve one output: smoother brake release, more progressive steering, cleaner throttle as the wheel unwinds, or fuller planned track use at exit. Your success criterion is that the chosen output improves without losing the visual and tactile map from the first two sessions. If your recall collapses, you added too much demand.
After each session, download on a track map. After the third, run a short mental imagery lap using the references and sensations you collected. The drill works because it follows the same order as good learning: improve input, build the map, then ask for better output.
Common mistakes
Mistake one: adding speed to confusion. This is the classic intermediate error. A corner feels vague, so you try to solve it by going faster and hoping commitment will create clarity. Sometimes commitment is needed, but confusion is not commitment. Good looks like backing the speed down just enough to identify the missing cue, then rebuilding pace with the cue loaded.
Mistake two: collecting cues with no job. You notice everything and use nothing. The track feels rich but your driving does not change. Good looks like connecting each cue to an action: brake here, release by here, begin steering here, expect rotation here, open the wheel here, full throttle here.
Mistake three: blaming the car before auditing the input. Too much steering angle for the amount of braking or acceleration can create understeer or oversteer. Good looks like checking your technique before declaring a handling problem. Ask whether you asked one end of the car to do more than the tires could support.
Mistake four: perfect-line driving below the limit. You put the car on the textbook path but never ask the tires to work. Bentley's track-learning guidance makes the point that a car driven at its limit, even off line, can be faster than a perfect line driven below the limit. Good looks like using the line as a tool for loading the tires and maximizing exit, not as a drawing exercise.
Mistake five: using all the track accidentally. The car runs to the edge because you are out of steering and options. That is not the same as planned track use. Good looks like outside tires reaching the exit edge because entry speed, rotation, and throttle timing made that the natural end of the corner.
Mistake six: skipping the download. You drive, park, talk, snack, and forget. Then the next session starts from a vague memory. Good looks like immediate notes on the track map while the lap is still alive in your head. That is how a session becomes programming rather than entertainment.
Mistake seven: ignoring state. You use your best morning pace as the standard when you are tired, frustrated, hot, or anxious. Good looks like adjusting the bandwidth budget to the state you actually have. If input quality is degraded, reduce speed or task load until output quality returns.
Calibration cues
You are improving when the lap feels calmer at the same speed. Calm does not mean slow. It means the car is no longer surprising your brain. You know what job is coming next. You can sense speed before the corner forces the issue. You release the brake because it is time, not because you panic. You build steering progressively and need less total wheel. You can unwind earlier and add throttle with less conflict.
You are improving when recall improves. After the session, you can mark the track map accurately. You know where you began braking, where you ended braking, where full throttle returned, and what reference points mattered. You remember surface details and car feel, not only lap drama. That recall is evidence that your brain had enough spare capacity to record useful information.
You are improving when the car uses more of the track by design. On exit, the outside tires approach the edge because the corner was solved, not because the car escaped. On entry, the car comes toward apex without an extra steering stab. In a production car that reacts more slowly, you notice that an earlier, progressive turn-in reduces the need to over-slow.
You are improving when a new technique costs less attention over time. Trail braking, progressive steering, or a cleaner throttle unwind may feel mentally expensive at first. With focused practice and imagery, the program strengthens. Eventually, the task moves closer to automatic, leaving more attention available for traffic, surface changes, and racecraft.
You are not improving if higher speed always erases recall, makes inputs abrupt, or leaves you unable to explain what changed. That is not brave learning. That is driving outside the brain's current budget.
When to back up one step
Back up when you miss the same reference repeatedly and cannot say why. Back up when the car starts to feel like it has a handling problem only in the corner where you are busiest. Back up when you add steering late, pinch the car at exit, or abandon the planned throttle because you are still solving entry. Back up when fatigue or anxiety lowers input quality. Back up when a new technique turns the whole lap into a blur.
Backing up does not always mean driving slowly. It may mean keeping speed but narrowing the task. It may mean holding the brake point constant while changing only release. It may mean using a visual-input session after lunch before chasing lap time again. The correction should match the overload. If speed is the problem, reduce speed. If task load is the problem, reduce tasks. If sensory input is the problem, run a session dedicated to seeing and feeling more clearly.
Cross-references in this module
Use this lesson as the operating rule for the rest of the perceptual-map module. Recognize overload before you add speed helps you notice when you have already exceeded capacity. Filter for cues that change the drive helps you decide which sensory details deserve attention. Keep only the next useful cues loaded helps manage working attention once the map is richer. Convert laps into patterns you can reuse builds the programming that reduces future bandwidth cost. Find the cues you habitually miss and Audit the cues you habitually miss are the repair tools when your map has blind spots.
This lesson sits before and underneath those skills. It tells you when to add demand and when to simplify. The best intermediate drivers are not the ones who think about the most things. They are the ones who arrange the lap so the right things are available at the right time, with enough brain left to drive the car.
Takeaway
Drive only as fast as your current input quality, mental programming, and task load can support. Then improve those three things deliberately. Build the perceptual map. Download the lap. Use mental imagery. Sharpen what you see and feel. Practice the right inputs until they become reliable programs. Add speed only when the output stays clean.
That is how you raise the bandwidth limit instead of merely crashing into it.
Worked example: the unfamiliar-track first session
The lesson adds an unfamiliar-track example because the corpus supports track learning through visual discovery, post-session map notes, and mental imagery. The driver holds pace low enough to notice new surface, curb, reference, and exit information, then downloads the session immediately so the next session costs less mental bandwidth.
Worked example: the Trans-Am trail-braking lesson
The lesson uses Bentley's progression from straight-line braking to trail braking, including the Trans-Am example, to show that a faster technique can exceed a driver's processing capacity before it becomes programmed. The practice task is narrowed to one or two corners, with stable brake points and attention on release shape, steering build, and recall.
Worked example: the high-moment production car
The lesson includes a production-car example from the moment-of-inertia material. A slower-responding car can punish a driver who waits too long and then adds abrupt steering, so the bandwidth-aware solution is a slightly earlier, more progressive turn-in that lets the car respond without over-slowing.
Drill: the three-session bandwidth ladder
The drill is a three-session progression: visual input, tactile input, then output quality. Each session has one primary job and a success criterion based on recall, feel, and clean execution rather than lap time. The drill ends with a track-map download and mental imagery lap.
Common mistakes
The lesson names seven errors: adding speed to confusion, collecting cues with no job, blaming the car before auditing input, perfect-line driving below the limit, using all the track accidentally, skipping the download, and ignoring state. Each mistake is paired with what good looks like so the driver has a correction, not just a warning.
Calibration cues
The lesson defines improvement through calmer laps at the same speed, better post-session recall, more planned track use, less steering demand, cleaner brake-release and throttle timing, and techniques that cost less attention as practice turns them into programming.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | Ultimate Speed Secrets - Ross Bentley | a15bb1d9-0888-2ec1-8aff-8b8234ef2f48 | 277 | 1 | uio_books_raw_v1 |
| 2 | Inner Speed Secrets - Ross Bentley | 2cb62c7b-2fca-9336-102c-2ec226d93f7d | 78 | 1 | uio_books_raw_v1 |
| 3 | Inner Speed Secrets - Ross Bentley | 7f788f5a-9a30-fc71-3220-8bdc3e9c1171 | 75 | 1 | uio_books_raw_v1 |
| 4 | Ultimate Speed Secrets - Ross Bentley | a9a648d9-5c51-dce8-aed0-7835e25db48e | 211 | 1 | uio_books_raw_v1 |
| 5 | Inner Speed Secrets - Ross Bentley | ac79dd94-d916-3f8f-3176-97849b421fe0 | 145 | 1 | uio_books_raw_v1 |
| 6 | Ultimate Speed Secrets - Ross Bentley | da4318b3-e49b-f6b8-133a-236b8f480ea6 | 318 | 1 | uio_books_raw_v1 |
| 7 | Inner Speed Secrets - Ross Bentley | 42cd9797-25c1-9bbb-d1f4-7aa50b893094 | 189 | 1 | uio_books_raw_v1 |
| 8 | Ultimate Speed Secrets - Ross Bentley | 8a59dd5c-bd92-7571-3b97-879bd28ffbf5 | 109 | 1 | uio_books_raw_v1 |
| 9 | Ultimate Speed Secrets - Ross Bentley | 47f6de8d-9d56-5b6d-547a-f1e7bb92faaf | 152 | 1 | uio_books_raw_v1 |
| 10 | Ultimate Speed Secrets - Ross Bentley | 536ffcb0-b4fd-90e0-b1a6-b29d29b9de0f | 217 | 1 | uio_books_raw_v1 |
| 11 | Ultimate Speed Secrets - Ross Bentley | ee4ddb39-cb81-0fa5-5322-b5aefed1e642 | 276 | 1 | uio_books_raw_v1 |
| 12 | Inner Speed Secrets - Ross Bentley | 1f89d950-4532-a2f9-3f06-33a6a39f92d6 | 24 | 1 | uio_books_raw_v1 |
| 13 | Ultimate Speed Secrets - Ross Bentley | 0237a5bd-e2d4-724e-bc2e-ba13db924f66 | 11 | 1 | uio_books_raw_v1 |
| 14 | Ultimate Speed Secrets - Ross Bentley | c179b4ca-b1cd-bbae-16ca-d15b1ecdfc12 | 11 | 1 | uio_books_raw_v1 |
| 15 | Ultimate Speed Secrets - Ross Bentley | 4400491c-451f-86fc-590c-1fa83983aef9 | 12 | 1 | uio_books_raw_v1 |
| 16 | Performance-Driving-Illustrated-Ross-Bentley | d03d8129-9884-8385-fe77-b2af5835c3e6 | 1 | 1 | uio_books_raw_v1 |