TODAY’S PAPER | October 20, 2026 | EPAPER

SHC rejects state appeal against Mahrang's acquittal

.


Nasir Butt October 20, 2026 1 min read
Photo: File

KAARCHI:

The Sindh High Court (SHC) on Monday dismissed a provincial government appeal challenging the acquittal of Baloch Yakjehti Committee (BYC) leader Mahrang Baloch in an incitement case, declaring the appeal not maintainable.

The case against Mahrang and others was registered in Karachi on Oct 11, 2024, on the complaint of a citizen, Asad Ali, under the country's terror law. The complainant stated that Mahrang was a facilitator of terrorist organisations that were enticing educated youth from Balochistan and arranging a movement of terrorists under the guise of processions and rallies. A year later, an anti-terrorism court (ATC) acquitted Mahrang, ruling that the prosecution had failed to present credible evidence. Subsequently, the acting prosecutor general Sindh challenged the acquittal before the SHC in December 2025.

During today's hearing, the high court questioned the prosecution's authority to challenge the acquittal, observing that the original complainant in the case was a private individual. The bench questioned how the prosecution could independently file an appeal against the acquittal when the case had been lodged by a private complainant.

The prosecution argued that the ATC had overlooked material facts while allowing Mahrang's application for acquittal. The state counsel maintained that clear evidence existed against her and argued that the prosecution should have been allowed to present its evidence during the trial.

The prosecutor further contended that acquitting her before the formal framing of charges was inappropriate, as the prosecution had not yet presented its case before the trial court. However, the high court declared the appeal not maintainable and dismissed it, leaving the ATC's acquittal decision undisturbed.

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