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

Report of collision Bedford (Elstow) - 19/06/26

Status
Not open for further replies.

Aspen90

Member
Joined
12 Sep 2018
Messages
259
Location
Leicester

I have a whole heap of questions which only RAIB can answer. A key piece of information is what AWS indication(s) the 360 driver received.

It seems to me that he clearly wasn’t expecting the red signal to be red - when on restrictives, you just do not chase the red at 76mph. So, did he get bell vice horn, nothing vice horn?

RAIB will look at the sun angles to see if there’s a chance of misreading due to sun illumination.

They’ll also look at whether there was a potential read across to the adjacent signal on the slows.

They’ll look at his training records. Any prior incidents and Competence Development Plans arising.

They’ll look at possible driver fatigue - rostering etc.

There are many possibilities, not limited to the above. I urge all to remember that the Swiss cheese model is real - incidents of this nature rarely have a single point of failure…

I await the RAIB’s further contributions with interest.
The usual process is WH356 is red as you approach, then changes to yellow with a number 4 junction indicator as you get nearer. When you cross the magnet, WH154 cycles through to green, then the signal protecting Bedford South, WH356 cycles through to green. It’s not normally still yellow before you contact the points. It was a break in ‘routine’.
 
Sponsor Post - registered members do not see these adverts; click here to register, or click here to log in
R

RailUK Forums

hexagon789

Veteran Member
Joined
2 Sep 2016
Messages
18,282
Location
Glasgow
They did specifically say that they only, as yet, have the data from the recorder in the rear cab of the train, which only records the output/results of the train movements; getting to the one from the crumpled front cab, which will have recorded the driver's inputs, has taken them longer in the recovery process given the need to separate the trains, remove the corpse, record the positions of everything, and then go cutting through the wreckage to get at the recorder. So I think this is simply RAIB being their usual precise selves with their wording.
That definitely remains a very high possibility - I'm perhaps just reading too much into choice of words.
 

AlterEgo

Verified Rep - Wingin' It! Paul Lucas
Joined
30 Dec 2008
Messages
29,179
Location
LBK
It was on a right hand bend. To me it seems this is the point the driver realised that the 810 was in its path and applied the brake.
This is the most likely explanation given the unwarranted acceleration while under caution, although a coincidental timely activation of the DSD cannot be ruled out.

Worth also mentioning the accident occurred in brilliant sunshine, which would have been coming from the driver's right hand side - the investigation will want to attempt to reproduce the lighting conditions on the day to see if the red signal could be adequately seen.
 

bramling

Veteran Member
Joined
5 Mar 2012
Messages
20,305
Location
Hertfordshire / Teesdale
The usual process is WH356 is red as you approach, then changes to yellow with a number 4 junction indicator as you get nearer. When you cross the magnet, WH154 cycles through to green, then the signal protecting Bedford South, WH356 cycles through to green. It’s not normally still yellow before you contact the points. It was a break in ‘routine’.

It must presumably be fairly common for the signal to remain at yellow if being turned out following another train on the up fast, though? It will be interesting to see if RAIB are able to produce some daya on how often drivers, or even the driver involved, would have experienced each scenario.

What absolutely wouldn’t be common is for the next signal to remain at red, especially if the train passing on the up fast has just been seen to pass through at full speed.
 

AlterEgo

Verified Rep - Wingin' It! Paul Lucas
Joined
30 Dec 2008
Messages
29,179
Location
LBK
It must presumably be fairly common for the signal to remain at yellow if being turned out following another train on the up fast, though? It will be interesting to see if RAIB are able to produce some daya on how often drivers, or even the driver involved, would have experienced each scenario.

What absolutely wouldn’t be common is for the next signal to remain at red, especially if the train passing on the up fast has just been seen to pass through at full speed.
Are we suggesting a contributing factor may be the driver has witnessed the 810 belt through Bedford at linespeed, and thought "I'm following that all the way to London (great, WH154 will clear to green on the fasts)"?

Once again, not prejudging the driver's actions or inactions, but attempting to understand the factors at play.
 

Signal Head

