Bordercollie
Senior Member
Probably tracks out of alignment at the Spur.
DSCToronto
Superstar
crs1026
Superstar
Nope. It was a stalled GO train that died right on the key crossovers at Bathurst St. Seems to be taking forever to get a rescue train hooked up to drag the dead train away.
The real issue for ML is how one set of Xovers can kill service on a whole line in USRC. Only so much redundancy exists, especially while the Kitchener line is down to two tracks.
- Paul
Bordercollie
Senior Member
Could they not get around it and bypass some stations?
crs1026
Superstar
How would they do that when the train stalled while crossing over between the only two tracks that are active on the Kitchener line?
- Paul
dowlingm
Senior Member
Does Metrolinx manage Milton tracks between USRC and West Toronto Junction, or does CP manage through Bloor and all the way down to the USRC?
If the latter, it might explain why Metrolinx doesn't try to use the Milton tracks as part of an expanded Kitchener trackage south of Bloor, especially on weekends when no Milton trains are usually running, with an additional switch or switches cut in just south of Bloor Street West.
If the latter, it might explain why Metrolinx doesn't try to use the Milton tracks as part of an expanded Kitchener trackage south of Bloor, especially on weekends when no Milton trains are usually running, with an additional switch or switches cut in just south of Bloor Street West.
Bordercollie
Senior Member
I didn't know it was blocking the actual cross over.
smallspy
Senior Member
Metrolinx manages and dispatches them, but via a plug-in to the CP's signalling system. It's CP's system all the way down to Bathurst.
At some point in the future - honestly not sure if it's near or distant at this point - that whole section is supposed to be cutover to the GO's signalling network, which would greatly simplify what you are suggesting. But as they are two different systems today, putting in a crossover from one to the other (and signalling it) is not an easy proposition.
Dan