Boarding pass for connecting flight did not show updated schedule.
Nov 17, 2016, 2:35 pm
#1
Original Poster
Join Date: Oct 2003
Location: Washington, DC
Programs: UA 4 million miler; Hilton goldMarriott platinum elite
Posts: 63
Boarding pass for connecting flight did not show updated schedule.
Checked in this morning at IAD with my wife to fly on UA389 to Seattle connecting to UA8244, an Air Canada Express flight to YVR.
When we got to Seattle we were told that the connecting flight does not operate today.
How can UA issue boarding passes for a non-existent flight?
When we got to Seattle we were told that the connecting flight does not operate today.
How can UA issue boarding passes for a non-existent flight?
Nov 17, 2016, 2:38 pm
#2
FlyerTalk Evangelist
Join Date: Nov 2014
Location: MSP
Programs: DL PM, UA Gold, WN, Global Entry; +others wherever miles/points are found
Posts: 14,384
It seems to have flown: https://flightaware.com/live/flight/UAL8244
Nov 17, 2016, 2:42 pm
#3
Join Date: Nov 2010
Programs: UA Silver, Marriott Gold, Hilton Gold
Posts: 74
Who told you that it doesn't operate today? It appears on both Flight Aware and United status pages.
More importantly, with a scheduled arrival time of 11:39AM for UA389 and a scheduled departure time of 11:50AM for UA8244, why did UA even allow this to ticket? Is this an allowable connection time? Were these on separate tickets perhaps?
More importantly, with a scheduled arrival time of 11:39AM for UA389 and a scheduled departure time of 11:50AM for UA8244, why did UA even allow this to ticket? Is this an allowable connection time? Were these on separate tickets perhaps?
Nov 17, 2016, 2:59 pm
#4
Original Poster
Join Date: Oct 2003
Location: Washington, DC
Programs: UA 4 million miler; Hilton goldMarriott platinum elite
Posts: 63
Who told you that it doesn't operate today? It appears on both Flight Aware and United status pages.
More importantly, with a scheduled arrival time of 11:39AM for UA389 and a scheduled departure time of 11:50AM for UA8244, why did UA even allow this to ticket? Is this an allowable connection time? Were these on separate tickets perhaps?
More importantly, with a scheduled arrival time of 11:39AM for UA389 and a scheduled departure time of 11:50AM for UA8244, why did UA even allow this to ticket? Is this an allowable connection time? Were these on separate tickets perhaps?
First I knew something was wrong was seeing the global services agent at the aircraft door in Seattle with our name on a sign.
So maybe the flight existed but it did not depart on the schedule shown on either our reservation or our boarding passes.
UA tried to get us on the 11:50 departure but could not get checked bags rescreened in time to make the flight so we are spending a few hours in United Club, waiting for a much later flight.
Nov 17, 2016, 3:01 pm
#5
Join Date: Apr 2015
Location: YVR
Programs: UA Premier Platinum
Posts: 3,759
I guess the schedule change never showed up in UA's systems under the codeshared flight number. I have seen this a number of times on YVR<>SFO. UA shows completely wrong times for codeshared AC flights even up to the day of departure and allows booking of impossible connections as a result. Lesson learned: always check the operating airline's website when booking interline or codeshare connections with UA.
Nov 17, 2016, 3:18 pm
#6
Moderator: Budget Travel forum & Credit Card Programs, FlyerTalk Evangelist
Join Date: Aug 2002
Location: YYJ/YVR and back on Van Isle ....... for now
Programs: UA lifetime MM / *A Gold
Posts: 14,426
I have seen this a number of times on YVR<>SFO. UA shows completely wrong times for codeshared AC flights even up to the day of departure and allows booking of impossible connections as a result. Lesson learned: always check the operating airline's website when booking interline or codeshare connections with UA.
I've never bothered to check AC for my many YVR/YYC-YYJ flights connecting from UA (and vv) and never had a problem. From SFO I've always flown UA to YYJ or YVR so have no experience there with AC.
Nov 17, 2016, 3:28 pm
#7
Original Poster
Join Date: Oct 2003
Location: Washington, DC
Programs: UA 4 million miler; Hilton goldMarriott platinum elite
Posts: 63
I guess the schedule change never showed up in UA's systems under the codeshared flight number. I have seen this a number of times on YVR<>SFO. UA shows completely wrong times for codeshared AC flights even up to the day of departure and allows booking of impossible connections as a result. Lesson learned: always check the operating airline's website when booking interline or codeshare connections with UA.
Nov 17, 2016, 4:01 pm
#8
FlyerTalk Evangelist
Join Date: May 2007
Location: Houston
Programs: UA Plat, Marriott Gold
Posts: 12,686
UAL8244, a codeshare on ACA8122, operated as JZA122, certainly did operate today.
Indeed the departure time moved by about an hour sometime in September, when the aircraft type changed from the 300 to the 400:
AC changed the schedule in August, and also dropped some days of the week that UA seems to have never picked up on:
I wouldn't be surprised if the GA confusion is because the flight didn't operate yesterday.
Indeed the departure time moved by about an hour sometime in September, when the aircraft type changed from the 300 to the 400:
Code:
schedule | flight | orig | dest | eqp | departs | from | to | days ------------+--------+------+------+-----+----------+------------+------------+--------- 2016-01-01 | UA8244 | SEA | YVR | DH3 | 12:55:00 | 2016-11-06 | 2016-12-05 | MTWRFSU 2016-02-01 | UA8244 | SEA | YVR | DH3 | 12:55:00 | 2016-11-06 | 2016-12-05 | MTWRFSU 2016-03-01 | UA8244 | SEA | YVR | DH3 | 12:55:00 | 2016-11-06 | 2016-12-05 | MTWRFSU 2016-04-01 | UA8244 | SEA | YVR | DH3 | 12:55:00 | 2016-11-06 | 2016-12-05 | MTWRFSU 2016-05-01 | UA8244 | SEA | YVR | DH3 | 12:55:00 | 2016-11-06 | 2016-12-05 | MTWRFSU 2016-06-01 | UA8244 | SEA | YVR | DH3 | 12:55:00 | 2016-11-06 | 2016-12-05 | MTWRFSU 2016-07-01 | UA8244 | SEA | YVR | DH3 | 12:55:00 | 2016-11-06 | 2016-12-05 | MTWRFSU 2016-08-01 | UA8244 | SEA | YVR | DH3 | 12:55:00 | 2016-11-06 | 2016-12-05 | MTWRFSU 2016-09-01 | UA8244 | SEA | YVR | DH3 | 12:55:00 | 2016-11-06 | 2016-12-05 | MTWRFSU 2016-10-01 | UA8244 | SEA | YVR | DH4 | 11:50:00 | 2016-10-30 | 2016-12-18 | MTWRFSU 2016-11-01 | UA8244 | SEA | YVR | DH4 | 11:50:00 | 2016-11-10 | 2016-11-21 | M WRFSU
Code:
schedule | flight | orig | dest | eqp | departs | from | to | days ------------+--------+------+------+-----+----------+------------+------------+--------- 2016-01-01 | AC8122 | SEA | YVR | DH3 | 12:55:00 | 2016-11-06 | 2016-12-05 | MTWRFSU 2016-02-01 | AC8122 | SEA | YVR | DH3 | 12:55:00 | 2016-11-06 | 2016-12-05 | MTWRFSU 2016-03-01 | AC8122 | SEA | YVR | DH3 | 12:55:00 | 2016-11-06 | 2016-12-05 | MTWRFSU 2016-04-01 | AC8122 | SEA | YVR | DH3 | 12:55:00 | 2016-11-06 | 2016-12-05 | MTWRFSU 2016-05-01 | AC8122 | SEA | YVR | DH3 | 12:55:00 | 2016-11-07 | 2016-12-05 | MT R 2016-06-01 | AC8122 | SEA | YVR | DH3 | 12:55:00 | 2016-11-07 | 2016-12-05 | MT R 2016-07-01 | AC8122 | SEA | YVR | DH3 | 12:55:00 | 2016-11-07 | 2016-12-05 | MT R 2016-08-01 | AC8122 | SEA | YVR | DH3 | 12:55:00 | 2016-11-07 | 2016-12-05 | MT R 2016-09-01 | AC8122 | SEA | YVR | DH4 | 11:50:00 | 2016-11-07 | 2016-12-05 | MT R 2016-10-01 | AC8122 | SEA | YVR | DH4 | 11:50:00 | 2016-11-07 | 2016-12-05 | MT R 2016-11-01 | AC8122 | SEA | YVR | DH4 | 11:50:00 | 2016-11-17 | 2016-11-22 | MT R
Nov 17, 2016, 4:09 pm
#9
Join Date: Jan 2009
Location: LHR (sometimes CLE, SFO, BOS, LAX, SEA)
Programs: UA 1K
Posts: 5,892
I guess the schedule change never showed up in UA's systems under the codeshared flight number. I have seen this a number of times on YVR<>SFO. UA shows completely wrong times for codeshared AC flights even up to the day of departure and allows booking of impossible connections as a result. Lesson learned: always check the operating airline's website when booking interline or codeshare connections with UA.
Nov 17, 2016, 5:48 pm
#11
Join Date: Dec 2013
Location: dark side of the moon
Programs: papa card, UA 1K
Posts: 707
I guess the schedule change never showed up in UA's systems under the codeshared flight number. I have seen this a number of times on YVR<>SFO. UA shows completely wrong times for codeshared AC flights even up to the day of departure and allows booking of impossible connections as a result. Lesson learned: always check the operating airline's website when booking interline or codeshare connections with UA.
Nov 18, 2016, 6:58 pm
#13
Join Date: Apr 2015
Location: YVR
Programs: UA Premier Platinum
Posts: 3,759
It most recently happened to me for November 3rd, I had YVR-SFO-LAX (UA ticket) booked and the YVR-SFO was AC metal codeshared by UA. I called AC to select my seat two weeks before the flight and the agent said "do you realize you have negative 15 minutes connecting time?". Everything still looked OK on UA.com but there had been a schedule change to the AC flight months earlier that was never picked up by United. But it's far from the first time I have seen major discrepancies between the published times of the same flights between UA and AC on this route.
Nov 19, 2016, 2:18 am
#14
Join Date: Jul 2007
Location: San Francisco/Sydney
Programs: UA 1K/MM, Hilton Diamond, Marriott Something, IHG Gold, Hertz PC, Avis PC
Posts: 8,147
Based on who's "T" ? According to the OP :
So based on the boarding pass, issued by United, they were clearly ready to present themselves at T-15min.
So based on the boarding pass, issued by United, they were clearly ready to present themselves at T-15min.
Nov 19, 2016, 3:31 am
#15
Join Date: Mar 2005
Programs: fwp blood diamond, dykwia uranium
Posts: 7,251
what'? that's ridiculous. you can fly ahead of your bags, (and i'd say it's fair ua owes you delivery in yvr) so i have no clue why they'd hold you up because of bag rescreening. plus i thought bag re-screening only applies to inbound cnx from canada.
