CM Bizenjo survives no-trust move

No-confidence motion against Bizenjo was tabled amid differences within the ruling BAP


Syed Ali Shah May 26, 2022
Qudoos Bizenjo. PHOTO: EXPRESS

QUETTA:

The no-confidence motion filed in the Balochistan Assembly against Chief Minister Mir Quddus Bizenjo failed on Thursday as the movers could not produce the required majority in the house.

Former chief minister Jam Kamal Khan, Sardar Yar Muhammad Rind of the Pakistan Tehreek-e-Insaf (PTI), Asghar Achakzai of the Awami National Party (ANP) and others had submitted a no-confidence motion against the incumbent chief minister.

However, two signatures of former provincial ministers Nawabzada Tariq Magsi and Mobeen Khilji were missing during the vote of no confidence.

Constitutionally, 13 members were required to be present in the house and support the no-confidence motion for admissibility, however, only 11 members were present at the provincial assembly in support of the no-confidence motion.

Subsequently, Deputy Speaker Balochistan Assembly Sardar Babar Musakhail said that the no-trust motion cannot be passed as the movers could not produce the required number of signatures.

"Pakistan Democratic Movement (PDM) had promised to support our no-confidence motion when we supported them against former prime minister Imran Khan," Jam Kamal told reporters.

Read Bizenjo vows to face no-trust motion in democratic way

The former Balochistan chief minister also lashed out at the present government for what he called the worst governance and corruption.

He added that the Election Commission of Pakistan (ECP) would be approached to take action against the Balochistan Awami Party (BAP) members who had not supported party policy.

The no-confidence motion against the Bizenjo was tabled in an earlier session of the provincial assembly amid differences within the ruling Balochistan Awami Party (BAP).

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