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.

Landing Vref bug question

Featured Replies

When i setup the entire flight trough FMC, on landing i have a nice white bug on the speed tape together with a green one.But none of them is ever in the indicated speed.I mean if i have a certain vref, say 137kts, and add 8kts wind correction, i have a final vref of 145kts.Well neigther of the bugs do ever point to 145, nor 137 for the sake of it...So i am asking if there are some internal calculations i do not know of, or what?

Hi>So i am asking if there are some internal calculations i do not know >of, or what?YEs. I would certainly think this is the case. You'd be amazed if you knew what takes place inside this sim.The white bug on approach is the bug for the flaps 15 speed (I'm sure it has some fancy V-abbreviation as well). Useful for GAs.Also you should have a couple of green bugs. Some are speed bugs for the next flap setting and finally you have a Vref bug which should be at the Vref speed in the FMC.Hope it helps,

Mats Johansson
PMDG Flight Test Dept
Boeing777_Banner_BetaTeam.jpg

| Asus Z270-A | Intel i5-7600K @ 4.8 GHz OC/H2O | nVidia Geforce GTX 1070 8GB OC/O2|

The white speed bug you are refering to is called the "VREF+15 Bug" and is displayed after selection of VREF. It's automaticlly set 15 knots above VREF. On a single engine go-around VREF+15 is approximately equal to V2 for flaps 1.On a engine failure on final approach VREF+15 is equal to at least VREF for flaps 15.Set the magenta command speed bug (MCP airspeed window) to VREF + wind correction always.Floyd

John Floyd

Guten Tag gentlemen.PMDG 737-600/700 The following 2 excerpts of FMC Users Manual cover the issue. For 'take-off' FMC "...control the speed bugs on the Primary Flight Display"For 'landing' the manual says NOTHING about FMC speed bug control.Q:does FMC set speed bugs for landing correctly or not ?Regards, G

"V1/Vr/V2: The Next Generation 737 does not automatically populate the FMC with V-Speeds based on crew input to the FMC/CDU. V-Speeds are normally entered manually into the TAKEOFF REF page to control the speed bugs on the Primary Flight Display."This is not entirely true. The Bulfer FMC Guide mentions an option which will allow this. Suggested speeds are generated after crew initialization data entry. These appear as small font speeds in the centre of the CDU display. Pushing the right line select keys adjacent to the speeds twice will transfer the speeds to the PFD."Q: does FMC set speed bugs for landing correctly or not ?"They should do. Are you not getting them... or getting them in the wrong spots? For A/T control, it's normal, of course, to manually set the command airspeed bug via the MCP to match the FMC-computed value.Cheers.Ian.

I am getting two bugs:one whiteone greenand the usual magenta oneMy problems where with the white and green, because they did not point to any of the speeds selected in the mcp.Now thanks to the messages to this post i am going to have a check on it.

Create an account or sign in to comment

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.