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.

Do you set V2 speed in MCP to V2 or V2+20

Featured Replies

Ok say i have V2 speed in FMC to 134, do you then set the 134 V2 speed in the MCP or do you add +20 to it? so insted 134 you add 154 into the MCP ?

You're supposed to set V2. The FD will automatically show a pitch that will lead to a V2+20 speed despite the speed setting in the MCP. It's also entioned in the tutorial prepared by Ryan (I think).

George Golas

----------------------

I hate gravity!

Fine, set it as V2+20, that is the option we used. We're just trying to educate people here, either option is correct is basically what we're saying, they'll just need a bit more research to find out what procedure the company they are flying for uses.....

Rónán O Cadhain.

sig_FSLBetaTester.jpg

Fine, set it as V2+20, that is the option we used. We're just trying to educate people here, either option is correct is basically what we're saying, they'll just need a bit more research to find out what procedure the company they are flying for uses.....
I'm always finding there are many options for the 737. The basic guidance is for V2 to be set in the MCP. I suppose Boeing could come up with other options. However, the setup for the sim is to set V2 in the MCP, no?

Matt Cee

Yes. I always set V2 in the MCP and then arm VNAV either before takeoff or after crossing through 400' ft AGL. I arm the A/T before lining up, engage TOGA after N1 stabilizes at about 40%, and I let VNAV do the rest in terms of speeds. I never "bug up" nor have I ever gotten the flashing "A" by not bugging up. Once you reach your acceleration height, pitch the nose down (following FD cue) to begin gaining speed and as soon as speed is increasing, retract flaps one notch. Then follow the FD commands to continue acceleration and retract flaps as you reach the flap speeds. VNAV should automatically "bug up" for you...at least that's how I've always done it. Adam

Adam Hill

  • Author

Ok thx Gents, Both is correct as I understand it then ;)

No. just setting V2 is correct! Try to find some real 737NG flight video on YouTube and get convinced. / Leffe

Leif A Mikkelsen

**********************

If you set the MCP V2+20, the F/D is going to give you an initial climb of V2+40 - not so good in an engine failure.

Matt Cee

No. just setting V2 is correct! Try to find some real 737NG flight video on YouTube and get convinced. / Leffe
Yes it is....Whistle.gif

Rónán O Cadhain.

sig_FSLBetaTester.jpg

Now with regards to this, I'm not sure if that's a software update that is present in the NG, so an NG pilot will have to inform us there, but basically, it wasn't there in the classic series. If it does do that though, just fly at V2+20 anyway, you're a pilot, not a button monkey and the majority of the time you won't have an engine failure, so it's safer to have V2+20 bugged for your departure if you haven't got VNAV armed.....
I'm current on both Classics and NG, and the guidance is the same:
if an engine failure occurs during takeoff, the pitch command target speedis:- V2, if airspeed is below V2- existing speed, if airspeed is between V2 and V2 + 20- V2 + 20, if airspeed is above V2 + 20
Sorry, but to me it doesn't sound like a matter of preference. To guarantee the performance requirements, you need to fly at V2 to V2+20 and to get that guidance, you need to bug V2. I've flown for two 737 operators and jump seated on several others and they all did it the same: Bug V2. Could you dust off your old manuals and take a peek? I'd like to see what the guidance would say if it was otherwise.

Matt Cee

I'm current on both Classics and NG, and the guidance is the same:
Thanks, good to know...
Sorry, but to me it doesn't sound like a matter of preference. To guarantee the performance requirements, you need to fly at V2 to V2+20 and to get that guidance, you need to bug V2. I've flown for two 737 operators and jump seated on several others and they all did it the same: Bug V2. Could you dust off your old manuals and take a peek? I'd like to see what the guidance would say if it was otherwise.
Don't have my manuals anymore, but I'll get my hands on some and get back to you on that one, I'm 100% certain though that we used V2+20 on our MCP when we were operating them... Out of curiosity, which side of the pond are you operating on? [Not that it should make much of a difference, just curious]

Rónán O Cadhain.

sig_FSLBetaTester.jpg

Thanks, good to know... Don't have my manuals anymore, but I'll get my hands on some and get back to you on that one, I'm 100% certain though that we used V2+20 on our MCP when we were operating them...Out of curiosity, which side of the pond are you operating on? [Not that it should make much of a difference, just curious]
Sadly, I haven't been to your side of the pond, even though I'm mostly Irish by lineage. I've been working in the US and in Asia. Maybe the next time I'm laid off, I'll try to find a European operator.

Matt Cee

Oh bugger, alright, I've just gotten off the phone with another pilot at EIN who also used fly the classics with me [not exactly the kind of telephone call you'd be expecting on a Sunday afternoon, but these are the lengths I go to for yee] and I've been set straight, so, to swallow my pride, Set V2 in MCP and then it will automatically increase to MCP+20 after takeoff, sorry about that, I was dead sure, although 16 years away from an aircraft can leave things a little blurry, sorry for any misguidance here, totally my fault....So correctly, the MCP window will show V2 but the speed bug will display V2+20... Oh darnation.... blush.png

Rónán O Cadhain.

sig_FSLBetaTester.jpg

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.