|
Chris from Nailsea
|
 |
« Reply #15 on: May 10, 2011, 17:38:31 » |
|
Sounds bad
It was indeed a bad day on the railways, animationmilo - but welcome to the Coffee Shop forum, anyway!  |
|
|
|
|
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.
|
|
|
|
6 OF 2 redundant adjunct of unimatrix 01
|
|
« Reply #16 on: May 10, 2011, 17:46:55 » |
|
talking of displacement 142064 plus 143619 on 0740 Paignton to BTM▸ replacing hst..... is/was this service busy?
|
|
|
|
|
Logged
|
|
|
|
|
bobm
|
|
« Reply #17 on: May 10, 2011, 17:51:33 » |
|
Don't know but it was 11 late by Bristol and was terminated.
|
|
|
|
|
Logged
|
|
|
|
|
ChrisB
|
|
« Reply #18 on: May 10, 2011, 19:40:03 » |
|
talking of displacement 142064 plus 143619 on 0740 Paignton to BTM▸ replacing hst..... is/was this service busy? That would be BRI» .....? Don't know but it was 11 late by Bristol and was terminated. Which is where it was due to finish its journey..... |
|
|
|
|
Logged
|
|
|
|
|
Bob_Blakey
|
|
« Reply #19 on: May 10, 2011, 19:59:54 » |
|
The 0740 Paignton - 1138 Paddington via Brizzle is generally rammed between Torbay & Exeter, largely with a mix of incoming Exeter College students and commuters.
It also ran as a 2 x 2 DMU▸ as far as BRI» a couple of weeks back when the ECS▸ HST▸ from Laira failed before departure.
|
|
|
|
|
Logged
|
|
|
|
|
bobm
|
|
« Reply #20 on: May 10, 2011, 20:43:30 » |
|
talking of displacement 142064 plus 143619 on 0740 Paignton to BTM▸ replacing hst..... is/was this service busy? That would be BRI» .....? Don't know but it was 11 late by Bristol and was terminated. Which is where it was due to finish its journey..... Not according to FGW▸ website an HST▸ was due to take up the reins from Temple Meads but about 10 minutes after the units arrived from Paignton the onward service was cancelled. |
|
|
|
|
Logged
|
|
|
|
|
Louis94
|
|
« Reply #21 on: May 10, 2011, 22:54:40 » |
|
Service ran as 1Z12, left Bristol about 10 minutes late, however it was reported No Log until just after Swindon.
|
|
|
|
|
Logged
|
|
|
|
|
bobm
|
|
« Reply #22 on: June 13, 2011, 13:54:46 » |
|
From the BBC» Seems the delays in the Reading area on 9th May were the worst across the country last month. Cows on the line among top delays
Cows on the line led to 15 train cancellations on Britain's rail network in May, Network Rail has said.
The incident on the West Coast line between Nuneaton and Rugby came fifth in a new listing of top delays from the company behind the rail infrastructure.
Signal failure on the Western route near Reading, which saw 139 cancellations, was top, followed by power failure and theft of cable.
On average, 93.7% of trains ran on time in May, matching the figure for 2010.
This is the first time the list of the top five incidents the company is responsible for in a month has been published, Network Rail said.
Power failure caused by overhead wires resulted in 101 train cancellations on the East coast line between Stoke and Tallington junction, the list showed.
There were a total of 95 cancellations caused by two incidents of cable theft - on the East Coast line near Scunthorpe and on the Anglia route between Chelmsford and Witham.
Above average
The incident involving cows on the line took place on 27 May.
It comes after cows got on to the line between Swindon and Didcot in January, causing delays on the main line to Paddington when one of them was hit by a train.
Among train companies, only the East Coast company (85.9%) and West Coast operator Virgin Trains (89.6%) had punctuality of less than 90% in May.
The best-performing company last month was the London to Tilbury and Southend operator c2c which ran 97.5% of trains on time.
Merseyrail, London Overground, Arriva Trains Wales and First TransPennine Express all had above average punctuality in the month. |
|
|
|
|
Logged
|
|
|
|
|
hornbeam
|
|
« Reply #23 on: June 14, 2011, 12:40:15 » |
|
I know some issues are down to cable theft, but is the signalling getting less reliable? Also is the 1960^s signalling being replaced? I notice a few new signal heads popping up but nothing like a major replacement. Also, when the GW▸ mainline was done most of the cables were put in sand filled trenches. So a cable fault means new cables above ground, is this correct?
|
|
|
|
|
Logged
|
|
|
|
|
ChrisB
|
|
« Reply #24 on: June 14, 2011, 12:43:32 » |
|
Why wouldn't they just replace the cables in the trenches?
|
|
|
|
|
Logged
|
|
|
|
|
hornbeam
|
|
« Reply #25 on: June 14, 2011, 17:00:19 » |
|
From what I remember when I did work experience its because they were so deep in the ground, and the worry is of moving other cables alongside could damage them in the process. The advantage was that rats couldn^t get to them and of course now cable thefts, but makes repairs much harder.
|
|
|
|
|
Logged
|
|
|
|
|
Electric train
|
|
« Reply #26 on: June 14, 2011, 18:32:54 » |
|
I know some issues are down to cable theft, but is the signalling getting less reliable? Also is the 1960^s signalling being replaced? I notice a few new signal heads popping up but nothing like a major replacement. Also, when the GW▸ mainline was done most of the cables were put in sand filled trenches. So a cable fault means new cables above ground, is this correct?
Some cable were buried in the ground and yes they suffered from damage and are difficult to fault find and repair, also the civil engineers are not keen of trenches along side the railway destabilises embankments and cuttings etc. The GW Mainline is having substantial work done, Crossrail, Reading rebuild and electrification there are also a number of resignalling / relocking / renewals programs in the pipeline |
|
|
|
|
Logged
|
Starship just experienced what we call a rapid unscheduled disassembly, or a RUD, during ascent,”
|
|
|
|
