Rawalpindi Division is facing a prolonged four-month drought for the first time in history, attributed to the effects of climate change. Traditionally, the region experiences significant rainfall from October to February, but this year, no rainfall has occurred since October. The drought has severely affected agriculture, water resources, and public health.
The extended dry spell has caused widespread damage to wheat crops, summer-planted vegetables, and seasonal fruit orchards. Wheat crops in the Potohar region have stopped growing after reaching just one foot in height and are turning yellow due to the absence of rain. This could result in a severe decline in wheat production this year.
Moreover, groundwater levels have plummeted further, exceeding depths of 700 to 800 feet. Tube wells, which previously operated effectively at depths of 300 to 500 feet, are at risk of running dry. This has also affected reservoirs such as Rawal Dam, Simly Dam, and Khanpur Dam, raising fears of a major water crisis during the upcoming summer months.
Health concerns have also surged amid the drought. The dry weather has prolonged cases of colds, coughs, sore throats, eye inflammation, skin diseases, and stomach ailments. Public hospitals are reporting 2,000 to 3,000 cases daily, while private clinics are witnessing a rush of patients.
Dr Inayat, Deputy Medical Superintendent (DMS) at Benazir Bhutto General Hospital, urged citizens to take preventive measures such as wearing masks, consuming warm foods like soups and stews, avoiding cold water and ice cream, and wearing proper protective clothing, especially at night.
Agriculture Department Spokesperson Haroon Ahmed emphasised that the Potohar region relies heavily on rainfall for crops, gardens, and vegetables. The prolonged drought, he said, is having a devastating impact. He appealed for prayers for rain and announced a collective prayer for rainfall scheduled for Friday, February 1.
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