One passenger complained on social media: "How hard is it to move a swan?"
"Has nobody been on the shooing course. I cannot believe you closed the entire Elizabeth line for a swan on the tracks," they added.
Passengers reported being held on trains — which do not have toilets — for up to an hour due to the swan.
I think it was Westbourne park/Westbound running tunnel which is why it only effected the Elizabeth linePresumably the swan incident was west pf Paddington on the GWML, before Acton ML and therefore a Network Rail problem?
Were GWR services also affected?
Why would a blockage west of Paddington prevent Shenfield/Abbey Wood-Paddington services running - something half the service does anyway.
Media reports (BBC etc) were very vague about where the problem was, and any alternative routes to take.
Just "swan on the tracks", a bit like the "wrong kind of snow"...
![]()
Elizabeth line suspended due to swan on the track
Passengers say they have been held on trains for up to an hour because of the swan at Paddington.www.bbc.co.uk
It blocked off the exit around Westbourne Park heading to Acton which is RFLI owned. This caused tailbacks shortly as all the westbound trains Queued up for longer than they should have instead of being emptied out and turned back imo to east bound stations to at least do a limited Paddington to Shenfield/ Abbey Wood service which didn't happen till line reopening.Presumably the swan incident was west pf Paddington on the GWML, before Acton ML and therefore a Network Rail problem?
Were GWR services also affected?
Why would a blockage west of Paddington prevent Shenfield/Abbey Wood-Paddington services running - something half the service does anyway.
Media reports (BBC etc) were very vague about where the problem was, and any alternative routes to take.
Just "swan on the tracks", a bit like the "wrong kind of snow"...
![]()
Elizabeth line suspended due to swan on the track
Passengers say they have been held on trains for up to an hour because of the swan at Paddington.www.bbc.co.uk
Presumably the swan incident was west pf Paddington on the GWML, before Acton ML and therefore a Network Rail problem?
Were GWR services also affected?
Why would a blockage west of Paddington prevent Shenfield/Abbey Wood-Paddington services running - something half the service does anyway.
Media reports (BBC etc) were very vague about where the problem was, and any alternative routes to take.
Just "swan on the tracks", a bit like the "wrong kind of snow"...
![]()
Elizabeth line suspended due to swan on the track
Passengers say they have been held on trains for up to an hour because of the swan at Paddington.www.bbc.co.uk
It blocked off the exit around Westbourne Park heading to Acton which is RFLI owned. This caused tailbacks shortly as all the westbound trains Queued up for longer than they should have instead of being emptied out and turned back imo to east bound stations to at least do a limited Paddington to Shenfield/ Abbey Wood service which didn't happen till line reopening.
Trains were stacked on the Westbound line, so Shenfield services start from Liverpool Street and wouldn't have been able to reach Paddington. There's only really one good place to turnback Eastbound and that's Tottenham Court Road. If that driver was due to finish at say Maidenhead, it might not have been feasible. Plenty of alternative routes were advertised, but the BBC story is quite a short one.
I remember being at Crewe in the 80s when the southbound WCML was brought to a halt by a train being disabled after hitting a swan between Hartford and Winsford. A 47 had to be dispatched to haul it to Crewe, where it was terminated.As an aside, I wonder how a swan on the tracks would've been dealt with if this were 1923 instead of 2023? I rather suspect it wouldn't have been by letting the entire service go to pot for practically the entire rest of the day.
I remember being at Crewe in the 80s when the southbound WCML was brought to a halt by a train being disabled after hitting a swan between Hartford and Winsford. A 47 had to be dispatched to haul it to Crewe, where it was terminated.
Rather pre-1923 I realise, but given that one I.K. Brunel dealt with the problem of working in the overly small gaps between double hulls in steam ships by sending sufficiently small boys in there*, we can guess that his swan solution might have been more... pragmatic/industrial.As an aside, I wonder how a swan on the tracks would've been dealt with if this were 1923 instead of 2023? I rather suspect it wouldn't have been by letting the entire service go to pot for practically the entire rest of the day.
I realise we're speculating here, but say that was the scenario and the driver was due to finish at Maidenhead. Wouldn't it likely still be better to turn the train at Tottenham Court Road, leave it in the Eastbound platform, and then let the driver use Underground/GWR to get back to Maidenhead: Since if you did that, presumably there will be quite a few other drivers in the vicinity, some of whom would be able to take over that train as an Eastbound service? Better surely than losing the service completely because every train is slowly getting stacked up on the Westbound track behind the swan?
As an aside, I wonder how a swan on the tracks would've been dealt with if this were 1923 instead of 2023? I rather suspect it wouldn't have been by letting the entire service go to pot for practically the entire rest of the day.
So a very awkward situation for the railway (and the swan).I think it was Westbourne park/Westbound running tunnel which is why it only effected the Elizabeth line
I was on a westbound yesterday lunchtime. It arrived more or less on time but then sat at TCR. After 10 minutes I got off. Just as well as RTT suggests the train eventually ran 171 minutes late.Presumably the swan incident was west pf Paddington on the GWML, before Acton ML and therefore a Network Rail problem?
Were GWR services also affected?
Why would a blockage west of Paddington prevent Shenfield/Abbey Wood-Paddington services running - something half the service does anyway.
Media reports (BBC etc) were very vague about where the problem was, and any alternative routes to take.
Just "swan on the tracks", a bit like the "wrong kind of snow"...
![]()
Elizabeth line suspended due to swan on the track
Passengers say they have been held on trains for up to an hour because of the swan at Paddington.www.bbc.co.uk


