Originally Posted by
PLeblond
Well as I say in french... Noui. It would be logical that AC has data on every query into their website and can extrapolate a certain level of demand based on that. Secondly, one would also assume that AC has access to data from sites like GF and other ticket agglomerators to use as a tool for planning new routes and adjusting potential demand (higher and lower)on existing routes – along with their own internal data.
There are tools route managers and revenue management likely with the all-encompassing AI to optimise loads and RASM.
Bottom line is that I highly doubt AC looks at routes where J cabins are constantly full and say… Bah… that’s fine. We don’t need a bigger J cabin there.
So… I’m leaning more towards AC, their RM people and all the available data versus 1 person’s data points.
I have no problem with you stating something to the effect of “I wish AC would have more J seats on the routes I regularly fly” versus saying “They should”. Semantics? Perhaps, but I assume they are better equipped, have more and better information and a team trained for these decisions.
You seem to be assuming that they've looked at all their data and decided they don't need more J on the route.
I'm not saying that at all. I'm saying they don't have anything in their fleet for this. The only way they can add more J "tomorrow" is by adding a ton of Y, which they do
not need.
I know for a fact they have considered sub-fleets with different J/Y ratios. That gets complicated. But the fact that it hasn't been done doesn't mean they shouldn't (or that they don't want to), and I suspect the XLR will play a part in making something like this happen.