There were severe delays caused by a signal failure at High Street Ken plus further delays caused a passenger taken ill at Monument.
If controllers could foresee a log jam of Circle/H&C services, they may have chosen to bail services early as your colleague described at Baker Street (MET) given that gaps in City services heading out can be as much as 5-6mins making backing from platform 2 via Baker St Junction and 32 points tight but still plausible.
Since 2010, the track layout immediately north of Baker Street can’t facilitate a NB to SB (City) move since the scissors crossover has been replaced with a diamond crossing between the NB and platform 4. Even pre 2010, I don’t think the area was signalled up to do such a move.
Next reversal point heading north would be 6 points at Swiss Cottage (Disused) which would take up more time than reversing in situ. Still if they did what was described above, hats off to controllers as it appears that they got away with the move not affecting MET services.
Most strange. Please could you check from 0900 to 0930 - he is quite a late arriving person coming in from darkest Essex. It was definitely a Circle Line service he picked up at Liverpool Street. Commuters being creatures of great habit, they all ended up looking very confused at Baker Street - he said - having ended up at a platform most had never seen before. Might as well have been Platform 9 3/4 !
Thought, before GoldenArrow's post, that someone had taken 'a wrong un'.
Just a thought, would the controller have had to renumber the Circle Line service before the system would send it up the Met to reverse in p2?
This may or may not be the same train, but arriving at Aldgate yesterday (c. 0820) I found, as usual, a Met train in P3 whilst I waited on P4 for the Circle Line to Hammersmith. About a minute before the Met train departed, the announcement "The destination of this train has changed, this is now a Circle Line train to Hammersmith" was played and the displays reflected this. I waited on the platform regardless since I was skeptical, and as it pulled away I can confirm it was definitely an S8 with Circle Line descriptors. I am very much assuming that this train, being an S8, didn't actually transpire to be a Circle Line train for its duration!
Now that I’ve calmed down a bit, this video was shot by myself on 23rd October at 14:51 PM, annoyingly my phone was so grimy from spending over four hours on the Bakerloo that it couldn’t focus on the train number or unit number either. Although I have posted the part of the video that excludes my mini rant at how dirty my phone is, the full video does show seven cars.
Child of Middlesex, student of the City, resident of the Metropolitan
Right. Let's get some misconceptions out of the way, and answer some questions.
1. S7s are not "rare" in either Met platform. There are two booked daily movements to and from Neasden for stabling purposes, one at the start of the day and one at the end of the day.
2. Even during the day, S7s are not "rare" in either Met platform. Although not in service, there are scheduled stock movement paths (in the 7xx series) to transfer stock around the various depots. I expect that this is what is see in the video above.
3. It is not unheard of for S7s to run to platform 2 in service, before terminating and returning to the City. Unless crewed by a Met driver, or with pilot, they cannot run north with C&H crews. This can be done either to recover late running (very unusual though) or a a result of a failure or wrong signal lowered. Remember, controllers and signallers are looking at the bigger picture.
4. There is no need to renumber a train if it is running onto other line, unless that number will clash with one already running. There is no overlap between any numbers on the SSR and Piccadilly (and also Jubilee).
5. The S stock TCMS is S L O W. It is very easy for the wrong destination code to be entered, which is what will have happened on the above S8. There are codes for C&H and Met destinations with common numbers - see previously when C&H trains have had Ruislip up.
As for the initial point, again no C&H trains ran into P2 between 0900 and 0930. Indeed, checking other information available to me, no C&H trains were diverted into platform 2 at all yesterday.
Post by norbitonflyer on Nov 13, 2018 14:19:57 GMT
Is it possible the train was misdescribed on leaving Aldgate, but corrected before it got to Baker Street? As I understand it, the train numbers are three-digit octal numbers, each digit a being triplet of bits (binary digits). If so, transposing the first two bits would turn a Met (4xx, or 100 xxx xxx into a Circle (2xx, or 010 xxx xxx). If the train was set up as a 2xx, it would display that error on its onboard systems and pass that information to the "Next Train" indicators on the platforms. Not sure whether the signalling system would also treat it as a Circle in such cases, but if so, as long as the driver spotted the problem before being sent the wrong way at Baker Street it could be fixed. Thus when it arrived at Baker Street it would be shown as a 4xx. Whether Trackernet would show a 2xx mysteriously transmogrifying into a 4xx en route I wouldn't know! (Or would Trackernet show the correct number despite what the train was reporting itself to be?)
And the reason everyone got out at Baker Street (even though it was a Met service going to ?Amersham/Chesham/wherever) would be because anyone waiting for a Met between Aldgate and Gt Portland Street would have let it go as it appeared to be a circle.
Post by aslefshrugged on Nov 13, 2018 15:02:15 GMT
On the Central Line the boards on the platform and Trackernet get their information from the signal system not from the destination displayed by the train, I assume its the same on others lines. Its not unknown for trains to go westbound with Epping or Hainault via Newbury Park on the front by mistake but the platform boards and Trackernet will be showing the correct destination.