Entries Tagged 'Thameslink Delays' ↓

First Capital Connect recently published their performance stats for the period running between 30 May to 26 June. Once again, performance on the Thameslink route was unacceptable with just 88.2% of planned train service running less than 5 minutes late at their final destination. 3.2% of planned services (Thameslink + Great Northern routes combined) were also cancelled for part or all of their journey.

FCC also disclose that their target is for 90.32% of planned Thameslink services to run less than 5 minutes late at their final destination. Therefore, in the May – June period FCC underperformed even by their own standards! Continue reading →

First Capital Connect have published their Thameslink service statistics for the Jan/Feb period.

Following the abysmal service experienced over the Dec/Jan period (when only 62.8% of trains reached their final destination less than five minutes late) First capital Connect continue to disappoint with only 76.8% of training running ‘on time’ in Jan/Feb.

It was also revealed that 8.3% of trains were cancelled for part or all of their journey across the whole FCC network. I Hate Thameslink has previously pointed out that FCC do not reveal how many cancellations occurred on the Thameslink route alone which we feel they should.

First Capital Connect recently revealed their results for ‘period 10′ which covers 13th December 2009 to 9th January 2010. The FCC press release reveals that in this period just 62.8% of trains ran with less than a five minute delay on the Thameslink route and Continue reading →

First Capital Connect advised customers  not to travel and to leave London by 7pm yestersday. Their Twiter status was

Limited service this eve on Thameslink route, don’t travel unless you have to. Advise that you leave London by 7pm. May not be later trains.

Morning commuter services were severly disrupted, by up to 2 hours in some cases,  and nearly all services were cancelled by mid afternoon. A snapshot of the live departure table, submitted by one of our readers shows the extent of the disruption. Continue reading →

It appears that FCC have hit an all time low by providing an abysmal level of service today on the Thameslink route. I was lucky enough to take today off as annual leave, but have been able to monitor the chaos via twitter. It appears FCC have not only delayed customers for (literally) hours but have endangered lives.

It looks like a train broke down which caused unimaginable chaos. This combined with the bad weather and the ongoing dispute with drivers was just just too much for FCC to cope with.

A selection of tweets are posted below. Shocking. Continue reading →

First Capital Connect announced the following on Thursday 10th December;

ASLEF has withdrawn the ballot for industrial action.
The union has considered our revised pay offer and agreed to recommend it for acceptance to members. The offer is spread over two years and includes productivity based increases. We are working jointly with Aslef to encourage our drivers to resume rest day and overtime working, our aim being to provide a full, normal service to our customers as quickly as possible.

Despite this, the reduced timetable is stil in operation. Leaflets were distributed at thameslink stations this morning that state;

Fewer than the anticipated number of drivers have put themselves down to be rostered next week given that they only learned on Tuesday night of the ASLEF decision.

Another poor excuse, and being the betting man I am, I would put m Continue reading →

In addition to the amended timetable, the following trains will be running / canceled today – lucky us!

Thameslink route

Northbound
- 09:37 Sutton – Kentish Town
- 16:18 Elephant & Castle – Bedford (calls at Farringdon at 16:27)
- 16:04 Brighton – London Bridge
- 17:58 Elephant & Castle – Luton (calls at Farringdon at 18:07)
- 18:18 Herne Hill – Bedford (calls at Farringdon at 18:37)

Southbound
- 08:06 St Albans – Sutton
- 08:54 Luton – Elephant & Castle
- 17:11 London Bridge – Brighton

Great Northern route

Northbound
1312 Moorgate to Hertford North terminates at Alexandra Palace
1332 Moorgate to Hertford North cancelled
1442 Moorgate to Welwyn Garden City cancelled
1552 Moorgate to Stevenage cancelled
1638 Moorgate to Hertford North cancelled
1757 Kings Cross to Welwyn Garden City cancelled
1808 Moorgate to Welwyn Garden City cancelled
1823 Moorgate to Welwyn Garden City cancelled
1937 Moorgate to Welwyn Garden City cancelled
2007 Moorgate to Welwyn Garden City starts at Alexandra Palace
2152 Moorgate to Hertford North cancelled
2241 Kings Cross to Welwyn Garden City cancelled
0106 Kings Cross to Letchworth (Saturday morning) cancelled

Southbound
1232 Hertford North to Moorgate terminates at Alexandra Palace
1343 Welwyn Garden City to Moorgate cancelled
1452 Hertford North to Moorgate cancelled
1544 Welwyn Garden City to Moorgate cancelled
1620 Letchworth Garden City to Moorgate due 1726 will no longer call at:  Letchworth Garden City, Hitchin, Stevenage and Watton-At-Stone.
1659 Stevenage to Moorgate cancelled
1736 Hertford North to Moorgate cancelled
2058 Welwyn Garden City to Moorgate cancelled
2310 Hertford North to Kings Cross cancelled
2318 Letchworth to Kings Cross cancelled
0516 Royston to Kings (Saturday morning) cancelled

Evening.

First Capital Connect have launched a new Twitter service where you can receive custom messages about your specific journey.

Here’s how it works – from the FCC website;

Send our Twitter account, FirstCC, a direct message listing your stations and times. The direct message should look something like this (using commas to separate stations and times, and stating times in 24-hour format):

kings cross, cambridge, 0800, 1800

We’ll receive your stations and times and store them in our database. Then, when major incidents occur on your route within an hour either side of your times, you’ll receive a direct message sent to your Twitter account straight away.

Continue reading →

Looks like the weather is turning… not only does this mean I will most probably get a cold in the next few days but the First Capital Connect service will deteriorate – dramatically.

The 06.52am from Cricklewood arrived at about 06.58am today (only a few mins late, not bad) but on approaching Kentish Town the train just decided to stop…dead. The lights turned out, and we were informed that the overhead power lines had failed. We miraculously regained power for a while and were able to stop at Kentish Town. A further announcement saw mass exodus from the train as the driver informed us he had no idea when we would be moving again.

I decided to wait it out, and we were on the move again within 10 mins, but the whole journey saw me 30 mins late for work. Were you on this train? Suffered similarly? Leave a comment below….

NB In response the the geezer who left the comment below…yes the network is FCC but the London section is commonly referred to as Thameslink, as are many of the stations…..Plonker.