India train derailment kills at least two

Local government officials at the accident site said some coaches had crashed into each other


Afp December 28, 2016
PHOTO: REUTERS

NEW DELHI, INDIA: At least two people died and 28 were injured on Wednesday after a train derailed in north India, close to the site of a previous rail accident that killed 146.

The incident happened in Kanpur, Uttar Pradesh state, when more than a dozen coaches of an express train derailed. Local government officials at the accident site said some coaches had crashed into each other and turned sideways after coming off the tracks.

India train disaster toll rises to 142, more dead feared

"We can confirm two deaths and injuries to at least 28 persons, who are admitted at different hospitals around Kanpur," Zaki Ahmad inspector general of Kanpur police told AFP.

"The incident happened around 5:30am. There were passengers, other than the 28, who'd received minor injuries and left after receiving first aid," he added.

15 killed, over 100 injured as Jaffer Express derails in Balochistan

India's railways minister Suresh Prabhu said senior department officials had already rushed to the accident spot. He kept the public informed through Twitter.







India's railway network, one of the world's largest, is still the main form of long-distance travel in the vast country, but it is poorly funded and deadly accidents occur relatively frequently.

At least 146 people were killed last month in Kanpur, the same district as Wednesday's derailment, when a train disrupted in one of India's worst rail disasters in recent years.

21 dead as trains collide near Karachi's Landhi Railway Station

A 2012 government report said almost 15,000 people were killed every year on India's railways and described the loss of life as an annual "massacre".

The government has signed numerous deals with private companies to upgrade the ageing rail network.

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