ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

This Year's Chase May Show What Kind of Champion Keselowski Is

Updated on September 4, 2013
Words of wisdom from a six time champion
Words of wisdom from a six time champion

Sometimes you learn more about a player, driver or team when they lose than you can learn from a victory. No one wins every race, makes every shot, wins every game. Even the 1972 Dolphins, who ran the table at 17-0 with a Super Bowl victory, lost the following year with basically the same roster. So losing is a part of all sports, including auto racing. With Brad Keselowski needing a miracle Saturday night at Richmond, we may well soon see just how the Blue Deuce team responds to being unable to defend their series championship in this year's Chase. How they react when and if that happens may yet tell us if Keselowski is the next Gordon / Johnson / Earnhardt- or if he's simply a one hit wonder who happened to put together a lucky season.

Brad Keselowski sits on the edge of missing the Chase after winning it all last season
Brad Keselowski sits on the edge of missing the Chase after winning it all last season
Kasey Kahne will be a part of NASCAR's playoffs while Keselowski needs a miracle
Kasey Kahne will be a part of NASCAR's playoffs while Keselowski needs a miracle

Keselowski's run to the Sprint Cup in 2012 was an example of sustained consistency and excellence. In ten Chase races, Brad won twice and finished outside the top ten only two times. One has an 11th place finish in Charlotte and the other was a 15th place in the finale at Homestead (when the title was already decided). The only real adversity the team faced during that ten race stretch was overcoming their pedestrian qualifying efforts. They avoided the major wrecks, managed to hit on the right setup weekly, and raced smart at every track. Over the course of the entire 36 race schedule they had only one DNF, a crash at the season opening race at Daytona.

While luck certainly plays a role in racing, Keselowski's struggles in 2013 (compared to 2012) do not seem to stem from a simple lack of luck. Aside from last Saturday's engine woes at Atlanta, the #2 has only one other DNF this year (a crash at Charlotte). The team has completed over 96% of the scheduled laps this season. Contrast that with hard-luck case Kasey Kahne, who's lost several races to accidents not of his making and has completed under 95% of the scheduled laps.

The difference between Kahne and Keselowski is that when Kahne hasn't wrecked his car has had speed. He has a pair of wins that ensure should he finish outside the top ten in points he'll still have a seat at the table once NASCAR's playoffs start. In addition to the wins he has more than double the laps led this season compared to Keselowski. Ultimately Kahne is running up front and in contention for wins while the defending series champion is clinging to the end of the lead lap.

Logano is having the best season of his career and is Chase eligible, driving the same equipment as the defending champ Keselowski
Logano is having the best season of his career and is Chase eligible, driving the same equipment as the defending champ Keselowski

Coming into 2013, Penske was expected to experience some growing pains. The team had been the lone major Dodge team left in the sport in 2012 and received their manufacturers undivided attention. While the imminent departure of Penske to Ford was known prior to season's end, Dodge undoubtedly wanted to go out on a high note and provided Penske with the tools they needed to compete for a title. The transition to Ford meant that Penske not only changed manufacturers but also that they gave up control of their engines. That kind of change is something that any team would struggle with; throw in the new Gen 6 car NASCAR debuted this season and you have enough change to throw any team off its game.

Yet it's not as if the team as a whole is down on power or speed. In his first season with Penske, Joey Logano is having the best season of his career. He has a win, eight top fives and 14 top ten finishes in the first 25 races. He's in position to qualify for the Chase and hasn't finished below eight since July's race in New Hampshire. The team qualifies well and follows it up with solid finishes every week. With the Chase looming, Logano's team is hitting on all cylinders and has a real shot to replicate this year what Keselowski did last year.

Keselowski and Wolfe won a title together last season
Keselowski and Wolfe won a title together last season
Dale Jarrett won the 1999 title by more than a full race in points
Dale Jarrett won the 1999 title by more than a full race in points

NASCAR's history is littered with drivers who built to one magical season then never reached those heights again. In the last 20 years, Dale Jarrett and Bobby Labonte provide a pair of cautionary tales. Jarrett won the 1999 series championship after finishing either second or third the three years prior. After his title run, Jarrett's points position steadily declined to where he finished 26th in points four years later. Labonte won the 2000 championship but by 2004 he was outside the top ten in points and never won a race after the '03 season. Both drivers ran for competitive teams; Jarrett spent a decade with Yates while Labonte watched his teammate, Tony Stewart, win a pair of championships. Yet both never achieved the same level of success they found in winning a championship. That's not to say that either was a poor driver or lacked effort; in fact, both gained even greater popularity in the seasons after their titles. But they were not running for championships.

Keselowski and Paul Wolfe may soon face that dilemma themselves. Unless they win at Richmond (and several other things break their way), they will be on the outside looking in for the last ten races of the season. They will have every reason to go through the motions in terms of their own performance and begin waiting for the calendar pages to turn. With NASCAR's attention firmly fixed on the 12 Chase drivers, their performances will go under the radar. Few will notice and fewer will care what takes place inside the Blue Deuce garage. But they will know and that knowledge will go a long way into determining whether Keselowski is ever able to be a championship contender again.

Kyle Busch missed the Chase last year and his team responded with a great run of finishes to end the year
Kyle Busch missed the Chase last year and his team responded with a great run of finishes to end the year

Kyle Busch knows a little something about that. His team missed the Chase last season. While their season-end numbers in top five and top ten finishes roughly matched their prior year's performance, the wins just weren't there (he won only one race, a spring victory in Richmond). Already ineligible to compete for a championship, the team hit its nadir at Chase race #2 in New Hampshire. They finished two laps down in 28th place. Instead of packing it in and waiting until next year, the team doubled down their efforts and scored six top five finishes over the final eight races. Busch now credits that strong finish with the momentum the team carries this season. They've won four races and sit firmly inside the Chase even if they team were to sit out the Richmond race.

So the question for the Blue Deuce crew is not how can they qualify for the Chase. Even a win would not guarantee them a chance; it's merely the price of admission to even have a shot right now. Like Jordan, they've failed multiple times so far. The question is whether they're going to merely accept the reality of their current situation- or whether this failure will be why they succeed.

Now it's your turn!

If Brad Keselowski misses this year's Chase, how do you think the team will respond?

See results


    0 of 8192 characters used
    Post Comment
    • profile image

      Christian Budd 

      6 years ago

      You oversimplify the issue of Keselowski's season. Yes, he has had some poor runs. They were not running well at Bristol, for instance, before being caught up in a wreck. They didn't run well at Charlotte before a self inflicted accident with Danica Patrick. They made some poor strategy calls (Indianapolis for example) but they have also had their share of bad luck.

      In modern day Nascar, you can have a bad luck and not DNF. They had a top 10 car before an engine problem at California in the waning laps that cost a lot of points (finished 23rd). They had another top 10 car (despite hitting the wall due to a cut valve stem) before another engine problem at the end of the Richmond race (finished 33rd). Obviously they had a third terminal engine problem at Atlanta with a competitive car. They were wrecked while running top 10 by Kurt Busch at Kentucky (finished 33rd). They were caught up in a wreck not of their own making at Darlington (finished 32nd).

      All in all, your analysis is simply wrong. They were extremely fast early in the season (despite Ford's well documented struggles) and have been a top 10 car in most of the races they have run. Ultimately, reliability is what will keep this team out of the chase this year. You can't break parts, and the #2 team has broken three engines this year that cost them easily 50 points. Add in the inevitable wrecks, and you end up with a disappointing season.


    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

    Show Details
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
    ClickscoThis is a data management platform studying reader behavior (Privacy Policy)