
INDY 500: Howard confirmed for Tony Stewart-SPM
revealed in February
, the Briton will join SPM regulars James Hinchcliffe and Mikhail Aleshin for the 101st Indy 500 as the team seeks its first win at the Speedway.The 2011 Indy 500 starter will represent Stewart's Team One Cure initiative, which seeks to raise awareness and donations for cancer research.
"I can't begin to tell you how honored I am to have this opportunity," said Howard, who finished 30th on his Indy 500 debut driving an entry for Rahal Letterman Lanigan Racing/Sam Schmidt Motorsports. "I'm not one to give up on a dream and I have every bit of determination to make this a successful effort for Tony, Team One Cure and Schmidt Peterson Motorsports. I'm in the best condition both mentally and physically, and my race craft is on point. We will be more than ready when IMS opens for practice this May."
"I have every bit of confidence in the skills of Jay behind the wheel," Stewart said. "Growing up 45 minutes from the Speedway, the Indianapolis 500 is an important part of my racing history. Participating in this year's race with Jay and Sam through Team One Cure, we will be making a difference in both the 500 and the race against cancer."
Reuniting with Howard, who won the 2006 Indy Lights title while driving for Schmidt, will make for a an overdue homecoming.
"We are pleased to have Jay competing with Schmidt Peterson Motorsports once again," said Schmidt. "Given our impressive winning record together in the past, we have high expectations for the 101st Indy 500. Jay is extremely talented in the car as well as being a great advocate for the Team One Cure initiative."
.@14TSF&@CSUVetMedBioScihave announced the#TeamOneCurepick for this year's#Indy500in@JayHowardRacing.#INDYCARpic.twitter.com/CcpDsxVHQp— Schmidt Peterson (@SPMIndyCar)March 6, 2017
//platform.twitter.com/widgets.js
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.





