LNER delay repay refusal

[Bletchleyite]

But anyway that's not the important bit - the question is whether I'm denied Delay Repay for the second scenario because I didn't have a contract for the second part until I knew it was delayed.

I've created a new thread for this question:

Does Delay Repay apply when the delay is known about already at ticket purchase?

But anyway that's not the important bit - the question is whether I'm denied Delay Repay for the second scenario because I didn't have a contract for the second part until I knew it was delayed. This is a wider question - does DR apply when you know about the delay when you purchase the ticket...

www.railforums.co.uk

Not sure we will get consensus, though!

 

[Haywain]

Also, how does one check the published timetable of the day after the fact?

The FastJP journey planner allows an itinerary to be produced for a past date, and for the OP's journey it gives an arrival at Huntingdon at 22:08.

 

[Royston Vasey]

Curious though that the booking confirmation (which surely forms the contract) provides a connection below MCT.

 

[Trainbike46]

The FastJP journey planner allows an itinerary to be produced for a past date, and for your journey it gives an arrival at Huntingdon at 22:08.

Thank you, I didn't realise that. That will be useful next time I have to make a delay repay claim.

As a point of order though, I am not the OP and didn't make the journey described in this thread

 

[Haywain]

Curious though that the booking confirmation (which surely forms the contract) provides a connection below MCT.

What booking confirmation? The OP says they bought the Huntingdon to Peterborough ticket on the day of travel. The three tickets used were bought at separate times, so no connections were contractual by dint of an itinerary for the through journey.

 

[Belperpete]

That’s interesting, Watershed. Thank you. I’ve looked at my advance ticket and it does say 2118 as the arrival time at Peterborough. However, when I did a through itinerary for the trip beforehand, the through times offered on the LNER booking engine were on the 2124 from Peterborough to Huntingdon, even though the connection time was apparently 6 minutes.

Do you have a record of this itinerary that you could use to support your claim? Could you accidentally have entered the wrong date?

 

[Royston Vasey]

What booking confirmation? The OP says they bought the Huntingdon to Peterborough ticket on the day of travel. The three tickets used were bought at separate times, so no connections were contractual by dint of an itinerary for the through journey.

I was mistakenly referring to the itinerary mentioned in post #24 as a booking confirmation, sorry. Curious that even a journey planner would offer below MCT but no, clearly that is not a contract

 

[Belperpete]

LNER have refused my delay repay application stating ‘as your tickets were purchased in different places we are not able to compensate for a missed connection’.

If you had bought your tickets in one transaction you would inherently have had a valid itinerary. By buying the tickets separately, you have inadvertently ended up with an invalid itinerary. I suspect that this is what LNER mean.

 

[andylikestrain]

Do you have a record of this itinerary that you could use to support your claim? Could you accidentally have entered the wrong date?

No, I don’t have any evidence of the itinerary, but I’m 100% sure that the LNER booking engine showed the ‘timetabled’ arrival time of 2114 at Peterborough, just like the dummy booking I posted above.
I didn’t know that relying on a pdf timetable was not a good idea these days!
Every day’s a school day.

== Doublepost prevention - post automatically merged: 12 Oct 2025 ==

If you had bought your tickets in one transaction you would inherently have had a valid itinerary. By buying the tickets separately, you have inadvertently ended up with an invalid itinerary. I suspect that this is what LNER mean.

But my understanding of the rules is that is not relevant? The tickets don’t have to be bought in one transaction?

 

[Bletchleyite]

But my understanding of the rules is that is not relevant? The tickets don’t have to be bought in one transaction?

They indeed do not. LNER have given a wrong reason for rejection, but as there is a correct reason for rejection as already noted there is little point in appealing as they won't pay it, they will just find that correct reason and give that instead.

== Doublepost prevention - post automatically merged: 12 Oct 2025 ==

If you had bought your tickets in one transaction you would inherently have had a valid itinerary. By buying the tickets separately, you have inadvertently ended up with an invalid itinerary. I suspect that this is what LNER mean.

That would assume competence, but it is true...

 

[andylikestrain]

According to Timetable History, the 20:25 was advertised as arriving at PBO at 21:18 since 1 June this year. Unless the OP booked their Advance before this - and it seems unlikely that LNER would have opened up reservations before then, since this was a day with Carlisle diversions - then 21:18 would have been the PBO arrival time they would have been told from the outset.

As others have said, this is why reference to a printed or PDF timetable can be misleading. In practical terms it would clearly be feasible to make an 6 minute connection like that, but it's not an official connection. The next Thameslink train (the fist one with a valid connection) would have been half an hour later and ran on time.

Thanks All again.
Well I’ve just gone onto Real Time Trains and the 2025 from Doncaster is scheduled to arrive at 2114, not. 2118 this coming Saturday (18 Oct).Screenshot below. This concurs with the LNER booking engine screenshot posted above for an itinerary on that day, stating 2114 as the arrival time at Peterborough and arriving Huntingdon at 2138.
I see that on timetable history the arrival time at Peterborough has been 2118 from 1.6.25, as mentioned above.
I wonder if that is going to be changed between now and Saturday…?

== Doublepost prevention - post automatically merged: 12 Oct 2025 ==

It’s also interesting that the service has an arrival time of 2114 on RTT on Sat. 4th October, despite timetable history apparently having an arrival time of 2118 since 1.6.25…
Bletchlyite, you are of course correct that some fights aren’t worth the hassle, but this has got me annoyed!

 

[Haywain]

I wonder if that is going to be changed between now and Saturday…?

Whether it is or not isn't going to be of any help to you.

 

[Watershed]

Thanks All again.
Well I’ve just gone onto Real Time Trains and the 2025 from Doncaster is scheduled to arrive at 2114, not. 2118 this coming Saturday (18 Oct).Screenshot below. This concurs with the LNER booking engine screenshot posted above for an itinerary on that day, stating 2114 as the arrival time at Peterborough and arriving Huntingdon at 2138.
I see that on timetable history the arrival time at Peterborough has been 2118 from 1.6.25, as mentioned above.
I wonder if that is going to be changed between now and Saturday…?View attachment 190246

== Doublepost prevention - post automatically merged: 12 Oct 2025 ==

It’s also interesting that the service has an arrival time of 2114 on RTT on Sat. 4th October, despite timetable history apparently having an arrival time of 2118 since 1.6.25…
Bletchlyite, you are of course correct that some fights aren’t worth the hassle, but this has got me annoyed!

The PBO arrival time for that service is indeed 21:14 under the permanent (WTT) schedule, which is what runs on most days.

However, an amended schedule for the day you travelled (20 Sep) was published on 1 June. That involved a later PBO arrival time of 21:18, so that is what you would have been told when you booked your Advance ticket.

The arrival time on another date is of no relevance to your claim for travel on 20 Sep.

 

[andylikestrain]

Ah I see. I thought the amended schedule was for all the services since 1.6.25, not just 20 September.
That‘s that then. Thank you for all your help and knowledge. I’ve learned stuff!

 

[Watershed]

Ah I see. I thought the amended schedule was for all the services since 1.6.25, not just 20 September.
That‘s that then. Thank you for all your help and knowledge. I’ve learned stuff!

No problem, it can be a complex subject but in this particular instance I think you 'fell between the cracks' by not buying your split tickets from one retailer in a single transaction, or at least checking a journey planner for your through journey before travel.

Either option would have alerted you to tell fact that the connection you wanted wasn't possible, so I would suggest doing one of those two for future journeys