Leeds trains: Heavy flooding on railway line cause disruption and cancellations between Horsforth and Harrogate
and live on Freeview channel 276
Trains running between Leeds and Harrogate this morning (Friday February 9) ran the risk of being cancelled, delayed by up to 40 minutes or revised.
Advertisement
Hide AdAdvertisement
Hide AdNational Rail advised its customers to use the real-time Journey Planner before travelling.
Severe flooding on the railway cause delays
The flooding is affecting the LNER service between London Kings Cross and Harrogate as well as the Northern service between Leeds and Harrogate, Knaresborough and York.
LNER replacement services
Replacement coaches provided by York Pullman have been requested by LNER from Leeds and are en route to Harrogate.
Customers can use their LNER tickets on Northern services to complete their journey.
Northern customers
Northern has provided alternative travel suggestions, advising its customers to travel on the mainline via Cross Gates and Micklefield between Leeds and York.
Northern tickets will also be accepted on TransPennine Express and alternative Northern services between Leeds and York.
Network Rail on location
Network Rail are on site assessing the flooding, and disruption is expected to last until 10.15am.
LNER services affected
A number of trains to and from Kings Cross Station passing through Leeds have been affected by the floods:
Lines reopened
National Rail has confirmed that lines have reopened following heavy rain flooding the railway between Horsforth and Harrogate.
Keep in mind that trains running between Leeds and Harrogate may still be cancelled, delayed by up to 40 minutes or revised whilst service recovers.
Disruption is still expected until 10.15,
Trains are operating like normal again
Trains are now able to run like normal between Horsforth and Harrogate.
Thanks for following this live blog!
Comment Guidelines
National World encourages reader discussion on our stories. User feedback, insights and back-and-forth exchanges add a rich layer of context to reporting. Please review our Community Guidelines before commenting.