News   Nov 26, 2024
Reverse View
 167     0 
News   Nov 25, 2024
Work Advances at Line 5 Condos Near Yonge and Mount Pleasant
 739     0 
News   Nov 25, 2024
Pinnacle Resubmission Bumps Heights of Lakeside Project at Sherbourne and Lake Shore
 1K     0 

VIA Rail

SaugeenJunction said:
Next trainset near Chicago. I believe it is number 17.


Consist 18 has that unique paint job, so I hope we can see it soon.
Click to expand...
I wonder when we will see the short and long consists that were proposed back in the design stage. Iirc they proposed 3 and 7 cars before the cab car as possible combinations
 
cplchanb said:
I wonder when we will see the short and long consists that were proposed back in the design stage. Iirc they proposed 3 and 7 cars before the cab car as possible combinations
Click to expand...
If I recall corrently, the two cars removed for a 3-car consist are not the same which need to be added for a 7-car consist, which means you can’t just simply reconfigure two 5-car consists into one short and one long consist without procuring extra cars (or sacrificing a third set). For that reason I‘m rather skeptical that VIA will play around much with consist sizes. If trains are extremely polular, they might just double the consist…
 
Last edited:
On Tuesday I rode train 46 from Toronto to Ottawa, and the train was initially delayed departing Union due to "equipment availability". Something about waiting for a train to arrive from the Toronto Maintenance Centre. Staff in the station did keep us informed of the delay, and I received an email with an updated departure time.

Within a half hour, we had boarded the train and it departed at 16:01, 11 minutes behind the previous GO Train, and 4 minutes ahead of the following GO train. But rather than allowing us to use the perfect gap between GO trains, Metrolinx dispatching decided to make us sit just outside Union Station for five minutes waiting for the 16:05 Lakeshore East local to go first. And then of course once we did get to go, we were now stuck behind a GO Transit local train and had to crawl slowly all the way from Toronto to Pickering.

The result was that Metrolinx turned a 29-minute delay at Union into a 48-minute delay at Pickering where Via Trains leave the GO line.
Screenshot 2024-06-01 at 18.25.51.png


In my experience, it is very common for Metrolinx dispatching to sabotage Via Rail operations. Another common scenario I've experienced is when westbound Via Trains on the express track get held at Danforth so that a local GO train that they have already overtaken can catch up to them again, and cut them off. In all of these situations, the GO Train would have experienced little to no delay if the Via train had been allowed to proceed first.

People often say that Via's poor reliability is because they use railways owned by freight companies, but in my experience, the most hostile track owner they have is the Government of Ontario. CN seems to be far more accommodating than Metrolinx when it comes to changing track assignmenets in real time to allow a Via Train to overtake a slower train.
 
Last edited:
Westbound on the 401 today, around 5 pm, in the vicinity of Liverpool Road, I passed three VIA trainsets, stopped and holding. At least two of the three were Westbound, as their locomotives were on the western head of the train, the third set was one of the recent acquisitions, so harder to conclusively say it was westbound, although that might make sense. Not sure this is a Metrolinx issue, as described above, but in full view of the 401, not a great PR bonanza, not to mention the passengers frustration. Time for dedicated tracks and there is room.
 
reaperexpress said:
In my experience, it is very common for Metrolinx dispatching to sabotage Via Rail operations. Another common scenario I've experienced is when westbound Via Trains on the express track get held at Danforth so that a local GO train that they have already overtaken a while ago can catch up to them again, and cut them off. In all of these situations, the GO Train would have experienced little to no delay if the Via train had been allowed to proceed first.

People often say that Via's poor reliability is because they use railways owned by freight companies, but in my experience, the most hostile track owner they have is the Government of Ontario. CN seems to be far more accommodating than Metrolinx when it comes to changing track assignmenets in real time to allow a Via Train to overtake a slower train.
Click to expand...
You might be right but leading off with an example where VIA appears to have sabotaged themselves first isn’t what I’d use. In the case of the Danforth express, was that train running on time?
 
cplchanb said:
The new train schedule has been updated.
Anyone spot the new slots?

New fleet | VIA Rail

www.viarail.ca www.viarail.ca
Click to expand...
Looks like train 40. Didn't see it on the previous schedule. I'm taking train 40 to Ottawa on June 19th.

I'm probably one of the few people that actually wants to ride the older trains. It's my first time riding VIA and I want to ride the older trains before they get phased out. Thankfully it looks like my train back to Toronto (train 53) is still one of the old trains.
 
