Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Jan 14, 2013, 12:30 PM (IST)
Edited: Jan 14, 2013, 12:30 PM (IST)
Head selector John Inverarity (right) said that Brad Haddin would be out a couple of weeks © Getty Images
Sydney: Jan 14, 2013
Australia wicketkeeper Brad Haddin is likely to miss the match between the Prime Minister’s XI and the West Indies at the Manuka Oval on January 29 due to a hamstring injury. The match is recently retired Australian batsman Ricky Ponting‘s farewell game.
Haddin injured his hamstring while playing for Australia in the second One-Day International (ODI) against Sri Lanka at the Adelaide Oval on Sunday.
However, John Inverarity, head selector of Cricket Australia, told Sydney Morning Herald that he was hopeful Haddin would miss only “a couple of weeks”.
“We don’t know exactly [the extent of Haddin’s injury], I saw Brad last night and again at the airport this morning,” Inverarity said.
“We’re hoping it’s not too serious, we hope it’s a couple of weeks and nothing more than that.
Talking of which keeper(s) will make Australia’s tour of India next month, Inverarity said, “There’s a real chance we’ll take two wicketkeepers to India and/or to England and, as I’ve said before, the two best keeper-batsmen in the country are he [Haddin] and Matthew Wade.”
Inverarity added that Australia had plenty of options to cover for Haddin, including South Australia’s Tim Ludeman and Tasmania’s Tim Paine.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.