Train Graphic
Great Western Passengers' Forum Great Western Coffee Shop - [home] and [about]
Read about the forum [here].
Register and contribute [here] - it's free.
 today - ACoRP board nominations close
29/10/2018 - Avocet line AGM
30/10/2018 - Minehaed Rail Link Group
31/10/2018 - CCIF Applications close
06/11/2018 - Talk Oxford / 800 intro
10/11/2018 - RailFuture National Conference
Random Image
Train Running @GWR Twitter Acronyms/Abbreviations Station Comparator Rail News GWR co. site Site Style 1 2 3 4 Chat on off
October 22, 2018, 03:27:18 am *
Welcome, Guest. Please login or register.

Login with username, password and session length
Forgotten your username or password? - get a reminder
Most liked recent subjects
[114] IETs into passenger service from 16 Oct 2017 and subsequent pe...
[90] Cambrian ERTMS - Loss of TSR Data (20/10/2017)
[61] Tram Surfer Awarded 485000 Damages
[52] Weymouth Harbour railway line - merged topic, ongoing discussi...
[42] Where was Lee?
[41] Weekend Engineering Works
News: A forum for passengers ... with input from rail professionals welcomed too
 
   Home   Help Search Calendar Login Register  
Pages: [1]
  Print  
Author Topic: Track problems near Earley  (Read 747 times)
eightonedee
Transport Scholar
Sr. Member
******
Posts: 118


View Profile
« on: August 03, 2018, 09:16:14 pm »

A warning for anyone using the North Downs line in and out of Reading this week.

For the second time in two days, there was a suspension of services between Wokingham and Reading for "inspection of possible track defect" in the early evening. Last night I took the Woking/Basingstoke zigzag route to avoid the problem, only to discover that the three trains held at Guildford were released shortly after I departed.

Today trains were running again by the time I left work, and I noticed discarded rail in sections lying on the eastbound track sleepers just west of Earley, so it seems there has been a stretch of rail replaced on the westbound side. We ran slow through this section, so I assume this is likely to persist for a few days if this heat continues.

Not a good week on this line this week - I was not in work on Wednesday, but I was told that trains to Reading were suspended due to a problem near Wanborough during the early evening as well.
Logged
CyclingSid
Transport Scholar
Sr. Member
******
Posts: 207


View Profile
« Reply #1 on: August 04, 2018, 08:41:56 pm »

I wonder if this is related to the incident discussed under the "Electricity failure", although it seems a long time for them to identify it.
Logged
CyclingSid
Transport Scholar
Sr. Member
******
Posts: 207


View Profile
« Reply #2 on: August 12, 2018, 11:13:57 am »

Another unlucky Saturday for the North Downs line.

Tree down between Wokingham and Crowthorne. My return trip from Brighton ended up allowing me to refresh my knowledge of Clapham Junction. All in all not a good day, I don't think a single train I used ran to time.
Logged
bobm
Administrator
Hero Member
*****
Posts: 6959



View Profile
« Reply #3 on: August 12, 2018, 05:57:32 pm »

Not been a particularly good Sunday.

The signal at the end of platform 1 at Wokingham will not clear for trains heading towards Bracknell so all Waterloo trains have had to be talked past it most of the days.  Services to Redhill and Gatwick are not affected but have occasionally been delayed while a SWR service clears the junction.
Logged
eightonedee
Transport Scholar
Sr. Member
******
Posts: 118


View Profile
« Reply #4 on: October 12, 2018, 10:34:22 pm »

Things seem to be getting worse on the line - speed restrictions in both directions between Ash and Guildford, and on the approach to Reading over the London Road bridge have resulted in poor timekeeping. There also seem to be problems east of Guildford.

There has though been almost no information, either at stations or on Journey Check which has typically been optimistic when estimating train arrival times for delayed services already on their way. However this evening the 18-26 ex-Guildford, 21 minutes late departing and 30 late into Reading was shown on Journey Check as cancelled beyond Wokingham - until it actually left that station.

Anyone any idea why it's got so poor?

Logged
Fourbee
Hero Member
*****
Posts: 511


View Profile
« Reply #5 on: October 13, 2018, 08:06:59 am »

