Save the Train forum

Dedicate to campaigning to retain an appropriate "TransWilts" passenger train service ... Swindon - Chippenham - Melksham - Trowbridge - Westbury - Dilton Marsh - Warminster - Salisbury ... and to other services too

THIS FORUM IS NOW A READ-ONLY ARCHIVE. Please use our Coffeeshop Forum for new posts

link to main site
Save the Melksham Train

Welcome, Guest. Please login or register.
May 18, 2012, 04:22:07 AM

Login with username, password and session length
Search:     Advanced search
Recommended service - hourly, according to the GWRUS. Let's work towards that service and towards ensuring all services are used.
7889 Posts in 5009 Topics by 96838 Members
Latest Member: liuliul60
* Home Help Search Calendar Login Register
+  Save the Train
|-+  General Discussion
| |-+  Greater Western
| | |-+  Severn Beach Line Problem (19/01/2007)
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Print
Author Topic: Severn Beach Line Problem (19/01/2007)  (Read 1993 times)
Lee
Administrator
*****
Offline Offline

Posts: 3633


View Profile WWW
Severn Beach Line Problem (19/01/2007)
« on: January 19, 2007, 06:26:52 PM »

The Severn Beach line train , due at Sea Mills at 1653 was stopped at the tunnel signal at Clifton Down for over an hour , and passengers were detrained through the rear of the train back onto the Clifton Down platform.
Logged
Lee
Administrator
*****
Offline Offline

Posts: 3633


View Profile WWW
Re: Severn Beach Line Problem (19/01/2007)
« Reply #1 on: January 20, 2007, 01:44:23 PM »

More on this from FOSBR :

It appears that the incident was due to the presence of a broken down train somewhere beyond Clifton Down, and possibly another train sent out to recover it. It is therefore entirely the responsiblity of First Great Western (FGW) .

Despite this situation being already known, it appears that FGW chose to allow passengers to board at Clifton Down, and then moved the train forward the short distance to the red signal, where it stopped, effectively confining them just beyond Clifton Down for nearly an hour, which could have been predicted before leaving the platform.

It also appears that it was only possible to detrain because the service was unusually made up of three coaches, leaving the last door still on the level part of the platform. Apparently FGW have no procedure for setting back in these circumstances, and without the fortunate accident of an unusually long train, it appears likely that the passengers would still be confined.

Two replacement buses arrived about 15 min after the passengers were disembarked, which is hardly prompt given that the problems must have been known probably about two hours by then.

The whole affair, arising first from reliability problems entirely within FGW responsibility, appears to have been grossly mismanaged, and as slowly as possible.
Logged
jonshaw1uk
Newbie
*
Offline Offline

Posts: 3


View Profile
Re: Severn Beach Line Problem (19/01/2007)
« Reply #2 on: January 22, 2007, 10:22:14 AM »

I was on that train - we were told at Temple Meads that it would only go as far as Redland before returning to Temple Meads. Once on the train, no announcements were made and no staff were on the train to tell people getting on about the problem. I got off at Redland, assuming that everybody else would as well - I was quite surprised when lots of people stayed on and the train carried on towards Clifton Down. I'm very pleased I got off now!
Logged
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Save the Train | Powered by SMF 1.0.5.
© 2001-2005, Lewis Media. All Rights Reserved.
Valid XHTML 1.0! Valid CSS!
Page created in 0.053 seconds with 19 queries.