Infrastructure problems in Thames Valley causing disruption elsewhere - ongoing, since Oct 2014

[whole diary]

[JayMac]

This morning I had to return the car I borrowed over Christmas back to my sister in Taunton.

My train journey home to Templecombe was planned for connecting at Exeter into the first train up The Mule at 1325. Thus I was aiming for the 1245 from Taunton, 1C78 ex Paddington. That left Paddington over 70 minutes late, so I had to look at alternatives. The problems in the Thames Valley were compounded by the signalling failure between Bristol and Weston SM. Nothing would get me to Exeter in time for the 1325 to Templecombe.

Eventually left Taunton at 1335 on 2C73 Cardiff to Penzance service, which had been diverted via Westbury to get round the signalling problems in the Yatton area.

Arrived Exeter at 1404. Next SWR^» (South Western Railway - about) service to Templecombe at 1525.

As I type I'm on the second leg of my journey. Traction provided by a VW Caddy. The 'line' I'm travelling on? A30.

Taxi provided by GWR^▸ (Great Western Railway) from Exeter St Davids to Templecombe.

[JayMac]

Prescient decision to request the taxi rather than wait for the 1525 from Exeter to Templecombe. Line is now closed at Axminster following a person hit by a train.

[AMLAG]

Yet another, as yet unspecified, disruption to services between Salisbury and Exeter.
The line was only planned today to have services attempted to operate from Midday.
From  NRES^▸ (National Rail Enquiry Service) 1530 27/12/22:-
The emergency services are dealing with an incident between Exeter Central and Axminster.
 As a result, all lines are blocked and trains may be cancelled, delayed or revised. This is expected until 20:00.
South Western Railway Customer Advice:
Trains between Waterloo and Exeter will run between London Waterloo and Yeovil Junction

[IndustryInsider]

Due to a fatality at Axminster as BNM said.

I fear it’s likely there will be a higher number than average of such incidents this winter.

[JayMac]

Due to a fatality at Axminster as BNM said.

I fear it’s likely there will be a higher number than average of such incidents this winter.

For clarity. Person struck by train. No idea if fatal.

[grahame]

As with [too many / any] incident, things start a little confused.  First thoughts with all those closely involved - whatever the outcome, and then for those inconvenienced, but not so much.  The outcome will become clear in time, and little glitches in data will sort out.   SWR^» (South Western Railway - about) are telling us that trains will be running Yeovil Junction to Waterloo while this is ongoing - odd, because nothing diesel is headed east of Basingstoke today, and GWR^▸ (Great Western Railway) is telling us that their Axminster service is terminating short due to a different reason (staff shortage, which is probably the default excuse).

II is correct - it's likely we'll see a higher number of such incidents this winter - and I will remind readers of the I need Help link at the top of this page, and to seek help if you need it.  That is irrespective of whether today's incident is one in which the person hit by the train has made a decision to be hit, or not - to know that we need to wait to hear more, and it's utterly wrong to make any assumptions until we know.

[JayMac]

I should also say that my rail replacement taxi journey was subject to delay too. The A303 was stop start across the Blackdown Hills, along the Ilminster bypass (whoever decided that section being built as three lanes, with alternating use of the middle lane, needs committing), and from Podimore to Sparkford. So bad was that last section that Google Maps was suggesting the route through Podimore village and on to Queen Camel before rejoining the A303 at Hazelgrove roundabout was quicker.

[Timmer]

Whoever decided that section being built as three lanes, with alternating use of the middle lane, needs committing.

Can say the same about the A36 Warminster bypass.  Darn right dangerous in some places as drivers attempt to overtake in the short second lane sections.

[grahame]

For clarity. Person struck by train. No idea if fatal.

From Devon Live

One person has been seriously injured in an incident on a Devon train track. Devon and Cornwall Police confirmed details of the incident between Honiton and Crewkerne earlier this evening (Tuesday, December 27) after South Western Railway (SWR^» (South Western Railway - about)) announced there would be delays and cancellations.

The trainline remains partially blocked while emergency services attend the incident. SWR confirmed some delays, or train cancellations through the area for a few hours.

A spokesperson for Devon and Cornwall Police said: "Unfortunately... there is a casualty. The person sustained a serious injury but unknown if it's life threatening." Witnesses have said the air ambulance also attended.

[Worcester_Passenger]

Going back to yesterday at Paddington:

Nothing moved in or out of PAD^» (Paddington (London) - next trains) until quite recently as over-running engineering works blocked access into/out of North Pole depot

Looks like it moved from empty to full quite quickly. Empties arrived from North Pole at 10:35, 10:39, 10:42, 10:43, 10:46, 10:50, 10:52 and 10:56.  Passenger services arrived from Reading and beyond at 10:46, 10:51, 11:00 and 11:01 - the first of those having been held for a while at Slough

I experienced a second round of this disruption.  I arrived at Paddington at about 12:30 to catch the 12:50 back to Worcester. The concourse was very full, partly because the Underground entrance was closed for some reason. Even when that cleared:

12:04 to Penzance left at 12:41
12:07 to Newbury cancelled
12:20 to Oxford left at 12:53
12:28 Swansea on time
12:31 Bristol Temple Meads left at 12:33
12:33 Exeter St Davids cancelled
12:50 Worcester Foregate Street left at 13:35
13:02 Bristol Temple Meads left 13:14, conveying passengers for
13:04 Plymouth started from Reading and calling at the 12:33's intermediate stations

The 12:50 was on the boards as delayed due to "over-running engineering works", but announced on the train as being a "signal failure at the depot".

The 12:50 left 45 late but didn't recover any time.  I was expecting it not to go beyond Shrub Hill but (praise be) we did actually make it through to Foregate Street, where a lot of passengers were waiting for the return journey.

[nickswift99]

I was on the 0945 from Didcot. The night before the timetable showed an 8 car EMU^▸ (Electric Multiple Unit) that should have run fast from Reading. One VSTP later and it was a 2x3 car DMU^▸ (Diesel Multiple Unit) which also called as Twyford, Maidenhead and Slough (presumably because TFL^▸ (Transport for London) weren't running).

The train was full and standing leaving Reading and left passengers behind at both Maidenhead and Slough with long dwells resulting in a very late arrival.

[GBM]

Only just seen this on our wonderful journeycheck
Cancellations to services between Reading and London Paddington
Due to damage to the overhead electric wires earlier today between Reading and London Paddington fewer trains are able to run.
Train services running to and from these stations may be cancelled or delayed by up to 30 minutes. Disruption is expected until 11:30 11/01.

[GBM]

Also a signalling problem around Kintbury adding to the morning delays.

[GBM]

And a track inspection Reading - Gatwick!
Not a good day to be in Control

[TaplowGreen]

Cancellations to services between London Paddington and Reading

Due to a points failure between London Paddington and Reading fewer trains are able to run.

Train services running to and from these stations may be cancelled or delayed. Disruption is expected until the end of the day.