Khyber-Pakhtunkhwa Chief Minister Ali Amin Gandapur has demanded a reduction in electricity loadshedding in the province, threatening to take over the system if the federal government fails to meet his demands.
In a statement issued on Wednesday, Gandapur said that the federal government should issue a schedule for reducing loadshedding by tonight, and if it fails to do so, he will personally visit the PESCO's office to issue the schedule himself.
He also warned that if PESCO does not implement the schedule, the provincial government will take over the system and run it itself.
Read:Power sector suffers Rs589b loss
Gandapur's comments come as the province is facing severe power outages, with loadshedding lasting up to 12 hours a day in some areas.
However, Gandapur accused the federal government of not taking the issue seriously, saying that they are not willing to listen to the province's demands.
He also threatened to take drastic action if the federal government fails to meet his demands, saying that the provincial government will not hesitate to take over the system if necessary.
Gandapur asserted that since these individuals fail to comprehend the language of decency, he will now articulate it in a "different manner."
The chief minister proposed that areas experiencing 10 to 12 hours of loadshedding should be reduced to 5 to 6 hours, while those enduring 15 to 16 hours should see a decrease to 8 to 10 hours.
Read: Power tariff may go up by Rs7 in July
Gandapur said that the federal government has been explicitly notified that the province's outstanding electricity dues should be offset from our funding allocation, insisting that they should not be referred to as ‘electricity thieves’.
He criticised the PML-N-led federal government, alleging their ascension to power through Form-47, citing irregularities during the February 8 polls. "They have usurped our mandate and are subjecting us to oppression," he decried.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