Traffic plan devised for Youm-e-Ali procession in Karachi

No vehicular traffic will be permitted to proceed towards Numaish under any circumstances


Our Correspondent June 17, 2017
PHOTO: PPI

KARACHI: The Karachi traffic police have issued a comprehensive traffic plan for processions on June 17 to commemorate the martyrdom of Hazrat Ali (RA).

The main procession will start from Nishtar Park and will terminate at Hussainian Iranian Imambargah. No vehicular traffic will be permitted to proceed towards Numaish.

As soon as the procession will start from Nishtar Park, all the traffic coming from the Nazimabad side to Saddar will be diverted from Lasbela on Nishtar Road towards Garden Zoo to reach their destinations.

Youm-e-Ali: Security beefed up in Multan

All kind of traffic coming from Liaquatabad will be diverted to Martin Road towards Jail Road, from where they will proceed via Jamshed Road, Dada Bhoy Noorji Road, Kashmir Road, Sharae Quaideen and Sharae Faisal to reach their destinations.

Meanwhile, traffic coming from Stadium Road will also be diverted at Dada Bhoy Noorji Road towards Kashmir Road, Society Light Signal, Sharae Quaideen and Sharae Faisal.

All traffic coming from Super Highway and Gulberg to Saddar shall be diverted from Liaquatabad No 10 towards Nazimabad No 2 and shall proceed via the Habib Bank Flyover, Estate Avenue Road and Shershah to Mauripur Road. For the opposite direction, vehicles will adopt the same route.

Traffic discipline reflects national character: IGP

Traffic will not be permitted to proceed towards the route of the procession from the Guru Mandir Roundabout. These vehicles shall be diverted towards Bahadur Yar Jang Road and Khan Bahadur Naqi Muhammad Khan Road.

Vehicular traffic approaching Numaish via Sharae Quaideen will not be allowed to proceed from Society Office roundabout behind Mazar-e-Quaid, except those arriving to participate in the procession.

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