Jump to content

Sign in to follow this  
JSACKS

Departure: How many valid ways to depart ?!@#$?

Recommended Posts

Bug Up manually to UPAP + LVLCHAP + VNAVFD + TOGA + N1It's so confusing!Still not clear on bugging up and when it takes place. Searched AVSIM forum and went mad tonight. Full of tweaks and exceptions. Can somebody explain consistently?Appreciated !Thanks!Jonathan


Jonathan Sacks

Dell XPS Gen 4, Pentium IV Northwood extreme 3.8Ghz, 3Ghz RAM, eVGA 7900 GTO,

12 GoFlight modules plus MCP-PRO AP and EFIS, GF pedestal, CH rudder pedals,

CH throttle quadrant, 42" LG LED, 24" DELL LCD, Windows XP, FS2004, FSUIPC 3.96

FS Autostart 1.1 (Build 11), FS Navigator 4.6, UT, FE, GE, REX, PMDG, Level-D, PSS, etc.

Share this post


Link to post

Hi Jonathon!My take on a consistent, by-the-book departure:1. Advance throttles to 40% and let them stabilise2. TO/GA button3. Ensure thrust is set - call 'Power set'4. At 65kts view the F/D bars moving to upright5. V1 and the V1 call just prior to6. Rotate7. V2 call with pitch moving up to meet the F/D bars8. Positive rate of climb, gear up9. Passing 400ft Autopilot following a lateral mode MAY be engaged9. I believe it's at >1500ft, select the N1 thrust mode, keeping Climb thrust and varying pitch to keep ~ V2+20 (provided V2 set in the speed window during preflight)10. Above 3000ft (flap retraction altitude here), and at ~ V2 + 20 call for and set flaps 1 (from 5)11. Bug up, that is wind up / set the speed window to the speed that corresponds to the -UP bug on the Speed Tape12. Passing through the -1 bug, set flaps up13. Start switches OFF, Landing Gear UP & OFF, Flaps UP, NO LIGHTS, Autobrakes OFF14. Engage VNAV or similar pitch mode as desiredOf course I'm not a real 737 driver, and those who remember more or indeed know more, please do enlighten us.Regards,Geoffrey Balean YSCBVirgin Blue Virtual - VOZ9211STU3 Controllerhttp://www.voz.ozflight.com.au/images/pmdgforumsignature.png


Geoff Balean

Share this post


Link to post

>>Bug Up manually to UP>AP + LVLCH>AP + VNAV>FD + TOGA + N1>>It's so confusing!>>Still not clear on bugging up and when it takes place. >Searched AVSIM forum and went mad tonight. Full of tweaks and>exceptions. Can somebody explain consistently?>>Appreciated !>>Thanks!>>Jonathan>>Jonathan,It's in the PMDG Documentation, Normal Procedures, After Takeoff Procedure Explained. It says," Above 1000 feet, set flaps up maneuvering speed. Verify climb thrust is set and proper mode is annunciated."The "set flaps up maneuvering speed" is the same as "Bug Up". "Bug Up" what the flying pilot would say to the non-flying pilot to accomplish this. It would be better if the PMDG documentation said," Passing 1000 feet AFE, push N1 and set flaps up maneuvering speed Verify climb thrust is set and proper FMA mode's are annunciated."One more thing, the documentation gives the impression that the autopilot should be engaged passing the minimum autopilot engagement altitude which is 400 feet AGL. It's better to clean the airplane up first and then engage the autopilot after passing 3000 feet. Make sense?Floyd


John Floyd

Share this post


Link to post

Geoff and Floyd:Good stuff. Now I can print and file. Thanks for posting.Yay!Jonathan


Jonathan Sacks

Dell XPS Gen 4, Pentium IV Northwood extreme 3.8Ghz, 3Ghz RAM, eVGA 7900 GTO,

12 GoFlight modules plus MCP-PRO AP and EFIS, GF pedestal, CH rudder pedals,

CH throttle quadrant, 42" LG LED, 24" DELL LCD, Windows XP, FS2004, FSUIPC 3.96

FS Autostart 1.1 (Build 11), FS Navigator 4.6, UT, FE, GE, REX, PMDG, Level-D, PSS, etc.

Share this post


Link to post

I just thought of another issue on climbout:Why is it actually necessary to push the N1 button at 1500 AGL or whatever the thrust reduction ALT is? If you have set up the FMC for a flight, but are taking off and flying manually up to say 3000 AGL and prior to engaging LNAV+VNAV, does not the FMC automatically reduce your thrust to CLB/CLB1/CLB2, thereby obviating the need to push the N1 button?Thanks!JS


Jonathan Sacks

Dell XPS Gen 4, Pentium IV Northwood extreme 3.8Ghz, 3Ghz RAM, eVGA 7900 GTO,

12 GoFlight modules plus MCP-PRO AP and EFIS, GF pedestal, CH rudder pedals,

CH throttle quadrant, 42" LG LED, 24" DELL LCD, Windows XP, FS2004, FSUIPC 3.96

FS Autostart 1.1 (Build 11), FS Navigator 4.6, UT, FE, GE, REX, PMDG, Level-D, PSS, etc.

Share this post


Link to post

>>I just thought of another issue on climbout:>>Why is it actually necessary to push the N1 button at 1500 AGL>or whatever the thrust reduction ALT is? If you have set up>the FMC for a flight, but are taking off and flying manually>up to say 3000 AGL and prior to engaging LNAV+VNAV, does not>the FMC automatically reduce your thrust to CLB/CLB1/CLB2,>thereby obviating the need to push the N1 button?>>Thanks!>>JSJS,Your right,If you see "N1" for A/T after takeoff on the FMA, then of course there is no need to push the N1 button now because it engaged automatically. Calling for "N1" and "flaps up maneuvering speed" above 1000 feet is a standard Boeing procedure with this airplane. Airlines may develop their own modified versions.Floyd


John Floyd

Share this post


Link to post

Thanks, Floyd. Jonathan


Jonathan Sacks

Dell XPS Gen 4, Pentium IV Northwood extreme 3.8Ghz, 3Ghz RAM, eVGA 7900 GTO,

12 GoFlight modules plus MCP-PRO AP and EFIS, GF pedestal, CH rudder pedals,

CH throttle quadrant, 42" LG LED, 24" DELL LCD, Windows XP, FS2004, FSUIPC 3.96

FS Autostart 1.1 (Build 11), FS Navigator 4.6, UT, FE, GE, REX, PMDG, Level-D, PSS, etc.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    2%
    $540.00 of $25,000.00 Donate Now
×
×
  • Create New...