Skip to content
General 14 min read 1.6k views

Boeing 737 descent: how do I set up an approach?

Ian Stephens
In short

Calculate a 737 descent rate and TOD, troubleshoot VNAV in MSFS 2024 and PMDG, manage high-and-fast arrivals, and set up ILS or RNAV.

In a Boeing 737 in a general flight simulator, use approximately groundspeed × 5 for a 3° descent: 140 kt is about 700 fpm, 180 kt 900 fpm and 250 kt 1,250 fpm. The planning equivalent is 3 NM per 1,000 ft; if the required rate becomes excessive, slow, add track miles or go around.

These are path-planning figures, not fixed targets. A higher rate can be normal early in the descent, but a rapidly increasing required rate while the aircraft remains high and fast is a warning to stop forcing the profile. Request vectors, extend the downwind or discontinue the approach before it becomes unstable.

Exact FMC prompts, button labels, flight-mode logic and autopilot capabilities differ between default 737s, the PMDG 737-800 and other study-level models. Treat the flight-mode annunciator and the documentation for your particular aircraft as the final authority.

What is the correct 737 descent rate?

A 3° descent path requires roughly five times the groundspeed in feet per minute.

GroundspeedApproximate rate for 3°Typical use
140 kt700 fpmFinal approach
180 kt900 fpmApproach or intermediate descent
250 kt1,250 fpmTerminal-area descent

Use groundspeed, not indicated airspeed. A tailwind raises the rate needed to remain on the same geometric path; a headwind lowers it. Follow the actual path indication rather than holding the calculated rate when the aircraft is already above or below profile.

There is no single correct Boeing 737 or 737 MAX descent rate for an entire arrival. Idle thrust, wind, speed restrictions, level segments and aircraft weight all change it. On final, a sustained sink rate around or above 1,000 fpm deserves close attention and must meet the stabilised-approach standard being simulated.

When should you start descending in a 737?

Start approximately 3 NM before the target point for every 1,000 ft that must be lost, then account for deceleration, wind and route restrictions.

Subtract the target altitude from the present altitude, divide by 1,000 and multiply by three. From 35,000 ft to a 3,000 ft platform altitude, the basic calculation is 32 × 3, giving about 96 track miles.

  • Calculate to the next controlling restriction. Do not automatically calculate to runway elevation when a STAR crossing altitude comes first.
  • Use track miles. Distance along the programmed arrival matters more than direct distance to the airport. Specific routes, transitions and vectors can produce very different top-of-descent points.
  • Allow room to slow. Around 10–15 NM can be a useful initial allowance for reducing from 250 kt towards approach speed, but do not add it twice if the FMC profile already includes deceleration.
  • Correct for wind. A strong tailwind usually requires an earlier descent. Forecast wind errors can also move the calculated TOD after descent has begun.

Our fuller explanation of the 3:1 descent-planning rule and TOD adjustments covers speed restrictions, wind and level segments in more detail.

What should be set before top of descent?

Before TOD, verify the route, restrictions, approach data, navigation aids and the MCP altitude that will permit the aircraft to descend.

  1. Brief the arrival and approach. Confirm the runway, STAR, transition, final course, platform altitude, minima and missed approach. Loading the right runway with the wrong transition is a common cause of unexpected turns.
  2. Inspect every FMC leg. Check waypoint order, discontinuities, speed and altitude constraints, duplicate fixes and the connection between the STAR and approach. Do not remove a discontinuity until you know which legs should be joined. Use our step-by-step 737 FMC setup and route-checking guidance if the arrival is not sequencing correctly.
  3. Enter relevant descent data. Add forecast winds, transition-level information and approach data where the model supports them. Change from standard pressure to local QNH at the applicable transition level.
  4. Set the cleared MCP altitude. VNAV will not normally descend below the selected altitude. Without simulated ATC, select an altitude compatible with the next published constraint rather than winding the window straight to runway elevation without checking the route.
  5. Prepare landing data. Set the landing flap, VREF and applicable wind additive, minima and autobrake. Verify ILS tuning or the RNAV procedure before workload increases.

