FOI request detail

TFL Rail Breakdowns 2016 to present

Request ID: FOI-1349-1718
Date published: 15 November 2017

You asked

Hi, Could you please send data on the number of tfl rail breakdowns since January 2016 to present? To clarify, I would like details of any train fault causing a delay of 30 minutes or more, or any train that has had to be removed from service Many thanks

We answered

Thank you for your email received by us on 4 September 2017 asking for information about TfL Rail train cancellations since January 2016.

Your request has been considered in accordance with the requirements of the Freedom of Information Act and our information access policy. I can confirm that we hold the information you require. You asked for:

data on the number of tfl rail breakdowns since January 2016 to present?

To clarify, I would like details of any train fault causing a delay of 30 minutes or more, or any train that has had to be removed from service

Transport for London began managing the Liverpool Street to Shenfield rail service in May 2015. Currently operating as TfL Rail, this service will form the part of the Elizabeth line when it opens from December 2018.

TfL Rail is undergoing a series of major improvements to both infrastructure and train services, such as the introduction of new trains and refurbished ticket halls as explained here on our website:

https://tfl.gov.uk/travel-information/improvements-and-projects/tfl-rail-improvements?intcmp=35316

Please find attached the requested data showing delays of thirty minutes or more; an explanation of the headings and codes used in the table is listed below:

· Incident Description – These details are provided by Network Rail on the day of the incident. Further detail to note:

o Headcode – Always presented as three numbers and one letter, which denotes the train’s identity. Headcodes are not unique to a single Train Operating Company, they can be replicated across the country. The first number is the ‘class’ of the train, indicating an express passenger service (Class 1), or stopping service (Class 2). MTR Crossrail, who operate the service on our behalf, always run with Class 2 headcodes.

o Title – If the issue is related to a Fleet cause, the words ‘Unit Defect’ are typically used. Occasionally more specific information may be referenced such as PA (Public Announcement), or Door Defect. Again, this is created by Network Rail on our behalf.

o Location – All stations within the UK are allocated a three letter ‘CRS’ code, used internally within the rail industry. They are usually reflective of the station name’s spelling, for example, the code for Shenfield is ‘SNF’. A full list can be found by referring to this website: http://www.railwaycodes.org.uk/crs/CRS0.shtm .

· Delay Minutes Incurred – This is the level of impact caused by the incident, inclusive of both primary and reactionary delay. For instance, a train experiencing difficulty at Ilford might only incur a five minute delay to its schedule but consequently could cause 60 minutes of reactionary delay to other services. This is accounted for in the information attached.

· Number of Cancellations – If the fault cannot be rectified, it may be necessary to cancel the service altogether. Additionally, if the fault caused severe late running to other services, a decision may be made to cancel some trains to enable a speedier recovery in overall service.

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

Jasmine Howard
FOI Case Officer
Information Governance
Transport For London

Attachments

Back to top

Want to make a request?

We'll email you the response within 20 working days.


We'll publish the response online without disclosing any personal information.