Learn to fly the PMDG 777-300ER in MSFS 2024: FMC setup, engine start, take-off, LNAV/VNAV, descent, landing and common fixes.
To fly the PMDG 777-300ER in MSFS 2024, load the compatible aircraft package, set fuel and payload, initialise the FMC, start the engines, configure take-off, then manage the flight with LNAV/VNAV and the MCP. The crucial habit is checking the flight-mode annunciator after every mode selection rather than assuming the aircraft obeyed.
Set up the PMDG 777 before departure
Begin with the correct Microsoft Flight Simulator 2024 package for your platform rather than manually copying an unsupported installation. If there is any doubt, check the supported PMDG packages and installation route for MSFS 2024 before troubleshooting the aircraft itself.
For a first flight, we recommend a powered gate or ready-for-taxi panel state, clear weather and a route long enough to practise the climb and descent. Use the PMDG tablet or aircraft menus for fuel and payload where provided. Finish those changes before calculating performance, because altering weight afterwards invalidates the take-off speeds, trim and landing data.
Check the following before programming:
- Your pitch, roll, rudder, throttles and toe brakes each have only one active assignment.
- Reversers, tiller or nosewheel steering and the parking brake operate correctly.
- Chocks and ground equipment are removed when required.
- AI piloting or assistance options are not moving switches and controls for you.
- The units used for fuel and weight match the values being entered.
Fly the PMDG 777-300ER step by step
A reliable first sector follows the aircraft's normal flow: configure, programme, start, taxi, take off and then engage automation only after verifying its modes.
- Load the aircraft at a gate. Set the parking brake or chocks, establish electrical power and confirm that the displays and EICAS are alive. A powered panel state removes most startup workload while you learn the FMC and autopilot.
- Set fuel and payload. Load a realistic amount for the route, then verify gross weight and centre of gravity. Do not use take-off figures copied from another flight; runway, weather, flap setting and aircraft weight all affect them.
- Start from cold and dark if desired. The broad order is battery and external power or APU, ADIRU alignment, fuel and hydraulic configuration, APU air, then engine start. Our full PMDG 777 cold-and-dark sequence covers the switch-by-switch procedure without duplicating it here.
- Programme the FMC. Confirm the aircraft position, enter or load the route, select the runway and departure, and inspect every leg. Then complete performance initialisation, thrust limit and take-off reference data. The required flow is explained in our route and performance-entry walkthrough for an airliner FMC.
- Check the route rather than trusting the map. Do not assume a route drawn in the MSFS World Map has populated the PMDG FMC correctly. Activate and execute the intended route, inspect the LEGS pages and remove a discontinuity only when the procedures genuinely connect. A discontinuity associated with radar vectors may be intentional.
- Set the MCP. Turn on both flight directors, arm the autothrottle, set the cleared initial altitude and select the appropriate heading or LNAV mode. Set the take-off speed required by the procedure. LNAV and VNAV may be armed before departure when the programmed route and clearance support them.
- Push back and start the engines. Switch on the beacon, ensure an air source and fuel supply are available, select engine start and move the relevant fuel control switch to RUN after rotation is established. Monitor EICAS until both engines are stable; then check generators, hydraulics and pneumatic systems before shutting down the APU.
- Configure for take-off. Set the calculated flap position and stabiliser trim, place the speedbrake lever in the take-off position, select RTO autobrake, test the flight controls and verify the entered V-speeds. Resolve any EICAS warning or take-off configuration alert before entering the runway.
- Take off with TO/GA. Line up, confirm the runway and press a TO/GA switch or the appropriate simulator control. Verify take-off thrust and the expected modes on the flight-mode annunciator. At VR, rotate smoothly towards the flight-director command; after a positive climb, retract the landing gear.
- Clean up on schedule. Follow the flap retraction indications rather than retracting everything immediately. Allow VNAV to manage acceleration and climb, or use the MCP modes required by your clearance. Engage the autopilot only after the aircraft is stable and above the applicable engagement height.
How should I use LNAV, VNAV and the autopilot?
Use LNAV for the lateral FMC route, VNAV for the programmed vertical profile and the MCP as the pilot's clearance boundary. None of those labels proves what the aircraft is doing; the flight-mode annunciator at the top of the primary flight display is the final authority.
| Control | What it does | What to verify |
|---|---|---|
| FMC | Stores the route, constraints and performance plan | The active leg and altitude constraints are correct |
| MCP | Sets selected speed, heading, altitude and autopilot modes | The selected values match your clearance |
| LNAV/VNAV | Commands the programmed lateral and vertical paths | The expected modes are active, not merely armed |
| FMA | Shows what the flight-control system is commanding | Thrust, roll and pitch modes change as expected |
During climb, set standard pressure at the applicable transition altitude and monitor speed, route progress and fuel. If ATC gives a heading, use heading select rather than trying to force LNAV. For a tactical altitude change, FLCH is usually clearer than vertical speed because it protects the selected speed with pitch and thrust.
A mistake we see constantly is pressing MCP controls repeatedly when the aeroplane does not respond. Pause and read the FMA first. You may have an armed mode waiting for capture, an MCP altitude blocking VNAV or an active route leg that cannot be intercepted from the present position.
What should I do before top of descent?
Set up the arrival, approach and landing data before top of descent, then lower the MCP altitude to the next cleared level so VNAV is permitted to descend.
- Select the expected arrival, approach and runway, then inspect every changed leg.
- Enter forecast descent data if available and check the computed top-of-descent point.
- Select the intended landing flap and VREF on the approach reference page.
- Set radio or barometric minima as appropriate.
- Verify the ILS frequency, course and identifier when flying an ILS.
- Reset the altimeters at the applicable transition level during descent.
If the aircraft reaches top of descent while the MCP still contains cruise altitude, VNAV will remain level. Lower it only to an altitude you are cleared or prepared to descend to. If you become high, use speedbrake carefully while monitoring airspeed; extending the landing gear or flaps early is not a substitute for managing the profile.
How do I approach and land the PMDG 777?
For an ILS, intercept the localiser from a sensible angle and the glideslope from below, arm APP and confirm localiser and glideslope capture on the FMA. APP does not tune, identify or create an approach by itself.
Extend flaps in stages without exceeding their placard speeds, lower the landing gear and set the final approach speed derived from VREF and the required wind correction. Arm the speedbrake, select the planned landing autobrake and complete the landing checklist. If the aircraft is not stable by your chosen stabilisation gate, go around rather than trying to rescue the approach close to the ground.
For a manual landing, disconnect the autopilot at a comfortable height, keep the runway aim point stable and make a small flare while closing the thrust levers. After touchdown, verify speedbrake deployment, apply reverse thrust and use the selected autobrake or manual braking. Our 777 approach, flare and go-around procedure covers the final phase in greater depth.
Can the PMDG 777-300ER autoland?
Yes, the PMDG 777 can autoland on a suitable ILS when the aircraft is correctly configured and no relevant failure prevents it. Select and verify the ILS, arm APP, allow the required autopilot engagement and confirm the displayed autoland status, such as LAND 3 or LAND 2. An armed APP button alone does not confirm autoland capability.
Why are LNAV, VNAV or take-off thrust not working?
Most PMDG 777 automation failures come from incomplete FMC data, an incorrect MCP limit or conflicting controller inputs rather than a failed aircraft system.
| Symptom | Likely cause | Fix |
|---|---|---|
| LNAV will not engage | No valid active leg, an unexecuted route or unsuitable intercept geometry | Check the active leg, execute pending changes and use heading select to establish an intercept |
| VNAV will not climb or descend | The MCP altitude blocks the movement, performance data are incomplete or there is no valid vertical path | Set the cleared altitude, inspect the VNAV pages and confirm the active pitch mode |
| No take-off thrust | Autothrottle not armed, TO/GA not pressed or a throttle axis is overriding it | Arm the autothrottle, use TO/GA and remove duplicate or noisy throttle assignments |
| Aircraft will not taxi | Chocks, tug or parking brake still engaged; inverted brake axes; or missing hydraulic pressure | Remove ground restraints, test each brake axis and check engine-driven hydraulic systems |
| Autopilot disconnects or oscillates | Duplicate pitch or roll axes, insufficient dead zone or continuous manual input | Remove duplicate bindings, add a small dead zone and release the controls after engagement |
| ILS does not capture | Wrong approach data, no valid signal, interception from above or excessive intercept angle | Verify frequency, course and identifier, then intercept the localiser and glideslope correctly |
After landing, stow reverse thrust, vacate the runway and complete the after-landing flow: flaps up, speedbrake down, exterior lights and transponder set appropriately, then start the APU before shutting down the engines if gate power is unavailable. Set the parking brake or chocks before moving both fuel control switches to cutoff.