Politics
Welcome to Live View – Take the tour to learn more
Start Tour
There is currently 1 person viewing this thread.
24 Jun 26
16:59
Joined:
Date Joined:
07 Nov 08
Train in front stopped due to train fault.
Signal behind automatically stays at red.
Following train passes yellow signal and then should be slowing down to stop at the red signal.
But continues at full speed and passed the red signal at 76mph.
Driver realises error and hits brakes, but too late and hits the back of stationary train at 49mph at moment of impact.
Cause: train driver error
Signal behind automatically stays at red.
Following train passes yellow signal and then should be slowing down to stop at the red signal.
But continues at full speed and passed the red signal at 76mph.
Driver realises error and hits brakes, but too late and hits the back of stationary train at 49mph at moment of impact.
Cause: train driver error
Show More
Miracle he is the only person that Died TBH many injured some serious
Rather too quick and not sure the RAIB initial report fully supports this.
To me there is a bit more info required before the Dead Driver is blamed.
Both Trains one electric one duel power, initially front train is behind, after stopping at station this is reversed, first train is auto stopped by aws system but report also suggests it was just stopped. Anyway no time on when it stopped and how long before second train slams into it, again at same point and again by aws system? , could be a min or so maybe less.
Track was due to close at weekend for works.
So not impossable both got stopped by same issue at same same point?
The report is not clear and lacks info, and they did not have all the data, like the info from the first train as to why it stopped and was it stopped because it went through a red light?
RAIB has report on its site.
This is from wiki.
Preliminary report
edit
In its preliminary report released on 24 June 2026, the Rail Accident Investigation Branch identified the likely contributing factors. Due to a fault with the Automatic Warning System (AWS) which caused the brakes to apply, the Nottingham service had stopped unexpectedly on the up fast line where it was struck from the rear by the Corby service.[19][2] The report stated that the Corby service passed a signal at danger (SPAD), which was protecting the Nottingham service.[2] The Corby service made a brake application just nine seconds before the collision, with the train travelling at approximately 76 miles per hour (122 km/h). The Corby service was still travelling at 49 miles per hour (79 km/h) at the time of the collision.[2] One of the carriages of the Nottingham train was derailed by the collision.[20]
As you can see it's ambiguous as to whether driver applied brakes on second train, it says there was brake application.
Big diff between an auto brake application and a driver applied imo.
Let's see how it pans out but need to know if first train went through red too hence aws application and how long it was stationary and what applied brakes on second train.
Not to mention a detailed explanation of the "fault".
To me there is a bit more info required before the Dead Driver is blamed.
Both Trains one electric one duel power, initially front train is behind, after stopping at station this is reversed, first train is auto stopped by aws system but report also suggests it was just stopped. Anyway no time on when it stopped and how long before second train slams into it, again at same point and again by aws system? , could be a min or so maybe less.
Track was due to close at weekend for works.
So not impossable both got stopped by same issue at same same point?
The report is not clear and lacks info, and they did not have all the data, like the info from the first train as to why it stopped and was it stopped because it went through a red light?
RAIB has report on its site.
This is from wiki.
Preliminary report
edit
In its preliminary report released on 24 June 2026, the Rail Accident Investigation Branch identified the likely contributing factors. Due to a fault with the Automatic Warning System (AWS) which caused the brakes to apply, the Nottingham service had stopped unexpectedly on the up fast line where it was struck from the rear by the Corby service.[19][2] The report stated that the Corby service passed a signal at danger (SPAD), which was protecting the Nottingham service.[2] The Corby service made a brake application just nine seconds before the collision, with the train travelling at approximately 76 miles per hour (122 km/h). The Corby service was still travelling at 49 miles per hour (79 km/h) at the time of the collision.[2] One of the carriages of the Nottingham train was derailed by the collision.[20]
As you can see it's ambiguous as to whether driver applied brakes on second train, it says there was brake application.
Big diff between an auto brake application and a driver applied imo.
Let's see how it pans out but need to know if first train went through red too hence aws application and how long it was stationary and what applied brakes on second train.
Not to mention a detailed explanation of the "fault".
Track signalling playing up due to heat ?? Another death Today at railway crossing !
seen that sounds like Mum dead daughter badly injured 
staggered Crossing Surely you would not try to go round the Barriers
staggered Crossing Surely you would not try to go round the Barriers
Post Your Reply
Please login to post a reply.
Wonder
Instance ID: 13539