Delay due to loading luggage; missed connection
Aug 19, 2012, 9:25 pm
#16
Original Poster
Join Date: Dec 2009
Location: WAS
Posts: 3,006
It's a glitch. Back in June all of our delay codes switched to new ones. I don't think the system to decode those has been updated, as things from ramp delays to slow boarding will show up as "Airport Conditions."
It's not like UA is intentionally mis-coding delays, the system just isn't interpreting them right.
If the flight is the one I think it is (1234), the delay was coded to late inbound aircraft, and load planning/weight and balance. So rest assured, it's not anything malicious.
It's not like UA is intentionally mis-coding delays, the system just isn't interpreting them right.
If the flight is the one I think it is (1234), the delay was coded to late inbound aircraft, and load planning/weight and balance. So rest assured, it's not anything malicious.
Aug 19, 2012, 9:30 pm
#17
FlyerTalk Evangelist
Join Date: Aug 2002
Location: Bay Area, CA
Programs: UA Plat 2MM; AS MVP Gold 75K
Posts: 35,067
It's a glitch. Back in June all of our delay codes switched to new ones. I don't think the system to decode those has been updated, as things from ramp delays to slow boarding will show up as "Airport Conditions."
It's not like UA is intentionally mis-coding delays, the system just isn't interpreting them right.
If the flight is the one I think it is (1234), the delay was coded to late inbound aircraft, and load planning/weight and balance. So rest assured, it's not anything malicious.
It's not like UA is intentionally mis-coding delays, the system just isn't interpreting them right.
If the flight is the one I think it is (1234), the delay was coded to late inbound aircraft, and load planning/weight and balance. So rest assured, it's not anything malicious.
While the intent may not be malicious, lack of corrective action on a known item after several months may be negligent.
The delay codes were changed in June. If the systems were tested correctly, end to end, there would have been no visible impact. It's sad that front-liners and customers have to know these things more than 2 months post implementation.
