Reply to thread

Maybe the fact that ANA is happy to link from incoming international VA flights, onto ANA dom flights to put pax onto them (ANAdom) could work in VA's favour, revenue sharing wise.

The HK uprising, if we can call it that, and the Coronavirus also did not help VAi's case flying into HKG.

Because with HK flights, once you arrive into HKG, thats it, you will be using ground transport after that, but with VA's HND slot, there is still money to be earnt by pax going ANA dom, all the better if the pax is able to buy the ANA dom tix at the same time, with the same PNR, to onlink from VA straight onto ANA dom via the dedicated int to dom transfer, like what QF have at SYD from T1 to T3, via the internal roadway.

In the end tough, I am not sure where to put my support, for VA being very ambitious in flying internationally, far and wide.

Not forgetting what happened to AN as in Ansett, didn't they go to HKG, and Japan too, and they had their deep link to SQ and (Air)NZ, then (Air)NZ bit them, just like what (Air)NZ did to VA.

Granted that VA and (Air)NZ are still in a code share agreement with (Air)NZ dom within NZ, no FF points earnt or course, just VA carrying the (Air)NZ flight # in the same PNR as incoming VAi flight.

In the end, I don't know, though, bravo VA for going far and wide, and giving it a try, or are they just throwing good money after bad.

Should they (VA) just in the end, put all its emphasis on Aust dom flights only, as a rival to QF.

Will the VA HND flights, last or not, (financially wise), 6 months/12/18 months?

Edit: > If you go to the ANA Aust website, and type in Au - Japan flights, you will see that on the ANA website, where the flight compnay is VA, it already carries an NH flight number, to link flyers to PER/SYD.


Back
Top