
Image by Nigel Kinrade/LAT
Kahne to call time on Cup at year’s end
Kasey Kahne is the second driver in as many days to have announced his impending NASCAR retirement.
Via his Twitter page, Kahne explained that “racing in Cup full-time for a few more years was just something that I couldn’t commit to.” The 38-year-old says he will focus on his son, Tanner, and his Kasey Kahne Racing sprint car teams.
https://twitter.com/kaseykahne/status/1030068665620811777/photo/1
Kahne won the 2004 Rookie of the Year award in the NASCAR Cup Series after arriving on the scene as a highly-touted prospect driving for Ray Evernham. A winner of 18 Cup races, his most recent being the 2017 Brickyard 400, Kahne has competed for teams such as Richard Petty, Red Bull Racing, and Hendrick Motorsports.

Kahne (9) battles Jimmie Johnson at Darlington in 2004. (Image by Robert LeSieur/LAT)
To date, Kahne has made 527 Cup Series starts. He also has eight career wins in the Xfinity Series in 215 starts, and five wins in the Camping World Truck Series in six starts.
Kahne will vacate the No. 95 seat at Leavine Family Racing. In addition to replacing the driver, LFR is also evaluating its options when it comes to manufacturer and alliance support, having told Richard Childress Racing last month they would not continue with them next season.
News of Kahne's plans follow yesterday's announcement that Elliott Sadler will step back from full-time racing at the end of the year.
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
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.




