Train Graphic
Great Western Passengers' Forum
GWR advice during Coronavirus
Coffee Shop during Coronavirus
Great Western Coffee Shop - [home] and [about]
Read about the forum [here].
Register [here] - it's free.
What do I gain from registering? [here]
 15/07/2020 - Harness social media - ONLINE
22/07/2020 - Melksham Rail User Group CANX
16/09/2020 - Melksham Rail User Group
17/09/2020 - National Rail Awards
Random Image
Train Running Polls Acronyms/Abbreviations Station Comparator Rail news GWR co. site Site Style 1 2 3 4
Next departures • Bristol Temple MeadsBath SpaChippenhamSwindonDidcot ParkwayReadingLondon PaddingtonMelksham
Exeter St DavidsTauntonWestburyTrowbridgeBristol ParkwayCardiff CentralOxfordCheltenham SpaBirmingham New Street
July 09, 2020, 02:40:55 am *
Welcome, Guest. Please login or register.

Login with username, password and session length
Forgotten your username or password? - get a reminder
Most liked recent subjects
[238] Getting a grip on GRIP.
[93] Devizes 52-year wait for train station could end
[91] Four new stations...
[50] Boris Johnson: TfL driverless trains 'should be funding condit...
[28] Low bridge? no problem
[25] Is it OK to snack on a train?
News: A forum for passengers ... with input from rail professionals welcomed too
 
   Home   Help Search Calendar Login Register  
Pages: [1]
  Print  
Author Topic: Disruption between Bristol and Weston super Mare  (Read 1560 times)
Timmer
Global Moderator
Hero Member
*****
Posts: 5498


View Profile
« on: January 11, 2020, 08:40:06 am »

A ‘late running freight train’ is causing all sorts of issues between Bristol and Weston super Mare and has been since first thing. Surely there’s more to it than just running late. Broken down perhaps or a sensitive cargo (nuclear)?

Quote
Due to a late running freight train between Bristol Temple Meads and Weston-Super-Mare the line towards Weston-super-Mare is blocked.
Train services running through these stations may be cancelled, delayed by up to 60 minutes or revised. Disruption is expected until 10:30 11/01.
Logged
bobm
Administrator
Hero Member
*****
Posts: 8190



View Profile
« Reply #1 on: January 11, 2020, 10:26:16 am »

It was a freight from Felixstowe which was stuck on the main line for over three hours waiting to be accepted into Bristol Freightliner yard.
Logged
Timmer
Global Moderator
Hero Member
*****
Posts: 5498


View Profile
« Reply #2 on: January 11, 2020, 12:06:29 pm »

It was a freight from Felixstowe which was stuck on the main line for over three hours waiting to be accepted into Bristol Freightliner yard.
Will be interesting to know who pays for the delays and cancellations that it caused.
Logged
GBM
Transport Scholar
Hero Member
******
Posts: 574


View Profile
« Reply #3 on: January 11, 2020, 03:12:52 pm »

It was a freight from Felixstowe which was stuck on the main line for over three hours waiting to be accepted into Bristol Freightliner yard.
May you please clarify "waiting to be accepted..."  Surely provided the signal(s) were good to go, the freight could just roll into the yard.  If the signals were against it and it had to wait (over three hours - really?) purely because of the signals, then it's a Network Rail fault.
Logged

Personal opinion only.  Writings not representative of any union, collective, management or employer. (Think that absolves me...........)
stuving
Transport Scholar
Hero Member
******
Posts: 4849


View Profile
« Reply #4 on: January 11, 2020, 03:13:17 pm »

It was a freight from Felixstowe which was stuck on the main line for over three hours waiting to be accepted into Bristol Freightliner yard.
Will be interesting to know who pays for the delays and cancellations that it caused.

This incident was initially attributed as "waiting for terminal/yard acceptance (AA)", applying to all the delayed and cancelled passenger services.

In the DAPR, the list of codes has AA (Waiting Terminal/Yard acceptance) under freight terminal operating company causes". In section 4.2, explaining such incidents (Acceptance into Freight Terminals/Yards) in more detail, it has:
Quote
Circumstances: Incident within a yard/terminal, off Network Rail operated infrastructure, causing trains to be delayed entering into either that yard/terminal or an adjacent yard/terminal sharing the same connection to the Network.
Delay Code:  Appropriate A*, F* or M* Code
Incident Attribution:  Freight Operator(s) - separate Incident for each Operator involved (A##*)

Circumstances: Freight Operator of train waiting outside terminal/yard does not provide information on incident in terminal/yard
Delay Code:  AA
Incident Attribution:  Operator of train concerned
(I presume that by Freight Operator is means terminal operator.)

In any case, the contracts linking the train and terminal operators will cover who ultimately pays for it.
Logged
Celestial
Transport Scholar
Hero Member
******
Posts: 595


View Profile
« Reply #5 on: January 11, 2020, 03:17:24 pm »

I thought I read some months ago that the Bristol Freighliner yard had closed, and it's traffic rerouted to Pengam, which was more viable since the toll was removed on the bridge.
Logged
stuving
Transport Scholar
Hero Member
******
Posts: 4849


View Profile
« Reply #6 on: January 11, 2020, 03:20:32 pm »

It was a freight from Felixstowe which was stuck on the main line for over three hours waiting to be accepted into Bristol Freightliner yard.
May you please clarify "waiting to be accepted..."  Surely provided the signal(s) were good to go, the freight could just roll into the yard.  If the signals were against it and it had to wait (over three hours - really?) purely because of the signals, then it's a Network Rail fault.

It means going off NR's network onto someone else's. That move can only happen (and only be signalled) after it is accepted by the operator of the other "network" - even if it's just a bit of track.
Logged
stuving
Transport Scholar
Hero Member
******
Posts: 4849


View Profile
« Reply #7 on: January 11, 2020, 03:25:32 pm »

I thought I read some months ago that the Bristol Freighliner yard had closed, and it's traffic rerouted to Pengam, which was more viable since the toll was removed on the bridge.

There were several movements last week - not every day, but at weekends in particular, and including to/from Felixstowe.
Logged
Do you have something you would like to add to this thread, or would you like to raise a new question at the Coffee Shop? Please [register] (it is free) if you have not done so before, or login (at the top of this page) if you already have an account - we would love to read what you have to say!

You can find out more about how this forum works [here] - that will link you to a copy of the forum agreement that you can read before you join, and tell you very much more about how we operate. We are an independent forum, provided and run by customers of Great Western Railway, for customers of Great Western Railway and we welcome railway professionals as members too, in either a personal or official capacity. Views expressed in posts are not necessarily the views of the operators of the forum.

As well as posting messages onto existing threads, and starting new subjects, members can communicate with each other through personal messages if they wish. And once members have made a certain number of posts, they will automatically be admitted to the "frequent posters club", where subjects not-for-public-domain are discussed; anything from the occasional rant to meetups we may be having ...

 
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.2 | SMF © 2006-2007, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
This forum is provided by a customer of Great Western Railway (formerly First Great Western), and the views expressed are those of the individual posters concerned. Visit www.gwr.com for the official Great Western Railway website. Please contact the administrators of this site if you feel that the content provided by one of our posters contravenes our posting rules (email link). Forum hosted by Well House Consultants

Jump to top of pageJump to Forum Home Page