Sunday, 04 May 2025 21:59

Jaguar TCS Racing eyes second race of the Monaco E-Prix

Written by
Rate this item
(0 votes)

Jaguar TCS Racing is setting its sights on a strong result in the second ABB FIA Formula E Monaco E-Prix tomorrow, after a promising day was curtailed by technical issues that cost the team what was at one stage looking like a very positive result in the Principality.

Round 6 of the 2024/25 ABB FIA Formula E World Championship saw the return of mandatory Pit Boost mid-race charging, and an aggressive strategy from Nick Cassidy in the opening stages saw the Jaguar TCS Racing #37 climb into the podium positions after starting from P19 on the grid.

After taking his first Attack Mode early in the race and his Pit Boost charge before anyone else, Cassidy – who recorded the fastest lap of the race – was on course for a strong haul of points. However, a full course safety car immediately after his Pit Boost and second Attack Mode negated his advantage. This was compounded by an energy setting error leading Nick to believe there were fewer laps left than there were – something he and the team will work to address in the future.

After running in the top-eight during the opening laps, and with two Attack Modes still to deploy, what appears to be an issue with the common supplied RESS unit (Rechargable Energy Storage System) halted Mitch Evans’ attempts for another strong result in Monaco. The team are still investigating the issue. After stopping to reset his car Mitch dropped to last place, the Kiwi was eventually able to continue, but the lengthy setback ensured the Jaguar TCS Racing #9 was too far back to make significant progress.

All eyes are on tomorrow (4 May 2025) for the British team, with the second part of the Monaco E-Prix double-header getting underway at 14:05 BST.

James Barclay, Jaguar TCS Racing Team Principal, said: “A race of two halves today that at times looked likely to yield us a great result but in the end it didn’t pan out that way. Nick started with a strong and ambitious strategy to take his attack early and over-consume on energy so he could take Pit Boost first, this approach saw him climb 13 places to P6 in the opening phase so it was extremely effective. However, Nick’s race was ruined immediately after taking his second Attack Mode as the safety car was deployed and then compounded by an energy setting error. That ultimately resulted in Nick having to run to an extremely aggressive target, having overconsumed for a number of laps, and dropped him down the order in the closing laps.

“Mitch’s efforts in qualifying paid off, pushing him into a top eight starting position. His pace and performance were very strong with him running in a promising P7 and in the points. With our eyes on a top six and possible podium a technical issue related to the RESS unit, sadly halted his race half-way through. He got going again but was outside the points.

“This is racing though and there are many positives to take from the race, not least the pace that was shown in the Jaguar I-TYPE 7 and our progress through the field. The whole team is determined to bounce back tomorrow in the Principality.”

Jaguar TCS Racing driver Mitch Evans, #9: “We started the race solidly in the points with two Attack Mode deployments still to take when I had a powertrain cut on the car. When I got the Jaguar I-TYPE 7 going again we were well down the field and so could not compete for points, but the potential in the car is there so we’re looking to bounce back strongly tomorrow.”

Jaguar TCS Racing driver Nick Cassidy, #37: “Today was a hard day. A technical issue in FP1 put us on the back-foot through qualifying, so we decided on an aggressive strategy for the race. We took an Attack Mode early and intentionally used energy so we could take our Pit Boost early too, and it worked well. But 40-seconds after I had pitted and taken my second attack, there was a Full Course Yellow. That ruined our race - fastest lap is little consolation – but we go again tomorrow.”

Read 60 times

Leave a comment

Make sure you enter all the required information, indicated by an asterisk (*). HTML code is not allowed.