MI vs GT | Twitterati and Rohit in splits as Pandya's hesitant shot in the dark proves gamechanging
Fortune favours the brave they say -- no one would agree more than Hardik Pandya after all that unfolded at the Wankhede on Tuesday. The Mumbai Indians skipper seemed to review a decision for the sake of it right at the death, only for his decision to pay dividends and shock the Paltan.
Gujarat Titans were well on-course for victory when rain stopped proceedings for the first time at the 14-over mark in the second innings, with Mumbai Indians trailing the DLS score and staring at a defeat. However, by the time rain Gods relented briefly before making a second appearance when 12 balls were remaining, the tables had completely turned and now it was the hosts that found themselves on the right side of the calculations. While some typical Jasprit Bumrah brilliance had a defining say in circumstances culminating such, it was a Hardik Pandya gamble that ultimately proved to be the difference maker.
Ashwani Kumar came on to bowl his final over of the innings in the 18th over and found himself up against Rashid Khan on the second delivery. The left-arm quick steamed in from over the wicket and fired in a leg-stump yorker to take the Afghan by surprise as the Kookaburra thumped into his leg. The Paltan immediately went up for a loud appeal but the umpire firmly shook his head no, believing the ball to be pitching outside leg. Pandya seemed to be in agreement as feeble discussions of a review brewed but just when the MI skipper seemed to have decided against going upstairs, he made a timid T signal with his hands to opt for the DRS anyway. As it turned out, the white rock had pitched just in line and Rashid had to be on his way, leaving Gujarat in dire straits. The likes of Trent Boult could not believe their luck, apparent through a bright smile and gaping eyes as soon as the ball tracking came up on the big screen, while former skipper Rohit Sharma was caught by the cameras shrieking in ecstacy upon watching the replay himself.
As if Fate had conspired against GT, the rain came hurtling back to force players off at the end of the over, with the wicket practically proving to be the difference between victory and defeat for the visitors.
Gone!
— samson (@samson8943) May 6, 2025
Gone
WICKET! 17.2: Rashid Khan 2(3) lbw Ashwani Kumar, Gujarat Titans 126/6 pic.twitter.com/800HjCp0Sb
— Virat (@virat518) May 6, 2025
Interesting
#MIvsGT @IPL
— Tejas Parekh (@ptejas3) May 6, 2025
I noticed during todays match that Rashid Khan’s LBW out decision didn’t get the usual zoomed-in replay like other decisions. Seems ball was pitching outside leg. It was an important moment, and it felt a bit unclear.
Views on this please.
Why?
Why is pitching not umpires call in Rashid Khan LBW? Is 50% of the ball inside the pitch line ?
— HarishM (@HarishViews) May 6, 2025
Brain dead
Brain dead batting by GT batters and that LBW of Rashid is controversial, that can't pitch in line, seemed outside leg .
— Slog Sweep-189 (@SloggSweep) May 6, 2025
Boom
Ashwin Kumar strikes again! 🎯
— Adarsh Dubey (@AdarshCrkt) May 6, 2025
Rashid Khan trapped LBW — and GT are falling apart under pressure!
Mumbai tightening the noose 😤#MIvsGT #RashidKhan #AshwinKumar #IPL2025 #GTinTrouble #TATAIPL #CricketTwitter pic.twitter.com/EomJ3sc8hp
IDK
idk if Rashid’s LBW was clear outside leg but at least an umpires call man , what fuckery is this ??
— Ishaan Tandel (@TandelIshaan) May 6, 2025
Yes please
#MIvsGT 3rd umpire pls review the lbw with what happened on Rohit Sharma decision the other day. @mipaltan was winning it fair n square, so what was the need? Maybe more loyal than the king. rashid would have not finished the game, so why unnecessary crap. Every MI match really?
— Ajay Sharma (@ajaynvini) May 6, 2025
Brain dead
Brain dead batting by GT batters and that LBW of Rashid is controversial, that can't pitch in line, seemed outside leg .
— Slog Sweep-189 (@SloggSweep) May 6, 2025
Good question
rashid wale lbw ka top view dikhaya tha ki nahi? #MIvGT
— ali (@IndiannMadrista) May 6, 2025
Comments
Leave a comment0 Comments