Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Engines turn to idle during take-off run

Featured Replies

Hi Folks, every time i try to lift my new PMDG 737 NGX in the air both engines return to hardware thrust-lever position after 75% of the take-off run (Autothrust still active!).The cockpit is set up as usual, V2 is set from QRH recommendation in FMC.I´m sure it´s my mistake, but i don´t find out which settings are wrong. Who can give me some information?Looking forward to your help... Happy Landings Matth (IVAO Germany)

Matthias Siegler

Germany

every time i try to lift my new PMDG 737 NGX in the air both engines return to hardware thrust-lever position after 75% of the take-off run (Autothrust still active!).
Aintcha answering your own question? Well, then place your hardware throttle to takeoff thrust to get rid of this effect... You are aware the THR HOLD has little to do with autothrottle and is a mode that will disconnect A/T servos from the levers, hence whatever you set manually will be your thrust target? sig.gif

The problem here are the spikes on the Throttle control. When you reach 80 the AT turn to ARM, and here you can control the Throttles manually. I'm sure that the spikes in the joystick is making the engines go idle.There is an option on the CDU (i don't remember where) that make the simulation to ignore any joystick input once you push TO/GA.

Matias Sorcinelli
CHECK MY CHANNEL!!! - http://www.youtube.com/user/masneoquil

Banner_FS2Crew_Supporter.jpg

fs2crew777.jpg

Yeah I think the option is how or when to allow manual override - never, always (which is semi-realistic but not so realistic on HW throttles without servos), and "in THR HOLD and ARM only", which is probably most realistic for most HW throttles. Although I'm not 100% if that option made it into HF4, but before that it was definitely there. sig.gif

Yeah I think the option is how or when to allow manual override - never, always (which is semi-realistic but not so realistic on HW throttles without servos), and "in THR HOLD and ARM only", which is probably most realistic for most HW throttles. Although I'm not 100% if that option made it into HF4, but before that it was definitely there. sig.gif
Yeaph, it is still there.

Matias Sorcinelli
CHECK MY CHANNEL!!! - http://www.youtube.com/user/masneoquil

Banner_FS2Crew_Supporter.jpg

fs2crew777.jpg

  • Author

Hi folks, thanks a lot for your quick and detailed answers! The setting "in THR HOLD and ARM only" was chosen but I still don't understand WHY Thrust mode changes from N1 to THR HOLD... Is it because of the different HW throttle setting? Choosing the "Never" option would mean to loose the option of a rejected take off...Will try to get a little bit deeper in system knowledge when time permits! So far Matth

Matthias Siegler

Germany

N1 to THR Hold is normal during takeoff. There is a related issue where the throttles are overiding the AT when active when they should not be which I have already reported to PMDG support.

System specs: Dual core E6300 (1.86g X 2), 2gb RAM, nvidea7800GT, Saitek yoke, CH throttle (6 lever), Soundblaster live.
Add-ons: FSX: LDS767, FSL Concorde, FT E175/195, PMDG 747X/737X, Active Sky E, some freeware airports.
Human specs: Desktop simulation since FS1, beta tester (LDS, FSL), 737NG simulator tech (Threshold Aviation), r sole+.

I still don't understand WHY Thrust mode changes from N1 to THR HOLD...
Erhm... cause it's how the system works??? You seriously need to read some FCOM, for a start on your issue Vol II 4.20.6 & 4.20.12 is your friend. THR HLD allows complete manual control due to disconnected servos. It's still good and recommended practice to hit the disco switches whenever aborting for example. Since you could have aborted when N1 was still active, which will still allow manual override (against the servos), but once you get your hands off the levers they would obviously advance again, which you probably wouldn't exactly look for during an RTO. Other than that, once THR HLD is announced you full authority over the levers... (until another mode engages) sig.gif
Hi folks, thanks a lot for your quick and detailed answers! The setting "in THR HOLD and ARM only" was chosen but I still don't understand WHY Thrust mode changes from N1 to THR HOLD... Is it because of the different HW throttle setting? Choosing the "Never" option would mean to loose the option of a rejected take off...Will try to get a little bit deeper in system knowledge when time permits! So far Matth
If you can't calibrate your throttle axes you should choose never on that option. Otherwise yo will have the same problem always

Matias Sorcinelli
CHECK MY CHANNEL!!! - http://www.youtube.com/user/masneoquil

Banner_FS2Crew_Supporter.jpg

fs2crew777.jpg

Te issue, that is not an issue, can be solved by disabling throttle movement in thrust hold (from the menus), in this mode the only way to manually move throttles will be disengaging AT.

Regards

Andrea Daviero

  • Author

Hi, thanks once more for your helpful comments (badderjet, you MUST be a real-world pilot...); going to simulate the servos of my X52 throttle by hand before thrust mode changes from N1 to THR HOLD since i find a more satisfying solution... Matthias

Matthias Siegler

Germany

I have the same problem with the saitek x52. It's always moving a little bit and that interrupts the TO/GA Mode. What helped for me was to leave the throttle at 0 and just push TO/GA. In 0 Position I have no unwanted Hardware movement on the throttle. But somehow some of my approaches end up with a go arround because of full thrust...Gabriel

System: i7-2600K, 4x 3.40GHz | ASUS P8P67 Deluxe B3 | 8GB Kingston HyperX T1 DDR3-1600 CL9 | HD 6950 2GB | 750W BeQuiet! Dark Power Pro P9 - 80Plus GOLD | 2x SSD SATA 3

FSX: SP1+Acceleration+REX

Erhm... cause it's how the system works??? You seriously need to read some FCOM, for a start on your issue Vol II 4.20.6 & 4.20.12 is your friend. THR HLD allows complete manual control due to disconnected servos. It's still good and recommended practice to hit the disco switches whenever aborting for example. Since you could have aborted when N1 was still active, which will still allow manual override (against the servos), but once you get your hands off the levers they would obviously advance again, which you probably wouldn't exactly look for during an RTO. Other than that, once THR HLD is announced you full authority over the levers... (until another mode engages) sig.gif
Etienne, you appear to be sounding quite a bit harsh and aggressive these days? :|That's not like you.

Sorry man, didn't mean to come across rude or anything. Always too easy to get a message across the wrong way by text-exclusive communication I guess... blush.png I'm willing to help people out where I can! Hope he didn't take my pointer to the FCOM sections in the wrong way. They basically describe the AFDS mode scenarios during takeoff, which is probably something useful for him.

Sorry man, didn't mean to come across rude or anything. Always too easy to get a message across the wrong way by text-exclusive communication I guess... blush.png I'm willing to help people out where I can! Hope he didn't take my pointer to the FCOM sections in the wrong way. They basically describe the AFDS mode scenarios during takeoff, which is probably something useful for him.
I know what you mean, it's no problem, as long as you are helping (:

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.