
IndyCar: BHA confirms Chaves
As predicted by RACER last week
, Bryan Herta Autosport has confirmed that 2014 Indy Lights champion Gabby Chaves will drive its No. 98 entry in the 2015 Verizon IndyCar Series.Colombian-American Chaves took four wins en route to last year's Indy Lights title, and joins the team for his rookie IndyCar season. Toronto-based David Bowen continues his partnership in the #98 entry that began in 2012. "Corporate partners for the team will be revealed in a series of upcoming announcements," according to a BHA release.
"I'm so excited and honored to be the latest Colombian driver in IndyCar!" said Chaves. "Our country has such a great history in the sport and especially at the Indianapolis 500 with drivers like Roberto Guerrero, Juan Pablo Montoya, and Carlos Munoz – I can't wait to make my own history there!
"I'd like to thank my personal team that has been supporting me since the start of my career. It's been an incredible journey and to finally become a Verizon IndyCar driver is an awesome feeling and the start of a great future. I'd also like to thank Bryan Herta and the entire BHA team for this opportunity. I'm really excited and prepared to get the 2015 season underway."
Said team boss Bryan Herta: "We're excited to have Gabby join the team this year. In December we had the opportunity to test him at Sebring and his speed and feedback were very impressive. Gabby has the skills and mindset to make a real impact in Indycar, I see no reason why Gabby should not be a top contender for Sunoco Rookie of the Year honors."
"Recent experience has shown that top drivers graduating from Indy Lights have transitioned to Indycar with great success. We have had the opportunity to work with a few rookie drivers in the last couple years and we believe we have a great environment to support their development and achieve great results."
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.





