jayunited wrote:On yesterday June 11, at DEN where the system is fully deployed UA's D:0 was 63%, A:14 was 89.4%, completion rate was 100%. For UAX the D:0 number still hasn't been published, but the A:14 was 84.5% and the completion rate was 99.6%.
If you consider a 63% D0 great, then there is a problem. Given the UAX number wasn't published but keeping in line with the A14; it was probably around 60%. A 60-63% D0 in a hub without any WX yesterday isn't something to brag about. Its not terrible but it indicates that there were still a good handful of problems in getting aircraft out on-time.
jayunited wrote:Again ORD's number which are terrible was caused by the all day ATC ground delay program do high winds. However DEN's numbers which was fully within UA's control are great and this was with over 500 departures and ConnectionSaver being fully deployed. So I would say UA has done their homework and covered all their bases and the over 14,400 connection passengers who would have misconnected over the previous 4 months at DEN alone is proof ConnectionSaver is working.
14k passengers isn't proof at all. That averages out to 120 passengers a day but you have to compare that to the prior metrics. If Feb-May 2018 the old system held for 15k passengers, then that would show ConnectionSaver isn't doing anything any better than before. 120 pax/day also isn't much when you think that most holds are between 5-10 passengers so that would equate to 12-24 (out of 450+) per day which is probably what UA was already holding for.
As mentioned, this is nothing new when it comes to deciding to hold; the only new piece is the customer guidance which will probably improve A14 on short holds.