Prithvi Shaw will miss domestic cricket season for at least three months after picking up a knee injury during his stint in England. This means he will be out for a majority of the domestic season that gets underway with the Irani Cup on 1 October.
Shaw picked up the injury while playing for Northamptonshire against Durham, and scans revealed the injury was a lot worse than initially expected.
The batter first consulted a specialist in London but then returned to the National Cricket Academy (NCA) in Bengaluru for another assessment. At the moment, the medical team is considering options with surgery the last resort.
A Mumbai Cricket Association (MCA) official was quoted as saying by ESPNcricinfo that they would adopt a wait-and-watch approach with Shaw and hope to have him ready for the Ranji Trophy in January. For now, though, it appears he won’t play in the limited-overs competitions beginning with the Syed Mushtaq Ali Trophy on 16 October.
The injury comes at the worst possible time for Shaw just when he was starting to click. He was the highest run-getter in limited overs competitions with 429 runs in four innings, including a record breaking 244 in 153 balls against Somerset.
The 23-year-old was last part of the Indian cricket team squad for the home T20s against New Zealand in February. In the IPL that followed, he had a poor run of form and was dropped at one point. Eventually, he missed the cut for India’s second-string side for Ireland and the Asian Games.
Shaw has confirmed he will return to Northants for the 2024 season, where he’ll feature across formats.
“I’m so excited to be heading back to Northamptonshire next summer,” he had said upon his return from England. “Even though it was over quickly, I really enjoyed my time there. It’s a great club to be a part of and I was welcomed by everyone immediately. I can’t wait to get back. My goal is always to help win games for the team and it was so disappointing to get injured and have to leave early this time.”
from Firstpost Sports Latest News https://ift.tt/0EXqlH4
No comments:
Post a Comment