
Colin McMaster/Getty Images
LM24 Hour 5: Ferrari 1-2-3
Ferrari 499Ps run 1-2-3 after five hours of the 24 Hours of Le Mans, after the No. 51 factory Ferrari AF Corse car of Antonio Giovinazzi and the No. 83 quasi-privateer car of Robert Kubica each fought their way past the No. 6 Penske Porsche 963 of Laurens Vanthoor.
It's still Ferrari 1-2-3 at the front but after driver changes, the leading No. 50 is now driven by Miguel Molina, the No. 51 now in the hands of Alessandro Pier Guidi, and the No. 83 controlled by Ye Yifei, all in for their first stints. The No. 83 did have a reported brake issue, and also had to take five extra seconds on a pit stop for cutting the second Mulsanne Chicane.
Matt Campbell is now in the No. 6 Porsche and in middle of a battle for fourth, behind the No. 20 Team WRT BMW M Hybrid V8 of Raffaele Marciello, and ahead of the No. 8 Toyota Gazoo Racing GR010 HYBRID of Ryo Hirakawa.
Then it's the No. 15 WRT BMW, the No. 38 Cadillac Hertz Team JOTA V-Series.R, No. 4 Penske Porsche 963, and the No. 311 Whelen Cadillac rounding out the top 10.
More Le Mans/WEC
At the top of the hour it's the No. 48 VDS Panis Racing ORECA 07-Gibson that leads LMP2 with Oliver Gray aboard, some distance ahead of Reshad de Gerus' No. 9 Iron Lynx-Proton ORECA in second.
The No. 43 Inter Europol Competition car had been cruising with Nick Yelloly in for his first stint but he's since pitted and dropped to third after a long pit stop. Jakub Smiechowski had reported a gear selection issue during his stint.
In LMGT3, Valentino Rossi continues to lead firmly in the No. 46 Team WRT BMW M4 LMGT3 EVO. Francois Heriau is back in the second-place No. 21 Vista AF Corse Ferrari 296 LMGT3, trying to clear more of his Bronze driver time.
Riccardo Pera is now aboard the No. 92 Manthey 1st Phorm Porsche 911 LMGT3 R, running third.
R.J. O'Connell
Read R.J. O'Connell's articles
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.





