Page 1 of 1

Can't book flight despite being available?!

PostPosted: 25 Jan 2010, 21:36
by Mont25
Hi,

I'm trying to book a flight back from LAX to LHR on Weds 25/08/2010 on the Virgin website. It says that the flight is available but when I select it and hit next it says that the flight is no longer available.

I've looked on SeatCounter and there is availability in most classes. Plus, it's available on Expedia.

Does anyone know why I can't book it and whether there's any chance of it 'opening up' for booking at any point? I'm wondering whether to book through Expedia but am worried that the flight has been cancelled but not everyone's been told yet!

Thanks.

PostPosted: 25 Jan 2010, 21:48
by Darren Wheeler
Could be there has been a flight cancellation or there is a problem with the front-end of the booking tool.

Is it for VS08 or VS24?

PostPosted: 25 Jan 2010, 21:50
by Mont25
quote:Originally posted by Darren Wheeler

Is it for VS08 or VS24?


Hi,
It's the VS24 we're after. The VS8 looks ok to book (but strangely with fewer classes available according to SeatCounter).
Cheers.

PostPosted: 25 Jan 2010, 22:01
by Darren Wheeler
Ahh, it's not unknown for the 24 to be cancelled and merged with the 8, but the 23 is showing as bookable...

PostPosted: 25 Jan 2010, 22:08
by Penny_L
looks ok on my screen, up to the point of entering credit card details

PostPosted: 25 Jan 2010, 22:19
by Stevieboy
There are currently quite a lot of other flights especially on the MCO route which are showing as available but are unable to be booked. I spoke to VS regarding this last week and they told me that the two flights were in the process of being merged.

-Steve

PostPosted: 25 Jan 2010, 22:48
by Mont25
Well, I phoned reservations and they had availability on the VS24 so I booked through them. It is a Q fare (so slightly more expensive than the website suggested). I guess it's now just a case of waiting to see if it gets cancelled!

PostPosted: 25 Jan 2010, 22:53
by slinky09
I'd be surprised if the VS24 was cancelled in August. I suspect a Web site glitch.