At least 164 fire incidents have ravaged wheat fields across Punjab in the past 48 hours, resulting in the destruction of over 750 acres and thousands of tons of harvested wheat.
Nankana Sahib emerged as the most affected district, reporting 20 separate fire incidents. Other districts with significant damage include Sheikhupura with 16 incidents, Dera Ghazi Khan (12), Hafizabad (11), Khanewal (10), while the remaining 95 incidents were reported across various other districts.
Emergency Services Department Secretary Dr Rizwan Naseer expressed serious concern over the rising trend of wheat crop fires and emphasized the urgent need for coordinated efforts to prevent such incidents.
He stressed the importance of public awareness, farmer education, and the activation of Community Emergency Response Teams (CERTs) to ensure early detection and swift response.
During a video link meeting on Monday, Divisional Emergency Officers from across Punjab briefed the secretary on the alarming surge in wheat crop fires.
The District Emergency Officer of Nankana highlighted Rescue 1122's prompt response, which helped contain the fires and prevented further loss. Despite the destruction of 750 acres, timely intervention saved thousands of additional acres from burning.
Dr. Naseer presided over the department's daily operational review meeting, which was attended by wing heads, the Provincial Monitoring Officer, and DEOs via video link.
Each officer presented updates on major operations and notable incidents in their respective districts.
Addressing the gathering, Dr Naseer advised farmers to take preventive measures such as creating firebreaks around their fields, avoiding stubble burning, and ensuring proper maintenance of harvesting machinery to prevent accidental sparks.
He also instructed Rescue 1122 teams to remain on high alert and maintain strong coordination with local communities for rapid response.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