James Anderson to miss opening Test against India

England’s all-time leading Test wicket-taker has not played since August due to a shoulder injury


Afp October 19, 2016
James Anderson. PHOTO: AFP

CHITTAGONG: England’s record-breaking bowler James Anderson, who has already been ruled out of the current tour of Bangladesh, will miss next month’s first Test against India, captain Alastair Cook said on Wednesday.

“I don’t think he’ll be there for the start. He might be ready to do some training, but he won’t be ready for the first Test match in India,” Cook told reporters.

“I don’t know what’s happening -- they will be making some decisions over the next seven days or so. I spoke to him last night and he is training well and in good shape physically.”

Confident of returning against India: Anderson

Anderson, England’s all-time leading Test wicket-taker, has not played since the fourth Test against Pakistan in August because of a shoulder injury. He has not travelled to Bangladesh, where England on Thursday begin a two-Test series in Chittagong.

Asked whether he was optimistic the 34-year-old would play some part in the five-Test India series, Cook refused to give any guarantees and said a decision on when he would travel had still to be made.

"You should probably speak to the medical team and Jimmy on that. He hasn't yet bowled since, and that has been the problem in the past," Cook told reporters in Chittagong. "He's making some really good strides and we'll know more later on."

Injured Anderson to miss Bangladesh tour

Anderson's continued absence would be a significant blow to England's chances in India, who are the world's number one Test side and have a formidable home record.

England are expected to field three spinners in the Chittagong Test, with the 39-year-old Gareth Batty expected to be selected after more than a decade in the international wilderness.

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