Andretti, Rossi staying with Honda
Alexander Rossi will be staying with Michael Andretti in 2018, which answers the question about which engine manufacturer Andretti Autosport is going to be running.
RACER can report they're both staying with Honda. The lengths of their respective contracts are unknown.
RACER broke the story over the weekend that this year's Indy 500 winner, Takuma Sato, was headed for Rahal/Letterman/Lanigan Racing to join Graham Rahal next season
, Andretti was asked if that would have any bearing on his engine decision. He smiled and replied, "Are you sure about that?" and then said he hadn't made up his mind but hoped to have an answer before the Sonoma finale on Sept. 17.Andretti and team manager Rob Edwards were seen talking with Honda officials at Gateway and Monday afternoon RACER confirmed through team sources that the winners of three of the past four Indianapolis 500s with Honda were staying put after weeks of speculation that Chevrolet had made Michael a tempting offer to leave.
Related Stories
Rossi, the 2016 Indy victor, has become a Honda favorite and it was believed he would be driving for Honda regardless of what Andretti did.
A call to Rossi for comment was not immediately returned.
Ryan Hunter-Reay, Marco Andretti and Rossi are now set for next year with a fourth driver yet to be decided, although it appears Zach Veach, among others, is in the picture for Sato's vacant seat.
A strong recruiting effort to bring Rossi and his Bryan Herta team over to Schmidt Peterson Motorsports to partner with James Hinchcliffe was ultimately unsuccessful, so now the rumor mill switches to Chip Ganassi Racing. CGR is likely losing three of his four current drivers but obviously retaining four-time champ Scott Dixon in his Honda-backed operation, and like Ganassi, most IndyCar teams are also less than solid on next year's driver line-ups.
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.
