
Ravichandran Ashwin criticizes CSK’s handling of Ayush Mhatre’s injury, calling the on-field decisions shocking.
Veteran spinner Ravichandran Ashwin has strongly criticized Chennai Super Kings over their treatment of young batter Ayush Mhatre during their clash against Sunrisers Hyderabad in the Indian Premier League 2026.
Mhatre, one of the breakout performers this season, walked out to bat with visible knee strapping and soon appeared in discomfort. Despite being used as an Impact Player to limit his workload, the youngster struggled to run between the wickets during the powerplay while chasing a stiff target of 195. His condition worsened as he limped during singles, raising concerns over his fitness.
Ashwin expressed serious doubts about how the situation was managed, stating, “Ayush Mhatre’s injury: I hope he is back, but by the look of it, I fear he will be out for a while,”. He also highlighted that Mhatre had been used as a substitute in recent matches due to ongoing fitness concerns.
“Shocking” On-Field Decisions Leave Experts Stunned
The most controversial moment came when CSK allowed Mhatre to continue batting despite clear signs of distress. Even after physios checked on him, the team chose not to retire him, and he was asked to keep playing and running.
Ashwin did not hold back in his criticism of the decision-making, explaining, “While coming into bat, he came with a strap on his knee. For 2-3 matches, he has been playing as Impact Sub. People are asking ‘Why he is an Impact Player? Is he not a good fielder?’. His injury has been a concern.”
He further questioned the medical judgment, saying, “It couldn’t have been a cramp because he did not field at all. Even if he had gotten cramps even when not fielding, then we have to look at his hydration. Okay, it’s not a cramp. Let’s assume it was an injury. Your physios have come in and checked him. He was limping badly, you are asking him to play another ball and making him run between wickets!”
The situation left even commentators stunned. Ashwin remarked, “I couldn’t understand. Should he have not retired out when he was limping? In this season, Ayush Mhatre has been one of the stars. I don’t understand how they can handle him carelessly. I was shocked.” He added, “Everyone in the commentary box kept their mic on the table and watched what was happening with complete shock. Very, very surprising.”
Mhatre was eventually dismissed for a quick 30 off 17 balls, but his injury overshadowed his performance and raised serious questions about player welfare.
Bigger Concerns Over CSK’s Injury Management System
Ashwin extended his criticism beyond this single incident, suggesting a recurring issue within CSK’s injury management system. He pointed to past examples, including Deepak Chahar, who struggled with injuries during his stint with CSK but later featured consistently for Mumbai Indians.
Highlighting the importance of long-term care, Ashwin said, “I have been saying this for long. CSK have been hit with such injuries season after season. Deepak Chahar has played 3 years for CSK. He played a total of 16 games. But, for Mumbai Indians, he played 14 matches straight. Injury management starts well before a season begins and goes year long.”
Drawing from his own experience with Rajasthan Royals, he added, “When I had a knee injury, Rajasthan Royals monitored me the whole year. Muscle injuries, which happen during the season, can be easily avoided. If every year, someone gets injured, how can you find players? You won’t get them in bazars.”
Following Mhatre’s dismissal, CSK’s innings collapsed from a strong position, eventually falling short by nine runs. The defeat marked another setback in their campaign, which has already been plagued by injuries to key players like MS Dhoni and Khaleel Ahmed.
ALSO READ | Shreyas Iyer Calls Virat Kohli T20 GOAT, Praises His Consistency
Ashwin’s remarks have now intensified the spotlight on CSK’s approach to player fitness and injury management, raising concerns about how teams balance performance with player safety.
This article follows WicketWatcher’s editorial standards. Learn more in our Editorial Policy or report an issue via our Corrections Policy.