How do I use the Boeing 777-200ER FMC in MSFS 2020?

To use the Boeing 777-200ER FMC in MSFS 2020, power the aircraft, initialise its position, enter the route and procedures, complete PERF INIT, THRUST LIM and TAKEOFF REF, then check LEGS and press EXEC. Set the MCP altitude and arm LNAV/VNAV; the FMC guides the autopilot rather than flying the aircraft itself.

MSFS 2020 does not include a stock 777-200ER, so the available pages and functions depend on your add-on. The CDU is the keypad and display through which you operate the FMC; simmers commonly call the whole unit the FMC.

Which Boeing 777-200ER FMC implementation do I have?

Your aircraft's system depth determines which parts of the normal Boeing procedure will work.

• Full-depth simulation: Position initialisation, route entry, performance calculations, take-off data, VNAV and route modification should all be available.
• Default-avionics derivative: The aircraft may obtain its route from the MSFS World Map and omit genuine 777 pages or calculations. Missing functions can be an add-on limitation rather than an error.
• Simplified aircraft: Some CDU buttons or pages may be decorative. If entries never reach the scratchpad or page keys do nothing, check the features documented for that aircraft.

Do not copy a PMDG-specific key sequence blindly into another 777-200ER. The general workflow is the same, but route importing, weight entry and VNAV modelling can differ.

How do I program the 777-200ER FMC before take-off?

Enter data with the CDU keypad so it appears in the scratchpad, then use the adjacent line-select key to place it in the required field. If the scratchpad shows an error, clear the message and correct the entry rather than repeatedly pressing the line-select key.

1. Power the aircraft and align the IRS. Connect electrical power, place the inertial reference selectors in NAV and allow alignment to finish if the add-on models it. A route can sometimes be entered during alignment, but LNAV position data may remain unavailable until it completes.
2. Check the IDENT page. Confirm that the FMC recognises the intended aircraft model and displays navigation data. This is also a quick way to detect a simplified or incomplete FMC implementation.
3. Initialise the position. On POS INIT, enter the departure airport as the reference airport. In a detailed 777, copy the displayed GPS position into SET IRS POS; simplified aircraft may perform this automatically.
4. Create or load the route. On RTE, enter the departure and destination ICAO identifiers. Add waypoints directly, or enter an airway under VIA followed by its exit fix under TO. If the add-on supports World Map, company-route or external-plan importing, use the method intended for that model; our detailed route-entry and import instructions explain how to check the resulting route.
5. Select departure and arrival procedures. Open DEP/ARR and choose the runway, SID and transition that match the clearance. The arrival, STAR and approach can be entered before departure or added later. Avoid entering the same procedure in both the World Map and CDU if that produces duplicated fixes.
6. Inspect every LEGS page. Check waypoint order, bearings, altitude restrictions and the route line on the navigation display. A ROUTE DISCONTINUITY is not automatically an error: close it only when the clearance or published procedure connects those legs. Copying the next fix over every discontinuity can create unsafe shortcuts.
7. Activate and execute the route. Select ACTIVATE on RTE, then press EXEC. Any later modification also needs EXEC; an illuminated EXEC key means the change is staged but not yet part of the active route.
8. Complete PERF INIT. Enter the accepted weight value, reserves, cost index and cruise altitude. Depending on the add-on, zero-fuel weight or gross weight may populate the other field automatically. Make sure the aircraft and FMC are using the expected weight units.
9. Set thrust and take-off data. On THRUST LIM, use normal take-off thrust unless you have valid data for a derate or selected temperature. On TAKEOFF REF, set the flap configuration, confirm the centre of gravity, select or enter V1, VR and V2, and set the indicated stabiliser trim.
10. Prepare the MCP. Set the cleared initial altitude plus the required heading and speed. Turn on the flight directors, arm the autothrottle and arm LNAV or VNAV only where the add-on and departure procedure support it. Pressing EXEC commits FMC data; it does not engage the autopilot.

What should I check before take-off?

The aircraft is ready for FMC-guided departure only when the route, performance data and MCP agree with one another.

• The departure runway and SID match the clearance and the runway actually in use.
• The route is active, the EXEC light is out and no unintended discontinuity remains near departure.
• PERF INIT contains valid weight, reserves, cost index and cruise altitude data.
• Take-off flaps, V-speeds and stabiliser trim agree with TAKEOFF REF.
• The MCP altitude is set to the cleared altitude, not automatically to the final cruise level.
• The flight directors, autothrottle and intended lateral and vertical modes are armed.

Why will LNAV or VNAV not engage?

LNAV needs an active route and usable aircraft position, while VNAV also needs complete performance data and a valid vertical profile.

• No active route: Return to RTE and confirm that ACTIVATE and EXEC were completed.
• Unexecuted modification: Check for an illuminated EXEC key after changing a runway, procedure, waypoint or restriction.
• Invalid active leg: Inspect the first LEGS page. The aircraft may be too far from the selected leg or pointed away from a practical intercept.
• Incomplete PERF INIT: Check weight, reserves, cost index and cruise altitude. Missing take-off data can also prevent normal VNAV behaviour.
• IRS not aligned: LNAV cannot follow the route reliably without a valid position.
• MCP conflict: VNAV cannot command a climb above, or a descent below, the selected MCP altitude.
• Add-on limitation: Some simplified 777 aircraft require different mode handling or do not reproduce the full Boeing logic.

Watch the flight mode annunciator on the primary flight display rather than trusting illuminated buttons. Our explanation of MCP modes, flight directors and FMA verification covers the division between FMC guidance and autopilot control. For the PMDG aircraft specifically, use our PMDG 777 VNAV troubleshooting checklist when VNAV pages or predictions disappear.

How do I change the FMC route in flight?

Use LEGS for direct-to changes and DEP/ARR for revised procedures, then review the modified route before pressing EXEC.

For a direct-to, select the desired waypoint into the scratchpad and place it at the active-leg position, but first check which intermediate fixes this will remove. When changing an arrival or approach, inspect every LEGS page for duplicated fixes, sharp turns, new discontinuities and altered altitude restrictions. Keep the modification unexecuted until it matches the clearance.

How do I use the FMC for descent and approach?

Before top of descent, select the expected arrival and approach, verify its constraints, complete the descent data available in your add-on and set the MCP altitude when cleared to descend.

VNAV should follow the calculated path only when the route and performance predictions are valid. Monitor the FMA, speed and path indication; use speedbrake when required rather than forcing the aircraft down with an unsuitable vertical mode.

Set the landing flap and VREF on APPROACH REF, applying an appropriate wind correction where required. ILS tuning may be automatic in a detailed 777 but manual or simplified in another add-on. The full 777 arrival, ILS and landing workflow covers the remaining approach setup.

What do common 777 FMC messages mean?

Most FMC messages identify missing data, an uncommitted change or a route that the computer cannot calculate as entered.