Sure would but I'm not sure my wallet thinks likewise

With all the fuel you have been wasting, you could afford a nice one!

 

 

Sure would but I'm not sure my wallet thinks likewise

 

 

With all the fuel you have been wasting, you could afford a nice one!

Guess you're right

My usual (non-servo hardware throttle) procedure is

 

At takeoff:

Advance to 40% N1.

select TOGA (Clickspot on VC)

Check that thrust is advancing to takeoff thrust.

Push hardware throttle to it's fully forward position which should be inside a pre-set null zone (transiting through max thrust on the way).

 

That way the throttle is in a null zone and won't spike (theoretically).

 

On decent,

 

Prior to removing Autothrottle, set thrust (using the blue throttle position things that PMDG have given us) to the currently produced thrust (that Autothrust is giving you), then come out of autothrottle. Because the hardware was pre-set to the same thrust setting as Autothrust had, the thrust you have after disconnecting autothrust will be the same as beforehand.

 

Incidently disconnecting the Autothrust on a (real) A320 works similar to this.

1: Pull thrust levers back to the position you want (ie match Autothrust value)

2: press Autothrust disconnect

3: The thrust is yours without getting a big surge of power as you draw the thrust back through the max thrust position.

Lots of interesting input and good advice here but just thought I should clarify what my original problem was...not that I had a problem with a mismatch between where I had my throttles and what thrust was commanded by the autothrottle when I disengaged it but rather that I during descent ended up with a command thrust of about 40% (where I left my throttles at takeoff) instead of throttles at idle since the autothrottle when in ARM mode and with the PMDG option set the way I mentioned in my original post will be where the physical throttles are left.

 

 

Lots of interesting input and good advice here but just thought I should clarify what my original problem was...not that I had a problem with a mismatch between where I had my throttles and what thrust was commanded by the autothrottle when I disengaged it but rather that I during descent ended up with a command thrust of about 40% (where I left my throttles at takeoff) instead of throttles at idle since the autothrottle when in ARM mode and with the PMDG option set the way I mentioned in my original post will be where the physical throttles are left.

 

Yeah, I derailed your topic. Sorry.

 

My usual (non-servo hardware throttle) procedure is

 

At takeoff:

Advance to 40% N1.

select TOGA (Clickspot on VC)

Check that thrust is advancing to takeoff thrust.

Push hardware throttle to it's fully forward position which should be inside a pre-set null zone (transiting through max thrust on the way).

 

That way the throttle is in a null zone and won't spike (theoretically).

 

On decent,

 

Prior to removing Autothrottle, set thrust (using the blue throttle position things that PMDG have given us) to the currently produced thrust (that Autothrust is giving you), then come out of autothrottle. Because the hardware was pre-set to the same thrust setting as Autothrust had, the thrust you have after disconnecting autothrust will be the same as beforehand.

 

Incidently disconnecting the Autothrust on a (real) A320 works similar to this.

1: Pull thrust levers back to the position you want (ie match Autothrust value)

2: press Autothrust disconnect

3: The thrust is yours without getting a big surge of power as you draw the thrust back through the max thrust position.

 

Thanks.  I'll try that.

 

 

Yeah, I derailed your topic. Sorry.

 

Absolutely no problem :smile:

 

Just wanted to clarify what my actual problem was for any others with the same problem wondering why their descent rate isn't what I should be.