E16 Cyclist
Member
Hearing reports of a collision between two trains at Bedford with one train now derailed
-
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
- Thread starter E16 Cyclist
- Start date
- Status
Sponsor Post - registered members do not see these adverts; click here to register, or click here to log in
R
RailUK Forums
yorkshirerail
Member
810016 and 360115+360114 the units involved
Apparently all lines closed and emr trains stopped, just got train cancelled at Kettering but no word from staff as they are not being told what happened by network rail other than it’s serious and worse than a collision with a person
Last edited:
Realtime trains is saying 810015
tram21
Established Member
I am told the EMR connect collided into the back of the Intercity Aurora service
dk1
Veteran Member
Yes they appeared to be a minute or so apart but although not great both heading in the same direction thankfully.
According to this X comment https://x.com/NaazroUk/status/2068018274336407886?s=20 There are at least 4 air ambulances attending
j_walker1804
Member
43096
On Moderation
- Joined
- 23 Nov 2015
- Messages
- 18,722
Photographic evidence says 810015. 360115 the colliding unit.
Intercity_225
Member
Seems like a very odd place for the incident to happen if SignalMaps is to be believed (just south of Bedford South Junction). Had the 810 stopped for some reason before hand?
tram21
Established Member
It was running on time up until that point- nothing really showing why it would stop.
The location is correct
Is the green signal visible in the right side aligned with the fast line the 810 is occupying?
BHMGuard
Member
Was thinking the same
Haywain
Veteran Member
- Joined
- 3 Feb 2013
- Messages
- 24,477
It had gone through on the Up Fast, so no obvious reason to be stopping.
MatthewE707
Member
Having looked at RTT and the maps on OpenTrainTimes, I think the 810 was running about 18 minutes late, and the 360, having stopped at Bedford, crossed from the Up Slow to the Up Fast at Bedford South Jn and collided with the rear of the 810.
dk1
Veteran Member
Keep hearing reports of a derailment.
CR165022
Established Member
Reportedly an AWS fault on the 810 meaning it had to stop, but would wait until the report to confirm that.
dk1
Veteran Member
Which shouldn’t affect any signalling. Seems so odd.
The BBC have started a live feed on the incident https://www.bbc.co.uk/news/live/cy8dy2pr8ymt
Link is to BBC live feed
Link is to BBC live feed
Live page on BBC News now (although not much there at time of writing):
www.bbc.co.uk
Nine people in critical condition among 100 injured in fatal collision
A driver was killed in the collision between the 16:40 train from Corby and 15:50 service from Nottingham on Friday.
www.bbc.co.uk
It looks from RTT like it was 18L when it passed Bedford. And then stopped shortly after. The EMR Connect is showing as on time leaving Bedford
Haywain
Veteran Member
- Joined
- 3 Feb 2013
- Messages
- 24,477
Became aware of a problem as I walked over Luton station and noticed a Meridian running from the Down Fast to Up Fast platform 4.
Reported on the other site that 810 stopped due to AWS fault.
tram21
Established Member
That could have been a signal fault causing that, rather than the train itself having a AWS fault, if that makes sense?
SomeTrainboy
Member
Maybe the 360 also had the AWS fault and the driver (for some reason) couldn't stop for the red signal.
Intercity_225
Member
Signalling must've been working, since why else would the collision have been so minor (considering what could've happened)?
dk1
Veteran Member
But that wouldn’t affect the signalling and unless isolated TPWS would’ve kicked in.
If I’m honest I’m quite annoyed at myself for speculating as not my style.
== Doublepost prevention - post automatically merged: ==
Previous signal to the 810 should've been at danger though.
- Status