Jaguar R3

The Jaguar R3 is a Formula One racing car with which Jaguar Racing competed in the 2002 Formula One season. The car was launched on 4 January 2002. It was driven by Eddie Irvine and Pedro de la Rosa, both retained from 2001.

Jaguar R3
CategoryFormula One
ConstructorJaguar
Designer(s)Steve Nichols (Technical Director)
John Russell (Chief Designer)
Darren Davies (Head of Aerodynamics)
PredecessorR2
SuccessorR4
Technical specifications
ChassisCarbon-fibre monocoque
EngineCosworth CR3 V10 (72°) naturally aspirated
TransmissionJaguar 7-speed longitudinal semi-automatic sequential
FuelBP
LubricantsCastrol
TyresMichelin
Competition history
Notable entrantsJaguar Racing
Notable drivers16. Eddie Irvine
17. Pedro de la Rosa
Debut2002 Australian Grand Prix
Last event2002 Japanese Grand Prix
RacesWinsPodiumsPolesF.Laps
170100
Constructors' Championships0
Drivers' Championships0

After the disappointing past two seasons, 2002 was even worse for Jaguar. The team admitted to making a lot of mistakes especially in the wind tunnel, as its calculations were wrong. After an impressive fourth place at the attritional Australian GP, the car's poor reliability and lack of horsepower began to show and the team slipped down the rankings; however, towards the end of the season updates were brought in and the car began to improve, culminating in Irvine scoring the team's final podium finish at Monza.

The team finished 7th in the Constructors' Championship, with eight points, all scored by Irvine.

Jaguar R3 which competed in the 2002 season driven by Eddie Irvine
The Donington Collection's Eddie Irvine R3 from 2002

Sponsors

Complete Formula One results

(key)

Year Team Engine Tyres Drivers 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Points WCC
2002 Jaguar Cosworth V10 M AUS MAL BRA SMR ESP AUT MON CAN EUR GBR FRA GER HUN BEL ITA USA JPN 8 7th
Eddie Irvine 4 Ret 7 Ret Ret Ret 9 Ret Ret Ret Ret Ret Ret 6 3 10 9
Pedro de la Rosa 8 10 8 Ret Ret Ret 10 Ret 11 11 9 Ret 13 Ret Ret Ret Ret


gollark: While it is capable™ of effectively setting `innerHTML` internally, this would make the links not work properly.
gollark: My application™ is a single-page app™ and the UI™ renders to virtual DOM™.
gollark: Based on my extremely unscientific benchmarks, markdown-it would be about twice as fast, but it's not really as customizable, doesn't produce a parse tree I can use for stuff, and produces HTML directly, which is not ideal.
gollark: I disabled an extension for *tab counting* which was apparently insanely inefficient and got a 150ms saving, though.
gollark: Mayhapß™ I should just use a background thread thing (browsers can totally™ do that) for markdown handling.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.