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.