Originally Posted by
emcampbe
So exactly what I was talking about. Married segment inventory is high (U), while doing as a multi-city should produce a T, assuming a filed fare in that bucked (unless its cheaper to do a split fare - though it's often not). Again, what I constantly used to see...but again, I used to look up multi-city's as UA, especially in the early post-merger years was horrible about bringing up reasonable connections that should have been options but didn't show.
I think there used to be a IAH-YMM flight (someone more knowledgeable than me, and who maybe used to fly up that way...ever...probably could verify). Believe it got canned when there was a contraction in IAH due to slowing oil industry. Forget when exactly that was. 2016'ish? 2018'ish?
As it turns out, UA does not actually have any fares filed on VCT-YQU (not too surprisingly). In this case, the pricing involves separate fares on each segment in both cases. But whether or not there are through O&D fares on a route, pricing is "supposed" to use married segment inventory to choose fares on itin even when multiple fares are involved. Clearly that is not happening with multi-city searches.