Read the story your feet are telling
Generated from
content/lms/data-interpretation-for-drivers/03-brake-throttle-analysis/03-combined-pedal-analysis.md; edit the source file, not this page.
Source path: content/lms/data-interpretation-for-drivers/03-brake-throttle-analysis/03-combined-pedal-analysis.md
Course: Data Interpretation for Drivers
Module: Brake & Throttle Analysis
Estimated duration: 60 minutes
This lesson is about reading brake and throttle together. The sibling lessons teach you how to inspect the brake trace by itself and the throttle trace by itself. Here, you stop treating them as separate squiggly lines. You read them as one continuous footwork story: what you did at the end of the straight, how quickly you committed to braking, how you carried or released brake into the corner, where the dead time appeared, how you began feeding throttle back in, and whether that throttle was confident enough to stay in.
The core rule is simple: the car should not spend useful track distance waiting for you. At the end of a straight, a good trace normally shows a decisive transition from throttle to brake. Near corner entry, it shows brake release shaped around the turning job. At or after the point where acceleration can begin, it shows throttle returning progressively enough that the car accepts it. The details change with corner type, but the diagnostic target stays the same: find the places where your feet create time loss, balance loss, or both.
Combined pedal analysis matters because braking and throttle are not just speed controls. Brake pressure changes the tire workload, loads the front end, and decides how much deceleration is available before and during turn-in. Throttle returns acceleration, but it also settles the chassis and supports the line as steering unwinds. The transition between the pedals is therefore a balance event, not just a foot movement. If you stare only at brake pressure, you can miss the wasted distance before braking or after release. If you stare only at throttle, you can miss whether the delayed throttle was caused by an over-slow entry, a sudden brake release, or a corner entry that left the car pointed badly.
Think of the trace as a sentence with four clauses. First, you are on throttle. Second, you leave throttle and build brake pressure. Third, you release or hold brake while the car turns. Fourth, you begin throttle again and keep it in. The quality of the sentence is in the punctuation between those clauses. A pause between throttle and brake is usually coasting. A vertical brake release can unload the front tires and make the car feel suddenly light. A long empty gap between brake release and throttle application usually means the car was not ready, you were not confident, or the line did not support acceleration. A throttle application followed by a lift says you asked for acceleration before the car, tire, or line could accept it.
Start every analysis pass with the same order. First, locate the corner and decide what phase you are studying: straight-line deceleration, brake-turn, transition to throttle, or exit. Second, place the brake and throttle traces on the same distance axis. Distance is usually more useful than time for driver work because it shows where on the track the action happened. Third, mark four points: throttle-off, brake-on, brake release complete, and throttle-on. Fourth, measure the gaps and the slopes. Fifth, compare those points against speed, steering, lateral g, longitudinal g, gear, RPM, segment time, GPS line, or whatever supporting channels you have. Finally, ask why the shape exists before deciding what to change.
The first sub-skill is finding dead air between throttle and brake. This is the easiest time loss to see because the trace shows neither meaningful acceleration nor meaningful braking. In a braking zone after a straight, dead air usually appears as throttle dropping before brake pressure rises. The driver may remember the lap as careful and tidy. The data calls it a coast. Segers gives a concrete example with two drivers entering a medium-speed corner after reaching about 225 km/h and slowing to about 110 km/h. The earlier-braking driver shows an 8 m coast between coming off throttle and going to the brakes. That is not a subtle engineering interpretation. It is track distance spent neither accelerating nor braking.
For an intermediate driver, the correction is not simply brake later. The correction is to remove the hesitation first. If your trace shows an 8 m coast before brake pressure, move your brake application earlier relative to your throttle lift until the gap disappears, then work on moving the whole combined event later only when the transition is clean. A driver who deletes the coast by braking decisively at the same reference point often gains both consistency and safety. A driver who chases later braking while keeping the hesitation may arrive at the corner with more uncertainty, not more skill.
The second sub-skill is reading how brake pressure builds. A useful braking event is normally quick and firm when the car is straight and the tires are available for deceleration. The data question is not only how late you braked. It is how quickly you created useful deceleration after you decided to brake. Segers lists quickness in building maximum deceleration, how hard the driver brakes, and braking point consistency as core braking analysis items. The combined view adds one more question: did the throttle-to-brake transition support that brake build, or did your foot spend distance in between?
You can diagnose this with the shape of the brake trace. A clean straight-line brake application rises decisively. A timid one creeps upward, often paired with an early throttle lift. A panic one may spike hard and then immediately back away because you overshot the grip or frightened yourself. A consistent driver can still choose less than maximum braking in some corners, but that choice should look planned. Lopez describes the analytical racer as someone who knows the plan: brake there, shift there, turn in at that spot, take a specific apex, apply power just so, and clip the exit. Your data should show a plan, not a negotiation.
The third sub-skill is separating straight-line braking from brake-turn. In the straight-line part, the car has no major tire demand except braking, so the tires can be used primarily for deceleration. During brake-turn, the tires must both slow the car and change direction. The brake trace should therefore stop looking like a pure maximum-deceleration event and start looking like a managed load transfer tool. The question becomes whether you are releasing the brakes in a way that matches the increasing steering and cornering demand.
This is where combined pedal analysis is more valuable than a single-channel brake review. If the brake trace trails away while steering and lateral g rise, that may be a deliberate brake-turn phase. If the brake trace falls off a cliff exactly as steering comes in, the car may lose front load abruptly. If the brake stays too high too long, the car may be overloaded at entry, forcing you to wait on throttle later. Lopez describes two broad ways to use the brakes while turning: progressively trailing away the braking load as the car decelerates while turning, or relaxing to a selected pressure and holding it briefly in longer brake-turn segments. The trace does not have one ideal shape for every corner. It has to match the corner’s direction change and the car’s balance.
The fourth sub-skill is reading the brake-to-throttle handoff. This is the centerpiece of the lesson. The end of braking should not feel like a cliff, and the beginning of throttle should not feel like a separate, delayed decision. Bentley emphasizes that the transition from braking to acceleration can affect car balance more than many drivers realize. He also says you should be able to release the brakes and begin applying throttle without feeling the transition, and the foot move should be immediate. In data terms, you are looking for a purposeful handoff: brake releases as the car can accept less front load, throttle begins as the car can accept drive, and the gap between them is as small as the corner allows.
Do not misunderstand this as a command to mash throttle the instant the brake trace hits zero. The shape depends on corner type, line, speed, steering, and car. In some corners, especially where throttle can begin around turn-in, there may be little or no trail-braking phase. In a longer brake-turn entry, you may need to hold a defined amount of brake while the car rotates, then release and begin throttle later. The diagnostic error is not that the two traces fail to follow one universal drawing. The error is when the trace shows you waiting for no reason, releasing in a way that upsets the car, or applying throttle in a way that immediately forces a lift.
The fifth sub-skill is reading throttle confidence. A throttle trace is not good because it rises early. It is good when it rises at the point the car can keep accepting it. Data for Drivers flags hesitant application, early application leading to lift, and lifts in fast corners as throttle-trace questions. A clean combined trace does not celebrate the first touch of throttle if that touch is followed by a correction. If throttle comes in, then backs out, the story is that the first application was not fully believable. The cause may be entry speed, brake release, line, steering angle, surface grip, or driver confidence. The trace tells you where to ask the question.
The sixth sub-skill is checking the pedals against steering and g-load. Pedal channels tell you what your feet did. They do not fully explain whether the car was ready for it. Add steering and lateral g to see if throttle was delayed because you were still asking for too much cornering. Add longitudinal g to see whether brake pressure created deceleration promptly or whether the car coasted. Add GPS line to see whether a late throttle point came from a late apex that worked or from a line that simply left the car pointed at the wrong place. Add segment reports, fastest rolling, theoretical fastest, and throttle histogram when you have them, but keep the question simple: what did the feet ask for, and did the rest of the car agree?
A clean combined-pedal trace has several recognizable features. The throttle stays in until the braking decision. The brake begins without a lazy coast. Brake pressure builds fast enough for the corner and car. If the car turns while braking, brake pressure is released or held deliberately rather than accidentally. The release does not suddenly unload the car at the same moment steering demand appears. The throttle returns when the car can accept it. The throttle then keeps building or holds maintenance throttle instead of popping in and out. The whole trace looks like one continuous plan.
A weak trace tells a different story. You may see a lift before the brake marker, then a pause, then a gentle brake ramp that never reaches the car’s useful deceleration. You may see a hard brake spike caused by finally realizing you are late. You may see the brake dropped abruptly at turn-in, followed by a coast because the car is not settled or not pointed. You may see a hopeful throttle pickup before the apex, then a lift because the car runs wide. Each of those patterns costs time differently. Some cost straight-line speed. Some cost minimum speed. Some cost exit speed. Some cost confidence, which then shows up as inconsistency lap to lap.
Use the combined trace to separate courage problems from technique problems. A driver may say they need to be braver on throttle. The data may show they are late to throttle because brake release is abrupt and the car will not accept drive. Another driver may say they need later brakes. The data may show the first fix is the 8 m coast before brake pressure. Another may say the car understeers on entry. The trace may show brake release ending too early, leaving the front unloaded during the first steering demand. Data and feel do not have to agree at first. Bentley’s point is that the useful information comes from both sources: how you felt it and how the data reported it.
The intermediate skill is to turn the trace into one next-session objective, not ten. Data for Drivers gives the right process: look for incongruencies, dig for details, use other channels, ask why, compare if you can, calibrate to your driving, imagine what ideal would look like, and set objectives for the next session. That is the workflow. Do not leave the paddock with a vague instruction to be smoother. Leave with a concrete target such as no measurable coast between throttle-off and brake-on at Turn 4, or brake release no longer vertical at turn-in, or throttle application after brake release with no second lift.
When comparing laps, resist the trap of judging by single peak values. The better lap is not always the one with the highest brake pressure or earliest throttle touch. Compare the combined sequence and the segment time. A lap with slightly earlier brake-on but no coast, a clean release, and committed exit throttle may beat a lap with a heroic late brake point followed by a long wait before throttle. A lap with an earlier throttle touch followed by a lift may be worse than a lap where throttle starts a little later and then keeps building. Your goal is not the prettiest individual trace. Your goal is the fastest repeatable car-and-driver package through that section.
The car-and-driver package matters because some technically faster data shapes may not be immediately usable for you. Bentley warns that the car can sometimes be made faster in a way that makes the driver less comfortable, and an uncomfortable driver is slow. Treat that as a calibration rule. If the data says the theoretical fastest version has a razor-thin brake release and instant throttle but your current skill produces tension, start by building a trace you can repeat. Smooth, immediate, confident, and repeatable beats a one-lap shape that scares you into backing up the next three laps.
For safety, keep the analysis inside the rules of the event and the corner. Threshold braking belongs in a straight line when the tire’s grip can be used for deceleration. Brake release should become more gradual and smooth as the car turns in. Throttle should be progressive from the apex and coordinated with unwinding the wheel, with maintenance throttle available to settle the car mid-corner. If the data tempts you to keep adding brake or throttle while steering demand is already high, check lateral g, steering, line, and whether the car actually accepted the command. The trace is not permission to overload the tire.
Here is the practical reading routine you can use after every session. Pick one corner. Put speed, throttle, brake pressure, steering, and lateral and longitudinal g on the screen if available. Use distance. Mark throttle-off, brake-on, brake release complete, and throttle-on. Measure the throttle-off to brake-on gap. Look at how fast brake pressure rises. Look at whether release shape changes as steering rises. Measure the brake-release to throttle-on gap. Check whether throttle has a second lift after first application. Compare your best segment lap to a slower but clean lap. Write one sentence explaining the story. Then write one objective for the next session.
A good one-sentence diagnosis sounds like this: I lifted 10 m before braking, built pressure slowly, released the brake abruptly at turn-in, then waited until the car was nearly straight before throttle. Another good diagnosis: I braked at the same point each lap, trailed pressure into the first steering, released smoothly, picked up throttle just after the car accepted rotation, and did not lift. Those sentences matter because they convert data into a driving instruction. The trace is only useful if it changes what your right foot does on the next lap.
The most important habit is to keep the story continuous. The end of throttle sets up the beginning of brake. The beginning of brake shapes the entry speed and front load. The brake release shapes whether the car turns. The first throttle application proves whether the entry worked. If you read those events separately, you get fragments. If you read them together, you see why the lap actually gained or lost time.
Worked example: the 225 km/h to 110 km/h medium-speed corner
Segers’ comparison is the cleanest example of why combined pedal analysis begins before the brake trace rises. Two drivers approach a medium-speed corner from a straight, reaching about 225 km/h and slowing to about 110 km/h. The displayed channels are speed, throttle, and front brake pressure. The obvious difference is braking point location: one brake pressure trace jumps up 35 m earlier than the other. The later-braking driver stays on throttle longer. The earlier-braking driver also shows an 8 m coasting period between coming off throttle and going on the brakes.
That 8 m coast is the lesson. If you looked only at the brake trace, you might talk about brake point, peak pressure, or brake distance. If you looked only at throttle, you might say the driver lifted early. Combined, the traces reveal the actual footwork story: throttle ended, useful braking did not begin, and distance disappeared. The correction is not to make a heroic jump to the later brake point. The first correction is to connect throttle-off to brake-on so the car is either accelerating or decelerating when it should be.
On your own data, find a similar corner and measure the same thing. Use the distance axis. Put a cursor at throttle-off and another at brake-on. If the gap is visible, name it honestly as coast. In the next session, keep the same brake reference at first and remove the gap by making the foot transfer cleaner. Once the trace shows no dead air, then test whether the whole brake event can move later. This sequence keeps the analysis disciplined: clean transition first, later braking second.
Worked example: Carousel Turn 4 and the brake-to-throttle handoff
The Going Faster telemetry image for Carousel, Turn 4, is useful because it shows why pedals cannot be read without the rest of the car. The displayed channels include speed, brake force, throttle position, steering, lateral g, and longitudinal g. At the shown point, brake force is zero, throttle position is about half, steering angle is substantial, lateral g is high, and longitudinal g is slightly negative. That single moment is not a complete corner diagnosis, but it is exactly the kind of snapshot that forces the right question: has the car accepted the handoff from braking to throttle while it is still cornering?
If you saw that point in your data, you would not stop at saying throttle is on. You would look backward to see how the brake was released. Did the brake pressure taper away as steering and lateral g built, or did it disappear abruptly? Did throttle begin immediately after release, or was there a long gap? Did the throttle remain stable, or did it come in and then lift? Did speed flatten, recover, or continue falling? Did steering begin to unwind as throttle increased, or was the driver adding throttle while still asking for nearly the same direction change?
This is the combined-pedal mindset. Brake force at zero does not mean the braking story is over. Throttle at half does not mean the exit is solved. The transition must be checked against steering and g-load because throttle is also a balance input. A confident trace through this kind of corner would show the driver releasing brake in a way the front tires accept, feeding throttle in without a second lift, and coordinating that throttle with the line rather than using the pedal as a guess.
Worked example: the longer 135-degree brake-turn entry
Lopez’s discussion of a 135-degree corner gives you the opposite case from a quick brake-and-go corner. In a longer direction-change entry, the brake-turn segment can be long enough that a simple progressive release is not the only useful shape. The driver may relax brake pressure to a selected level, hold that level briefly, and use that combination of braking and cornering effort to slow the car while putting it on the right path for the apex.
In data, this can look strange if you expect every correct brake trace to be a smooth diagonal line to zero. The trace may drop from a high initial pressure to a lower plateau, hold, and then release the rest near the brake-throttle transition. The question is whether the plateau is deliberate and repeatable. If it produces the right speed loss, keeps the car balanced, and puts the car on the correct path for throttle, it may be good technique for that corner. If the plateau changes every lap, extends too far, or creates a late wait for throttle, it is probably not controlled brake-turning.
This example also protects you from copying traces blindly. A brief corner may need little or no trail-braking phase. A long brake-turn corner may need a held pressure phase. A data lesson that teaches one ideal brake shape for every corner is too shallow. The better skill is to ask what the corner demands: how much direction change, how much speed loss, and where the brake-throttle transition has to happen.
Common mistakes
The first common mistake is the comfort coast. You lift before the brake marker, wait for the car to feel settled, and then brake. It feels tidy because nothing dramatic happens, but the combined trace shows distance with no acceleration and no meaningful deceleration. Good looks like a clean connection from throttle-off to brake-on, followed by a deliberate brake build.
The second mistake is the late-brake cover-up. You move the brake point later before fixing the foot transfer. The lap may feel more aggressive, but the trace still shows a gap, a panic ramp, or an abrupt release. Good looks like removing the coast first, then moving the whole connected event later only when the shape stays repeatable.
The third mistake is the cliff release. Brake pressure drops suddenly as steering demand begins. The driver often describes this as entry understeer, nervousness, or needing to wait before throttle. The trace shows the front load being taken away too quickly. Good looks like brake release matched to steering and cornering demand, with the car accepting the handoff instead of reacting to it.
The fourth mistake is the empty middle. The brake is fully released, but throttle does not begin for a long distance. Sometimes this means the entry was too fast. Sometimes it means the car was not pointed. Sometimes it means the driver released the brake in a way that created uncertainty. Good looks like a smaller, explainable gap between brake release and throttle-on, checked against steering angle, lateral g, and line.
The fifth mistake is the false early throttle. The trace shows throttle pickup, then a lift. It is tempting to count the first pickup as progress because it happened earlier, but the second lift is the confession. The car did not accept the request. Good looks like throttle that may start slightly later but stays in, builds progressively, and coordinates with unwinding steering.
The sixth mistake is single-channel judgment. You declare the braking good because peak pressure is high, or the throttle good because the first pickup is early. Combined pedal analysis asks whether the whole sequence worked. Good looks like speed, brake, throttle, steering, g-load, and segment time agreeing that the car was slowed, turned, and accelerated with less waiting and less correction.
Drill: the four-cursor footwork audit
Run this drill at your next event over three sessions. Pick one medium-speed corner with a clear braking zone and enough exit that throttle timing matters. Do not use the whole track. One corner is enough.
After session one, open your best lap and one ordinary lap. On each lap, place four cursors on the distance trace: throttle-off, brake-on, brake release complete, and throttle-on. Write down two distances: throttle-off to brake-on, and brake release complete to throttle-on. Then note whether throttle has a second lift after first application. Your only driving objective for session two is to reduce the first gap without moving the brake reference later. Success means the throttle-off to brake-on gap is smaller or gone on at least three laps, with no new panic spike in brake pressure.
After session two, repeat the cursor work. If the first gap is clean, shift attention to the brake release and throttle pickup. Look at steering and lateral g. Your session three objective is to make the release-to-throttle gap smaller only if the car is ready for it. Success means throttle begins with no second lift on at least three laps, and the segment time improves or stays equal with better repeatability. If earlier throttle creates a lift, count that as a failed attempt, not a win.
The drill works because it forces the data into a driver action. You are not trying to become a data engineer in the paddock. You are learning to see the story your feet told, choose one edit, and test whether the next story is cleaner.
Calibration cues
Use three kinds of cues: felt cues, trace cues, and lap-result cues. The felt cue for a good brake-to-throttle handoff is that you cannot clearly feel the car change personalities when you leave brake and begin throttle. The car should not pitch, wash, snap, or demand a long wait. It should feel like one continuous corner entry and exit process.
The trace cue is continuity. Throttle-off and brake-on are connected. Brake pressure builds deliberately. Brake release shape matches the steering and lateral-g story. Throttle begins when the car can accept it and does not immediately retreat. The supporting channels should explain the pedal choices rather than contradict them.
The lap-result cue is repeatability before heroics. Segment time should improve because waste is removed, not because one lap was brave and three laps were messy. If your theoretical fastest lap improves but your normal laps scatter, the change may be beyond your current calibration. If your ordinary laps tighten up and the trace shows less waiting, you are building the skill correctly.
When the principle changes by corner type
The no-wasted-distance principle is constant, but the best trace shape changes with the corner. A heavy straight-line braking zone rewards a decisive throttle-to-brake transition and quick pressure build because the tires are mostly available for deceleration. A short corner where throttle can begin around turn-in may have little or no trail-brake phase. A longer brake-turn corner may need pressure trailed away gradually or reduced to a held level before the final release.
Fast corners deserve extra caution in analysis. Data for Drivers specifically calls out lifts in fast corners as something to look for. A lift in a fast corner can be a confidence problem, a line problem, or a response to asking too much of the car. Do not solve it by ordering yourself to keep your foot down. Check whether the first throttle application, steering demand, and lateral g make sense together.
The principle also changes with your current skill. Bentley’s car-and-driver package warning matters here. The data may point toward a quicker transition, but the useful version is the quickest transition you can repeat while staying smooth and confident. As your calibration improves, the trace can become more immediate without becoming abrupt.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | Ultimate Speed Secrets - Ross Bentley | c1003d983022bb389e95863e22484e7a | 308 | 1 | uio_books_raw_v1 |
| 2 | Ultimate Speed Secrets - Ross Bentley | 24d0fd2e-bc3c-04ba-6c51-6a9e81262f3d | 166 | 1 | uio_books_raw_v1 |
| 3 | Analysis Techniques for Racecar Data Acquisition | 027ef26c-8c9d-bed5-441c-ad04c76402d8 | 18 | 1 | uio_books_raw_v1 |
| 4 | Data for Drivers | cabda699642b26311b0a7ef998da2c71 | 15 | 1 | uio_books_raw_v1 |
| 5 | Going Faster Mastering the Art of Race Driving - Carl Lopez | b44facad-81c0-1eac-14be-cb4387cc3304 | 101 | 1 | uio_books_raw_v1 |
| 6 | Going Faster Mastering the Art of Race Driving - Carl Lopez | 3b70eb1f-e4e3-c70c-1221-c2c8a8e43d83 | 51 | 1 | uio_books_raw_v1 |
| 7 | Going Faster Mastering the Art of Race Driving - Carl Lopez | 45971dd4-0d71-6e07-fc70-11fcf52f0fb6 | 102 | 1 | uio_books_raw_v1 |
| 8 | Briefing on High-Performance Driving and Event Operations | 7210c4cf-a7ff-fe1e-01f8-63fca8b5a8fd | 1 | 1 | uio_books_raw_v1 |