IPL 2024, CSK vs GT - 3 Things That Went Wrong For GT

GT faced their first defeat of IPL 2024 vs CSK (IPLT20.com)GT faced their first defeat of IPL 2024 vs CSK (IPLT20.com)

Gujarat Titans (GT) faced a crushing 63-run defeat at the hands of Chennai Super Kings (CSK) in Match 7 of the Indian Premier League (IPL) 2024 at the M.A. Chidambaram Stadium in Chennai.

Opting to field first, GT’s strategy backfired as CSK capitalized on the batting-friendly conditions and posted a colossal total of 206/6. Rachin Ravindra and Shivam Dube were particularly destructive, with Ravindra notching 46 off 20 balls and Dube hitting a swift 51 off 23 balls.

In response, GT's batting lineup floundered from the outset, losing captain Shubman Gill early for 8 and never finding momentum, eventually limping to 143/8.

Several tactical blunders and critical choices proved to be the downfall of Gujarat Titans. Here are 3 things that went wrong for GT vs CSK in their second match of IPL 2024.

1. Toss Misjudgment

Shubman Gill's decision to bowl first at Chepauk backfired big time (IPLT20.com)Shubman Gill's decision to bowl first at Chepauk backfired big time (IPLT20.com)

The M.A. Chidambaram Stadium in Chennai stands out for its notorious second-innings slowdown, a fact well-documented in cricketing records. 

Historically, captains winning the toss here have opted to bat first, leveraging the wicket's early-game generosity before it transitions into a sluggish beast, retarding the pace of the ball and complicating stroke-play.

Against the grain of conventional choices, Shubman Gill's decision to field first in their match against CSK was a tactical blunder. 

This oversight offered CSK an open invitation to exploit the sublime batting conditions of the first innings, where the ball's enthusiastic response off the pitch facilitated fluid stroke-play.

The contrast was stark in the second innings, where the wicket's sluggish nature made stroke-making a Herculean task for the visitors. Had GT seized the opportunity to bat first, the scales might have significantly tipped in their favour.


2. Powerplay Pandemonium

GT conceded 69 runs in the powerplay (IPLT20.com)GT conceded 69 runs in the powerplay (IPLT20.com)

The powerplay turned into a spectacle of misfired deliveries and missed opportunities for GT. Azmatullah Omarzai and Umesh Yadav, GT's spearheads with the new ball, found themselves on a slippery slope right from the outset.

Omarzai's promising start quickly turned into a nightmare. Ravindra, seizing the moment, unleashed a torrent of runs, turning the second over into an 11-run feast and maintaining a relentless assault in the overs that followed.

The duo's deviation from the intended lines and lengths transformed the pitch into a batting heaven where CSK reigned supreme, amassing 69 runs in the first six overs.

Rashid Khan's singular success in this phase, claiming Ravindra's wicket, was but a consolation, a lone bright spot in a grim narrative of bowling disarray that set the ball rolling for CSK.

3. Batting Debacle

None of the GT batters could play a substantial knock (IPLT20.com)None of the GT batters could play a substantial knock (IPLT20.com)

In the massive chase that followed, GT's opening salvo crumbled under pressure, with Shubman Gill and Wriddhiman Saha departing early, their contributions truncated at 8 and 21 runs respectively.

The subsequent lineup, each stepping in with the potential to anchor the innings, instead contributed to a domino effect of dismissals. Vijay Shankar, David Miller, Sai Sudharsan, and Azmatullah Omarzai—despite getting off the blocks—failed to convert their starts into impactful innings.

In their haste to accumulate runs, GT's batsmen lost their wickets in quick succession, a strategic misfire that saw them chasing shadows instead of the huge target set by CSK.

The resultant deficit highlighted a distressing day at the office for GT, a day when missed opportunities and tactical misjudgments coalesced into a staggering loss.