metman
Global Moderator
5056 05/12/1961-23/04/2012 RIP
Posts: 7,421
|
Post by metman on Oct 28, 2010 15:58:05 GMT
More signalling problems this afternoon
What sort of service was being run? Were trains reversing at Chalfont N-S or were some being routed to Chesham and the shuttle was being held in the bay?
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Oct 28, 2010 16:27:38 GMT
Because of a signal mains failure I believe services are being reversed n>s at chalfont, some trains are turning at Ricky and Chilterns are suspended
|
|
|
|
Post by knap on Oct 28, 2010 18:08:36 GMT
The 17:27 ex Marylebone got through to Amersham, as did the previous service. At Amersham there were a croud of people and a coach outside with destination Chalfont on it. I did not hear any announcements (did not hear any at stations on route) so don't know what alternatives were being offered for Met users, I thought it best not to hang around but get clear to help with the congestion. The Chiltern driver announced signal problems when he got to Chalfont and was held. My wife had told me about the problems as she was on the train ahead of me, picking it up at Harrow. My Iphone app told me the line was susepnded Rickmansworth to Amersham, yet Chiltern seemed to be getting through. I assume it was best to let them through on some sort of emergancy signal arrangement and hold met trains out of the way.
|
|
|
|
Post by citysig on Oct 29, 2010 8:34:39 GMT
At around 1450 the northbound Chiltern RHTT encountered a signalling problem just north of Amersham. This was immediately followed by a further failure of a signal at Amersham.
Whilst the second failure was being dealt with, a loss of the signal main (the electricity supply to the signalling equipment) was experienced.
To begin with, services were either reversed at Chalfont, or diverted to Chesham. However after some time, the problems at Amersham spread to Chalfont, and although the loss of control was intermittent at Chalfont, the decision was taken to suspend the Met service north of Rickmansworth.
We then introduced a method of block working (known as point to point working) between Chalfont and north of Amersham to enable certain northbound Chiltern services to operate through the area.
The problems went on until around 2130, when signalling was mostly restored and a through service re-introduced.
The issue with information:
There is no longer a "long-line" Public Address system, so no announcement from our room could be made to inform everyone of what was going on. This problem was made worse by the fact that many of the available station staff (and there's not that many at that end of the line) were occupied either on the track for large amounts of time (securing pointwork) or were outside their stations dealing with taxis or buses. So whilst the staff knew what was going on, it wasn't always possible for them to let everyone else know. To be frank, I think those on duty did an excellent job in moving what people we did.
The geography of the area (it is by no means central London) meant that it took a fair amount of time to source replacement bus services. Taxis were laid on at some stations relatively quickly.
|
|
cso
Posts: 1,043 
|
Post by cso on Oct 29, 2010 9:05:46 GMT
According to Chiltern, this was due to water in an LU Relay Box which affected signals in the Amersham area. twitter.com/#!/chilternrailway |
|
|
|
Post by citysig on Oct 29, 2010 9:31:22 GMT
Technically (and I suppose politically) it was water ingress to a relay / transformer box which does indeed control an LUL signal. The signal concerned allows trains to leave LU metals and go back onto NR. The box concerned is located beyond the LU/NR boundary on the NR side. Whilst it is believed to be LU equipment, it is not us who have introduced a high pressure leaf-clearing train which sprays water everywhere this autumn  ;D (This last part is merely speculation on the part of the team who had to try and run the service last night). |
|
cso
Posts: 1,043
|
Post by cso on Oct 29, 2010 10:43:49 GMT
I have to say, that would be a somewhat ironic cause of the problem  |
|
;D
