Mumbai Indians v Daredevils, IPL 2014, Mumbai May 23, 2014

Hussey, bowlers keep Mumbai alive


Mumbai Indians 173 (Hussey 56, Tahir 3-37) beat Delhi Daredevils 158 for 4 (Duminy 45*) by 15 runs
Scorecard and ball-by-ball details

Play 05:20
Guha: Mumbai Indians won despite being patchy

Mumbai Indians lost their last eight wickets for 33 runs, and were bowled out with three balls left to play. As Rohit Sharma watched his team collapse, the expression on his face went from incredulous to annoyed to angry. This, after all, was a must-win game for Mumbai if they wanted to retain any chance of qualifying for the playoffs.

Eight wickets for 33 runs. And yet, Mumbai won, and comfortably at that. They did just about enough either side of the collapse to keep their hopes alive.

Michael Hussey got them off to a flier with a 33-ball 56, and Mumbai had been looking at 200 before their innings came crashing down. Chasing 174, Delhi Daredevils never got any real momentum going. JP Duminy and Manoj Tiwary kept them alive with an 85-run fourth-wicket partnership, but 32 from the last two overs proved beyond their reach. Marchant de Lange and Jasprit Bumhah bowled two excellent overs to close out a 15-run win for Mumbai.

Sent in to bat, Mumbai profited from some ordinary bowling at the start to run away to 65 for no loss at the end of the Powerplay and 100 for 1 after 10 overs. Siddarth Kaul and Jaydev Unadkat kept drifting down leg to Hussey, and he kept playing pick-up shots and pulls into the gaps on the leg-side boundary.

Imran Tahir's introduction did nothing to slow Mumbai down. On the contrary, it brought Lendl Simmons into the game. He took three fours off the over, two with his favourite square cut - off back foot and then front foot - to capitalise on the width offered by the legspinner.

The dismissal of Simmons brought Rohit Sharma in, and he was soon capitalising on some width of his own - this time offered by JP Duminy, who bowled short and wide despite having only deep cover on the off-side boundary. Mumbai were going at close to 10 an over, and even the first few wickets didn't slow them down. Kieron Pollard hit the first ball he faced for six. Aditya Tare caressed the first two balls he faced to the off-side boundary.

The slide really began when Ambati Rayudu picked out long-off off Shahbaz Nadeem, and soon batsmen were holing out and running themselves out all over the place. Mumbai didn't even play out their full 20 overs. On this pitch, a target of 174 didn't look like all that much.

But Daredevils, as they have so often done this season, batted pretty well without ever giving their opponents a real scare. They got off the blocks quickly enough, with Kevin Pietersen striking three fours off de Lange in the second over of the chase, and were 43 for no loss after five overs. The next five overs, however, brought them only 19 runs and cost them three wickets.

Shreyas Gopal had M Vijay stumped with an enticingly loopy legbreak that the batsman flailed at and missed, but the bowlers didn't have to do too much to earn the next two wickets. Pietersen was bowled trying to switch-hit Harbhajan; Dinesh Karthik was bowled trying to scoop a full, straight ball from de Lange.

Daredevils were left needing 112 from their last 10 overs. They stayed in the hunt, with Duminy clinical in targeting the midwicket area, and Tiwary getting into good positions against the spinners to slog-sweep or hit inside out. When de Lange started the penultimate over by giving away two free runs with a chest-high full toss to Duminy, it looked like Mumbai could come to regret their batting meltdown.

But de Lange quickly recalibrated his radar, and found the blockhole three times in the next six balls. He also dismissed Tiwary, and 30 off 12 balls became 25 off six. There was still an outside chance, but Jasprit Bumrah quickly snuffed that out with some yorkers of his own. Mumbai hadn't been at their best, and had put themselves in some extremely sticky spots, but they were still breathing, just about, at the end of it.

Karthik Krishnaswamy is a senior sub-editor at ESPNcricinfo

