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

LNAV enabled and sometimes it doesn’t

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    LNAV enabled and sometimes it doesn’t

    Question on Lnav. Most of the time before I taxi I arm AT and enable VNav and Lnav on the 737. Sometimes the Lnav light doesn’t come on. The 777 seems to always come on. So why would the Lnav light not show up until after takeoff. I thought it had to do with the flight path but that doesn’t seem to be the case. I am using a check list so what is a good practice to follow on when to engage Lnav. I am not using ATC.
    Dean Salman
    Tags: None
    #2
    Originally posted by dsalman1 View Post
    Question on Lnav. Most of the time before I taxi I arm AT and enable VNav and Lnav on the 737. Sometimes the Lnav light doesn’t come on. The 777 seems to always come on. So why would the Lnav light not show up until after takeoff. I thought it had to do with the flight path but that doesn’t seem to be the case. I am using a check list so what is a good practice to follow on when to engage Lnav. I am not using ATC.
    LNAV engagement requires an active FMC route that can be intercepted within 3 nm or if a greater distance then the airplane must be on an intercept course of 90 deg or less and intercept the active route segment before the next active waypoint. On the ground before takeoff, LNAV may not be engaged unless the first waypoint is within a number of degrees of the runway heading. I'm not sure but I think it is 60 deg.

    Check your PMDG Aircraft Equipment options to verify the takeoff roll mode, normally this wings level until about 400 ft AAL where then an AFDS roll mode can be selected. The options are wings level and HDG mode.

    I will often seen LNAV not engage before takeoff without knowing why, but it's a simple matter of using HDG or handflying until reaching V2+20 then engage it. My personal preference is to only use LNAV on departure when using a RNAV SID or a non-RNAV SID with a straight forward departure path. Otherwise I use HDG.
    Dan Downs KCRP
    i7-10700K 32GB 3600MHz 3080Ti
    • Likes 1

    Comment

      #3
      Hey, Dean-

      Dan has given you some good guidance above. I am not a 737 driver, and someone else on the team codes that part of the airplane- but I do know that the 737 has slightly different arm/engagement limitations than the big boeings- so perhaps you are seeing one of those limitations.

      You didn't offer any info on a specific runway/departure configuration- so I am largely guessing- but when out flying real-world, we will generally use LNAV if using a SID that has a defined departure path. If we do not have a programmed departure SID, or if the SID is a vector-to-fix, we'll then choose either TO/GA or HDG. The choice between them really depends upon what we expect to happen in the initial climb. For example, if we get "climb runway heading" we'll use HDG mode. If we get "fly heading XXX when able" then we'll set the heading bug to that heading and use TO/GA for the initial climb. Pilot flying then calls for HDG during the climb and we commence the turn.

      As is always the case in complex environments: Your mileage may vary.

      If there is a specific SID you want to evaluate- just shout out here. Plenty of us here to help you.

      Robert S. Randazzo
      PMDG Simulations
      http://www.pmdg.com


      Comment

        #4
        Thanks for the Feeback, dan and Robert. When I see this again, I can include the route as well. But it sounds like the first way point being within the required turn. I will look deeper into this, thanks
        Dean Salman

        Comment

          #5
          I’ve had the same issue. Whenever I’m departing from DTW’s 21R, with the PAVYL2 departure, LNAV will not stay armed on the ground. When I select LNAV on the ground, the button briefly lights up then goes out. I’ve had the same issue with another airport with a RNAV SID but I don’t recall where.
          Loren Gogins
          B737
          E170/E190

          Comment

            #6
            Hey Dean,

            LNAV will not arm of the first turn after departure is greater than 5 degrees in this plane. Also just mentioning it both FD's need to be on for LNAV to arm on the ground. Two of several checks the system does

            Best,

            Vangelis

            Comment

            Previous template Next
            Working...
            X