IPL 2024, SRH vs MI - 3 Things That Went Wrong For MI

Tim David couldn't showcase his might vs SRH on Wednesday (AP)Tim David couldn't showcase his might vs SRH on Wednesday (AP)

Sunrisers Hyderabad (SRH) outclassed Mumbai Indians (MI) by 31 runs in a record-shattering encounter at the Rajiv Gandhi International Stadium on Wednesday.

The Match 8 of the Indian Premier League (IPL 2024) witnessed an impeccable display of explosive batting that will be etched in the tournament’s history as SRH set a new benchmark with the highest team total ever, amassing a gargantuan 277/3.

The onslaught was spearheaded by Travis Head, whose debut innings for SRH was nothing short of fireworks, blazing to 62 off 24 balls. He found a formidable ally in Abhishek Sharma, who matched the tempo with a blistering 63 off 23 balls. 

Heinrich Klaasen's unbeaten 80 off 34 balls and Aiden Markram's solid 42 off 28 ensured SRH left no stone unturned in their quest for supremacy.

Undeterred by the monumental target, MI embarked on a gallant chase, keeping the spectators on the edge of their seats. Tilak Varma's scintillating 64 off 34 balls and Tim David's rapid 42 off 22 kept the dream alive. However, despite the spirited endeavour, MI's innings concluded at 246/5.

The game was a classic case of "so near yet so far" for MI. Despite the glittering array of cameos, the team's efforts were eclipsed by SRH's earlier batting blitz.

There were several factors that resulted in Mumbai Indians’ second successive defeat. Here’s are three things that went wrong for MI vs SRH in their second game of IPL 2024.


1. Captaincy Blunders

Hardik Pandya made several questionable decsions in the SRH vs MI match (IPLT20.com)Hardik Pandya made several questionable decsions in the SRH vs MI match (IPLT20.com)

In a display that oscillated between the sublime and the slipshod, Mumbai Indians’ captain Hardik Pandya's decisions raised eyebrows and questions in equal measure.

At the outset, winning the toss yet opting to field on a track manifestly favourable to batsmen set the stage for what was to unravel. This dubious inception was exacerbated by Hardik’s perplexing allocation of the new ball.

Opting to introduce Kwena Maphaka, a debutant, into the high-pressure environment of the IPL while holding back Jasprit Bumrah, a bowler of proven mettle, was a gamble that did not pay off.

Hardik's own over (2nd), leaking 11 runs, and then witnessing Maphaka getting hammered for 22 in the next, laid the groundwork for SRH's record-setting total.


2. Tim David’s Costly Spill

Tim David dropped Travis Head on 5 (Twitter)Tim David dropped Travis Head on 5 (Twitter)

The gravity of fielding lapses in cricket can never be understated, a point highlighted when Tim David dropped what seemed like a regulation catch off Hardik’s bowling.

Travis Head made full use of the lifeline, and unleashed fury on the field, plundering Maphaka for two sixes and a pair of boundaries in a single over, following it up by taking Hardik to task with three consecutive boundaries in his next over.

Tim David's dropped catch was not merely an incident but a crucial moment that swung momentum decisively in SRH's favour, propelling Head and subsequently Abhishek Sharma to dismantle MI's bowling attack with impunity.

The cost of this error was monumental, igniting SRH's batting fireworks and ultimately setting a colossal target that would test the mettle of any chasing team.


3. Misfiring Hardik Pandya

Hardik Pandya had an abysmal day in the field (IPLT20.com)Hardik Pandya had an abysmal day in the field (IPLT20.com)

The focus invariably harsh, turned to Hardik himself, who had a day to forget both with the bat and the ball. His bowling figures showed his struggles, bleeding 46 runs across four overs for a solitary wicket.

The captain's woes compounded while batting as well, scraping together 24 runs off 20 deliveries in a chase that demanded firework-like explosiveness.

Excluding a solitary four and six, his strike rate plummeted to an underwhelming 120, a metric painfully inadequate for the high-octane finish MI desperately needed.

During the crucial middle overs, from the 13th to the 18th, Hardik, alongside Tim David, managed only 59 runs at a point when the required rate was soaring beyond 15 runs per over.

This phase of play was the reason behind MI's faltering chase, with Hardik unable to break the shackles, culminating in a chase that fizzled out 31 runs shy of its target.