Advertisement
Advertisement
Kenseth's Cup return ends in late Kansas wreck

Image by LaBounty/LAT

By Kelly Crandall - May 13, 2018, 12:13 AM ET

Kenseth's Cup return ends in late Kansas wreck

Matt Kenseth’s return to NASCAR competition ended prematurely Saturday night at Kansas Speedway with a torn-up race car.

Involved in a multi-car accident off Turn 4 on Lap 254, Kenseth finished 36th.

“I don’t have any idea what happened with the wreck; I just saw everybody wrecking and the track was kind of blocked, so I tried to get down towards the grass,” Kenseth said. “This grass is not the new friendly grass with the rain and all it just kind dug in and then I hit the car in front of me.”

[protected-iframe id="b0e9687d072fee0827f10efc7920bdca-139854255-134414717" info="twsrc%5Etfw" class="twitter-video" height="350"]

Prior to the accident Kenseth struggled with his first experience in the No. 6 Ford.

Repeatedly telling the team the car was undrivable and had no grip, Kenseth ran outside the top 25 much of the night. Falling off the lead lap before the competition caution was displayed on Lap 30, Kenseth got the free pass under the subsequent caution but lost a lap again later on.

“I expected us to be a little more competitive than that, so it was a really tough weekend all around,” Kenseth said. “We obviously have some work to do. The good news is it’s got to get better.”

Kenseth will continue in the car for the next four consecutive weeks.

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.