Last edited:
dowlingm said:
You might be right but leading off with an example where VIA appears to have sabotaged themselves first isn’t what I’d use.
Click to expand...
I don't know why the train was late arriving from the maintenance centre. Maybe Via screwed up, or maybe Metrolinx failed to give them a slot to exit the yard. Both have happened before.

What I do know is that 19 minutes of delay was actively caused by Metrolinx. Eastbound Via trains are scheduled to depart Union at :02, :17, :32, and :47 past the hour because those are the times that are optimal to fit between Lakeshore East local trains (which depart at :05, :20, :35 and :50 past the hour). The Via train in question departed Union at :02 past the hour and the surrounding GO trains were on time, so allowing the train to depart when it was ready would have incurred little or no impact on GO trains while minimizing delay for the Via train.

Being late is not a reason to delay a train, on the contrary it's a reason to prioritize a train so that the delay can be minimized.

dowlingm said:
In the case of the Danforth express, was that train running on time?
Click to expand...
No, the Via train to Toronto was running late, which makes it especially important to prioritize it over trains that are on time and have schedule padding available to make up delays. Especially in cases such as this one where the delay to the on-time train would be negligible if any. The Via train was already in front of the GO train and going over 130 km/h, so the worst case scenario is literally less than a minute of delay while the GO train waits for the switch to change, after which it would have an unobstructed shot to Union because the Via train would be long gone. A Via train to Windsor was holding in Union Station waiting for the Via train to arrive, and because of the additional 10 minutes of delay that Metrolinx created in addition to the original delay, that train to Windsor departed 10 minutes late, allowing delays to continue propagating across the Ontario rail network.

From what I've observed from Metrolinx dispatching, the decision between letting the GO train go first or the Via train has nothing to do with the delay to either train. If the Via train is late, the GO train goes first. And if the GO train is late, the GO train goes first.
Capture2.PNG

Capture3.PNG


If Metrolinx were a for-profit company then it would be understandable that they prioritize their own trains regardless of how much delay that will cause to other train operators relative to how much delay their trains would save. But they are not a private company. They are a government agency so their duty is to the citizens of Ontario, including those in Via trains. As such they should be dispatching their railways in the way that minimizes delay to train passengers, including those in Via trains. In effect, Metrolinx should be operating as a rail infrastructure manager, for whom Via and GO are simply two Train Operating Companies that are their customers. The train that gets prioritized should be the one that will minimize the overall impact on the Ontario rail network, not simply the one that's green.
 

Attachments

  • Capture.PNG
    Capture.PNG
    143.2 KB · Views: 48
Last edited:
reaperexpress said:
I don't know why the train was late arriving from the maintenance centre. Maybe Via screwed up, or maybe Metrolinx failed to give them a slot to exit the yard. Both have happened before.

What I do know is that 19 minutes of delay was actively caused by Metrolinx. Eastbound Via trains are scheduled to depart Union at :02, :17, :32, and :47 past the hour because those are the times that are optimal to fit between Lakeshore East local trains (which depart at :05, :20, :35 and :50 past the hour). The Via train in question departed Union at :02 past the hour and the surrounding GO trains were on time, so allowing the train to depart when it was ready would have incurred little or no impact on GO trains while minimizing delay for the Via train.

Being late is not a reason to delay a train, on the contrary it's a reason to prioritize a train so that the delay can be minimized.


No, the Via train to Toronto was running late, which makes it especially important to prioritize it over trains that are on time and have schedule padding available to make up delays. Especially in cases such as this one where the delay to the on-time train would be negligible if any. The Via train was already in front of the GO train and going over 130 km/h, so the worst case scenario is literally less than a minute of delay while the GO train waits for the switch to change, after which it would have an unobstructed shot to Union because the Via train would be long gone. A Via train to Windsor was holding in Union Station waiting for the Via train to arrive, and because of the additional 10 minutes of delay that Metrolinx created in addition to the original delay, that train to Windsor departed 10 minutes late, allowing delays to continue propagating across the Ontario rail network.

From what I've observed from Metrolinx dispatching, the decision between letting the GO train go first or the Via train has nothing to do with the delay to either train. If the Via train is late, the GO train goes first. And if the GO train is late, the GO train goes first.
View attachment 568904
View attachment 568906

