Diagnose exit traction before you change the car
Generated from
content/lms/data-interpretation-ii-advanced/07-putting-it-together/02-case-study-exit-traction.md; edit the source file, not this page.
Source path: content/lms/data-interpretation-ii-advanced/07-putting-it-together/02-case-study-exit-traction.md
Course: Read the data your hands can't feel
Module: Run a complete analysis workflow end to end
Estimated duration: 55 minutes
Exit traction is one of the easiest problems to misdiagnose because the symptom arrives at the most emotional part of the corner. You are looking at the straight, you want to be accelerating, and the car does not give you the clean exit you expected. It feels obvious to blame the rear tires, the setup sheet, or the car's handling. Sometimes the car really is the problem. But your first job in data review is not to protect the setup theory. Your first job is to prove what happened.
The principle for this lesson is simple: diagnose the driver demand, the corner phase, and the repeatability of the symptom before changing the car. Exit traction is not just rear grip under throttle. It is the outcome of how much speed you brought to the exit, where the car was pointed, how much steering angle remained, how the brake release or shift finished, how the throttle was applied, and whether the speed trace answered that request. If you skip those questions, you can spend money and sessions tuning around a driving pattern.
This is why the data process in this lesson starts with a question, not a part. The useful data channels are the same basic channels that show up in the Data for Drivers process: throttle trace, brake pressure trace, steering, RPM, gear, segment or section time, speed, G-sum, and GPS line. Those channels do not automatically tell you the answer, but they keep you honest. They let you see whether the problem is coasting, hesitant throttle, throttle applied early and followed by a lift, long brake pressure, inconsistent pressure, steering still loaded when the pedal comes in, an exit line that uses too much track too soon, or a pattern that remains even when the driver executes cleanly.
Start by defining the exit window. For this lesson, the exit window begins when you are approaching or passing the apex and intending to unwind the steering while adding throttle. It ends when the car is clearly in the next acceleration phase. You are not diagnosing entry understeer here; that is a sibling skill. You are allowed to notice that a bad entry caused the exit problem, but you do not turn this lesson into a full entry-understeer analysis. Your target is the moment where the car should transition from cornering demand toward acceleration demand.
A clean exit has a recognizable shape. The steering trace should begin to unwind as the throttle trace builds. The speed trace should stop being merely carried speed and begin showing acceleration. The driver should not need a second lift immediately after asking for throttle. The segment time gain should appear from the exit forward, not only from charging entry faster. The GPS line should make sense with the data: if the car is still pinched, still pointed at the outside edge, or still carrying a large steering request, the throttle trace is not the only thing being tested. You are asking the tires to finish the corner and accelerate at the same time.
The core diagnostic question is: did the car refuse a reasonable throttle request, or did the driver make an unreasonable request for the phase of the corner? That question is the difference between tuning and chasing. A reasonable request is made when the car is pointed enough, steering is coming out, the brake event is finished or clearly releasing, the shift is not upsetting the platform, and the throttle application is consistent with the available cornering load. An unreasonable request is not a character flaw. It is simply a mismatch between what the tires were still doing and what the driver asked them to do next.
Use a three-pass review. The first pass is the shape pass. Look at the exit from a distance and ask what changed first. Did throttle come in and speed increase cleanly? Did throttle come in, then lift? Did the driver coast after the apex? Did the brake pressure have a long tail that delayed the exit? Did steering stay high after the pedal came in? Did the gear or RPM trace show a shift or release event placed inside the exit window? Do not decide yet. Just name the shape.
The second pass is the comparison pass. Compare the lap to your own best clean lap, a faster rolling lap, a theoretical best reference, or another driver if you have one. The point is not to shame one lap with another. The point is to avoid diagnosing from a single squiggle. If one lap exits poorly because you were offline in traffic, that is not a setup finding. If every clean lap shows the same throttle-on-lift pattern at the same exit, and the steering, speed, gear, and line tell the same story, now you have something worth investigating.
The third pass is the why pass. Data for Drivers makes the overall process plain: look for incongruencies, dig for details, use other channels to check, ask why, compare when you can, calibrate to your driving, imagine the ideal, and set objectives for the next session. Exit traction diagnosis lives exactly there. You are not looking for a magic trace. You are looking for a mismatch between what the driver thought happened and what the channels show.
The most common first diagnosis is not lack of rear traction. It is an exit built on too much remaining cornering demand. Going Faster frames corner speed and exit speed as fundamental, and the supplied chunks tie the lesson to car control for exit speed, turn-in timing, late apex symptoms, and throttle influence on understeer or oversteer. That matters because a car that is not pointed cannot use throttle like a car that is already unwinding. If the throttle trace rises while steering remains high and the speed trace does not build, the first question is whether the line and timing left the car any room to accelerate.
This is also where early throttle can fool you. Early throttle that stays in and improves speed is one thing. Early throttle followed by a lift is different. The Data for Drivers throttle checklist calls out coasting, hesitant application, early application leading to lift, and lifts in fast corners. For exit traction, early application leading to lift is a key pattern. It may feel like you were brave with throttle and the car had no traction. The trace may show that you asked early, discovered the request was too much for the corner phase, and had to take the request back. That is not yet a car change. It is a calibration problem.
Coasting is the opposite-looking but related error. If you wait after the apex with little or no throttle, the exit may feel traction-limited because the car never gets into a committed acceleration phase. You might then add more pedal later, in a shorter window, and make the rear feel busier than it needed to be. The trace can expose this because the throttle line has a gap where the car should already be taking a measured request. The fix is not automatically to mash the pedal earlier. The fix is to build a throttle request that matches steering unwind and line position.
Brake pressure matters too. A long brake tail into the exit window can keep the car from accepting throttle cleanly. The Data for Drivers brake process points you to the shape of the pressure trace, the initial application, the trail, the long tail, inconsistent pressure, and light-long versus hard-short braking. You are not doing an entry-understeer lesson, but you cannot ignore a brake trace that is still shaping the platform when you claim the problem is exit traction. If the brake event never really ended before the throttle event began, your exit problem may be a transition problem.
Shifting can create a false exit-traction story. The supplied Going Faster shifting chunk shows the sequence around deceleration, clutch, gear lever movement, clutch release, turn-in, and relaxed brake pressure. For exit diagnosis, the point is not to teach every shift technique. The point is to include RPM and gear in the review before blaming the car. If the exit trace changes at the same time as a shift, clutch release, or gear-selection event, you need to know that. A car that hesitates because the driver is busy finishing the shift is not the same problem as a car that cannot accept throttle after the shift is complete.
Steering is the channel that keeps exit-traction analysis honest. A throttle trace by itself can make a driver look timid or aggressive. Add steering and you see whether the car was still being asked to corner hard. Add speed and you see whether the car answered. Add GPS line and you see whether the car was placed where the exit could work. Add G-sum and you get another view of how loaded the car was. The Van Valkenburgh chunk describes a simple MoTeC screen with lateral g, steering, speed, and throttle in a 100-mph turn, with class annotations noting understeer, front tires overused, and throttle on. That is a perfect caution for this lesson. A driver might report an exit problem under throttle, but the data can reveal that the front tires were already overused when the throttle arrived. Changing the rear of the car first would be a weak diagnosis.
There are driver-side and car-side versions of the same symptom. The driver-side version is inconsistent. One lap has coasting, the next has early throttle and lift, the next has a late shift, and the next has a different line. The car may still need work, but the evidence is noisy because the driver is changing the test every lap. The car-side version is repeatable after the driver pattern stabilizes. The same exit, same driver request, same line family, same gear, same brake-release shape, and the same refusal to accelerate. That is when a setup conversation becomes more credible.
This is where Lopez's becoming-a-racer guidance matters. The supplied chunk says that at the start of a racing career, the driver can suddenly find one or two percent of lap time, and that the driver must be as perceptive and critical of personal performance as of the car's handling. The car could have a problem, but it might be the driver. For this lesson, that is not a motivational poster. It is a diagnostic standard. Before you alter the car, check whether the driver is repeatable enough for the data to mean what you think it means.
A more experienced driver can sometimes settle the car-versus-driver question. The same chunk recommends using a more experienced and accomplished driver in the same class on a test day as one way to settle whether the problem is the car or you. That is not always available at an HPDE or club weekend, but the idea scales down. Use a coach, an instructor, a reference lap, or your own cleanest repeatable lap. The point is to create a comparison that tests the hypothesis instead of defending it.
Once you have a diagnosis, convert it into one next-session objective. Do not leave the trailer with six changes in your head. If the pattern is coasting, the objective might be to begin a small, continuous throttle build as steering starts to unwind, then verify that no second lift appears. If the pattern is early throttle then lift, the objective might be to delay the first real throttle request until the car is better pointed and then make one cleaner build. If steering is still high at throttle pickup, the objective might be to adjust turn-in or apex timing so the exit starts with more room. If brake pressure has a long tail, the objective might be to clean up the brake release before judging throttle. If gear or RPM points to a shift issue, the objective might be to complete the shift sequence earlier and keep the exit window simpler.
Success is not proved by one faster lap. It is proved by a cleaner relationship between channels. You want less hesitation or fewer lifts in the throttle trace, a speed trace that begins accelerating earlier or more smoothly in the intended window, steering that unwinds with the throttle rather than fighting it, and a segment gain that appears where the exit matters. If the lap time improves but the trace shows a bigger entry risk and the same exit problem, you did not fix exit traction. You found time somewhere else.
The sensory cues should match the trace. A good exit usually feels like the car accepted the request. You are not a passenger waiting to see what happens. You begin to unwind, you ask for power, and the car builds speed without needing a correction that resets the whole phase. A poor exit diagnosis often feels rushed or late. You are pointed less well than you hoped, still waiting on the car, still holding steering, or taking back a throttle request you made too soon. The lesson is to connect those feelings to the channels, not to replace one with the other.
There is a narrow setup doorway at the end of the process. You change the car only after the data shows that the driver request is reasonable, repeatable, and still not being accepted. If the trace shows clean throttle build, proper steering unwind, stable brake release, no obvious shift disturbance, and repeated poor acceleration from the same exit across clean laps, now you have earned a car-side question. That question might involve traction basics, balance, gearing, or another car-side area, but this bonded corpus does not give enough detail to prescribe those changes. The lesson stops at the diagnostic handoff: prove it is not simply your corner phase before you ask the car to be different.
Keep the scope clean. This module already has sibling lessons on diagnosing entry understeer. If your exit analysis keeps pointing back to entry, cross-reference those skills and work there. If your exit analysis points to throttle trace shape, steering unwind, gear/RPM, brake tail, or comparison quality, stay in this lesson. Exit traction diagnosis is the discipline of not treating every poor exit as the same problem.
Worked example: the MoTeC 100-mph turn
In the Van Valkenburgh chunk, the example data screen is deliberately simple: lateral g, steering, speed, and throttle in a 100-mph turn, with seminar annotations calling out understeer, front tires overused, and throttle on. Treat that as your model for a disciplined exit-traction review.
Imagine the driver comes in saying the car would not put power down on exit. If you look only at throttle, you may see the pedal coming in and conclude that the rear of the car lacked traction. But add steering and lateral g. If the steering trace is still high and the lateral load is still strong, the car is not yet in a clean acceleration phase. Add speed. If speed does not respond when throttle arrives, the trace does not automatically prove a rear problem. It proves that the throttle request did not create acceleration in that corner state.
The annotation that the front tires were overused changes the diagnosis. The driver may have been asking for power while the car was still understeering. That can feel like an exit problem because the symptom appears under throttle, but the mechanism is that the car is not pointed and the front axle is already saturated. A rear setup change could hide or move the symptom, but the first driver objective is cleaner: get the car turned enough before the real throttle request, or reduce the steering demand by improving line and timing.
A good next-session test is one controlled change. On that same turn, drive three clean laps where you deliberately wait for steering unwind before the main throttle build, then compare the same four channels. You are looking for the throttle to rise with less remaining steering, the speed trace to answer sooner or more smoothly, and the need for a second lift to disappear. If that happens, you diagnosed a corner-phase problem, not a car that needed immediate adjustment. If it does not happen and the driver request is now clean and repeatable, you have stronger evidence for a car-side conversation.
Worked example: the Formula Dodge 110-to-35 mph corner
The Going Faster braking-and-entering chunk describes a racecar approaching a 35 mph corner at 110 mph in a Formula Dodge context. That is exactly the kind of corner where drivers create exit-traction stories before the exit has even begun. There is a large speed change, a braking event, a turn-in event, and often a downshift sequence. If the exit is poor, you must inspect the whole transition before blaming the car.
Start with the brake pressure trace. If the brake pressure has a long tail that continues deep into the point where throttle should begin, the driver may still be finishing the entry while expecting an exit. Then add gear and RPM. If the shift sequence or clutch release is happening close to turn-in or throttle pickup, the car may be unsettled or the driver may be late getting back to the work of unwinding and accelerating. The shifting chunk's illustrated sequence connects clutch release, turn-in, and relaxing brake pressure, which is enough to justify checking whether your exit window is being crowded by unfinished inputs.
Now inspect throttle. If the driver coasts after the apex, the exit may be late, not traction-limited. If the driver stabs early and lifts, the throttle request may be ahead of the car. If the driver waits, then adds too much in a short distance, the car may feel worse than it would have with an earlier, smaller, continuous build. All three can produce the same complaint in the paddock: poor exit drive.
The next-session objective should match the trace. For the long-brake-tail version, clean up the release and simplify the transition before asking for more exit throttle. For the shift-crowded version, make the shift timing repeatable and keep the exit window free of late housekeeping. For the early-throttle-lift version, delay the first serious throttle request until steering is coming out, then keep the build continuous. You are not trying three fixes at once. You are proving which part of the transition was stealing the exit.
Drill: three-session exit-traction diagnosis loop
Run this drill at your next event on one or two exits only. Choose corners where exit speed matters and where traffic will not make every lap unusable. Do not change the car during the drill unless there is a safety or reliability reason.
Session 1 is the evidence session. Drive normally, but after the session mark the laps that were clean, traffic-free, and representative. In the data, isolate each chosen exit and review throttle, brake pressure, steering, speed, RPM, gear, G-sum if available, and GPS line if available. Name the pattern in plain language: coasting, hesitant throttle, early throttle then lift, steering still high at throttle pickup, brake tail crowding the exit, shift event crowding the exit, or repeatable refusal despite clean inputs. Pick one pattern only.
Session 2 is the single-objective session. If the pattern was coasting, your objective is a small continuous throttle build as steering begins to unwind. If the pattern was early throttle followed by lift, your objective is a slightly later but cleaner pickup with no second lift. If steering remained high, your objective is a line or timing adjustment that leaves more unwind available at throttle pickup. If brake pressure crowded the exit, your objective is a cleaner release before judging power. If gear or RPM pointed to a shift problem, your objective is repeatable shift timing that does not occupy the exit window.
Between Session 2 and Session 3, compare the same exit windows. The success criterion is not just a faster lap. You need at least three clean laps where the targeted trace improves and the exit segment does not get worse. The strongest result is a throttle trace with less hesitation or fewer second lifts, steering that unwinds with the throttle, and a speed trace that responds in the intended exit window. Session 3 repeats the same objective to see whether the pattern holds. If it only works once, it is not yet a diagnosis. If it repeats, you have a driver-side fix or a stronger basis for changing the car.
Common mistakes
The first mistake is naming the symptom as the cause. Poor exit acceleration is the symptom. Lack of rear traction is only one possible cause. Good analysis starts by asking what the throttle, steering, speed, brake, RPM, gear, and line say together.
The second mistake is treating early throttle as automatically better. If early throttle is followed by a lift, the trace is telling you that the first request did not fit the corner state. Good work is not merely earlier pedal. Good work is a throttle build the car can keep.
The third mistake is ignoring steering angle. A driver can be on throttle and still be asking the tires to finish too much cornering. Good exit diagnosis checks whether steering is unwinding as throttle rises. If steering remains high, first examine line, turn-in, apex timing, and patience before tuning the car.
The fourth mistake is judging from lap time alone. A faster lap can hide the same exit error if the driver gained time on entry or in another corner. Good analysis uses segment or section timing and then checks the channels inside the exact exit window.
The fifth mistake is changing the car while the driver test is inconsistent. If every lap uses a different line, throttle timing, brake release, or shift timing, the car is being asked a different question every time. Good diagnosis stabilizes the driver pattern first.
The sixth mistake is forgetting the shift. RPM and gear are part of the exit story because a late or crowded shift can look like poor drive. Good analysis checks whether the exit problem begins at the same time as a gear or clutch event before calling it traction.
Failure modes and recoveries
Failure mode one is the throttle-on-lift pattern. It feels like commitment, then uncertainty. In data, throttle rises and then drops before the exit phase is complete. The cost is speed and confidence because the car gets two separate requests instead of one clean build. Recover by moving the first real throttle request to the point where steering can come out, then build once and verify that the second lift disappears.
Failure mode two is the long wait. It feels safe but slow. In data, the throttle trace stays low or flat after the apex while speed fails to build. The cost is that you give away exit distance, then may over-ask the rear tires later. Recover by adding a small, earlier, continuous build tied to steering unwind rather than a late larger request.
Failure mode three is the still-steering throttle request. It feels like the car will not drive off the corner. In data, steering remains high when throttle rises, and speed does not answer cleanly. The cost is combined demand: the car is still busy turning when you ask it to accelerate. Recover by changing the line or timing so the car is more pointed before the throttle build, then confirm with steering and speed traces.
Failure mode four is the transition pile-up. Brake release, shift completion, steering, and throttle all crowd the same short window. It feels rushed, and the driver may report being along for the ride. In data, brake pressure, gear or RPM movement, steering, and throttle all overlap messily near the exit. Recover by simplifying the sequence. Finish the necessary entry work earlier or more repeatably before making a setup judgment.
Failure mode five is the false car problem. It feels repeatable because the same corner is always bad, but the traces show a driver pattern causing it every time. The cost is setup churn. Recover by treating the driver pattern as the test item for the next session. Only reopen the car-side diagnosis after the trace shows a reasonable, repeatable request that the car still will not accept.
Cross-references
If the exit problem begins before the apex and the data shows the car already refusing to rotate or still carrying too much front-tire load, cross-reference the module's entry-understeer lessons. Do not force that problem into an exit-traction box.
If the exit problem is mainly a data-method problem, cross-reference the metric-driven analysis skill. This lesson assumes you can isolate a corner, compare laps, and use segment or section timing. If those foundations are weak, the exit-traction diagnosis will become guesswork.
If the exit problem repeatedly points to driver inconsistency, cross-reference car-control and throttle-brake transition work. The Going Faster chunks connect exit speed, car control, braking and entering, throttle-brake transition, and shifting. The common thread is that the car responds to the sequence, not to one isolated input.
If the exit problem remains after clean, repeatable driver evidence, that is the handoff point to setup and engineering. This bonded corpus supports the decision to look inward before blaming the car, but it does not provide enough detail to prescribe specific setup changes from an exit trace alone.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | Data for Drivers | cabda699642b26311b0a7ef998da2c71 | 15 | 1 | uio_books_raw_v1 |
| 2 | Going Faster Mastering the Art of Race Driving - Carl Lopez | ef9ea5d6-92b2-e60a-d6d0-5adac150482c | 234 | 1 | uio_books_raw_v1 |
| 3 | Race Car Engineering Mechanics Paul Van Valkenburgh | f721fe85-812c-0bdc-d9b3-212cd51c14f7 | 149 | 1 | uio_books_raw_v1 |
| 4 | Going Faster Mastering the Art of Race Driving - Carl Lopez | 06787811-3605-ee7a-2388-a0d1655d9ace | 27 | 1 | uio_books_raw_v1 |
| 5 | Going Faster Mastering the Art of Race Driving - Carl Lopez | 0778700e-6af6-3eac-c148-83f21b0501b4 | 44 | 1 | uio_books_raw_v1 |
| 6 | Going Faster Mastering the Art of Race Driving - Carl Lopez | b2c44205-8e7a-2622-d998-a8b843b3229a | 92 | 1 | uio_books_raw_v1 |
| 7 | Going Faster Mastering the Art of Race Driving - Carl Lopez | c064268a-5a02-48d2-2ad4-15b4bb05a6dc | 114 | 1 | uio_books_raw_v1 |
| 8 | Going Faster Mastering the Art of Race Driving - Carl Lopez | b25a5abe-55f5-bfe9-c7d7-d89151314400 | 47 | 1 | uio_books_raw_v1 |
| 9 | Going Faster Mastering the Art of Race Driving - Carl Lopez | f2410e4f-42d0-24db-af78-3d9940ff312d | 75 | 1 | uio_books_raw_v1 |
| 10 | Going Faster Mastering the Art of Race Driving - Carl Lopez | 915e3934-2e52-4c3f-9d6c-3d96e7adf2d9 | 51 | 1 | uio_books_raw_v1 |
| 11 | Going Faster Mastering the Art of Race Driving - Carl Lopez | fa01ec16-aace-9079-2afa-de127b8272a9 | 300 | 1 | uio_books_raw_v1 |
| 12 | Data-for-Drivers-PRINT | b80dc634-a0a7-d6de-d470-353aed47e2a6 | 17 | 1 | uio_books_raw_v1 |