Member
Joined
26 May 2013
Messages
458
It seems one possibility is the Corby train driver took the single yellow to be approach control for the crossover, not an indication that next signal is a 'red', hence his acceleration to 76mph once on the 'fast' which is not consistent with his expecting a 'Red' at the next signal. Please correct me if I'm wrong but I though approach control for turnouts were flashing yellows (single or double) to obviate that confusion. I have seen no mention that the single yellow at the crossover was flashing, so is my understanding incorrect?
Flashing yellows are a means of conveying additional information to the driver, ie 'you are receiving cautionary aspects because a diverging route is set at the next junction", rather than because a signal is at red.

They also remove the anticipation risk inherent in Approach Release from Red, which was the norm for signalling schemes commissioned before the mid to late 1970s.

This junction doesn't have flashing yellows.
 

Mile Post 13

Member
Joined
20 Jun 2024
Messages
26
Location
Near a proper PSB
If a train signalled under the same arrangements as at Bedford South Jct would be travelling towards a red signal on a regular basis (of course "regular" would need to be defined) then there is the making of an argument that TPWS may be justified. However in this case WH154 would not usually be at Red in which case would installing TPWS produce a justifiable safety benefit ? I think not.

Locations where trains will regularly approach a Red aspect after passing a Y with a junction indicator are generally located at busy junctions or at station approaches where speeds will be low.

Bedford South Jct is a running junction which was originally designed to enable accelerating trains to gain line speed quickly and so does not fall into this category. As I think others have already alluded to, safety costs money and money is always in short supply, and will be even more going forward no doubt. The HASAWA and the Management Regs clearly accept that safety is risk based and only imposes control measures to meet ALARP or SAFAIRP principles.
 

John R

Established Member
Joined
1 Jul 2013
Messages
6,059
Very good point! I hadn’t clocked this. This does add another unknown, albeit one we should get an answer to fairly quickly.
Surely an AWS brake application would have happened much earlier, as the Corby train was just about at the end of the section having passed the red?
 

bramling

Veteran Member
Joined
5 Mar 2012
Messages
20,305
Location
Hertfordshire / Teesdale
Are we suggesting a contributing factor may be the driver has witnessed the 810 belt through Bedford at linespeed, and thought "I'm following that all the way to London (great, WH154 will clear to green on the fasts)"?

Once again, not prejudging the driver's actions or inactions, but attempting to understand the factors at play.

I wouldn’t go quite that far. I think it’s one of potentially many factors that could have been in play.

What I would say I think it’s unlikely that the driver has consciously thought “the train has just gone past, the line ahead will be clear”. But it could have had a subconscious impact on what happened next. But equally plenty of other possibilities.

I’d have been much less intrigued had it been a case of the driver reacting to the red at the last moment and braking hard but with insufficient room to stop. What seems to have occurred is much more unusual, and will no doubt probably have a more complex explanation.

What I was more alluding to is that having the yellow remain on at the junction signal would be quite normal, hence there can be a tendency to sort of normalise the situation and let the guard down, whereas in reality the opposite should happen. This seems to be a facet of human nature rather than anything negligent. Could well be something else though, a lot hinges on how the train was driven in the bit where it passed over the crossovers and when it reached the up fast line, there’s a lot we don’t yet know.
 

Mile Post 13

Member
Joined
20 Jun 2024
Messages
26
Location
Near a proper PSB
Are we suggesting a contributing factor may be the driver has witnessed the 810 belt through Bedford at linespeed, and thought "I'm following that all the way to London (great, WH154 will clear to green on the fasts)"?

Once again, not prejudging the driver's actions or inactions, but attempting to understand the factors at play.
I have experience of precisely that occurring some years ago.
They also remove the anticipation risk inherent in Approach Release from Red, which was the norm for signalling schemes commissioned before the mid to late 1970s.
That did not end in the 1970s. It remained the standard, early approach release from R to Y with a step up after the AWS magnet was only implemented for junctions 40mph and above. This was to enable the benefit from these speeds. Lower speed junctions always released from R either on the approach to or after the magnet. This arrangement was also always applied where a set of points was located greater than 200 yards ahead of a protecting signal. P468 signal on the Up Fast at Spital Jct, Peterborough being a good example
 

