KE responds to power outages petition in SHC, NEPRA summoned on next hearing on August 5

Power company cites Supreme Court ruling against direct court approaches on such matters


News Desk July 23, 2024

K-Electric (KE) on Monday submitted its response to a petition filed in the Sindh High Court (SHC) against prolonged load shedding during Karachi's severe heatwave.

In the petition, it was contended that three deaths occurred due to extreme heat and pointed out that residents face up to 12-hour power outages despite timely bill payments.

KE noted that load shedding occurs on feeders with losses and referenced a Supreme Court ruling against direct court approaches on such matters.

However, advocate Muhammad Vawda argued that KE’s response is "irrelevant and lacks significance," noting that complaints had been lodged with the National Electric Power Regulatory Authority (Nepra), which has yet to act.

Vawda questioned the justification for load shedding on a no-loss feeder, accusing KE of violating policy and NEPRA of inaction. The petition emphasised the suffering caused by alleged collusion between NEPRA and KE, despite residents' timely bill payments.

The court has adjourned the hearing until August 5, directing NEPRA to respond at the next session.

A Jamaat-i-Islami (JI) leader had filed a petition in the Sindh High Court (SHC) last week against KE, seeking an end to the load shedding during the ongoing heatwave in the metropolis.

JI Karachi president Munim Zafar, deputy parliamentary leader in the City Council Advocate Saifuddin and others filed the petition before the SHC, naming the power ministry, Nepra and the KE as respondents.

The petitioners contended that the KE transmission and distribution in Karachi had been observing load shedding for an average duration of 10 to 16 hours daily in various localities, attributing the measure to power theft-related losses.

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