“In view of repeated attacks on the oil tankers and merciless beating of drivers and cleaners by miscreants in the valley, all Jammu and Kashmir oil tanker operators have decided to suspend petrol, diesel and kerosene oil supplies,” India Times quoted J&K Petrol Tanker Owners Association president Anand Sharma as saying. Sharma alleged that the failure of security agencies to protect drivers, cleaners and tankers had forced the association to take this decision.
UN chief condemns Indian Kashmir killings, calls for dialogue
“Drivers have been targeted for the last several days in the valley. Two tanker drivers were mercilessly beaten by a mob near Khannabal in Anantnag district on Saturday. Both arms of the drivers were fractured. The vehicles were also badly damaged,” he said, adding, “At least a dozen tankers have been damaged so far.”
The association president further alleged that the Indian government had totally failed to ensure security to the drivers and vehicles operating in the disputed region. Panic had gripped the Himalayan region last week after rumours that the authorities had decided to suspend fuel supplies to the valley.
UN chief lauds Pakistan’s resolve for peaceful Kashmir settlement
However, J&K Divisional Commissioner Baseer Khan denied the rumours saying adequate security would be provided to oil tanker operators to ensure uninterrupted supply to the valley. The decision of the oil tanker owners association to go on a strike is likely to plunge Indian-held Kashmir into a fuel crisis at a time when authorities have been battling a fresh wave of separatism.
Kashmir has been divided between Pakistan and India since the end of British colonial rule in August, 1947. Both states claim the territory in full. It is the epicentre of an insurgency, with several rebel groups fighting Indian troops and police in a bid for independence or merger with Pakistan.
This article originally appeared on India Times.
COMMENTS (1)
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