F1 »

Engine continuity eased Red Bull design process

Retaining Renault F1 power may not have been what Red Bull wanted for 2016, but the team believes it can be more successful this season with an evolution of recent designs.
It may not have been too enamoured with the prospect of running Renault-derived V6s this season, but Red Bull Racing admits that there would have been more work to do had it managed to change engine suppliers after a dire 2015 campaign.

The fall-out between RBR and Renault was very public and, for some time, could have led to the four-time world champion constructor withdrawing from the sport, as it appeared that the rift with Viry-Chatillon was too big to bridge after alternative suppliers - namely Ferrari and Mercedes - made no secret of the fact that they were unwilling to partner RBR on the team's terms.

With some sort of healing process put in place towards the end of last year, however, RBR will be on the grid, running Renault power units under the TAG-Heuer moniker and with Mario Ilien providing the tweaks the team hopes will move it closer to the pace and improved reliability. It may not have been the preferred option - although year-old Ferrari engines was hardly a desired alternative - but the design team in Milton Keynes admits that retaining a familiar power unit made the build-up to 2016 a lot smoother.

"We were looking at other power units, there is no secret to that," chief engineering officer Rob Marshall confirmed, "We had a good idea of what requirements those would have on [the RB12] car design, so we were looking at various different car design concepts in parallel.

"It is obviously never easy when you get a late decision on what engine you are going to put in but, in hindsight, keeping one which is generically similar to one we took out did simplify the task. Whilst we could have squeezed a different engine on a tighter timescale, it made it much easier to have one that was the same shape and architecture.

"If we were going to put a different power unit in, the car would be quite different architecturally, basically because the various different power units up and down the grid need different installations - where the batteries are, how big they are, that sort of stuff. It would affect the overall car architecture and also the cooling requirements for the power units are different but, by staying with the same unit, we understood all the heat rejection requirements so, while it was late, it meant we could be quite confident we could get it right."

With the change in the terms of Renault's supply deal, there will be less technical collaboration between the two parties, but Marshall admits that the French connection will still be keeping an eye on how the RBR package runs this year.

"I think Renault are still interested in how the whole power unit/chassis should be integrated, but I guess we want to see how we move forward from here," he noted.

Although the matter is not open for debate, there will always be the question of whether remaining with Renault was the right option for Red Bull, but chief technical officer Adrian Newey is convinced the team took the best option available.

"Firstly, the option was closed to us with regard to the one year out of date Ferrari," he clarified, "Secondly, you are dooming yourself to always be some way behind and, while I believe I am not allowed to refer to who makes the power unit these days, our power unit manufacturer are on a good course now. They had a good winter. Obviously, it is a big deficit to make up, but I think, with the new procedures, the new budget, the way they are working, they are on a good path, so I am confident they will slowly close the gap."



Related Pictures

Click on relevant pic to enlarge
(L to R): Christian Horner (GBR) Red Bull Racing Team Principal with Rob Marshall (GBR) Red Bull Racing Chief Engineering Officer. 02.02.2015.
Daniil Kvyat (RUS) Red Bull Racing RB12. 24.02.2016.
Daniil Kvyat (RUS) Red Bull Racing RB12. 25.02.2016.
Daniel Ricciardo (AUS) Red Bull Racing RB11 rear wing detail. 23.02.2016.
Daniel Ricciardo (AUS) Red Bull Racing RB11. 23.02.2016.
27.11.2016 - Race, Start of the race, Daniel Ricciardo (AUS) Red Bull Racing RB12 and Sebastian Vettel (GER) Scuderia Ferrari SF16-H and Kimi Raikkonen (FIN) Scuderia Ferrari SF16-H
27.11.2016 - Race, Max Verstappen (NED) Red Bull Racing RB12
27.11.2016 - Race, Jolyon Palmer (GBR) Renault Sport F1 Team RS16 and Esteban Gutierrez (MEX) Haas F1 Team VF-16
27.11.2016 - Race, Max Verstappen (NED) Red Bull Racing RB12 leads Nico Rosberg (GER) Mercedes AMG F1 W07 Hybrid
27.11.2016 - Race, Jolyon Palmer (GBR) Renault Sport F1 Team RS16 and Jenson Button (GBR)  McLaren Honda MP4-31
27.11.2016 - Race,Kimi Raikkonen (FIN) Scuderia Ferrari SF16-H  leads Daniel Ricciardo (AUS) Red Bull Racing RB12
27.11.2016 - Race, Felipe Nasr (BRA) Sauber C34 and Max Verstappen (NED) Red Bull Racing RB12
27.11.2016 - Race, Daniel Ricciardo (AUS) Red Bull Racing RB12 leads Sebastian Vettel (GER) Scuderia Ferrari SF16-H
27.11.2016 - Race, Daniel Ricciardo (AUS) Red Bull Racing RB12
27.11.2016 - Race, Start of the race, Fernando Alonso (ESP) McLaren Honda MP4-31 off trach and Max Verstappen (NED) Red Bull Racing RB12 spins
27.11.2016 - Race, Daniel Ricciardo (AUS) Red Bull Racing RB12 and Sebastian Vettel (GER) Scuderia Ferrari SF16-H
27.11.2016 - Race, Daniel Ricciardo (AUS) Red Bull Racing RB12 and Sebastian Vettel (GER) Scuderia Ferrari SF16-H
27.11.2016 - Race, Max Verstappen (NED) Red Bull Racing RB12

Join the conversation - Add your comment

Please login or register before adding your comments.

Although the administrators and moderators of this website will attempt to keep all objectionable comments off these pages, it is impossible for us to review all messages. All messages express the views of the poster, and neither Crash Media Group nor Crash.Net will be held responsible for the content of any message. We do not vouch for or warrant the accuracy, completeness or usefulness of any message, and are not responsible for the contents of any message. If you find a message objectionable, please contact us and inform us of the problem or use the [report] function next to the offending post. Any message that does not conform with the policy of this service can be edited or removed with immediate effect.




© 1999 - 2016 Crash Media Group

The total or partial reproduction of text, photographs or illustrations is not permitted in any form.