elementalpat
Member
- Joined
- 7 Nov 2011
- Messages
- 81
More delays on the ECML this Sunday, if the 'broken down train' is due to the same reason of coasting, all I can say is hmmmm!!!
The 1300 Kings Cross to Aberdeen hasn't even reached Newcastle yet - currently 4 hours late (ouch!).
Sounds as if the timetable is a bit of a house of cards. One slip, and the whole lot collapses.
If there is enough space, send all GC and HT that way as well, then turn everything else back at Peterborough.
Since eureka, there does seem to be a hell of a lot less wiggle room...
While all the above may well be true it had little bearing on todays events, from what ive been told a FCC failed on the only line in use at Hitchin that both south and north bound trains were using, no Hull Trains or GC services were operating south of Peterbrough anyway today. Just 3 EC services in each direction per hour and 1/2? FCC services per hour. Just bad luck.
Was it the same problem as last week with a 365 not playing ball?
Meanwhile, there must be some way to reinforce the headspans.
I thought the WCML was bad enough prior to the route modernisation project.
It sounds like the ECML is in much need of a similar project, including power supply upgrades and where ever possible, remodelling of junctions.
Sounds as if the timetable is a bit of a house of cards. One slip, and the whole lot collapses. I'm not entirely sure where the problem is, but if it's north of Cambridge Junction, they really ought to look at running two trains per hour via Cambridge in the paths of the usual fast shuttles. Obviously, those would have to be HSTs. If there is enough space, send all GC and HT that way as well, then turn everything else back at Peterborough. FCC could handle all the local traffic they could, with options to turn back at Stevenage, Huntingdon, Letchworth or wherever. Fill in with buses. It's better than trying to do the impossible.
Meanwhile, there must be some way to reinforce the headspans.
Was it the same problem as last week with a 365 not playing ball?
Of course it was. Nice to see FCC went some way to try and mitigate the problem by doing, err, nothing.
Apparently the problem stems from an AWS application. The 365s were built with two separate control loops for the AWS, one for AC and one for DC. When DC capability was removed, the two AWS loops were merged into one. Now when they drop the pan to coast, AWS automatically activates. The driver can override it, but somewhere the DC loop is still active behind all the gubbins, and this gives a brake application in the middle of the section.
FCC tried to get drivers to disable AWS just before entering the section, but it didn't seem to work. Thanks to someone on wnxx for the technical stuff.
[...I] get the feeling FCC may try a bit harder to do something about it before next weekend.
Yesterday's disruption on the East Coast Main Line was a complex incident with several contributing factors.
At approximately 1315hrs the (electric) 1215hrs @FirstCC London King's Cross to Peterborough service failed north of Hitchin in a section of single-line working, with the other lines closed for scheduled engineering works. Overhead lines were turned off in this section - owing to the engineering work on the adjacent lines - and as a result the service was "coasting" through. For reasons which are currently under investigation, an automatic warning system was activated on the train which brought it to a stop. As it was unable to continue further, a diesel loco was then scrambled to move it.
There were then further problems with coupling the rescue loco and then with releasing the brakes on the failed train. As a result the 81 passengers on this were evacuated and walked down the tracks where onward road transport was provided.
Both @firstcc and @eastcoastuk rescheduled their timetables in consultation with us to prevent stranded trains having to stand between stations for an extended time.
Our engineering work was then revised to open up an additional line to get services through while the stranded train was removed. It was removed and clear by 1717hrs and the single line working arrangements restored to original configuration.
We apologise to all those delayed or inconvenienced by this disruption.
I can't understand why this was allowed to happen again after what happened two weeks ago, unless some kind of "fix" had been applied to the 365s which they wrongly believed to have resolved the problem?
Presumably not all of the 365s are affected by this problem as the service that failed was by no means the first to coast through that section yesterday?
Also is it just my imagination, or are more trains than usual running slowly through the previously dead section today? I seem to recall making a similar observation after last time as well
There is nothing really wrong with the headspans, they don't seem to demonstrate any problems in other places they are used in the UK, it is simply that the line is very heavily loaded especially as it is largely a two track route compared to the other main lines.
As it is, the debacle that was the WCRM has forever poisoned the reputation of upgrades in this country, as now they will all be assumed to cost tens of billions of pounds and so on.
The ECML will have to struggle on until HS2 arrives and renders it a backwater along the lines of the West of England Main line.