Quote:
Originally Posted by Johnny Aussie
Yes, I saw that comment.
People forget, and yes we have brought this up many times before.
Transport Canada (Government of Canada) tends to grant access based on O&D and not based on transfer traffic to a particular country.
If you all recall, and I'm too lazy to dig it up again, somebody posted the market size of YVR-IST in comparison to other North American markets. The local O&D was tiny. However, the potential for transit passengers was much larger of course. Same argument against EK and EY. The local market from YVR-DXB or YVR-AUH is minute. But, like IST, the amount of potential transit traffic is so much larger. That's the crux of the Government's approach. Like it or lump it... that's their model.
So to summarise, Transport Canada would be unlikely to grant further access to Turkish despite the lobbying of various groups (eg Turkish Airlines and local Turkish community groups). Unless someone can prove the YVR-IST market is large enough to support a direct service based on the local market only..... Even though they are a Star Alliance member, Air Canada may also lobby against further access as it may (will) hurt their business model. It has nothing to do with favouring YYZ or YUL, this has more to do with Air Canada... their global hub just happens to be at YYZ.
|
Thanks, Johnny. But an example I donot quite understand, in keeping with what you said about O/D being tiny:
at Seattle, EK flies to DBX TWICE A DAY. Surely that is mostly connecting traffic. So how come Seattle (a bit bigger, a bit $$$$er than Vancouver I admit)
can support 2 flights per day to the Middle East?
And Vancouver, not at all?
There is a huge contrast and discrepency somewhere. Could you venture an explanation? EK flies to other US cities, too, and Seattle doesn't have to change at JFK or ORD.
Mathematically, what is happening? / Thanks again