Things seem to be getting worse on the line - speed restrictions in both directions between Ash and Guildford, and on the approach to Reading over the London Road bridge have resulted in poor timekeeping. There also seem to be problems east of Guildford.

The TSRs East of Wanborough I believe are going to be sorted in 'October'. I assume it's an embankment/ground issue. I heard a pair of GWR drivers complaining about them recently.
Logged
martyjon
Transport Scholar
Hero Member
******
Posts: 1166


View Profile
« Reply #6 on: October 13, 2018, 09:25:07 am »

Things seem to be getting worse on the line - speed restrictions in both directions between Ash and Guildford, and on the approach to Reading over the London Road bridge have resulted in poor timekeeping. There also seem to be problems east of Guildford.

The TSRs East of Wanborough I believe are going to be sorted in 'October'. I assume it's an embankment/ground issue. I heard a pair of GWR drivers complaining about them recently.

October , what year ?
Logged
eightonedee
Transport Scholar
Sr. Member
******
Posts: 118


View Profile
« Reply #7 on: October 15, 2018, 10:20:39 pm »

Still misery and disruption on the North Downs line.

Speed restrictions apparently partly removed between Wanborough and Ash this morning, but slow eastbound. Trains generally late into Reading with knock-on delays on services back to Guildford, Redhill & Gatwick.

This evening semi-meltdown. GW's website advised that most services were running on time with no reported problems. However, 17-44 ex Guildford cancelled, I didn't get away in time for 18-04 (started from Shalford). Next two trains (started in theory from Redhill and Gatwick) subject to conflicting information on GW website and Journey Check, apparently due to signal problems at Gatwick, unclear which starting first, but clear will be late. At one stage it seems later limited stop train may leave earlier, but then clarified that it will not, but its shown arriving earlier at Guildford (later corrected after a period when no Guildford arrival time shown, but earlier at Reading - this later corrected too). Surely someone entering data onto Journey Check must know that aside from Guildford there is nowhere en route for one train to pass another?

Eventually 18-26 ex-Guildford leaves at 18-55, Journey Check promises arrival at 19-35 (actual arrival 19-46). It's a 2 car train full of Gatwick passengers with luggage, piled on or between seats. I sit with an elderly couple, he recovering from hip surgery, anxious about catching onward train at 19-50 from Reading to Pershore, and two elderly women who miss a 19-30 for Newton Abbot, so face an hour's wait for the next train. Fortunately the Pershore couple's daughter arranges assistance at Reading.

During the journey another commuter and I keep them informed from Journey Check, warning them that the information would be (as usual) hopelessly optimistic about catching up the delay, especially as speed restriction still on part of Wanborough to Ash and also over London Road road bridge in Reading. There was just one inaudible on-board announcement.  Understandably our four elderly holidaymakers vow never to take the train to Gatwick again, and one suggests ceremonially burning her railcard at Reading.

I am sorry GWR - THIS IS SIMPLY NOT GOOD ENOUGH!   
Logged
Do you have something you would like to add to this thread, or would you like to raise a new question at the Coffee Shop? Please [register] (it is free) if you have not done so before, or login (at the top of this page) if you already have an account - we would love to read what you have to say!

You can find out more about how this forum works [here] - that will link you to a copy of the forum agreement that you can read before you join, and tell you very much more about how we operate. We are an independent forum, provided and run by customers of Great Western Railway, for customers of Great Western Railway and we welcome railway professionals as members too, in either a personal or official capacity. Views expressed in posts are not necessarily the views of the operators of the forum.

As well as posting messages onto existing threads, and starting new subjects, members can communicate with each other through personal messages if they wish. And once members have made a certain number of posts, they will automatically be admitted to the "frequent posters club", where subjects not-for-public-domain are discussed; anything from the occasional rant to meetups we may be having ...

 
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.2 | SMF © 2006-2007, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
This forum is provided by a customer of Great Western Railway (formerly First Great Western), and the views expressed are those of the individual posters concerned. Visit www.gwr.com for the official Great Western Railway website. Please contact the administrators of this site if you feel that the content provided by one of our posters contravenes our posting rules (email link). Forum hosted by Well House Consultants