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

737 Flap extension schedule

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

    737 Flap extension schedule

    I saw a video about when to drop the flap and I've always had a bit of a problem with the timing of dropping the flap. Firstly, wouldn't the maximum extended flap speed be shown in the 737 as it is in the 320? (on the PFD). The video says that you can drop flap1 when the aircraft automatically slows down to Appr speed, and then drop flap5 when the speed reaches the PFD speed display to 1 or when flap1 has been completely dropped (green light shown). at the final intercept ILS or the last 5-7nm, drop landing gear and then drop flap15. the last is 30 or 40

    I'm also curious about the PFD still showing a UP on landing, is the purpose of this for GA? I don't find it does anything practical in landing.








    CasperChen​

    #2
    Originally posted by CasperChen View Post
    I saw a video about when to drop the flap and I've always had a bit of a problem with the timing of dropping the flap. Firstly, wouldn't the maximum extended flap speed be shown in the 737 as it is in the 320? (on the PFD). The video says that you can drop flap1 when the aircraft automatically slows down to Appr speed, and then drop flap5 when the speed reaches the PFD speed display to 1 or when flap1 has been completely dropped (green light shown). at the final intercept ILS or the last 5-7nm, drop landing gear and then drop flap15. the last is 30 or 40

    I'm also curious about the PFD still showing a UP on landing, is the purpose of this for GA? I don't find it does anything practical in landing.




    CasperChen​
    It is good practice not to use the flaps as brakes, unless you need to. Always shoot for deploying the first flap setting when close to or at the UP speed. That is, if VREF40 for your weight is 130kts, try to select F1 when you're flying 200kts. UP speed is always VREF40+70kts, even if you've chosen F30 for the approach. UP, F1 and F5 are separated by 20kts.

    Then fly standard speeds on approach (180kts on intercept until 8nm and some 160kts until 6nm). In order to do this, make sure the speeds on every point on your legs page before the GS capture point match the speeds you want to fly. If you have set up your speeds in the legs page VNAV will sort out your vertical path to include deceleration segments. Fly it in VNAV until you get the hang of it to see how the AFDS does it and eventually you'll get to the point where you can do CDAs with more basic modes like LVL CHG and V/S to fine tune when on vectors.

    A good point to select F1 is at about 11/12nm. You may need F2 to fly 180kts or you may choose to go F5 and bug 180kts. F5 between 9/10nm. Use F10 and or speebrakes if the airplane has a hard time maintaining speed when on the glideslope. Select Gear Down and F15 at 4nm in VMC or 5nm in IMC for a Low Drag Approach. Finish configuring after that and finish your landing checklist.
    Last edited by Aeromar; 23May2023, 10:16.
    Omar Josef
    737 FO
    757/767 rated
    Spain

    Comment


      #3
      Originally posted by Aeromar View Post

      It is good practice not to use the flaps as brakes, unless you need to. Always shoot for deploying the first flap setting when close to or at the UP speed. That is, if VREF40 for your weight is 130kts, try to select F1 when you're flying 200kts. UP speed is always VREF40+70kts, even if you've chosen F30 for the approach. UP, F1 and F5 are separated by 20kts.

      Then fly standard speeds on approach (180kts on intercept until 8nm and some 160kts until 6nm). In order to do this, make sure the speeds on every point on your legs page before the GS capture point match the speeds you want to fly. If you have set up your speeds in the legs page VNAV will sort out your vertical path to include deceleration segments. Fly it in VNAV until you get the hang of it to see how the AFDS does it and eventually you'll get to the point where you can do CDAs with more basic modes like LVL CHG and V/S to fine tune when on vectors.

      A good point to select F1 is at about 11/12nm. You may need F2 to fly 180kts or you may choose to go F5 and bug 180kts. F5 between 9/10nm. Use F10 and or speebrakes if the airplane has a hard time maintaining speed when on the glideslope. Select Gear Down and F15 at 4nm in VMC or 5nm in IMC for a Low Drag Approach. Finish configuring after that and finish your landing checklist.
      Hey Omar,
      Thank you very much for this, I was able to use your advice from this post to have my best approach yet in the 738:​

      #msfs2020 #pmdg #pmdg737 #microsoftflightsimulator #msfs #flightsimulator #flightsim #flightsimulator2020 #flightsimulation #justflight #aviation #avgeeks #f...

      Mike Ryan

      Comment


        #4
        Originally posted by mryan75 View Post

        Hey Omar,
        Thank you very much for this, I was able to use your advice from this post to have my best approach yet in the 738:​
        That was very nicely done. That looked like a continuous descent to approach on standard speeds like a professional would do it. No unnecessary mode changes, VNAV all the way because there was no need to revert to other modes, nice intercept with no overshoot. Very nicely done.

        One thing you may want to know. Normally on descent, on the VNAV version that PMDG and many RL airplanes have, if you push SPD INTV it will take you out of VNAV PTH and it will switch to VNAV SPD, which is basically a legs protected version of LVL CHG. The exception to this is what's called ON PROFILE logic. When the airplane is ON PROFILE logic pushing SPD INTV will not switch from VNAV PTH to VNAV SPD. This will open up the speed window to allows you to select your speeds (200, 180, 160) as required by you or ATC, instead of having VNAV bug the flap manoeuvre speed which may be too slow for the sequence in large airports. We take advantage of this on non-precision approaches flown in VNAV and on precision approaches on the last stage of approach before GS capture (where the speed window will open anyway).

        So you would come in right before F1 and as soon as you select FLAPS 1, while still on VNAV PTH, you can push SPD INTV and bug exactly the speed you want. The airplane will stay on path and it will not go to idle thrust unless it needs to to maintain speed and path. Then when you select further flaps you can bug your next speed manually either to the flap manoeuvre speed or to the round speed number you want (180kts to 8nm, 160kts to 6nm...).

        Also the autobrake setting. Don't forget about it. It's a huge threat that can and does lead runway excursions consistently (which is a trendy key risk operating area in most places). Before descent when you calculate your landing performance you will consider Landing Distance Available, wind (brake on speed), temperature (brake cooling), runway condition (braking action) and airplane weight (resulting VREF) to make a decision on your landing flaps, reversers AND autobrake setting. All three settings are set and briefed as one.
        Last edited by Aeromar; 24May2023, 16:51.
        Omar Josef
        737 FO
        757/767 rated
        Spain

        Comment


          #5
          You can also add rings on the fix page. By example RW07 /10 /5
          It can also help you get started with the flap extensions approach.
          Kimi Häkkinen

          Comment


            #6
            Can you explain what is: ON PROFILE logic ?
            Thanks
            jorge soldano

            Comment


              #7
              On profile logic refers to a submode of VNAV. Ordinarily, pressing speed intervention will open the speed window and the vertical mode will revert from VNAV Path to VNAV Speed. Once it's in profile logic though, it will remain in Vnav Path (meaning it will prioritize vertical path keeping over speed), but will allow you to use the MCP speed window to command a speed.

              Regarding auto brakes, they're useful but I'd point out that they're optional. They're a fine thing to use in situations where they're helpful, but on a normal day it's fine to land without them as well, and that is encouraged as appropriate for proficiency and habit pattern maintenance. We don't want a generation of pilots who never brake manually any more than we want a generation of pilots who never hand fly approaches in IMC.
              Andrew Crowley

              Comment

              Working...
              X