How do I use the Garmin G1000 in Microsoft Flight Simulator?

To use the Garmin G1000 in Microsoft Flight Simulator, power both displays, set the PFD’s CDI to the correct source, enter or activate a route on the MFD, then use the FMS knobs to edit waypoints. Fly the magenta guidance manually or couple it to the autopilot with NAV and APR modes.

What do the Garmin G1000 controls do?

The left-hand primary flight display (PFD) provides flight instruments and navigation guidance, while the right-hand multi-function display (MFD) handles maps, flight plans, procedures and engine information. Some aircraft arrange the units differently, but their basic functions remain the same.

The two-part FMS knob causes much of the confusion. Pressing it normally turns the cursor on or off; the large outer knob moves between fields, while the small inner knob changes characters or values. Mouse interaction labels help identify the inner, outer and push actions.

How do I set up and fly a G1000 route?

A usable G1000 route needs an active flight plan, an active leg and the correct CDI source. A magenta line on the map alone does not prove that the aircraft or autopilot is following it.

1. Power the avionics. Follow the aircraft checklist to switch on the battery, electrical source and avionics buses. Both displays should complete their start-up sequence.
2. Create or load the route. A route made on the World Map will usually appear in compatible aircraft when the flight loads. Our guide to building and checking a route with the MSFS flight planner covers that side of the process.
3. Inspect the active flight plan. Press FPL on the MFD and check the waypoint order, departure, arrival and approach. Look for an active magenta leg rather than relying only on the map.
4. Set the navigation source. Press the PFD’s CDI softkey until GPS is shown for a normal flight-plan route. GPS guidance is magenta; VOR and localiser guidance uses VLOC and is normally green.
5. Take off manually. Establish a stable climb before using the autopilot. The G1000 supplies guidance, but it does not manage take-off power or fly the aircraft merely because a route is loaded.
6. Intercept the route. Use heading mode to point towards the active leg, then arm NAV. NAV may remain armed until the aircraft reaches a suitable intercept angle.
7. Select a vertical mode. Set the target altitude, then use FLC or VS to climb or descend. Merely turning the altitude selector does not command a climb.
8. Monitor the PFD annunciations. The flight-mode annunciator across the top of the PFD shows what is active and what is armed. Trust those labels rather than the button lights alone.

How do I enter a waypoint manually?

Manual waypoint entry is done from the active flight-plan page with the FMS cursor enabled. On the common G1000 NXi-style implementation, use this sequence:

1. Press FPL and then press the FMS knob to activate the cursor.
2. Use the large outer knob to highlight an empty waypoint row.
3. Rotate the small inner knob to begin entering the airport, VOR or intersection identifier.
4. Press ENT to accept the matched waypoint, then confirm its insertion if prompted.
5. Press the FMS knob again to leave cursor mode.

For a quick diversion, press Direct-to, enter or select the identifier, confirm it with ENT and activate it. Direct-to replaces the immediate leg guidance; it does not necessarily rebuild the remaining route in the way you expect.

How do I make the G1000 autopilot follow the route?

To make the autopilot follow a G1000 route, select GPS as the CDI source, establish an intercept and arm NAV mode. The PFD should show NAV or GPS armed before it changes to the active lateral mode.

• HDG follows the heading bug, not the magenta route.
• NAV captures and follows GPS, VOR or localiser guidance according to the selected CDI source.
• FLC controls pitch to maintain a selected airspeed; you still manage engine power.
• VS holds a selected vertical speed. Watch airspeed closely during climbs.
• ALT usually holds the present altitude. It does not make the aircraft climb to the altitude set in the selector.
• APR arms approach guidance, including an ILS glideslope or an eligible RNAV glidepath.

A mistake we see constantly is pressing NAV while the aircraft is flying away from the active leg. Turn towards the course in HDG mode first. If the highlighted leg points to a waypoint behind you, activate the correct leg or use Direct-to before arming NAV.

How do I fly an approach with the G1000?

Load the approach through PROC, choose the correct transition, verify the resulting flight-plan legs and arm APR only when positioned to intercept final approach guidance. Loading an approach adds it to the plan; activating it changes which leg the G1000 treats as active.

For an RNAV approach, retain the GPS CDI source and check whether the procedure provides lateral guidance only or an approved glidepath. For an ILS, verify the localiser frequency and inbound course, select VLOC when required and intercept from below the glideslope. Some implementations switch sources automatically, but the PFD indication must still be checked.

Avoid selecting vectors-to-final unless ATC is actually vectoring you. That option can remove intermediate approach legs you still need. The full procedure, including GPS source selection and APR capture, is covered in our step-by-step RNAV approach guidance.

Why is my G1000 not working?

Most G1000 failures in Microsoft Flight Simulator come from missing electrical power, an inactive cursor, the wrong CDI source or an autopilot mode that is armed but has not captured.

• Both screens are blank: check the battery, alternator or generator, avionics switches and relevant electrical buses. A cold-and-dark aircraft will not power the displays automatically.
• The FMS knob does nothing: press the knob to activate the cursor, distinguish between its inner and outer sections, and check for conflicting cockpit or controller bindings.
• The knob moves the camera: restore cockpit interaction focus and verify that camera controls are not sharing the same mouse or controller input.
• NAV will not capture: confirm that GPS is selected, a valid leg is active and the aircraft is approaching that leg at a sensible angle.
• The aircraft follows the heading bug: HDG is still active. NAV may be armed but waiting to capture, which will be shown on the PFD.
• The aircraft will not climb to the selected altitude: choose FLC or VS after setting the altitude. The altitude selector by itself only sets the capture target.
• APR gives no descent: the procedure may lack vertical guidance, the aircraft may be outside capture limits, or the wrong CDI source may be selected.
• The loaded route looks different: aircraft-specific avionics do not always import World Map departures, arrivals and approaches identically. Inspect the FPL and PROC pages before departure.

For controls that cannot be selected, dead navigation fields or persistent input problems, follow our G1000 and FMS control troubleshooting checks.

Does the G1000 work the same in MSFS 2020 and 2024?

The core G1000 workflow is the same in Microsoft Flight Simulator 2020 and 2024, but individual aircraft can use different avionics builds and customised engine or autopilot pages. Third-party aircraft may also alter, replace or restrict standard G1000 functions.

Learn the PFD annunciations, CDI source selection and FMS cursor first; those skills transfer between versions. When a button or page differs, use the aircraft’s own checklist and cockpit labels rather than assuming every G1000 installation is identical.