Trespass incident between Paddington and Reading causing problems (6/10/2010)

[whole diary]

[Chris from Nailsea]

From FGW^▸ (First Great Western) live updates:

Line incident

Line problem between London Paddington and Reading.

Train services have been disrupted due to a trespass incident between London Paddington and Reading. Short notice cancellations and delays of up to 30 minutes can be expected.

London Underground, Chiltern Railways, South West Trains and CrossCountry Trains are currently accepting First Great Western tickets.

Last Updated: 06/10/2010 17:27

Service incidents

15:57 London Paddington to Banbury due 18:15
This train has been revised. It will no longer call at: Tilehurst, Pangbourne, Goring & Streatley, Cholsey, Didcot Parkway, Appleford, Culham and Radley. This is due to a trespass incident.
Last Updated: 06/10/2010 17:25

16:00 London Paddington to Bristol Temple Meads due 17:41
This train will be started from Reading. It will no longer call at: London Paddington. This is due to a trespass incident.
Last Updated: 06/10/2010 16:24

16:18 London Paddington to Bedwyn due 17:45
This train will be started from Reading. It will no longer call at: London Paddington. This is due to a trespass incident.
Last Updated: 06/10/2010 16:25

16:27 London Paddington to Oxford due 18:11
This train has been revised. It will call additionally at: Appleford and Culham. This is due to a trespass incident.
Last Updated: 06/10/2010 17:38

16:37 Oxford to London Paddington due 18:31
This train will be formed of 3 coaches instead of 5.
Last Updated: 06/10/2010 15:06

16:42 London Paddington to Reading due 17:46
This train has been cancelled. This is due to a trespass incident.
Last Updated: 06/10/2010 17:37

16:48 London Paddington to Oxford due 17:50
This train has been cancelled. This is due to a trespass incident.
Last Updated: 06/10/2010 17:08

17:12 London Paddington to Henley-On-Thames due 18:13
This train will be terminated at Twyford. It will no longer call at: Wargrave, Shiplake and Henley-On-Thames. This is due to a trespass incident.
Last Updated: 06/10/2010 17:00

18:17 Henley-On-Thames to Twyford due 18:29
This train has been cancelled. This is due to a trespass incident.
Last Updated: 06/10/2010 17:06

18:31 Oxford to London Paddington due 19:31
This train has been cancelled. This is due to a trespass incident.
Last Updated: 06/10/2010 17:10

[Oxman]

A suicidal person climbed onto one of the gantries at Royal Oak, just outside Paddington. All trains stopped and the power was switched off to the overhead wires. Took about an hour to get trains moving again.

[adc82140]

Sat on the 17:18 to Oxford at Paddington, only to be told that the 17:12 Henley train (albeit terminating at Twyford) had arrived in front of us, so the quickest way to Maidenhead would be on that. Dutifully boarded that, and crawled along the slow lines behind a heavily loaded stopper for the whole journey. London-Maidenhead was just over the hour. To add insult to injury the 17:18 overtook us on the fast lines at Southall, almost empty.

So although not FGW^▸ (First Great Western)'s fault initially, a poor show re: correct information for the passengers.

[Chris from Nailsea]

Problems are continuing, apparently - from FGW^▸ (First Great Western) live updates:

Line incident

Line problem between London Paddington and Reading.

Train services have been disrupted due to a trespass incident between London Paddington and Reading. Short notice alterations, cancellations and delays of up to 30 minutes can be expected.
Last Updated: 06/10/2010 18:21

Service incidents

17:36 London Paddington to Paignton due 21:17
This train will be started from Exeter St Davids. It will no longer call at: London Paddington, Reading, Newbury, Pewsey, Westbury, Castle Cary, Taunton and Tiverton Parkway. This train will be formed of 2 coaches instead of 8. This is due to a trespass incident.
Last Updated: 06/10/2010 18:31

17:50 London Paddington to Worcester Shrub Hill due 20:23
This train has been delayed at Reading and is now 24 minutes late. This is due to a trespass incident.
Last Updated: 06/10/2010 18:50

18:15 London Paddington to Oxford due 20:14
This train has been delayed and is now 60 minutes late. This train has been revised. It will no longer call at: Ealing Broadway, Southall, Hayes & Harlington, West Drayton, Langley, Slough, Burnham, Maidenhead and Twyford. This is due to a trespass incident.
Last Updated: 06/10/2010 19:21

19:01 Oxford to London Paddington due 20:59
This train will be started from Reading. It will no longer call at: Oxford, Radley, Didcot Parkway, Cholsey, Goring & Streatley, Pangbourne and Tilehurst. This is due to a trespass incident.
Last Updated: 06/10/2010 19:34

20:48 Reading to London Paddington due 21:48
This train has been cancelled. This is due to a trespass incident.
Last Updated: 06/10/2010 19:18

[johoare]

I agree with adc82140 re information

I got to Paddington about 18.45.. Most trains were showing as delayed. The 19.06 was showing as on time and in fact stayed that way until 19.04 when that also became delayed..(why I ask myself)

