Jammu and Kashmir High Court

RP/48/2024 of ROSHAN LAL Vs UT OF J AND K TH PRINCIPAL SECRETARY TO GOVT PUBLIC WORKS DEPTT AND OTHERS on 19 May 2026

Cites 0, Cited by 0

No. 1 Supplementary Cause list HIGH COURT OF JAMMU & KASHMIR AND LADAKH AT JAMMU (Through Virtual Mode) RP 48/2024 in WP(C) 1080/2022 CM 4095/2024 Roshan Lal (45 Years) S/O Sh. Mulkh Raj R/O Village Hidyal Tehsil & District Kishtwar …Appellant(s)/Petitioner(s) Through: Mr. Vishal

Serial No. 1

Supplementary Cause list

HIGH COURT OF JAMMU & KASHMIR AND LADAKH

AT JAMMU

(Through Virtual Mode)

RP 48/2024 in WP(C) 1080/2022

CM 4095/2024

Roshan Lal (45 Years)

S/O Sh. Mulkh Raj

R/O Village Hidyal

Tehsil & District Kishtwar

…Appellant(s)/Petitioner(s)

Through: Mr. Vishal Sharma, Advocate

Vs.

1. Union Territory of J&K Through

Principal Secretary to Govt.

Publis Works Department

Civil Secretariat, Jammu/Srinagar

2. Development

Commissioner

(Works)

PW(R&B),

Civil Secretariat Jammu/Srinagar

3. Chief Engineer, PWD (R&B)

Lok Nirman Bhawan

Rail Head Complex Jammu

4. Superintending Engineer PWD (R&B)

Circle Doda

5. Executive Engineer, PWD (R&B)

Division Kishtwar

...Respondent(s)

Through: Mr. Ravinder Gupta, AAG

CORAM:

HON’BLE MR. JUSTICE M. A. CHOWDHARY, JUDGE.

Citations and Judicial Treatment

No citing decisions in the index yet

Cited by

0

Decisions in the index citing it

Cites

0

Decisions referred to

In this index

0

Of the decisions it cites

Overruled / Questioned

0

No negative treatment found

Loading the citing and cited decisions…

ORDER

19.05.2026

1. Petitioner, through the medium of this petition, seeks review of the judgment dated 16.12.2023 passed in WP(C) 1080/2022 titled “Roshan Lal Vs. UT of J&K & Ors.”, with a prayer for recalling the same and for hearing the writ petition afresh.

2. Learned counsel for the petitioner submits that the petitioner had filed two writ petitions viz WP(C) No. 1080/2022 and WP(C) No. 1023/2022, and that the respondents had erroneously filed the objections pertaining to WP(C) No. 1023/2022 in WP(C) No. 1080/2022, on the basis whereof the judgment sought to be reviewed came to be passed.

3. Pursuant to notice, respondents have filed objections to the present review petition, stating therein that the objections were inadvertently filed in WP(C) No. 1080/2022 instead of WP(C) No. 1023/2022, and that this

Court, on the basis of the said objections, passed the judgment sought to be reviewed.

4. On perusal of the record of the case, it transpires that the respondents had inadvertently filed reply/objections prepared to be filed in response to WP(C) 1023/2022 in WP(C) 1080/2022, in view of the same cause title of both the petitions. The respondents have thus fairly conceded, the plea raised in this review petition.

5. For the aforestated reasons, the judgment sought to be reviewed has been passed, on consideration of the facts and submissions made with regard to another case, as such, case is made out to review the judgment dated 16.12.2023, passed in WP(C) 1080/2022.

6. In view of the facts and circumstances of the case, review petition is allowed and the judgment sought to be reviewed is ordered to be recalled and WP(C) 1080/2022 is ordered to be taken up afresh, for hearing.

7. List WP(C) 1080/2022 on 10.07.2026.

8. Accordingly, the review petition stands disposed of, along with all connected application(s).

(M. A. CHOWDHARY)

JUDGE

SRINAGAR: 19.05.2026 “Adil Ismail”

You have used today's free searches. Sign in, for free, to keep searching without a limit.

Compass reads the judgments for you and finds the paragraphs for and against your question. Sign in to use it.

My Vault follows judgments for you and records every later decision that cites them. Sign in to keep one.

Sign in to download the court's PDF. The full text stays free to read here.

Sign in, for free, to download the court copy. Reading the full text here stays open to everyone.

Search and read Indian judgments without limits, save them to My Vault and find the relevant paragraphs with Compass.

Open the sign-in page instead