Advertisement
Advertisement
Hocevar penalized for spinning Burton under yellow at Nashville

Matt Thacker/Motorsport Images

By Kelly Crandall - Jul 2, 2024, 5:58 PM ET

Hocevar penalized for spinning Burton under yellow at Nashville

Carson Hocevar has been fined and docked points by NASCAR for spinning Harrison Burton under caution Sunday at Nashville Superspeedway.

The Spire Motorsports driver lost $50,000 and 25 driver points. NASCAR cited sections 4.4B of the Rule Book, which is NASCAR Member Code of Conduct Penalty Options and Guidelines.

The incident between Hocevar and Burton happened with 58 laps to go in the Ally 400. Under caution, which was brought out for a Brad Keselowski crash in Turn 2, Hocevar hooked Burton in the right rear and spun him on the backstretch. The two had already cleared the crash scene when Hocevar drove up to the rear of Burton’s No. 21 Wood Brothers Racing Ford Mustang and made contact.

Burton did not hit the wall or make contact with another driver. He finished 28th.

Hocevar and the No. 77 Spire Motorsports team finished 16th. He was not penalized for the incident during the race.

Additionally, Tuesday’s penalty report featured two fines for Craftsman Truck Series crew chiefs. Both were for having one loose lug nut after Friday night’s race.

Jon Leonard, crew chief of the No. 42 for Matt Mills, was fined $2,500. Jeriod Prince, crew chief of the No. 88 for Matt Crafton, was also fined $2,500.

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.