Request ID: FOI-2499-2324 Date published: 02 November 2023
You asked
Dear TfL,
I'm writing to you today to request the following information, relating to the delays on the Elizabeth line between Paddington and Reading on the evening of the 11th October.
1. Please provide copies of any reports produced by TfL, MTR or Network Rail outlining the cause of this incident, and any action taken by MTR or Network Rail to minimise disruption to customers who were travelling that evening.
2. Yesterday, it was decided that 9T98 would start from Acton Main Line, in front of 3 already late running trains (9R90 - 26 mins late, 9T97 - 10 mins late and 9R92 - 25 mins late).
Once 9T98, 9R90 and 9T97 had cleared Hayes & Harlington, 9R92 was held in Platform 3 at Southall - to allow 9T94 to pass (via the main line), and pull in to Platform 5 at Hayes & Harlington.
Which organisation was allocated responsibility for causing the additional delay (stated below) resulting from the above actions, to the following trains? Was it Network Rail, or MTR (the operator)?
12 mins to 9R90
11 mins to 9T97
30 mins to 9R92
21 mins to 9N96
If Network Rail were allocated any responsibility for the delays mentioned, please provide a copy of the statement of allocated responsibility.
3. Please provide copies of any correspondence between MTR and Network Rail on the planning and execution of these train movements.
Thanks.
We answered
TfL Ref: FOI-2499-2324
Thank you for your request received by Transport for London (TfL) on 12th October 2023 asking for information about delays on the Elizabeth Line.
Your request has been considered in accordance with the requirements of the Freedom of Information Act and our information access policy.
Your questions are answered in turn below:
Elizabeth line delays - 11th October:
Question 1. Please provide copies of any reports produced by TfL, MTR or Network Rail outlining the cause of this incident, and any action taken by MTR or Network Rail to minimise disruption to customers who were travelling that evening.
Answer: The delays and the associated disruption that impacted the Elizabeth line between Paddington and Reading on this day was caused by a track circuit failure at Stratford starting at 16:15. This failure meant that for the duration of the failure no trains were able to leave the Central Operating Section travelling eastbound to Stratford. To keep the services moving, all trains were then required to divert to Abbey Wood. Further delay was then caused due to congestion at Abbey Wood. This then impacted on trains starting at Abbey Wood going west to Heathrow and Maidenhead / Reading. Please see the attached documents:
SSDO Post incident review TCF 9W18 which provides details/actions of the contingency plan and the communication protocol;
Compass Event 116811 which shows the Elizabeth Line incident log.
Note that a small number of redactions have been made to the material under sections 24 (National Security) and 38 (Health and Safety) of the Freedom of Information. This generally relates to diagrams of the track. The exemptions apply because the requested material would be of use to any persons wishing to disrupt London’s transport infrastructure by placing into the public domain information which would otherwise not be available via other means. Whilst we make no suggestion that you would use this information for anything other than you own interest, disclosure of information under FOI is regarded as a disclosure to the public at large. As you will no doubt be aware, the transport system in London has been the target of attacks in the past. The information requested contains sensitive information which could be of use for anyone seeking to research or plan for such an attack or to actively cause disruption to the network.
The Information Commissioner’s Office has previously issued a Decision Notice regarding the application of sections 24 and 38 to withhold information in relation to the security of public transport. Whilst the information requested in this case is different to the information you have requested, we believe the same arguments can be applied:
The use of the section 24 and 38 exemptions are subject to an assessment of the public interest in relation to the disclosure of the information concerned. We recognise the need for openness and transparency by public authorities, and acknowledge that there may be some interest in the information in question - as evidenced by the fact that you have requested it. However, as we believe this information could potentially be obtained and utilised by individuals who may wish to use it to cause disruption or harm to London’s transport infrastructure, in this instance we believe that minimising the risk to that infrastructure and protecting the safety and welfare of members of the general public and our staff outweighs the limited public interest in disclosure.
Question 2. Yesterday, it was decided that 9T98 would start from Acton Main Line, in front of 3 already late running trains (9R90 - 26 mins late, 9T97 - 10 mins late and 9R92 - 25 mins late).
Once 9T98, 9R90 and 9T97 had cleared Hayes & Harlington, 9R92 was held in Platform 3 at Southall - to allow 9T94 to pass (via the main line), and pull in to Platform 5 at Hayes & Harlington.
Which organisation was allocated responsibility for causing the additional delay (stated below) resulting from the above actions, to the following trains? Was it Network Rail, or MTR (the operator)?
12 mins to 9R90 11 mins to 9T97 30 mins to 9R92 21 mins to 9N96
If Network Rail were allocated any responsibility for the delays mentioned, please provide a copy of the statement of allocated responsibility.
Answer: 9R90, 9R92 and 9N96 were delayed departing Abbey Wood due to the congestion caused by the incident outlined above in answer to Question 1. 9T97 from Shenfield to Paddington/Heathrow was delayed in the east before Stratford due to the same incident. 9T98 (Shenfield to Heathrow service) was significantly delayed by the failure at Stratford and in order to move more customers during the evening peak service recovery period. It was agreed that a train unit from Old Oak Common depot would be brought out in the pathway of 9T98 starting at Acton Mainline. A further incident then caused more delay. At 18:49 9R92 arrived at Southall platform 3 with a passenger ill on the train. This caused an extended delay to 9R92. It was agreed with Network Rail and MTREL that 9T94 would be diverted around 9R92 (via the mainlines) and terminate at Hayes and Harlington. See the attached document: Event – 116820 - PIOT - Compass log for the passenger ill on 9R92
Question 3. Please provide copies of any correspondence between MTR and Network Rail on the planning and execution of these train movements.
Answer: There is no “correspopndence” as such. As the incident developed, all service changes would have been agreed between MTREL and Network Rail via a phone call. Once the agreement was made the details of the agreed amendments to the train service are entered by MTREL in the “Tyrell” system. This system in turn feeds the changes to ‘DARWIN’ (the rail industry’s official train running information engine). This will then feed the information to the Customer information screens on the stations and also to the online timetables. The excerpts in the attached document “Communications” are taken from the Tyrell system, showing the communications regarding the service agreement plan with the Network Rail for 9R90, 9T97, 9R92, 9T94, 9T84 and 9N96.
If this is not the information you are looking for, or if you are unable to access it for any reason, please do not hesitate to contact me.
Please see the attached information sheet for details of your right to appeal as well as information on copyright and what to do if you would like to re-use any of the information we have disclosed.
Yours sincerely,
David Wells FOI Case Officer FOI Case Management Team General Counsel Transport for London
