802013 dumped at Newbury Yard

[317362]

Realtime Trains | 1K71 0510 Bristol Temple Meads to Newbury | 03/03/2023

Real-time train running information for 1K71 0510 departure from Bristol Temple Meads to Newbury on 03/03/2023. From Realtime Trains, an independent source of train running info for Great Britain.

www.realtimetrains.co.uk

0510 Bristol-Paddington via Hungerford terminated at Newbury. 2 hrs from Pewsey to Newbury. Wasn't fun to wait for, especially on day 1 of reopened line and with the Bedwyn shuttles also cancelled.

Issue with brakes/wheels/axles depending who you spoke to, is now sat in Newbury Yard looking a bit incongruous. Travelled in service but limited to 20 (was more like 12) today. 'lost time' covers it.

== Doublepost prevention - post automatically merged: 3 Mar 2023 ==

Issue not with train but with the hot axlebox detectors

 

[VP185]

Triggered the lineside GOTCHA system. This picks up issues like vehicle wheel-set defects such as wheel flats and axle loads and sends an alarm to the signaller who in turn, brings the train to a stand at a signal and informs the driver of this issue.

The set was then restricted to 10mph and will be moved to depot overnight.

 

[FGW_DID]

Due to various possessions, 802013 has been put onto Reading TCD to await a path back to North Pole whenever that may be!!

Moved as 8Z10 Newbury - Reading TCD.

 

[Benjwri]

Bit late but for anyone interested 802013 ran from Reading TCD to North Pole on the 7th, as 5Z71, appears to have been able to keep up to 387 pathing, so presumably allowed to run at line speed. Returned to passenger service on the 9th

 

[fgwrich]

Triggered the lineside GOTCHA system. This picks up issues like vehicle wheel-set defects such as wheel flats and axle loads and sends an alarm to the signaller who in turn, brings the train to a stand at a signal and informs the driver of this issue.

The set was then restricted to 10mph and will be moved to depot overnight.

On a slightly related note, I was passing OOC / North Pole on a 345 last week and noticed a Siemens RailBAM around there too. I thought they were largely concentrated on routes with Siemens stock eg SWR (one near Swaythling) and in TPE land.

 

[Benjwri]

Also looking further into 802013, it appears to have run to Great Malvern and back, but then gone onto 1C36, which was departed late, however picked up a staggering 70 minute delay at Bristol, where 802013 was meant to uncouple. The ECS move for 802013 was cancelled, and it hasn't been seen since, with no possible moves out of Bristol. Does anyone know what happened and where it is?

 

[Jrocks]

1C36 last night was delayed at Bristol with a Break fault where 802013 was uncoupled and sent to SGI.

 

[Crossover]

Bit late but for anyone interested 802013 ran from Reading TCD to North Pole on the 7th, as 5Z71, appears to have been able to keep up to 387 pathing, so presumably allowed to run at line speed. Returned to passenger service on the 9th

I would presume it is an amended path due to a limited top speed - Reading to Paddington was scheduled as around 1 hr 40 mins, whereas a pair of 387's were booked just over 50 minutes including a number of station calls

 

[Benjwri]

1C36 last night was delayed at Bristol with a Break fault where 802013 was uncoupled and sent to SGI.

Same fault as the original incident or another? Odd that it took so long to dump it, considering it was scheduled to uncouple at Bristol anyways

I would presume it is an amended path due to a limited top speed - Reading to Paddington was scheduled as around 1 hr 40 mins, whereas a pair of 387's were booked just over 50 minutes including a number of station calls

Looks about right to me, there's a lot of pathing allowance which it didn't seem to need, and it sat at Old Oak for 20 minutes.

 

[Jrocks]

Same fault as the original incident or another? Odd that it took so long to dump it, considering it was scheduled to uncouple at Bristol anyways

A new fault as far as I'm aware - completely seperate to the reason it was delayed at Pad anyway. 1C36 doesn't usually uncouple at Bristol anymore, was scheduled as a 10 car all the way to Plymouth. 2U06 this morning was started at Taunton vice Exeter and with a 2+4 due to the failure in the early hours of the morning.

 

[Benjwri]

A new fault as far as I'm aware - completely seperate to the reason it was delayed at Pad anyway. 1C36 doesn't usually uncouple at Bristol anymore, was scheduled as a 10 car all the way to Plymouth. 2U06 this morning was started at Taunton vice Exeter and with a 2+4 due to the failure in the early hours of the morning.

By original fault I meant the one which caused the original incident for this thread where a GOTCHA system was triggered. I don't believe it was scheduled as a 10 car, on the 9th it was an altered WTT schedule, with a divides flag at BTM.

 

[Nippy]

On a slightly related note, I was passing OOC / North Pole on a 345 last week and noticed a Siemens RailBAM around there too. I thought they were largely concentrated on routes with Siemens stock eg SWR (one near Swaythling) and in TPE land.

I am pretty sure that was there for when the 332s were in use on the HEx trains.

 

[Jrocks]

By original fault I meant the one which caused the original incident for this thread where a GOTCHA system was triggered.

I would assume that it's a different fault to the one that GOTCHA caught. I would be very supprised if Hitachi hadn't checked the unit over thoroughly to ensure that the same fault wouldn't (or shouldn't) occur again in the near future. Especially considering this unit had managed a few journeys earlier in the day.

I don't believe it was scheduled as a 10 car, on the 9th it was an altered WTT schedule, with a divides flag at BTM.

Schedules arent always correct, it always used to split at Bristol but since the new class 80x diagrams on PNZ CDF, they have been changing them on a adhoc basis. Look at the 7th for example - it was altered in the train planning schedule for the train to divide at Bristol when infact it gained coaches.

 

[stuving]

I am pretty sure that was there for when the 332s were in use on the HEx trains.

This is from Rail Engineer in 2019:

Whilst the majority of systems have been installed overseas, the first UK application was a limited trial in 2007 on Southern at Three Bridges, targeting the Class 377 fleet. Although successful, the trial was not expanded.

In 2009, Siemens installed the first RailBAM system in the UK and the first globally to target only passenger stock. This was on the South West Trains network and monitored Class 444 and 450 units with the trackside unit installed at Swaythling, between Southampton and Eastleigh. The system captures data for the whole Siemens fleet as well as other trains using the route.

A second trackside unit was later installed at Mortlake with the fitting of tags to more of the SWT fleets, thus enabling all units on what is now South Western Railway to be monitored.

Noting the results, First Great Western installed a trackside unit at Kensal Green, near to North Pole depot, and began equipping its HST fleet with tags. This was then expanded to take in other classes of FGW trains.

But has it been extended to 80xs? Presumably it would be for Hitachi/Angel, as maintainers, to sign up and fit the specific RFID tags. Somehow that doesn't sound like something they'd do.

 

[Nippy]

Thanks for the info, I can remember it being there when I went out with the patrolling team, but we were not told much about it in the box.