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.

ASI Bug settings

Featured Replies

Need a little help with this:on the PIC panel there are 5 bug settings on the ASI plus the command speed bug.These are set as follows for takeoff:Bug 1: V1CMD SPD: V2Bug 2: VREF + 20Bug 3: VREF + 40Bug 4: VREF + 60Bug 5: VREF + 80with VREF+80 corresponding to the FLAPS UP Maneuvering Speed for a given weight.However www.b767.org.uk shows the following:Bug 1: V1Bug 2: VRCMD SPD: V2Bug 3: VREF + 40Bug 4: VREF + 80they do not show a bug 5.Using the hidden click spot in PIC, the bugs are automatically set as per the first example.Now what I want to know is, is this the correct method for bug setting or is the www.b767.org.uk bug setting method the correct one.Thanks

MarkThe 2nd one from 767.org.uk is the BA way of doing it - a lot of the stuff on that site appears to be copied from the BA 75/76 operating manual.Maybe other carriers do things differently?

Tom,thanks for replying. I had a funny feeling that a lot of that site's contents were from BA procedures - the RR powered 767 info gave it away. I will need to do a little more research then before I commit to a certain method.

Mark,I'm glad you brought this up, since I have had n+1 emails concerning how airspeed bugs should be placed.PIC sets them very nicely. Since PIC has 5 bugs + the orange bug, there's absolutely no reason to use LESS bugs.For example, Finnair uses the exact same method for setting the bugs as is described in both 757/767.org.uk pages. The reason for this is twofold:1. The aircraft only have 4 white bugs available2. 4 bugs are used not to clutter the ASI.The basic layout is always the same:In takeoff, V1, (Vr), V2 and +40 , +80For ldg, Vref doublebug, +40, +80The intermittent bugs +20 and +60 are of course exactly inbetween the other bugs so they needn't be set if a less cluttered ASI is desired.Both ways are absolutely correct. Use what suits you the best. I myself use both, depending on if I'm lazy or not...ALSO, what's very important is that both during acceleration and decceleration, the next FLAP setting should be selected 20kts PRIOR to the current setting man. speed (decceleration) and 20kts PRIOR to the next setting's man. speed (acceleration).However, rarely the decceleration can be done at once, through all the settings. In that case, it's ok to just select next flap setting before reaching the man. speed of the current setting. During takeoff it's different as NORMALLY the aircraft can be accelerated to at least +80 after takeoff.Tero

PPL(A)

Tero,thanks for replying.How does this sound then - combo of both methods:V1 VR VREF+40 VREF+60 VREF+80

I find the hidden click spot thingy on the VSI doesn't set accurate speeds.I like to calculate more accurate V1/VR speeds with the use of a performance manual. I don't even bother entering a takeoff flap setting into the FMC. Then I read my V2 and VREF speeds from my checklist and then set all the bugs manually according to my calculated speeds.

Hi MarkHow does this sound then - combo of both methods:V1 VR VREF+40 VREF+60 VREF+80But doesn't the orange cmd bug always set V2 i.e. whatever speed is set on the MCP? Is there a way to move the orange bug around the circumference of the ASI?

Hi Tom,I take it you are using the BA perf manual?

How does this Look:http://forums.avsim.net/user_files/63913.jpgBug 1 is set to 80 KnotsBug 2 is set to V1Bug 3 is set to VRCMD BUG is set to V2Bug 4 is set to VREF + 40Bug 5 is set to VREF + 80

Tom,PIC767 sets the bugs correctly.Of course you can move the orange bug, it is the MCP speed bug. For takeoff it's always set at V2.Tero

PPL(A)

Mark,Why not use the PIC settings ? You do not need the "80" bug there at all. The callout "eighty knots" is there merely to check that both ASIs are working, and that there is no significant difference between the readouts of capt. and f/o side ASIs. I would prefer either PIC's own system or the one promoted in the 757.org.uk.Tero

PPL(A)

I will probably go with the 757.org.uk settings. I found these a bit easier on the eye.

  • Commercial Member

Here's my pet peevesBug 1: Masculine womenCMD SPD: "If I told you you had a beautiful body, would you hold it against me?"Bug 2: Ju jubes... yeck.Bug 3: Dirty washrooms at the service station.Bug 4: InsincerityBug 5: Barry ManilowDaryl ShuttleworthDS 3339http://vatsim.pilotmedia.fi/statusindicato...tor=OD1&a=a.jpg

The SUPPORT FORUM for Level-D Simulations products: http://www.leveldsim.com/forums

LVLDF1.gif

Surprised Barry Manilow did not make it higher up the list.

Mark - yeah BA perf manualTeropa - it only sets the correct speeds if you use the FMC calculated speeds!

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.