Klaasen catch controversy sparks furious debate on IPL 2026's opening night

Heinrich Klaasen was left fuming after third umpire Rohan Pandit gave him out caught on the boundary despite replays failing to confirm whether Phil Salt's foot touched the cushion. The dismissal overshadowed a record-breaking RCB chase and became the first talking point of the new season.
March 29, 2026
klaasen catch controversy ipl 2026

The IPL 2026 season is barely 24 hours old and it already has its first full-blown controversy. Heinrich Klaasen was given out caught on the deep mid-wicket boundary by Phil Salt during Sunrisers Hyderabad's innings against Royal Challengers Bengaluru on March 28, and the decision has split opinion clean down the middle.

What happened on the catch

Klaasen had scored 31 off 22 balls and was starting to shift through the gears alongside Ishan Kishan when he pulled a short delivery from Romario Shepherd towards the deep mid-wicket fence. Salt sprinted across, dived and gathered the ball close to the boundary cushion before tumbling to the ground.

The on-field umpires immediately sent it upstairs. Third umpire Rohan Pandit studied several replays, checking whether Salt's shoe had made contact with the cushion while he still had the ball in his hands. After a lengthy review, Pandit ruled Klaasen out, saying he did not see "any movement of the cushions" that proved contact.

The angle that arrived too late

Here is where it gets messy. A top-angle replay, shown after the broadcast break, appeared to show the boundary cushion shifting slightly. Fans, commentators and former players immediately seized on it. The question is simple: did Salt's boot nudge the cushion before he completed the catch? If so, it should have been six runs and Klaasen not out.

The problem is that this particular angle was reportedly not available to Pandit in real time. Without it, the footage was genuinely inconclusive, and the third umpire's decision to give him out stood.

Klaasen did not hold back

Klaasen stood his ground and had a visible exchange with the on-field officials before eventually walking off. He was convinced he was not out. Considering he and Kishan had rescued SRH from a shaky start and were building a partnership that eventually produced 97 runs, the timing of the decision stung badly. SRH posted 201 for 9 in 20 overs, a total that should have been more competitive. RCB chased it in 15.4 overs with six wickets to spare.

Would it have changed the result?

That is debatable. Kishan top-scored with 80 off 38 balls and Aniket Verma hit a quick 43, so SRH still put up a big total. But Klaasen on 31 and accelerating could easily have pushed them past 220. Against a Virat Kohli in this kind of form (unbeaten 69 off 38), even an extra 20 might not have been enough. But we will never know, and that is exactly the point frustrated SRH supporters are making.

A technology question that refuses to go away

This is not the first time a boundary catch has caused confusion in the IPL. It probably will not be the last. The debate comes back to the same issue every time: if the technology exists but was not provided to the decision-maker at the right moment, then the system has failed regardless of what the umpire saw.

The IPL season is 74 matches long. That is a lot of tight calls still to come. If the BCCI wants to avoid this argument repeating itself every other week, a full review of how boundary replays reach the third umpire might be worth doing sooner rather than later.

Catch all the latest IPL 2026 news and talking points