What Went Wrong for West Indies T20 WC Super Clash?

What Went Wrong for West Indies 

View below topics in this post

In a superb Super 8 clash the host nation West Indies were knocked out from the T20 World Cup by the South African nation in the do-or-die match here at Antigua. Even though rain played its part with score deduction and overs cut down. The hosts also made a few mistakes that cost them dearly in beating the Proteas side. Let us look at What Went Wrong for West Indies T20 WC Super Clash.

Starting with the toss the host failed to win the toss and was thus sent out to bat first by the South African skipper in these gloomy weather conditions. Except for Kyle Mayers and Roston Chase, no one really held the rope for the West Indies side with the bat. A side known for his batting powers failed on an important day.

DOWNLOAD: STUMPSANDBAILS FANTASY CRICKET APP

Players like Nicholas Pooran, Shai Hope, Rovman Powell, Sherfane Rutherford, and Andre Russell all failed to support the team in scoring a huge total. This is the side that has the potential to beat any team in the T20 format but unfortunately in this crucial game, the Caribbean side failed to show up.

Why West Indies Failed to Score a Decent Total

As said before the batting was a big failure, a team that has the record of highest first-innings runs in this World Cup was only able to score 135 in 20 overs for the loss of 8 wickets. It was expected that the Caribbean side would at least post a decent total, however, the batting lineup crumbled up the bowling attack of the Proteas.

Tabraiz Shamsi was the star man for South Africa as he picked up three wickets.  Was able to apply pressure on the West Indies batsman. But overall it was a combined bowling effort from the South African side to restrict a dangerous West Indies side to 135. Moreover adding to their vows, due to rain the target was cut down to 123 in 17 overs.

FOLLOW STUMPS AND BAILS FOR FREQUENT CRICKET PREDICTIONS  

Captaincy Mistakes During the Second Innings

West Indies were confident that if they bowled well they could have a chance of restricting South Africa. Where inside the first 5.2 overs the Caribbean side picked up three wickets and South Africa was down to 42. From here on it was a proper end-to-end battle, where wickets kept falling and runs kept coming slowly.

What Went Wrong for West Indies against
News9Live

Here West Indies skipper made the mistake of not using Roston Chase early on in the game. We even saw the difference when he came out to bowl later in the innings. At the end of the match, he bowled three overs and picked up three wickets.

He also gave just one boundary in his three overs. By the time Roston Chase could impact the game, it was an easy task from the South African side. That is why the West Indies skipper should have given the ball to Roston Chase early on and it would have been better if he used his weapon early on.

FOR MORE CRICKET NEWS AND UPDATES JOIN OUR TELEGRAM CHANNEL  

Few Feilding Mistakes Which Could Have Been Avoided  

While the South African team did occasionally demonstrate resilience in the field during the first innings, we could not see the same in the second innings when the West Indies were bowling. The outcome of the game may have been altered if those few runs and the drop catch had been used.

Conclusion: Things Could Have been Much Different If These Could Have been Avoided

In the end, West Indies faced a disappointing exit from the T20 World Cup due to a combination of batting collapses, missed opportunities in captaincy decisions, and lapses in the field. Despite some individual efforts, the team failed to capitalize on its strengths against South Africa, ultimately falling short of expectations. Addressing these areas could have potentially changed the outcome. Highlighting the need for sharper execution in critical matches ahead in the future.

0 Shares:
Leave a Reply

Your email address will not be published. Required fields are marked *

You May Also Like