Hafeez yet to recover from troublesome knee

Batsman almost certain to miss out on training camp which begins from next week


Our Correspondent May 27, 2016
Batsman almost certain to miss out on training camp which begins from next week. PHOTO: AFP

KARACHI: Right-handed opener Mohammad Hafeez is yet to recover from the knee injury that ruled him out of Pakistan’s final two World T20 games against Australia and New Zealand in March.

The batsman is now expected to miss the ‘skill camp’ that begins in Lahore on May 30 for the tour of England.

Despite undergoing treatment under the supervision of PCB’s medical panel for more than two months, the pain in Hafeez’s right knee is yet to subside.

The batsman was given a roadmap by the panel to ensure smooth recovery from his injury but progress so far hasn’t been very encouraging. The player is reportedly suffering from bony edema and muscular pain, which is generally caused by wear and tear in and around the knee.

Since suffering the injury, the batsman has gone through three scans — the third of which was conducted in Lahore yesterday and revealed the extent of the injury.

With the start of the Test series against England still some six weeks away, the batsman is expected to travel abroad for a second opinion in a bid to speed-up his recovery.

Pakistan Cricket Board doctors were hoping that Hafeez would recover without having to undergo surgery but it seems that he might have to go under the knife after all.

Hafeez had a richly rewarding 2015 in the Test format with a tally of 710 runs at an average of 59.16. He capped off the year with a match-winning century in the second innings of the Sharjah Test against England last November; widely hailed by many as the best innings of his 47-Test career.

Published in The Express Tribune, May 27th, 2016.

Like Sports on Facebook, follow @ETribuneSports on Twitter to stay informed and join in the conversation.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