Accountability court irked at Nawaz's absence

Judge Malik warns to cancel surety bonds, issue arrest warrants if Nawaz's absence continues


Rizwan Shehzad October 01, 2018
Nawaz Sharif. PHOTO: PML-N

ISLAMABAD: The accountability court hearing corruption cases against members of the Sharif family expressed displeasure on Monday after deposed prime minister Nawaz Sharif failed to appear before the court in the Flagship reference hearing.

 

Judge Muhammad Arshad Malik warned to cancel Nawaz’s surety bond and issue arrest warrants if the former premier failed to appear before the bench.

Deposition in Al-Azizia, Hill Metals reference concludes

Judge Malik was further irked when defence counsel Khawaja Haris requested, through his associate Munawwar Iqbal Duggal, for a two-day adjournment of Flagship, Al Aziziya and Hill Metal Establishment reference hearings, owing to health issues.

When the judge inquired about Nawaz’s absence, Duggal asserted that the accused was supposed to appear and sought time to probe the matter. Upon his return, Duggal said the Pakistan Muslim League-Nawaz (PML-N) supremo did not appear owing to “genuine confusion”. The defence counsel added that Nawaz, however, was willing to immediately leave Lahore if the court allowed two to three hours to travel to Islamabad.

NAB officials told to expedite anti-graft investigations

Judge Malik chided defence counsel and the accused of wasting the court and witness’ time but accepted their assurance regarding Nawaz’s appearance for the future hearings.

Referring to Haris’s adjournment appeal, the court noted that the request could only be accepted as far as Flagship reference was concerned and adjourned the hearing until October 4.

The accountability court, however, will hear Al Aziziya and Hill Metal Establishment references on October 2.

 

COMMENTS (1)

Bunny Rabbit | 6 years ago | Reply he seems to have aged over night . he needs a break.
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