English BlogsFeaturedIPL 2019

3 massive mistakes that costed the Match to the Mumbai Indians

A new look Delhi Capitals side took on three-time IPL Champions Mumbai Indian’s at the Wankhede Stadium in the third match of the season. Rohit Sharma won the toss and just as most captains would do, he opted to chase. Mumbai got off to a great start as Mitch McClenaghan snared Prithvi Shaw and Delhi skipper Shreyas Iyer inside the first four overs. Dhawan and Ingram steadied the ship, before Pant, who walked in at 5, smoked a sensational 27-ball 78 to power the Capitals to a solid 213 for 6.

Chasing in excess of 10 RPO, it is imperative to start off with a bang. Unfortunately for the home side, DC pegged them back with as many as three wickets in the powerplay overs. Kieron Pollard, Yuvraj Singh, and Krunal Pandya did manage to score some runs but they were always behind the required run rate. In the end, the Capitals registered a facile win to get their campaign off and running.

Here are three mistakes that cost Mumbai Indians the match.


Not picking the in-form Ishan Kishan

The Wankhede has always been a high scoring venue and with Ishan Kishan in imperious form, it was a shocker to see the Jharkhand lad warm the bench. Kishan, who played in the Syed Mushtaq Ali Trophy, scored two hundred’s for his state side Jharkhand. Everyone did imagine that Kishan would certainly walk in into the Mumbai Indians playing XI, but is wasn’t to be. With Quinton De Kock taking up the gloves and Suryakumar Yadav came out to bat at number three. But we have seen teams play a keeper as a pure batter, and Mumbai certainly missed the pocket dynamite dearly. Perhaps after the loss, Rohit Sharma will definitely feel he missed a trick by not playing Ishan Kishan. It also should be said that if Ishan Kishan had played, Yuvraj Singh might have missed out. After Yuvi’s gritty half century, Mumbai fans probably wouldn’t criticize the team selection made by the team management.

Tossing the bowl to Rasikh Salam in the penultimate over

The stage was set for Delhi Capitals to finish off the innings with a flourish. Rishab Pant was once again at his lethal best and looked menacing. Mumbai, on the other hand, needed a good penultimate over. With Rohit already deciding to give his best bowler Bumrah the last over, 17-year-old Rasikh Salam was given the ball. Until then, Salam had bowled reasonably well to concede only 21 runs in his three overs on his debut.

Not maximizing the powerplay overs

When you are chasing a target of 215, it is important you maximize the first six overs. For Mumbai, it did not happen as Ishant Sharma struck twice and a silly run-out pushed the home side back. Losing three key wickets very early on, especially in a huge chase is a crime in T20 cricket. Rohit Sharma finally opened the innings along with De Kock and the Mumbai locals hoped both would go hammer and tongs. But unfortunately for the home crowd, the Delhi Capitals had other ideas. Once Mumbai Indians lost three wickets inside six overs, the game was almost lost. Yuvraj Singh, Krunal Pandya, and Kieron Pollard chipped in with valuable contributions, but it was never going to be enough as the run rate kept creeping up. Furthermore, the three-time champions lost wickets at regular wickets throughout the course of the chase and eventually fell short by 37 runs.

Tags

Related Articles

Leave a Reply

avatar
Back to top button