1Y17 Leeds to Nottingham 04.05.26

[Amos390]

Afternoon all,
I heard that apparently, on Monday, 1Y17 Nottingham to Leeds operated by 195018 nearly derailed on approach into Nottingham, with a report of the train “Hitting something hard and fast” and “jolting left and right”, with the driver applying emergency brakes, with medical attention required due to someone being thrown across the carriage.

I’ve only heard this from one source that I was sent (image attached) and would like to confirm whether this is true, and what happened, which appears to be from a Reddit user, however not sure where on Reddit. I have also linked the service involved and the following service (Which was cancelled for YI - Late arrival of inbound booked stock), which ran out of Notts later under 5Z20 (off timetable). I should also mention 195018 has not returned to service yet.

1Y17 - https://www.realtimetrains.co.uk/service/gb-nr:G91067/2026-05-04/detailed#allox_id=0
1Y20 - https://www.realtimetrains.co.uk/service/gb-nr:G91075/2026-05-04/detailed

 

[800002]

I wouldn't wish to speculate,
But appears there was an allegation of some sort on the inward working, to Nottingham, 1Y17 at Trowell Jn.
The YI since updated in systems to TG, TOC Driver.
The back working, 1Y20, being cancelled due to the driver being unable to work the train back towards Leeds after having made their report.

There could be numerous reasons why the unit has not been in service today.

 

[ALEMASTER]

If that incident happened i'm surprised it wasn't late arriving into Nottingham, unless it occurred after the train was recorded as entering the station.

 

[800002]

Or reported after the train arrived.

 

[321362]

Probably shouldn't speculate this early, but it seems like an overspeeding incident to me.

 

[Amos390]

Probably shouldn't speculate this early, but it seems like an overspeeding incident to me.

That’s what I was thinking, either that or an object on the tracks

 

[321362]

If it jolted left and right that seems exactly like passing over a set of facing points too fast - hitting an object would likely either be one big jolt then nothing, or a series of jolts as the train derailed, which it didn't in this incident

== Doublepost prevention - post automatically merged: 6 May 2026 ==

I wouldn't wish to speculate,
But appears there was an allegation of some sort on the inward working, to Nottingham, 1Y17 at Trowell Jn.
The YI since updated in systems to TG, TOC Driver.
The back working, 1Y20, being cancelled due to the driver being unable to work the train back towards Leeds after having made their report.

There could be numerous reasons why the unit has not been in service today.

Corroborated by this, which seems to imply driver error so overspeeding on points looks most likely

 

[yorkie]

According to a trusted source, this incident happened at Trowell Junction, it was reported when the train got to Nottingham and subsequently the driver was stood down, hence back working cancelled. It is understood that the train went over the junction at 55mph, line speed over the junction is 30mph.

 

[Amos390]

According to a trusted source, this incident happened at Trowell Junction, it was reported when the train got to Nottingham and subsequently the driver was stood down, hence back working cancelled. It is understood that the train went over the junction at 55mph, line speed over the junction is 30mph.

Thanks, do we know if any damage sustained to the unit or not? I would presume not much but you never know.

 

[MCR247]

Did the unit work back ECS or stay at Nottingham to be coupled to the next one?

 

[Amos390]

Did the unit work back ECS or stay at Nottingham to be coupled to the next one?

Ran back off-timetable under 5Z20, caught it at Chesterfield on Railcam

 

[MCR247]

Ran back off-timetable under 5Z20, caught it at Chesterfield on Railcam

Thanks for the quick response!

 

[dodecahedron67]

Allegedly the train went over the 30mph crossover at approximately 70mph with full power applied

 

[voyagerdude220]

Will there be a report made publicly available about this?

 

[Amos390]

Allegedly the train went over the 30mph crossover at approximately 70mph with full power applied

Wow a tad too much speed then, oops.

Will there be a report made publicly available about this?

Presumably RAIB are undergoing an investigation on it, doubt anything much up until then though.

 

[rmHawk765]

Getting an awful lot of these overspeeding incidents happening lately...

Will there be a report made publicly available about this?

It was quite an overspeed (25-40mph simply going off the two speeds quoted in this thread), and has the risk of damaging infrastructure therefore posing a risk to the next trains to pass over the junction, so I would think so, yes. The recent Sep 25 Grantham South Jn overspeed on the ECML was reported to the RAIB and a report has already been published if I remember correctly, so I'd imagine this will be covered as well.

 

