Blogs

Kyle Larson Returning to No. 42 Car for Duck Commander 500

Kyle Larson Returning to No. 42 Car for Duck Commander 500

by April 3, 2015 0 comments

Photo credit: Jeff Zelevansky/NASCAR via Getty Images

CHARLOTTE, N.C. — After sitting out of Sunday’s STP 500 after spending Saturday to Monday night in various hospitals, Kyle Larson has received the okay to return to the race track for next Saturday night’s Duck Commander 500 at Texas Motor Speedway.

The driver of the No. 42 Target Chevrolet for Chip Ganassi began to feel lightheaded late into an autograph session at Martinsville Speedway on Saturday before fainting.

The 2014 Sprint Cup rookie of the year was immediately taken to Martinsville Memorial Hospital in Martinsville, Va. and was then flown to Carolinas Medical Center in Charlotte to undergo further tests, all which came up negative.

Speaking on what held himself from competing in his fourth career race at the half-mile short track, Larson points to dehydration as the culprit for his weekend spent away from the race track.

“Well, I felt fine before we went to the autograph session,” Larson explained. “I got through to the end of it, and I was just talking to one more fan, the last person there really, and just started getting lightheaded and tried to lean forward and maybe see if that fixed it, and then I passed out.

“I don’t know, it was just kind of a weird morning just because I was almost late to practice, so I just rushed myself that morning and didn’t take very good care of myself throughout the day and just ended up dehydrating myself. Just got to do a better job of taking care of myself, and that should never happen again.”

After missing the STP 500, Larson enters next Saturday’s Duck Commander 500 24th in the drivers standings while the No. 42 Chevrolet enters Texas 21st in the owners standings after Regan Smith drove the car at Martinsville to a 16th-place finish.

Follow Kyle Pokrefky on Twitter at @KPokrefky

Kyle Pokrefky
Follow Kyle Pokrefky on Twitter at @KPokrefky

No Comments so far

Jump into a conversation

No Comments Yet!

You can be the one to start a conversation.

Leave a Comment