Delay on the evening of 27th September eastbound on the District Line. I was left waiting at Barking for about 30minutes whilst 4-5 trains terminated there. Even the drivers exiting the terminating trains were being quizzed by TFL staff about the delay for a through train to Upminster and why so many in succession had terminated there. On attempting an Oyster travel refund online I was told it was unsuccessful as there were no reported delays that evening. I would like to know how and why this wasn't recorded. I got on the train at 22:50 at Aldgate East, it terminated at Barking where I waited at length for a through train to Upminster. I finally checked out at 23:57 at Elm Park.

---

Our ref: FOI-1914-1718/GH

Thank you for your request received by Transport for London (TfL) on 17 October 2017 asking for information about a delay on the District Line.

Your request has been considered under the requirements of the Freedom of Information Act 2000 and our information access policy. I can confirm that we do hold the information you require.

The table below shows the trains relevant to your journey on 27 September 2017.

The top line, which is highlighted shows the Hammersmith & City Train 213 which you alighted from and was scheduled to terminate Barking.

The next train into Barking was also a H&C Train 264 scheduled to terminate at Barking.

The next District train to arrive was 033 and this was the only train to terminate short at Barking to go back westbound.

The next train to arrive was another H&C (T265) to Barking.

The last line shows the District line train T007 which is the train which took you to Upminster. This train was scheduled to depart at 23.33 but did not depart until 23.44. The records show that you waited in total approximately 28 minutes.

The timetable below shows the scheduled trains. The train numbers are shown on the top row of the table.

Train 006 was scheduled to leave Barking at 23.13. This train was cancelled, however, as you arrived at Barking at 23.16 you would not have been able to board this service anyway.

Train 122 was also cancelled but was always timetabled to terminate at Barking.

Service T033 was timetabled to go to Upminster but was terminated short at Barking.

Timetable:-

The information available to our Oyster team only shows more general problems which would affect many people using our services. On this occasion there were no actual delays noted as the problems you experienced were due to cancellations/termination of service. Despite the difficulties you experienced the overall service on the line was still considered to be ‘good’. When you raised your complaint this should have been looked into further, and the reasons for the problems you experienced would then have been noted.

I am sorry that a further investigation was not carried out, and for the inconvenience caused on the day of your journey. I note that, although our Oyster team did not identify the cause of your delay, they did credit your web account with £3.10 as a gesture of goodwill.

If this is not the information you are looking for, or if you are unable to access it for some reason, please do not hesitate to contact me.

If you are not satisfied with this response please see the attached information sheet for details of your right to appeal.

Yours sincerely

Graham Hurt

FOI Case Officer

FOI Case Management Team

General Counsel

Transport for London

Back to top

---