Boeing 737 take-off procedure: set flaps and V-speeds, understand the 40% N1 check, rotate at VR, raise the gear and solve MCP alerts.
To take off in a Boeing 737, calculate the runway-specific thrust, V-speeds, flap setting and trim; line up, stabilise both engines near 40% N1, select TO/GA, track the centreline, rotate smoothly at VR, and select gear up only after confirming a positive rate. Then accelerate and retract flaps on schedule.
For our Aviation & Real-World Flying readers, this is an educational explanation and a realistic simulator workflow, not authority to operate a real aircraft. Real 737 crews use approved performance data, their operator's procedures and the checklist for the exact variant.
Boeing 737 take-off setup: what must be set first?
A 737 take-off begins with performance calculation and configuration, not by advancing the thrust levers. Weight, centre of gravity, runway length and condition, wind, temperature, pressure, slope, obstacles, anti-ice use and flap selection can all change the required thrust, trim and speeds.
Complete the applicable flows and challenge-response items before entering the runway. Our 737 normal checklist sequence from cockpit preparation to take-off explains how those stages fit together.
- Departure and runway: Verify the runway, departure procedure, first FMC route leg and any altitude or heading restriction. Check the route on the navigation display rather than assuming an entered procedure is correct.
- Take-off performance: Use the aircraft's approved performance source or the add-on's performance tool to obtain take-off thrust, V1, VR, V2 and stabiliser trim. Never copy numbers from a previous flight.
- Flaps and trim: Set the calculated flap position, confirm the flap indication agrees with the lever and set the stabiliser trim from the take-off data. The trim indication must be in the take-off range.
- Mode Control Panel: Set the cleared initial altitude, assigned heading or course and normally V2 in the speed window, subject to the model's procedure. Turn on both flight directors and arm the autothrottle. Arm LNAV or VNAV only after validating the route and performance entries.
- Aircraft configuration: Confirm the flight controls have been checked, spoilers are down, autobrake is at RTO, doors are closed and the take-off configuration is valid. A configuration warning during thrust application is a reason to stop at low speed and correct the setup.
If the aircraft is still cold and dark or its FMC has not been prepared, follow a complete 737 simulator workflow covering setup, taxi and automation before using this runway sequence.
Which take-off flaps does a Boeing 737 use?
Flaps 5 is common, but there is no universal Boeing 737 take-off flap setting. On many 737 NG and MAX models, certified take-off settings include Flaps 1, 5, 10, 15 and 25; available settings and performance limits must be confirmed for the exact aircraft.
Lower flap settings create less drag but normally require more runway and higher take-off speeds. Larger settings can reduce the ground run and speeds, but add drag and may limit climb performance. Runway length, obstacles, weight, temperature and engine-out climb requirements determine the correct compromise.
Do not assume that every 737 MAX take-off uses Flaps 5, or transfer an NG result into a MAX. Use the value produced by the model-specific performance calculation and make sure the CDU flap entry agrees with the physical lever.
Can I reuse the same V-speeds and N1 setting?
No. V1 is the take-off decision speed, VR is the rotation speed and V2 is the take-off safety speed; each changes with the aircraft and departure conditions.
Take-off N1 is also calculated for that flight. Full-rated thrust, a fixed derate and an assumed-temperature reduction can produce different commanded values. An arbitrary N1 percentage that worked on another runway is not valid performance data.
What is the 40% N1 check on a Boeing 737?
The 40% N1 check is an engine-stabilisation step before selecting take-off thrust, not the thrust setting used for the take-off roll. The crew advances both engines to approximately 40% N1, allows the indications to settle and checks that the engines respond evenly before pressing TO/GA.
The exact stabilisation target can vary with the 737 variant, operator procedure and simulator add-on. Treat 40% as an approximate procedural target where specified, not a number to chase while the aircraft accelerates. Once stable, select TO/GA and verify that both engines advance symmetrically to the calculated take-off limit.
Pressing TO/GA directly from idle can produce uneven spool-up and leaves less time to identify an abnormal indication. Our explanation of what the 737 TO/GA switch commands and how simulators implement it covers the thrust and flight-director logic in detail.
How do you perform a Boeing 737 take-off?
The normal sequence is to stabilise the engines, select TO/GA, maintain directional control, rotate at VR and retract the gear only after confirming a climb.
- Line up and verify the runway. Check the runway designation, magnetic heading, departure clearance and initial MCP altitude. Centre the nosewheel and complete the before-take-off checklist.
- Stabilise the engines. Smoothly advance both thrust levers to approximately 40% N1, or the value specified for that model, and allow the engines to stabilise.
- Select TO/GA. Use the cockpit switch, add-on hotspot or assigned control. Check the flight mode annunciator and confirm both engines are advancing towards the commanded take-off thrust.
- Track the centreline. Use rudder pedals as speed increases. In a crosswind, apply into-wind aileron and reduce it progressively. Do not use a nosewheel tiller assignment for high-speed steering.
- Monitor acceleration. Confirm both airspeed indications are alive and agree. At the 80-knot call, cross-check the instruments and thrust. Use the applicable rejected-take-off criteria rather than stopping for every minor message.
- Continue through V1. V1 is the decision speed, not the rotation cue. In normal operations the hand is removed from the thrust levers at V1 and the take-off continues unless the aircraft is incapable of flight.
- Rotate at VR. Apply smooth back pressure at roughly 2-3 degrees of pitch per second. An initial attitude near 15 degrees is typical, but follow the flight director and avoid an abrupt pull that could cause a tailstrike.
- Confirm positive rate and select gear up. Check that the altimeter is increasing and the vertical-speed indication shows an established climb. Do not raise the gear merely because the wheels have left the runway.
- Follow the departure. Maintain the commanded speed and flight-director guidance. At the planned acceleration height, lower the pitch as required, accelerate and retract the flaps according to the manoeuvring-speed indications.
What does “V1, rotate, positive rate, gear up” mean?
The familiar call sequence marks four separate events: the take-off decision at V1, rotation at VR, confirmation that the aircraft is climbing, and landing-gear retraction. They are not one continuous command.
A mistake we see constantly in simulators is rotating when the V1 call is heard. Wait for VR. Likewise, “positive rate” should be supported by the instruments rather than called immediately at lift-off from a momentary vertical-speed movement.
When should the 737 gear and take-off flaps be retracted?
Raise the landing gear after a confirmed positive rate, but retain the take-off flap setting until the planned acceleration height. Thrust-reduction height and acceleration height are separate values and may occur at different altitudes.
At thrust-reduction height, take-off thrust is changed to the scheduled climb thrust. At acceleration height, the aircraft accelerates towards the flap-up manoeuvring speed. Retract the flaps in scheduled stages: when at or above the manoeuvring speed for the existing setting, select the next scheduled setting and verify movement before continuing.
Do not move the lever directly from the take-off setting to UP immediately after lift-off. Premature retraction can remove needed lift and climb margin; late retraction can cause a flap overspeed or leave the aircraft climbing slowly with excessive drag.
Can the 737 autopilot be engaged during take-off?
The 737 autopilot does not control the ground roll or rotation and is engaged only after lift-off, at or above the model's minimum engagement altitude. Many 737 procedures use 400 feet above ground as the earliest point, but the aircraft documentation and operator procedure take precedence.
After selecting CMD, confirm the expected modes on the flight mode annunciator. An illuminated button alone does not prove that LNAV, VNAV or another mode has captured. See our 737 autopilot engagement and mode guidance for the post-take-off automation sequence.
Why does PMDG 737 show RESET MCP ALTITUDE after take-off?
In the PMDG 737, the RESET MCP ALT message means the selected MCP altitude is preventing VNAV from following the altitude profile expected by the FMC. During departure, this often happens after the aircraft reaches the initial cleared altitude while the FMC route expects a further climb.
Set the next altitude that ATC has actually cleared in the MCP altitude window, then verify the active and armed modes on the flight mode annunciator. The FMC cruise altitude does not override the MCP altitude, which acts as a clearance limit.
Do not wind the MCP straight to cruise altitude merely to remove the message if an altitude restriction or ATC clearance still applies. If no higher clearance has been given, remain at the cleared level. Pressing altitude intervention can alter or remove FMC constraints, so it should not be used simply as a message-clear button.
Why will the 737 not rotate or follow the departure?
Most failed simulator take-offs come from bad performance entries, incorrect trim, control assignments or an unnoticed automation mode rather than an aerodynamic fault.
| Symptom | Likely cause | What to check |
|---|---|---|
| Take-off configuration horn sounds | Incorrect flaps, stabiliser trim, spoilers or another required configuration item | Stop at low speed, correct the configuration and repeat the checklist; never ignore the warning |
| Aircraft will not rotate at VR | Wrong trim or centre of gravity, invalid V-speeds, control lock, conflicting bindings or insufficient elevator travel | Recalculate the take-off data and inspect the simulator's control-position display for full, correct elevator movement |
| Aircraft leaps off or pitches sharply | Rotation before VR, excessive nose-up trim or an abrupt control input | Verify VR and trim, then rotate progressively instead of pulling the control fully aft |
| Aircraft veers during the roll | Uneven thrust, rudder calibration, crosswind input or a tiller axis being used at speed | Stabilise both engines, check rudder and tiller assignments, and use small rudder corrections |
| TO/GA does not command thrust | Autothrottle not armed, an incorrect add-on state, unmapped TO/GA control or a hardware throttle overriding automation | Check the flight mode annunciator, TO/GA assignment and throttle-axis noise or conflicting bindings |
| LNAV does not follow the departure | Wrong runway, route discontinuity, invalid first leg or LNAV not armed or captured | Check the FMC legs against the navigation display and use heading mode if the route is not trustworthy |
| High pitch and poor acceleration | Incorrect thrust, premature rotation, excess weight or failure to begin the flap-retraction schedule | Verify commanded N1, follow the flight director and accelerate at the planned height |
Does the take-off procedure change for the 737 Classic, NG and MAX?
The broad sequence is the same, but performance figures, flap options, engine response, cockpit indications and automation details differ between 737 families. The 737 MAX does not use one special take-off flap setting or a fixed N1 value.
Use the checklist and performance tool supplied for the exact aircraft. Do not transfer PMDG 737 NG values to a MAX add-on, copy trim from a Classic, or assume that a simplified default aircraft reproduces Boeing's TO/GA and FMC logic exactly.