News   Mar 13, 2026
 420     3 
News   Mar 13, 2026
 409     0 
News   Mar 13, 2026
 696     0 

Metrolinx: Other Items (catch all)

Not sure if it's the right place to ask but has anyone ever had to escalate presto issues with metrolinx?

I was charged to aldershot 2x when I paid by credit card, for some reason both taps were counted as a tap on! they admitted it was wrong and I'll get a refund that was well over a month ago, with follow up calls telling me to keep waiting.
I guess another real life data point of presto sucking!

View attachment 721144
Try your MPP as one option.
 
This could go in the GO service thread, or here, I'll plunk it here:


Long and short, there was an 'incident' on January 5th that involved a near derailment of a GO Train at speed, near Oakville Stn.

The trail blew through a stop signal at 112 km/ph and then through a switch, changing tracks, at that speed, whereas the switch was rated for 24km/ph.

Excerpts of the article follow:

1773406607590.png


Gareth Dennis, a UK-based railway engineer w/Mx experience is quoted:

1773406674734.png


In the piece we find:

1) A internal report from Mx was due within 60-75 days, said report has not been published or made public.

2) The Federal Transportation Safety Board is not investigating

3) Alstom declined to comment. Mx offered the usual fluff.

***

Also discussed, a past committing to delivering modern Train Protection systems such as ECTS, but that they are not in place and that no timeline for delivery has been announced.

and

That the TSB is concerned about regulatory oversight of GO. From a 2023 Report:

1773406922806.png


****

Overall, an excellent, insightful piece from @atakagi1 I highly commend it.

@crs1026

@smallspy
 
One interesting detail I noted was the use of the term "signal passed at danger" which is UK terminology.

In North America the term would be "movement exceeds limits of authority" or more specifically a violation of CROR Rule 439 (which defines a 'stop' signal)

For context, one can find data here
https://www.tsb.gc.ca/eng/stats/rail/2024/sser-ssro-2024.html#tsb-common-toc-57hlu64omqp-item-4 (frustrating failure of my tablet word processor rhat won't let me embed the link, sorry)
on how often this is happening in Canada. ML data will not appear in this tabulation because ML is not required to report incidents to Ottawa. The fact that similar data is not made public at provincial level is indeed a serious failure in public transparency.

Without knowing the details of this incident (which we should not prejudge) one can be fairly certain that a train which reached a stop signal at the reported 112 km/h should have already passed one or more ""approach" signals which would have indicated a need to slow down and prepare to stop.

The reality is, in Canada "limits to authority" in signalled territory are managed by human beings reading and interpreting the colour and indication of visual signals, with no technological oversight. This is why PTC has been implemented in the US already - Canada lags behind this advance. ML is beginning to test advanced train control, but slowly - and it's not an implementation that happens in a flash.

The lack of provincial regulatory oversight has been flagged in the past - I recall a similar warning after a fatal incident in Kitchener, will try to find that report. And personally I would trust TSB investigators more than a fledgling Ontario rail safety investigator if one were ever established.

No one likes regulation, but a public institution that moves thousands of people every day should expect to have intrusive safety inspections. And better technology. And be required to account publicly for failures.

- Paul
 
Last edited:
worth noting MX said the crew for this incident had been dismissed.

Probably means some mistake they dont want people to know about
 
worth noting MX said the crew for this incident had been dismissed.

Probably means some mistake they dont want people to know about

One has to remember that in a unionised setting, which GO operations is, the decision to terminate someone for cause requires a great deal of due diligence as it can be challenged at arbitration. In other words, if the employer is saying that they proceeded to terminate, it means they have investigated and have amassed a body of facts that they believe justifies the firings. So, if they have that investigation and analysis, why is it not public ? ( Arbitration awards, especially in railway space, do reach the public domain.....much later)

It is quite possible that the public disclosure that people were fired is part of a PR strategy and is less than the complete story about causes and mitigating factors. It would not be the first time that firings (and later reinstatements) were decided by legal and PR considerations. The firing is public theatre and satisfies the court of public opinion, the legal decision comes later and may be settled in the back room. I have seen this done in my own career.

So, I don't trust this disclosure as final word on the matter. That's why we need independent third party investigations by safety experts.

- Paul
 

Back
Top