• 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!

Most amount of timetable padding?

Status
Not open for further replies.

D6975

Established Member
Joined
26 Nov 2009
Messages
3,053
Location
Bristol
The Night Riviera Sleeper. So much padding it has left Plymouth 102 late and arrived into Paddington 7 early!

I think the up riviera is timed to allow running via Bristol or Yeovil and arriving right time at Padd.
It quite often runs via Bristol, especially during Winter, and is sometimes actually timetabled to stop at TM and Swindon.
 
Sponsor Post - registered members do not see these adverts; click here to register, or click here to log in
R

RailUK Forums

pnepaul

Member
Joined
11 Sep 2012
Messages
192
Location
Carlisle
Today I was on the 13.10 Carlisle to London Euston via Birmingham (12noon ex Glasgow). We had a very leisurely journey between Stafford and Wolverhampton, I presumed we were stuck behind a slower train, however we arrived at Wolverhampton 3 mins early - so I guess a bit of padding in the schedule!
 

crispy1978

Member
Joined
4 Feb 2013
Messages
1,037
Location
Scarborough
There seems to be a generous amount of time for the train between Seamer and Scarborough. Takes 4-5 minutes to get out there, but often 8-9 allowed on the return journey.
 

Boysteve

Member
Joined
25 Apr 2013
Messages
235
Location
Manchester
TPEx can be bad but it's combined over stops. Regularly Manchester to Newcastle trains stop at Leeds for about 6 minutes and then York for 10! That means arrival at Leeds to departure from York of over 40 minutes despite a 24 minute journey between the stops.

I think we should make a distinction with padding time. Some is genuinely to stop delays on one congested part of the nextwork being spread to another (TPEx maybe). Some are to keep clock face patterns when a service moves from one network/region to another, such as EC Highland Chieftan in which case it's not really padding. Genuine padding would mean the Southbound Inverness to LKX service would be scheduled to arrive at Edinburgh at 11:27 not 11:17 as at present.
However padding exists between Peterborough and LKX in spades and should be regulated or curtailed.
 

heart-of-wessex

Established Member
Joined
11 Jun 2005
Messages
3,089
Location
Trowbridge
I've noticed a reverse to padding on one of the Birmingham - Leicesters, in that it is booked to leave Water Orton 2 minutes later in the WTT than in the public timetable, however there is a 2 min path allowance at Landor Street Jn that would probably see it arrive at Water Orton 'on time' by the public TT anyway.

You're right about padding though, some of it is to regain a clockface timetable. I've noticed too in Open Train Times, there are some services that have 1-2 mins engineering allowances, however it seems to be the only train of the day that actually has an allowance but it does bring the times back to it's pattern, for example

Location A: Train 1 pass 08/01, Train 2 pass 09/01, Train 3 pass 10/00 (eng: 1)
Location B: Train 1 pass 08/03, Train 2 pass 09/03, Train 3 pass 10/03
 

The Planner

Veteran Member
Joined
15 Apr 2008
Messages
19,762
Two seperate things, the Landor St allwoance is for something coming across it from St Andrews.
 

heart-of-wessex

Established Member
Joined
11 Jun 2005
Messages
3,089
Location
Trowbridge
Found it, it's 1 minute allowance at Landor Street Jn that adds the time to Water Orton. For at least the whole evening, that's the only XC Leicester that has 1 minute allowance there.

