
Hunter-Reay hoping for 2017 turnaround at Texas
It happens to at least one IndyCar veteran each season, and this year, it's Ryan Hunter-Reay's turn.
"My wife and I were talking about this the other day...what do we need to do?" the Andretti Autosport driver told RACER with a laugh. "We're honest, hard-working people...we try to lead good, positive lives...something's gotta give at some point, right? We just can't buy a break, it seems."
The 2012 series champion and 2014 Indy 500 has led a blessed life, but you wouldn't know it by looking at the current stats from the opening eight rounds of the year. Hunter-Reay has two bright spots to cling to – a fourth at St. Petersburg and a third at the GP of Indy – but everything else has been a championship killer.
Five finishes of 13th or worse – including a 27th at the Indy 500 after an engine blew while contending for the win – and double disappointment at the Dual in Detroit where he placed 13th and 17th, has Hunter-Reay clinging to hopes and prayers his luck will improve.
Related Stories
"It's mind-boggling, but I'm also aware I'm the lucky guy who's going to drive the No. 28 DHL Honda through 2020, and I have a shot to win everywhere we go," he said. "I won't lie and say it isn't frustrating; dating back to Pocono last year, it seems like we've been trying to shake this bad luck, and coming out of the Indy GP in sixth in points.
"We had a lot of misfortune at the 500 and again in Detroit, but if you look at what Graham [Rahal] did, he put two wins together and now he's in the thick of the points battle. He's where we want to be, and we know we can be there with him if a few breaks go our way."
Hunter-Reay heads into tonight's RainGuard 600 race at Texas holding 13th in the championship standings with 183 points, 120 behind leader Scott Dixon.
Presented by:

For making every mile more exhilarating
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.





