Justice Khan to take oath as SC judge tomorrow

Will serve as the top court judge until November 30, 2025


Hasnaat Maik October 20, 2019
A view of the Supreme Court of Pakistan in Islamabad. PHOTO: REUTERS

ISLAMABAD: Justice Amin-Ud-Din Khan will take oath as a Supreme Court judge on Monday (tomorrow). Chief Justice of Pakistan (CJP) Asif Saeed Khosa will be administrator to Justice Khan’s oath.

Justice Khan, who was fifth in the seniority list of the Lahore High Court, would serve as the SC judge until November 30, 2025.

Justice Khan’s elevation has been proposed because of his expertise in civil laws.

After the retirement of the CJP Mian Saqib Nisar and Justice Sheikh Azmat Saeed this year, the SC has already lost its experts on civil laws.

The apex court will reach its full strength after Justice Khan’s elevation.

The Pakistan Bar Council (PBC) has supported Justice Khan’s elevation to the apex court.

The Parliamentary Committee on Judges Appointment on October 7 approved his nomination. However, the committee observed that thirteen judges of the high courts in the country were senior to him.

The committee considered all aspects of the matter and was of the view that, although the nomination of his lordship was covered under the Constitution, all provinces – especially the smaller ones – should have been given due share in the appointments of judges to the top court in order to remove a sense of deprivation.

The body expressed concern over low elevation rate of judges to the SC from smaller provinces.

Currently, eight SC judges are from Punjab, six from Sindh and two from Khyber-Pakhtunkhwa. Interestingly, only one SC judge, Qazi Faez Isa, hails from Balochistan.

Justice Isa, who has been working as the top court judge since 2014, is facing a presidential reference.

It will be interesting as to whether Justice Khan will be part of the full court hearing Justice Isa case.

 

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