If Metrolinx were a for-profit company then it would be understandable that they prioritize their own trains regardless of how much delay that will cause to other train operators relative to how much delay their trains would save. But they are not a private company. They are a government agency so their duty is to the citizens of Ontario, including those in Via trains. As such they should be dispatching their railways in the way that minimizes delay to train passengers, including those in Via trains. In effect, Metrolinx should be operating as a rail infrastructure manager, for whom Via and GO are simply two Train Operating Companies that are their customers. The train that gets prioritized should be the one that will minimize the overall impact on the Ontario rail network, not simply the one that's green.
Click to expand...
It's moronic how difficult it is for 2 transit agencies to work out together for trains departing max every 15 min and hourly, meanwhile places like Tokyo station with multiple operators, dozens of lines, local, rapid and limited express trains, departing every other minute, all with their own self interests yet they are able to work together to deliver pin point accuracy to their schedules down to the second. Makes us look like novices in this business. Not even amateurs
 
reaperexpress said:
I don't know why the train was late arriving from the maintenance centre. Maybe Via screwed up, or maybe Metrolinx failed to give them a slot to exit the yard. Both have happened before.

What I do know is that 19 minutes of delay was actively caused by Metrolinx. Eastbound Via trains are scheduled to depart Union at :02, :17, :32, and :47 past the hour because those are the times that are optimal to fit between Lakeshore East local trains (which depart at :05, :20, :35 and :50 past the hour). The Via train in question departed Union at :02 past the hour and the surrounding GO trains were on time, so allowing the train to depart when it was ready would have incurred little or no impact on GO trains while minimizing delay for the Via train.

Being late is not a reason to delay a train, on the contrary it's a reason to prioritize a train so that the delay can be minimized.


No, the Via train to Toronto was running late, which makes it especially important to prioritize it over trains that are on time and have schedule padding available to make up delays. Especially in cases such as this one where the delay to the on-time train would be negligible if any. The Via train was already in front of the GO train and going over 130 km/h, so the worst case scenario is literally less than a minute of delay while the GO train waits for the switch to change, after which it would have an unobstructed shot to Union because the Via train would be long gone. A Via train to Windsor was holding in Union Station waiting for the Via train to arrive, and because of the additional 10 minutes of delay that Metrolinx created in addition to the original delay, that train to Windsor departed 10 minutes late, allowing delays to continue propagating across the Ontario rail network.

From what I've observed from Metrolinx dispatching, the decision between letting the GO train go first or the Via train has nothing to do with the delay to either train. If the Via train is late, the GO train goes first. And if the GO train is late, the GO train goes first.
View attachment 568904
View attachment 568906

If Metrolinx were a for-profit company then it would be understandable that they prioritize their own trains regardless of how much delay that will cause to other train operators relative to how much delay their trains would save. But they are not a private company. They are a government agency so their duty is to the citizens of Ontario, including those in Via trains. As such they should be dispatching their railways in the way that minimizes delay to train passengers, including those in Via trains. In effect, Metrolinx should be operating as a rail infrastructure manager, for whom Via and GO are simply two Train Operating Companies that are their customers. The train that gets prioritized should be the one that will minimize the overall impact on the Ontario rail network, not simply the one that's green.
Click to expand...
GO trains pride themselves on being on time. It is not a surprise that the Via would need to wait so that a GO train was able to keep its schedule. Thsi does beg the question about what will happen with Via HFR and Go 2WAD when they are operating in the same tracks.
 
In terms of Metrolinx dispatching, from riding the Milton line, I'd say that Milton is always the least prioritized because we are literally always waiting for signals without fail. So clearly someone else is prioritized ahead of Milton trains, whether that's Lakeshore or Georgetown trains or both, but I'm sure Milton has the lowest priority for them.
 
reaperexpress said:
Being late is not a reason to delay a train, on the contrary it's a reason to prioritize a train so that the delay can be minimized.


No, the Via train to Toronto was running late, which makes it especially important to prioritize it over trains that are on time and have schedule padding available to make up delays. Especially in cases such as this one where the delay to the on-time train would be negligible if any. The Via train was already in front of the GO train and going over 130 km/h, so the worst case scenario is literally less than a minute of delay while the GO train waits for the switch to change, after which it would have an unobstructed shot to Union because the Via train would be long gone. A Via train to Windsor was holding in Union Station waiting for the Via train to arrive, and because of the additional 10 minutes of delay that Metrolinx created in addition to the original delay, that train to Windsor departed 10 minutes late, allowing delays to continue propagating across the Ontario rail network.
Click to expand...
There is a problem with this line of thinking, from a railroading standpoint.

The dispatching organization also runs their own trains, and so has a vested interest in the timeliness of those trains.

They have no so interest in the timeliness of the trains that they allow from other organizations.

Until such a time that on-time performance metrics get tied into the remuneration for allowing those trains to operate on the track, there is zero incentive to fix it.

Dan
 
You must log in or register to post here.

Back
Top