Announcement

Collapse

PMDG Forum Rules

1) SIGN YOUR POSTS. Since 1997, we have asked users to sign their real name, first and last, to all posts in the PMDG forum. We do this in order to keep conversations personal and familiar. You took the time to be here, we want to get to know you. This is one of the few rigid rules that we enforce regularly. We do so because we feel that forums in which users must engage one another personally are generally warmer, more collegial and friendly. Posts that are unsigned will be quietly removed without comment by the moderators, so to make your life easy- we recommend enabling your forum signature so that you never need to remember. Do this by clicking the username pull-down at the top right, then selecting "User Settings." You will find the signature editor on the ACCOUNT tab, about half way down the page. Look for "Edit Post Signature." Be sure to click the "Show Signatures" box.

2) BE NICE. We are all simmers here and no matter our differences of opinion, we share a common love of aviation, computing and simulation. Treat everyone else in the forum with respect even when you disagree. If someone frustrates you, walk away from the conversation or ask for a moderator to get involved. Speaking of Moderators, they prefer not to be treated as "The Thought Police" but if any behavior infringes on the enjoyment of another user or is otherwise considered to be unacceptable in the moderator's judgment, it will be addressed in keeping with our view of ensuring that this forum remains a healthy environment for all simmers.

3) BE LAWFUL: Any behavior that infringes upon the law, such as discussion or solicitation of piracy, threats, intimidation or abuse will be handled unsympathetically by the moderators. Threats and intimidation may, at the moderator's discretion, be provided to law enforcement for handling.

4) BE FACTUAL: When you post, always be factual. Moderators will remove posts that are determined not to be factually accurate.

5) RESPECT COPYRIGHTS: Posting of copyrighted material such as flight manuals owned by Boeing or various airlines is not allowed in this forum. If you have questions related to copyrighted material, please contact a forum moderator for clarification.

6) RESPECT PMDG: We love to hear what you like about our products. We also like to hear what you think can be improved, or what isn't working. Please do tell us and we will always treat your feedback with value. Just be sure to treat the team respectfully, as they do put a significant amount of effort into building and maintaining these great simulation products for you.

7) RESPECT PMDG DEVELOPERS: All of the developers will spend some time here. Given the ratio of developers-to-users, it simply isn't possible for us to answer every post and private message individually. Please know that we do try to read everything, but developer workload is simply too high to manage personal contact with tens-of-thousands of users simultaneously. In most cases, members of the development team will stick to conversations in the forum and will not answer private messages.

8) RESPECT OTHER DEVELOPERS: PMDG has always advocated for a strong development community and we have many friends within this community. Every developer offers something unique that helps to make the simming community larger and more vibrant. We insist that you treat our friends respectfully.

9) RESPECT MODERATORS: Moderators have a tough job, and none of them enjoy having to stomp out negativity. If a moderator has to weigh in to keep a thread peaceful, please respect that effort and refrain from giving the moderator any grief.

10) If you require official support for any of our products please open a support ticket through the support portal, https://support.precisionmanuals.com

11) This forum is designed primarily as a vehicle for the PMDG development team to interact with our customers, and for customers to interact with one another in a manner that is positive, supportive and assists in the general advancement of understanding the simulation and helping to make this and future simulations better. Any other use of this forum is not permitted, including but not limited to discussion of pricing policies, business practices, forum moderating policies, advertising of non-PMDG products, promotion of events, services or products that are not approved in advance by PMDG or any other topic deemed unacceptable by any forum administrator

12) HAVE FUN: This is the whole point of it all.
See more
See less

