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

Question re default Transition Level in FMC-CDU Database

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

    Question re default Transition Level in FMC-CDU Database

    I noticed that the standard transition level displayed in the FMC - CDU of the PMDG 777-200 is always 18000 ft.

    Is this real world indicative when flying the real 777?



    Steve Summers - i7 8770K @ 4.7Ghz - 16Gb Corsair Vengeance DDR4 3000Mhz - Geforce GTX 1070 Ti 8Gb - ACER X34 Predator IPS GSYNC 3440x1440 - ASUS ROG STRIX Z370-H - 3 x Samsung Pro SSD 512Gb - Water Cooler: Corsair H100i GTX - Win 10 Pro 64 - P3Dv4.5 + ASP4 + ASCA + PMDG NGX + ORBX + FlightBeam + FSDT + Fly Tampa + Pacsim + AUScene: Revenge is not a valid motive, it's an emotional response. No, not vengeance. Punishment.

    #2
    Originally posted by XCLTM3 View Post
    Is this real world indicative when flying the real 777?
    steven

    you adjust the transition altitude & level in the VNAV pages to suit the "regional" values shown on sid & star charts.

    cheers
    john martin

    Comment


      #3
      Originally posted by vadriver View Post

      steven

      you adjust the transition altitude & level in the VNAV pages to suit the "regional" values shown on sid & star charts.
      Thanks John,

      I'm aware of that.

      However, my question posed - "Is this real world indicative when flying the real 777?" ie is the real 777 using a default Transition Level of 18000ft?

      I was wondering if the real 777 has a way of determining automatically the actual Transition Level once the pilots enter the Departure and Arrival Airport codes.

      Hoping a rw 777 pilot would chime in or a PMDG staffer (who is experienced with the real 777).

      krodgers
      Last edited by XCLTM3; 12Aug2019, 11:52.
      Steve Summers - i7 8770K @ 4.7Ghz - 16Gb Corsair Vengeance DDR4 3000Mhz - Geforce GTX 1070 Ti 8Gb - ACER X34 Predator IPS GSYNC 3440x1440 - ASUS ROG STRIX Z370-H - 3 x Samsung Pro SSD 512Gb - Water Cooler: Corsair H100i GTX - Win 10 Pro 64 - P3Dv4.5 + ASP4 + ASCA + PMDG NGX + ORBX + FlightBeam + FSDT + Fly Tampa + Pacsim + AUScene: Revenge is not a valid motive, it's an emotional response. No, not vengeance. Punishment.

      Comment


        #4
        Originally posted by XCLTM3 View Post

        Thanks John,

        I'm aware of that.

        However, my question posed - "Is this real world indicative when flying the real 777?" ie is the real 777 using a default Transition Level of 18000ft?

        I was wondering if the real 777 has a way of determining automatically the actual Transition Level once the pilots enter the Departure and Arrival Airport codes.

        Hoping a rw 777 pilot would chime in or a PMDG staffer (who is experienced with the real 777).
        Hi Steve.

        In the 777, the FMC knows what the transition altitudes and levels are based on the departure and destination. The caveat being in countries where transition level is assigned by ATC it will put a value in there (like in Germany it will put FL60) but we will need to change it to the actual TL assigned by ATC if it’s different than default value.

        In the PMDG 777 settings there is a default transition altitude or flight level setting. I’ve seen some different defaults for different livery installations and you can set your own in the settings as well for each livery. However, this isn’t how it works on the real 777. As started above, the FMC will display a value valid for the region your departing and arriving.

        Regards,

        Aaron Zylman

        Comment


          #5
          Originally posted by azylman1 View Post

          Hi Steve.

          In the 777, the FMC knows what the transition altitudes and levels are based on the departure and destination. The caveat being in countries where transition level is assigned by ATC it will put a value in there (like in Germany it will put FL60) but we will need to change it to the actual TL assigned by ATC if it’s different than default value.

          In the PMDG 777 settings there is a default transition altitude or flight level setting. I’ve seen some different defaults for different livery installations and you can set your own in the settings as well for each livery. However, this isn’t how it works on the real 777. As started above, the FMC will display a value valid for the region your departing and arriving.
          Thanks very much Aaron.

          I wonder if PMDG will be able to update the real 777 feature into this simulator in the next product update.

          krodgers - can you shed any light on this please?
          Last edited by XCLTM3; 12Aug2019, 21:49.
          Steve Summers - i7 8770K @ 4.7Ghz - 16Gb Corsair Vengeance DDR4 3000Mhz - Geforce GTX 1070 Ti 8Gb - ACER X34 Predator IPS GSYNC 3440x1440 - ASUS ROG STRIX Z370-H - 3 x Samsung Pro SSD 512Gb - Water Cooler: Corsair H100i GTX - Win 10 Pro 64 - P3Dv4.5 + ASP4 + ASCA + PMDG NGX + ORBX + FlightBeam + FSDT + Fly Tampa + Pacsim + AUScene: Revenge is not a valid motive, it's an emotional response. No, not vengeance. Punishment.

          Comment


            #6
            Transition Levels are determined by the barometric pressure at the arrival/departure airport. For separation purposes by ATC in the U.S. FL180 is not a usable altitude when the altimeter setting is below 29.92.
            Bode Bridges

            Beta Tester XM-26 Tow

            Comment

            Working...
            X