yorkie

Forum Staff
Staff Member
Administrator
Joined
6 Jun 2005
Messages
78,188
Location
Yorkshire
Are we suggesting a contributing factor may be the driver has witnessed the 810 belt through Bedford at linespeed, and thought "I'm following that all the way to London (great, WH154 will clear to green on the fasts)"?

Once again, not prejudging the driver's actions or inactions, but attempting to understand the factors at play.
I am sure RAIB will be considering this, however as @Haywain says above, it doesn't explain what happened next.
 
Last edited:

sharpener

Member
Joined
4 Oct 2018
Messages
370
What I was more alluding to is that having the yellow remain on at the junction signal would be quite normal

But as @baz962 and others have said this is that is not what was normal. Because of the two-stage release WH356 normally stepped up to YY and then G while it was still in view. Unless the UF was not in fact clear. This could of course have been explained by 1B76 occupying the next section.
 

Bald Rick

Veteran Member
Joined
28 Sep 2010
Messages
35,581
But as @baz962 and others have said this is that is not what was normal. Because of the two-stage release WH356 normally stepped up to YY and then G while it was still in view. Unless the UF was not in fact clear. This could of course have been explained by 1B76 occupying the next section.

But it can be normal. It is quite routine for WH356 to remain at Y if a train is routed to the UF right behind a passing service. That happens frequently. What doesnt happen often - if ever until now - is for that passing service (or indeed any service) to stop in the section ahead of WH154.
 

MarkWi72

Member
Joined
13 Nov 2017
Messages
365
The recording data , with other evidence (Railcam?) will tell more about line speeds and driving before the collision , RAIB will be over this now its been acquired.
 

Signal Head

Member
Joined
26 May 2013
Messages
458
I have experience of precisely that occurring some years ago.

That did not end in the 1970s. It remained the standard, early approach release from R to Y with a step up after the AWS magnet was only implemented for junctions 40mph and above. This was to enable the benefit from these speeds. Lower speed junctions always released from R either on the approach to or after the magnet. This arrangement was also always applied where a set of points was located greater than 200 yards ahead of a protecting signal. P468 signal on the Up Fast at Spital Jct, Peterborough being a good example
I agree that MAR was, and is still, provided when other forms are not appropriate. Perhaps I should have said that MAR (Main Aspect Approach Released from Red) was the predominant, or even the only, form of junction control for those schemes.
In its original form it was an attempt to impose speed signalling on top of the route signalling, with graphs showing where the release point should be to regulate the speed for the junction. The release point was typically relatively close to the signal back then.

I remember SSP6 became rather notorious for regular revisions, some undoing changes which hadn't been in place for that long.
 

bramling

Veteran Member
Joined
5 Mar 2012
Messages
20,305
Location
Hertfordshire / Teesdale
But as @baz962 and others have said this is that is not what was normal. Because of the two-stage release WH356 normally stepped up to YY and then G while it was still in view. Unless the UF was not in fact clear. This could of course have been explained by 1B76 occupying the next section.

What I was saying is that it would, I imagine, be quite common for the junction signal to remain at yellow due to a train just having passed on the up fast - just as the Nottingham train did. By the time a train has crossed over it is likely on the vast majority of occasions that the next signal would be displaying some kind of proceed aspect as the preceding train had progressed onwards.

This is something commonly experienced on the GN route out of King’s Cross, although less common since 2018. You would regularly get southbound Cambridge stopping trains held on the up slow line waiting for a slot on the up fast, at places like Welwyn Garden City, Marshmoor, Potters Bar, New Barnet or Alexandra Palace. It still happens at Hitchin mainly with up Fen Line trains. In these locations you would normally get fairly unrestricted acceleration once clear of the points, though of note is that in those days it was 317/321/365, which didn’t accelerate quite as much as more modern trains (especially 317/321). In my 40 years of using the GN route I’m struggling to think of a time when I’ve been on a train which has been “turned out” onto the up fast line and then had to come to a complete stand at the next signal. I’m sure it will have happened, but certainly very atypical.
 

