I’ve recently been using Travelzoo’s metasearch engine fly.com to research some flights, and have noticed a number of major bugs. One has been ongoing and I had simply chosen to ignore it. I’ve only recently discovered the other problem, but perhaps it’s been there for a while an I just never noticed it.
The newly discovered (yet perhaps not new) problem is fly.com’s inability to understand time zones. The good news is that it only appears to be affecting search results with British Airways. The bad news is that British Airways is a pretty major carrier (the largest in the UK, and the largest international carrier serving the US), so having a BA-related bug is a much bigger deal than if there was a similar issue with a smaller carrier such as Uzbekistan Airways.
Take a look at the screenshot below. According to this, BA’s nonstop flights from San Francisco to London are just over 18 hours, whereas the return nonstop flight to SFO is just under 3 hours:
Not even the Concorde is that fast. And even it if was, it’s now out of commission anyway.
I’ve checked the same flights on BA’s website directly, as well as on other metasearch sites such as Kayak and OTA’s such as Expedia. The only place where I saw this bug is with BA flights on fly.com, but that’s not to say that there might not also be bugs with other airlines, or similar BA time zone issues on websites that I didn’t check. However, I have a hunch that it is an internal bug with fly.com.
One of the reasons that I suspect that the fault is with fly.com is because of another ongoing bug that I can confirm has been ongoing for several months, perhaps longer. It appears the fly.com doesn’t yet understand the difference between nonstop and direct flights.
In travel terminology, a nonstop flight is exactly what it sounds like it is – a flight from Point A to Point B that doesn’t make any stops. A direct flight normally means that the flight makes an intermediate stop, usually for refueling on long-haul routes. For example, Singapore Airlines operates two daily flights between San Francisco and Singapore, stopping in either Seoul or Hong Kong. However, if you search for those flights on fly.com, they appear to be nonstop:
A more serious issue is that there is a second definition of a direct flight, and that would be a series of flights marketed with a single flight number…but that still involve a change of planes. Many US airlines are guilty of this deceptive practice, which is nothing new and has been around for many years, long before fly.com was ever launched.
For example, United Airlines markets flight UA 972 as a “direct” flight from San Francisco to Brussels, despite the fact that it not only makes a stop in Chicago, but actually requires a change of planes there. However, on fly.com it appears that the flight is nonstop:
If you check out the same flight on United’s website directly, they do advise of the plane change:
There are numerous other examples for the above scenario, some of which do involve actual plane changes and others that make stops (ie: DEN-NRT UA 875 which actually stops in Seattle, but appears as nonstop on fly.com).
It appears that fly.com is interpreting all single flight numbers to be nonstop, which is a pretty major technology fail. The good news for fly.com is that since they are simply a metasearch site that doesn’t actually sell tickets, all of their actual fulfillment partners that do actually sell tickets appear to have their houses in order, and do show the actual stopover information once you’ve clicked through to them. However, speaking as someone who has himself worked for one of those fulfillment partners (vayama.com), I can speak from experience that consumers are unlikely to notice the issue until after they’ve purchased their tickets, at which point it may be too late to make any changes without incurring hefty cancellation or reissue fees.
Ultimately it is indeed the consumer’s responsibility to double-check their information before purchasing, but in cases like this they are led to the purchase process under false pretenses. That’s where an inevitable, endless and vicious cycle of finger-pointing begins. The consumer doesn’t care who’s wrong, and they usually wind up blaming the fulfillment agency. The fulfillment agency (rightfully) blames fly.com, who are really powerless to do anything after the sale. So the consumer is unhappy, fly.com’s partners are unhappy (and are the ones who usually must bear the brunt of the consumer’s frustration), and fly.com basically gets off scot free.
The fact that these bugs have been out there for as long as they have indicates that either nobody else has bothered to report them (which means that fly.com’s user base is what analysts would refer to as “statistically insignificant”), or that fly.com is aware of the problems, but simply hasn’t gotten around to fixing them yet. In either scenario, it’s not impressive.
In full disclosure, in addition to formerly working at vayama.com, I also worked at Travelzoo. One of the reasons that I like fly.com is because it does work with international discount sites such as vayama, Airfare.com and CheapoAir. This makes them a much better source for international searches as opposed to Kayak, whose exclusive OTA agreement with Orbitz prevents them from showing anything other than published fares. While Orbitz and discount sites such as vayama might often have the exact same fares for international routes (which means that Kayak and fly.com would both as well), there are several instances where the discount sites (and thus results on fly.com) would be cheaper. These include (but are not limited to) international one-way flights, or for long-term stays (ie: over 30 days, over 6 months, or whatever the current market standard is on published fares for a specific route).
Anyway, because of my own working experience with companies like vayama and Travelzoo, I am admittedly more critical of them. However, I also want to see them succeed, which is why I find bugs like this to be so disappointing…yet unfortunately not at all surprising.


