|
Palfers
|
 |
« on: May 17, 2015, 22:52:51 » |
|
Some big delays tonight due to person being hit by a train. This one caught my attention by how much it's delayed!!! 20:57 London Paddington to Exeter St Davids due 23:19
This train will be starting late from London Paddington by 100 minutes and will be further delayed between Reading and Exeter St Davids.
This train will be diverted between Reading and Exeter St Davids.
This train will no longer call at Taunton and Tiverton Parkway.
This is due to a person hit by a train earlier.
Message Received :17/05/2015 22:30
Time Destination
20:57 London Paddington 22:37
21:31 Reading 23:11
23:19 Exeter St Davids 01:49
|
|
|
|
|
Logged
|
|
|
|
|
Adelante_CCT
|
|
« Reply #1 on: May 18, 2015, 05:54:27 » |
|
01:15 arrival in Exeter, not too bad then
|
|
|
|
|
Logged
|
|
|
|
|
Southernman
|
|
« Reply #2 on: May 18, 2015, 08:34:03 » |
|
Diverted via Yeovil. Appears to have free run down, crossing the up sleeper between Pinhoe and Exeter Central.
Lost 7 minutes (only) on the schedule between Castle Cary and Exeter despite the trundle down to Yeovil Pen Mill. Running time between Yeovil Junction and Exeter St Davids approx. 43 minutes.
All it needs for double track to be re-instated and then you have a fast line alternative from London to Exeter (and whisper it, perhaps to Plymouth via Okehampton)!! Wonder if the new Government will deliver on some of the proposed improvements...
|
|
|
|
|
Logged
|
|
|
|
|
TaplowGreen
|
|
« Reply #3 on: May 18, 2015, 17:40:37 » |
|
I did hear that the person hit by the train has survived, but that's unconfirmed.
|
|
|
|
|
Logged
|
|
|
|
|
bobm
|
|
« Reply #4 on: May 18, 2015, 18:05:47 » |
|
The person, a 54 year old man, was taken to hospital by air ambulance but, sadly, later died.
|
|
|
|
|
Logged
|
|
|
|
|
jane s
|
|
« Reply #5 on: May 19, 2015, 13:31:43 » |
|
I was unfortunately caught up in this. Arrived at Paddington @8pm, finally got on a train @ 9:35pm. Had assumed that stopper to Oxford would be started from Reading (were all cancelled from Padd) but when I got there @ 10:30ish, was nothing scheduled until 23:48!
Eventually (with help of the duty police, who were very sympathetic to a group of passengers frustrated by total lack of announcements and asisstance from staff) we got put into taxis.
|
|
|
|
|
Logged
|
|
|
|
|
Chris from Nailsea
|
|
« Reply #6 on: May 19, 2015, 21:45:25 » |
|
Purely in the interests of clarity and ease of future reference, I've amended the heading of this topic. Another sad story from the railways: our thoughts are with the family and friends of the deceased.  |
|
|
|
|
Logged
|
William Huskisson MP▸ was the first person to be killed by a train while crossing the tracks, in 1830. Many more have died in the same way since then. Don't take a chance: stop, look, listen.
"Level crossings are safe, unless they are used in an unsafe manner." Discuss.
|
|
|
|
PhilWakely
|
|
« Reply #7 on: May 20, 2015, 10:15:14 » |
|
Forgive me for being somewhat dim  The OP▸ refers to 1C98 delayed from 20:57 to 22:37 and I can understand the unfortunate reason for said delay. However, according to Real Time Trains, there was an additional service (1Z98) which departed PAD» at 21:30 for Plymouth via Newbury, Westbury and Taunton which was only 15 late at Exeter, so was there another reason for the huge delay to 1C98? |
|
|
|
|
Logged
|
|
|
|
|
Godfrey Tables
|
|
« Reply #8 on: May 22, 2015, 16:46:33 » |
|
I too was caught up in the disruption on the Sunday. I went to the station earlier today, only to find it's happened yet again. That's the same place twice in one week. What a tragedy, and thoughts go to all those involved |
|
|
|
|
Logged
|
|
|
|
|
Western Pathfinder
|
|
« Reply #9 on: May 22, 2015, 18:51:02 » |
|
Yet again it would seem that the actions of one sad person have caused major havoc to thousands of people who at the end of the working week now face hours on the journey time before they can start the weekend my thoughts go out to all that are caught up in this mess and especially the BTP▸ and the other services who have the task of clearing it up hope the driver will be ok. WP.
|
|
|
|
|
Logged
|
|
|
|
|
Oxonhutch
|
|
« Reply #10 on: May 22, 2015, 19:23:11 » |
|
It was my train that struck the person and I knew immediately what had happened - I won't elaborate. I got up as we ground to a halt on the country side of Twyford and caught the initial conversation of the lady train manager with the driver. Her face was was one of shock and after listening to the driver said "how are you?". Nice concern from a team. No mention on board of person-hit-by-train - standard operating procedure but I knew we were going to be there for the next few hours. BTP▸ x 2 walked down from TWY▸ with fitter and driver relief. Carriage and wagon inspection, BTP walk-through and phoning ahead for an unaccompanied minor on the train and we set off under caution clear of Twyford West Junction and set back - bang road - to the up main to Twyford p2 where the train terminated. The passengers were picked up by a Bristol now running on the down relief.
I have been delayed many times at Paddington as a consequence but never on the train involved. Not nice. Sympathies to all - not least the driver and the family of the person hit.
|
|
|
|
« Last Edit: May 22, 2015, 19:53:39 by Oxonhutch »
|
Logged
|
|
|
|
|
phile
|
|
« Reply #11 on: May 22, 2015, 20:42:07 » |
|
It was my train that struck the person and I knew immediately what had happened - I won't elaborate. I got up as we ground to a halt on the country side of Twyford and caught the initial conversation of the lady train manager with the driver. Her face was was one of shock and after listening to the driver said "how are you?". Nice concern from a team. No mention on board of person-hit-by-train - standard operating procedure but I knew we were going to be there for the next few hours. BTP▸ x 2 walked down from TWY▸ with fitter and driver relief. Carriage and wagon inspection, BTP walk-through and phoning ahead for an unaccompanied minor on the train and we set off under caution clear of Twyford West Junction and set back - bang road - to the up main to Twyford p2 where the train terminated. The passengers were picked up by a Bristol now running on the down relief.
I have been delayed many times at Paddington as a consequence but never on the train involved. Not nice. Sympathies to all - not least the driver and the family of the person hit.
What was the train ? |
|
|
|
|
Logged
|
|
|
|
|
bobm
|
|
« Reply #12 on: May 22, 2015, 20:55:07 » |
|
14:45 London Paddington to Swansea
|
|
|
|
|
Logged
|
|
|
|
|
John R
|
|
« Reply #13 on: May 23, 2015, 10:03:35 » |
|
I was caught up in this trying to get from SWI» to NLS in the early evening.
What struck me was the poor decision by control to run the 1630 PAD» to TAU» non stop from BRI» to TAU. Yes, it was running 45 mins late, so needed to make up time if it were to have a prompt departure on the return trip, but just about everyone on the train would be travelling to the intermediate stations.
Whilst they held the 1855 BRI to TAU for 15 mins to make sure people got the connection, the result was that the 2 car 150 was crushed to capacity and many people were not able to board. A more sensible approach would have been to have retained a couple of stops on the 1630 to keep on board enough pax to enable the local unit to cope. As it turned out the 1630 arrived in TAU only 8 mins late. A couple of intermediate stops would still have enabled an arrival within 15 mins of booked time, and probably removed over 100 people from the local.
Appreciate that control have a lot of things to manage under such difficult circumstances but it did appear that in this instance they put the priority of punctual timekeeping over the needs of passengers.
|
|
|
|
|
Logged
|
|
|
|
|
TaplowGreen
|
|
« Reply #14 on: May 23, 2015, 10:13:30 » |
|
Still having an impact this morning with the first PNZ-PAD» cancelled.
|
|
|
|
|
Logged
|
|
|
|
|
