Q: Just wanted to tell you I thought your column in Winding Road on how to know when you’re driving on the limit was especially powerful. The insight that the way you drive affects the theoretical limit ought to be drilled into every race driver. But for me, the really critical element was the section about corner entry. Corner exit is relatively easy, and I’m there or thereabouts at the apex. But the really good guys still carry more speed than me down to the apex. (The other issue in Spec Miata is that you have to commit to the throttle before the car takes a set, which requires a certain amount of confidence.) I really make a point during practice of forcing myself to go fast enough so that the car loses grip on turn-in, then dial it back a notch. Unfortunately, I don’t have the stones to do this in the really fast, high-commitment corners. Speaking of which, I was talking to Josef Newgarden at the Phoenix test this year, and I asked him how he worked up to speed in Turn 1. He told me that his approach on ovals is to go flat, and if the car starts to move, then he slows down. It’s a good thing I can make a living as a journalist… but how do I know what’s the right corner entry speed?
A: I think what Josef talked about is one of the most difficult things for a driver to do. Human instinct agrees with the old advice, “Go in slow, and come out fast,” and yet it’s not always the fastest way to drive. Trusting that if you go in fast (even too fast), that you can respond appropriately, and even use that to your advantage, is the key, right? This really applies to driving in the rain, too. Many drivers go into a corner at something just below the limit, and then gradually increase their speed through the corner until the car “steps out.” At that point, they’re reacting to it. If, instead, they go into the corner slightly above the limit, they know that the car is going to “step out,” and then the response is expected – even planned. It’s the difference between being reactive and being proactive.
How many times have you entered a corner too fast? I suspect it’s more than once! How many times did entering too fast result in a crash? I suspect very few, if any. When you think about that logically, it makes you trust yourself more, knowing that if you carry too much entry speed, it’ll be okay. The worse case is that you’ll be slow; the best case is that you find out that speed works – not only works, but is the right speed. So do the analysis – statistically, how many times have going into a corner “too fast” resulted in a crash? Then let that sink in. It’s okay to enter a corner too fast – just as Josef does.
Of course, having lots of time to practice this helps…
This is a really good question, and a great answer from Ross. I’ll add that in order to improve your corner entry speed, you need to be able to “see” it, and plan for it not working. I’ll explain what I mean by that:
1. We all know the power of visualization. If you have driven a particular corner hundreds of times, you are probably able to visualize your typical approach through that corner in very high detail. If you want to increase your corner entry speed, I suggest starting with trying to visualize it. Can you imagine yourself entering the corner with a higher speed? What does that do to when you get on and off the brakes? How does it affect your turn in point? How does it affect your entry angle? How does it affect the behavior of the car mid corner? How does it affect when you will be able to get back on the throttle? Try to visualize all of that is as much detail as possible! Doing so will give you (safe) practice before you ever try it on a track.
2. Building on that, also plan for the different ways things can go wrong. Maybe the car will understeer when you turn in at a higher speed? Maybe the car will get loose as you try to scrub speed off after entering a bit too fast. Imagine all those scenarios, and plan your contingencies ahead of time. This way, you aren’t surprised if/when it happens. You will already have a safe exit strategy planned out.
Great stuff, Vivek. Thanks for adding on to my answer.