That is 0 articles you have read today.
The Aporia is free and carries no advertising, so readers are the only
thing paying for it. If you are getting this much out of it, a small
donation is what keeps it independent.
Daily limit reached
You have read 0 articles today.
That is more than the 15 a day The Aporia gives away,
and well past what it can carry on nothing. Your allowance resets at
midnight.
There is no advertising here and nothing about you is sold, so readers
are the only thing paying for it. If the site is worth this much of
your day, it is worth a few dollars.
Everything else stays open: the
maps, the
directory and
search do
not count against this, and neither does re-opening something you have
already read today.
Investigators found that a train driver ignored a red signal just before a fatal crash near Bedford on June 19, accelerating past it despite the signal rarely ever displaying red in its history since 1985. The collision occurred when Shaun Burton's London-bound service hit another East Midlands Railway (EMR) train that had stopped after receiving an Automatic Warning System (AWS) alert, which was incorrectly interpreted by the first train’s crew. The RAIB is examining whether incorrect AWS warnings or signal positioning contributed to the incident but has found no evidence of a faulty red signal itself.
Written locally by qwen2.5:14b on 2026-10-01,
using this article's own text rather than the other coverage of the
same event (that is the story summary below).
Story summary
On June 19, a fatal train crash occurred near Elstow south of Bedford station, when East Midlands Railway (EMR) driver Shaun Burton's Class 360 Luton Express collided with another EMR train at 50mph, injuring over 160 people, including 11 seriously. The Rail Accident Investigation Branch (RAIB) report revealed that Burton had passed a red signal at high speed despite being alerted by the Automatic Warning System (AWS). He acknowledged the red light but continued to accelerate up to 76mph before braking seconds before impact. Survivors are calling for the Train Protection & Warning System (TPWS), which could have prevented the crash, to be installed on that stretch of railway after Network Rail decided against it following a safety review. The collision occurred due to an Automatic Warning System (AWS) fault causing the lead train to stop unexpectedly, and Burton’s failure to heed the red signal warning.
Written for “Bedford Train Crash Investigation” on 2026-10-05,
grounded in this article and the 1 other(s) covering the same event.
- Published
A train involved in a fatal crash had accelerated past a red signal that was rarely ever on, investigators have found.
asserted
investigators → publish → signal
Train driver Shaun Burton, 60, died and more than 160 people were injured when his London-bound service crashed into the back of another train on 19 June at Elstow, near Bedford.
The Rail Accident Investigation Branch, external (RAIB) has found the signal had not displayed a red light to any train before the crash during 2026.
asserted
signal → die → 2026
The latest interim report said CCTV had shown the signal had displayed red correctly, and Burton had acknowledged it, but he had continued to accelerate and applied brakes only seconds before hitting the other train, which had earlier come to a stop.
The collision took place between two East Midlands Railway (EMR) services on Network Rail's Midland Main Line, about 2.5 miles (4km) south of Bedford station.
asserted
collision → say → station
The driver of the first train, travelling from Nottingham to London, was learning how to operate a new type of train under the supervision of an instructor.
asserted
driver → travel → instructor
It stopped after receiving an Automatic Warning System (AWS) alert, despite the signal ahead displaying green.
asserted
signal → stop → green
Neither the driver nor the instructor recognised the alarm as an AWS warning, and it was not acknowledged within the required window.
asserted
it → recognise → window
This caused the train's emergency brakes to be applied automatically.
asserted
brakes → cause → ?
When Burton's train approached from Corby, the signal was displaying red, although he acknowledged its AWS warning, he continued to accelerate.
asserted
he → approach → warning
RAIB said no train had previously been recorded passing the signal while it was red since records began in 1985.
asserted
records → say → 1985
On 9 July, after the crash, another train approaching the same signal received an incorrect AWS warning despite it displaying green.
asserted
it → approach → green
The AWS equipment was later found to be positioned 16mm below rail level, outside the permitted tolerance.
asserted
equipment → find → tolerance
Investigators are examining whether this contributed to the incorrect warnings.
asserted
this → examine → warnings
However, investigators found no evidence that the signal itself was faulty when it was tested after the crash.
asserted
it → find → crash
RAIB said it would continue to investigate why Burton's train had passed the red signal, as well as the signal's positioning, visibility and status.
asserted
train → say → signal
The Aporia