[Amos390]

Getting an awful lot of these overspeeding incidents happening lately...

I wonder if this is as a result of attempting to make timetables more efficient and quicker

 

[edwin_m]

I wonder if this is as a result of attempting to make timetables more efficient and quicker

I don't see much sign of this happening with timetables...

What's the aspect sequence approaching this divergence?

 

[rmHawk765]

What's the aspect sequence approaching this divergence?

If we look back at the Peterborough incident, there was a lot of debate about whether the design of the approach to the junction was poor or not. I'm not sure about this junction but it may not be the best either.

 

[Nottingham59]

If we look back at the Peterborough incident, there was a lot of debate about whether the design of the approach to the junction was poor or not. I'm not sure about this junction but it may not be the best either.

If it was a Leeds to Nottingham service at Trowell South junction, then the Northern driver would (almost) always take the crossover from the fasts and then diverging path towards Nottingham. So unlike recent incidents at Peterborough and Grantham, where I understand the diverging move was unusual.

 

[rmHawk765]

I wonder if this is as a result of attempting to make timetables more efficient and quicker

Even if it is, it doesn't mean that this is a bad thing. It is simply because we have reached the end-of-life for TPWS in a sense. It was only ever intended as a cheap stop-gap to ETCS and indeed what it achieved given its cost and speed to install was remarkable. It was always known that trying to control junction speed with TPWS is, to say the least, sub-optimal, but the possible consequences of a SPAD were and are far, far higher. Obviously the only reason ATP was thrown out of the window in the first place was money and bureaucracy but that's a much wider-scale issue.

With timetables getting busier, trains getting faster, and junctions becoming more complex, a cheap stop-gap poised as the sole safety feature obviously isn't going to cut it. So to retain our network's status as one of the safest I think it's pretty important we give ETCS a lot more attention, even if that's just basic L1 installations which are significantly cheaper than L2 but still pretty much eliminate these sort of incidents. The main benefit of L2 over L1 is to provide the provisioning for moving-block and incredibly optimised braking distances to significantly increase capacity, not to significantly increase safety.

 

[dodecahedron67]

There’s been another overspeed very recently as well, though details of that aren’t public so I won’t share more than the fact that it was 91mph over a 50…

 

[Tomnick]

I don't see much sign of this happening with timetables...

What's the aspect sequence approaching this divergence?

Flashing yellow sequence available towards both the Trowell branch (usual route for Northern services, including this one) and the Up Erewash Slow. Ilkeston station is situated between the flashing double yellow and the flashing single yellow.

I've never really liked how the pos.2 junction indicator aligns with the Down direction signal gantry about 300yds on the approach.

 

[LCC106]

Allegedly the train went over the 30mph crossover at approximately 70mph with full power applied

Where is the source for this information? Also, where did the latter one you quoted allegedly happen? There is nothing to suggest any ongoing investigations on the RAIB website.

 

[edwin_m]

Where is the source for this information? Also, where did the latter one you quoted allegedly happen? There is nothing to suggest any ongoing investigations on the RAIB website.

If RAIB is involved, they normally don't post for several days.

 

[LCC106]

It’s been a week since the first alleged overspeed. I would have expected that one to be showing as an ongoing investigation by now if that’s the case. I’m just intrigued as to the source of the information and how the speeds involved have come into the public domain.

 

[LowLevel]

It’s been a week since the first alleged overspeed. I would have expected that one to be showing as an ongoing investigation by now if that’s the case. I’m just intrigued as to the source of the information and how the speeds involved have come into the public domain.

The information that caused them to begin investigating wasn't necessarily received on the day of the incident, though. It's not unusual for this forum for people to make vague references to internal information.

 

[LCC106]

If the back working was cancelled presumably the train would have been downloaded at Sheffield or Leeds. I think it’s useful for people to clarify whether they have the information from a reputable source or whether it is pure speculation based on, for example, messroom gossip. We all know how these things can get exaggerated, so I’m genuinely interested to see what comes of both alleged overspeeds.

 

[skyhigh]

If the back working was cancelled presumably the train would have been downloaded at Sheffield or Leeds.

If it was a 195 then it can be downloaded remotely and the data viewed pretty much immediately after an incident.

 

[LCC106]

Interesting to know. Thanks.