Show Posts
|
Pages: [1] 2 3 ... 30
|
1
|
Journey by Journey / Bristol (WECA) Commuters / Re: Four track for Filton Bank - ongoing discussion
|
on: November 22, 2018, 10:05:16
|
When you pointed out previously that the WTT▸ was still showing paths and platforms for the old track arrangement, I didn't twig that would include ones that are now physically impossible. But they are all still there - most northbound trains for south Wales are shown using P3, and none using P4. OK, one can understand that if it makes sense not to update the WTT (leaving aside why that might be). But what flummoxes me a bit is that RTT» and OTT▸ both show yesterday's 2U12 as actually using P3 (i.e. in bold or as "as booked").
At present whenever a train uses Platform 2 to go towards Cardiff, the signals it steps through are the same as what would be stepped through for Platform 3 previously. This results in incorrect reporting that the train is using Platform 3. It looks like Network Rail need to update their data (SMART) and the background data just needs a slight tweak on RTT to remove this incorrect platform report.
|
|
|
2
|
All across the Great Western territory / Fare's Fair / Re: Default connection time?
|
on: October 09, 2018, 11:11:12
|
There are 6 minutes of pathing allowance on this train prior to arrival in Bristol, 5 of which are between Freshford and Bath Spa. It had a three minute station stop at Bradford-on-Avon and left there late as a result, yet left Bath Spa early according to the working timetable (see attachment to this post). Unless it was blocking something else between Westbury and Bradford-on-Avon / Bradford Junction, it could have waited an extra minute or two.
That three minute stop at Bradford-on-Avon was most likely nothing of the sort, almost definitely in this case as there is no way the train could of left Bradford nearly 2 minutes late and only left Avoncliff 30 seconds late. There is no way to identify an accurate departure time from Bradford-upon-Avon when a train stops at Avoncliff as there is no means of a train reporting again until the train has arrived and departed Avoncliff. The reported departure time at Bradford-upon-Avon is based on if the train had not stopped at Avoncliff, obviously with a stop at Avoncliff the train will take longer to get to the next reporting point and therefore the dwell at Bradford will look longer.
|
|
|
3
|
All across the Great Western territory / Across the West / Re: 68 mins at Bath Spa station yesterday.........
|
on: August 30, 2018, 12:17:39
|
Most stations will operate like that because the announcements are automated and triggered by the train passing certain points on the network.
The announcements are automated and programmed the week or a few days before. The delayed announcements are automatic by the system unless altered by Swindon control. The announcements on GWR▸ have been largely the same since the new system was installed, the majority of them are timed based on the trains expected arrival time. This mean that if this time is wrong then the announcements are played at the wrong time. Announcements regarding train stops and formation are typically 3 minutes before expected arrival time, 1.5 minutes (for the slightly shorter announcement), and then on triggering the arrival report. The latter being the only one that is actually triggered by any train movement, the former 2 could play even if the train is stood at a red signal and actually being delayed. Announcements regarding delays are influenced by a range of factors including, but not limited to, how late the train currently is and its current expected arrival time. At one point 3 apologies were announced one after the other - with no break in between..........for a 13 min delay, then a 15 min delay, then a 13 min delay again - all for the same train !!!! This typically occurs when the train is passing through a station on its route, the train running reporting system only understanding trains arriving and departing. Therefore when the train reports as it passes a station an arrival report is made, this pushes the delay up as this is based on the train coming to a stand. Once the train has passed said station a departure report is made and this, in simple terms, cancels out the effect of the arrival report. The train then returns to its previous lateness or what the system has decided based on the time reported at that location. When you combine this with that at some station where a train isn't timed the system still has an expected passing time and this time isn't always accurate, so results in inaccuracies in the calculation of the trains delay. When a train is on time you typically won't notice the impact of this, this is because often this will be absorbed by the dwell time at the relevant location or because the system will not announce short delays.
|
|
|
5
|
Sideshoots - associated subjects / Campaigns for new and improved services / Re: Ebbw Vale direct service to (or via?) Newport?
|
on: June 06, 2018, 15:29:09
|
There was a need for double-tracking a further section to increase line capacity but this work has been completed. The issue is at least partly lack of rolling stock.
If you are referring to the doubling North of Crosskeys to the former Aberbeeg Junction (Just north of Llanhilleth), then this work has not been completed yet. Last I heard it had been paused, although there was never any official source for this. As far as I am aware the aim is to deliver the additional services between Newport and Ebbw Vale by May 2021, so the passing loop will need to be available for then if this is the case.
|
|
|
6
|
All across the Great Western territory / Across the West / Re: Hot Rails
|
on: May 08, 2018, 11:17:41
|
I recall it being utterly standard practise for newly replaced tracks to be bedded in with an initial speed restriction, but (now that I thick about it) I've not come across that recently. Perhaps this is just the older standard being applied with the higher temperatures being something of a red herring - or perhaps making for problems yesterday so the tracks haven't yet been fully stressed? Fair enough - if that's the case, initial report was a bit confusing as it suggested today's temperatures caused the problem.
This is a planned TSR▸ following track renewals over the weekend. 50mph in both directions between 19m4ch and 19m35ch, on the main lines. Update: Just done some digging, turns out the speed has actually been reduced to 20mph ESR▸ .
|
|
|
7
|
Journey by Journey / Cross Country services / Re: Cross Country Franchise
|
on: April 17, 2018, 13:51:38
|
It does also mean one of the units will have no Coach D with the luggage and bike spaces.
This isn't the case, a coach was swapped with Virgin. This was a coach with a shop from the Virgin set which previously had two shops. This coach was then converted to have the luggage and bike spaces as on the rest of the XC▸ voyager fleet. The additional vehicles entered service a few months ago, the result being that 1V46 0640 York-Plymouth and 1S53 1325 Plymouth-Edinburgh (As far as Newcastle) are now double voyager sets, when they are not an HST▸ . When they are an HST other services are strengthened instead.
|
|
|
8
|
Journey by Journey / London to South Wales / Re: Skipping Stops
|
on: February 09, 2018, 16:43:35
|
Any missed stops or early terminations will soon be classed as 'cancellations' for the new performance figure percentage metrics. This is what applies now, under the Cancellation and significant lateness metric (CaSL). A train is counted as being a CaSL failure if: It is cancelled at origin. It is cancelled en route. The originating station is changed. It fails to make a scheduled stop at a station. It is significantly late (ie it arrives at its terminating station 30 minutes or more late). Any train which is a CaSL failure also fails PPM‡. So therefore even if a train which has missed stops arrives at its destination on time, it is still a PPM failure.
|
|
|
9
|
All across the Great Western territory / Across the West / Re: Thames Valley infrastructure problems causing disruption elsewhere - 2018
|
on: January 18, 2018, 13:21:20
|
Due to a fault with the signalling system between Didcot Parkway and Reading some Didcot Parkway lines are blocked. Impact: Train services running to and from these stations may be delayed. Disruption is expected until 13:00 18/01.
Greetings from 1C12 at Goring and Streatley Fast lines westbound closed ... everyone on the slow lines Err - sorry - main lines closed ... everyone on the relief Said to be a "broken rail" to us on the train. Presumably the track is strong enough to take the new trains? Defect in a set of points on the Down Main at Didcot East. The set of points have in the last 15 minutes been authorised for train movements when in the reverse position, this means everything will have to cross over to the Relief lines if using the Down Main.
|
|
|
10
|
All across the Great Western territory / Across the West / Re: Thames Valley infrastructure problems causing disruption elsewhere - 2018
|
on: January 18, 2018, 11:29:08
|
.....here we go again...
Cancellations to services between Southall and Slough
Due to a speed restriction over defective track between Southall and Slough fewer trains are able to run on some lines towards Slough. Train services running through these stations may be cancelled or delayed by up to 20 minutes. Disruption is expected until 14:30 18/01. Further Information Trains from London Paddington/Southall towards Slough/Reading, are unable to call at Hayes, West Drayton, Iver and Langley.
5mph ESR▸ due to a broken insulated rail joint. Sounds like they are hoping to replace it this afternoon.
|
|
|
12
|
All across the Great Western territory / Across the West / Re: Thames Valley infrastructure problems causing disruption elsewhere - 2018
|
on: January 09, 2018, 16:19:41
|
And that starts with why isn't 1P10 in P10/11 anyway? There's a gap for it to do that.
Whilst it may look like there is a gap at Reading, there isn't a sufficient gap at Didcot for it to get across from the Relief Lines onto the Main Lines. There is freight paths through Platform 3 shortly after its departure, so it isn't possible to hold the 387 in the platform that bit longer to go behind the Bristol-Paddington. I could see this train perhaps starting from Swindon when the wires eventually extend that far, it could then run just behind the Bristol-Paddington service from Swindon and use the Main Lines throughout. When the 110mph running times are used it could be quite a fast service from Didcot.
|
|
|
13
|
Journey by Journey / Cross Country services / Re: Points failure - Didcot 30/12/17
|
on: December 31, 2017, 12:28:24
|
As does the XC▸ service. It doesn't use the west curve, at least, noton the nights that I have been on it....
It is booked to use the West Curve, and does use it most nights if it is on-time. There is a situation where it can't use the West Curve and that is what happened with this train. If the train reverses at Foxhall Junction on the Down Main, the West Curve is not accessible, therefore the train has to proceed into Didcot via the Didcot Relief Line and reverse again there. The train has to reverse on the Up Main in order to access the West Curve, obviously this causes disruption to services on the Up Main in unplanned scenarios like this. Similarly the 2145 Reading-Birmingham might get altered to reverse on the Down Main if there is disruption to services on the Up Main. The points failure was at Didcot East Junction on the points which allow trains to travel between the Down Relief and the Up Relief, there was no detection at all at both ends. This resulted in no route between Didcot station and the Relief Lines and no access to the Down Avoiding Line.
|
|
|
14
|
Journey by Journey / London to the West / Re: Earlier Service to Cornwall - Jan 2018
|
on: December 08, 2017, 11:00:03
|
09:33 public, so the train is scheduled to arrive 4 minutes late everyday, that's just silly
Not the only train in that direction that is like this. To a lesser extent 1003/1203 from Paddington are both booked into Plymouth a minute earlier to make the headline journey time, and have been for years. In more recent timetable changes Exeter also joined the party on these trains, 2 minutes earlier on the 1003 and 1 minute earlier on the 1203 in January. Although arguably, in the case of 1003/1203 from Paddington, if the train is given a clear run and there are no temporary or emergency speed restrictions, the public times are perfectly achievable because they are the WTT▸ with the engineering allowances removed. In the case of the 0633 from Paddington the running time in the passenger timetable from Exeter to Plymouth is 51 minutes, which arguable is achievable - i've been on trains that have done the run in 50 minutes. However in this case the working timetable running time is 53½ minutes, including one minute engineering allowance - so 52½ minutes without the allowance. So whilst it might be possible to do the public timetable running time under the right conditions, it certainly won't be possible all the time.
|
|
|
|