Why does the Boeing 737 MAX not descend automatically at TOD in MSFS 2024?

At TOD in Microsoft Flight Simulator 2024, the 737 MAX usually remains level because the MCP altitude, active vertical mode, route state or a constraint is preventing the descent.

  1. Check the MCP altitude first. It must be below the present altitude and consistent with the clearance or next restriction. Reaching TOD does not give VNAV permission to descend through the altitude selected on the MCP.
  2. Confirm VNAV and read the FMA. Pressing VNAV is not enough; inspect the active pitch mode on the primary flight display. An active mode such as VNAV PTH or VNAV SPD indicates different behaviour from ALT HOLD. The FMA, not the illuminated button alone, tells you what the aircraft is doing.
  3. Execute pending route modifications. A changed STAR, runway, direct-to or constraint left in a modification state may not be used for active guidance. Confirm that the intended route has actually been executed.
  4. Verify the active route leg. The aircraft needs a valid, sequenced leg ahead. A discontinuity, route end, vectors leg, duplicate waypoint or incorrect active leg can prevent a usable vertical path from being calculated.
  5. Inspect altitude constraints. A hard altitude, an incorrectly entered restriction or a level segment may intentionally hold the aeroplane. Compare the LEGS-page values with the chart before deleting anything.
  6. Reassess TOD after shortcuts. A direct-to or ATC shortcut removes track miles. The TOD may move behind the aircraft, disappear temporarily or be recalculated with the aeroplane already high. Add track miles or use another authorised descent mode rather than expecting the original marker to remain valid.
  7. Use altitude intervention only when appropriate. Some 737 models provide ALT INTV or an equivalent altitude-intervention action to initiate an early descent or remove a limiting constraint. Its effect varies: it may start descent, advance to another constraint or delete a restriction. Do not press it blindly.

Button names and supported logic differ between 737 MAX implementations, 737 NG add-ons and simplified default aircraft. If the model does not reproduce full Boeing VNAV or altitude-intervention logic, selecting LVL CHG or a controlled vertical speed may be the reliable solution after confirming that the lower altitude is authorised.

How do I know whether the PMDG 737-800 descent is on schedule?

In the PMDG 737-800 and comparable study-level 737s, verify the LEGS-page constraints and TOD mathematically, then monitor path deviation and the active FMA throughout the descent.

  1. Check the LEGS page. Confirm that each altitude and speed restriction matches the procedure and that the active leg is sensible. A valid-looking TOD is not useful if it was calculated from the wrong transition or constraint.
  2. Cross-check with 3:1. If 9,000 ft must be lost before a 3,000 ft restriction, expect about 27 NM before allowing for slowing or level flight. A large disagreement with the displayed TOD should be investigated before descent.
  3. Watch path deviation and the FMA. Do not assume VNAV is descending merely because VNAV was selected earlier. Confirm the active vertical mode, thrust behaviour and whether the aeroplane is above or below the calculated path.
  4. Recheck after every route change. Directs, shortcuts, runway changes and vector legs alter the available track miles. Recalculate rather than chasing a stale profile.
  5. Choose the correction that fits the problem. Speed intervention can change the commanded speed while retaining VNAV where supported. LVL CHG gives direct speed-controlled descent towards the MCP altitude. A modest V/S correction is useful when you need a predictable temporary rate, but it requires continuous speed monitoring.
Mode or controlUse it whenWatch for
VNAVThe active route, winds and constraints are validA shortcut or bad constraint moving the vertical path
Speed interventionYou need direct MCP speed control without immediately abandoning VNAVChanging speed alone does not restore missing track miles
LVL CHGYou need a straightforward descent while pitching for selected speedLeaving the FMC path and arriving high if the mode is selected too late
V/SYou need a small, measured correction or are using a simpler add-onOverspeed in a steep descent or decaying speed with a shallow rate

