Greybeard33
Established Member
This was undoubtedly an unfortunate and confusing incident. I do not know the root causes, but the data in RTT enables some clarification of, and rationale for, the sequence of events:I rarely use Northern, and to be fair, on the odd occasion I have there have been no real issues. Not so, today, however;
Travelling from Oxford to Glasgow I decided to go via XC to Stockport, EMR from there to Manchester Oxford Road, then Northern (1C55 1029 Manchester Airport [MIA]-Barrow) to Preston for a good connection into Avanti. I had checked that all trains were running, and they were, including 1C55, formed by 195121.
So I arrived at Oxford Road, a little late but in time for 1C55, only to see no mention of it on the information screens; Not showing cancelled, just not mentioned at all! But thanks to a non-rail industry system (Realtime Trains) I found that it was indeed cancelled, due to a traincrew issue, code TH.
While waiting at Oxford Road working out what to do next, the place descended into chaos; A train from Barrow, 1Y94 0848 to MIA, arrived in Platform 2 and stood there for 29 minutes, due to unit swap, code YU. Meanwhile, a train, formed strangely enough by 195121, arrived in Platform 3 from the Piccadilly direction and was advertised as a train back to MIA, that set then stood for a while and before departure was amended to running to Piccadilly only - An absolutely ludicrous, pointless train. Meanwhile trains backed up behind this set resulting in delays of up to 30 minutes to services for Liverpool, Blackpool, Saltburn and Glasgow. No attempt was made to route anything via Platform 1.
Passenger information was desperately poor as well, although I doubt whether the station staff knew any more about what was going on than the passengers.
Just an embarrassing shambles.
195124, working 1Y94, Barrow to Manchester Airport, arrived at Oxford Road two minutes late, at 1056. This unit was then taken out of service. It subsequently departed back west at 1114 as Very Short Term Plan (VSTP) ECS working 5J87, to Newton Heath depot via the Ordsall Chord.
195121, which was booked to work the cancelled Airport to Barrow service 1C55, instead formed 5C55, a VSTP ECS working from the Airport to Oxford Road. This was planned to arrive at 1051, so that the unit would have been ready to immediately pick up the 1Y94 passengers for the onward working to the Airport (the unit swap). Unfortunately 5C55 departed late from the Airport and was then trapped behind the late running Airport to Liverpool stopper 2F33, causing further delay. It did not get to Oxford Road until 1113. 195121 eventually departed back east, now as 1Y94, at 1125, 29 late. The service was then cut short to terminate at Piccadilly. The unit reversed again and subsequently formed 1C79 to Windermere, which was scheduled to start from the Airport but started short from Piccadilly, departing Oxford Road at 1154, 1 late.
Regarding the related delays to other services:
323225, working the aforementioned 2F33 Airport to Liverpool stopper, was already 10 minutes late leaving the Airport, due to late arrival of the unit from its previous service. It departed Oxford Road at 1111, 13 late, 2 minutes before the arrival of 195121, working 5C55. 1P71, Airport to Saltburn, arrived at Piccadilly at 1110, already 13 late, and then lost a further 14 minutes between Piccadilly and Oxford Road, arriving there at 1127. It was followed by 1N61, Airport to Blackpool, which was also 28 late departing Oxford Road. Finally 1S51, Airport to Glasgow, was 13 late departing Oxford Road.
Oxford Road Platform 1 is only 105m (4-car length) and so could not have accommodated the 6-car Saltburn train 1P71. Presumably this is why the queue developed.
Realtime Trains | Departures from Manchester Oxford Road around 1100 on 24/04/2023
Train information at Manchester Oxford Road around 1100 on 24/04/2023. From Realtime Trains, an independent source of train running info for Great Britain.