Autoland function und A/T

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Autoland function und A/T


    Hello, everyone. I have a problem with the Final Approach with and without autoland. If I want to use the autoland function, I cannot activate both autopilots (CMD A and B) at the same time. Only one turns on at a time and the other turns off a short time later. Also: is it correct, that Autothrust needs to be disabled just prior to touchdown? I would be very happy about a short answer. Happy landings!

    #2
    You need to select FAIL OPS in the PMDG options.
    René Moelaert EHLE

    Comment


      #3
      for the 2nd autopilot being turned off make sure you fulfill all requirements. Most commonly people forget to set the ILS on BOTH NAV receivers.
      Ryzen 9 5900X, RX 6900XT, 32GB DDR4 RAM @3600MHz, 4k
      Marc Ehnle

      Comment


        #4
        Originally posted by Fleng200 View Post
        You need to select FAIL OPS in the PMDG options.
        Nope, Fail Passive will autoland just fine.

        Leave the autothrottles and autopilot engaged until after touchdown, then disconnect them both.

        To autoland:
        1. Both (captain and first officer) flight directors on.
        2. Both nav radios tuned to ILS.
        3. Both inbound courses set.
        4. On an intercept heading.
        5. Arm Approach mode.
        6. Turn on Both autopilots - this is the only time that selecting the second autopilot will not deselect the first.
        7. At approximately 1200ft above ground, a self-test will occur and if it passes, the Single Channel autoflight annunciation will change to CMD, and you'll see the Flare mode armed as a vertical mode on the flight mode annunciator (in fail passive.)
        8. After touchdown, disconnect autopilot and autothrottles, deploy reverse, maintain centerline.
        Andrew Crowley

        Comment


          #5
          4.5. Both the glideslope and localizer indicators are alive in the PFD. Don't arm approch before that.
          Geoff Darst

          Comment


            #6
            Originally posted by Stearmandriver View Post

            Nope, Fail Passive will autoland just fine.
            It will autoland just fine, but only using a single AP. Fail Operational allows for 2 APs to be engaged.

            Chris Lawrence
            Tin-Pusher @ EGPH

            Comment


              #7
              Originally posted by SeatonTower View Post

              It will autoland just fine, but only using a single AP. Fail Operational allows for 2 APs to be engaged.
              Nope still. Fail passive uses both APs. There's no way to autoland using a single AP.

              Our fleet at work is Fail passive; we very definitely need to use both APs.

              Fail Operational just uses a third axis of the autopilots for yaw, allowing the aircraft to track centerline after touchdown and thus lower vis requirements... unless you monitor the approach with the HUD in Aiii mode with rollout mode, which is what we do. Then fail passive autoland achieves the same landing minima as fail operational.
              Last edited by Stearmandriver; 14May2022, 21:42.
              Andrew Crowley

              Comment


                #8
                Originally posted by Stearmandriver View Post

                Nope still. Fail passive uses both APs. There's no way to autoland using a single AP.

                Our fleet at work is Fail passive; we very definitely need to use both APs.

                Fail Operational just uses a third axis of the autopilots for yaw, allowing the aircraft to track centerline after touchdown and thus lower vis requirements... unless you monitor the approach with the HUD in Aiii mode with rollout mode, which is what we do. Then fail passive autoland achieves the same landing minima as fail operational.
                I stand corrected. Just read the related section in the Boeing Operating manual too. I assume then that Fail Operational AP operation isn't an option on the real aircraft? It's not mentioned anywhere in the manual.
                Chris Lawrence
                Tin-Pusher @ EGPH

                Comment


                  #9
                  It is an option in the real aircraft. PMDG wouldn't have made it available if it wasn't. Both the FCOM and the FCTM mention it.
                  Geoff Darst

                  Comment


                    #10
                    Oh yeah it's an option. Often, fleets that don't equip with HUDs will choose fail Operational for the rollout control. I actually did not know there were even different choices here until I started using the NGx back in FSX. PMDG has taught me a lot about how varied 737s can be all over the world. When you learn an airplane at an airline, you learn their planes and that's it... never talk about options your fleet doesn't have.

                    So TL;DR - both fail passive and operational modes will autoland just fine, using both autopilots.
                    Andrew Crowley

                    Comment

                    Working...
                    X