Chiltern Railways to run most services despite RMT strike
Summarised from 2 outlets · Updated 6 Nov, 21:27 · Archive
Chiltern Railways says more than 90 per cent of its services will run as normal on Thursday 12 November during industrial action by RMT union members. The strike concerns how the company intends to run services on the first stage of East West Rail between Oxford and Milton Keynes.
Some services will be affected. No direct Chiltern services will operate between Stratford-upon-Avon and Leamington Spa, while no services will run north of Birmingham Moor Street. There will also be a small reduction in trains between Leamington Spa and Birmingham Moor Street, affecting Hatton and Lapworth stations.
Tony Baxter, interim managing director of Chiltern Railways, said: "We expect to run the vast majority of our services on that day, helping to minimise disruption for customers." Chiltern said the proposed arrangements would create more than 100 new permanent jobs and would not change the roles of existing employees. Confirmed timetables for 12 November will be published in the coming days.
How it is being reported
- Chiltern Railways issues update to Bucks passengers ahead of strike actionChiltern Railways says more than 90 per cent of services will run as usual during RMT industrial action on November 12.Bucks Free Press · 6 Nov, 20:00
- More than 90 per cent of Chiltern Railways services through Aylesbury to run as normal despite industrial action on day of England matchChiltern Railways says that more than 90 per cent of its services through Aylesbury will run as scheduled, despite members of the RMT union announcing strike action on Thursday November 12, when England are due to play at Wembley in football’s Nations League competition.Bucks Herald · 6 Nov, 14:56
In this story: Chiltern Railways · RMT · East West Rail · Aylesbury · Oxford · Milton Keynes
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)