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.

Assumed temp takeoff - V2

Featured Replies

Whenever I perform an assumed temperature takeoff, and commanded N1 changes from D-TO to CLB, V2 always falls within the orange low speed buffet range and A14X flashes on the speed window to indicate that the selected speed is too low. Obviously, the speed means very little because with the pitch mode in 'TOGA' the FD is commanding V2+20.

 

However, I have a friend who flies the real 738 and his company SOP calls for 'bug up' at thrust reduction alt (the queue for the PM to select the airspeed bug to flap up speed). He said that he's never seen the speed window indicating min speed reversion on takeoff.

 

Where am I going wrong?

Martin Neep

Where am I going wrong?

 

This is assuming the FMS has been properly setup before takeoff.

 

Increase the thrust levers to 40% N1 and let the engines stabilize. Then press the TO/GA button (key command, clickspot or actual button). Ensure thrust has been set by 80 knots.

 

Rotate at VR and pitch up toward 15 degrees. Once airborne, follow the commands from the flight director. Raise the landing gear when a positive climb has been indicated on the baro altimeter.

 

Above 400 feet, select a roll mode (LNAV or HDG SEL)

 

At the thrust reduction altitude, select or verify that climb thrust has been set,

 

At the acceleration altitude, pitch down and increase speed to 250 knots. Retract the flaps on schedule. Select VNAV. Engage the autopilot after a roll mode and pitch mode are activated.

 

V2 always falls within the orange low speed buffet range and A14X flashes on the speed window to indicate that the selected speed is too low. Obviously, the speed means very little because with the pitch mode in 'TOGA' the FD is commanding V2+20.

 

I think you should monitor your airspeed and correct it if necessary.

Kenny Lee
"Keep climbing"
pmdg_trijet.jpg

The change to CLB has no effect on the minimum speed. The top of the lower amber bar is a function of weight - the more the higher it is. So if V2+20 is within the amber band, then your T/O performance calcs/speed is incorrect.

Banner_FS2Crew_Tech_Team.jpg

Hi,

 

if you sent me your payload, number of passangers, metar, airport, runway, I can put it in my topcat and send you correct speeds. We can then compare if you have the same (plus minus)

 

Petr

 

 

 

Sent from my BlackBerry 9900 using Tapatalk

Best regards

Petr

sign_small.php?call=036

  • Author

Sorry, I didn't explain it very well.

 

It's not that my actual airspeed is low, following the FD, current IAS is approximately V2+20.

 

The problem is that the airspeed bug, which is set to V2 prior to takeoff, falls within the low speed buffet margin, causing the A/T to display low speed protection.

 

I'll take a screenshot later when I get home that might help to explain it better.

Martin Neep

  • Author
Sounds like you might be in kg versus pounds.

 

I'm not using a 3rd party application to calculate V-Speeds. They're coming directly from the FMC based on actual weights.

Martin Neep

  • Commercial Member

I'm not using a 3rd party application to calculate V-Speeds. They're coming directly from the FMC based on actual weights.

 

That's not what he's talking about.

 

If the FMC is expecting LBS and you give it KGs, it will assume you're very light, and use very low (unattainable) speeds.

Kyle Rodgers

  • Author

p1403104298-2.jpg

 

p1403104312-2.jpg

 

p1403104272-2.jpg

 

p1403104270-6.jpg

Martin Neep

I'm probably doing it wrong perhaps, but I always set the MCP IAS window to V2+20 (172 in your case) since I don't plan on going slower than that anyway. After that I'll engage one of the vertical modes (usually VNAV) and accelerate to 250kias unless otherwise stated in the flight plan.

Thanks

Matthew T Gardiner

Hmmm. Did you maybe over-rotate and get slow?

 

Did you have F5 set for T/O? Your indicator is at about 7. . .

 

I'm probably doing it wrong perhaps, but I always set the MCP IAS window to V2+20 (172 in your case) since I don't plan on going slower than that anyway.

 

 

V2 goes in the window, and the box figures out the rest.

Matt Cee

Hmmm. Did you maybe over-rotate and get slow?

 

Did you have F5 set for T/O? Your indicator is at about 7. . .

 

 

 

 

V2 goes in the window, and the box figures out the rest.

 

Makes sense. Thanks

Thanks

Matthew T Gardiner

Where am I going wrong?

You're going wrong in that you haven't manually selected flaps up speed on the MCP at acceleration height, nor have selected a pitch mode (you're still on TO/GA), nor have armed a pitch mode (VNAV) on the ground. That, in combination with a heavily loaded aircraft, will result in the behaviour you're observing (disclaimer: I Am Not A Pilot).

 

Instead, do as the FCOM says (NP.21.29) and arm VNAV as part of your before start procedure. Alternatively (depending on the SOP you're following), you could engage LVL CHG at 1000' AGL and select flaps up speed manually at acceleration height.

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.