[John Ray[_3_]]

I've just looked at the live departure board for Norwood Junction and
found a rather strange entry. It shows a 1602 departure to Beckenham
Junction (currently running 22 mins late) via East Croydon. The full
journey is shown as departing London Bridge at 1533, then all stations
to Norwood Jct via Tulse Hill and Crystal Palace, then on to East
Croydon arriving at 1606, Birkbeck arrival 1603 (but reported as
cancelled), and scheduled to arrive at Beckenham Jct. at 1606 but
estimated at 1628. Weird. I wonder how that happened?

--
John Ray

[Peter Smyth]

"John Ray" wrote in message
news
I've just looked at the live departure board for Norwood Junction and
found a rather strange entry. It shows a 1602 departure to Beckenham
Junction (currently running 22 mins late) via East Croydon. The full
journey is shown as departing London Bridge at 1533, then all stations
to Norwood Jct via Tulse Hill and Crystal Palace, then on to East
Croydon arriving at 1606, Birkbeck arrival 1603 (but reported as
cancelled), and scheduled to arrive at Beckenham Jct. at 1606 but
estimated at 1628. Weird. I wonder how that happened?

The 1533 is supposed to go to Beckenham Junction so presumably it was
diverted to East Croydon but whoever entered it in the system didn't
cancel the Beckenham bit properly.

Peter Smyth

[John Ray[_3_]]

On 01/12/2010 18:03, Peter Smyth wrote:


The 1533 is supposed to go to Beckenham Junction so presumably it was
diverted to East Croydon but whoever entered it in the system didn't
cancel the Beckenham bit properly.


Thanks - that explains it.

--
John Ray

[Q]

"Peter Smyth" wrote in message
...

The 1533 is supposed to go to Beckenham Junction so presumably it was
diverted to East Croydon but whoever entered it in the system didn't
cancel the Beckenham bit properly.


TRUST shows it arv ECR at 16:41 but not leaving.

CIS shows it Cancelled at BIK

RTTI shown as 'Dealyed' at BKJ

I should have been cancelled either in CIS, Live Departure Boards, or Tyrell
and then it would have shown up correctly everywhere else.

Simple stuff really - and TOC's wonder why pax get hacked off with them.

[Graham J[_2_]]

I wonder how that happened?

There were some interesting entries for East Croydon to London Bridge
services this morning. First Capital Connect's emergency service from
Brighton to City Thameslink was being listed fine, but Southern's service
not quite so well. The Three Bridges to London Bridge service was being
listed three times. Once as a cancelled service (presumably the normal
timetabled service) and twice for what was presumably meant to be the
special service. The East Croydon to London Bridge slow service was
likewise being listed three times, one the Tattenham Corner cancelled
service, and the other two with the Tattenham Corner to East Croydon stops
cancelled but then running fast to London Bridge. Having corrected it to a
slow stopping service the destinations became variously New Cross Gate,
Sydenham and the truly inspired Bricklayers Arms Junction (might have just
said Bricklayers Junction, either way it wasn't terribly helpful). They've
settled on New Cross Gate now (the London Bridge stop showing as timed at
0.00 and cancelled) so still not right.