From Newsgroup: aus.rail
On 29/3/22 15:33, Sylvia Else wrote:
Trains starts against signal at danger after guard gives incorrect "rightaway" signal.
https://www.atsb.gov.au/media/5781009/ro-2019-009-final-1.pdf
So there are neither catch points nor trip cocks to prevent this from developing into an accident.
QR use a variation of the British AWS system where signals passed at restrictive indications generate an AWS warning that if not
acknowledged, will stop the train.
I once rode into the city in from I think the Cleveland Line in the cab
and about half way in we started to follow another train and were thus
getting caution signals. I noticed the driver was reacting almost
automatically to the AWS warning at each signal I remember at the time
thinking that given cancelling the AWS alarm becomes an automatic action
that it's effectiveness seemed to me, to be limited.
QR didn't do overlaps like NSW does either. Not sure what they do now,
but I also remember being stopped at a signal just before a set of
points and remarking how close we were to the opposing movement. NSW
philosophy assumes a train WILL at some point SPAD the signal so
provides 'overlaps'. This also governs where they put catch points - if
there isn't the space to put an overlap before a junction, they will put
in catch-points.
It would appear in this case the driver DID get an AWS warning, but it
was approaching the platform. There wasn't another AWS magnet after
departure. Looks like they were relying on process (put the reverser to
neutral and apply the parking brake) as a 'driver reminder device'.
NSW hasn't been immune to 'ding ding and away' incidents, but the
mechanical train stop usually pulls them up.
NSW wants to replace the mechanical train stop system with ETCS. However
the project has suffered feature creep and turned int a full blown ATP implementation project.
--- Synchronet 3.21d-Linux NewsLink 1.2