Ealing Broadway - station facilities, access issues and many sad incidents (merged posts)

[whole diary]

[James Vertigan]

ActonW3.com now has article online suggesting a 40-year old female was on the high speed tracks and was hit by the 10:15 service to Cardiff.

http://www.actonw3.com/info/conaccident021.htm

[Chris from Nailsea]

And yet again, sadly - from FGW^▸ (First Great Western) live updates:

Line incident

Line problem between Reading and London Paddington.
Train services are being disrupted due to a person hit by a train between Reading and London Paddington. Short notice alterations, cancellations and delays can be expected.
Services are currently unable to call at Ealing Broadway station. First Great Western ticket holders may use London Underground services between Ealing Broadway and London Paddington.
Last Updated: 12/12/2010 19:21

Service incidents

18:05 Oxford to London Paddington due 19:51
This train has been revised. It will no longer call at: Ealing Broadway. This is due to a person hit by a train.
Last Updated: 12/12/2010 19:32

18:43 London Paddington to Oxford due 20:25
This train has been revised. It will no longer call at: Ealing Broadway. This is due to a person hit by a train.
Last Updated: 12/12/2010 19:18

19:15 London Paddington to Reading due 20:12
This train has been cancelled. This is due to a person hit by a train.
Last Updated: 12/12/2010 19:08

19:43 London Paddington to Oxford due 21:27
This train has been revised. It will no longer call at: Ealing Broadway. This is due to a person hit by a train.
Last Updated: 12/12/2010 19:34

[Chris from Nailsea]

Update, from FGW^▸ (First Great Western) live updates:

Line incident

Line problem between Reading and London Paddington.
Train services have been disrupted due to a person hit by a train earlier between Reading and London Paddington. Short notice alterations, cancellations and delays may still occur.
First Great Western ticket holders may use London Underground services between Ealing Broadway and London Paddington.
Last Updated: 12/12/2010 20:06

Service incidents

18:43 London Paddington to Oxford due 20:25
This train has been revised. It will no longer call at: Ealing Broadway. This is due to a person hit by a train.
Last Updated: 12/12/2010 19:18

19:15 London Paddington to Reading due 20:12
This train has been cancelled. This is due to a person hit by a train.
Last Updated: 12/12/2010 19:08

19:43 London Paddington to Oxford due 21:27
This train will be terminated at Reading. It will no longer call at: Tilehurst, Pangbourne, Goring & Streatley, Cholsey, Didcot Parkway, Radley and Oxford. This is due to a person hit by a train earlier.
Last Updated: 12/12/2010 20:06

[IndustryInsider]

Tonight's was a very low speed one, with the person concerned trapped under the train for some time, eventually taken to hospital but not killed.  That's why after a short while, the main lines were open again.

[Chris from Nailsea]

Thanks for that further information, IndustryInsider! 

[Brucey]

From FGW^▸ (First Great Western) JourneyCheck

Owing to a person hit by a train between London Paddington and Slough all lines are blocked.

Impact:
Train services running through these stations may be cancelled or delayed by up to 45 mins at short notice. An estimate for the resumption of normal services will be provided as soon as the problem has been fully assessed.

Service involved was the 15:48 Heathrow T5 to London Paddington (Heathrow Express) service.

[James Vertigan]

Picking up news of a fatality at Ealing Broadway a little earlier this afternoon.

As always, thoughts with the train crew involved and the family of the deceased.

[Chris from Nailsea]

An update, from First Great Western JourneyCheck:

Line problem: between London Paddington and Slough
Following a person hit by a train earlier between London Paddington and Slough all lines have now reopened.
Train services running through these stations are returning to normal but some services may still be cancelled or delayed by up to 30 mins at short notice. Disruption is expected until 18:00 10/02.
Message Received: 10/02/2013 17:44

[TonyK]

From Twitter:

First Great Western @FGW^▸ (First Great Western)

For Information. Owing to a person hit by a train between London Paddington and Slough all lines are blocked.

[Chris from Nailsea]

Thanks for posting, FTN, but as this relates to the same incident, I've moved your post and merged it here. 

[trainer]

I was on the 16:03 to Bristol TM^‡(resolve) (BRI^» (Bristol Temple Meads - next trains)) which only got as far as Acton before being sent back to Paddington.  It was re-started at approx 16:58 as a fast service to Chippenham then picking up the normal calling pattern of Bath Spa, and BRI.  In all his announcements the Train Manager reminded us that all the disruption was because of 'a tragedy' at Ealing, which I think helped us keep things in proportion.

However, there was major disruption to many people as all those for Reading, Didcot Pkwy and Swindon disembarked and re-boarded the service behind, and many waiting for the later service boarded our train giving the standard class section the air of the rush hour and many standing for over an hour.  The train manager (I think wisely) checked no tickets in first class and a few 'lucky' pax travelled in comfort they hadn't paid for (I was on 1st Class Rover) and although not announcing that he was not enforcing the rules , tacitly did so.  He also kept us informed personally (before the train filled to bursting) by walking through the train.

The upshot was that I was only 55 minutes late at BRI and the set and crew were positioned to return on the 19:00 to Paddington.  I believe full marks are due to those who were able to deal with the original incident with alacrity (and I hope sensitivity) those who decided to run the service fast to Chippenham and the train crew for keeping us informed.  The down side was the severe overcrowding for much of the journey, but since those who packed onto the train after its return to Paddington could have caught the train they had originally gone for and probably had a seat after Reading, there may have been an element of a self-inflicted wound.  Because I don't know what was announced on the platform, I can't reach a full judgement about this.

I was fortunate.  There will be those tonight with less happy images of dealing with what happened and at least one family bereft of a loved one.

[Chris from Nailsea]

Thanks for posting those constructive and thought-provoking comments, trainer.

[Ollie]

Thanks for posting those constructive and thought-provoking comments, trainer.

My understanding is the person in question didn't die at the scene and was taken by paramedics, so I do hope that the person gets the help they need and has a speedy recovery.

Thoughts do of course go to those involved who witnessed it all.

[trainer]

Thanks for that update Ollie.  That may explain why the lines re-opened so swiftly.

[Chris from Nailsea]

From the BBC^» (British Broadcasting Corporation - home page):

Wales rugby fans suffer train disruption in London

Wales rugby fans coming home by train following the Six Nations win over France in Paris could face long delays.

First Great Western services between London Paddington and south Wales have been disrupted after a person was hit by a train at Ealing Broadway. Services may be cancelled or delayed by up to 45 minutes at short notice, said the train operator.

Fans returning to west Wales by train on Sunday already faced up to 75 minutes added to journey times.

Engineering work meant First Great Western and Arriva Trains Wales services were suspended between Cardiff and west Wales with buses running instead.

Wales beat France 16-6 on Saturday, their first win in this year's Six Nations.