There’s more to this than just th ORR being mean, the WCRC have not been holding up their end of the bargain:
You are failing to ensure the health and safety of your passengers and crew, thus putting them at risk of serious personal injury, as you are not implementing the controls identified in your risk assessment for rolling stock fitted with secondary door locking, in that:
- Passengers are being told by train crew to operate the secondary door locks;
- Stewards are not preventing passengers from operating the secondary door locks;
- Stewards are not preventing passengers from leaning on train doors or from leaning out of the open droplight windows in train doors of moving trains; and
- Secondary door locks are not in the ‘locked’ position or are being opened by train crew before the train is stationary; Therefore, creating a risk of persons falling from a train or being struck by infrastructure being passed by the moving train.
The WCRC have form for poor adherence to railway operating rules - they’ve been banned before once, see the Wootton Bassett Junction near miss (where one of their steam tours came within under a minute of colliding with a high speed train due to train crew routinely defeating safety systems) - https://en.wikipedia.org/wiki/2015_Wootton_Bassett_rail_incident - in brief, this ended up with WCRC being banned from the national rail network for a time, the notice stating “the operations of WCR are a threat to the safe operation of the railway”.
An older friend of mine told me years back about an incident that happened on a university VAX running Unix. In those days, everyone was using vt100 terminals, and the disk drives weren’t all that quick. He was working on his own terminal when without warning, he got this error when trying to run a common command (e.g.
ls)$ ls -l sh: ls: command not foundSo he went on over to the system admin’s office, where he found the sysadmin and his assistant, staring at their terminal in frozen horror. Their screen had something like:
# rm -rf / tmp/*.log ^C^C^C^C^C^C^C^C^C^C # ls -l sh: ls: command not found # stat /bin/ls sh: stat: command not foundA few seconds after hitting return, and the
rmcommand not finishing immediately, he realised about the errant space, and then madly hammered Ctrl-C to try to stop it. It turns out that the disk was slow enough that not everything was lost, and by careful use of the commands that hadn’t been deleted, managed to copy the executables off another server without having to reinstall the OS.