
Larson wins Richmond as playoff field is set
Although there was considerable focus leading up to Saturday night's final regular-season race of the Monster Energy NASCAR Cup Series season at Richmond International Raceway on those needing a win to get in being in win-or-bust mode, as it turned out the race proved a battle between regular season heavyweights. Kyle Larson claimed his fourth win of the year, eclipsing regular season champ Martin Truex Jr. in an overtime finish. Truex then crashed in the final lap after making contact with Denny Hamlin, and finished 20th.
Larson took the lead for the final time after a brilliant pit stop from the Chip Ganassi Racing No. 42 Chevrolet crew put him in front for the overtime restart.
Related Stories
"I've got the greatest team out here and definitely the best pit crew," Larson said. "That showed tonight. I can't thank those guys enough. They were money all night long to gain spots. This win is a huge congrats to them. The Target Chevy was pretty good all night. The No. 78 (Truex) was definitely the best, but I thought I was second best for most of the runs.
"It came down to the last restart there, and I got a good start. I spun my tires pretty bad, and I was a little nervous, but we cleared him (Truex) into (Turn) 1, and I was pretty excited about that. I'm really pumped for the playoffs. We've got a great shot at the championship, I feel like, this year. So I'm looking forward to it."
Joey Logano finished second his Team Penske No. 22 Ford 0.951 seconds behind at the the checkered flag – and consequently that much short of a playoff berth – after Truex crashed. Ryan Newman, Kurt Busch and Daniel Suarez rounded out the top five, while Matt Kenseth, Chase Elliott and Jamie McMurray claimed the final three playoff slots.
Click here
for full results.The 16-driver playoff field, with the projected seeding, follows below.
Latest News
Comments
Comments are disabled until you accept Social Networking Cookies. Update cookie preferences
If the dialog doesn't appear, ad-blockers are often the cause; try disabling yours or see our Social Features Support.




