Pakistan Cricket Board’s (PCB) selectors dropped fast-bowler Sohail Khan and leg-spinner Yasir Shah, while reposing confidence on the team’s current batting line-up, overlooking the seasoned wicketkeeper-batsman.
“It’s very shocking for me to not see my name in the team,” Kamran told The Express Tribune. “I was confident of my selection after the PCB took my passport to register for an Australian visa and I am very disheartened over the snub.”
PCB divided over Kamran Akmal's inclusion in ODI squad
The veteran feels he has done everything he could to deserve a place in the side. “A player can only perform to force his way into the team again,” he said. “I have performed in all formats of the domestic season and my form is for everyone to see. I want to ask the selection committee and team management what else I need to do to return to the national team?”
Kamran, who last represented Pakistan in the World T20 in Bangladesh a couple of years ago, was under consideration for the ODI series due to his brilliant run at the Quaid-e-Azam Trophy (QAT) and National One-Day Cup.
The 34-year-old top-scored in QAT with 1,035 runs and made five centuries, scoring at an average of almost 80. He is also among the highest runs scorer in the ongoing National One Day Cup, amassing 361 runs at an average of over 51.
Salman Butt, Kamran Akmal eye national team call-up
Kamran’s inclusion was advocated strongly by the selection committee headed by former captain Inzamamul Haq but the team management, led by head coach Mickey Arthur, opposed his selection.
“If the selection committee doesn’t have the power, then it should not be criticised for the side’s failures and only the team management should be held responsible,” he said.
Kamran, who has played 53 Tests and 154 ODIs for Pakistan, said he would continue to fight for his slot in the national team. “I am not stopping here. I would continue the hard work until it pays off,” he said.
COMMENTS (9)
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