How do I use the G1000 in Prepar3D?

To use the G1000 in Prepar3D, power the aircraft’s electrical and avionics systems, use the PFD for flight instruments and the MFD for navigation, enter or load a route, select GPS or VLOC with CDI, then arm the appropriate autopilot and approach modes while monitoring every capture.

Start with the aircraft’s G1000 implementation

The exact G1000 functions available in Prepar3D depend on the simulator version, aircraft and gauge package. A default aircraft may use Prepar3D’s shared flight-plan system, while a complex add-on can have its own navigation database, route importer and autopilot logic.

Do not assume every real Garmin or modern G1000 NXi feature is modelled. Check the aircraft manual when a button, procedure page or vertical-navigation function behaves differently from another G1000-equipped aircraft.

What do the G1000 controls do?

The PFD handles primary flight information and guidance, while the MFD is normally used for the moving map, flight plan, navigation data and aircraft systems.

Mouse-wheel, left-click and right-click behaviour can vary between virtual cockpits. Use cockpit tooltips or a pop-up panel where provided. Our detailed guide to G1000 knobs, pages and navigation modes explains the underlying Garmin workflow in more depth.

How do I power up the G1000 in Prepar3D?

The G1000 will start only when its displays and avionics bus receive electrical power.

1. Use a ready-to-fly state while learning. This removes cold-and-dark electrical problems from the lesson.
2. For a cold-and-dark start, follow the aircraft checklist. Energise the battery and electrical system, start the engine as required, bring the alternator or generator online, and then switch on the avionics.
3. Allow the displays to initialise. Confirm that both screens complete their start-up sequence and acknowledge any prompt presented by that implementation.
4. Check display brightness. A fully dimmed screen can look unpowered even when its electrical bus is live.

How do I enter a flight plan?

The simplest route-entry method in a default Prepar3D aircraft is usually to load a simulator flight plan before departure.

Create the route through Prepar3D’s planner, load it into the flight and then inspect the G1000’s FPL page. Our Prepar3D flight-planning instructions cover route creation, saving and loading without repeating that process here.

For manual entry, use this basic sequence:

1. Press FPL and activate the cursor.
2. Use the outer FMS knob to move between legs or fields.
3. Use the inner knob to enter an airport, VOR, intersection or other recognised identifier.
4. Press ENT to confirm each selection.
5. Check the active leg, magenta course and next-waypoint field before departure.

Some simplified gauges display the simulator’s active route but do not support full editing from the panel. Conversely, some add-on G1000 units ignore Prepar3D’s route and require an aircraft-specific import. If the route appears on Prepar3D’s map but not on the MFD, determine which flight-plan source that aircraft uses.

Flying directly to a waypoint

Direct-To is the quickest way to make a waypoint the active destination.

1. Press the Direct-To control.
2. Select the identifier field and enter the waypoint.
3. Press ENT to confirm the identified waypoint.
4. Confirm activation if a second prompt appears.
5. Verify the new active leg and course on both the PFD and MFD.

A Direct-To command can bypass earlier flight-plan legs. Cancel it or activate the intended leg if the aircraft later turns towards the wrong waypoint.

How do I make the autopilot follow the G1000?

The autopilot follows the selected navigation source and active mode, not merely the line shown on the MFD.

1. Set the heading and altitude references. Move the heading bug and preselect the required altitude before engaging automation.
2. Select the correct CDI source. Use GPS for a GPS flight-plan leg or VLOC for a VOR, localiser or ILS.
3. Establish an intercept. Use HDG mode to approach the desired course at a sensible angle.
4. Arm NAV or APR. NAV tracks an en-route course; APR provides approach capture logic where supported.
5. Engage the autopilot and inspect the PFD annunciations. Confirm which lateral and vertical modes are active and which are only armed.

A mistake we see constantly is pressing NAV and then watching the aircraft continue straight ahead. Typical causes are the wrong CDI source, no active flight-plan leg, an excessive intercept angle or NAV being armed but not yet captured.

ALT holds or captures altitude according to the aircraft’s autopilot, while VS or FLC controls the climb or descent where modelled. The autopilot is not an autothrottle: power, propeller and mixture still require manual management unless the aircraft explicitly provides automatic thrust control.

How do I fly GPS and ILS approaches?

GPS and ILS approaches use different navigation sources, so the CDI selection must match the procedure being flown.

GPS approach

1. Use PROC to select the approach and transition, or load it through the route system supported by the aircraft.
2. Choose load or activate carefully; activating too early may send the aircraft directly towards an approach leg.
3. Confirm that GPS is the CDI source and that the correct leg is active.
4. Intercept the final approach course and arm APR if the implementation supports approach guidance.
5. Check the PFD for lateral and, where available, vertical guidance capture.

Not every simulated GPS approach supplies a vertical path. Missing procedures can also result from the aircraft and Prepar3D using different navigation-data sources.

ILS approach

1. Tune the ILS frequency into the active NAV receiver and identify the station where the simulation permits it.
2. Set the published inbound course if the aircraft’s CDI requires one.
3. Select VLOC rather than GPS.
4. Intercept the localiser and arm APR.
5. Approach the glideslope from below and verify separate localiser and glideslope captures on the PFD.

Some G1000 implementations switch from GPS to VLOC automatically during an ILS procedure, but others do not. We recommend checking the CDI source yourself rather than relying on that transfer.

Why isn’t the G1000 working?

Most Prepar3D G1000 faults come from electrical power, an inactive route, the wrong navigation source or confusion between armed and active autopilot modes.

If an add-on aircraft behaves differently after you have verified these basics, use its documentation rather than applying settings intended for Prepar3D’s default G1000. Aircraft developers can replace the navigation, electrical and autopilot logic even when the panel looks almost identical.