Skip to main content

Dnipro Station Strike Death Toll Rises to 14 as Rail Operator Reviews Evacuation

Regional authorities raised the toll from a Russian drone strike on Dnipro railway station to 14 dead and 14 injured on October 29. Ukrainian Railways said it was reconstructing the sequence of events and reviewing its safety procedures after a drone hit a platform where a train stood. Dnipropetrovsk regional military administration head Oleksandr Hanzha said 13 of the injured were hospitalized. Six were in serious condition, including an eleven-year-old boy. The railway operator identified the train as an electric service bound for Zaporizhzhia. Ukrainian Railways said evacuation aboard that train was announced more than ten minutes before impact. Voice announcements began, and an assistant driver walked through every carriage. The operator said its monitoring staff had raised the assessed danger as the drone approached, and instructions to suspend movement went to train crews and the station. Passengers were instructed to leave the platform and move at least 200 metres away. The crew evacuated, it said. The railway said station announcements repeatedly directed passengers to shelters and told them departures would resume after the alert. Nevertheless, “Many people were in the immediate vicinity of the train,” Ukrainian Railways said. The operator’s account of the evacuation remains part of its continuing investigation. It pledged a further detailed review of its protocols to identify additional measures and improve the movement of passengers to safety.

Sources

Telegram · @dnipropetrovskaODA12Telegram · @UkrzalInfo12
Courtroom-sketch editorial illustration of the Tunelna railway platform in Dnipro, with tracks, overhead wires, white railings and a concrete pole bearing a railway engineering marker, based on an archival April 2020 photograph; contextual railway view, not the struck station or October 2026 attack, rendered in warm ochre and slate-blue pastel strokes.

Commentary

Loading comments…

Something went wrong

We couldn't complete that action. Check your connection and try again.