Advertisement
Advertisement
Trouble for Porsche GT, DragonSpeed in LM H14
By alley - Jun 17, 2017, 11:06 PM ET

Trouble for Porsche GT, DragonSpeed in LM H14

The start of the hour saw terminal trouble for Michael Christensen in the already delayed No. 92 Porsche 911 RSR. He got it wrong into the Ford Chicane at the end of his 180th lap, hitting the curbs at speed, spinning and impacting the wall on the outside. The car was forced to retire.

As the track went back to full green-flag running after the Slow Zone brought out to assist the recovery of the Porsche, Oliver Jarvis took advantage of the opportunity to get onto terms with and pass LMP2 leader and second-place overall David Heinemeier Hansson, the No. 38 Jackie Chan DC Racing ORECA taking the slot from the No. 13 Vaillante Rebellion ORECA.

Kazuki Nakajima brought the sole surviving No. 8 Toyota back into the overall to 30th as its fightback continued. Unlike the No. 2 Porsche though, by then up to 14th, the TS050 cannot make up the time and positions needed without significant dramas ahead.

Darren Turner (No. 97 Aston Martin), meanwhile, was fighting hard with Alessandro Pier Guidi (No. 51 AF Corse Ferrari 488) over second in GTE Pro, the pair 20 seconds back from the leading No. 95 Aston Martin.

The final five minutes of the hour saw Ben Hanley running slowly, and eventually pitting to be wheeled immediately back in to the garage, this after the No. 21 DragonSpeed ORECA was seen blowing smoke in the run down to the Forest Esses. The car pitted after a slow lap and was pushed straight into the garage.

#LeMans24result after 14 hours.#WECpic.twitter.com/zMSlY54fF6— FIA WEC (@FIAWEC)June 18, 2017

//platform.twitter.com/widgets.js

RACER.com coverage of the 24 Hours of Le Mans is presented by

Lone Star Le Mans

, a six-hour sprint deep in the heart of Texas:

September 15-16 at COTA

.

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.