Thu. Oct 21st, 2021

Haas F1 driver Romain Grosjean is continuing his recovery from the injuries he sustained in his terrifying Bahrain GP crash and is expected to be released from hospital on Tuesday. Grosjean miraculously walked away from a sickening, 137mph head-on collision with the barriers on the opening lap of Sunday’s race in Bahrain.

The Frenchman’s Haas car sliced through the barriers, tore in half and burst into flames. Grosjean was in his burning car for nearly 30 seconds before he managed to extricate himself from the wreckage with the aid of the on-site medical team.

Grosjean was taken to hospital in Manama after sustaining burns to his hands and ankles. There were also fears he had suffered broken ribs in the accident, but X-rays showed there were no fractures.

In an update issued by Haas on Monday, the team confirmed that treatment on the burns to the back of both Grosjean’s hands is “going well.”

Haas team principal Guenther Steiner visited Grosjean in hospital on Monday morning and his injuries and recovery will continue to be assessed over the coming days and it is anticipated he will be discharged from hospital on Tuesday 1 December.

In an update from his hospital bed on Sunday night, Grosjean confirmed he was OK and paid tribute to the Halo head protection device which he believes ultimately saved his life.

Haas’ intention is to run Grosjean at next weekend’s Sakhir Grand Prix in Bahrain providing he is fit and willing to drive.

“We’ve always got a plan in place but at the moment my plan is if he’s OK to get back in there to race in Bahrain next week [he can]. But we have to wait,” Steiner told the media on Sunday evening.

“I want to speak first to Romain before speculating whoever goes in there if he cannot drive,” he added.

“So, it will be only in the next few days when we get from the doctors the verdict of how bad the injuries are then we decide what we’re doing.

“At the moment for me Romain is driving.”

Leave a Reply

Your email address will not be published. Required fields are marked *

error

Enjoy this blog? Please spread the word :)