Comments have now been closed for this article

  • Dummy4 on May 24, 2014, 13:23 GMT

    SRH will never progress.. only MI or RR can go..whereas RR has higher chances of qualifying as they only need to win or lose by a small margin whereas MI has a tough task ahead. Let's analyze the same.

    A. Scenario for MI if they bat second: They need to restrict RR to 165 (20 ovs) and then chase down the target in 14.1 ovs.

    B. Scenario for MI if they bat first: They need to score 200 (20 ovs) and restrict RR to 157 in 20 ovs.

    I would give a higher if they chase the target, otherwise RR would qualify easily as MI don't have a bowling attack to skittle any opposition.

    Still, in any case I would be routing for MI. Love MI. Go MI. Cheers...!!!

  • Android on May 24, 2014, 5:07 GMT

    if mi qualify for semis they will play their first qualifier in mumbai and another one in wankhede if they beat their opposition badly then they will play in bengluru the flattest track in the world .

  • Steve on May 24, 2014, 3:23 GMT

    Have De Kock and Neesham gone home? DD need to give these young guys another shot. 8 losses in a row, can't do any worse!!!

  • na on May 23, 2014, 20:20 GMT

    If MI bat second, they need to chase down their target in about 14-15 overs(exact number will depend on the target) to qualify for the playoffs.

  • Garry on May 23, 2014, 17:33 GMT

    IS KP man enough to say "look I am not a good captain, give someone else a go" or is his ego to big?

  • Android on May 23, 2014, 16:33 GMT

    @Greatest Game Agree with your comment, well thought out.

    Also when you have someone like Ross Taylor in your squad you don't bench him. Its all like Pune again. Play him at no. 3 or 4 to get the best out of him but poor management plays hin at no. 6 and 7.

  • David on May 23, 2014, 15:04 GMT

    After the match, Kevin Pietersen said "The frustrating thing is that we can get so close but can't get over the finish line ... when we keep losing and get so close, we form bad habits."

    KP, you get close & lose, because you mismanage your best batsman, keeping him down the order, & bringing him in too late. JP scored the league's 5th most runs this season, not-out in 6 of 13 matches. 46% of his chances to make MORE have been lost. DD gets close close & loses, & yet wastes 46% of Duminy's full run-making opportunities! Does this not add up? If your best batsman is denied the maximum possible scoring chances, do you really expect to win?

    Today, Vijay & Karthik made15 off 25 balls - SR 60!. At SR 155.17, JP would have scored 39 off those 25 balls. That's 24 more runs, & 8 MORE than Delhi needed to win!

    Mumbai won by 15 - 1 more than Vijay scored in his LAST 3 GAMES. JP scored 70, but Vijay gets the maximum scoring chances, & JP sits & waits!

    KP's Bad Habit is called captaincy.

  • Dummy4 on May 23, 2014, 15:03 GMT

    Did the 1 day shot (switch hit ) by KP on 44 send the wron message to the other batsmen? Was it required at that time?

  • Francois on May 23, 2014, 13:58 GMT

    Great to see De Lange getting a change.

  • David on May 23, 2014, 13:57 GMT

    Interesting to note that after 5 matches, Imran Tahir is now tied for the most wickets for Delhi: Nadeem (10 matches,) Unadkat (8 matches) and Tahir have all taken 8 wickets, but Tahir's ave of 17 is half that of Nadeem (35.87) and Unadkat (33.97.) Tahir's strike rate of 12.7 is the leagues best for of all who played more than 2 matches.

    Tahir is taking wickets at just a fraction under the same rate-per-match as the leagues leading wicket takers, Sunil Narine & Bhuvi Kumar. Delhi might be in a much better position if they had been smart enough to bring him at the beginning of the season.

    Although Tahir was the leading wicket taker in the World T20, IPL teams failed to pay attention to the fact that he is a very effective T20 bowler, especially on sub-continent pitches. Kirsten should have brought him in as soon as Coulter Nile broke down. But, as they say, you snooze, you lose!

  • No featured comments at the moment.