Yes 5 & 8 are both currently at OOCAh, thanks for the confirmation - clearly 345038 remains a 7-car. The move at 0900 was the locomotive arrival.
So 345005 and 345008 both at Old Oak currently?
Yes 5 & 8 are both currently at OOCAh, thanks for the confirmation - clearly 345038 remains a 7-car. The move at 0900 was the locomotive arrival.
So 345005 and 345008 both at Old Oak currently?
Are both in for 9-car conversion or just one of them?Yes 5 & 8 are both currently at OOC
Not sure, sorry. Both are there, 5 was in 7 car formation the other day.Are both in for 9-car conversion or just one of them?
7-car seems more likely. No need to drag a 9-car unit.37800 dragged 9 car 345038 on yesterdays 5Q50 OOC to Ilford.
Just 15 7-car units now - that is 003/006/007/009/011-017/022/038/042/056, all to be found on the east side of the operation.i am going to London after a long break away from spotting and am interested to find out which 345s are still running in 7-car formation. I seen on this site that there are about 18 sets yet to be converted to 9-car. Does anyone please have a list of which are still 7-car
Trial Running happened on Tuesday and Wednesday this week but with an earlier finish time - eg units back onto depot around 5pm - 6pm instead of around two hours later.Does anyone know what has happened to Trial Running? I have been away and not able to check every day, but the days I did check in the last two weeks I have not seen anything running in the central section.
Thanks. That explains it I was only looking on signalmaps after 6:30. I wonder if they are short of drivers because of Holidays and/or Pings from the App. I see some engineering trains on the COS today so maybe it's just to leave days for other work.Trial Running happened on Tuesday and Wednesday this week but with an earlier finish time - eg units back onto depot around 5pm - 6pm instead of around two hours later.
I was checking RTT and a 12tph (5min frequency) service was running on Wednesday at least. There were some delays early on, but on-time running was achieved in the middle of the day:Trial Running happened on Tuesday and Wednesday this week but with an earlier finish time - eg units back onto depot around 5pm - 6pm instead of around two hours later.
I have been wondering if they are actually trying to achieve 12tph or practice what should happen when something goes wrong.I was checking RTT and a 12tph (5min frequency) service was running on Wednesday at least. There were some delays early on, but on-time running was achieved in the middle of the day.
Definitely not short of drivers. They are doing additional works which is reducing the time / days of operation.Thanks. That explains it I was only looking on signalmaps after 6:30. I wonder if they are short of drivers because of Holidays and/or Pings from the App. I see some engineering trains on the COS today so maybe it's just to leave days for other work.
Definitely not short of drivers. They are doing additional works which is reducing the time / days of operation.
I believe it's Monday to Wednesday next week. The 12tph service is proving very difficult to achieve reliably. Apparently they are trying to introduce new control methods so that when things go wrong, they can get back on track sooner.
I think it's probably too early to be drawing conclusions like that.There has to be something that is causing this, and must be to do with automatic operation. Not being able to run 12tph seems odd when many other lines (into Waterloo, London Bridge, Liverpool St etc are operating at 22-24 tph everyday (with mixed fleets, which have performance variations)
Now if someone had said struggling to push it upto 27, 30 or 32tph then I could understand, but struggling to reliably get half of frequency that is elsewhere suggests new system is not fit for purpose in current form. Especially as only using one type of train where each can accelerate and brake at same rate.
That is because it came 'into service' at Whitechapel Crossrail under the trial running timetable, having been empty stock from Gidea Park.I just saw an interesting thing on Signal Maps. 5Y58 Gidea Park to Whitechapel Crossrail, changed its headcode to 9Y58 after arriving at Whitechapel and continued to Paddington.
I don't think it is indicative of that other than for empty stock movements that then come into service.I am wondering if this is what might happen when the through service from Shenfield to Paddington starts.
They are unlikely to stay as they are - 9Pxx used on the west side appears to denote Paddington at present (consistent with 1Pxx and 2Pxx used by GWR for Oxford / Didcot / Reading to Paddington) and all the east side operation is currently under 2Xxx headcodes - eg 2Wxx for Shenfield. A west side to east side service terminating at Shenfield might be 9Wxx throughout.Does that mean headcodes on the GWML and GEML will have to continue as they are and switch when entering or leaving the COS?
Thank you.That is because it came 'into service' at Whitechapel Crossrail under the trial running timetable, having been empty stock from Gidea Park.
They are unlikely to stay as they are - 9Pxx used on the west side appears to denote Paddington at present (consistent with 1Pxx and 2Pxx used by GWR for Oxford / Didcot / Reading to Paddington) and all the east side operation is currently under 2Xxx headcodes - eg 2Wxx for Shenfield. A west side to east side service terminating at Shenfield might be 9Wxx throughout.
On class 345 matters, 345008 appears to have been on shunts at Old Oak Common to the first signal berth this morning.
Something a bit awry with the RTT log for 9Y58, - it left Liverpool St at 09:34 and arrived at Farringdon at 09:34. Impressive or what?That is because it came 'into service' at Whitechapel Crossrail under the trial running timetable, having been empty stock from Gidea Park.
5Y58 0945 Gidea Park C.H.S. to Whitechapel Crossrail
https://www.realtimetrains.co.uk/service/gb-nr:54884/2021-08-23/detailed
9Y58 1015 Abbey Wood (Crossrail) to Paddington Crossrail started at Whitechapel
https://www.realtimetrains.co.uk/service/gb-nr:C69487/2021-08-23/detailed
Empty stock moves from Gidea Park to Old Oak Common run as 5Xxx throughout.
I don't think it is indicative of that other than for empty stock movements that then come into service.
They are unlikely to stay as they are - 9Pxx used on the west side appears to denote Paddington at present (consistent with 1Pxx and 2Pxx used by GWR for Oxford / Didcot / Reading to Paddington) and all the east side operation is currently under 2Xxx headcodes - eg 2Wxx for Shenfield. A west side to east side service terminating at Shenfield might be 9Wxx throughout.
On class 345 matters, 345008 appears to have been on shunts at Old Oak Common to the first signal berth this morning.
53 seconds between stations - seeSomething a bit awry with the RTT log for 9Y58, - it left Liverpool St at 09:34 and arrived at Farringdon at 09:34. Impressive or what?
53 seconds between stations - see
- - TrackIT!
trackit.uppyjc.co.uk
Depart Liverpool Street 10:34:05
Arrive Farringdon 10:34:58
Not sure what the rounding convention is in RTT for these services but not sure it is necessarily awry.
Thank you.
That is because it came 'into service' at Whitechapel Crossrail under the trial running timetable, having been empty stock from Gidea Park.
5Y58 0945 Gidea Park C.H.S. to Whitechapel Crossrail
https://www.realtimetrains.co.uk/service/gb-nr:54884/2021-08-23/detailed
9Y58 1015 Abbey Wood (Crossrail) to Paddington Crossrail started at Whitechapel
https://www.realtimetrains.co.uk/service/gb-nr:C69487/2021-08-23/detailed
Empty stock moves from Gidea Park to Old Oak Common run as 5Xxx throughout.
I don't think it is indicative of that other than for empty stock movements that then come into service.
They are unlikely to stay as they are - 9Pxx used on the west side appears to denote Paddington at present (consistent with 1Pxx and 2Pxx used by GWR for Oxford / Didcot / Reading to Paddington) and all the east side operation is currently under 2Xxx headcodes - eg 2Wxx for Shenfield. A west side to east side service terminating at Shenfield might be 9Wxx throughout.
On class 345 matters, 345008 appears to have been on shunts at Old Oak Common to the first signal berth this morning.
Interestingly, this documentation does not cover the 2X## headcodes described earlier in the thread as running in the East.The Crossrail train planning rules are uploaded online (http://content.tfl.gov.uk/ttpr-2021.pdf) which include the headcode definitions for Crossrail/EL:
The Crossrail train planning rules are uploaded online (http://content.tfl.gov.uk/ttpr-2021.pdf) which include the headcode definitions for Crossrail/EL:
Interestingly, this documentation does not cover the 2X## headcodes described earlier in the thread as running in the East.
I suppose they have simply inherited the Class 315's headcodes, and are covered under "TfL Rail" rather than "Crossrail". I wonder whether the peak Liverpool Street High Level services will continue with 2X## after the COS opens?
So it seems to me that only trains that go into the COS will have a 9 prefix.
Curious then, that there is a letter prefix for Paddington High Level in the XR doc, but not for Liverpool Street High Level.I checked out the Anglia Timetable Planning Rules https://sacuksprodnrdigital0001.blob.core.windows.net/operational-rules/Operational Rules/TPR 2022/V4/TPR 2022 V4 AR.pdf for May 2022 and on page 9 they say:
So it seems to me that only trains that go into the COS will have a 9 prefix.
Curious then, that there is a letter prefix for Paddington High Level in the XR doc, but not for Liverpool Street High Level.