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.

Continued ATS problems!

Featured Replies

I have resolved most of the issues I have had as a newbe with this simulation.  So far all were because I had misinterpreted the FCOM, but this last issue has persisted.  Here it is:

 

On takeoff with everything set and checked, I arm NAV, then arm PROFILE, and lastely press AUTOFLIGHT.  I am showing TKOF CLAMP on the PFD.  I advance throttles to 75% but nothing happens.  I push throttles further...still nothing.  The FCOM states that the ATS should kick in and advance throttles to the preselected TKOF setting.  Everything is set correctly in the FMC and I have completed all the tests and setups.  I am either going to run out of runway attempting to takeoff with 75% power or I have to advance the throttles manually.  When I do that they always go to FULL TAKEOFF power instead of my FLEX setting.

 

The only thing that I might be doing differently is that I begin advancing the throttles BEFORE I release the brakes.  Could that in anyway be compromising the ATS?  Doesn't seem logical that it would have anything to do with it.  Please advise!

 

 

Do you hear a click when you push the throttles forward? Probably won't help at all but was watching the AoA training flights the other day an they say that the preferred takeoff method with the MD11 is a rolling takeoff.

Gavin Price

  • Author

@ Gavin:

 

   I listened but the only click I think I am hearing is the brakes disconnecting.  I do not use a control device, only mouse and keyboard but, again, that should not matter.  I have been increasing speed using the keypad "9" key or the F3 key but I don't believe I am hearing "thrust set" either.   I do hear "80 knots" and then the v-speeds and positive climb callouts.

 

   Maybe there is something I am not setting right but as far as I know I have everything set correctly before I enter runway.  

 

   I will try again and this time I will take screen shots showing the PDF before I arm the automatics and then again just before I apply throttle.  See if something wrong is recognizable to one of you experienced MD11 drivers.

 

    I will try a rolling takeoff next time to see if that is the issue, but again, a rolling takeoff may not be prudent if the runway condition or length could put the plane in a marginal situation if an engine failure.  Can't imagine that the ATS has any connection to the brakes on as long as they are released before the "brakes" warning announces but I must admit I am just guessing here.

You should definitely be hearing the click of the ATS engaging when advancing the throttles to near the stops so can't think of what could be causing this.

Have you got the Green box in the display to say you're correctly configured for takeoff? Also have you tried advancing the throttles with the mouse to see if that works?

Gavin Price

  • Author

Hi Gavin!

 

    I tried again and kept the brakes on while I gradually increased the power past 75% and CLIMB THRUST engaged at a little over 95%!!!  I guess my problem is that I was not advancing throttles far enough.  The FCOM says 75% and so did the advanced tutorial.  75% sounds more RW.   Now I just purchased the product as a download from PMDG.  I am assuming that the one upgrade that was made after RTM has been already included in the current download version, but now I am beginning to wonder.  I noticed another bug in my last test flight:

 

While at cruise I encountered traffic at same flight level and closing in so instead of waiting for TCAS I anticipated the course of the conflict and changed my heading to pass to the right but when I dialed the heading and pulled the switch to activate HDG SEL (as outlined in the FCOM) the plane began banking the opposite way directly into the path of the oncoming so I had to take over manually.   Pressing NAV brought me back on track and I then began to experiment and each time I turned the HDG SEL dial the aircraft turned in the OPPOSITE direction!   Is that a known bug or has nobody taken the plane out of automatics enough to realize it?  Below is a picture showing the heading line in one direction, the heading on the bug and the plane beginning its bank in the OPPOSITE direction!

 

 

Hi,

 

I tried again and kept the brakes on while I gradually increased the power past 75% and CLIMB THRUST engaged at a little over 95%!!!  I guess my problem is that I was not advancing throttles far enough.  The FCOM says 75% and so did the advanced tutorial.  75% sounds more RW.   Now I just purchased the product as a download from PMDG.  I am assuming that the one upgrade that was made after RTM has been already included in the current download version, but now I am beginning to wonder.  I noticed another bug in my last test flight:

 

