Originally Posted by
Nazdoom
Being a points booking doesn't relieve the airline of the responsibility of rebooking a missed connection that is caused due to a late inbound, so long as it is the same ticket and not due to some pax error (e.g., falling asleep on the toilet). When it's under airport control, rebooking by the carrier is not limited to available last-minute points inventory as would be an ordinary AP flight change but any space or routing the airline has available in the same class of service (or in the event flights are all full due to some special circumstances, e.g., a multi-day ice storm, then one may agree to a lower class of service in order to get an earlier flight if preferable).
I'm going to address those two bolded points.
1. "under airport control" is a ticketing term, and means very different things for different airlines. You can book a flight for 11 months from now and have it under airport control until you check in (at which point it flips to "checked in"). Different airlines have different thresholds for when something goes from a schedule change to IRROPS, but it's generally in the 2-14 day range.
Also, different airlines have a different willingness to deal with this. AC, if an AC flight has issues, is very willing to do whatever they can. Meanwhile, you don't have to travel far in *A world to find other experiences:
https://www.flyertalk.com/forum/unit...rline-biz.html
2. "the airline has available"... I'd actually be cautious with that. I've been rebooked by AC from NH F to NH F on an Aeroplan ticket, where the only reason I was able to actually fly on the rebooked F was because I was SE with concierge access. Otherwise it would have been J. SQ (which may be relevant due to the SIN destination) is much worse. Good luck getting them to accept a coupon for something where they don't feel they've been properly compensated.
And since it's CPH-SIN, what happens when SK is no longer in *A?
Membership in *A (with the exception of SQ) requires them to accept any *A coupon for the same class of service in the event of IRROPS. Most members are fine with that. But non-*A (and SQ) have no requirement to do that.