Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

dlh737

Members
  • Joined

  • Last visited

  1. Matt,... sorry for Raw Data with FD.... my flight instructors should kill me..... (I mean no Autopilot, just TO/GA) The speed value set as Bug UP into MCP at acceleration height is the same shown by the magenta bug on PFD... example 220 kts but the Flight Director commands a pitch up/down in order to fly at 240 kts.Is it normal?About FCOM you cosider a T/O with the VNAV engage .... but without....?However... I think that is a very very small thing.... just few people point it up... and look the great job around the NGX... I can say that was just my curiosity understand the issue and not absolutly a complain!so.... thanks to everyone that gave me an opinion about and to Roberts, Ryan and all the PMDG staff for the great product.
  2. As mentioned in my (and not) previuous post... it should work also without VNAV engaged! I'm always refere to Raw Data.... No Auto Pilot angaged apart TO/GA.....
  3. That's true Ryan... the procedure is fine... V2+20, the speed window jump as you mentioned...... everithing correct!What I don't understand is why if the bugup speed is set at example 220 then the FD commands to maintain 240 after acceleration height!Maybe something I'm missing?Thanks for support
  4. YES... exactly what happen! The problem is only after acceleration height! NO... What I found (as shown in my previous post nr 3)" Sylvain is right Ryan, even not selecting LVL CHG or VNAV , when at acceleration height and selecting Bug Up speed on MCP the FD should command a nose down pitch towards that selected speed. That's how it's done, it's clearly shown on FCOM and SOP's worldwide." YES... I set it at 3000 ft with reduced CLB at 1500 ft like RYR Procedure
  5. So... do you think that is correct what I reported at the beginning of the post? (I always refer after Acceleration Height) The maximum airspeed limit is the flap placard speed until the airplane reaches the MCP speed..... not MCP speed + 20
  6. Ok, really thanks...my doubt rised from a previous post: http://forum.avsim.n...-after-takeoff/exactly... posts nr 9, 19 (reported below) and 20"Sylvain is right Ryan, even not selecting LVL CHG or VNAV, when at acceleration height and selecting Bug Up speed on MCP the FD should command a nose down pitch towards that selected speed. That's how it's done, it's clearly shown on FCOM and SOP's worldwide."Maybe my misunderstanding or different 737 options.
  7. Hello guys,Could you please confirm If the following happen to everyone or just to my config:After acceleration height (A/T TOGA mode with no Autopilot) once the BUG UP speed is selected into MCP the Flight Director commands correctly an acceleration but with a target speed of MCP speed + 20 instead of MCP speed.Any opinion about?Thanks
  8. Yes, now it is correct! Only if you disconnect FD from TOGA using an AP mode, the magenta bug and the fmc speed will be changed at V2+20.Before that the bug stays at V2.
  9. VR ENG failure tried this morning.... I have two different situation: 1. Two TO (eng1 / eng2) - VR ENG Fail - At A/C load I set Armed = the Speed bug on PFD stayed at V2 (correct) 2. Two TO (eng1 / eng2) - VR ENG Fail - At A/C load I set Active = the Speed bug on PFD change to V2+20 for few seconds and then back to V2 Please let me know if you and someone else have the same..... p.s: PMDG tech support already informed into my open ticket
  10. Exactly... FD work correctly..... The strange thing is the MAGENTA BUG on ASI (PFD).... However, I'm wait for a tech replay before just to be sure to not saying something wrong. I think PMDG have a really professional and competent staff so they know the 737 and that's is why I'm waiting a replay.
  11. +1 Already discussed and I have a personal open ticket (still work in progress) with PMDG Support! I hope they solve the issue..... After read, read, and read again the manuals I didn't find any point that specify that Magenta bug into PFD go to V2+20! The only thing is AFTER I engage an A/P mode that remove FD from TO/GA (p225)..... then both MCP speed AND Magenta bug go to V2+20 Before they just mentioned about FD commands at MCP speed +20 (Pitch then commands MCP speed (normally V2) plus 20 knots). Read pages 223, 224 and 225 of FCOM2! So what you state I think is correct! However we will wait for a tech support reply
  12. Please anyone from "Tech Team" could answer to my last post.... Thanks
  13. Really thanks guys for your patience The first two point are exactly what I can see and do..... NO A/P - FMA: THR HLD/ N1| | TO/GA | At acceleration height I call PNF BUG UP speed without any AP command or VNAV or LVL CHG.... the magenta bug is at V2 + 20 and the MCP at V2.... so when my PNF select on the MCP the BUG UP (Speed indicated on PFD ex 220) on my MCP he set 220 but the bug on PFD is at 240.... That's never happend to me.... and why I ask support to you.... Still sorry P.S.: I personally never saw a discrepancy between BUG on PFD and MCP select speed (normally an AP mode as VNAV remove the speed from the box.... but if I see the select speed the magenta bug must match it) Am I wrong?
  14. So.... it is impossible fly manually the airplane whitout FD and AP...... I need to engage AP.... I did MCC on 737 and never happen..... but probably is an option on the 737...... Sorry for my not understanding..... but I'm preparing myself for selection and I would like to understand if it was my mistake.... Really thanks for your quick answer!

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.