113 cancellations on FCC Thameslink
 

At least a quick glance suggests Thameslink services make up 113 of
the 116 cancelled trains now showing on FCC Journey Check (the other
three being GN services):
http://www.jcheck.com/firstcapitalconnect

In the 'Line Update' section on the Journey Check page, one entry
cites "Line problem in the Blackfriars area", specifically "poor rail
conditions" as one contributory factor. Another entry just cites "poor
weather conditions".


Meanwhile this is on the FCC website:

---quote---
Major disruption
Monday morning service

Thameslink route

There are many cancellations on the Thameslink route because of last
night's extreme frost which reached -13 degrees in some places and
affected trains and track infrastructure.

Tickets can be used on East Midlands services and London Underground
on all reasonable routes as well as Great Northern route services.

We have not been able to call at London Bridge and services have been
diverted via Herne Hill.
---/quote---

113 cancellations on FCC Thameslink
 

On Dec 20, 8:17*am, Mizter T wrote:


At least a quick glance suggests Thameslink services make up 113 of
the 116 cancelled trains now showing on FCC Journey Check (the other
three being GN services):
http://www.jcheck.com/firstcapitalconnect

In the 'Line Update' section on the Journey Check page, one entry
cites "Line problem in the Blackfriars area", specifically "poor rail
conditions" as one contributory factor. Another entry just cites "poor
weather conditions".

Meanwhile this is on the FCC website:

---quote---
Major disruption
Monday morning service

Thameslink route

There are many cancellations on the Thameslink route because of last
night's extreme frost which reached -13 degrees in some places and
affected trains and track infrastructure.

Tickets can be used on East Midlands services and London Underground
on all reasonable routes as well as Great Northern route services.

We have not been able to call at London Bridge and services have been
diverted via Herne Hill.
---/quote---



All info shows all FCC trains cancelled at Luton, but I have seen and
heard the occasional 319 in the last hour or so.


I shall investigate travel further once I've read all the work
weekends emails by remote access.



--
Nick

113 cancellations on FCC Thameslink
 

In message
, at
00:17:37 on Mon, 20 Dec 2010, Mizter T remarked:
At least a quick glance suggests Thameslink services make up 113 of
the 116 cancelled trains now showing on FCC Journey Check (the other
three being GN services):
http://www.jcheck.com/firstcapitalconnect

Wires in trouble at St Neots. Lots of cancellations and some trains
shuttling London-Hitchin.
--
Roland Perry

113 cancellations on FCC Thameslink
 

Appeared on web site in only the last 30 mins, it was not there when I
checked at 10:20
:


Major disruption
Monday morning service


Thameslink route

A power cut in the Farringdon area is contributing to significant
disruption caused by the extreme weather conditions and last night's
extreme frost which reached -13 degrees in some places. A separate
power cut has also affected our information systems which are
incorrectly showing our services as cancelled. In fact, we are
operating a revised timetable as follows:

There are no services across central London or between Wimbledon and
Sutton and London.

London Bridge - Brighton we are operating two trains per hour as
follows:
From London Bridge: xx12 and xx42
From Brighton: xx07 and xx37

St Pancras International - Bedford we are operating four trains per
hour as follows:
From Bedford: xx:10 and xx40 all stations; xx00 and xx30 all stations
to St Albans and then fast to West Hampstead and St Pancras
International.
From St Pancras International: xx14 and xx44 all stations to Bedford;
xx09 and xx39 to West Hampstead, St Albans then all stations to
Bedford.

Network Rail is working hard to restore services across central London
which will allow us to resume services on the Wimbledon/Sutton loop.




--
Nick

113 cancellations on FCC Thameslink
 

In article
,
(Mizter T) wrote:

At least a quick glance suggests Thameslink services make up 113 of
the 116 cancelled trains now showing on FCC Journey Check (the other
three being GN services):
http://www.jcheck.com/firstcapitalconnect

In the 'Line Update' section on the Journey Check page, one entry
cites "Line problem in the Blackfriars area", specifically "poor rail
conditions" as one contributory factor. Another entry just cites "poor
weather conditions".


Meanwhile this is on the FCC website:

---quote---
Major disruption
Monday morning service

Thameslink route

There are many cancellations on the Thameslink route because of last
night's extreme frost which reached -13 degrees in some places and
affected trains and track infrastructure.

Tickets can be used on East Midlands services and London Underground
on all reasonable routes as well as Great Northern route services.

We have not been able to call at London Bridge and services have been
diverted via Herne Hill.
---/quote---

The GN wasn't doing too well this morning either. I got the 9:20 which was
only 4 cars (so jam packed) and arrived just over half an hour late
(enough for a Passenger Charter claim? I forget).

