Learn the Boeing 737 take-off sequence: performance setup, TO/GA, V1/VR rotation, flap retraction and fixes for common simulator errors.
To take off in a Boeing 737, calculate and enter the correct V-speeds, thrust, flap setting and trim; line up, stabilise the engines, select TO/GA, maintain the centreline, rotate smoothly at VR, raise the gear after a positive climb, then accelerate and retract flaps on the scheduled speed marks. Never use guessed numbers.
For real-world aviation, a 737 take-off must be performed by a qualified crew using the operator’s procedures and approved performance data. The sequence below is intended to explain the procedure and help pilots flying realistic 737 simulations.
What must be set before a Boeing 737 take-off?
A safe 737 departure begins with performance calculation and configuration, not with advancing the thrust levers. Weight, runway length and condition, wind, temperature, pressure, slope, obstacles, engine anti-ice and aircraft configuration can all change the required thrust and speeds.
- Route and departure: Check the runway, departure procedure and first route leg in the FMC. The first leg must make sense on the navigation display; an incorrect runway or discontinuity can send LNAV in the wrong direction.
- Take-off performance: Obtain the correct thrust setting and V1, VR and V2 from the aircraft’s approved performance system or the add-on’s performance tool. Enter and verify them in the CDU rather than copying values from another flight. Our 737 FMC programming walkthrough covers the route and performance pages without duplicating them here.
- Flaps and trim: Set the calculated flap position and stabiliser trim. Flaps 5 is common, but it is not a universal setting; runway, weight and obstacle requirements can dictate another choice. See our explanation of how to choose a take-off flap setting.
- Mode Control Panel: Set the cleared altitude, initial heading or course, flight directors and the required initial speed. Arm the autothrottle. Arm LNAV or VNAV only when the route, performance data and aircraft procedure support it.
- Aircraft configuration: Confirm flight controls checked, speedbrake down, autobrake set to RTO, trim in the take-off range and flight instruments agreeing. Complete the model-specific before-take-off checklist.
Can I use the same V-speeds and flap setting every time?
No. V1 is the take-off decision speed, VR is the rotation speed and V2 is the take-off safety speed, and all three change with the departure conditions. Reusing yesterday’s numbers can produce a premature rotation, excessive runway use or inadequate climb performance.
The same rule applies to thrust. Do not select an arbitrary N1 percentage because it worked on another flight. Use the calculated full-rated or reduced-thrust setting and verify that the engines reach the commanded take-off thrust.
How do you perform the take-off roll and rotation?
Use TO/GA to command the calculated take-off thrust, then steer with rudder and rotate smoothly at VR. A normal simulator sequence is:
- Line up and verify the runway. Confirm the runway designation, heading, departure clearance and initial altitude. Centre the aircraft before applying take-off thrust.
- Stabilise the engines. Bring both engines to approximately 40% N1, or the value specified by that 737 model, and allow them to stabilise. Press TO/GA and check that both engines advance evenly to the commanded thrust.
- Hold the centreline. Use rudder pedals for directional control as speed increases. Apply appropriate into-wind aileron during a crosswind take-off and reduce it progressively; do not steer at high speed with a nosewheel tiller assignment.
- Monitor the acceleration. Verify take-off thrust and check that both airspeed indications are increasing. At the 80-knot call, confirm the instruments agree. A rejected take-off is governed by defined criteria, not by every minor warning.
- Continue through V1. In normal operations the crew removes its hand from the thrust levers at V1 and continues unless the aircraft cannot fly. Simulator callouts may be missing, so watch the speed tape without losing directional control.
- Rotate at VR. Apply smooth back pressure at roughly 2–3 degrees of pitch per second. An initial target near 15 degrees is typical, but follow the flight director and avoid snapping the nose upwards; rapid or excessive rotation risks a tailstrike.
- Establish the climb. Follow the flight director and keep the aircraft near the commanded take-off speed. Once a positive rate of climb is confirmed, select gear up.
A common mistake we see in simulators is pressing TO/GA from idle and then trying to correct an uneven thrust increase during the roll. Stabilising the engines first makes asymmetric acceleration less likely and gives time to detect a configuration warning.
When should the gear and flaps be retracted?
Raise the landing gear after a confirmed positive climb, but leave the flaps in their take-off position until the planned acceleration height. Thrust-reduction height and acceleration height are separate settings and need not occur at the same altitude.
At thrust-reduction height, the aircraft or crew selects climb thrust. At acceleration height, lower the nose enough to accelerate and retract the flaps one scheduled stage at a time as the relevant manoeuvring-speed marks are reached. Do not move the lever straight to up immediately after lift-off.
Engage the autopilot only above the minimum engagement altitude specified for the aircraft and procedure. Many normal 737 procedures use 400 feet above ground as the earliest point, but the applicable aircraft documentation or add-on procedure takes precedence. Keep watching the flight mode annunciator after every automation selection.
Why will the 737 not rotate or follow the departure?
Most failed simulator take-offs come from incorrect performance data, trim, control calibration or automation setup rather than an aerodynamic fault.
| Symptom | Likely cause | What to check |
|---|---|---|
| Take-off configuration horn sounds | Flaps, stabiliser trim, speedbrake or another take-off item is incorrectly set | Stop while still at low speed, reset the configuration and complete the checklist; do not silence or ignore the warning |
| Aircraft will not rotate at VR | Wrong trim, bad weight or centre-of-gravity entry, incorrect V-speeds, control lock or calibration problem | Recalculate performance, verify trim and confirm the elevator reaches full travel in the simulator’s control display |
| Aircraft lifts off too early or pitches sharply | Rotation started before VR, excessive control input or excessive nose-up trim | Use the calculated VR and rotate progressively rather than pulling abruptly |
| TO/GA does not command thrust | Autothrottle not armed, engines not stabilised, incorrect add-on state or unmapped TO/GA control | Check the flight mode annunciator, throttle assignment and aircraft-specific TO/GA method |
| LNAV or VNAV will not engage | Invalid FMC route, missing performance data, unsuitable first leg or MCP altitude restriction | Use our pre-departure LNAV and VNAV fault checks before attempting another take-off |
| Aircraft climbs slowly with high pitch | Wrong thrust, premature rotation, excessive weight or failure to accelerate and retract flaps | Verify commanded N1, follow the flight director and use the planned acceleration schedule |
Does the procedure change between 737 variants and add-ons?
The basic aerodynamic sequence remains the same, but cockpit flows, performance tools and automation details differ between the 737 Classic, NG and MAX families. Simulator aircraft also range from simplified default models to add-ons that reproduce configuration warnings, derated thrust, FMC logic and flight-mode behaviour in far greater depth.
Use the checklist supplied with the exact aircraft rather than transferring button sequences between products. For the PMDG 737 NGX in FSX, our sequential cockpit-to-cruise PMDG tutorial shows how the preparation and take-off stages fit into a complete flight.