Anyway finally it arrived.. That was a total bun fight to get on.. It's still two carriages only which is totally ridiculous in everyone apart from FGW^▸ (First Great Western)'s eyes.. I had to apologise to some poor man for me pushing him although it wasn't my fault.. I was being pushed and just couldn't make myself any smaller..(I tried very hard)..

Once we were all on the train they announced that if anyone was going to Maidenhead the 19.18 was on the adjacent platform.. Both trains are first stop Maidenhead.. So, some people who weren't regular commuters got off to get the other train as the announcement said no more than that and I guess made them think that the train they were on wasn't going to stop at Maidenhead..

Oh well.. I was only 20 mins or so late and for once had a seat on the 19.06.. and that was only cos I got shoved onto the train 

[BBM]

Sat on the 17:18 to Oxford at Paddington, only to be told that the 17:12 Henley train (albeit terminating at Twyford) had arrived in front of us, so the quickest way to Maidenhead would be on that.

Having abandoned any hope of getting my usual train, the 17:06 to Westbury (first stop Twyford), I was also on the 17:18 when there was the announcement about the 17:12 being in front (why block the 17:18 like that?). Knowing that the 17:12 is scheduled to take the relief line for its whole journey I decided to take a chance and ran back to the footbridge to see if there was any news on the 17:06. It was still showing as 'Delayed', however the 17:33 to Oxford (calling at Maidenhead and Twyford) was showing as 'Preparing'. By now it was about 17:25 and after a short while the 17:33 was announced as going from Platform 1. As soon as I reached the bottom of the footbridge steps the 17:06 was announced as going from Platform 3! So I decided to chance that and ran back over the footbridge (boy you have to be fit to be an FGW^▸ (First Great Western) commuter! ).

The result of all this was that the 17:33 left on time and the 17:06 left about 3 minutes behind it. I guessed that we might overtake the 17:33 at Maidenhead and that indeed happened. Arrival at Twyford was at just before 18:00 so I was definitely quicker home than if I'd taken the 17:12 or the 17:33, not sure though what happened to the 17:18?

[Chris from Nailsea]

From FGW^▸ (First Great Western) live updates:

Line incident

Line problem between London Paddington and Reading.

Train services are now running normally between London Paddington and Reading.

Last Updated: 06/10/2010 21:34

 

[johoare]

Smashing 

[SDS]

Were murmurs of an incident being spoken over the radios for a while, but as should be nothing solid was spoken.
at 15:55 was told no trains to be dispatched and the overheads had been isolated. Furthermore the DC^▸ (Direct Current) lines between Hammersmith and Edgeware Road were also turned off.
Male was hanging over lines 5-6 and LUL^▸ (London Underground Ltd).

BTP^▸ (British Transport Police) originally decided to give lines 1-3 back but then changed their minds.
BTP refused to give lines back until MOM^▸ (Mobile Operations Manager) was on site.

The 16:00 BRI^» (Bristol Temple Meads - next trains) never got dispatched and was cancelled. It was then turned into the 16:30 and then every commuter under the sun decided to get on that one train. TM^‡(resolve) Refused to take it on safety grounds.

Not to call order issued for RDG^‡(resolve) (but it did stop there).
All platforms all over the place, trains all over the place.
The 16:00 now 16:30 left at around 17:10.

Loads of westbury people tried to get on assuming that because every other day of the week it goes from platform 8, it would today. READ THE SCREENS this is a Bristol train, no its not the westbury train.
Grrrrrr.

[Chris from Nailsea]

Hmm.  You do seem to have had a bit of a fraught day of it, SDS pad. 

However - just for clarity - may I ask, what is MOM^▸ (Mobile Operations Manager)?

CfN. 

[John R]

The 16:00 BRI^» (Bristol Temple Meads - next trains) never got dispatched and was cancelled. It was then turned into the 16:30 and then every commuter under the sun decided to get on that one train. TM^‡(resolve) Refused to take it on safety grounds.

Can confirm that, as TM was telling a colleague taking over at Bristol what had happened. Standard was rammed all the way to Bristol apparently.  Not surprising really as it was taking the load for three trains as it didn't get away until after 1700.

[JayMac]

Well, I got to hear of the problems in that London all the way down in deepest, darkest (actually quite bright today!) Cornwall. Overheard the Train Manager talking to the Customer Host.

Honestly!

[johoare]

Oh dear as I didn't get to hear about any of it until I got to Paddington about 18.45.. I MUST remember to check departures boards at Paddington every single day.. No need to rush if there is no need to rush 

[devon_metro]

Hmm.  You do seem to have had a bit of a fraught day of it, SDS pad. 

However - just for clarity - may I ask, what is MOM^▸ (Mobile Operations Manager)?

CfN. 

Mobile ops manager afaik.

[Chris from Nailsea]

Thanks!  I'll add it to our 'acronyms / abbreviations' list.