Time discrepancy in flight details
#1
Original Poster
Join Date: Nov 2010
Location: Milton Keynes
Programs: BA Blue
Posts: 373
Time discrepancy in flight details
Good day. I'm looking up flights and get the usual list of results.
When I click on Details for any flight the departure and arrival times are advanced 8 hours!
I'm in the UK, where there is a 8 hour time difference, but what is happening?!
When I click on Details for any flight the departure and arrival times are advanced 8 hours!
I'm in the UK, where there is a 8 hour time difference, but what is happening?!
#2
FlyerTalk Evangelist
Join Date: Aug 2017
Programs: AS 75K, DL Silver, UA Platinum, Hilton Diamond, Hyatt Discoverist, Marriott Platinum + LT Gold
Posts: 10,329
It may be easier if you can share an example for us to reference and provide feedback.
#3
Original Poster
Join Date: Nov 2010
Location: Milton Keynes
Programs: BA Blue
Posts: 373
PDX-DEN on 10 Aug next year, though it doesnt matter which flights/dates are entered.
The non stop 616 departs at 10.45am. When I click on details it says 6.45pm. Ive now just realised it is also saying 6.45 on the following day!
The non stop 616 departs at 10.45am. When I click on details it says 6.45pm. Ive now just realised it is also saying 6.45 on the following day!
#6
Original Poster
Join Date: Nov 2010
Location: Milton Keynes
Programs: BA Blue
Posts: 373
Yes, it would seem to be something on my computer.
I've cleared cookies and cache in the browser, but I've now noticed if I select a date and press submit at the beginning of the booking process, the results are for the previous day!
So at least when I click on details, the date is correct :-)
I've cleared cookies and cache in the browser, but I've now noticed if I select a date and press submit at the beginning of the booking process, the results are for the previous day!
So at least when I click on details, the date is correct :-)
#7
FlyerTalk Evangelist
Join Date: Aug 2017
Programs: AS 75K, DL Silver, UA Platinum, Hilton Diamond, Hyatt Discoverist, Marriott Platinum + LT Gold
Posts: 10,329
#9
FlyerTalk Evangelist
Join Date: Nov 2009
Location: SEA (the REAL Washington); occasionally in the other Washington (DCA area)
Programs: DL PM 1.57MM; AS MVPG 100K
Posts: 21,308
I noted a similar discrepancy (3 hours) earlier this month, and it’s reappearing today (looking randomly at SEA<>LAX flights in mid May)
#10
Join Date: May 2012
Location: DCA, lived MCI, SEA/PDX,BUF (born/raised)
Programs: Marriott (Silver/Gold), IHG, Carlson, Best Western, Choice( Gold), AS (MVP), WN, UA
Posts: 8,629
I dont get that when I book flights.
Ifi go and look at schedule of games on espn it adjusts to the time zone Im physically in via my connection
#11
Join Date: Mar 2017
Location: British Columbia
Programs: AS MVPG100K, Marriott Marriott Titanium Elite, Hilton Gold
Posts: 7,263
I had a similar occurance with an itinerary in early November. I was in the Eastern Time Zone and flight times for segments in the PST were shown in EST instead of PST. I also had segments with Departure & Arrival times the same. It corrected itself.
James
James
#12
Original Poster
Join Date: Nov 2010
Location: Milton Keynes
Programs: BA Blue
Posts: 373
Search Criteria
Search Results
Flight Details
This is what is happening.
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!
#13
Join Date: Mar 2008
Location: Fort Lauderdale, FL
Posts: 3,360
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.
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.)
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.
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.)
#15
FlyerTalk Evangelist
Join Date: Nov 2009
Location: SEA (the REAL Washington); occasionally in the other Washington (DCA area)
Programs: DL PM 1.57MM; AS MVPG 100K
Posts: 21,308
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.
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.)
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.
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.)