Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Aug 04, 2016, 01:09 PM (IST)
Edited: Aug 04, 2016, 01:11 PM (IST)
Cricket Australia are in a fix over two international fixture clashing in 2017. They might have to send separate teams for T20 series against Sri Lanka back home and first Test against India in Bangalore. Border-Gavaskar trophy fixture clashing with T20 series against Sri Lanka is a possibility. According to Australia‘s schedule, they are to play T20 matches against Sri Lanka in February 17, 19 and 22. Cricket Australia’s General Manager of Team Performance Pat Howard is concerned over the possibility. However, teams playing two matches in different countries has happened in the past for Australia as a few players left for New Zealand tour mid-way as simultaneously Australia were playing India in T20 series earlier this year. FULL CRICKET SCORECARD: Sri Lanka vs Australia 2016, 2nd Test at Galle
Pat Howard told Foxsports.com.au, “We are scenario-planning and we strongly don’t anticipate that an Australian team will be playing the same day as another Aussie team. Our caveat is we don’t know when the Indian Tests are. We haven’t got that schedule confirmed. The schedule will continue to be tight and has been for the last couple of years. There have been contingency plans discussed.”
A similar incident resulted in Shane Watson leading the T20 side against India at home and Steven Smith leaving for New Zealand. They will be at BCCI fixtures planner’s mercy as those fixtures will decide whether the fixtures clash or not. “I don’t apologise for putting Test cricket first. We have to give the guys every opportunity to play well in India, which will mean guys will get an opportunity to play T20 international cricket here. The preparation clashes which happened in the past, I can absolutely see happening again,” Holland added.
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.