Traffic warden assault: Umar Akmal's father tenders apology on son's behalf, apology accepted

Akmal was arrested on Feb 1 for allegedly violating traffic rules and 'scuffling' with traffic official.


APP/web Desk March 06, 2014
Cricketer Umar Akmal. PHOTO: AFP

LAHORE: Cricketer Umar Akmal's father expressed an unconditional apology to the traffic warden who was allegedly assaulted by his son, Express News reported on Thursday.

The traffic warden accepted the unconditional apology from Akmal's father.

Police sources said the father of the cricketer met Deputy Inspector General (DIG) Investigation Zulfiqar Hameed at his office on Thursday and told him that his son could not appear as he was out of the country for the Asia Cup tour. Superintendent of Police (SP) CIA Umer Virk and Chief Traffic Officer (CTO) Sohail Chaudhry were also present.

Akmal was arrested on February 1 for allegedly violating traffic rules, interfering in government work and “scuffling” with a traffic official.

A court in Lahore had issued an arrest warrant for Akmal for not attending a hearing of traffic warden assault case on February 27. The court had ordered that Akmal should appear before the bench on March 11.

The sportsperson was detained at the Gulberg Circle police station for a few hours, before being released on a personal surety bond of Rs100,000. He was granted bail by a court on February 2.

An FIR was registered against him under Sections 279 (rash driving), 186 (obstructing public servant in discharge of public functions) and 353 (assault to deter public servant).

COMMENTS (18)

True Karachiwala | 10 years ago | Reply

Good stand by Traffic Police. But should be consistent, for every one, and every department should act like this.

Bashir | 10 years ago | Reply

@Imran Bashir: that means the law of the land is different for lawyers, for politicians , for our heroes and the common man in the street.

VIEW MORE 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