News   Feb 04, 2026
 167     0 
News   Feb 04, 2026
 536     0 
News   Feb 03, 2026
 654     0 

Toronto Eglinton Line 5 | ?m | ?s | Metrolinx | Arcadis

There we are. A collision in the Mount Dennis yard.

ok if thats the case then it shouldnt be too bad since it doesnt affect the mainline. looks like somebody was daydreaming and caused a collision. shouldnt need to restart
 
ok if thats the case then it shouldnt be too bad since it doesnt affect the mainline. looks like somebody was daydreaming and caused a collision. shouldnt need to restart
Agreed with you, if they say testing will resume shortly in that article, would that mean not a restart?
 
This happened in the yard, apparently under automated control with no one driving.
Not apparently.

One of the "features' of the ATC/ATO is completely unattended operation of equipment within the yard limits. This means that trains can be remarshalled, sent for cleaning and servicing, and prepped for entry into service or stored after it without having anyone trackside or onboard.

That the system allowed an accident in this configuration is extremely problematic, as it is set up the same as the mainline signal system and supposed to offer the same safeguards as it - but because it operates at low speeds and without passengers is deemed to be "safe enough" in its current configuration to operate unattended (versus on the mainline, were there would need to be additional measures to protect the trains from the public and vice versa).

If it happened in the yard, it can happen elsewhere in the system. For something as safety-critical as the signal system, that is unacceptable. Which is why it's been closed since Thursday - they need to inspect every single potential route capable within the system and ensure that there are no other "blind spots" that would allow this to happen again. And that's why I'm skeptical that testing will resume quickly.

Dan
 
Not apparently.

One of the "features' of the ATC/ATO is completely unattended operation of equipment within the yard limits. This means that trains can be remarshalled, sent for cleaning and servicing, and prepped for entry into service or stored after it without having anyone trackside or onboard.

That the system allowed an accident in this configuration is extremely problematic, as it is set up the same as the mainline signal system and supposed to offer the same safeguards as it - but because it operates at low speeds and without passengers is deemed to be "safe enough" in its current configuration to operate unattended (versus on the mainline, were there would need to be additional measures to protect the trains from the public and vice versa).

If it happened in the yard, it can happen elsewhere in the system. For something as safety-critical as the signal system, that is unacceptable. Which is why it's been closed since Thursday - they need to inspect every single potential route capable within the system and ensure that there are no other "blind spots" that would allow this to happen again. And that's why I'm skeptical that testing will resume quickly.

Dan
Yet another signal issue!
Correct me if I'm wrong but last time it took several months to fix all the software bugs?
 
When two LRT vehicles collide in the maintenance yard and the line hasn’t opened yet, do they make a sound?

If two Metrolinx executives’ heads collide at a press conference where they declare for the 1500th time they’re making relentless progress, do they sound like two coconuts? 🥥 🥥

Being more serious, this could be an easy fix if e.g. someone entered bad info that the software relied on. But if the software itself messed up even after being given valid data, that’s a disaster. All bets are off for who knows how much longer?

And how likely are we to learn the difference from Metrolinx? A fart’s chance in a hurricane, is how. What a Charlie Foxtrot.
 
When two LRT vehicles collide in the maintenance yard and the line hasn’t opened yet, do they make a sound?
FFS, this is one cursed project.

Super7-Toho_W8_Godzilla-Train_Biter_blind_box_600x600.jpg
 
HOLD ON, HOLD ON! According to the news, the collision happened "Tuesday" which I presume means today, not last week. But we have been noticing testing was stopped all weekend, plus Monday. So the collision is NOT what caused testing to stop. Something else happened, that we don't know about!
Edit: I have been corrected; the collision occurred on Thursday, 5 days ago.
 
Last edited:

Back
Top