
PWC: Update on Jorge De La Torre
Aston Martin Racing provided a statement Friday on driver Jorge De La Torre, who along with Andrew Palmer was involved in a heavy accident in the warm-up lap for the Pirelli World Challenge race at Lime Rock Park:
"Aston Martin Racing would like to report the updated status of injured driver Jorge De La Torre following an incident last Saturday at Lime Rock Park in Lakeville, Conn., involving the V12 Vantage GT3 of De La Torre and Bentley driver Andrew Palmer.
"Jorge sustained several fractures which were repaired in surgery on Tuesday at Hartford Hospital. He currently remains in hospital where he has demonstrated strength and good spirits this week. Jorge plans to begin rehabilitation as soon as he is released.
"The medical team at Hartford Hospital are monitoring Jorge's progress and will determine when his release will be granted.
"Jorge and Aston Martin Racing want to thank everyone for their thoughts and prayers throughout this trying situation. Our thoughts remain with Jorge, Andrew and the Bentley team.
"Any further information will be available in due course."
Bentley Motorsport's May 28 update on Palmer stated that the driver suffered a head injury and was expected to remain in the hospital, closely monitored after treatment by specialists. There is no further update on his condition.
A spokesman for the track told WFSB-TV the day of the accident that Palmer and De La Torre were were taken to Sharon Hospital following the accident, where there conditions were stabilized, before being airlifted to Hartford.
According to reports, Palmer's No. 87 Bentley Team Absolute Bentley Continental GT3 collided with De la Torre's No. 4 Aston Martin V12 Vantage GT3 when the latter had come to a stop in the Turn 1 runoff area. Palmer's car reportedly was launched over the Aston Martin upon impact and flew over multiple tire barriers.
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.





