Fix PMDG 777 ILS problems in MSFS by checking FMC setup, NAV RAD tuning, station ident, intercept geometry, APP mode and navdata mismatches.
The PMDG 777’s ILS in Microsoft Flight Simulator usually fails because the approach was not selected and executed in its FMC, the ILS frequency or course is wrong or manually overridden, or the aircraft reaches final too high. Check the NAV RAD page and station ident, then arm APP below the glideslope.
How do I set up the PMDG 777 for an ILS approach?
Set up the ILS in the 777’s own FMC and verify its radio tuning before relying on APP mode.
- Select and execute the ILS approach. Use the FMC arrival pages to choose the correct ILS runway and transition, then press EXEC. Selecting a runway in the MSFS World Map or receiving an ATC clearance does not prove that the PMDG FMC has loaded the approach.
- Check the active legs. Make sure the route reaches a sensible intercept with the final approach course. A vectors discontinuity can be valid when using heading vectors; clearing every discontinuity may instead create a direct track towards the runway from an impossible angle.
- Verify NAV RAD tuning. The ILS field should show the intended frequency and front course. Correct any stale manual entry, or delete the manual override to let the FMC resume automatic tuning. If automatic tuning still selects the wrong station, enter the correct ILS frequency and course manually.
- Confirm reception. Look for the decoded station ident and localiser/glideslope indications. A frequency displayed on the CDU is not proof that the receiver has acquired the transmitter.
- Intercept from below. Approach the localiser at a shallow angle, normally no more than about 30 degrees, while level at the published intercept altitude and below the glideslope. Correct QNH matters because an altitude error can place the aircraft physically above the beam.
- Arm APP and watch the FMA. The flight mode annunciator is authoritative: LOC and G/S should arm and then change to captured modes. Selecting LOC alone, where applicable, provides lateral capture but does not arm the glideslope.
There is no Garmin-style GPS/VLOC switch to change in the 777. Its FMC, navigation radios and AFDS manage the source. Our plain-English refresher on localiser and glideslope capture explains the underlying signal geometry.
What does each ILS symptom mean?
The station ident and FMA reveal whether the PMDG 777 has a tuning problem, a bad intercept or an automation issue.
| Symptom | Likely cause | What to do |
|---|---|---|
| No ident or deviation scales | Blank or wrong frequency, aircraft out of range, wrong runway, or faulty airport scenery | Verify NAV RAD tuning and the runway’s ILS ident, then test closer to the published final approach |
| Localiser is alive but LOC will not capture | APP is not armed, the intercept is too steep, or the aircraft is approaching the back course | Use the published front course, reduce the intercept angle and confirm LOC is armed on the FMA |
| LOC captures but G/S remains armed | The aircraft is above the glideslope, LOC-only mode was selected, or the procedure has no glideslope | Confirm it is an ILS rather than a LOC approach, arm APP and reposition below the beam |
| The tuned frequency changes by itself | FMC auto-tuning, AI radio assistance or a conflicting control assignment | Remove incorrect manual entries, disable AI piloting or radio assistance, and inspect duplicated bindings |
| The aircraft captures the wrong final course | Wrong approach, duplicated frequency, back-course reception or scenery mismatch | Compare the station ident, runway, inbound course and FMC approach rather than checking frequency alone |
For a closer look at altitude, intercept angle, nav source and mode sequencing, use our MSFS 2024 checklist for intercept geometry and APP capture. The same core geometry applies to the PMDG 777.
Why is the ILS frequency wrong in the PMDG 777?
A wrong PMDG 777 ILS frequency usually indicates disagreement between the FMC navigation database, the simulator’s radio aid and the installed airport scenery.
If the problem affects only one runway or airport, suspect outdated or duplicated scenery first. Temporarily remove the affected airport add-on, check for another package covering the same airport, and repeat the approach using the stock scenery. A small published course difference can result from magnetic-data changes, but a different frequency or station ident is a stronger sign of mismatched data.
If every airport is affected, inspect the FMC setup, persistent manual tuning, aircraft installation and radio-assistance settings. Updating only one source can preserve the mismatch, so the lasting fix is to align the navigation data and scenery rather than manually correcting every approach.
How can I tell whether PMDG or MSFS is at fault?
A controlled comparison at an unmodified airport quickly separates an aircraft problem from a simulator or scenery problem.
- Choose a stock airport with a straightforward ILS and use clear weather.
- Load the PMDG 777, programme the approach, verify NAV RAD and establish below the glideslope on a shallow intercept.
- Check the ident and FMA. If the 777 receives and captures both beams, the original airport or its data was the likely cause.
- Repeat in a default aircraft. If the default aircraft receives the same ILS but the 777 does not, concentrate on PMDG tuning, FMC data, assistance settings or installation conflicts.
If neither aircraft receives the signal, follow our simulator-wide ILS fault checklist and inspect the airport scenery rather than repeatedly changing the 777’s autopilot settings.
Does ILS capture mean the PMDG 777 should autoland?
No: ILS capture and autoland are separate stages, so successful LOC and G/S capture does not by itself guarantee an automatic touchdown.
For an autoland, monitor the FMA for an autoland status such as LAND 3 or LAND 2 and, later, FLARE and ROLLOUT. Aircraft configuration, AFDS or radio-altimeter faults, and loss of a stable ILS signal can prevent those modes even when the approach initially captures correctly.
If the PFD shows NO AUTOLAND while LOC and G/S remain captured, the ILS is supplying guidance but the autoland criteria have not been met. Continue manually only when the approach is stable and appropriate; otherwise go around and correct the separate autoland problem.