23 hours ago, Kopteeni said:

That's what the Airbus is all about. Reduce the workload, reduce the risks. That's why the procedure where you explicitly ditch the autothrust sounds outlandish.

There are quite a few more airlines that either do not use autothrust on landing or leave it to the pilot's discretion. In any case, you'll have to discuss that with this airline's flight standards department. ;)

16 minutes ago, threegreen said:

 

There is nothing hard to believe about it. Airlines have different SOPs, what airline A does isn't always the same that airline B does. Delta may leave autothrust on while another airline uses the aforementioned procedure while some other airlines leave it to the pilots to decide on a case by case basis. There can be radical differences between airlines and manufacturer SOPs.

You quoted me totally out of context, and it makes zero sense. 

1 minute ago, Bobsk8 said:

You quoted me totally out of context, and it makes zero sense. 

Kopteeni posted about the procedure being different from Airbus SOPs to which you replied you find it hard to believe and how the Delta check airman said something different.

No idea how my response is out of context or where you think a lack of sense is.

1 minute ago, threegreen said:

Kopteeni posted about the procedure being different from Airbus SOPs to which you replied you find it hard to believe and how the Delta check airman said something different.

No idea how my response is out of context or where you think a lack of sense is.

I was stating that I found it hard to believe and was agreeing with the poster, that some airline SOP knew more about flying the Airbus, than Airbus did. 

1 hour ago, sonny147 said:

hover over the knob and you see either a small up arrow or down arrow to pull left click down to pull thats if you have settings to "lock" if legacy its different , sorry iam landing

I've tried Lock, & Legacy.

Neither let me switch to LNAV, but I may not have properly programmed the MCDU & actually have a flight plan loaded, so that might be the issue.

T45

8 minutes ago, Bobsk8 said:

I was stating that I found it hard to believe and was agreeing with the poster, that some airline SOP knew more about flying the Airbus, than Airbus did. 

Yes and that's what I replied to...

Again, many airlines have SOPs that, while based on the manufacturer SOPs, differ in some or more areas from the manufacturer's and there are some airlines that even have very unique SOPs, like that big European low cost carrier flying 737s, for example. Manufacturer SOPs aren't strict, compulsory rules and when an airline's SOPs differ it's so to cater to their own needs and policies with a good reason rather than some airline thinking they know more about the plane than the manufacturer.

Just updated. Seems fine except landing. As bad as before the update with 3 kts....and uncontrolled after touchdown.

16 minutes ago, miguelpp said:

Seems fine except landing. As bad as before the update with 3 kts...

Try flying the approach 140 kts faster then! 😄

Don't understand what you mean by "with 3 kts". I think this is a good hotfix after a great update.

26 minutes ago, miguelpp said:

Just updated. Seems fine except landing. As bad as before the update with 3 kts....and uncontrolled after touchdown.

Watch you don't have the tiller operational on landing, that will swing you straight off every time.

1 hour ago, threegreen said:

There are quite a few more airlines that either do not use autothrust on landing or leave it to the pilot's discretion. In any case, you'll have to discuss that with this airline's flight standards department. 😉

Thanks for your help 🤷‍♂️

13 hours ago, Kopteeni said:

Thanks for your help 🤷‍♂️

I read my post again and in case this wasn't clear in my explanation above, there is no policy to avoid autothrust on landing and it is generally permitted to be used through touchdown. Autothrust arming and having to manually adjust thrust to maintain Vtgt is a consequence of idle thrust by making use of the airframe design feature of descending at idle thrust at 170 kts, flaps 3 on a 3 degree glideslope. This doesn't work on every approach though depending on the wind conditions and the approach itself and energy state (the latter of which is the reason to go 170 kts in manual speed selection one dot before the glideslope to help with energy management), in which case thrust above idle may be required and autothrust isn't going into armed mode and can be used until touchdown at pilot's discretion. There is no policy mandating the use of autothrust either.

Perhaps this makes it clearer. Other than that I'm not sure what else I'm supposed to say.

Edited September 26, 20223 yr by threegreen
Clarification

How does one engage the "simplified” NWS logic?  I couldn't find anything in the FMGC or on the tablet for this option.  As I understand it, this option will disengage NWS above certain speeds (ie when taking off/landing)?  Currently my NWS and rudder are both engaged even during take-off/landing which is leading to some pretty wild control inputs at higher speeds.

Thanks

1 hour ago, regis9 said:

How does one engage the "simplified” NWS logic?  I couldn't find anything in the FMGC or on the tablet for this option.  As I understand it, this option will disengage NWS above certain speeds (ie when taking off/landing)?  Currently my NWS and rudder are both engaged even during take-off/landing which is leading to some pretty wild control inputs at higher speeds.

Thanks

It's automatic in the new update: You have a control for the NWS tiller set in MSFS? It will work exactly like that (NWS with tiller, rudder with pedals). You have not? Both will be controlled by your pedals, and NWS will be auto-on on the ground and auto-off once you are above a certain speed (e.g. on takeoff or during landing). What is it in your case? Separated controls or pedals only?
I have separated controls and it works perfectly, I use the NWS during taxi and the rudder during takeoff/landing rolls.

Thanks, I have pedals only, no axis assigned to NWS so I would have assumed this would cause the NWS to automatically turn on and off but that does not seem to be the case.

50 minutes ago, regis9 said:

Thanks, I have pedals only, no axis assigned to NWS so I would have assumed this would cause the NWS to automatically turn on and off but that does not seem to be the case.

I don't know what the threshold is for NWS to disengage in the Fenix, but it's not low enough. Once I set a NWS axis to a controller my take-offs and landings became 1000 times more controllable at speed. I used to almost veer off the runway right before V1 - now I hug the centerline like I was on rails.

So there absolutely is a difference, at speed. Maybe the NWS auto-toggle is broken and the team isn't aware?