FlyerTalk Forums - View Single Post - Boarding pass for connecting flight did not show updated schedule.

Nov 17, 2016 | 4:01 pm

#8

mduell

FlyerTalk Evangelist

Join Date: May 2007

Location: Houston

Programs: UA Plat, Marriott Plat

Posts: 13,321

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:

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

AC changed the schedule in August, and also dropped some days of the week that UA seems to have never picked up on:

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

I wouldn't be surprised if the GA confusion is because the flight didn't operate yesterday.

Reply