Train not calling at certain stops.

[Coolguy22468]

I was on the 17:46 London Midland train from London Euston to Crewe and they said that the train was meant to call at Leighton Buzzard and Bleatchley today but the announcer said that the train will now longer be calling at the two stops because the monitors at London Euston were displaying the wrong information, can London Midland do that?

 

[yorkie]

I don't fully understand what you are saying, but the 1746 is scheduled to only call at Watford Junction, Milton Keynes, Northampton, Rugby and then most stations to Crewe.

 

[Searle]

He might mean it wasn't meant to call at Leighton Buzzard and Bletchley, but the boards incorrectly said that it would, so it had to stop additionally there to avoid lots of angry commuters? Just a guess :P

EDIT: Actually on second thoughts, that wouldn't make much sense in accordance with the title, haha

 

[MidnightFlyer]

It sounds like the monitors at EUS were saying (incorrectly) that it called at Leighton Buzzard and Bletchley, and the member of staff said that this was incorrect and the train wasn't going to...

 

[Urban Gateline]

It sounds like the monitors at EUS were saying (incorrectly) that it called at Leighton Buzzard and Bletchley, and the member of staff said that this was incorrect and the train wasn't going to...

I understood it like this too!

 

[yorkie]

Ah, "they said" was meant to be "the boards displayed", makes sense now!

 

[DarloRich]

I was on the 17:46 London Midland train from London Euston to Crewe and they said that the train was meant to call at Leighton Buzzard and Bleatchley today but the announcer said that the train will now longer be calling at the two stops because the monitors at London Euston were displaying the wrong information, can London Midland do that?

The 17:46 doesn't stop at The Buzzard or Beltcho. It runs fast from Watford to MK.

Bit confused tbh............

 

[Coolguy22468]

It sounds like the monitors at EUS were saying (incorrectly) that it called at Leighton Buzzard and Bletchley, and the member of staff said that this was incorrect and the train wasn't going to...

I think that might be the case, the announcer who said it didn't say it very clearly.

 

[ollyrogers]

Boy, that escalated quickly... I mean, that really got out of hand fast!

Sounds like he meant the monitors showed the train as stopping at Leighton Buzzard and Bletchley but when on the train the driver/ guard announced it would in fact not be stopping at either place

 

[Bedpan]

Boy, that escalated quickly... I mean, that really got out of hand fast!

Sounds like he meant the monitors showed the train as stopping at Leighton Buzzard and Bletchley but when on the train the driver/ guard announced it would in fact not be stopping at either place

......because the monitors at Euston were giving the wrong information (!!??!!).

So if the monitors at Euston were giving the right info, would it have stopped at Leighton Buzzard and Bletchley, despite the fact that the 17.46 is fast from Watford to MK?

 

[dvboy]

Have had ATW services incorrectly display internally that they were stopping at SGB when in fact they weren't and first stop was WVH.

 

[causton]

......because the monitors at Euston were giving the wrong information (!!??!!).

So if the monitors at Euston were giving the right info, would it have stopped at Leighton Buzzard and Bletchley, despite the fact that the 17.46 is fast from Watford to MK?

no no, the announcer said it... because the monitors were giving the wrong information! That's how I read it

 

[Coolguy22468]

no no, the announcer said it... because the monitors were giving the wrong information! That's how I read it

I think that was it that the monitors said the wrong thing, its a good thing that it didn't stop at those stops otherwise it would of made a slow journey even slower.

 

[maniacmartin]

Was the onboard announcement made after the train departed?

If the monitors said it would be making these stops, when in fact it wasn't timetabled to, and the onboard announcer only announced the true calling pattern after the train departed, should the TOC be obliged to make those extra stops for passengers who boarded due to the station monitor error?

I know I would be annoyed if I boarded a train calling at Leighton Buzzard or Bletchley (where my final destination may be), only to find out that it wouldn't be calling there after all.

I presume the announcer advised passengers to extra stations to change at Watford Jxn

 

[LE Greys]

At least they spotted it. The old destination board at King's Cross would sometimes throw in a random 'Stevenage' or 'Hitchin' on an express or the Peterborough fasts, leaving a dozen or so passengers having to make their way back from St Neots, Letchworth or Peterborough.