|
Post by superteacher on Sept 1, 2019 20:30:37 GMT
Thames News episode containing reports about the accident.
|
|
roythebus
Pleased to say the restoration of BEA coach MLL738 is as complete as it can be, now restoring MLL721
Posts: 1,275
|
Post by roythebus on Sept 4, 2019 19:27:29 GMT
What was the cause of the accident?
|
|
|
Post by superteacher on Sept 4, 2019 19:34:47 GMT
|
|
|
Post by Dstock7080 on Sept 4, 2019 19:53:22 GMT
Blames driver error, although surely the signalling should have prevented the collision? Second paragraph of the Report you linked to above states:
|
|
|
Post by superteacher on Sept 4, 2019 20:05:56 GMT
Ah, so the driver reset the tripcock and proceeded.
|
|
Tom
Administrator
Signalfel?
Posts: 4,196
|
Post by Tom on Sept 4, 2019 20:11:46 GMT
The collision revealed a design flaw that the outer home signal would clear with simple approach control regardless of the speed of the approaching train.
In this instance Train 66 was travelling at a greater speed than the reduced overlap on the intermediate home was calculated for (what we would now term a compromised overlap) and was not brought to rest prior to colliding with T10. The approach control feature was decommissioned following the collision and decommissioned or modified where other similar circumstances existed.
|
|
|
Post by rheostar on Sept 5, 2019 21:44:20 GMT
Prior to this incident, as Motormen we were taught that there was always 'a safe braking distance' between a signal and a train in section ahead. Afterwards, this was changed to 'a breaking distance'.
|
|
|
Post by norbitonflyer on Sept 6, 2019 6:21:03 GMT
I hope you mean "braking distance" !
|
|
|
Post by rheostar on Sept 6, 2019 7:09:09 GMT
I hope you mean "braking distance" ! Oops! Dyslexic fingers! Mind you, in the case of Holborn perhaps I was right. :-D
|
|