bramling

Veteran Member
Joined
5 Mar 2012
Messages
20,305
Location
Hertfordshire / Teesdale
I take it the full report will take another year to conduct and release?

I suspect there will be another interim report fairly soon. There’s significant key issues to be resolved, not least the issue over what AWS indication the driver received, and how the train was driven in that crucial couple of minutes.

This should all be able to be resolved fairly soon. Then it all gets more complex and yes we’ll likely be oooking at a year or so
 

43074

Established Member
Joined
10 Oct 2012
Messages
2,253
Indeed. It looks like 5Z14 was checked, losing 3 minutes, on the approach to WH343 to allow 1H46 to cross in front of it. I am sure that the CCTV from this unit will form part of the RAIB investigation as it must have seen both trains.
The driver of 5Z14 will also be vital evidence as they would have seen both trains in the seconds before the collision occured.
 

AlterEgo

Verified Rep - Wingin' It! Paul Lucas
Joined
30 Dec 2008
Messages
29,179
Location
LBK
RAIB are traditionally cautious to a fault with their investigations
Yes, they are very careful with their language. It's not their direct role but they also need to maintain faith and trust in the railway (among both passengers and staff) and this is why they will release only known facts.

Today's update is careful about what it does and does not say.
 

sharpener

Member
Joined
4 Oct 2018
Messages
370
What I was saying is that it would, I imagine, be quite common for the junction signal to remain at yellow due to a train just having passed on the up fast - just as the Nottingham train did. By the time a train has crossed over it is likely on the vast majority of occasions that the next signal would be displaying some kind of proceed aspect as the preceding train had progressed onwards.

Yes I accept that hence the final sentence of my post, the aspect is readily explained by the recent passage of 1B76.

This is something commonly experienced on the GN route out of King’s Cross, although less common since 2018. You would regularly get southbound Cambridge stopping trains held on the up slow line waiting for a slot on the up fast, at places like Welwyn Garden City, Marshmoor, Potters Bar, New Barnet or Alexandra Palace. It still happens at Hitchin mainly with up Fen Line trains. In these locations you would normally get fairly unrestricted acceleration once clear of the points, though of note is that in those days it was 317/321/365, which didn’t accelerate quite as much as more modern trains (especially 317/321). In my 40 years of using the GN route I’m struggling to think of a time when I’ve been on a train which has been “turned out” onto the up fast line and then had to come to a complete stand at the next signal. I’m sure it will have happened, but certainly very atypical.

Yes, it doesn't happen often. I recall enquiring here about the similar 4 into 2 tracks situation at Digswell, how do the slow line drivers judge their approach to the restriction? And the answer was they look at the fast signals so they can predict when their slow signal will clear, with a good deal of precision.
 

CalderRail

Member
Joined
21 Aug 2013
Messages
281
The driver of 5Z14 will also be vital evidence as they would have seen both trains in the seconds before the collision occured.
Does the rear cab still record the Forward Facing CCTV (actually Rearward Facing, but YKWIM)? It may even have seen the collision if so.
 

Markuk

Member
Joined
16 Mar 2021
Messages
44
Location
Northamptonshire
Still lots of unanswered questions, which will be answered by RAIB
Was the AWS fault the 810 experienced due to a fault at WH154. The section doesn't seem very long so an AWS brake application at WH154 could have brought the train to a stand in the area of WH152, depending on the trains speed.
We know the 360 passed a red signal but don't know yet what if any AWS indication was recieved by the driver.
There was an issue earlier in the journey that caused a delay at Leicester wasn't there? Was this also an AWS system issue?

== Doublepost prevention - post automatically merged: ==

Even in an energy dissipating collision, momentum is still conserved. If the 5-car 810 weighed twice as much as the 4-car 360, then the combined consist will have been moving at one third of 49mph immediately after the collision, i.e. around 16mph. With several bogies derailed and the brakes fully applied on both units, I'd expect it would stop well within 700m
Only true if the brakes on the 810 were not applied.
 

DynamicSpirit

