Translate high-speed feedback into testable aero questions
Generated from
content/lms/race-aerodynamics/07-turn-findings-into-a-tuning-plan/01-translate-high-speed-feedback-into-hypotheses.md; edit the source file, not this page.
Source path: content/lms/race-aerodynamics/07-turn-findings-into-a-tuning-plan/01-translate-high-speed-feedback-into-hypotheses.md
Course: Engineer downforce you can actually use
Module: Turn findings into a tuning plan
Estimated duration: 55 minutes
What you are learning
This lesson is about the moment after a high-speed run when the driver comes in with feedback and the team has to decide what to do with it. The wrong move is to treat the first sentence from the cockpit as a setup answer. The better move is to translate that feedback into a question that can be tested with the tools you actually have: a speed or rpm trace, split times, braking deceleration, lap time, visual evidence from airflow, and a disciplined comparison between runs.
You are not trying to become a full aerodynamicist in one lesson. You are learning the working skill that lets a driver, mechanic, engineer, or data person move from impression to investigation. The bonded corpus gives that skill a very practical shape. McBeath points out that even a simple trace of rpm or speed versus time can tell you corner speeds, straight speeds, elapsed time, split times, and braking deceleration. That means your high-speed feedback can be turned into evidence if you phrase it correctly. The same source also warns that aero development is difficult to generalise, because what works on one car may not work on another. Trial and error are not an embarrassment in this subject. They are part of the method.
The rule of the skill is simple: never let a high-speed feeling become a conclusion until it has become a testable question. A feeling tells you where to look. A question tells you what evidence would change your mind.
The principle: feedback is an observation, not a diagnosis
At speed, the car can give you strong sensations. It may feel planted, nervous, reluctant to rotate, unusually draggy, better in one direction than the other, or different after a bodywork adjustment. Those sensations matter, but they do not name the cause by themselves. A driver can accurately report that a car lost high-speed confidence, yet be wrong about whether the cause is aero balance, drag, a braking issue, a mechanical setup issue, a ride-height effect, a driver adaptation, or traffic and wind conditions. This lesson stays inside the aero lane, but it does not assume every high-speed complaint is automatically an aero problem.
The principle is to move through four stages. First, capture the observation as precisely as possible. Second, turn it into an aerodynamic hypothesis. Third, state what the data or airflow evidence should look like if that hypothesis is true. Fourth, decide what action you will take after the test, including the possibility that the hypothesis was wrong.
That order matters. If you jump from observation to adjustment, you usually create confusion. If the car feels slower after adding downforce, you may be tempted to remove the change. But McBeath describes the exact trade you have to inspect: increasing downforce can raise corner speed while creating a related drop in straight-line speed, and the overall elapsed time decides whether the result is a net gain or loss. The testable question is not simply whether the car feels better. The question is whether the corner-speed benefit outweighs the straight-speed cost on the part of the lap that matters.
This is why high-speed aero feedback must be phrased around measurable signatures. The car may feel secure in a fast corner, but the useful question is whether the minimum speed, exit speed, or segment time improved. The car may feel lazy on the straight, but the useful question is whether the straight speed or acceleration trace degraded after the aero configuration changed. The car may feel unstable under braking from high speed, but the useful question is whether the braking deceleration trace changed in the same zone under comparable conditions.
The mechanism: how aero questions show up in evidence
The bonded aero material gives you three main evidence families. The first is performance data from speed or rpm over time. Even without an expensive system, you can extract corner speeds, straight speeds, elapsed run time, split times, and braking deceleration. That is enough to ask whether a high-speed complaint has a measurable performance signature.
The second family is visual airflow evidence. McBeath emphasises the value of seeing what the air is doing around critical areas such as wings, spoilers, diffusers, cooling intakes, and outlets. Flow visualisation does not magically tell you the setup answer, but it gives you pointers. If the air is doing something unexpected around a wing, diffuser, intake, or outlet, you have a better place to aim the next test.
The third family is external modelling or controlled testing. The professionals use CFD to model many configurations and wind tunnels to validate solutions. For most club racers, those tools may be out of reach, but the lesson is still useful: modelling, tunnel work, track testing, and simple data analysis all need the same discipline. A tool only helps if you use it carefully and with common sense. A simple tool used clearly can answer a better question than a sophisticated tool used casually.
This is the important intermediate-driver step. You do not need to own the most expensive tool to ask a better aero question. You need to know which observable outcome would support or weaken the hypothesis. If the hypothesis is more useful downforce in a high-speed corner, look for corner-speed or segment-time gain and then check the straight-speed cost. If the hypothesis is excessive drag, look at straight speed and the time taken to cover the straight, while checking that you are not giving away critical corner speed. If the hypothesis is disturbed airflow around a device, use visualisation as a pointer and then confirm with performance data. If the hypothesis involves braking stability from high speed, check the braking deceleration rate and the repeatability of the speed trace in that zone.
The translation template
Use this template whenever you come in from a run with high-speed feedback.
First, name the exact moment. Do not say the car was bad at high speed. Say which phase of the lap produced the feedback: entry, mid-corner, exit, the fastest part of the straight, the braking zone after the straight, or the transition from straight to corner. The available data described by McBeath is time-based and speed-based, so your feedback needs an anchor in time, speed, gear, or track section. The more exact the moment, the easier it is to compare traces later.
Second, separate sensation from diagnosis. The sensation is what you felt. The diagnosis is what you think caused it. Keep them separate until the test is done. A sensation might be that the car would not carry the expected speed through a fast bend. A diagnosis might be that the rear wing is not working. The first statement belongs in the feedback. The second belongs only as a hypothesis.
Third, choose the performance measure. Ask which number should move if the hypothesis is true. The bonded material gives you several choices: corner speed, straight speed, elapsed time, split time, and braking deceleration. You do not need all of them for every question. You need the one or two that would make the hypothesis falsifiable. A vague question asks whether the car is better. A useful question asks whether the same section is faster, whether the straight speed has fallen, or whether braking deceleration is different.
Fourth, predict the trade. Aero changes rarely give only one effect. Downforce and drag are often tied together in the evidence. McBeath gives the common example clearly: added downforce may improve corner speed while lowering straight-line speed, and the net gain or loss has to be judged against elapsed time. When you form the question, include the expected benefit and the expected cost. That keeps you from celebrating one number while ignoring the number that paid for it.
Fifth, choose the comparison. Track testing can produce serious aero data only with discipline. The practical phrase from the corpus is that other things need to be equal for the comparison to mean much. That means you should compare similar laps, similar run conditions, similar fuel and tyre states when possible, and the same driver intent. You are not trying to create a laboratory at an amateur event, but you are trying to avoid comparing a committed lap against a traffic lap and then calling the result aero.
Sixth, decide the action threshold before you run. If the high-speed corner speed improves but the following straight loses more time, you need to know whether you will revert, keep testing, or try a smaller configuration change. If the visual evidence points to disturbed airflow but the performance data does not change, you need to know whether the next step is more visual work, a different measurement, or stopping the aero line of inquiry. A testable question has a planned next step for yes, no, and unclear.
Technique: building the question from the driver's debrief
Start the debrief by getting the raw report before anyone argues about fixes. Ask the driver where the feedback appeared, whether it repeated, whether it appeared in clean laps, and whether the driver changed line, braking, throttle, or confidence because of it. You are looking for a repeatable high-speed pattern, not a single emotional sentence after a busy session.
Then translate that report into a one-sentence question. A good one-sentence question has four parts: condition, suspected aero mechanism, predicted evidence, and decision measure. For example, after a change that should add downforce, the question might be whether the car now carries more speed through the fast corner without giving away more time on the following straight than it gains in the corner. That question is grounded because McBeath identifies both corner-speed gain and straight-line loss as measurable aero consequences, and because elapsed time is the net judge.
Do not write a question that only protects your favorite answer. A useful question is allowed to fail. If the data says the corner is no faster, or the straight loss is too large, or the braking trace did not change, the question did its job. It saved you from tuning by loyalty to a guess.
After the question, write the evidence list. Use the simplest evidence that can answer the question. If you have only speed versus time, that is still useful. You can compare the speed at the same point, the minimum speed in the corner, the speed at the end of a straight, the time between two points, and the rate of speed change under braking. If you have more serious logging, you can add channels, but the basic discipline stays the same. McBeath's practical point is not that only professionals can learn from data. It is that a disciplined approach lets track testing become a meaningful supplement or alternative to wind tunnel and CFD time.
If the question involves airflow behavior, plan the visual evidence before the run. Flow visualisation is useful because it lets you see what the air is doing around the areas where aero devices, cooling paths, and underbody features work. Use it as a pointer, not as the verdict. If the pattern around a wing, spoiler, diffuser, intake, or outlet looks suspicious, your next question should still ask whether a change produces a measurable performance effect.
Finally, write the comparison rule. Decide which laps count. Decide what you will ignore. Decide whether the session had enough clean running to compare. This is where many amateur tests fail. They gather interesting information but do not protect the comparison. The result is a pile of impressions instead of a decision.
Sub-skill 1: make the feedback time-based
The most useful aero feedback is tied to a place on the trace. The corpus says a simple rpm or speed trace can reveal corner and straight speeds, elapsed time, split times, and braking deceleration. That means you should train yourself to debrief in a way that can be matched to those data features.
Instead of saying the car was unstable at speed, say that the instability appeared after the fastest straight when you first applied brake pressure, or that it appeared from the middle of the fast corner to the exit, or that it appeared only after the latest aero change. Instead of saying the car was slow, say whether it was slow to reach the end-of-straight speed, slow through the corner, or slower over the whole section. Your language should point the data person to a segment.
This is also where an intermediate driver can add real value. You may not know whether the rear diffuser is working correctly. But you can know whether the feedback appeared at the same place on three clean laps. You can know whether you had to lift earlier than usual. You can know whether the car felt secure but the straight speed looked worse. Good aero testing starts with that kind of disciplined driver report.
Sub-skill 2: predict the signature before looking at the data
A hypothesis is weak if it only becomes specific after you have seen the trace. Before looking, write what you expect. If you think added downforce helped, you should expect a corner-speed or section-time improvement in the high-speed area. If you think the same change added too much drag, you should expect a straight-speed or straight-time penalty. If you think a braking-zone complaint is connected to high-speed aero behavior, you should expect the deceleration trace or entry-speed pattern to change in the relevant braking zone.
This does not mean the prediction will always be right. It means the test can teach you. If the prediction fails, you have learned that your first story did not fit the evidence. That is valuable because McBeath repeatedly frames aero development as a process with blind alleys, car-specific results, and trial and error. The question that fails cleanly is better than the vague opinion that survives forever.
Sub-skill 3: read net performance, not one attractive number
The most common trap in aero testing is falling in love with the number that improved. A car that gains speed through a fast corner may still be slower over the whole lap if it loses too much on the straight. A car that gains end-of-straight speed may still be worse if the driver cannot carry speed through the next fast corner. McBeath's simple speed-versus-time analysis is valuable because it lets you set one change against the whole elapsed time, not just against the most flattering point.
When you review the run, read the evidence in order. Start with the segment where the feedback occurred. Then inspect the section before and after it. Then look at the whole lap or run if the data is clean enough. This protects you from making a setup decision from a single number. The question is not whether any number got better. The question is whether the car went faster in the way the hypothesis predicted, and whether the trade was worth it.
Sub-skill 4: use flow visualisation as a pointer
When the question is about what the air is doing, visual evidence can be extremely useful. McBeath specifically calls out wings, spoilers, diffusers, cooling intakes, and outlets as areas where seeing the airflow can help understanding and give pointers for development. That is exactly how you should use it: to aim your next question.
A common intermediate mistake is to treat a flow pattern as a final answer. A pattern can tell you that an area deserves attention. It can suggest that flow is not behaving as expected. It can help you decide where to inspect, where to change, and where to test next. But the performance question still has to be answered. Did the change improve the speed trace, split time, corner speed, straight speed, braking deceleration, or elapsed time in the predicted way? If not, the visual evidence may be interesting but not yet useful.
Sub-skill 5: protect tool quality
A logger that is not installed or calibrated well can create confidence in bad numbers. One bonded chunk describes data logging work in practical terms: buying a system that suits present and future needs, installing and calibrating it to give useful results, and extracting useful information for mechanics, engineers, and drivers. That is the standard here. The value is not the gadget. The value is the useful result.
For your aero question, useful result means the data is accurate enough and repeatable enough to support the decision you are making. If the speed trace is noisy, if the lap was interrupted, if the comparison lap had traffic, or if you cannot locate the same section on both traces, say so. The disciplined answer may be that the test was inconclusive. That is not failure. It is honesty, and honesty is what keeps the next test from being built on sand.
Sub-skill 6: stay humble about car-specific results
The aero corpus is blunt about generalisation. What works on one car may not work on another, even if the cars look similar. That means your question should be about your car, your configuration, and your track condition. Do not turn one test into a universal rule. Do not assume that a device, angle, opening, or configuration will behave the same way on a different body shape or in a different operating condition.
This humility is not a reason to avoid testing. It is the reason testing matters. The professional path may involve CFD to search through configurations and wind tunnels to validate them. The amateur path may involve simple logging, flow visualisation, and careful back-to-back comparisons. Both paths depend on the same attitude: let the evidence teach you what your car did.
Calibration cues: what improvement looks like
You are improving at this skill when your debriefs get shorter and sharper. At first, you may come in with a broad feeling. With practice, you will name the phase, the speed area, the expected signature, and the comparison you need. The driver report becomes easier to test.
You are improving when your hypotheses include tradeoffs. A weak aero question asks whether more wing is better. A stronger question asks whether the extra high-speed corner speed is worth the straight-speed loss. A weak drag question asks whether the car is too draggy. A stronger question asks whether the end-of-straight speed and straight split changed after the configuration change, and whether any improvement came at the cost of corner speed.
You are improving when you can separate evidence types. Data tells you what the car did over time. Flow visualisation helps show what the air was doing around important areas. CFD and wind tunnel work can model or validate configurations when available. None of those evidence types replaces common sense. The bonded text says the prerequisite in all cases is careful use of tools with common sense. That is a useful standard for club-level testing.
You are improving when you can say inconclusive without frustration. A muddy comparison is not a result. A session with traffic, a driver mistake, or an untrustworthy logger may still teach you what to improve about the test, but it should not drive a confident aero decision. A permanent record of laps and runs is valuable because it lets you inspect more thoroughly later, but only if you protect the meaning of that record.
Worked example 1: the corner-speed gain with a straight-speed cost
Use this situation when a configuration change was intended to increase downforce and the driver reports that the car felt better in the fast corner but slower afterward. The lazy conclusion is that the change worked because the car felt planted. The equally lazy conclusion is that the change failed because the straight speed was lower. The testable question is whether the corner-speed gain was larger than the straight-line penalty when judged by elapsed time over the relevant section.
Build the question like this. In the fast corner after the change, did minimum speed, average corner speed, or section time improve compared with the baseline clean laps? On the following straight, did the end speed or straight split get worse? Across the combined corner-plus-straight segment, did elapsed time improve or degrade? This question comes directly from the bonded aero method: use speed or rpm over time to measure corner speeds, straight speeds, split times, and overall elapsed time, then compare the downforce benefit against the straight-line loss.
The good outcome is not automatically maximum corner speed. The good outcome is a net gain that matches the purpose of the car and session. If the corner-speed gain is real but the straight loss costs more time, you have learned that the configuration may be too costly for that section. If the straight-speed loss exists but the combined segment is faster, you have evidence that the trade may be worthwhile. If the data does not show the corner-speed gain the driver felt, the next question may involve confidence, line, conditions, or whether the supposed aero change actually affected the car in the speed range being tested.
Worked example 2: visualising air around a device before changing the plan
Use this situation when the feedback points to a high-speed area and the team suspects airflow around a wing, spoiler, diffuser, cooling intake, or outlet. The mistake is to start moving parts until the driver likes the sensation. The better approach is to ask what the air appears to be doing, then connect that observation to a performance question.
Begin with the exact complaint. Suppose the driver reports that the car changed character in the same high-speed section after a bodywork or aero-device change. The first question is not which adjustment will fix it. The first question is whether airflow around the relevant area gives a pointer. McBeath says that seeing the air around crucial areas can help understanding and provide pointers for improvement and development. So the test plan may include flow visualisation on the suspected area during a controlled run.
After the run, do not stop at the pattern. Translate it. If the visual evidence suggests a disturbed area near a device, the next performance question might ask whether a small configuration change improves the speed trace in the affected corner, changes the straight-speed penalty, or improves braking-zone repeatability. If the visual evidence looks uneventful but the data still shows a performance loss, the next step may be to stop blaming that airflow area and reframe the question. The visual work was useful because it narrowed the search, not because it delivered a verdict by itself.
Common mistakes
Mistake 1: naming the fix before naming the question. The driver says the car feels weak in a fast section, and the paddock immediately decides to add, remove, raise, lower, open, close, tape, or trim something. Good practice is slower. State the observation, write the hypothesis, predict the measurable signature, and then choose the test. The fix comes after the evidence.
Mistake 2: using lap time alone. Lap time matters, but it can hide the reason for the change. The bonded material specifically points to corner speeds, straight speeds, split times, braking deceleration, and elapsed time. Use those pieces. If the lap is faster, you still need to know where it came from. If the lap is slower, you still need to know whether the aero change helped one part and hurt another.
Mistake 3: chasing peak corner speed. A single improved corner number can be seductive. Good practice is to check the trade. Did the car pay for that speed on the following straight? Did the combined segment improve? Did the whole run improve? This is the specific downforce-versus-straight-speed comparison McBeath describes.
Mistake 4: believing flow visualisation without performance confirmation. Visual evidence is powerful because it lets you see what the air is doing near important devices and openings. But it provides pointers. Good practice is to connect the pointer to a performance measure before calling the change successful.
Mistake 5: trusting unprotected comparisons. If one run was clean and the other was messy, if the logger was not calibrated well enough, or if the driver used a different approach, the result may not answer the question. Good practice is to call the test inconclusive and improve the next comparison.
Mistake 6: generalising from another car. The corpus is clear that aero results are hard to generalise and that similar cars can respond differently. Good practice is to use other cars and professional tools as learning aids, not as proof that your car will respond the same way.
Mistake 7: making the question too large. If you ask whether the whole aero package is better, you may not know what to do with the answer. Ask a narrower question first. Did this change affect this high-speed corner, this straight, this braking zone, or this airflow area in the predicted way? Small questions build a tuning plan better than giant opinions.
Drill: the three-session aero question ladder
Do this drill at your next test day or practice event when you have permission and conditions to test safely. The count is three sessions. The duration is one run group or session for baseline, one for the first question, and one for confirmation or reframing. The success criterion is not that the car gets faster. The success criterion is that you finish with one clear answered question, including the evidence that supported or rejected it.
Before session 1, write one high-speed observation you want to investigate. Keep it narrow. Choose a section where you can compare speed or rpm over time. Write the data you will use: corner speed, straight speed, split time, braking deceleration, elapsed time, or flow visualisation. Then run clean baseline laps without changing the car for this question. After the session, mark the clean laps and ignore the ones with traffic or obvious driver errors.
Before session 2, turn the observation into a hypothesis. Write the expected signature. For example, if the hypothesis is useful added downforce, the expected signature may be a better fast-corner speed with a possible straight-speed cost. If the hypothesis is excessive drag, the expected signature may be worse straight speed or straight split after a configuration change. If the hypothesis is disturbed airflow near a device or opening, the expected signature may begin with visual evidence and then require a data comparison. Make only the planned test change, or if no change is being made yet, run the planned visualisation or comparison exactly as written.
After session 2, decide only from the evidence. If the signature appeared and the net result is better, record the question as supported. If the opposite appeared, record it as rejected. If the evidence is mixed, record which part was supported and which part was not. If the comparison was bad, record it as inconclusive and name why.
Use session 3 to confirm or reframe. Confirmation means repeating the supported result under comparable conditions. Reframing means writing a better question because the original did not fit the evidence. This is not wasted time. The corpus treats trial and error as essential in aero development, and it also encourages asking why and keeping the analysis simple. A cleanly rejected hypothesis is a step toward a better plan.
How this lesson fits the rest of the module
This lesson stops at translation. It teaches you how to turn high-speed feedback into questions that can survive a test. The sibling lesson on prioritising balance, load, then drag handles how to rank competing changes. The lesson on validating in racing air handles the environment where the test should be trusted. The lesson on documenting a speed and ride-height map handles the longer-term record. The lesson on deciding what is not an aero problem handles the boundary between aero, mechanical setup, driver technique, and conditions.
The reason to keep those boundaries is clarity. If every high-speed complaint becomes an aero fix, you will chase blind alleys. If every data trace becomes a full tuning plan, you will move faster than your evidence. Your job here is narrower and more useful: write the next good aero question.
A final paddock standard
At the end of a run, you should be able to say four things. Here is what the driver felt. Here is the aero hypothesis. Here is the evidence that would support it. Here is what we will do if the evidence says yes, no, or unclear. That is the difference between guessing at high speed and learning from high speed.
Worked example: corner-speed gain with straight-speed cost
A downforce-oriented change may make the car feel better in a fast corner while lowering straight-line speed. The testable question is whether the corner-speed or section-time gain is larger than the straight-speed loss when judged over the relevant segment and the whole run. Compare clean baseline laps against clean test laps, then inspect corner speed, straight speed, split time, and elapsed time before deciding whether the trade is worth keeping.
Worked example: visualising air around aero devices and openings
When the feedback points toward airflow around a wing, spoiler, diffuser, intake, or outlet, use flow visualisation as a pointer rather than a verdict. If the pattern suggests an area worth investigating, connect it to a performance question: did the next configuration improve the speed trace, segment time, straight speed, or braking-zone repeatability in the affected section?
Common mistakes
The main errors are naming the fix before the question, using lap time alone, chasing peak corner speed while ignoring straight-speed cost, treating flow visualisation as proof without performance confirmation, trusting messy comparisons, generalising from another car, and making the question too large. Good practice is to keep the question narrow, measurable, and tied to the exact high-speed phase where the feedback appeared.
Drill: three-session aero question ladder
Run one baseline session, one test session, and one confirmation or reframing session. Before each session, write the question and the expected signature. After each session, compare only clean laps and decide whether the hypothesis was supported, rejected, or inconclusive. The success criterion is one clearly answered aero question with evidence, not necessarily a faster lap.
Calibration cues
You are improving when your debriefs name the exact phase, expected data signature, likely tradeoff, and decision threshold. Good questions predict both benefit and cost, such as corner-speed gain against straight-speed penalty. Good reviews separate data evidence from airflow evidence and are willing to call a test inconclusive when the comparison is not protected.
When to stop and reframe
Stop and reframe when the data does not show the predicted signature, when visual evidence points somewhere that performance data does not support, when the logger or comparison laps are not trustworthy, or when the question has become too broad to answer. Aero development includes trial and error, so a rejected hypothesis is useful if it makes the next question cleaner.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | Competition Car Aerodynamics 3rd Edition McBeath Simon | ac2b13c4-51bb-bcb1-cbe4-e7f34da7f114 | 344 | 1 | uio_books_raw_v1 |
| 2 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 576d96a1-00b7-66dd-f5b1-e33666cc457f | 334 | 1 | uio_books_raw_v1 |
| 3 | Competition Car Aerodynamics 3rd Edition McBeath Simon | c7d0125c-8080-dbcc-df83-3b96d0b84bab | 477 | 1 | uio_books_raw_v1 |
| 4 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 6edca499-2988-7702-ccc8-3d17b516edff | 385 | 1 | uio_books_raw_v1 |
| 5 | Competition Car Aerodynamics 3rd Edition McBeath Simon | cd94958f-1042-ceff-8d99-06fa06ac633b | 504 | 1 | uio_books_raw_v1 |
| 6 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 9e3001fd-e626-5565-9b11-bc3cab151d27 | 281 | 1 | uio_books_raw_v1 |
| 7 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 61068e74-0999-1e25-03bd-8c545f352d25 | 26 | 1 | uio_books_raw_v1 |
| 8 | Ultimate Speed Secrets - Ross Bentley | 0237a5bd-e2d4-724e-bc2e-ba13db924f66 | 11 | 1 | uio_books_raw_v1 |
| 9 | Ultimate Speed Secrets - Ross Bentley | 4400491c-451f-86fc-590c-1fa83983aef9 | 12 | 1 | uio_books_raw_v1 |
| 10 | Inner Speed Secrets - Ross Bentley | 1f89d950-4532-a2f9-3f06-33a6a39f92d6 | 24 | 1 | uio_books_raw_v1 |
| 11 | Data-for-Drivers-PRINT | b80dc634-a0a7-d6de-d470-353aed47e2a6 | 17 | 1 | uio_books_raw_v1 |
| 12 | Competition Car Aerodynamics 3rd Edition McBeath Simon | 291ddd73-fa7f-e4ba-cd67-fac7413c98ca | 5 | 1 | uio_books_raw_v1 |