Sulaiman Lashari murder case: ATC rejects application to start proceedings against IO

The IO had allegedly overwritten the suspect's medical report issued by a private hospital


Our Correspondent November 17, 2014
Sulaiman Lashari murder case: ATC rejects application to start proceedings against IO

KARACHI: An anti-terrorism court (ATC) rejected on Monday an application seeking action against the investigation officer (IO) of the Sulaiman Lashari murder case for tampering with the medical report of the prime suspect.

Judge Saleem Raza Baloch of the ATC-III dismissed the application filed by the counsel of Salman Abro, the main accused, and police officer Maqbool Brohi, to initiate criminal proceedings against the IO, Mubin Ahmed, under Section 200 of Code of Criminal Proceeding (CrPC).

The suspects, Salman Abro and Maqbool Brohi, had accused the IO of overwriting the medical report issued by a private hospital, wherein, he deliberately mentioned his wrong age. They had pleaded to the court to order action against the police official under Section 200 of the Code of Criminal Procedure (CrPC).



On the other hand, the special public prosecutor opposed the request, arguing that the hospital's medical report had nothing to do with the determination of age, so it did not affect the case.

Dismissing the suspects' plea, the judge adjourned the hearing till November 22 for arguments on Abro's other applications of acquittal and transfer of the case to district court. Through an application under Section 265K, the court has been requested to acquit the suspect while through another application under section 23A, the suspect has appealed to transfer the case to a district court.

Salman, the son of a senior police officer, and five of his guards, are booked for allegedly murdering 18-year-old Lashari in Defence Housing Authority (DHA) on May 8 this year.

Published in The Express Tribune, November 18th, 2014.

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