
Force India VJM10 unveiled at Silverstone
Force India has become the latest team to launch its 2017 car, unveiling the VJM10 at Silverstone.
Fresh from finishing fourth in the constructors' championship last season – the best result in the team's history – Force India took the covers off its 2017 car at the Silverstone circuit, just across the road from its Dadford Road factory. The new car was unveiled by Sergio Perez and Esteban Ocon, who replaces Nico Hulkenberg after the latter moved to Renault.
The new car features a large shark fin extending toward the rear wing, while there is a clear step as the nose drops away from the front of the chassis. The "nostrils" seen on previous Force India noses have been updated on the car, which features a predominantly silver livery this season.

Team principal Vijay Mallya says Force India has been preparing for a high rate of development this season and will be updating the car throughout the year.
"The 2017 regulations has meant everyone has to start with a clean slate so I don't think we will know the likely pecking order before the tests in Barcelona," Mallya said. "I know we have to keep developing this car right through the 2017 season; there's no stopping because we're starting from scratch, all the teams are doing the same. We're ready for it, we've planned for it."
As revealed by RACER in January
, the VJM10 is the first car featuring a tub produced by Force India in-house."We always bought [the tub] in," chief operating officer Otmar Szafnauer told RACER last month. "It was laminated and manufactured with a close eye of Force India overlooking the manufacturing process but it was never in-house. This is our first year doing it in-house."
Force India is the third team to physically launch its new car, following on from Sauber and Renault, while Williams released rendered images of its design at the end of last week.
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.





