PBKS drops 18 catches, chaos vs SRH
- Sunrisers Hyderabad turned Punjab Kings’ sloppiness into a run-fest on May 6, with dropped chances handing Ishan Kishan and Heinrich Klaasen a free ride. - Klaasen reached fifty in 32 balls after being dropped on 9, while Kishan made 55 off 32 despite two dropped catches and a missed stumping. - Punjab were still top before the game, but the fielding collapse exposed the one flaw that can wreck a playoff-caliber side.
Punjab Kings didn’t get blown away by genius. They mostly got undone by their own hands. Against Sunrisers Hyderabad on May 6, PBKS kept putting chances down, and SRH’s middle order did what good T20 batting units always do with extra lives — they turned them into a flood of runs. By the middle overs, the game had stopped feeling like a contest of plans and started looking like a fielding intervention gone wrong. (espncricinfo.com) ### What actually went wrong? The simple version is this: PBKS created openings and then refused to cash them in. ESPNcricinfo’s live report had the theme right in the headline — “Butter-fingers PBKS let game slip.” That wasn’t exaggeration. Heinrich Klaasen was dropped on 9 by Shashank Singh, and Ishan Kishan survived two dropped catches plus a missed stumping before he got to a half-century. (espncricinfo.com) ### Why did those misses hurt so much? Because these weren’t tailenders scratching around. Kishan got to 55 off 32 balls, and Klaasen reached fifty off 32 himself after that early reprieve. In a format where one batter can flip the game in 15 balls, giving both of them extra lives is basically like bowling bonus overs. SRH had raced past 200 by the 18th over while PBKS were still chasing moments they had already let go. (espncricinfo.com) ### Was it one bad over or a pattern? Looks like a pattern. Ricky Ponting said during the game that PBKS had put “a lot of catches down so far this season” and called it “like a virus.” That line matters because coaches usually protect their players in public. For Ponting to frame it that bluntly, mid-match, tells you this isn’t being treated as random bad luck inside the camp. (espncricinfo.com) ### Where did the innings get away? Once the reprieves stacked up, SRH’s scoring rate never really dipped. The side moved beyond 200 in the 18th over, with Nitish Kumar Reddy also cashing in late. PBKS had chosen to field, which meant they had already committed to controlling the chase through execution in the ring and on the rope. When the catching goes, that whole decision starts to collapse with it. (espncricinfo.com) ### Why does Klaasen keep making this worse? Because he is exactly the batter you cannot gift. The PBKS official site’s league tracker listed Klaasen as the Orange Cap holder entering the day, and ESPNcricinfo noted he had made a double-digit score in every game this season. So the drop on 9 wasn’t just a missed chance against a dangerous hitter — it was a missed chance against one of the hottest batters in the tournament. (punjabkingsipl.in) ### Does this change the bigger PBKS picture? Not completely — but it sharpens the risk. PBKS were still sitting at or near the top end of the table around this match, with a strong run behind them. The problem is that fielding errors are the fastest way to waste a good season, because they cancel out correct bowling plans and make even manageable totals explode. A playoff team can sur(punjabkingsipl.in)es are harder to hide. (punjabkingsipl.in) ### So what’s the real takeaway? PBKS didn’t reveal a mystery weakness here. They revealed an obvious one, loudly. Their bowling created enough moments to keep SRH in check, but the catching turned those moments into highlights for the other side. If Punjab fix that, they still look dangerous. If they don’t, every big knockout game will carry the same fear — not whether they can create chances, but whether they can hold them. (espncricinfo.com)