There was nothing coming from London to Cambridge that wasn't the best
part of an hour late at 9:00 and the 9:04 arrival/9:26 departure were
cancelled. The 09:20 having Royston and Letchworth stops added in the new
timetable didn't help either.

Stansted Cross Country services were late too. I'm not clear if the Sandy
wires down problem was cleared by then.

--
Colin Rosenstiel

113 cancellations on FCC Thameslink
 

On Dec 20, 11:00*am, D7666 wrote:

Major disruption
Monday morning service

Thameslink route


further update

''Tomorrow, Tuesday: At the request of Network Rail, because of
further freezing conditions that will affect track, signalling and
other infrastructure, we will be running a revised timetable again
tomorrow. It is expected the Thameslink route will be open across
central London so we will be able to operate a service between London
and Sutton/Wimbledon.

''


--
Nick

113 cancellations on FCC Thameslink
 

In article
,
(D7666) wrote:

Appeared on web site in only the last 30 mins, it was not there when I
checked at 10:20:


Major disruption
Monday morning service


Thameslink route

[snip]

They've adopted the emergency timetable on the GN. I'm on the 15:06 (2C20)
to Cambridge. Finsbury Park, Potter's Bar, Hatfield, then all stations to
Royston, then Cambridge.

Meanwhile "Live Departures" is a bigger work of fiction than normal,
showing a completely different set of GN trains. As I was leaving the
Cross, it was showing Cambridge departures, all "on time" at 15:15, 15:45,
15:52 and 16:06 and departures from Cambridge at 15:15, 15:26, 15:45 and
15:55.

Passenger Focus are right. Once disruption comes the fragmented railway
becomes completely dysfunctional.

--
Colin Rosenstiel

113 cancellations on FCC Thameslink
 

On Dec 20, 3:10*pm, D7666 wrote:
On Dec 20, 11:00*am, D7666 wrote:

Major disruption
Monday morning service

Thameslink route

further update

''Tomorrow, Tuesday: At the request of Network Rail, because of
further freezing conditions that will affect track, signalling and
other infrastructure, we will be running a revised timetable again
tomorrow. It is expected the Thameslink route will be open across
central London so we will be able to operate a service between London
and Sutton/Wimbledon.

''

--
Nick

Todays saga was 08:15 - 09:00 at Luton then I gave up. There were a
couple of trains but wedged solid could not get on them.

Tried again after 11:15 going for web site gen 11:10 ex Bedford in
their alleged 4 TPH pattern. When I got to LUT I find it was not 4 TPH
but some half way house as units and crews still in wrong place. 8.377
arrived at about 11:30 and ran all stations & I left it at WHP.

All day they been showing their web site a 4 TPH service. I checked
this at ~14:00 ~15:00 and ~16:20.

Got to SPI 16:35 and found it was 2 TPH.

16:44 ex SPI 8.377 and rammed solid full. The only reason I manged a
seat was I happened to be in pole position for the rearmost door and
went for f.c.

And hey presto I get home an check and now it says 2 TPH.

This morning was just chaos, not helped by info system being down, but
the disruption was driven by the Farringdon power outage.

This evening I don't know. FCC appear to be blaming Networkrail but no
reason given.

I am suspicious as all 4 of the only 4 FCC trains working I saw this
evening were all 8.377 - no 319s seen moving. OK with 4 trains I've
seen only around half the number of trains needed for 2 TPH but I do
wonder if something else is going on they ain;lt telling us yet.


--
Nick

113 cancellations on FCC Thameslink
 

On 20/12/2010 18:25, D7666 wrote:

Todays saga was 08:15 - 09:00 at Luton then I gave up. There were a
couple of trains but wedged solid could not get on them.

At Sutton announcements were saying there were no FCC services, and
passengers should use SWT, Underground and Tramlink instead. Just one
tiny snag with that at Sutton station... :)

--
Arthur Figgis Surrey, UK

113 cancellations on FCC Thameslink
 

On Dec 20, 7:08*pm, Arthur Figgis wrote:

passengers should use SWT, Underground and Tramlink instead. Just one
tiny snag with that at Sutton station... :)

LOL

The perils of long line auto PA.

Perhaps LOL is not appropriate, passengers expect sensible
information, and its dribble like that that causes no-one to pay
attention.

Amid all the shambolic chaos this morning, we still had the routine
droning about Blackfriars closed (largely irrelevant at Luton since
there were no through core trains anyway) AND the routine weekend
engineering works one which on any normal weekend has little value on
a Monday, but completely useless refering to coming weekend works as
Sat+Sun is xmas weekend.

Did we get any PA about what trains were actually running or audio
info that the visual info was screwed ... did we ****.

--
Nick


--
Nick