WATCH: Azam Khan hit on neck by bouncer, dismissed in CPL 2024

Azam Khan dismissed after bouncer hits neck in CPL match. A tense moment for the Pakistani cricketer.


News Desk August 31, 2024
Courtesy AFP

Listen to article

Pakistani wicketkeeper batter Azam Khan who is representing Guyana Amazon Warriors, narrowly escaped serious injury when he was struck on the neck by a bouncer from Antigua and Barbuda Falcons' pacer Shamar Springer during their Caribbean Premier League (CPL) match on August 30.

Azam tried to pull a short delivery but the ball hit him on the shoulder and then on to the neck.

He ended up getting bowled as the ball crashed into stumps.

He walked out to bat in the 10th over of the run chase at no.5.

The incident took place in the 12th over of Warriors' run chase. On the previous ball, he tried to punch the ball towards off side but got an edge that went past the wicketkeeper Sam Billings.

The 26-year-old fell on the ground and was in pain before the physio rushed to his aide. After receiving medical attention, he walked back to the pavillion with the help of physio.

Azam was dismissed for a run-a-ball nine.

After Azam's wicket, Warriors were 77/4 in 11.3 overs.

Romario Shepherd's 16-ball 32 cameo and Dwaine Pretorius' last-over heroics against Pakistan's left-arm pacer Mohammad Amir helped Warriors win the game by three wickets.

Azam Khan has been under immense scrutiny for his failure to contribute to the Pakistan team.

He was heavily criticised for his weight and fitness, which many think didn't make the cut as per international levels. He had a decent outing for Islamabad United in their title-winning campaign at PSL 2024.

After that, he was included in Pakistan's squad against Ireland, England and the T20 World Cup.

He couldn't make any impact with the bat and was not considered for selection after the team suffered an early exit from the T20 World Cup 2024 in June.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