Pakistan Cricket Board (PCB) has disclosed that the board was close to inking a deal with West Indies cricket team to have some limited-over matches in the country, but a bomb blast in Lahore in March derailed the plan.
Najam Sethi, who heads PCB’s executive committee, said that the West Indies Cricket Board (WICB) was on the verge of agreeing to play a few matches of the scheduled series in Pakistan, however, the terror incident at Gulshan Park, Lahore made the visitors review their security concerns.
“We nearly convinced them that they needed to support us by playing [cricket] in Pakistan,” he said. “We told them this gesture would help us convince other teams to tour the country as well, despite their security concerns.”
Will try to stage PSL’s second edition final in Pakistan: Najam Sethi
He added: “However, after the bomb blast at Gulshan Park, they told us that the security situation in Pakistan was not right for them to send their team at this time.”
Both the teams will now play the full series in UAE, which has been Pakistan’s home ground since 2009 after militants attacked the Sri Lankan team in Lahore. Only Zimbabwe, Kenya and Afghanistan have visited the country for short tours in last seven years.
CB buys bulletproof buses to woo back international teams
Pakistan Super League (PSL) chairman also said that the board had purchased four bullet proof buses for the purpose of security, and was also building additional rooms at National Cricket Academy (NCA) adjacent to the Gaddafi Stadium to reassure foreign players of the security measures being undertaken.
Sethi has been eager to revive international cricket in Pakistan by persuading foreign players and boards to tour the country. Previously, he said that overseas players were being offered extra money to play PSL final in Lahore. “We are offering them at least $20000 each if they play the final in Lahore,” he had said.
Najam Sethi was quoted by Press Trust of India
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