IPL 2024 | Twitter explodes as Narine gets lifeline after Pant’s late DRS call proves costly

IPL 2024 | Twitter explodes as Narine gets lifeline after Pant’s late DRS call proves costly

no photo

A leader needs to make quick decisions, especially when it comes to clutch moments in important games. Such was the case with Delhi Capitals' skipper Rishab Pant who made a mistake by taking a late DRS call when the ball touched Kolkata’s opener Sunil Narine’s bat and Pant caught it.

‌Opting to bat first proved advantageous for the Kolkata Knight Riders as their opening pair of Sunil Narine and Phil Salt made an impressive start. The duo showcased excellent batting power, propelling their team to 32/0 within just three overs. Their contributions of seven, 10, and 15 runs respectively in the initial overs left the Delhi bowlers scrambling for a breakthrough. However, amidst their relentless assault, a critical moment arose when a delayed decision by Pant led to a potential game-changing situation.

In the fourth over, Delhi's pacer Ishant Sharma delivered a well-directed short-of-a-good-length ball to the seasoned Trinidadian. Attempting to loft the delivery, Narine's bat only managed a thin edge, resulting in a straightforward catch for Pant. Ishant, seemingly disinterested in reviewing the decision, turned around. However, Mitchell Marsh, fielding at cover, expressed interest in a review and sought guidance from Pant. Despite initial hesitation, Pant eventually opted for the DRS. However, deliberation consumed precious time, and by the time Pant decided, the DRS timer had expired, leaving the on-field umpire, Akshay Totre, to inform Pant of the missed opportunity.

Several overs later, as Narine continued to punish Kolkata's bowlers with a strike rate of 238, a replay of the crucial delivery revealed that the ball had indeed brushed Narine's bat. With the Snickometer confirming the contact, it became evident that if Pant had initiated the review promptly, Narine would have been dismissed. The batter went on to score a 39-ball 85.

The incident did not go unnoticed by the Twitterverse, sparking discussions across social media platforms.

Poor captaincy

Late signal

Worst

Kuldeep is helping

Bad in both

Too poor

Worst of the league

Dream

Nothing can't help

Can't be childish

Get updates! Follow us on

Open all