19-year-old succumbs to 100% burns

Police have arrested a suspect and are currently investigating the incident


Our Correspondent March 17, 2016
PHOTO: FILE

KARACHI: A 19-year-old man set ablaze on Sunday allegedly by unknown men in Sehwan succumbed to his injuries on Wednesday evening while being treated at the burns ward at Civil Hospital, Karachi.

Ghulam Ali Solangi was brought to the burns ward in a critical condition on Tuesday and the doctors declared him burnt on 100% of his body. "There was no hope when he was brought to the hospital," said Dr Ahmer, the ward's senior doctor. He told The Express Tribune that patients with such severe injuries rarely survive.

19-year-old fighting for life after receiving 100% burns

Solangi reportedly had a tea shop in Sehwan and belonged to one of the town's most influential tribes. Various rumours circulated in the area, including one that suspected him of taking his life due to a love affair.



"Nothing is clear right now," said Sehwan SHO Mumtaz Thebo. He said that the case had been lodged and that the family nominated Pappu Bhatti and two unknown persons in it.

Speaking to The Express Tribune, Thebo said that Bhatti was arrested on the day of the incident on the complaint of the family. "We have to investigate the truth behind the incident," he added, saying the police did not record Solangi's statement because of his serious condition.

15-year-old girl raped, set on fire in India

The police will trace the culprits in a few days if Solangi's injuries were the result of foul play, claimed the SHO, who added that the family has to cooperate for a proper investigation to be carried out. "It is a small town and finding out the truth behind the incident will not be a major issue for investigating team," said Thebo.

The body was taken back to Sehwan where Solangi was buried on Thursday morning.

Published in The Express Tribune, March 18th, 2016.

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