I'm speculating, but I would say that the programmer accidently encoded the arrival time to match the user's time zone instead of just leaving it alone.
In sites that operate across different time zones, it's customary to match the user's time zone using user location (via address if logged in or IP address if not). Programmers create a single function that can be used on any time throughout the website. When time is used, it pulls the time of the server and offsets it via that function.
Airlines websites add complexity because departure/arrival times are always listed in the local time zone of the airport. Again I'm guessing, but perhaps the programmers accidentally added the time zone offset function to the arrival time.
Originally Posted by
chrismk
It has to be website related? I get these results in Firefox and Chrome on 3 different devices - 2 desktops (W10) and a laptop (W7).
BUT when I perform the search on the laptop using an old Internet Explorer it's fine!
As random as that seems, it makes sense. Websites are often programmed using multiple computing languages. Some languages play well with some browsers and not with others.
Since Internet Explorer (IE) is not considered a "modern" browser, programmers will no longer check it to ensure it's presenting information correctly. Although, in this example, it's a little backwards. IE seems to be correct only because it's failing to properly work with whatever time zone function the programmers accidentally added to the arrival time.
(I hope that made sense.)