Shadow of doubt: Notice issued to MPA for inviting PTI leaders to dinner

JUI-F says Fazal Shakoor Khan should have taken party into confidence


Our Correspondent December 05, 2015
JUI-F says Fazal Shakoor Khan should have taken party into confidence. PHOTO: pakp.gov.pk

CHARSADDA: Jamiat Ulema-e-Islam-Fazl Charsadda chapter has issued a show-cause notice to MPA Fazal Shakoor Khan who hosted a dinner for Chief Minister Pervez Khattak and various Pakistan Tehreek-e-Insaf leaders.

According to a press release issued by JUI-F Charsadda Spokesperson Attaullah Khan on Saturday, JUI-F Charsadda chief Maulana Muhammad Hashim and General Secretary Pir Gohar Ali raised concern over the MPA’s decision to extend an invitation to PTI leaders. They insisted Shakoor should have taken the party leadership into confidence before hosting the dinner.

“Both leaders have issued a show-cause notice to the MPA,” read the press release.

As per the press release, Shakoor has made a series of statements in favour of PTI in the past.

“The party had sent a letter to him about these statements and demanded an explanation,” stated the press release. “However, Shakoor tore the letter and returned it to party officials.”

The dinner

The chief minister—along with PTI chief organiser for K-P and the assembly speaker—visited Charsadda on Shakoor’s dinner invitation Thursday night. According to insiders, the chief minister and speaker revealed Shakoor is willing to join PTI.

Shakoor was elected to provincial assembly in 2008 on an ANP ticket. He later developed contacts with JUI-F. As a result, ANP did not allot him ticket for the 2013 elections.

Shakoor was subsequently elected as an MPA on a JUI-F ticket. After winning Charsadda seats of the provincial assembly and national assembly, Shakoor and MNA Gauhar Shah, were sidelined by JUI-F provincial and district chapters.

Published in The Express Tribune, December 6th, 2015.

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