IPL 2026: Pandya Blames Early Wickets as MI Collapse to 104 vs CSK

Share:
Audio Loading voice…
IPL 2026: Pandya Blames Early Wickets as MI Collapse to 104 vs CSK

Synopsis

Mumbai Indians collapsed to 104 all out chasing 208 against CSK at Wankhede, suffering a humiliating 103-run defeat in IPL 2026. Captain Hardik Pandya blamed early Power-play wickets, refusing to fault the pitch. Sanju Samson's unbeaten 101 and Akeal Hosein's four-wicket haul were the difference. MI now sit 8th with just 4 points from 7 games.

Key Takeaways

Mumbai Indians were bowled out for just 104 chasing 208 against CSK in Match 33 of IPL 2026 at Wankhede Stadium on April 23 , losing by 103 runs .
Captain Hardik Pandya blamed early Power-play wicket losses for derailing the chase, saying MI "could not cope after that." Sanju Samson scored a brilliant unbeaten 101 to power CSK to 207/6 , while left-arm spinner Akeal Hosein took 4 wickets to dismantle MI's batting.
Pandya explicitly refused to blame pitch conditions, stating both teams played on "the same track, the same soil." Mumbai Indians have slipped to 8th position on the IPL 2026 points table with just 4 points from 7 matches .
MI's next match is against Sunrisers Hyderabad (SRH) on April 29 , a must-improve fixture for their playoff ambitions.

Mumbai Indians (MI) suffered one of their most humiliating defeats of the IPL 2026 season on Thursday, April 23, crumbling to just 104 all out while chasing 208 against Chennai Super Kings (CSK) in Match 33 at the Wankhede Stadium, Mumbai. Skipper Hardik Pandya squarely attributed the collapse to losing early wickets in the Power-play, admitting his side never recovered momentum throughout the chase. The crushing 103-run defeat has pushed MI further down the standings, raising serious concerns about their playoff prospects.

Power-Play Collapse Seals MI's Fate

Hardik Pandya was candid in his post-match assessment, pointing to the Power-play phase as the critical turning point. "I think that in the Power-play, losing that early wicket is always going to be tricky. You are always chasing the game, and we could not cope after that," the MI captain said after the match.

Chasing a daunting 208-run target, the Mumbai Indians never found their footing and were bowled out for a paltry 104 in 19 overs — less than half the target. The batting unit fell apart systematically, with no batter managing to anchor the innings or build a meaningful partnership.

The collapse is particularly alarming given that Wankhede Stadium has historically been a high-scoring venue and is considered MI's home fortress. Losing at home by such a wide margin signals deeper structural problems within the squad's batting unit.

Sanju Samson's Masterclass Powers CSK to 207

The foundation of CSK's imposing total was laid by Sanju Samson, who played a breathtaking unbeaten 101 to anchor the innings. His century, supported by handy contributions from the CSK middle order, helped the visitors post 207/6 in their allotted 20 overs.

Pandya acknowledged Samson's brilliance without making excuses. "Yes, I think even our spinners bowled pretty well. It's just that Sanju played an outstanding knock. At the same point in time, their batters kept coming and kind of chipping in and got them to a decent total — more than a decent total on that track," he said.

Samson's knock was his first IPL century for CSK and came at a crucial juncture, demonstrating the kind of match-defining individual brilliance that MI's batting lineup conspicuously lacked in response.

Hosein and Noor Ahmad Dismantle MI's Batting Order

Left-arm spinner Akeal Hosein was the standout performer with the ball, claiming a devastating four-wicket haul to rip through the Mumbai Indians batting lineup. Noor Ahmad complemented him with crucial breakthroughs, ensuring MI never built any meaningful resistance.

The performance of CSK's spinners on the Wankhede surface was a tactical masterstroke, exploiting whatever turn was available and keeping MI's powerful batting lineup — which includes the likes of Rohit Sharma and Tilak Varma — firmly under pressure throughout the chase.

The fact that MI's own spinners, by Pandya's admission, also bowled reasonably well, underscores that the pitch was not the issue — it was purely a batting failure under pressure.

Pandya Refuses to Blame Pitch, Vows Improvement

Pandya was notably firm in refusing to use pitch conditions as an excuse, a stance that reflects a degree of accountability rarely seen in post-match press conferences. "I would not say that. I'm not someone who would like to say that. They batted well; they scored 207. It was the same track, it was the same soil. We should have just batted well," he stated.

On the team's back-to-back home struggles, the MI skipper remained measured. "I think that will be the chat where we will go back to again, go forward, and figure out what we need to do. We have a couple of days. We just need to see what we can do best," he concluded.

This is not the first time MI have struggled at home in IPL 2026. The team has now suffered consecutive home defeats, a pattern that raises serious questions about their team combination, batting order, and strategic approach under Pandya's captaincy.

MI's Playoff Hopes Under Serious Threat

The defeat has pushed Mumbai Indians down to eighth position on the IPL 2026 points table, with just four points from seven matches. With the top four playoff spots becoming increasingly competitive, MI's run-rate and win percentage are both under severe strain.

Historically, MI — a five-time IPL champion — have shown the ability to mount dramatic comebacks mid-season. However, with the tournament's second half approaching, the margin for error is rapidly shrinking. Their next assignment is against Sunrisers Hyderabad (SRH) on April 29, a match that could be pivotal for their tournament survival.

The broader concern for MI management is whether Hardik Pandya's captaincy can galvanize a squad that appears to lack the batting depth and Power-play aggression needed to compete with the top sides. The April 29 clash against SRH may well define the trajectory of Mumbai Indians' IPL 2026 campaign.

Point of View

MI have repeatedly failed to build Power-play momentum, a fundamental requirement in modern T20 cricket. What's striking is that Pandya's post-match honesty — refusing to blame the pitch — is admirable, but accountability without correction is just optics. A five-time IPL champion sitting eighth with four points from seven games is a crisis, and the management must ask whether the current team combination and captaincy approach are fit for purpose before the window closes entirely.
NationPress
1 Jul 2026

Frequently Asked Questions

What was the result of MI vs CSK Match 33 in IPL 2026?
Chennai Super Kings defeated Mumbai Indians by 103 runs in Match 33 of IPL 2026 at Wankhede Stadium on April 23. MI were bowled out for just 104 while chasing a target of 208.
What did Hardik Pandya say after MI's defeat against CSK?
Hardik Pandya said losing early wickets in the Power-play made it impossible for MI to chase the target, stating 'we could not cope after that.' He also refused to blame pitch conditions, saying CSK batted on the same track and scored 207.
Who were the top performers in CSK vs MI IPL 2026 match?
Sanju Samson top-scored for CSK with an unbeaten 101, helping them post 207/6. With the ball, left-arm spinner Akeal Hosein took four wickets, while Noor Ahmad also contributed key breakthroughs to bowl MI out for 104.
Where do Mumbai Indians stand in the IPL 2026 points table after this defeat?
Mumbai Indians have dropped to eighth position on the IPL 2026 points table after this defeat, with only four points from seven matches. Their playoff qualification is under serious threat.
When is Mumbai Indians' next IPL 2026 match?
Mumbai Indians will next play against Sunrisers Hyderabad (SRH) on April 29 in IPL 2026. The match is crucial for MI's slim playoff hopes given their poor run of form.
Nation Press
The Trail

Connected Dots

Tracing the thread behind this story — newest first.

8 Dots
  1. Latest 1 month ago
  2. 2 months ago
  3. 2 months ago
  4. 2 months ago
  5. 2 months ago
  6. 2 months ago
  7. 1 year ago
  8. 1 year ago
Google Prefer NP
On Google