D365
Veteran Member
- Joined
- 29 Jun 2012
- Messages
- 13,157
Picking up on the post below from the Bedford 19/06/2026 incident thread:
Rulebook TW5 (Issue 10) states that, if AWS or TPWS is currently in operation, the driver must stop the train immediately and contact the signaller as soon as they become aware of a defect. The same also applies to defects relating to ATP, ETCS, DSD vigilance, horns or any mechanical / structural damage to the vehicles.
Notwithstanding the fact that the driver and signaller must come to a clear understanding before isolating any onboard systems, I don’t see how the driver of a defective train could be expected to diagnose the exact nature of a fault or defect with the train in motion.
A key learning may be that coming to a halt in the shortest distance possible after a suspected AWS fault may not be the best practice as the following train could also be impacted by a trackside fault. Possibly better to slow and contact signaller while proceeding at low speed if the signals infront permit to reduce the risk of being rear ended.
Rulebook TW5 (Issue 10) states that, if AWS or TPWS is currently in operation, the driver must stop the train immediately and contact the signaller as soon as they become aware of a defect. The same also applies to defects relating to ATP, ETCS, DSD vigilance, horns or any mechanical / structural damage to the vehicles.
Notwithstanding the fact that the driver and signaller must come to a clear understanding before isolating any onboard systems, I don’t see how the driver of a defective train could be expected to diagnose the exact nature of a fault or defect with the train in motion.

