Gaikwad Blames Challenging Pitch After CSK's Heavy Loss to GT in IPL 2026

Chennai Super Kings captain Ruturaj Gaikwad admitted his team struggled to adapt to a challenging pitch with variable bounce and inconsistent pace. CSK posted 158/7 after losing wickets in clusters, which proved insufficient against Gujarat Titans. Gaikwad anchored the innings with a composed knock but acknowledged that frequent wickets disrupted momentum. GT chased down the target comfortably, handing CSK an eight-wicket defeat at the MA Chidambaram Stadium.

Key Points: CSK vs GT: Gaikwad on Challenging Pitch After 8-Wicket Loss

  • CSK lost to GT by 8 wickets at Chepauk
  • Gaikwad called the pitch challenging with inconsistent bounce
  • CSK posted 158/7 after losing wickets in clusters
  • GT chased down the target comfortably
3 min read

IPL 2026: 'It was a challenging pitch, we couldn't adapt to the conditions,' says Gaikwad after CSK's loss to GT

Ruturaj Gaikwad admits CSK failed to adapt to a tricky pitch with variable bounce after an 8-wicket IPL defeat to Gujarat Titans in Chennai.

"We just couldn't adapt to the conditions. - Ruturaj Gaikwad"

Chennai, April 26

Chennai Super Kings captain Ruturaj Gaikwad admitted that his side struggled to adapt to challenging pitch conditions as they slumped to an eight-wicket defeat against the Gujarat Titans in Indian Premier League 2026 at the MA Chidambaram Stadium in Chennai on Sunday.

Reflecting on the surface, which offered variable bounce and inconsistent pace, Gaikwad highlighted how difficult it was for batters to settle in despite initial plans.

"To be honest, sometimes I hate to assess in that way, but I felt it was challenging. I was holding a bit for the pacers; the pace was inconsistent, and the bounce was up and down. But if we hadn't lost too many wickets, we could've reached 170-180. Not expected to be honest, it's tough to assess the conditions here. In the last three matches, we learned how the game would play out. We had a 60-70% chance in the last two or three games, but we didn't expect it to play like this today. We just couldn't adapt to the conditions," Gaikwad said after the game.

CSK, who eventually posted 158/7, had to recover from early setbacks after losing wickets in clusters. Gaikwad pointed out that the inability to adjust quickly to the surface proved costly, particularly during the Power-play and middle overs when partnerships were crucial.

Elaborating on his communication with the team management during the innings, Gaikwad revealed that even a proactive approach could not overcome the pitch's unpredictability.

"In the first timeout, I told Flem that I was trying to be positive and aggressive. But at times, the ball popped out with an inconsistent bounce. I told him I was trying to adapt, but it wasn't possible. You couldn't judge, and you couldn't expect it to turn out well. We were lethargic and didn't start well, but we needed to do better," Gaikwad said.

Despite the difficulties, the CSK skipper anchored the innings with a composed knock, finishing unbeaten and attempting to steer the side towards a competitive total. However, he acknowledged that wickets at regular intervals disrupted momentum and forced a change in approach.

"I got off to a good start (10 off 6), I thought I would keep the momentum, but then we saw 3 wickets fall while we were trying to build a partnership. Another wicket fell, and I wanted to take my time. For any other pitch, I might've rotated the strike better. Once I got hit, I just thought I would take my chances and get some momentum back," he said.

Gaikwad also touched upon the tactical decisions taken during the innings, including the use of the Impact Player, suggesting that the loss of wickets forced the team's hand, as he said, "We were batting really well; if we hadn't lost two quick wickets, Mukesh would've come in the second innings. But we lost two wickets quickly, which is why we opted for an impact player."

Chennai's total ultimately proved insufficient against a clinical Gujarat Titans batting unit, who chased down the target with ease.

- IANS

Share this article:

Reader Comments

P
Priya S
As a die-hard CSK fan, I appreciate Ruturaj's honesty. But honestly, 158 on a tricky pitch at Chepauk is not that bad. The problem is we keep losing early wickets in powerplay. Need to sort out opening combination—Gaikwad and Conway are too similar. 🧡
J
James A
Interesting perspective. From a neutral fan in the US, it seems like CSK's over-reliance on home conditions is backfiring. Teams like GT are better prepared for variable surfaces. Gaikwad needs to adapt his tactics if CSK wants another title.
V
Varun X
Bhai, it's not just the pitch. Our bowling looked toothless in death overs. Tushar Deshpande is leaking too many runs. And where was Deepak Chahar's swing? We miss Bravo's experience. 😔👎
M
Megan H
Watching from Australia, I think CSK fans are being too harsh. Gaikwad is right—sometimes conditions surprise everyone. 158 was competitive, and GT just played smarter cricket. The difference was Gill's maturity in chase. Good lesson for Gaikwad as captain.
K
Kavya N
I'm not buying the pitch excuse entirely. CSK has played 8 games at Chepauk this season—they should know the surface by now. The real issue is shot selection. Rayudu and Moeen threw their wickets away. If you're struggling on a tricky pitch, bat sensibly. 🏏

We welcome thoughtful discussions from our readers. Please keep comments respectful and on-topic.

Leave a Comment

Minimum 50 characters 0/50