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

"BYPASS" after entering waypoints in the FMC

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

    "BYPASS" after entering waypoints in the FMC

    Hello - I notice in some airports, after entering my flightplane, some waypoins near my arriving airport will say "bypass". It cuts my ILS approach and I miss my landing. How can I get rid of the "bypass" so my plane accepts my waypoints?

    Mike

    #2
    Originally posted by mike4063 View Post
    Hello - I notice in some airports, after entering my flightplane, some waypoins near my arriving airport will say "bypass". It cuts my ILS approach and I miss my landing. How can I get rid of the "bypass" so my plane accepts my waypoints?

    Mike
    Modify your flightplan or slow down. Bypass means that the aircraft cannot follow the flightplan track, usually because turns are too sharp.
    Mike Murphy
    Commercial, Instrument, Rotorcraft-Helicopter

    Comment


    • mike4063
      mike4063 commented
      Editing a comment
      Thank you. I will give it a shot. I appreciate your time. Have a great day!

    #3
    Originally posted by Helibrewer View Post

    Modify your flightplan or slow down. Bypass means that the aircraft cannot follow the flightplan track, usually because turns are too sharp.
    Oh come on Mike, that's not right. It means the aircraft will fly-by the waypoint which is perfectly acceptable. Don't have to change anything.
    Dan Downs KCRP
    i7-10700K 32GB 3600MHz 3080Ti

    Comment


      #4
      Originally posted by DDowns View Post

      Oh come on Mike, that's not right. It means the aircraft will fly-by the waypoint which is perfectly acceptable. Don't have to change anything.
      Don - the aircraft will not fly to the designated waypoint with "bypass" in the FMA. I wish I could post a video showing. But the B737 will not fly to the "bypass" waypoint.

      Mike

      Comment


        #5
        Originally posted by mike4063 View Post

        Don - the aircraft will not fly to the designated waypoint with "bypass" in the FMA. I wish I could post a video showing. But the B737 will not fly to the "bypass" waypoint.

        Mike
        The BYPASS refers to BYPASS LEG not waypoint and it will fly to the next waypoint along a path that is as close to the LEG as VNAV constraints allow. Most of the time when I see this it is on a departure procedure and the aircraft simply bypasses the waypoint that begins the leg and joins the leg not far after and proceeds to next waypoint. If your leg is very short then yes, the leg will be bypassed. Also, if three consecutive BYPASS LEG occur then FMS will insert a discontinuity.

        I also double checked the FCOM on this before posting so I feel like I'm on pretty solid ground.

        I don't want a video but I will look at the specific data, i.e., the procedure or route and specific speed/altitude/weights and aircraft type.
        Dan Downs KCRP
        i7-10700K 32GB 3600MHz 3080Ti

        Comment


        • Emi
          Emi commented
          Editing a comment
          Mike is actually correct Dan, the 737 FMC will show you BYPASS when it predicts that it can not cross the waypoint due to turns being too sharp or the speed not being right. It does not relate to overfly waypoints, which will not be "announced" by the 737.
          The correct action when you see BYPASS next to a waypoint is to reduce speed to enable the plane to fly the turn (assuming the route can for whatever reason not be modified, ie when it is a published route).

        #6
        Originally posted by DDowns View Post

        Oh come on Mike, that's not right. It means the aircraft will fly-by the waypoint which is perfectly acceptable. Don't have to change anything.
        If he doesn't want this to happen: "It cuts my ILS approach and I miss my landing." He needs to modify the flight plan, pretty simple. I'm not sure how you could bypass a leg without bypassing at least one of the legs waypoints. The flight plan is asking the FMS to do something the aircraft is not capable of, so it says "we are bypassing this" It is caused by a change of direction that exceeds the aircraft turning radius between 2 waypoints
        Mike Murphy
        Commercial, Instrument, Rotorcraft-Helicopter

        Comment


          #7
          Here is a pic of a bypass I experienced last week. The lower path is the RNP appr at NZQN which turned out to be a missed approach - the subsequent appr shows the bypass at GOSPA. I'd be interested in how to resolve this. From memory no matter what I did, I couldn't track from GOSPA to MABGA and it wouldn't let me track direct to MABGA, so I used HDG select to rejoin. But why the bypass and how to resolve IRL?
          Attached Files
          Last edited by Transair; 24Jan2023, 23:35.
          rgds
          Paul Bruce

          Comment


            #8
            I am not a RL pilot, but you are going way goo fast. Doing TAS 274, while IAS 210 is required at GOSPA. No wonder you will overshoot.
            And the route gets you perpendicular to the next segment. If you think the aircraft will not make that in a smooth way, at approximately 5 miles before GOSPA, set a direct MAGBA in the FMC.
            My 2c.
            René Moelaert EHLE

            Comment


              #9
              Originally posted by Fleng200 View Post
              I am not a RL pilot, but you are going way goo fast. Doing TAS 274, while IAS 210 is required at GOSPA. No wonder you will overshoot.
              And the route gets you perpendicular to the next segment. If you think the aircraft will not make that in a smooth way, at approximately 5 miles before GOSPA, set a direct MAGBA in the FMC.
              My 2c.
              I was doing 229 knots and the FMC had a 210 limit after GOSPA, so I thought that was reasonable. I also couldn't track direct to MABGA without HDG select. LNav wouldn't accept a 'direct'.
              rgds
              Paul Bruce

              Comment


                #10
                Originally posted by Transair View Post

                I was doing 229 knots and the FMC had a 210 limit after GOSPA, so I thought that was reasonable. I also couldn't track direct to MABGA without HDG select. LNav wouldn't accept a 'direct'.
                Your IAS doesn't matter, you can do 210kt but fly at FL200 and you'll still do some 300kt True Airspeed. The TAS is what matters.
                What do you mean with "LNAV wouldn't accept a direct"? I've never had such a problem yet.

                Comment


                  #11
                  Thanks Emi
                  I think when I selected MABGA, a similar thing happened - the bypass moved and there was no direct FMC path. I'm hazy now so happy not to pursue, but I thought providing the pic may help. What I'll do is recreate the scenario and see if I can get the same to occur....
                  Last edited by Transair; 25Jan2023, 22:50.
                  rgds
                  Paul Bruce

                  Comment

                  Working...
                  X