Advertisement
Advertisement
MOTOGP: Injured Rabat will try to race at Barcelona
By alley - May 31, 2016, 3:31 AM ET

MOTOGP: Injured Rabat will try to race at Barcelona

Marc VDS Honda rider Tito Rabat will attempt to race in MotoGP's Catalan Grand Prix this weekend, two weeks after fracturing his collarbone in Italy.

The 2014 Moto2 champion's tough initiation to MotoGP continued when he crashed in the third practice session at Mugello, suffering a fracture-dislocation of the sternoclavicular joint in his left shoulder. He underwent surgery in Barcelona last week and will have to pass a fitness test on Thursday before practice starts on Friday.

"Firstly, I want to say a big thanks to all the medical team and circuit staff at Mugello and Marc VDS for all the attention I received after my crash," Rabat said. "Their quick reaction was very important in giving me a chance to ride in my home race this weekend.

"The operation in Barcelona last week went very well and Doctors [Xavier] Mir and [Victor] Marlet as always did a great job.

"I have been fully concentrated on recovering as well as I possibly can, and I will be giving my all to be on track in my home grand prix. The target is to be as close to full strength as I can be and work closely with my team and Honda to try and make another step.

"I felt we'd made another small step before my crash in Mugello and that was good. I will try to finish the race and improve my feeling with the bike. If we can do that I think it will be a successful weekend."

Team principal Michael Bartholemy acknowledged that, "Sure, [Rabat] won't be fully fit, but he should be able to continue to improve his understanding of the bike despite the injury."

The other rider injured at Mugello, Loris Baz, has been ruled out, with Ducati tester Michele Pirro to ride his satellite Avintia entry.

 

Originally on Autosport.com

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.