Advertisement
Kyle Busch loses crew chief for one race after Roval lug nut infraction

John Harrelson/Motorsport Images

By Kelly Crandall - Oct 10, 2021, 7:52 PM ET

Kyle Busch loses crew chief for one race after Roval lug nut infraction

Kyle Busch will work with an interim crew chief next weekend at Texas Motor Speedway to open the Round of 8 in the NASCAR Cup Series playoffs.

In addition to being fined $20,000, Ben Beshore will have to serve a one-race suspension because there were two lug nuts not secure on the No. 18 Toyota Camry after Sunday afternoon’s race. Busch finished fourth in the elimination race at the Charlotte Motor Speedway Roval.

Busch starts the next round seeded fifth on the playoff grid with 4023 points.

“We won both of them within the last year, so I feel like that’s a good omen for us,” Busch said of the upcoming races at Texas and Kansas. “The mile-and-a-half programs have been really strong for us. We did not run so well at Texas with the All-Star Race, but that was different, just everything. Have to keep ourselves upfront, and hopefully, we get to start upfront, so that should be a pretty good starting spot for us. Looking forward to next week.”

There were no significant issues in post-race inspection at Charlotte. The cars of Denny Hamlin and Chris Buescher each had one lug nut not secure. The crew chiefs of their respective teams, Chris Gabehart and Scott Graves, will be fined $10,000.

Kelly Crandall
Kelly Crandall

Kelly has been on the NASCAR beat full-time since 2013, and joined RACER as chief NASCAR writer in 2017. Her work has also appeared in NASCAR.com, the NASCAR Illustrated magazine, and NBC Sports. A corporate communications graduate from Central Penn College, Crandall is a two-time George Cunningham Writer of the Year recipient from the National Motorsports Press Association.

Read Kelly Crandall's articles

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.