Moderators: richierich, ua900, PanAm_DC10, hOMSaR
bunumuring wrote:Hey guys,
Does anyone know if QF wil hold a public competition to name the second batch of Dreamliners like they did for the first batch? I know some of The eight names announced were not used and replaced by 'Yam Dreaming' and 'Jillaroo' ...perhaps the unused ones can be used this time around?
Cheers,
Bunumuring
QF754 wrote:NTLDaz wrote:qf2048 wrote:This has got me intrigued. All I can think of is Cobham. Don't forget how it worked out for Jetgo..
I'd love to see Airnorth expand into southern NSW. Maybe take on some of those old Jetgo routes? Think FC are doing okay with the Saabs.
This is intriguing- I took RE to possibly mean Regional Express. Bit extreme but they need to start thinking of SAAB replacements soon
I fly ZL regularly and the 340's are getting old. An E-jet may work on their heavier trafficked routes. I fly them to ONG 5 or 6 times a year. Has anyone else on here ever flown to ONG ?
I’m pretty sure the hint is suggesting that a previous E-jet operator is giving consideration to reintroducing the type. That narrows it down to VA, and probably VARA.
Maybe lower lease rates and lower VARA operating costs mean that E-jets are being looked at as a viable long-term replacement for the F100s on regional routes? I read on another thread that JetBlue are due to return a large number of leased E-jets from 2020 onwards as new A220s are delivered...
Ryanair01 wrote:tullamarine wrote:There isn't really room for automated bag drops. They have to share the terminal with Jetstar, Tiger, Rex and Fly Pelican. They really need their own terminal like QF has.
SYD T2 is operating way above the capacity it wa designed for when AN opened it nearly 20 years ago. It is felt most acutely at landside check-in and security but the terminal does struggle. There was a plan at one stage of doing an airside link between T3 and T2 which would potentially reduce congestion as some airlines could use the T3 check-in hall. Nothing has come of this; maybe it will change at the end of the QF lease of T3 at which time their exclusivity over that terminal will end and will probably move to a priority gate arrangement similar to what VA has in T2.
T3 opens up to other airlines this year, under a deal they did a few years back QF will keep priority access to 12 of 17 gates and 75% of check in desks until 2025. Most of the shop leases also end this year, so there might be some upgrades to the facilities on offer. I wondered if we might see Jetstar relocate to ease T2?
True, T2 landside is essentially as Ansett left it. What struck me is that the disruption seemed limited to VA and not the other carriers in T2.qf789 wrote:Ryanair01 wrote:Does anybody know what happened with the Virgin 'meltdown' in Sydney this week?
https://www.smh.com.au/national/nsw/i-expected-it-to-be-busy-but-wow-delays-at-sydney-airport-due-to-fog-20190102-p50p6i.html
I'm always cynical about these type of stories, but queuing out the door like that suggests something went pretty badly wrong.
VA had put out on social media that morning that delays were expected in both SYD and MEL as it was going to be particularly busy. The flight referenced in the article being VA555 was delayed for operational reasons. On top of that VA had to deal with a A332 at the wrong port after the red eye from PER diverted to MEL due to the fog in SYD. VA555 was operated by the inbound aircraft from HKG, with it only having just under 2 hours ground time, turning it around and add in it needed to be towed which could have been delayed to ATC it was an uphill battle to get the flight out of time. The displaced aircraft in MEL was ferried to SYD to operate the HKG flight which ended up with about a 3hr delay.
Interesting to know. Twitter videos seemed to show Jetstar just about coping, REX/Tiger desks coping but largely unstaffed and VA with queues out the door. I noticed somewhere it said they were queuing by departure time. I wondered if too many people turning up too early was a problem? I've known it when you need to ask pax who've arrived early to queue elsewhere, so that passengers for immediate flights can be processed. Certainly the number of desks VA has doesn't match their proportion of flights from T2, which would make that balance harder to achieve.
Hope there weren't too many people with connections in HKG!
SYDSpotter wrote:waoz1 wrote:Friend is currently on QF9
Last night in Perth apparently a few passengers were offloaded due to weight restrictions. She was one of them but was able to get a seat due to work commitments.
Were offerend Perth-Singapore-London in business if they went two days later.
Any ideas why it might be the case?
More fuel?
Stronger than normal headwinds? It looks like QF9 clocked in at 18hrs yesterday which seems above the normal flight time.
ben175 wrote:A friend of mine is flying QF12 JFK-LAX in February and his booking has just been changed to a 744 - is this a mistake?
ben175 wrote:A friend of mine is flying QF12 JFK-LAX in February and his booking has just been changed to a 744 - is this a mistake?
ben175 wrote:A friend of mine is flying QF12 JFK-LAX in February and his booking has just been changed to a 744 - is this a mistake?
HM7 wrote:Apologies for the triple post. My internet wasn’t working properly
aviationaware wrote:HM7 wrote:Apologies for the triple post. My internet wasn’t working properly
You must be on Belong as well then
With the A321LR replacing the 788 on some routes for JQ, where will the resulting slack be scheduled to? Are any details known yet?
jman wrote:aviationaware wrote:HM7 wrote:Apologies for the triple post. My internet wasn’t working properly
You must be on Belong as well then
With the A321LR replacing the 788 on some routes for JQ, where will the resulting slack be scheduled to? Are any details known yet?
That won't be announced until the end of the year for a start date of the flights mid 2020
getluv wrote:Looks like QF and CX will be expanding their code sharing agreement in a few months. QF has just filed a notice for CX to codeshare on QF services to Hong Kong from 31 March. I guess QF will also be code sharing on CX services.
Further to this, QF has also filed a notice requesting 400 seats to Korea with services operated by CX/KA.
smi0006 wrote:getluv wrote:Looks like QF and CX will be expanding their code sharing agreement in a few months. QF has just filed a notice for CX to codeshare on QF services to Hong Kong from 31 March. I guess QF will also be code sharing on CX services.
Further to this, QF has also filed a notice requesting 400 seats to Korea with services operated by CX/KA.
Interesting, I wonder if HU/HX and VA played into QF/CX hands by starting AU-HKG, enough completion to not pose a threat, but just enough to not worry the ACCC should QF and CX want to start to collaborate more and ultimately control capacity and pricing in the market ?
tullamarine wrote:smi0006 wrote:getluv wrote:Looks like QF and CX will be expanding their code sharing agreement in a few months. QF has just filed a notice for CX to codeshare on QF services to Hong Kong from 31 March. I guess QF will also be code sharing on CX services.
Further to this, QF has also filed a notice requesting 400 seats to Korea with services operated by CX/KA.
Interesting, I wonder if HU/HX and VA played into QF/CX hands by starting AU-HKG, enough completion to not pose a threat, but just enough to not worry the ACCC should QF and CX want to start to collaborate more and ultimately control capacity and pricing in the market ?
It is a codeshare not a JSA. Any attempt to collaborate on pricing or capacity would be illegal without JSA immunity and trigger multi-million dollar fines as well as potential loss of route rights.
Qantas94Heavy wrote:Note that codeshares can still be rejected if they would significantly reduce competition, such as with Qantas and Air Niugini: http://australianaviation.com.au/2018/0 ... r-niugini/
Having said that, there are already upcoming capacity reductions from both QF (747 -> 787) and CX (777 -> A330). This follows the 'price war' after VA introduced flights to HKG, where return fares below $500 were not that uncommon. (A couple of years ago, fares below $750 would be considered cheap already.)
getluv wrote:Looks like QF and CX will be expanding their code sharing agreement in a few months. QF has just filed a notice for CX to codeshare on QF services to Hong Kong from 31 March. I guess QF will also be code sharing on CX services.
Further to this, QF has also filed a notice requesting 400 seats to Korea with services operated by CX/KA.
aviationaware wrote:With the A321LR replacing the 788 on some routes for JQ, where will the resulting slack be scheduled to? Are any details known yet?
zkncj wrote:aviationaware wrote:With the A321LR replacing the 788 on some routes for JQ, where will the resulting slack be scheduled to? Are any details known yet?
Maybe USA mainland but via an secondary route e.g. MEL-AKL-LAX or MEL-NAN-LAX etc so not to directly compete with QF.
Pcoder wrote:zkncj wrote:aviationaware wrote:With the A321LR replacing the 788 on some routes for JQ, where will the resulting slack be scheduled to? Are any details known yet?
Maybe USA mainland but via an secondary route e.g. MEL-AKL-LAX or MEL-NAN-LAX etc so not to directly compete with QF.
Or could possibly go to LAS, which would be mainly leisure traffic and less likely to siphon business traffic from QF. Other destinations in Americas that JQ could do think about could also include SCL,EZE, MEX and YVR.
But I'm wondering do the JQ B788s have crew rests? (Lack of this would probably limit any Americas expansion)
Another destination that hasn't been mentioned here is CTS. I'm a little surprised QF group don't offer any seasonal flights here as many Australians go the Hokkaido for the winter.
With the extra B788s they will most likely increase trips to South East Asian Destinations (BKK, SGN, etc) and possibly explore a few other options people have highlighted.
bunumuring wrote:Hey guys,
There is the nose, cockpit and most of the forward fuselage of a Shorts 330 sitting on a custom built trailer in the Main Street of Burrawang, NSW, at the moment. It is bare metal with the remains of a curving red and white cheatline on it, that reminded me of the old American colourscheme. A yellow 'Ansett' labeled oki strap helped fasten it to the trailer.
I spoke with the owner this afternoon. He said that he had purchased it, and the rest of the fuselage, tail and wings, in Alice Springs. He apparently drives it to festivals and shows, the latest being in Werribee, Victoria.
If I could upload photos from my brand new iPhone, I would post photos of it..
Incidentally, through the now-opaque cabin Windows could clearly be seen an Ansett Air Freight container, other Ansett stuff and a large disco ball....
Cheers,
Bunumuring
Obzerva wrote:getluv wrote:Looks like QF and CX will be expanding their code sharing agreement in a few months. QF has just filed a notice for CX to codeshare on QF services to Hong Kong from 31 March. I guess QF will also be code sharing on CX services.
Further to this, QF has also filed a notice requesting 400 seats to Korea with services operated by CX/KA.
I'm not sure QF is going to apply to have a QF number on CX flights, I don't think that'd get past the ACCC.
I think it's CX applying on QF for HKG-MEL flights, where as in lieu, QF gets CX/KA flights to ICN (and presumably PUS and CJU).
I'm wondering why Korea.
Is QF's relationship ending with OZ?
or is it because the OZ codeshare only offers ICN vs other Korean ports.
It's just interesting because QF only started to work with CX with the first step being flights to India, and that was suspiciously timed around when 9W (QF's current codeshare to India) looks like it was about to fold. So CX was a bet hedge for 9W.
Makes me wonder why Korea and why now.
Qantas737 wrote:JQ 788s don't have crew rests and as far as I know are quite unique as a result.
zkncj wrote:Qantas737 wrote:JQ 788s don't have crew rests and as far as I know are quite unique as a result.
What does JQ do for crew resets on MEL-HNL then?
getluv wrote:Also it seems like Australian carriers do not have to apply to the IASC to put their code on HKG carriers. QF didn’t need approval from the IASC to codeshare on CX’s PER-HKG.
getluv wrote:Also it seems like Australian carriers do not have to apply to the IASC to put their code on HKG carriers. QF didn’t need approval from the IASC to codeshare on CX’s PER-HKG.
SCFlyer wrote:QF754 wrote:NTLDaz wrote:
This is intriguing- I took RE to possibly mean Regional Express. Bit extreme but they need to start thinking of SAAB replacements soon
I fly ZL regularly and the 340's are getting old. An E-jet may work on their heavier trafficked routes. I fly them to ONG 5 or 6 times a year. Has anyone else on here ever flown to ONG ?
I’m pretty sure the hint is suggesting that a previous E-jet operator is giving consideration to reintroducing the type. That narrows it down to VA, and probably VARA.
Maybe lower lease rates and lower VARA operating costs mean that E-jets are being looked at as a viable long-term replacement for the F100s on regional routes? I read on another thread that JetBlue are due to return a large number of leased E-jets from 2020 onwards as new A220s are delivered...
Can't see the VA group going down that path again considering reading so many complaints about the ongoing operational costs of the E190s over the years, despite it being a favourite with passengers.
My tip would be on sourcing used A319s and perhaps more A320 being transferred from the TT operation (as used 737s are transferred from VA mainline to TT).
qf789 wrote:Latest on WIFI on both QF & VA
https://www.ausbt.com.au/qantas-virgin- ... ource=hero
Both have 42 737's with WIFI installed, however I am pretty sure VA have more than 42
openskies88 wrote:qf789 wrote:Latest on WIFI on both QF & VA
https://www.ausbt.com.au/qantas-virgin- ... ource=hero
Both have 42 737's with WIFI installed, however I am pretty sure VA have more than 42
As at 20 December, 56 VA B737’s are fitted with wifi (rego’s if anyone is interested):
YIF, YIG, YFW, YVD, YIE, YIR, YIL, YIY, YIS, YIO, YIU, YWD, YIV, YFP, YFQ, YFS, YFR, YFT, YFU, YFG, YFV, YFJ, YFN, YFI, YVC, YID, YFL, YFY, VUW, YIB, YIQ, YIJ, YFE, VUR, VUS, BZG, YWE, YIW, YIZ, YIM, YIT, YIH, YFX, VUU, YIA, VUQ, VUO, YWA, VOO, VOP, YFK, YFF, VUH, VUT, YFH, YFC
All Yxx prefix registrations are the newer BSI interiors, the rest (Vxx and BZG) are standard NG.
qf2220 wrote:getluv wrote:Also it seems like Australian carriers do not have to apply to the IASC to put their code on HKG carriers. QF didn’t need approval from the IASC to codeshare on CX’s PER-HKG.
Perhaps the approvals for that were already there in the previous IASC determinations but QF/CX had not activated the services yet?
SCFlyer wrote:* One of VA's shareholders (possibly HNA) selling out before the end of the year - but stake may be to (dark-horse) China Eastern, perhaps influenced by both the Chinese Government and MU shareholder/VA USA JV partner - DL.
* EY announcing divesting VA before the 2019 year ends, stake following HNA sell-off to MU. DL and NH (Blue Swan Daily September 2018 dark-horse) announced as the potential suitors.
SCFlyer wrote:SCFlyer wrote:* One of VA's shareholders (possibly HNA) selling out before the end of the year - but stake may be to (dark-horse) China Eastern, perhaps influenced by both the Chinese Government and MU shareholder/VA USA JV partner - DL.
* EY announcing divesting VA before the 2019 year ends, stake following HNA sell-off to MU. DL and NH (Blue Swan Daily September 2018 dark-horse) announced as the potential suitors.
Looks like there's financial trouble for one of HNA's subsidiaries with news that they may possibly be filing directly for liquidation. (not sure if they officially offloaded HX/UO yet)
https://www.scmp.com/news/hong-kong/tra ... gency-plan
Going bold with the prediction that MU may be the bidder of HNA's 19.8% stake in VA later in the year, perhaps under the direction of both the CCP and DL.
Both DL and MU may keep an eye on the EY stake and EY's continual financial woes towards the end of the year. Should DL be the bidder of the EY stake in very late 2019/early 2020, it would give the Skyteam carriers a 40% stake in VA.
This would leave SQ's (Star) 20% stake and Nanshan's (unaligned) 20% stake, along with Branson's 10% stake. With news last year of SQ putting part of the blame for their profit downturn in the last quarter on their VA stake, I don't expect SQ to be interested in any further VA stake (nor sell out).
Also with Branson still owning a minority stake in VS (where VS is also majority owned by SkyTeam carriers), A combined 50% stake (MU, DL, Branson) it may also be enough for VA to form more partnerships with more SkyTeam carriers in late 2019/early 2020 without actually joining SkyTeam itself. While still maintaining their codeshare agreement with SQ for South East Asia and some European destinations.
RyanairGuru wrote:SCFlyer wrote:.
This entire post ignores the fact that MU has a JBA with QF.