Three Saudi nationals drown at Karachi beach

One of them was the son of a Saudi consulate official

Our Correspondent August 26, 2017

KARACHI: Three Saudi nationals drowned at Neelum Point beach in Karachi on Saturday evening.

Police said one of them was the son of a Saudi consulate official and other two employees at the consulate.

They were identified as Fahad, Alaa and Abdullah. The police said two other men accompanying them were rescued in time. The five men were picnicking at the beach.

The bodies of the three men have fished out and are likely to be sent to Saudi Arabia on Monday.

Four teenagers drown at Karachi's Sandspit beach

In May this year, following an increase in drowning cases at Karachi’s beaches, the provincial government had imposed a ban on swimming in the sea for six months.

The government had notified that under Section 144 of the CrPC, a ban has been imposed on wading through, swimming and diving in the sea at the beaches of metropolis for the next six months.

Eighteen people had drowned in May alone while swimming in the waters of different beaches in the city.



Faisal | 6 years ago | Reply lazy officials! Firstly what a tragedy this is to lose so many people in the now very dangerous waters off Karachi. It is all very scientific and it is proven that the weather, winds, sea floor terrain, etc. are making the waters particularly dangerous. Reminds me of the technical ban on Indian movies in our country in the aftermath of the 1965 war which was never really implemented! The ban reinforced after the 1971 Indian interference and annexation of East Pakistan into Bangladesh - never implemented. How low for us to go before we wake up?!!
Idol Breaker | 6 years ago | Reply Having just a ban imposed is not all an excuse for the Sindh government. Enforceability of the Law is equally as important. Somebody please make these people watch the movie 'Baywatch'. That just might put some sense in them!
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