Established Member
Joined
12 Apr 2012
Messages
9,211
Location
SE London
This will be a very long investigation and I expect a heavy focus on human factors on the risks of underload and the psychology of changing routes from a more intensive method of work involving a station stop onto a faster line where a driver may expect a clear run for 20 miles. Let's hope for a positive set of learnings from the incident, whatever the case, and for those still injured to make a recovery.

I'm puzzled by this. Before the stop at Bedford, there would have been 14 miles of clear running between Wellingborough and Bedford. Then a brief swap from fast running to dealing with the station-stop. So that would seem to me not so much like a change from intensive work to fast running, as a brief intensive work interval in the middle of a long fast running period. Would that really have the kind of psychological impact you're describing?
 

Kilopylae

Member
Joined
9 Jan 2018
Messages
1,065
Location
Uxbridge (ex Devon)
Although the report from RAIB notes the 810 came to a stop "unexpectedly", which implies the driver of the 810 did not initiate the brake application
I don't read it that way. I took it to imply merely that the 810 stopped out of its usual course, i.e. in the middle of the line without the signaller or other trains having any prior reason to anticipate that it might stop. Not that its stop was unexpected to the driver.
 

bramling

Veteran Member
Joined
5 Mar 2012
Messages
20,305
Location
Hertfordshire / Teesdale
I'm puzzled by this. Before the stop at Bedford, there would have been 14 miles of clear running between Wellingborough and Bedford. Then a brief swap from fast running to dealing with the station-stop. So that would seem to me not so much like a change from intensive work to fast running, as a brief intensive work interval in the middle of a long fast running period. Would that really have the kind of psychological impact you're describing?

The stop wouldn’t be that intensive, especially as the station work would be being handled by the guard. But we don’t know the context, what else might have been going on, especially in terms of human factors. A train cab is an awful place to be for someone who has things on their mind, for example.
 

edwin_m

Veteran Member
Joined
21 Apr 2013
Messages
28,586
Location
Nottingham
The discussion is what would have happened if the signal that was red (WH154) had been fitted.
For just the bare minimum, a TPWS Train Stop System (TSS), the "grids" (officially "loops") are fitted just past the signal. This would apply the train brakes as soon as the train passed the red signal.

If the additional TPWS Over Speed System (OSS) was also fitted, another set of loops is fitted on approach to the signal. If a train is travelling too fast, they trip the brakes. The intention is not to stop a train at line speed from passing the signal, but to slow it enough that any collision is at a much lower speed than if only an TSS is fitted.
Depending on spacing of the signals and points and the acceleration of the train, there's also the risk that the train might pass the overspeed sensor below the tripping speed but still accelerating, and TPWS only intervene when passing the red. TPWS OSSs are designed on the assumption the train is approaching at a constant speed.
 

Horizon22

Established Member
Associate Staff
Jobs & Careers
Joined
8 Sep 2019
Messages
10,942
Location
London
That's not the sequence of events. The sequence given by the RAIB is:
  • Platform signal at Yellow
  • Junction signal at Yellow
  • Up Slow to Up Fast
  • WH154 (red)
  • 76mph 9 seconds before collision
  • collision just before reaching WH152
The given speed was at a position well after passing the WH154 signal at red. There's no information released so far as to what speed the train was doing over the junction, between the junction and WH154, and what the speed (or acceleration) looked like after WH154 was passed.

What will also be of note would be at what point the signaller was aware that WH154 had been passed at danger and what - if any - action they took. I imagine we’re talking seconds, in which case there was nothing further they could do to intervene. Perhaps they were on with the driver of the 810 discussing the AWS issue.
 
Last edited:

Signal Head

Member
Joined
26 May 2013
Messages
458
What will also be of note would be at what point the signaller was aware that WH154 had been passed at danger and what - if any - action - they took. I imagine we’re talking seconds, in which case there was nothing further they could do to intervene. Perhaps they were on with the driver of the 810 discussing the AWS issue.
They wouldn't know until the rear of the 360 cleared the overlap at WH154, since the next track circuit was already occupied by the 810, so wouldn't 'see' the 360 entering it as well.
 
Status
Not open for further replies.

Top