It might be because 1M95 Cardiff - Nottingham is 3 minutes ahead, otherwise nothing close by that crosses over at the junction. However surely that would be 1 minute pathing allowance either case, not 1 minute engineering allowance that it is given (Some TSR allowance that doesn't seem to affect any other train...)
 

The Planner

Veteran Member
Joined
15 Apr 2008
Messages
19,762
In which case that is the reason, 4 minute headway from Landor St to Water Orton IIRC. If 1M95 is 3 ahead then the following one needs bumping out. It is 1 minute pathing and not box time in the schedule.
 

Taunton

Veteran Member
Joined
1 Aug 2013
Messages
12,355
One of the more bizarre is Bidston to Wrexham where the hourly timetable shows all trains taking 60 or 61 minutes, departing at about the same time from each end, yet it just uses two trains, which consistently at Wrexham have to depart on the return journey before the incoming is due to arrive.
 

D6975

Established Member
Joined
26 Nov 2009
Messages
3,053
Location
Bristol
2200 Kings Cross to Newcastle is pretty bad. It sits at York for 26 minutes, and then has pathing allowances of 10 minutes between York and Darlington, and then 20 minutes between Durham and Newcastle. And even though it is set down only after York, the last time I was on it it waited time at Darlo and Durham <(

The padding to York is there for a good reason. This service is booked to run via Knottingley to maintain route knowledge. This means that it's at the mercy of the weekly schedule of coal trains and can get delayed as a result.
 

D1009

Established Member
Joined
22 Feb 2012
Messages
3,166
Location
Stoke Gifford
Of course! I have just realised that what I have read was referring to the Caledonian Sleeper which uses Class 90's :oops:

I would think similar rules would apply though. Is there anyone here who works on the Night Riviera?
I don't work on it, but I'm sure I heard the 57s are restricted to 70 mph on ATP (automatic train protection) fitted routes, because they are not fitted with ATP. Normally they go via the Berks and Hants route which means this is not relevant apart from Padd to Reading.
 

edwin_m

Veteran Member
Joined
21 Apr 2013
Messages
28,784
Location
Nottingham
One of the more bizarre is Bidston to Wrexham where the hourly timetable shows all trains taking 60 or 61 minutes, departing at about the same time from each end, yet it just uses two trains, which consistently at Wrexham have to depart on the return journey before the incoming is due to arrive.

Discussed elsewhere on here recently. It's actually the same train - the turnaround is so short that the padding makes the arrival time later than the scheduled departure.
 

Tetchytyke

Veteran Member
Joined
12 Sep 2013
Messages
17,726
Location
Isle of Man
The padding to York is there for a good reason. This service is booked to run via Knottingley to maintain route knowledge.

RealTimeTrains says it goes straight up the ECML during the week, though I know it usually goes via Knottingley on a Sunday.
 

SeanG

Established Member
Joined
4 May 2013
Messages
1,378
The 2200 often arrives to Newcastle early, and hence to Heaton early.I should know, it often wakes me up
 

D6975

Established Member
Joined
26 Nov 2009
Messages
3,053
Location
Bristol
Real time trains says the 22:00 KGX-NCL runs via Knottingley every day - as it has done for a long time now. Knottingley S Jn at 00:08, Chuch Fenton 00:26, York 00:39/00:42. It is the ECML route that in this case is the diversion and causes the long wait at York when used.
 

Attachments

  • 1N35.jpg
    1N35.jpg
    36.6 KB · Views: 12
Last edited:

Martin_1981

Member
Joined
15 Jul 2011
Messages
274
XC services on the NE-SW route have often been known to leave Birmingham New Street 20 mins late, yet are on time by the time they leave Exeter.

The 0900 Glasgow-Penzance was once 40 mins late leaving Birmingham, having been diverted from Derby via Leicester to Brum, yet it made up all but 2 minutes by St Erth and arrived in Penzance 3 mins early. Scheduled layovers at Bristol TM and Plymouth probably saved 20-25 mins.

A couple of years ago, the 12.24 Plymouth-Glasgow HST left Plymouth 55 mins late and arrived in Glasgow just 6 minutes late, though it did miss out its scheduled stops at Wakefield and Leeds, running instead Sheffield-York via Doncaster which saved around 25 mins.
 

edwin_m

Veteran Member
Joined
21 Apr 2013
Messages
28,784
Location
Nottingham
XC services on the NE-SW route have often been known to leave Birmingham New Street 20 mins late, yet are on time by the time they leave Exeter.

The 0900 Glasgow-Penzance was once 40 mins late leaving Birmingham, having been diverted from Derby via Leicester to Brum, yet it made up all but 2 minutes by St Erth and arrived in Penzance 3 mins early. Scheduled layovers at Bristol TM and Plymouth probably saved 20-25 mins.

A couple of years ago, the 12.24 Plymouth-Glasgow HST left Plymouth 55 mins late and arrived in Glasgow just 6 minutes late, though it did miss out its scheduled stops at Wakefield and Leeds, running instead Sheffield-York via Doncaster which saved around 25 mins.

The "Operation Princess" timetable in 2002 accelerated the XC network to take advantage of the faster timings possible with Voyagers. However performance immediately collapsed and the timings were extended, perhaps too much. Hence the Voyagers have a lot of performance in reserve to recover from any delay.

Diversions to recover from delays are reasonably common, particularly if there is another train following that can take the passengers for the stations missed out. For example I've been on a Nottingham-Leeds diverted via Swinton and a Liverpool-Norwich diverted via Dore South Curve.
 
Last edited:

The Planner

Veteran Member
Joined
15 Apr 2008
Messages
19,762
The "Operation Princess" timetable in 2002 accelerated the XC network to take advantage of the faster timings possible with Voyagers. However performance immediately collapsed and the timings were extended, perhaps too much. Hence the Voyagers have a lot of performance in reserve to recover from any dealsy.

I would argue that a lot of XC running times are inadequate in places as they haven't been altered (and they haven't been altered much). The XC goal is A-B as quickly as possible with long layovers at B to make sure they have a good chance of their onward slot. They make up other time off engineering allowances, which they pick up a lot of on the routes they use and are also trying to get reduced.
 
Status
Not open for further replies.

Top