How should speed, flaps and landing gear be managed?

Configure progressively and reduce speed before final intercept, because a 737 does not slow efficiently while descending steeply.

  1. Meet the terminal speed restriction. Cross 10,000 ft at 250 kt or less unless the procedure or ATC instruction permits otherwise.
  2. Slow before base or final. Follow the modelled manoeuvring-speed bugs and flap placard limits. Flap 1 followed by flap 5 is common, but the correct speeds depend on weight and the particular 737.
  3. Add landing drag in sequence. Lower the gear and select further flap at the procedure’s normal points, not as an emergency response to a badly planned descent.
  4. Establish final speed early. Fly the calculated VREF plus the applicable additive and avoid major configuration, thrust or pitch changes near the stabilisation gate.

Flap 30 is a routine landing selection in many 737 procedures. Flap 40 produces more drag and a different speed and thrust picture, but it should be selected because the landing calculation or procedure calls for it—not simply to rescue an excessive-energy approach.

How do you recover when a 737 descent is off schedule?

An off-schedule descent should be corrected while there is still enough height and distance to regain a stable approach without excessive pitch, speed or configuration changes.

High and fast recovery

A high-and-fast aeroplane needs less energy, more distance or both; a steep dive is not the answer.

  1. Confirm the remaining restriction and track miles. Make sure the problem is real and not caused by reading direct distance instead of distance along the arrival.
  2. Reduce speed before increasing the descent rate. If possible, level briefly or use a less aggressive descent while the speed comes back. Descending faster often makes slowing harder.
  3. Use speedbrake early. Deploy it while clean or lightly configured, within the modelled limitations, and monitor buffet and speed. Retract it before final landing configuration unless the aircraft’s documented procedure permits otherwise.
  4. Use the gear only at an appropriate point. Landing gear provides strong, predictable drag, but it must remain within its extension speed and should fit a deliberate configuration plan.
  5. Do not dump additional flap as a last-minute fix. Flap limits can be exceeded, and a rushed sequence creates a high-workload, unstable final even if the speed briefly appears correct.
  6. Create track miles. Ask for vectors, a wider base or an extended downwind. Without simulated ATC, fly a safe extension rather than attempting to force the aeroplane down.
  7. Abandon the recovery when the stable gate is no longer achievable. If the aircraft reaches the final approach fix high, fast or incompletely configured, go around.

Low, below path or losing speed

A low or below-path aeroplane needs a reduced descent rate and appropriate thrust, not more drag.

  1. Identify the actual error. Compare altitude with the next published restriction and the path indicator. Being below the FMC path is different from violating a minimum altitude.
  2. Close the speedbrake and add thrust. Reduce the selected vertical speed or level temporarily so the path can descend towards the aeroplane.
  3. Preserve speed and configuration. Do not continue extending flap while speed is decaying. Once established on final, use small thrust and pitch corrections rather than abrupt configuration changes.
  4. Rejoin from below. For an ILS or IAN glidepath, maintain the cleared or published intercept altitude and allow capture from beneath. Do not dive farther or make an aggressive climb to chase the pointer.
  5. Go around if the approach remains unstable. Being low, slow or outside the protected vertical profile is not cured by pressing APP or selecting more automation.

How do you set up and capture a 737 ILS approach?

For an ILS, verify the frequency and front course, intercept the localiser at a shallow angle, and capture the glideslope from below at the published platform altitude.

  1. Verify the ILS. Confirm the frequency, identifier and runway. Auto-tuning does not remove the need to check the signal against the approach information.
  2. Set the published front course. The course is the runway-aligned inbound ILS course, not the heading being flown during the intercept.
  3. Intercept the localiser sensibly. An intercept angle of roughly 20–30° is easier for the autopilot to capture than crossing the beam at a large angle.
  4. Approach the glideslope from below. Remain at the published intercept altitude until capture. Do not descend through that altitude to chase a glideslope from above.
  5. Arm APP and read the FMA. Confirm localiser capture followed by glideslope capture. An armed indication is not the same as an active mode.
  6. Set the missed-approach altitude at the correct point. This is commonly done after glideslope capture, but follow the checklist for the model and procedure being simulated.