As far as I am aware, the service pack which has been released for the MD-11 is not included in the download version. You can find it out by activating reversers on your MD-11 while cold and dark. If they won't deploy, you are up do date, else download the service pack from the PDMG website.

 

Best regards,

 

Jonathan

John Rubens
PMDG_ngx_T7_sig.jpg

  • Author

@ Jonathan:

 

   Aha!  Thanks for the info.  I will run the test.  The website and the download both say they are v1.20.0055 which matches the number on the upgrade, but the text file only shows the version changes for FS9 version even though the install exe file is labeled FSX.

 

   Back to the main issue on this thread, however.  When you advance throttles for takeoff what % thrust before ATS takes over are you experiencing on your computer?  As I mentioned 95% seems way to high but since it was a rainy wet runway I was using Full Power Takeoff instead of derate.  Maybe the capture is proportional to the selected Takeoff power setting(?)  You seem to be the guru on this site, Jonathan, so your input is valued.  Thanks again. 

The dotted line on the outside of the ND compass tells you which direction your turn will go. It all depends which way you scroll the mouse wheel.

Gavin Price

 

 


On takeoff with everything set and checked, I arm NAV, then arm PROFILE, and lastely press AUTOFLIGHT.  I am showing TKOF CLAMP on the PFD.  I advance throttles to 75% but nothing happens.

 

Dont need brakes. If all is green for your takeoff checklist, advance the throttles to 70%N1, and only then press Autoflight. You will hear the click. I prefer to fly manually until stable and then press autoflight again. You dont need nav mode just yet if you fly runway heading. Just follow the Flight director. Once youve changed your heading to your first waypoint and stable climb, then press NAV and PROF. 

 

I highly suggest the AoA videos for the MD11. They have been fantastic in getting to handle the MD11 well. 

CYVR LSZH 

I7-14700k 64gb 6000Mhz DDR5 ASUS  z690 ROG STRIX Gaming  RTX 4080 Super, 

Hi,

 

 

Back to the main issue on this thread, however.  When you advance throttles for takeoff what % thrust before ATS takes over are you experiencing on your computer?  As I mentioned 95% seems way to high but since it was a rainy wet runway I was using Full Power Takeoff instead of derate.  Maybe the capture is proportional to the selected Takeoff power setting(?)

 

I did a short test with a full power takeoff and it came on at about 85% N1. However, on my physikal throttle that's about the 70% mark of travel. Maybe those 70% percent are throttle position? Or it could be, as you suggested, that it is 70% of your takeoff power setting. I honestly don't have a clue!

 

And no, I am not a Guru here, those are other people! I just made similar misstakes as you when I was new to the MD-11 and I have learned from them. ;)

 

Best regards,

 

Jonathan

John Rubens
PMDG_ngx_T7_sig.jpg

  • Author

Maybe you claim not to be a "guru", Jonathan, but your willingness to share your knowledge and help others certainly puts you in a class by yourself.  It is much appreciated not only by me but I'm sure by others who are reading these threads but not posting who may have had similar issues.  Again, many thanks.

 

.


I did a short test with a full power takeoff and it came on at about 85% N1. However, on my physikal throttle that's about the 70% mark of travel. Maybe those 70% percent are throttle position? Or it could be, as you suggested, that it is 70% of your takeoff power setting. I honestly don't have a clue!

 

I did try it both from braked position and rolling takeoff but I use the 2D panel so I am not able to watch the VC throttle position and the thought did cross my mind but rereading the FCOM re-affirmed that it was referring to 75% N1 rather than throttle position.  Could just be a glych with FSX delay in interpretting the input (?)  Either way now that I am aware of it I will just advance the throttle more slowly when I am past 75& until I see the PDF change to T/O THRUST.

  • Author

This is for FSX and I DID read your post.  The solution is to continue to slowly advance the throttle until T/O THRUST is displayed.  The issue is that RW thrust advance to just above 75% and my experience with the simulation is that it requires around 90+% before it engages.  It seems consistent so either PMDG programmed it that way for ?  or something in FSX slows the response.  My frame rates, however, with this sim are always in the low to mid 40's compared to the mid 20's with NGX so it shouldn't be a CPU or memory issue.  I can certainly live with it now that I know what to expect.

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.