Someone probably drove a train over it.
Currently on 9U69 travelling eastbound. Got into Paddington tunnel, but not the platform. There’s a train stuck in the platform that will not move at all. After 30 mins of being stuck, we’re now travelling back to Ealing Broadway, just where I started almost an hour ago.
Apparently there’s “nowhere else to go” apart from Ealing. No option to back into Paddington high level after leaving the tunnel?
On the events of yesterday, According to this Facebook source the swan that landed below ended up passing away. Exactly how baffles me. Unless it was prior to the Reading train stopping for it.
View attachment 138319
From that picture, the swan isn't even on the tracks at that point, although is very close to them.
You'd think that all you'd need to do is slowly edge a train forward towards it at say - 5mph, and it would probably move or fly away
On a more trivial note, it was interesting to see that the siding just east of Abbey Wood was actually occupied by a train - first time I can ever recall noticing that during the day since the line opened. Presumably parked there because of the disruption.
"Sandford's most wanted!"From that picture, the swan isn't even on the tracks at that point, although is very close to them.
You'd think that all you'd need to do is slowly edge a train forward towards it at say - 5mph, and it would probably move or fly away
I appreciate the double-reverse would have taken (even more) time, but Traksy showed 5 empty platforms, including the ones the EL used to terminate at, so I do think there was space.You'd have to have reversed and then reversed again. And no, Paddington would have already diverted trains, so was full. Very unfortunate situation to be in.
I appreciate the double-reverse would have taken (even more) time, but Traksy showed 5 empty platforms, including the ones the EL used to terminate at, so I do think there was space.
Not good TodaySeems to be major reliability problems on EL recently, maybe related to the recent software update. 3 failed trains I think today and yesterday.
Also today there was no passenger information systems working whatsoever when I was on it this afternoon, either above the platform doors or in the station entrances, which seems mad given there was live data on RTT available!
How many is that? Which platforms are allocated? I assume there’s a separate plan for peak and off peak? Does the plan take into account average passenger loading?Elizabeth line normally only has an agreed limited number of platforms during disruption - GWR or Heathrow services may have been due.
Surely more about how you can’t just turf GWR out of their station because once again the Elizabeth Line has screwed up. You can’t tell someone in Cornwall that their train is cancelled because the Elizabeth Line messed up, it already happens enough.Does the plan take into account average passenger loading?