16,313 provided emergency help in 2012

The average response time was six minutes and 12 seconds, says Divisional Emergency Officer.


Our Correspondent January 05, 2013
The average response time was six minutes and 12 seconds, says Divisional Emergency Officer. PHOTO: RESCUE.GOV.PK

BAHAWALPUR:


The Bahawalpur district control room responded to 16,313 emergency calls in 2012, Punjab Emergency Service (Rescue 1122) Divisional Emergency Officer Asif Rahim Channar said on Friday.


He was sharing the annual performance report with the reporters.

The average response time was six minutes and 12 seconds, he said.

Of the emergencies responded to, 4,463 were road traffic accidents, 279 fire incidents, two cylinder blasts, three building collapses, 622 quarrels, 10,820 medical emergencies, 36 drowning and 88 special rescue operations.

As many 3,806 were given first aid on the spot.

As many as 2,765 road accidents were reported in 2012. Of the 196 fire incident reported, 86 had been started due to electric short circuit and 54 were blamed on negligence. Reasons behind 48 could not be established.

The PES also provided basic life support and disaster management training at several departments.

Channar said that during the dengue fever season, the service organised several seminars at schools and colleges to spread awareness.

The service also marked the October 2005 earthquake anniversary by organising lectures at various educational institutes with focus on disaster management.

Published in The Express Tribune, January 5th, 2013.

COMMENTS (2)

Asad | 11 years ago | Reply

Real heroes of our nation.

Ayesha Pervez | 11 years ago | Reply

I do not have a good image of this so called Rescue 1122 Organization since the 2010 Sialkot incident where two brothers were publicly lynched in the most brutal manner and these guys didnt help! I really pray to Allah I never have to take help of this organization.

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