Our complete 737 ILS sequence covers tuning, course selection, APP mode, configuration and FMA monitoring without duplicating every ILS step here.

What about the COURSE selectors?

For an ILS, set the published inbound front course; study-level models may require both course selectors to agree for dual-channel or autoland logic.

The selected course does not steer the aircraft onto the localiser by itself, and it should not be confused with the intercept heading. On an RNAV approach there is normally no ILS frequency to tune; use the charted final course as a cross-check and set it only where the aircraft’s procedure calls for it.

What if the glideslope will not capture?

A failed glideslope capture is commonly caused by approaching from above, using the wrong frequency or runway, arming APP too late, selecting the wrong navigation source or intercepting with excessive speed and angle.

Level at an authorised altitude and re-establish below the beam if enough distance remains. Otherwise request another vector or go around. Never descend below a published altitude merely to make the pointer move towards the centre.

What changes for a 737 RNAV approach?

An RNAV approach uses the programmed route and supported FMC guidance rather than an ILS signal, so the waypoint sequence, vertical constraints and available approach modes must be verified carefully.

Guidance implementationExpected indicationsAPP use
LNAV/VNAVLNAV laterally with a VNAV vertical mode such as VNAV PTH where supportedAPP may not be required; follow the aircraft procedure
Integrated Approach NavigationFAC for lateral guidance and G/P for vertical guidanceAPP is normally used to arm supported FAC and G/P logic
Simplified simulationLNAV or GPS lateral guidance with manually managed V/SAPP may do nothing useful without modelled RNAV approach logic
  1. Verify the final sequence. Check that the named final-approach waypoint or fix, runway waypoint and missed-approach legs appear in the correct order, with no unexplained discontinuity.
  2. Check constraints and minima. Confirm the published altitude at the final-approach fix and set barometric minima where the aircraft models them.
  3. Review temperature requirements. Baro-VNAV procedures may contain temperature limits or require published cold-temperature corrections. Enter approach temperature or corrections only where the procedure and add-on support them.
  4. Join the vertical path from below. For FAC/G/P guidance, establish on the final course at or below the path before capture. With LNAV/VNAV, avoid diving from above to force the path back to centre.
  5. Confirm active indications. Look for active FAC and G/P or LNAV and the appropriate VNAV mode. Do not expect an ILS G/S indication where no ILS exists.
  6. Prepare the missed transition. At TO/GA, follow the flight-director command, establish a positive climb, set or confirm the missed-approach altitude and verify that the missed route sequences. LNAV may need to be selected once a valid leg exists, depending on the model.

Pressing APP simply because the aircraft is turning onto RNAV final can arm the wrong logic or nothing at all. The procedure type, FMA and aircraft documentation must agree.

What counts as a stabilised Boeing 737 approach?

A stabilised 737 approach is on the correct lateral and vertical path, at the planned speed, in landing configuration and requiring only small corrections by the chosen gate height.

  • The correct final course and vertical path are being followed.
  • Speed is at VREF plus the calculated additive, within the tolerance used by the simulated procedure.
  • Landing gear and the selected landing flap are set.
  • Thrust is appropriate and the sink rate is controlled.
  • The landing checklist and approach briefing are complete.

A widely used simulator benchmark is to be stabilised by 1,000 ft above aerodrome level in instrument conditions or 500 ft in visual conditions. Some operators use stricter criteria. Minima still apply: go around at DA, DH or the missed-approach point if the required visual reference is absent.

When a go-around is needed, use the modelled TO/GA command, follow the flight-director pitch guidance, confirm a positive climb, retract the gear and clean up on schedule while following the missed approach. Once safely established for landing, our 737 manual-landing and flare guidance continues from final configuration through touchdown.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members