Learn how to fly the PMDG 777 in MSFS 2020, from cold-and-dark setup and CDU programming to take-off, VNAV descent and landing.
To fly the PMDG 777 in MSFS 2020, power and align the aircraft, load fuel and payload, programme the CDU, complete the take-off performance entries, then use TO/GA, LNAV and VNAV for departure. Plan the descent before top of descent, configure early, and land manually or with a properly monitored autoland.
What should I set up before flying?
Use a clean MSFS 2020 control profile and disable assistance features that move the flight controls, trim, throttles or rudder. Duplicate throttle assignments are a common cause of moving thrust levers, rejected TO/GA commands and unstable autothrottle behaviour.
- Assign each throttle axis only once and check that both engines reach idle and take-off thrust.
- Use a small dead zone if an axis flickers near idle.
- Confirm that spoilers, flaps, brakes and reverse thrust are not bound to conflicting controls.
- Set PMDG failure options to normal operation while learning the aircraft.
Treat the PMDG CDU as the source of truth for navigation. A route selected on the MSFS World Map does not guarantee that the aircraft's active route, performance pages or departure procedure have been completed.
Should I start cold and dark or on the runway?
Start cold and dark when learning the systems, but use a ready-for-take-off state when practising handling, approaches or landings. A runway start saves time, although you must still verify the route, MCP, trim, V-speeds and take-off configuration.
For the full electrical, APU and engine sequence, follow our switch-by-switch PMDG 777 cold-and-dark procedure. Do not move the aircraft during alignment; if the navigation displays remain unusable, work through the separate ADIRU and CDU position-initialisation checks.
How do I fly a complete PMDG 777 flight?
Load the aircraft and choose its state. For a first flight, use clear weather, daylight and a long runway. Allow the PMDG systems to finish loading before operating switches or changing the panel state.
Load fuel and payload. Use the PMDG tablet or aircraft menus provided for fuel, passengers and cargo. Do this before completing performance calculations so that gross weight, centre of gravity and take-off data are based on the final load.
Programme the CDU route. Enter the origin, destination, departure runway and route, then select the appropriate departure, arrival and approach. Activate and execute the route, and inspect every page of the LEGS display rather than assuming an imported plan is valid.
Resolve genuine route discontinuities, but do not automatically join every pair of legs. A vector segment or discontinuity after a departure or arrival may be intentional and may require heading control before you rejoin LNAV.
Complete performance initialisation. Enter or verify the cruise altitude, cost index, reserves and required weight data. On the take-off pages, select the flap setting, confirm the runway and thrust option, calculate the V-speeds, and set the indicated stabiliser trim.
Configure the MCP. Turn on both flight directors, arm the autothrottle and set V2, the cleared initial altitude, and the required heading or track. LNAV and VNAV may be armed before departure when the active route and departure are valid; otherwise use heading and a suitable vertical mode until interception.
Start, taxi and complete the take-off check. After engine start, verify flight controls, flaps, trim, spoilers, brakes and the EICAS messages. Taxi slowly because the 777 responds late to nose-wheel inputs and continues rolling after thrust is reduced.
Use TO/GA for take-off. Line up, stabilise both engines at intermediate thrust, then press a cockpit TO/GA switch or your correctly assigned TO/GA control. Confirm that take-off thrust is set and that no configuration warning appears. At VR, rotate smoothly and follow the flight director rather than aiming for a fixed pitch angle.
Clean up and engage the autopilot. Select gear up after a positive climb, follow the cleared lateral mode, and retract the flaps on the indicated manoeuvre-speed schedule. Engage the autopilot once safely airborne and stable, then check the flight-mode annunciator to confirm what LNAV, VNAV and the autothrottle are actually doing.
Monitor climb and cruise. VNAV follows the CDU profile, but the MCP altitude still limits where the aircraft may climb or descend. Reset it as clearances change, check fuel predictions and watch for speed or altitude constraints. On a long flight, use the FMC predictions and MCP correctly when making PMDG 777 step climbs.
Prepare the descent before top of descent. Select and verify the arrival and approach, inspect altitude constraints, enter forecast data where available, set landing minima, and obtain VREF from the approach reference page. Set the cleared lower MCP altitude before top of descent; otherwise VNAV will remain at cruise altitude even when its calculated descent point is reached.
Configure for the approach and landing. Reduce speed early, select flaps in stages, lower the gear and arm the speedbrake and appropriate autobrake setting. For an ILS, verify the runway, frequency, course and identifier, intercept from a sensible angle and from below the glideslope, then select APP. Fly the flare manually or monitor the complete autoland sequence.
Why will LNAV or VNAV not engage?
LNAV and VNAV usually refuse to engage because the route, performance data, intercept geometry or MCP altitude does not permit the requested mode. Read the flight-mode annunciator first; the illuminated button only shows a selection, while the annunciator shows the active and armed modes.
| Symptom | Likely cause and fix |
|---|---|
| LNAV will not arm | Activate and execute the route, remove unintended discontinuities, and confirm that the first active leg is ahead of the aircraft. Use heading mode to establish a reasonable intercept if necessary. |
| VNAV is unavailable | Complete the performance and take-off pages, including cruise altitude and required weight data. Check for invalid or impossible constraints on the LEGS pages. |
| Aircraft will not climb | The MCP altitude may still be set to the previous clearance. Select the new cleared altitude and confirm the active vertical mode. |
| Aircraft passes top of descent | A lower MCP altitude was not set, the route was changed, or VNAV PATH was not available. Correct the clearance altitude and recheck the descent page rather than forcing a steep descent close to the airport. |
| No V-speeds appear | The runway, flap setting, weight or take-off performance entries are incomplete. Recalculate and select the displayed speeds before setting the MCP. |
| TO/GA does nothing | Check that the autothrottle is armed and remove conflicting throttle or TO/GA assignments. Confirm that both engines and the flight controls have finished initialising. |
| ILS does not capture | Verify the selected runway and ILS identifier, approach from within the localiser beam, and intercept the glideslope from below. Selecting APP cannot recover an unsuitable intercept automatically. |
Can the PMDG 777 autoland in MSFS 2020?
Yes, the PMDG 777 can autoland when a valid ILS, suitable aircraft configuration and required automatic-flight status are available. APP mode alone does not confirm an autoland; monitor localiser and glideslope capture, the displayed autoland status, and the FLARE and ROLLOUT mode indications.
If the expected status or mode annunciations do not appear, disconnect and land manually if the approach is stable, or go around. Our detailed PMDG 777 approach, manual landing and autoland procedure covers the setup and monitoring points without repeating the entire flight.
What is the best way to learn the PMDG 777?
Learn the PMDG 777 in layers rather than attempting a long cold-and-dark flight first. We recommend three short sessions:
- Practise take-off, basic MCP modes, manual handling and landing from a runway-ready state.
- Fly a short route using a complete CDU setup, LNAV, VNAV and an ILS approach.
- Add cold-and-dark preparation, realistic loading, departure and arrival procedures, step climbs and autoland monitoring.
After every mode selection, check the flight-mode annunciator. The most frequent PMDG 777 mistake is assuming the aircraft is following LNAV, VNAV or APP because a button was pressed, when a different mode is active.