Jozhua
Established Member
- Joined
- 6 Jan 2019
- Messages
- 1,865
Hello,
Thought I'd start a new thread branching off of the MML electrification regarding Erewash Valley & how we believe it could best fit in with plans for the rail network in the area?
I'll respond to a few people in my next post.
Cheers!
It seems like a fraction of those 4tph between Nottingham and Derby actually seem to run these days - last year it seemed to be about 1tph, now it seems to be 2/3tph depending on the day. Of course there is the painful 10mph speed limit when heading towards Long Eaton. Long Eaton station is also going to be a mess of stopping and express services battling it out, unless they find a way to quad track it...
Thought I'd start a new thread branching off of the MML electrification regarding Erewash Valley & how we believe it could best fit in with plans for the rail network in the area?
I'll respond to a few people in my next post.
Cheers!
The route via Ambergate is very constrained in terms of anything such as quad-tracking. One of the big issues is connectivity for intermediate towns such as Duffield/Belper northwards to Sheffield. At the moment, a pretty mediocre service is provided by the Matlock service stopping, which is often very capacity constrained in rush hour. Another stopping service northwards to Sheffield might mess the whole thing up. Of course, with original HS2 plans bypassing the whole thing, many more services would have been able to stop at Belper, improving regional connectivity.Would it? Comparatively few MML services actually go up it.
So the upgrades should focus on the route via Ambergate, surely?
Why would you switch the Fast and Slows around? There's already a slow on the eastern side, and at Trent the High Level lines are on the east. What really needs sorting out is the Toton/Trent area, as you have the Slow lines on the east side but DB's depot on the west. If the Erewash is to get busier between Trent and Trowell jns then these crossing moves will become problematic. A Flyover allowing High Level trains to get towards Castle Donnington would be wonderful.
All two of them an hour?
The issue isn't necessarily that those HS2 services can't be accommodated, it's just that they can't be accommodated whilst improving local connectivity at the same time. It is likely that to continue to provide the promised journey time benefits, local stopping services will be further constrained.I imagine the 2TPH London-Sheffield service could just be replaced by 2TPH of HS2 service, with the existing service cut back to Derby and possibly a London-Leicester-Nottingham-Sheffield which might even continue to Leeds using the current Northern path. This wouldn't increase the number of trains on any section except EM Parkway to Derby.
IRP has brought us back to express services battling it out with local, regional and freight...brilliant.The main issue seems to be congestion around the Trent Triangle. Some years ago, it took a lot of shifting the timetable around to allow 4tph between Nottingham and Derby. (The 4tph were to Birmingham x2, Crewe, Matlock). I don't think they could have found space for a fifth.
The IRP says that if HS2 is to join the MML south of East Midlands Parkway, then it would be necessary to grade-separate the flows from Nottingham to Derby and MML/HS2 to Nottingham. To do that around Trent Triangle would be very expensive. (Discussed here: https://www.railforums.co.uk/thread...-and-capacity-through-trent-junctions.225009/ )
So I fully expect that DfT/HS2 will ignore the IRP recommendation and leave Trent Triangle as it is, as a constraint to rail growth in the East Midlands for another generation.
It seems like a fraction of those 4tph between Nottingham and Derby actually seem to run these days - last year it seemed to be about 1tph, now it seems to be 2/3tph depending on the day. Of course there is the painful 10mph speed limit when heading towards Long Eaton. Long Eaton station is also going to be a mess of stopping and express services battling it out, unless they find a way to quad track it...
Last edited: