In a thrilling encounter at the Grand Prairie Cricket Stadium in Dallas on Thursday, the USA caused the first upset of the T20 World Cup 2024 by defeating Pakistan in the super over. Defending a 19-run target, the hosts restricted Pakistan to 13/1 in the Super Over, securing their second victory in the tournament and topping Group A with four points.
Chasing a modest 160-run target, the USA lost opener Steven Taylor for 12 in the sixth over, but captain Monank Patel and Andries Gous anchored their side's chase with a crucial 68-run partnership. Despite setbacks, newcomers Aaron Jones and Nitish Kumar fought valiantly, leveling the score with a final-ball boundary.
Haris Rauf bowled out Andries Gous for 35 off 26 while Muhammad Amir caught behind US Captain Monank Patel at the start of the 15th over with the score at 111-3. Patel led his side through the first half of their innings in great style, scoring a crucial half century in just 38 deliveries.
At the end of the first innings, Pakistan had managed to post 159-7 on the board. All-rounder Shaheen Shah Afridi came to the batters' rescue by taking on the US bowling attack in the last couple of overs with a decent contribution of 23 off 16 balls after Shadab Khan's attempts to counterattack failed as he succumbed to the wrath of the US spin attack for 40 off 25.
Captain Babar Azam looked to stabilize the innings by raining boundaries, however, the skipper finally lost the battle against US seamers, departing for 44 off 43 balls.
Mohammad Rizwan fell early to Saurabh Netravalkar's delivery, caught by Steven Taylor in slips, while Usman Khan was caught by Nitish Kumar off Nosthush Kenjige's bowling. Fakhar Zaman followed suit, departing after a mistimed shot.
US won the toss and chose to field first in the T20 World Cup match at Dallas’ Grand Prairie Stadium. The co-hosts, coming off a victory against arch-rivals Canada, faced Pakistan in their opening Group A encounter.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