Why are G1000 or FMS controls and nav fields not working?

In Microsoft Flight Simulator, G1000 and FMS controls usually stop responding because the avionics lack full power, the cursor is inactive, cockpit focus has moved, or a duplicate binding is overriding the input. A grey navigation field may instead be read-only, on the wrong page, or tied to the wrong nav source.

The same diagnostic order applies to MSFS 2020 and MSFS 2024, although interaction settings, menu labels and individual aircraft implementations differ.

What should I check when a G1000 function is not working?

Match the symptom before resetting anything; an unresponsive knob, a locked field and failed autopilot tracking have different causes.

Why is the FMS knob on the G1000 not working?

The G1000 FMS knob only edits a selectable field after its centre push function has activated the cursor. Rotating the knob without pressing it usually changes pages rather than editing data.

With the cursor inactive, the outer and inner rings normally move through page groups and individual pages. With the cursor active, the outer ring moves between fields or character positions, while the inner ring changes the selected value. Use ENT to accept an entry and CLR to remove it or back out.

The centre push, inner ring and outer ring are separate virtual clickspots. Zoom towards the bezel and confirm that the interaction hint identifies the intended part of the knob. A mistake we see often is turning the outer ring repeatedly when the missing action is the centre push.

The FMS knob also does not tune the COM or NAV frequency boxes. Those use their dedicated radio knobs and transfer buttons. Airliner-style CDUs and MCDUs work differently again: entries generally go into the scratchpad first and are then inserted with the adjacent line-select key.

Fix G1000 and FMS controls in the right order

Work through these checks in order so that a simple power or cursor problem is not mistaken for a broken aircraft.

1. Confirm full electrical power. Set the battery, alternator or generator, external power and avionics master as required by the aircraft. Complete any displayed start-up acknowledgement or self-test. If screens are blank, extremely dim or only partly alive, use our avionics power and blank-screen checks first.
2. Open the correct page and activate its cursor. For route editing, open the flight-plan or procedure page and press the FMS knob. Do not expect a data block on the PFD to become editable merely because it is visible.
3. Refocus the cockpit. Close or move away from ATC, the EFB, checklists, toolbars, pop-out instruments and other windows, then click directly on the avionics bezel. Keyboard, controller and VR focus can remain attached to another window even though the cockpit is visible.
4. Test the other cockpit interaction method. Where the simulator offers legacy-style and lock-style interaction, try the alternative. This is especially useful when the mouse wheel reaches the inner ring but not the outer ring, or when the centre push clickspot cannot be selected reliably.
5. Remove competing inputs. Disconnect spare gamepads, radio panels, touch interfaces, secondary throttles and other USB controllers. Search every remaining device profile for duplicate FMS, avionics, COM/NAV, cursor and increase/decrease assignments; the exact command names vary by aircraft and simulator version. If commands appear without deliberate input, follow our MSFS 2024 phantom-input and duplicate-binding checks.
6. Disable automation temporarily. AI radio communications can retune frequencies, while assisted aircraft control can change navigation modes or sources. Turn those features off during diagnosis so they cannot undo a manual entry.
7. Reload the cockpit state. Return to the main menu and start a fresh flight. Restart the simulator if the problem survives the reload; a temporary focus or input state may not clear inside the existing flight.
8. Compare with a default aircraft. Perform the same simple task, such as tuning a standby frequency or creating a direct-to waypoint, in a default Garmin-equipped aircraft. If it works there, investigate the affected aircraft and its avionics packages rather than resetting all controls.

Why will a nav field not highlight or accept input?

A navigation field will not accept input if it is calculated output, belongs to another page or requires a valid source before it can display data.

• Calculated fields such as bearing, distance, ETE and ETA display results; they are not direct entry boxes.
• Active-leg summaries are normally changed through the flight-plan page, not by clicking the summary shown on the PFD or map.
• COM and NAV frequency fields use the dedicated radio tuning controls rather than the FMS cursor.
• Blank or dashed fields can mean that no valid waypoint, GPS position or radio signal is available.
• Configurable data fields may require a page menu or data-field setup command instead of direct editing.
• Procedure data may be constrained by the loaded route, the active leg or the flight phase in a custom FMS.

On a Garmin flight-plan page, look for a visible flashing cursor before turning the knob. On an airliner CDU or MCDU, type the value into the scratchpad and use the line-select key beside the target field; clicking the displayed text often has no entry function.

Why does the knob work on one screen but not the other?

Each G1000 bezel normally controls its own display and active pane, so a working MFD knob does not prove that the PFD has focus or an editable field selected. Check that the intended screen owns the cursor and that a field is highlighted before turning the knob.

Why do values change and then jump back?

A value that changes and immediately returns is usually being overwritten by another controller, a repeating encoder, an external panel or an assistance feature.

The quickest proof is a mouse-and-keyboard-only test. If the problem disappears, reconnect devices one at a time and watch for the first one that makes the value skip, reverse or reset. Check all device profiles: clearing the keyboard assignment alone will not stop a duplicate command coming from a throttle, gamepad or radio panel.

Why is the route loaded but the aircraft will not follow it?

A displayed route does not command the aircraft unless the correct navigation source, active leg and autopilot mode are selected.

• For GPS flight-plan tracking, select the GPS or FMS source; on a Garmin display it is usually shown in magenta.
• For a VOR or localiser, select VLOC and place the correct frequency in the active NAV radio; this source is usually shown in green.
• Confirm that a leg is active, rather than merely listed, and that no route discontinuity is blocking sequencing.
• Check for SUSP or another sequencing hold near an approach or missed-approach point.
• Arm or engage the appropriate NAV or LNAV mode. If it remains armed, the aircraft may not yet be in a position to capture the course.

If conventional radio navigation is the part that fails, our VOR frequency, reception and GPS/VLOC troubleshooting separates a tuning problem from an avionics-control fault.

How can I tell if the aircraft or add-on is the problem?

A fault limited to one aircraft is probably caused by that aircraft, its custom avionics or a conflicting modification rather than the global control setup.

Repeat one exact operation in a default aircraft under the same power state. If the default cockpit works, update or reinstall the affected aircraft and temporarily disable packages that replace its avionics or cockpit behaviour. On PC, suspect Community packages can be removed or disabled for the test.

If every aircraft fails in the same way, return to electrical power, cockpit focus, interaction settings and duplicated device assignments. Those are simulator-wide causes; reinstalling one aircraft will not correct them.