Over 130 passengers spent the afternoon stuck on a sweaty nightmare train near Toronto
Passengers were stuck on a nightmare VIA Rail trip in the Greater Toronto Area for the better part of Friday afternoon when their train ground to a halt in Oshawa before 2 p.m.
As the sun shone out their train windows, passengers were cooped up on train #42 due to what VIA Rail described in a statement as "mechanical issues."
Sitting here in a dead train for over 2 hours.
— KnowledgePower (@Knowled79420294) April 14, 2023
No information.
Why @VIA_Rail @OmarAlghabra
A total of 133 passengers aboard the train were forced to wait aboard the train with little in the way of food, though some passengers were provided with light refreshments for what was initially estimated to be a 90-minute wait — though no working washrooms to make room for said refreshments.
Passengers stranded on dead #VIArail Train #42 given FREE digestive biscuits
— KnowledgePower (@Knowled79420294) April 14, 2023
...with no working washroom, this might be a problem. No? pic.twitter.com/A0af7SszYI
One of the passengers was live-tweeting their experience on the halted train, complaining that customers were told compensation would not be provided.
#VIArail Train 42 STUCK in #Oshawa
— KnowledgePower (@Knowled79420294) April 14, 2023
Engine broken. 90min delay.@VIA_Rail says they can't compensate
Making matters worse, the apparent engine outage meant that passengers had to endure rising temperatures in a train that lacked air conditioning.
No AC
— KnowledgePower (@Knowled79420294) April 14, 2023
VIA train #45 eventually showed up after over one hour to help get train #42 back up and running. The train operator said that the second train would share equipment with the affected train, in what I'm picturing as something akin to a car-and-jumper-cable situation.
— KnowledgePower (@Knowled79420294) April 14, 2023
Train #42 resumed service just before 4 p.m. after over two hours delay based on reports of passengers, though VIA states that the train is only running approximately one hour and 24 minutes behind schedule.
Join the conversation Load comments