tbtc
Veteran Member
Without wanting to disrupt the “Northern 153s” thread further (https://www.railforums.co.uk/threads/what-are-northerns-plans-for-their-10-class-153s.196181/), what is the most inefficient use of stock (and what was the most inefficient use of stock historically)?
For example, Northern are going to need two DMUs and two sets of staff to run the Huddersfield – Bradford shuttle because a single DMU cannot provide the hourly service, despite a round trip by rail being under thirty eight miles (a single journey is 18 miles 60 chains).
Yup - one train cannot reliably cover thirty eight miles in an hour (obviously allowing for station dwells, turnaround), so a TOC struggling to resource sufficient trains/staff on a daily basis is having to use two sets on this short local shuttle.
But there must be other examples where the need for an incoming unit to meet an outgoing path means that the dwell time is significant. Or a train spends almost as long at the terminus as it does on the journey.
The timetable EMR inherited from EMT means that the “fast” Nottingham service to London sits at St Pancras for seventy minutes (because services on the MML are divided into HSTs, short 222s and long 222s, so the HST used on the southbound service needs to wait for an HST path north (and ten minutes would be insufficient turnaround time to provide a reliable northbound service, so it has to wait seventy minutes – hopefully this will change when the long distance EMR services are run by one type of train – the 804).
What other examples are there (or were there)? E.g. when a frequent core splits into different branches, but one of the branches is slightly longer than the others, so units have to wait significantly longer than the other branches because they’d be too late to fit back into the “core”
(I appreciate that there are arguments about reliability and “having spare capacity” versus “stripping everything to the bare minimum” – and that the layover time needs to be seen in the context of how long the journey was – e.g. an Edinburgh service having a sixty minute layover in London may sound reasonable but a Nottingham service having a sixty minute layover in London may sound excessive - sometimes a long break is required for driver/guard’s “hours” but are there any examples like a train diagrammed to sit at a terminus for a long period each hour because the two paths couldn’t match up)
To avoid argument, I’m talking about off-peak – obviously there are some trains that sit unused between the peaks but you can’t do anything about that – I'm not bothered about trains that are idle from nine in the morning till five at night because there'll always be a need for diagrams like that - whereas you might be able to do something about improving line speeds or introducing faster accelerating trains or removing an intermediate stop to shave a few minutes off journeys to avoid situations like the Huddersfield – Bradford one.
For example, Northern are going to need two DMUs and two sets of staff to run the Huddersfield – Bradford shuttle because a single DMU cannot provide the hourly service, despite a round trip by rail being under thirty eight miles (a single journey is 18 miles 60 chains).
Yup - one train cannot reliably cover thirty eight miles in an hour (obviously allowing for station dwells, turnaround), so a TOC struggling to resource sufficient trains/staff on a daily basis is having to use two sets on this short local shuttle.
But there must be other examples where the need for an incoming unit to meet an outgoing path means that the dwell time is significant. Or a train spends almost as long at the terminus as it does on the journey.
The timetable EMR inherited from EMT means that the “fast” Nottingham service to London sits at St Pancras for seventy minutes (because services on the MML are divided into HSTs, short 222s and long 222s, so the HST used on the southbound service needs to wait for an HST path north (and ten minutes would be insufficient turnaround time to provide a reliable northbound service, so it has to wait seventy minutes – hopefully this will change when the long distance EMR services are run by one type of train – the 804).
What other examples are there (or were there)? E.g. when a frequent core splits into different branches, but one of the branches is slightly longer than the others, so units have to wait significantly longer than the other branches because they’d be too late to fit back into the “core”
(I appreciate that there are arguments about reliability and “having spare capacity” versus “stripping everything to the bare minimum” – and that the layover time needs to be seen in the context of how long the journey was – e.g. an Edinburgh service having a sixty minute layover in London may sound reasonable but a Nottingham service having a sixty minute layover in London may sound excessive - sometimes a long break is required for driver/guard’s “hours” but are there any examples like a train diagrammed to sit at a terminus for a long period each hour because the two paths couldn’t match up)
To avoid argument, I’m talking about off-peak – obviously there are some trains that sit unused between the peaks but you can’t do anything about that – I'm not bothered about trains that are idle from nine in the morning till five at night because there'll always be a need for diagrams like that - whereas you might be able to do something about improving line speeds or introducing faster accelerating trains or removing an intermediate stop to shave a few minutes off journeys to avoid situations like the Huddersfield – Bradford one.