• Our new ticketing site is now live! Using either this or the original site (both powered by TrainSplit) helps support the running of the forum with every ticket purchase! Find out more and ask any questions/give us feedback in this thread!

Train running with 2 headcodes simultaneously

Status
Not open for further replies.

SprinterMan

Established Member
Joined
20 Sep 2010
Messages
2,341
Location
Hertford
On a Sunday, both the 1150 and 1250 Holyhead - London Euston Virgin trains services run as a single Voyager as far as Chester, where they are coupled up to another Voyager to run to London as 10 cars. As far as I can tell, the Voyager that is attached at Chester runs with a separated headcode to the one from North Wales, despite forming the same train. Why is this? It seems really unusual.

1A35 1150 Holyhead to London Euston
1Z35 1330 Chester to London Euston

1A43 1250 Holyhead to London Euston
1Z43 1433 Chester to London Euston

Adam :D
 
Sponsor Post - registered members do not see these adverts; click here to register, or click here to log in
R

RailUK Forums

Simon11

Established Member
Joined
7 Nov 2010
Messages
1,389
I've heard that there is a plan during engineering work this year which will involve two different toc's trains coupling up together which will both have the same headcode until they split.
 

High Dyke

Established Member
Joined
1 Jan 2013
Messages
5,006
Location
Yellabelly Country
Info shows that the train runs with the 1A** headcode throughout, no mention of a 1Z** working - not last Sunday anyway. It's no different to strengthening any other service - in some cases the unit being attached may have been formed from an ECS.

EMT Norwich - Liverpool services are mostly booked for 4-cars between Nottingham and Liverpool (2-cars between Norwich & Nottingham), however out and back workings keep the same headcode for onward journies regardless of how the train is formed. i.e. 1R** to Liverpool, 1L** to Norwich.

This isn't to say that it doesn't happen; but it's usually an STP train that causes a change of headcode.
 

SprinterMan

Established Member
Joined
20 Sep 2010
Messages
2,341
Location
Hertford
I've heard that there is a plan during engineering work this year which will involve two different toc's trains coupling up together which will both have the same headcode until they split.

Grand Central and Hull Train do this, but this is not an example of that. This is VT doing something very unusual indeed.

Info shows that the train runs with the 1A** headcode throughout, no mention of a 1Z** working - not last Sunday anyway. It's no different to strengthening any other service - in some cases the unit being attached may have been formed from an ECS.

EMT Norwich - Liverpool services are mostly booked for 4-cars between Nottingham and Liverpool (2-cars between Norwich & Nottingham), however out and back workings keep the same headcode for onward journies regardless of how the train is formed. i.e. 1R** to Liverpool, 1L** to Norwich.

This isn't to say that it doesn't happen; but it's usually an STP train that causes a change of headcode.

The Chester starting half has a 1Z** headcode, but the Holyhead half retains the 1A** headcode throughout.

Adam :D
 

Tomnick

Established Member
Joined
10 Jun 2005
Messages
5,933
Clearly the 1Zxx schedules aren't regularly used - are they perhaps there to start the Chester portion right time if the Holyhead portion is delayed (waiting for a boat?). Just guessing!
 

Qwerty133

Established Member
Joined
7 Oct 2012
Messages
2,622
Location
Leicester/Sheffield
On a Sunday, both the 1150 and 1250 Holyhead - London Euston Virgin trains services run as a single Voyager as far as Chester, where they are coupled up to another Voyager to run to London as 10 cars. As far as I can tell, the Voyager that is attached at Chester runs with a separated headcode to the one from North Wales, despite forming the same train. Why is this? It seems really unusual.

1A35 1150 Holyhead to London Euston
1Z35 1330 Chester to London Euston

1A43 1250 Holyhead to London Euston
1Z43 1433 Chester to London Euston

Adam :D

Can't be bothered to look if this is still the case but on 19th jan the 17:09 ex euston ran with two head codes to Chester where it split
 

Rich McLean

Established Member
Joined
6 Feb 2012
Messages
1,757
Pretty sure its there in the case of delays on the North Wales coast, so that the Chester portion can leave on time on its own using its own head-code. Once joined up, the Holyhead head code is used for the job.
 

IrishDave

Member
Joined
30 Jun 2009
Messages
471
Location
Brighton
On a Sunday, both the 1150 and 1250 Holyhead - London Euston Virgin trains services run as a single Voyager as far as Chester, where they are coupled up to another Voyager to run to London as 10 cars. As far as I can tell, the Voyager that is attached at Chester runs with a separated headcode to the one from North Wales, despite forming the same train. Why is this? It seems really unusual.

It also happens every weekday, but in the other direction - the 1710 and 1910 Euston-Holyhead have two headcodes, 1D91/1Z91 and 1D93/1Z93. Presumably they both run as 10-car to Chester where the rear 5-car detaches. The headcodes have been like that for a while; in fact, I think it's been that way since the last timetable recast in December 2008. Since this is the other direction, I think that rules out the possibility that it's so you can start the 5-car short at Chester if the portion from Holyhead is late.

The only other idea I had was that there's some computer system that Virgin use for allocating rolling stock to services, and it gets confused with mid-journey attachments/detachments. In particular, they seem to have a separate headcode if, and only if, a unit attaches or detaches without having been, or becoming, a separate service. So the 1710 and 1910 Euston-Holyhead have a separate headcode for the Chester portion, because they just terminate at Chester and don't form a new service immediately; but the 1810 Euston-Holyhead/Wrexham is 1D92 which detaches 1J32. Similarly, with the up trains in the morning, 1R13 joins 1K14, and 1R24 joins 1D25. Because there's already a separate headcode for them to join/divide, they don't need to invent one to make the system work.

Just a guess, anyway...
 

DarloRich

Veteran Member
Joined
12 Oct 2010
Messages
32,909
Location
Fenny Stratford

Tomnick

Established Member
Joined
10 Jun 2005
Messages
5,933
It also happens every weekday, but in the other direction - the 1710 and 1910 Euston-Holyhead have two headcodes, 1D91/1Z91 and 1D93/1Z93. Presumably they both run as 10-car to Chester where the rear 5-car detaches.
But the combined train must run as one or the other in each case - as previously suggested, one train can't run under two headcodes simultaneously!
 

Derek Wilson

Member
Joined
1 Apr 2011
Messages
9
Location
Mansfield
Looking at Realtime Trains for today, 1Z35 didn't run, 1A35 was used for the whole train. Has as been stated, it is probably in case the Chester portion has to run on it's own, if the Holyhead portion was running late, or maybe cancelled due to failure etc. It saves having to wait for a VSTP shedule & keeps it running to time.

regards Derek Wilson
 

455driver

Veteran Member
Joined
10 May 2010
Messages
11,329
The 1Zxx headcodes are in the system "just in case", the train runs with the 1Axx headcode normally.
 

Tom

Member
Joined
19 Jan 2008
Messages
868
Location
35,000ft
My understanding is that the 1Zxx trains are principally there for hacks with the retail systems to try and push reservations towards certain coaches
 

dk1

Veteran Member
Joined
2 Oct 2009
Messages
19,848
Location
East Anglia
Live Boards for Euston frequently shows the xx.38 arrival from Chester as 'Delayed'. A quick check above or below will then show the xx.38 arrival from Holyhead as 'On time'. this has been happening ever since the VHF timetable began.
 
Status
Not open for further replies.

Top